ORA-01401: inserted value too large for column

Technote (FAQ)
Problem
You receive the error "ORA-01401: inserted value too large for column" when trying to create an Application Server or clone.
Solution
Error message from tracefile:

[02.06.18 13:05:59:042 EDT] 136497d DBMgr W Exception on database
update: "insert into ejsadmin.SESSION_MGR_TABLE values
(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)"
java.sql.SQLException: ORA-01401: inserted value too large for column
    at java.lang.Throwable.fillInStackTrace(Native Method)
    at java.lang.Throwable.fillInStackTrace(Compiled Code)
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Exception.<init>(Compiled Code)
    at java.sql.SQLException.<init>(Compiled Code)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(Compiled Code)
    at oracle.jdbc.ttc7.TTIoer.processError(Compiled Code)
    at oracle.jdbc.ttc7.Oall7.receive(Compiled Code)
    at oracle.jdbc.ttc7.TTC7Protocol.doOall7(Compiled Code)
    at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(Compiled Code)
    at oracle.jdbc.driver.OracleStatement.executeNonQuery(Compiled Code)
    at oracle.jdbc.driver.OracleStatement.doExecuteOther(Compiled Code)


Reason:
One of the Session Manager entries has a higher than expected value. Ensure that you follow the limits in the Administrative Console Session Manager. Highlight the Application Server or clone from which you are receiving the error. Next, navigate down to the objects shown below and locate the properties for those objects so you can check the following variables:

Session Manger object properties:

On the Cookies tab, check the following:

Cookie Name:VARCHAR(64)
Cookie Comment:VARCHAR(256)
Cookie Domain:VARCHAR(64)
Cookie Maximum Age:INTEGER NOT NULL (Default is "-1" )
Cookie Path:VARCHAR(256)

On the Persistence tab, check the following:

Datasource:VARCHAR(256)
Userid:" VARCHAR(64)
Password:VARCHAR(64)

On the Intervals tab, check the following:

Invalidate Time:INTEGER NOT NULL (Default is "1800")

The Session Manager uses a specific defined data source, which in turn uses a specific defined JDBC™ Driver. Errors can occur due to values set on these two objects.

In the Administrative Console, find the JDBC Driver that is used by the data source defined in the Session Manager; look at the properties for that object.

JDBC Driver object properties:

Name:VARCHAR(256) NOT NULL
Class Name:VARCHAR(64) NOT NULL
URL prefix:VARCHAR(64) NOT NULL

Next, still in the Administrative Console, locate the data source defined in the Session Manager; look at the properties for that object.

Data source object properties:

Data Source Name:VARCHAR(256) NOT NULL
Database Name:VARCHAR(256) NOT NULL
Minimum connection pool size:INTEGER NOT NULL
Maximum connection pool size:INTEGER NOT NULL
Connection timeout:INTEGER NOT NULL
Idle timeout:INTEGER NOT NULL
Orphan timeout:INTEGER NOT NULL

None of these values should be blank and the maximum length is the number in the parenthesis( ).











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, General
Operating system(s): Multi-Platform
Software version: 3.5
Software edition: Advanced
Reference #: 1054495
IBM Group: Software Group
Modified date: 2004-04-14