Problem Note 52292: Error "ORA-12899: value too large for Column "DI_DM"."PKO_SIZESET"."SIZESET_NM" (actual: 41, maximum: 40)" might be encountered
In SAS® Pack Optimization, the following exception might be generated when importing purchase order plans via an XML import file:
org.hibernate.QueryTimeoutException: Could not execute JDBC batch update
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:124)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
Caused by: java.sql.BatchUpdateException: ORA-12899: value too large for column "DI_DM"."PKO_SIZESET"."SIZESET_NM" (actual: 4X, maximum: 40)
at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:10070)
at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(OracleStatementWrapper.java:213)
at org.apache.commons.dbcp.DelegatingStatement.executeBatch(DelegatingStatement.java:297)
at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:70)
at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:268)
... 84 more
This exception is generated when the sizeset ID in the plan import XML is more than 40 character long.
The workaround for this issue is to limit the length of the sizeset ID to less than 40 characters.
Operating System and Release Information
| SAS System | SAS Pack Optimization | Linux for x64 | 3.2_M3 | 3.2_M4 | 9.3 TS1M2 | 9.3 TS1M2 |
| 64-bit Enabled AIX | 3.2_M3 | 3.2_M4 | 9.3 TS1M2 | 9.3 TS1M2 |
| Microsoft Windows Server 2008 | 3.2_M3 | 3.2_M4 | 9.3 TS1M2 | 9.3 TS1M2 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2018-02-28 13:23:14 |
| Date Created: | 2014-02-10 14:10:29 |
