Analytical Engine Failed Immediately With ORA-20002: ORA-00054: resource busy and acquire with NOWAIT specified (Doc ID 1059204.1)

Last updated on JUNE 28, 2017

Applies to:

Oracle Demantra Demand Management - Version 7.2 to 7.2 [Release 7.2]
Information in this document applies to any platform.
***Checked for relevance on 02-June-2013***


Symptoms


On Version 7.2 in Test:

User ran REBUILD_INDEXES then experienced this problem when running the Analytical Engine.

The following was seen in the Engine log screen:

4:07:26:650 [EngLogger.cpp,187] Logger General Level: info, UserLevel: message
14:07:26:650 Working with Oracle RDBMS
14:07:26:650 Database connection string: Provider=MSDAORA;Data Source=DEV User: MSDEM
14:07:26:916 --------------------------------------------------------------
14:07:26:916 Oracle Demantra Forecast Engine Version 7.2.0  (290)
14:07:26:916 Engine Start Time 14:07:26
14:07:26:916 Running in Batch mode
14:07:26:916 --------------------------------------------------------------
14:07:27:666 Text Pro creating global causal factor Sqls...
14:07:27:728 Text Pro creating Aggri Sqls...
14:07:27:947 Text Pro creating Psum Sqls...
14:07:28:119 Text Pro finished executing.
14:07:28:306 ERROR ---------------------------------------------------------------
14:07:28:306 ERROR   DB_Command::Execute threw an exception:
14:07:28:306 ERROR   { call CHECK_FORE_SERIES }
14:07:28:306 ERROR   - ErrorDescription: ORA-20002: ORA-00054: resource busy and acquire with NOWAIT specified
    Error in PROCEDURE DROP_FORE_COL line 82

       dynamic_ddl( 'ALTER TABLE SALES_DATA DROP COLUMN FORE_9')
ORA-06512: at "MSDEM.SEND_ERR_MESSAGE", line 21
ORA-06512: at "MSDEM.DYNAMIC_DDL", line 22
ORA-06512: at "MSDEM.DROP_FORE_COL", line 82
ORA-06512: at "MSDEM.CHECK_FORE_SERIES", line 217
ORA-06512: at line 1

14:07:28:306 ERROR   - ErrorNumber: 0x80004005 - Unspecified error


14:07:28:306 ERROR   - NativeErrorNumber: 20002
14:07:41:805 CHECK_FORE_SERIES failed

The User then bounced the server and re-ran the Engine.
This time the Engine hung and never completed.

The User discovered the following when running rebuild_indexes again:

"Some indexes or index [sub]partitions of table MSDEM.XXXX_XXXXX have been marked unusable
Thu Feb 4 11:06:46 2010"

This is seen multiple times with each line referencing a different index.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms