Symptom
- Profiling task issue.
- The Profiling task will run for days and never finish successfully.
- Profiling a wide table.
- Profiling a table with hundreds of columns, but not a lot of rows.
- Selecting all columns to profile at once.
- Only get errors when doing all column profiles (simple, median & distribution, word distribution) at once.
- If just doing simple, the profiling seems to complete.
- If it just keeps running, there may be no errors in the logs.
- Potential error: "Error accessing repository objects: java.sql.SQLException: Information Steward repository connections are shutting down. (COR-10367) (TSK-10061)"
- Potential error(s): "com.bobj.mm.sdk.SDKException: java.sql.SQLException: Information Steward repository connections are shutting down. (COR-10367)
at com.bobj.mm.sdk.DBObject.find(DBObject.java:2945)
at com.bobj.mm.sdk.DBObject.findByPrimaryKeyCreateOrUpdate(DBObject.java:876)
at com.sap.icc.task.EnterpriseProfileRecord.closeRun(EnterpriseProfileRecord.java:111)
at com.sap.icc.task.SubtaskQueue.close(SubtaskQueue.java:104)
at com.sap.icc.task.TaskUtility.executeTasks(TaskUtility.java:253)
at com.sap.icc.task.TaskUtility.execute(TaskUtility.java:215)
at com.bobj.mm.utility.Utility.runExecute(Utility.java:454)
at com.bobj.mm.core.Main.run(Main.java:1301)
at com.bobj.mm.core.Main.main(Main.java:241)
Caused by: java.sql.SQLException: Information Steward repository connections are shutting down. (COR-10367)
at com.bobj.mm.core.sqlimpl.MMConnectionPool.getConnection(MMConnectionPool.java:177)
at com.bobj.mm.core.sqlimpl.MMConnectionHolder.<init>(MMConnectionHolder.java:46)
at com.bobj.mm.core.sqlimpl.SQLProcessorManager.createConnectionHolder(SQLProcessorManager.java:209)
at com.bobj.mm.core.MMTransaction.getConnectionHolder(MMTransaction.java:365)
at com.bobj.mm.core.sqlimpl.SQLProcessor.init(SQLProcessor.java:83)
at com.bobj.mm.core.sqlimpl.SQLProcessorManager.getProcessor(SQLProcessorManager.java:337)
at com.bobj.mm.core.sqlimpl.SQLProcessorManager.getSqlProcessor(SQLProcessorManager.java:238)
at com.bobj.mm.core.MMWarehouse.getSqlProcessor(MMWarehouse.java:1368)
at com.bobj.mm.sdk.DBObject.selectByPrimaryKey(DBObject.java:3069)
at com.bobj.mm.sdk.DBObject.find(DBObject.java:2896)
... 8 more[E] 2013-12-12 18:10:33.234 Utility failed with code -1,005. (COR-10020)
[I] 2013-12-12 18:10:33.234 Completed execution on 2013-12-12 18:10:33. (COR-10015)
[I] 2013-12-12 18:10:33.234 Elapsed time is 2:00:00.128 [hrs:min:sec]. (COR-10081)
[E] 2013-12-12 18:10:33.234 Could not initialize Information Steward Core. (COR-10095)" - Potential errors: "Unable to reconnect to the CMS qambn038:6400. The session has been logged off or has expired. (FWM 01002)
[E] 2013-12-12 18:10:33.218 com.crystaldecisions.enterprise.ocaframework.IManagedService$ManagedLogoffException: Unable to reconnect to the CMS qambn038:6400. The session has been logged off or has expired. (FWM 01002)
at com.crystaldecisions.enterprise.ocaframework.ManagedService.invoke(ManagedService.java:315)
at com.crystaldecisions.sdk.occa.infostore.internal._InfoStoreEx4Proxy.queryEx3(_InfoStoreEx4Proxy.java:364)
at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore$XRL3WireStrategy.query(InternalInfoStore.java:1539)
at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore.queryHelper(InternalInfoStore.java:939)
at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore.queryHelper(InternalInfoStore.java:927)
at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore.query_aroundBody18(InternalInfoStore.java:796)
at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore.query(InternalInfoStore.java:1)
at com.crystaldecisions.sdk.occa.infostore.internal.InfoStore.query_aroundBody8(InfoStore.java:175)
at com.crystaldecisions.sdk.occa.infostore.internal.InfoStore.query_aroundBody9$advice(InfoStore.java:512)
at com.crystaldecisions.sdk.occa.infostore.internal.InfoStore.query(InfoStore.java:1)
at com.bobj.mm.boe.CMSManager.getObjectById(CMSManager.java:2195)
at com.bobj.mm.boe.CMSManager.getAppObjectById(CMSManager.java:836)
at com.sap.icc.task.TaskStatistic.updateJobStatistic(TaskStatistic.java:184)
at com.sap.icc.task.DataServiceDispatcherTaskStrategy$TaskMonitor.run(DataServiceDispatcherTaskStrategy.java:356)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:743)"
Read more...
Environment
SAP Information Steward
Product
SAP Information Steward 4.2
Keywords
IS, DI, COR 10367, TSK 10061, com.bobj.mm.sdk.SDKException, java.sql.SQLException , KBA , EIM-IS-DI , Information Steward - Data Insight , EIM-IS , Information Steward , Bug Filed
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.