Error Messages (N)

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z #

No valid license was found

"No valid license was found" errors tend to arise from one of three scenarios:

1. The target machine contains more CPUs than the license permits. Users must obtain licensing for all CPUs, in this instance.

2. Hyperthreading causes the OpenLink license manager to detect more CPUs than actually exists in the machine. Users may disable hyperthreading. Alternatively, users may contact OpenLink Sales or Support. Support is actively addressing this problem.

3. The license pertains to a major release of software, which differs from the major release of the software installed on the machine. Users must contact OpenLink Sales to obtain the appropriate license.

No valid license found (HSODBC)

Do you encounter OpenLink license errors with Oracle's HSODBC? If you do, take the following action:

1. Ensure that you have a valid OpenLink license file.

2. Ensure that the license file is placed in the same directory as an OpenLink Single-Tier client driver or an OpenLink Multi-Tier server components installation.

3. Ensure that binary ftp was used to transfer any license, when ftp is necessary. ASCII ftp corrupts licenses.

4. Ensure that openlink.sh or openlink.csh was run from the root of the relevant OpenLink installation. openlink.sh is compatible with bourne and bash shells. openlink.csh is compatible with C shells. This sets ODBCINI, ODBCINSTINI, and other environment variables that facilitate ODBC connectivity.

5. Use echo $OPL_LICENSE_DIR to see if the OPL_LICENSE_DIR environment variable is set. If not, export the variable from the commandline. It points to the directory that contains your OpenLink license file. For example:

export OPL_LICENSE_DIR=/usr/openlink/bin

6. Ensure that you can establish basic ODBC connections using simple applications like odbctest or iodbctest.

7. Ensure that the environment variables set in Step #4 are available at the time HSODBC is run.

8. Add OPL_LICENSE_DIR to the inithsodbc.ora file, if licensing problems persist. You may also set other environment variables like ODBCINI, the Single-Tier OPENLINKINI, and so on in inithsodbc.ora, as needed.

9. Test.