Applications running in WebSphere Application Server get error "COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1034C The database is damaged."
 Technote (troubleshooting)
 
Problem(Abstract)
After upgrading from DB2® V7.2 Fix Pack 9 to DB2 V8.1 Fix Pack 5, WebSphere® Application Server V4 Administrative Server fails to start and applications running in WebSphere Application Server V5.x fail with the following error:

COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1034C The database is damaged. All applications processing the database have been stopped. SQLSTATE=58031 when using DB2 JDBC™ V8.1 Fix Pack 6 (or prior)
 
Cause
IY51860: DATABASE MARKED BAD IF LC_CTYPE IS SET TO AN UNSUPPORTED LOCALE
 
Resolving the problem
Recommended Solution:

Upgrade to DB2 V8.1 Fix Pack 7a, or latest (Check DB2 Universal Database for Linux®, UNIX® and Windows® for the latest Fix Pack available with DB2 V8.1)

Workaround Solution:
Change or set LC_CTYPE and LC_ALL environment variables on the Solaris DB2 client to the following:

  • LC_CTYPE=iso_8859_1
  • LC_ALL=en_US
WebSphere Application Server must be restarted after making the above changes. The changes must be applied to the user's environment that start WebSphere Application Server and Node Agent (for WebSphere Server Application V5 and above).
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > DB Connections/Connection Pooling
Operating system(s): AIX
Software version: 6.0
Software edition:
Reference #: 1210886
IBM Group: Software Group
Modified date: Dec 9, 2005