Database must be started first before application server with session persistence.
 Technote (FAQ)
 
Problem
If a database is started later than the application server the session manager will throw a java.sql.SQLException.
 
Cause
Based on the current design of WebSphere® Application Server, databases configured for session persistence must be started before the Application Server. This is required because during startup the session manager will check for existence of session tables and create them as needed.


If the database is restarted when application server is running, the following exception will occur:

java.sql.SQLException: Invalid column index.
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:12)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:16)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:22)
at oracle.jdbc.driver.OraclePreparedStatement.setStringInternal(OraclePreparedStatement.java:4754)
...

 
Solution
Databases configured for session persistence must be started before the starting the Application Server.
 
 
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 > Sessions and Session Management
Operating system(s): Windows
Software version: 6.1
Software edition:
Reference #: 1257463
IBM Group: Software Group
Modified date: Mar 28, 2007