Cannot Run Planning Data Collection - Purge Staging Tables For Legacy Instance When ODS Load is Terminated Or Fails (Doc ID 2067366.1)

Last updated on APRIL 02, 2022

Applies to:

Symptoms

12.2.4.1

Using Legacy collections
Customer terminated ODS Load
-- this left msc_apps_instances.st_status = 3

Then when they tried to run
MSCPLID: Purge Legacy Data
And also tried to run
MSCPST: Purge Interface Tables

They get error and find in the log file

MSCPST: Purge Interface Tables

**Starts**01-OCT-2015 10:29:20
**Ends**01-OCT-2015 10:29:21
Either another Planning ODS Load process is running for this instance or an earlier ODS Load may have been terminated abnormally.If it is the latter case, you need to launch the 'Planning Data Collection - Purge Staging Table' program before launching the Planning Data Collections again.

MSCPLID: Purge Legacy Data

**Starts**30-SEP-2015 15:41:06
**Ends**30-SEP-2015 15:41:06
Either another Planning ODS Load process is running for this instance or an earlier ODS Load may have been terminated abnormally.If it is the latter case, you need to launch the 'Planning Data Collection - Purge Staging Table' program before launching the Planning Data Collections again.

SO THEN -- you try to run Planning Data Collection - Purge Staging Table and cannot choose the Legacy instance since this program uses value set - MSC_SRS_INSTANCE_CODE

SEARCH finds that in bug 2086291
We addressed similar concern by creating new value set - MSC_SRS_INSTANCE_CODE_ODS

Planning Data Collections - Purge Staging Tables should use value set
MSC_SRS_INSTANCE_CODE_ODS
and NOT use MSC_SRS_INSTANCE_CODE
This will allow us to choose the Legacy instance code and purge the staging tables and also reset msc_apps_instances.st_status = 0

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.