Troubleshoot databases

 

+

Search Tips   |   Advanced Search

 

 

Unable to connect to database

If Portal receives a connection error when trying to connect to a database using a valid username and password, it might be that the password 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:

We can solve this by manually resetting the password for the 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.

 

Do not use multi-row schema for a session database.

When using multi-rows in a database, we cannot have application data objects referencing each other which causes circular references.

Solution:

Do not use multi-row schema for a session database.

 

Database configuration tasks appear to hang on i5/OS

If a database configuration task appears to hang, check the QSYSOPR queue. The system might require a response in order to complete the task.

To check...

DSPMSG QSYSOPR

Type I to ignore the message so the task will continue.

Type C to to cancel the task.

 

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:

Use the My Query portlet to access Cloudscape databases without stopping WebSphere Portal.

Enter the correct JDBC driver and database URL in the portlet fields, as the database user ID. The default values are...

  • JDBC Driver:

    com.ibm.db2j.jdbc.DB2jDriver

  • Database URL:

    jdbc:db2j:/path/to/cloudscape

    Set to database directory name or an absolute path. For example, on UNIX...

    jdbc:db2j:/databases/wpsdb

    On Windows...

    jdbc:db2j:"c:/my databases/wpsdb"

    Use a forward slash to separate directories since the path is provided to Java.

db_location Location of the Cloudscape database
wpsdb Default datasource

 

Administrator login fails with concurrent DB2 connections on AIX

DB2 on AIX, has an issue with concurrent database connections that causes login difficulties. For multiple installations of WebSphere Portal, logging in to the portal page as an administrator fails for the second WebSphere Portal installation after running the database transfer. The following error displays in the log:

SQL1041N The maximum number of concurrent databases have already been started.

Solution:

Increase max connections by entering the following commands at the database prompt...

set client MAX_NETBIOS_CONNECTIONS 254

When the task is completed, the output displays a message indicating successful completion.

 

Configuration task to drop database fails on DB2

If the database already exists it will be removed (or dropped). 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.

 

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 in the following situations:

  • If you are attempting to connect to a DB2 database installation that was created with the 64-bit client setting. We can verify the bit setting by running the DB2 command db2level.

    If this has happened, remove the database installation, and create a new one with the 32-bit client setting.

  • If you are using UNIX and have not exported the DB2 user profile.

 

Unsuccessful execution error in IBM DB2 Universal Database for 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 z/OS.

 

SQL error SQL0969N in SystemErr log with DB2 for 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 DB2 Content Manager databases required by Personalization were created with one CCSID, and the resource tables are in a different database that has a different CCSID.

DB2 Content Manager databases should be created with UNICODE, and all the tables used with Personalization should be in databases with the same CCSID.

 

Database transfer on Oracle fails on validation

During the database transfer 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.

 

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_profile_root/tranlog

Grant the users for each database select rights on DBA_PENDING_TRANSACTIONS. For example...

SQL>grant select on dba_pending_transactions to wpsdbusr;

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.

 

Exceptions occur with Microsoft SQL Server Enterprise Edition

You might get the following error in trace.log:

---- 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.

 

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.

 

WebSphere Portal hangs after setting trace logging for SQL Server

Turning tracing on for the SQL Server causes WebSphere Portal to hang.

Solution:

Register with DataDirect and download the spy.jar file. Put the file in...

c:/dbdrivers/sqlserver/lib/spy.jar

 

Database transfer fails when transferring multiple domains

When transferring from one database to another, the transfer may fail if the properties are not set correctly.

Solution:

When transferring from one database to another, if the properties...

  • DbUser
  • DbUrl
  • DbPassword

...are not the same across domains, the DataSourceName value must differ accross domains.

 

Database transfer fails with the message "maximum open cursors exceeded" when Oracle Enterprise Edition is the source database

When attempting database transfer from Oracle to another supported database, the transfer might fail with the following exception:

ORA-01000: maximum open cursors exceeded

Solution:

Increase the open_cursor value on the Oracle database and start the transfer again. The minimum recommended value for open_cursor is 1500, but this value should be increased according to the environment.

 

Database Transfer fails on Oracle during LikeMinds table creation

When transferring to Oracle, you may get the following error:

BUILD FAILED file:../config/inclueds/lmdb_cfg.xml:414:ERROR:

Solution:

This error occurs because of a locking issue with Oracle that can occur during table creation. Wait a few moments and restart the transfer.