000028946 - KB-1278 - ORA-29913 during EDC collection

Document created by RSA Customer Support Employee on Jun 15, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000028946
Applies ToAffected Versions: All Versions
IssueORA-29913: error in executing ODCIEXTTABLEFETCH callout

ORA-30653: reject limit reached

Step 0: Main Entitlement Data Load Stored Procedure:Load_Res_User_Ent_Data execution aborted.(app=43edc=85,run=855,res_file=85585Resources.data,ent_file=85585EntitlementDefinitions.data,ent_grp_file=85585UserEntitlementBagDef.data,ent_grp_mem_data_file_name=85585UserEntitlementBag.data, userentfile=85585UserEntitlements.data, user_ent_const_file=85585EntitlementConstraints.data, user_ent_native_file=85585NativeData.data,user_ent_meta_data_file=85585UserEntitlementMetadata.data)

Stack:

ORA-06512: at "SYS.ORACLE_LOADER", line 52

ORA-06512: at "AVUSER.LOAD_ENTITLEMENT_DATA_PKG", line 2174

ORA-06512: at "AVUSER.LOAD_ENTITLEMENT_DATA_PKG", line 938

ORA-06512: at "AVUSER.LOAD_ENTITLEMENT_DATA_PKG", line 601

ORA-06512: at "AVUSER.ERROR_HANDLER_PKG", line 979

ORA-06512: at "AVUSER.LOAD_ENTITLEMENT_DATA_PKG", line 732

ORA-06512: at line 1



at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)


at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)

at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)

at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:215)

at oracle.jdbc.driver.T4CCallableStatement.executeForRows(T4CCallableStatement.java:954)

at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1168)

at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3285)

at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3390)

at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4223)

at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:168)

at com.aveksa.server.db.PersistenceManager.runStoredProcedure(PersistenceManager.java:1146)

at com.aveksa.server.xfw.DefaultEntitlementDataFilter.loadData(DefaultEntitlementDataFilter.java:575)

at com.aveksa.server.xfw.DefaultEntitlementDataFilter.process(DefaultEntitlementDataFilter.java:318)

at com.aveksa.server.xfw.DefaultEntitlementDataFilter.process(DefaultEntitlementDataFilter.java:192)

at com.aveksa.server.xfw.DataProcessor.process(DataProcessor.java:85)

at com.aveksa.server.xfw.DataProcessor.process(DataProcessor.java:64)

at com.aveksa.server.xfw.DataProcessingExecutor.executeTask(DataProcessingExecutor.java:124)

at com.aveksa.server.xfw.TaskExecutor.execute(TaskExecutor.java:86)

at com.aveksa.server.xfw.ExecutionTaskQueue$Worker.run(ExecutionTaskQueue.java:117)

at java.lang.Thread.run(Thread.java:595)
CauseThis Oracle error is typically seen if some incorrect data is collected (data type mismatch) and then attempted to be processed.
ResolutionCheck for .bad files, which would be located in /home/oracle/AveksaDataDir folder (check file time stamp to match that of collection). If this file exists, view the bad file and the corresponding .log file as well. This will give which data record and which data field are root causes of the underlying issue.
For example, .bad file looks like this: Collector_<Collector_Name>_ID_<Collector ID>_user.bad
 

Attachments

    Outcomes