ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience. Fail to import a cem db config from postgre to Oracle


Article ID: 107134


Updated On:


CA Application Performance Management Agent (APM / Wily / Introscope) INTROSCOPE


Next error message is received after run ./

7/18/18 08:10:54.768 PM COT [ERROR] [main] [root] [ConfigImport] - [email protected] 
java.sql.BatchUpdateException: ORA-12899: value too large for column "CEMDB"."TS_PARAMS"."TS_PATTERN" (actual: 1019, maximum: 1016) 

at oracle.jdbc.driver.OraclePreparedStatement.executeBatch( 
at oracle.jdbc.driver.OracleStatementWrapper.executeBatch( 
at com.wily.apm.dbtools.importexport.ConfigImport$SaxHandler.startElement( 
at Source) 
at Source) 
at Source) 
at$ Source) 
at Source) 
at Source) 
at Source) 
at Source) 
at Source) 
at Source) 
at$JAXPSAXParser.parse(Unknown Source) 
at Source) 
at javax.xml.parsers.SAXParser.parse(Unknown Source) 
at com.wily.apm.dbtools.importexport.ConfigImport.importConfig( 
at com.wily.apm.dbtools.importexport.ConfigImport.main( 
7/18/18 08:10:54.774 PM COT [ERROR] [main] [root] [ConfigImport] - Error parsing export file at line: 47466. Cause: SQL insert error: ORA-12899: value too large for column "CEMDB"."TS_PARAMS"."TS_PATTERN" (actual: 1019, maximum: 1016) 


The problem occurs because the origin column size is larger than the target column size.


APM versions: from to 
DB versions: from postgreSQL 9.2 to Oracle 12.1 
MOM: migrate from MOM in Windows 2008 R2 to MOM in Linux RedHat 7.x


The require an empty schema, so the only option here is to modify the SQL script createtables-oracle- modifying the size of the field from 1016 to 2048.
This will increase the size of the column to acommodate the content to import.

Additional Information

Link to product documentation