Portal startup failure due to table space or index space in check pending status

Technote (troubleshooting)


Problem

The IBM® WebSphere® Portal startup is failing with the following exception :


DYNA1001I: WebSphere Dynamic Cache instance named ws/wps.mappingurl.LookupCache initialized successfully.
[11/27/07 12:40:26:241 PST] 00000015 DataStoreCont E com.ibm.wps.datastore.impl.DataStoreContext handleException EJPDB0001E: Error occurred during database access. Last SQL statement is [SELECT OID, CREATED, MODIFIED, LABEL, PARENT_OID, RESOURCE_TYPE, RESOURCE_OID FROM DBT4REL.URL_MAP_CTX WHERE (PARENT_OID IS NULL)].
com.ibm.wps.util.DataBackendException: EJPDB0001E: Error occurred during database access. Last SQL statement is [SELECT OID, CREATED, MODIFIED, LABEL, PARENT_OID, RESOURCE_TYPE, RESOURCE_OID FROM DBT4REL.URL_MAP_CTX WHERE (PARENT_OID IS NULL)].

...

Caused by: com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -904, SQLSTATE: 57011, SQLERRMC: 00C900A3;00000200;TABLESPACENAME .TS830A
at com.ibm.db2.jcc.b.lf.b(lf.java:3267)

Symptom

Portal server fails to start with the SQL error codes mentioned despite having successfully completed a database transfer.


Cause

The SQL errors indicate an attempt was made to allocate a table space, index space, or a related index space while the table space or index space was in check pending status. Furthermore, the check pending status needs to be resolved before the operation will be allowed.

Environment

DB2® for zOS®

Resolving the problem

Essentially, it is up to the database administrator to run a job that will clear out the check pending status. They should be aware of the following utilities that should help resolve this issue on the database:


-- If the object is a table space with referential relationships, then run the CHECK DATA utility to check for referential integrity violations.

-- If the object is a base table space with LOB columns, then run the CHECK DATA utility to validate the auxiliary columns.

-- If the object is a LOB table space, then run the CHECK LOB utility to validate the structure of the LOB table space.

-- If the object is an index space, then run the CHECK INDEX utility to verify that the index keys are consistent with the data in the table space or table space partition.


Related information

SQLCODE: -904 and SQLSTATE: 57011


Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere Portal
Database Connectivity

Software version:

6.0, 6.1, 7.0

Operating system(s):

AIX, HP-UX, Linux, Solaris, Windows, z/OS

Software edition:

Enable, Express, Extend, Server

Reference #:

1289649

Modified date:

2013-01-31

Translate my page

Machine Translation

Content navigation