• Home Page
• Support
• Product Knowledgebase
• USQL
• USQL Common Issues
• USQL Common Issues

U/SQL - Common Issues

E3015 - Duplicate client licence detected

Likely Cause

This error is usually caused because of the following:

1. Two U/SQL clients have the same client license installed;
2. A U/SQL clients has previously terminated the connection to the U/SQL server abnormally, and the client connection is still cached on the server;
3. A DHCP environment is in use. When a client IP address changes, the U/SQL server will associate the licence with a new machine and believe it to be a duplicate.

Resolution

On Windows

Where the U/SQL Server is installed on a Windows operating system, follow the following steps to determine the exact cause of the E3015 error, and resolve it:

1. Check all U/SQL Client installations, and ensure that each has a unique Client licence installed;
2. Open the U/SQL Service Manager, and open the "Active Licenses" tab. Check that there are no client connections that have been "left behind". If there are any spurious connections, click the "Remove User" button to clear that connection;

On UNIX or Linux

In a non-Windows environment, the E3015 problem can usually be cleared by following the steps below:

1. Check all U/SQL Client installations, and ensure that each has a unique Client licence installed;
2. On the server, navigate to where U/SQL server is installed and open the /bin directory. Run the licmon utility (./licmon). This will perform two tasks:
   1. Clear any cached licenses from memory;
   2. Display a list of all current client connections.
3. If after running licmon the problem persists, you will need to ensure that all client users are disconnected from U/SQL, and stop the server. From the /bin directory, run "./licmon -k", and re-start the U/SQL server.

If after following the steps above, the problem still occurs, please contact Transoft Customer Services.

E3011 - The maximum licensed user count has been reached

Likely Cause

The most common cause of this error is that the user count in the U/SQL server license is too low to support the number of concurrent U/SQL client connections being received. This is also a typical issue where a mixture of U/SQL Client and U/SQL Gateway connections are being used. In general, each connection from a U/SQL gateway client is counted as a separate user by the U/SQL server. In addition, connections to U/SQL from software that can support multiple users, typically software that runs as a service on Windows, are each counted as a separate user.

Another possible cause is that licence slots are being taken by connections that may have been "left behind" due to an abnormal termination of a client. Please refer to the article "E3015 – Duplicate client licence detected" for further information on clearing such connections.

Resolution

The easiest way to monitor which users are consuming server licence slots, is to run the licmon utility on UNIX or Linux, or the U/SQL Service Manager  on Windows. Observe which client applications are using one or many server licenses. It may be that you will need to consider:

• Re-writing programs that require multiple connections to the U/SQL server.
• Speaking to your Transoft account manager about purchasing additional users in your U/SQL server license.

If you believe the cause to be due to a "dead" connection retaining a licence slot on the server, follow the resolution steps provided in the article "E3015 – Duplicate client licence detected".

E3024 - License problem: segment create error

Likely Cause

This error is normally associated with the U/SQL Server, when installed on a SCO UNIX machine. It is caused when the U/SQL Server is unable to create the semaphore that it requires to lock the shared memory block. This indicates that either:

• The operating system has run out of semaphores (the default for SCO UNIX is 10).
• The shared memory block has been killed but a rogue semaphore is persisting.

Resolution

The first step in resolving this issue is to check the semaphores that are active by typing "ipcs –s" from the command line. This will produce a list of all active semaphores, similar to the one shown below (in the example below, the key "4f726582" indicates the U/SQL semaphore has been successfully created):

$ ipcs -s

TID      KEY            MODE       OWNER GROUP
Semaphores:
s 7       0x4f726582 --ra-ra-ra- usqlqa Qcontrol
s 608   0x00001b64 --ra-ra-ra- aulm   Dev

If there are a substantial number of active semaphores on the system, it is likely that either a new semaphore cannot be created, or alternatively, the permissions set for the U/SQL semaphore are incorrect.

The easiest way to resolve this issue is to reboot the UNIX server, which will clear the shared memory and allow the U/SQL semaphore entry to be created. If this does not yield a successful result, please contact Transoft Customer Services.

E3009 - Invalid licence key

Likely Cause

Normally associated with U/SQL Server installations on a UNIX operating system, this error indicates that a licence has not been successfully released from shared memory.

Resolution

The first stage in resolving this issue is to navigate to the /bin directory of the server installation and run the licgen utility.

From the menu, select option 5 – "View & Remove Licence in Memory". This will display a list of all U/SQL licenses held in memory. Remove the licence(s) from memory, and restart the U/SQL server.

If this does not resolve the issue, the second stage is to stop the U/SQL server and run "licmon –k" to remove all licenses from memory.

Note that this will impact all U/SQL users/processes with connections to the server, so if multiple instances of the U/SQL Server are installed on your server, bear in mind that each will need to be restarted.

Finally, if this still has not resolved the E3009 error, you will need to reboot the UNIX machine.

E3007 - Licence does not apply to the current platform

Likely Cause

This error indicates that the U/SQL Server licence which has been installed on the server machine is for a different platform than the one it is installed on (e.g. a licence for Windows is installed on an IBM AIX server).

Resolution

Please contact Transoft Customer Services, providing them with details of the exact error message received, your server operating system, and a copy of your original licence. Customer Services will amend the licence to match your platform, and reissue it. Remove the previous U/SQL Server Licence and replace it with the new one to clear the error.

E3010 - Invalid user type

Likely Cause

This error indicates that the type of connection being attempted is invalid for the U/SQL Server licence that is installed.

This is usually caused when connecting from a Java application via JDBC, or from another application on UNIX or Linux.

Resolution

Examine your server licence to determine if it allows JDBC or UNIX server client connections.  These are enabled by a UD user count, for example:

S12345-U1-UD1…

If your licence does not include "UDx", you will need to contact your Transoft Account Manager and request an upgraded licence. Alternatively, contact Transoft Customer Services.