Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

---

 

Troubleshoot databases

This section contains information that can assist you in preventing, identifying, and correcting problems related to WebSphere Portal Express. For information related to specific components, see the appropriate troubleshooting topic.

• i5/OS: See the Troubleshooting DB2® for i5/OS™ database topic in the System i5 Information Center for information about solving problems with the performance of your DB2 for i5/OS database.

• Problem: Unable to connect to database

• Problem: When using multi-rows in a database, you cannot have application data objects referencing each other.

• Problem: Database configuration tasks appear to hang on i5/OS

• Problem: Configuration task to drop database fails on DB2

• Problem: Database transfer on Oracle fails on validation

• Problem: WebSphere Portal Express Server throws exceptions every time it starts

• Problem: Exceptions occur with Microsoft SQL Server Enterprise Edition

• Problem: Unable to transfer database to SQL Server

• Problem: WebSphere Portal Express hangs after setting trace logging for SQL Server

• Problem: Database transfer fails when transferring multiple domains

• Problem: Database transfer fails with the message "maximum open cursors exceeded" when Oracle is the source database

• Problem: Database Transfer fails on Oracle during LikeMinds table creation

• Problem: Error received when running reorgchk command on DB2

• Problem: Fix pack upgrade fails with SQLCODE: -204, SQLSTATE: 42704

• Error received when transferring data to an Oracle database using the Turkish locale

 

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 Express tries to make a connection to the database, a warning message is returned. This is not what WebSphere Portal Express 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 Express 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: Database configuration tasks appear to hang on i5/OS

 

Solution: If a database configuration task appears to hang, check the QSYSOPR queue on your i5/OS system for messages. The system might require a response from you in order to complete the task. To check the QSYSOPR queue, type the following command on an OS/400 command line:

DSPMSG QSYSOPR Please type I to indicate you wish to ignore the message so the task will continue. You may also type C to indicate you wish to cancel the task.

 

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

 

Problem: Database transfer on Oracle fails on validation

During the database transfer that occurs when configuring WebSphere Portal Express for Oracle, the database validation task might fail.

 

Solution: Verify that the Oracle database have been created using a UTF-8 character set.

 

Problem: WebSphere Portal Express Server throws exceptions every time it starts

When using an Oracle database, the WebSphere Portal Express Server throws an exception every time it starts.

 

Solution: Delete everything in was_profile_root/translog, where was_profile_root is the directory where WebSphere Application Server 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 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 from http://www.microsoft.com/sql/downloads.

 

Problem: Unable to transfer database to SQL Server

If the database transfer from the default database 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.

 

Problem: WebSphere Portal Express hangs after setting trace logging for SQL Server

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

 

Solution: Register with DataDirect and download the spy.jar file. Put the file in the c:/dbdrivers/sqlserver/lib/spy.jar directory.

 

Problem: 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 DbUser, DbUrl, and DbPassword properties are not the same across domains, the DataSourceName value must differ from the DataSourceName values of the other domains. The datasource values should be changed if any domain has a different user, password, or URL value than another domain.

For example, if transferring from the default database to DB2, use the same datasource for all domains if the DbUser, DbUrl, and DbPassword for those domains are the exact same. If any of these differ, that domain must be different then the rest.

 

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

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

ORA-01000: maximum open cursors exceeded

 

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

 

Problem: 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: Error during the execution of sql files

 

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

 

Problem: Error received when running reorgchk command on DB2

When running the reorgchk command, the command db2 reorgchk update statistics on table all > xyz.out may fail with the following error (error 964):

SQL2310N  The utility could not generate statistics.

 

Solution: If you receive this error, increase the LOGFILSIZ and LOGSECOND setting of the corresponding database. The default values of these settings are 1000 and 20, respectively. Refer to the DB2 documentation for details on how to apply the new setting.

 

Problem: Fix pack upgrade fails with SQLCODE: -204, SQLSTATE: 42704

Problem: During a fix pack upgrade using PTF6011 you may encounter the following exception trace:

define-schema-sync:
	     [copy] Copying 1 file to /opt/WebSphere/PortalServer/config/work/sync/v6.0/database/db2
	     [echo] DbDomain = sync 	     [echo] SyncDbType = db2


	  [sqlproc] action: execute-sql-scripts 	  [sqlproc] _________________________________________________________
	  [sqlproc] DbDomain: sync 	  [sqlproc] Database autocommit parameter true 	  [sqlproc] Reading file /opt/WebSphere/PortalServer/config/work/sync/v6.0/database/db2/defineSchema_sync.run 	  [sqlproc] Connected to jdbc:db2://brooklyn.rtp.raleigh.ibm.com:50000/wpsdb:returnAlias=0;
	  [sqlproc] Setting database autocommit to:true 	  [sqlproc] CREATE TABLE sync.SYNC_DEVICE  (
	  [sqlproc]     DEVICEID        VARCHAR(255)    NOT NULL, 	  [sqlproc]     DEVICETYPE      VARCHAR(255), 	  [sqlproc]     MANUFACTURER    VARCHAR(255), 	  [sqlproc]     MODEL           VARCHAR(255), 	  [sqlproc]     LANGUAGE        VARCHAR(255), 	  [sqlproc]     OEM             VARCHAR(255), 	  [sqlproc]     FIRMWAREVER     VARCHAR(255), 	  [sqlproc]     SOFTWAREVER     VARCHAR(255), 	  [sqlproc]     HARDWAREVER     VARCHAR(255), 	  [sqlproc]     MAXMSGSIZE      INTEGER, 	  [sqlproc]     MAXOBJSIZE      INTEGER, 	  [sqlproc]     SUPPORTSLRGOBJS CHAR(1), 	  [sqlproc]     SUPPORTSNOFM    CHAR(1), 	  [sqlproc]     SUPPORTSUTC     CHAR(1), 	  [sqlproc]
	  [sqlproc]     CONSTRAINT PKDEVICE PRIMARY KEY (DEVICEID)
	  [sqlproc]
	  [sqlproc] )IN SYNCREGTBS

	  [sqlproc] Error during statement execution!
	  [sqlproc] com.ibm.db2.jcc.a.SqlException: DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704, SQLERRMC: SYNCREGTBS
	  [sqlproc]     at com.ibm.db2.jcc.a.lg.e(lg.java:1600)
	  [sqlproc]     at com.ibm.db2.jcc.a.lg.b(lg.java:1164)
	  [sqlproc]     at com.ibm.db2.jcc.b.gb.h(gb.java:217)
	  [sqlproc]     at com.ibm.db2.jcc.b.gb.b(gb.java:46)
	  [sqlproc]     at com.ibm.db2.jcc.b.w.b(w.java:40)
	  [sqlproc]     at com.ibm.db2.jcc.b.vb.e(vb.java:118)
	  [sqlproc]     at com.ibm.db2.jcc.a.lg.m(lg.java:1159)
	  [sqlproc]     at com.ibm.db2.jcc.a.lg.a(lg.java:1874)
	  [sqlproc]     at com.ibm.db2.jcc.a.lg.e(lg.java:740)
	  [sqlproc]     at com.ibm.db2.jcc.a.lg.execute(lg.java:724)
	  [sqlproc]     at com.ibm.wps.config.SqlProcessor.process(SqlProcessor.java:591)
	  [sqlproc]     at com.ibm.wps.config.SqlProcessor.process(SqlProcessor.java:146)
	  [sqlproc]     at com.ibm.wps.config.SqlProcessorTask.executeSqlScript(SqlProcessorTask.java:735)
	  [sqlproc]     at com.ibm.wps.config.SqlProcessorTask.execute(SqlProcessorTask.java:296)
	  [sqlproc]     at org.apache.tools.ant.Task.perform(Task.java:341)
	  [sqlproc]     at org.apache.tools.ant.Target.execute(Target.java:309)
	  [sqlproc]     at org.apache.tools.ant.Target.performTasks(Target.java:336)
	  [sqlproc]     at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
	  [sqlproc]     at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:397)
	  [sqlproc]     at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:143)
	  [sqlproc]     at org.apache.tools.ant.Task.perform(Task.java:341)
	  [sqlproc]     at org.apache.tools.ant.Target.execute(Target.java:309)
	  [sqlproc]     at org.apache.tools.ant.Target.performTasks(Target.java:336)
	  [sqlproc]     at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
	  [sqlproc]     at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:397)
	  [sqlproc]     at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:143)
	  [sqlproc]     at org.apache.tools.ant.Task.perform(Task.java:341)
	  [sqlproc]     at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:117)
	  [sqlproc]     at com.ibm.wps.config.If.execute(If.java:75)
	  [sqlproc]     at org.apache.tools.ant.Task.perform(Task.java:341)
	  [sqlproc]     at org.apache.tools.ant.Target.execute(Target.java:309)
	  [sqlproc]     at org.apache.tools.ant.Target.performTasks(Target.java:336)
	  [sqlproc]     at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
        ...............
	BUILD FAILED
	file:../config/includes/syncdb_cfg.xml:135: ERROR: Error during the execution of the sql files.

 

Solution: The solution is to create the SYNC and DESIGNER tablespaces on your DB2 server as follows:

db2 -v connect to <designer.DbName> user <designer.DbUser> using <designer.DbPassword>
db2 -v "create regular tablespace DSGNRTBS pagesize 8k managed by system using ('DSGNRTBS') extentsize 32 prefetchsize 32 bufferpool IBMDEFAULTBP"
db2 -v connect to <sync.DbName> user <sync.DbUser> using <sync.DbPassword>
db2 -v "create regular tablespace SYNCREGTBS pagesize 8k managed by system using ('SYNCREGTBS') extentsize 32 prefetchsize 32 bufferpool IBMDEFAULTBP"
</sync.DbPassword></sync.DbUser></sync.DbName></designer.DbPassword></designer.DbUser></designer.DbName>

 

Error received when transferring data to an Oracle database using the Turkish locale

 

Problem: when running database transfer to Oracle when using the Turkish locale, an error is received that there is an invalid username and password.

 

Solution: In the file wpconfig_dbdomain.properties, specify the value of the user name in uppercase.

 

Parent topic:

Search the product documentation for a solution

---