Troubleshoot databases
Contents
- Unable to connect to database
- When using multi-rows in a database, you cannot have application data objects referencing each other.
- Unable to access Cloudscape databases outside of WebSphere Portal while WebSphere Portal is running
- Administrator login fails with concurrent DB2 connections on AIX
- Configuration task to drop database fails on DB2
- Configuration task to validate database on DB2 fails
- Unsuccessful execution error in DB2 for OS/390 and z/OS
- SQL error SQL0969N in SystemErr log with DB2 for OS/390 and z/OS
- Database import for Oracle fails on validation
- xError messages when inserting or updating a LOB greater than 4k on Oracle
- WebSphere Portal Server throws exceptions every time it starts
- Exceptions occur with SQL Server
- Unable to transfer database to SQL Server
Problem: Unable to connect to database
When attempting to connect to a database using a password that is about to expire, you might receive connection errors.
If you are trying to connect to a database using a valid username and password but are receiving a connection error, it might be that you are using a password that is about to expire. When WebSphere Portal tries to make a connection to the database, a warning message is returned. This is not what WebSphere Portal was expecting and will, therefore, give a connection error.
Solution: You can solve this by manually resetting the password for your database user from within the database management system. This will stop the warning messages and allow WebSphere Portal to connect to the database without a problem.
Problem: When using multi-rows in a database, you cannot have application data objects referencing each other.
When using multi-rows in a database, you cannot have application data objects referencing each other which causes circular references.
Solution: Do not use multi-row schema for a session database.
Problem: Unable to access Cloudscape databases outside of WebSphere Portal while WebSphere Portal is running
The Cloudscape environment allows only one JVM process to access the Cloudscape database. While Cloudscape provides Network Server framework to allow multiple users to connect simultaneously, it does not support two-phase commits.
Solution: To access or query the Cloudscape database without stopping WebSphere Portal, edit the My Query portlet to configure SQL queries for the Cloudscape database you want to access.
Be sure to enter the correct JDBC driver and Database URL in the portlet fields, as the database user ID. The default Cloudscape values for these fields are as follows:
JDBC Driver: com.ibm.db2j.jdbc.DB2jDriver Database URL: jdbc:db2j:/location_of_cloudscape_directory You can set this value to the database directory name or an absolute path. For example, this URL might be...
jdbc:db2j:/databases/default_datasource...on UNIX or...
jdbc:db2j:"c:/my databases/default_datasource"
Problem: Administrator login fails with concurrent DB2 connections on AIX
If you have DB2 on AIX, there is an issue with concurrent database connections that causes login difficulties. For multiple instances of WebSphere Portal, logging in to the portal page as an administrator fails for the second WebSphere Portal instance after running the database transfer. The following error displays in the log:
SQL1041N The maximum number of concurrent databases have already been started.
Solution: To correct this issue, increase the maximum numdb MAX_NETBIOS_CONNECTIONS. For example, enter the following commands at the database prompts:
set client MAX_NETBIOS_CONNECTIONS 254
When the task is completed, the output displays a message indicating successful completion.
Problem: Configuration task to drop database fails on DB2
If the database already exists it will be removed (or dropped) as part of the install process. This error can occur if the existing database is in use or locked by another process.
Solution: This problem can be solved using one of the following options:
- Open the IBM DB2 Control Center, and manually drop the appropriate database.
- Restart the machine to release the database and allowed the DB2 DROP command to complete.
Problem: Configuration task to validate database on DB2 fails
If the configuration task used to validate a database connection (for example, validate-database-connection-wps) is failing and displaying the message "No suitable driver," this indicates that WebSphere Portal is unable to establish the necessary JDBC connection to DB2.
Solution: This error can occur if you are attempting to connect to a DB2 database instance that was created with the 64-bit setting. You can verify the bit setting by running the DB2 command db2level. If this has happened, remove the database instance, and create a new one with the 32-bit setting. Although your system might support the creation of 64-bit database instances, WAS may not support the 64-bit configuration.
Problem: Unsuccessful execution error in DB2 for OS/390 and z/OS
If you have not enabled the database table spaces, the following error will occur during installation:
SQL0904N Unsuccessful execution caused by unavailable resource. SQLState=57011
Solution: If this error occurs, create a cataloged VSAM linear database for the table space or use the STOGROUP keyword when creating the table space. See the instructions in Creating databases and users in DB2 for OS/390 and z/OS.
Problem: SQL error SQL0969N in SystemErr log with DB2 for OS/390 and z/OS
The following error might appear in the SystemErr.log:
SQL0969N There is no message text corresponding to SQL error "-873" in the message file on this workstation. The error was returned from module "DSNX0END" with the original tokens. SQLSTATE=53090
Solution: This error occurs when the Personalization databases were created with one CCSID, and the resource tables are in a different database that has a different CCSID. Personalization databases should be created with CCSID UNICODE, and all the tables used with Personalization should be in databases with the same CCSID.
Problem: Database import on Oracle fails on validation
During the database import that occurs when configuring WebSphere Portal for Oracle, the database validation task might fail.
Solution: Verify that the Oracle database have been created using a UTF-8 character set.
Problem: Error messages when inserting or updating a LOB greater than 4k on Oracle
When inserting or updating a LOB (BLOBS and CLOBS) that are greater than 4k, you might receive see exceptions like the following:
java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column
Data size bigger than Max size for this type: xxxx. SQL State = <null>, Error Code = 17,070
Solution: This may happen if you use an Oracle database and enable session persistence in WAS. Install WAS PQ77056 to solve this problem with the session database.
Problem: WebSphere Portal Server throws exceptions every time it starts
When using an Oracle database, the WebSphere Portal Server throws an exception every time it starts.
Solution: Delete everything in was_root/translog, where was_root is the directory where WAS is installed. Grant the users for each database select rights on DBA_PENDING_TRANSACTIONS using the following command, where dbusr is the database user, for example wpsdbusr.
SQL>grant select on dba_pending_transactions to dbusr;If you are storing all data on one database run this command only for the wpsdbusr. If you are using more than one database to store data, run this command to grant privileges to users of each database you are using.
Problem: Exceptions occur with SQL Server
You might get the following error in wps_date-time.log where date and time are variables for the log date and time:
---- Begin backtrace for Nested Throwables
java.sql.SQLException: DSRA9002E: ResourceException with error code null: javax.resource.ResourceException: enlist: caught Exception
at com.ibm.ejs.j2c.XATransactionWrapper.enlist(XATransactionWrapper.java(Compiled Code))
at com.ibm.ejs.j2c.ConnectionEventListener.interactionPending(ConnectionEventListener.java(Compiled Code))
at com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.processInteractionPendingEvent(WSRdbManagedConnectionImpl.java(Compiled Code))
at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.beginTransactionIfNecessary(WSJdbcConnection.java(Compiled Code))
at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.prepareStatement(WSJdbcConnection.java(Compiled Code))
at com.ibm.ws.rsadapter.jdbc.WSJdbcConnection.prepareStatement(WSJdbcConnection.java(Compiled Code))
at com.ibm.wps.datastore.core.DataStoreContext.prepareStatement(DataStoreContext.java(Inlined Compiled Code))Solution: This error occurs if Microsoft Type 4 JDBC Drivers are not installed with versions 2000 SP3a or higher. Download and install SQL Server 2000 SP3a or higher from http://www.microsoft.com/sql/downloads.
Problem: Unable to transfer database to SQL Server
If the database transfer from Cloudscape to SQL Server fails after multiple attempts, there may be one or more foreign key references in the tables in that database, and the transfer tool may not be able to drop and recreate the tables.
This is an example of the error you might see in the console and ConfigTrace.log if you run into this problem:
[java] CREATE TABLE ICMUT01014001(COMPCLUSTERID INTEGER NOT NULL,COMPONENTID CHAR(18) NOT NULL,ITEMID CHAR(26) NOT NULL,VERSIONID SMALLINT NOT NULL,ACLCODE INTEGER NOT NULL,SEMANTICTYPE INTEGER NOT NULL,EXPIRATIONDATE DATETIME,COMPKEY CHAR(23) NOT NULL,CREATETS DATETIME NOT NULL,CREATEUSERID CHAR(32) NOT NULL,LASTCHANGEDTS DATETIME NOT NULL,LASTCHANGEDUSERID CHAR(32) NOT NULL,ATTR0000001008 VARCHAR(255),ATTR0000001019 VARCHAR(255), ATTR0000001012 SMALLINT,ATTR0000001014 VARCHAR(255),ATTR0000001015 SMALLINT,ATTR0000001016 SMALLINT,ATTR0000001017 SMALLINT,ATTR0000001000 VARCHAR(255), PRIMARY KEY (COMPKEY), UNIQUE (COMPONENTID,VERSIONID))
[java] Error during statement execution!
[java] java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]There is already an object named 'ICMUT01014001' in the database.
[java] at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
[java] at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
[java] at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
[java] at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
[java] at com.microsoft.jdbc.sqlserver.tds.TDSExecuteRequest.processReplyToken(Unknown Source)
[java] at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
[java] at com.microsoft.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown Source)
[java] at com.microsoft.jdbc.base.BaseStatement.commonTransitionToState(Unknown Source)
[java] at com.microsoft.jdbc.base.BaseStatement.postImplExecute(Unknown Source)
[java] at com.microsoft.jdbc.base.BasePreparedStatement.postImplExecute(Unknown Source)
[java] at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown Source)
[java] at com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown Source)
[java] at com.microsoft.jdbc.base.BasePreparedStatement.executeUpdate(Unknown Source)
[java] at com.ibm.wps.config.SqlProcessor.process(SqlProcessor.java:433)
[java] at com.ibm.wps.config.SqlProcessor.main(SqlProcessor.java:602)
[java] (ErrCode=2714, SqlState=42S01)Solution: Manually drop the tables and retry the database transfer.
See also
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.