What kind of problem are you having accessing your Cloudscape database?
Tip: Cloudscape errorCodes (2000, 3000, 4000) indicate levels of severity, not specific error conditions. In diagnosing Cloudscape problems, pay attention to the given sqlState value.
Cloudscape has discovered
a security exposure for version 5.1 of Cloudscape Network Server
WebSphere customers should download fix PQ86524, which will upgrade the Cloudscape version in WebSphere to the level that rectifies the problem.
Please Note the following changes with respect to the new Cloudscape version:
Unexpected IOException wrapped in SQLException, accessing Cloudscape database
This problem can occur because Cloudscape databases use a large number of files. Some operating systems, such as the Solaris Operating Environment, limit the number of files an application can open at one time. If the default is a low number, such as 64, you can get this exception.
If your operating system lets you configure the number of file descriptors, you can correct the problem by setting the number to a high value, such as 1024.
The "select for update" operation causes table lock and deadlock when accessing Cloudscape
If a select for update operation on one row locks the entire table, which creates a deadlock condition, there might be undefined indexes on that table. The lack of an index on the columns you use in the where clause can cause Cloudscape to create a table lock rather than a row level lock.
To resolve this problem, create an index on the affected table.
ERROR XSDB6: Another instance of Cloudscape may have already booted the database "database"
This problem occurs because Cloudscape embedded framework only allows one Java virtual machine (JVM) to access the database instance at a time.
To resolve this problem:
Error "The version of the IBM Universal JDBC driver in use is not licensed for connectivity to Cloudscape databases"
At the client runtime, an error similar to the following occurs:
The version of the IBM Universal JDBC driver in use is not licensed for connectivity to Cloudscape databases. To connect to this DB2 server, please obtain a licensed copy of the IBM DB2 Universal Driver for JDBC and SQLJ. An appropriate license file db2jcc_license_*.jar for this target platform must be installed to the application classpath. Connectivity to Cloudscape databases is enabled by any of the following license files: { db2jcc_license_c.jar, b2jcc_license_cu.jar, db2jcc_license_cisuz.jar }The problem occurs because an incorrect JDBC driver jar file name is specified in the class path for JDBC provider. For example, the jar file name may have an extra '_', as follows:
${UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license__cu.jar
To resolve the problem:
Running an application causes a runtime exception which produces an unreadable message.
At client runtime, you may receive a message similar to the following: Caused by: com.ibm.db2.jcc.a.SqlException: DB2 SQL error: SQLCODE: -1, SQLSTATE: 42X05, SQLERRMC: ANNUITYHOLDER20^T42X05
The problem occurs because the property retrieveMessagesfromServerOnGetMessage, which is required by WebSphere Application Server, has not been set.
To resolve the problem, on the admininstrative console
Unexpected SQL exception
after initially configuring Cloudscape Network Server for use with WebSphere
Application Server, version 5.0.2 or later
Problem | When running WebSphere Application Server, version 5.0.2 or later,
with Cloudscape using the Network Server framework, you receive the following
exception:com.ibm..db2.jcc.b.SQLException: Unexpected throwable caught java.lang.UnsatisfiedLinkError: DBConnect |
Recommended response | Verify that you have supplied a value for the driverType data source custom property, and that the value is not 2. For more information about configuring Cloudscape Network Server using the Universal JDBC driver, refer to the Cloudscape section of the topic . |
The administrative console
displays DB2 settings instead of Cloudscape settings when you create a new
Cloudscape JDBC Provider Network Server using the universal JDBC driver provider.
Problem | When creating a new Cloudscape JDBC Provider Network Server using
the universal JDBC driver provider through the administrative console in Websphere
Application Server, version 5.0.2 or later, be aware that the administrative
console fills in the DB2 universal data sources settings by default instead
of the Cloudscape Network Server settings. These erroneous settings include:
|
Recommended response | If you want to create the Cloudscape JDBC Provider Network Server
using the universal JDBC driver provider, you must modify the entries in the
administrative console as follows:
|