Planning ODS Load Worker For Legacy Collections Has False Error Message - Error: No org is assigned to instance [ID] ! Collection could be failed due to this error! (Doc ID 2827888.1)

Last updated on JUNE 01, 2023

Applies to:

Symptoms

12.2.6 and higher
with latest Cum Patch per note 1361221.1

PROBLEM
-------------
Legacy load
ODS Load and ODS loader worker log always displays message:
03-NOV 16:11:44 : Error: No org is assigned to instance 2061 ! Collection could be failed due to this error!
03-NOV 16:11:44 : GET_DEPOT_ORG_STR value of v_instance_id: 2061
03-NOV 16:11:44 : Error: No org is assigned to instance 2061 ! Collection could be failed due to this error!
03-NOV 16:11:44 : GET_DEPO_ORG_STR returned := -9999

There is not any failure and all completes successfully.

STEPS
--------
Load legacy data per sequence in <Note 1966629.1> - How To Load Legacy Data in ASCP?

NAV: ASCP responsibility / Data Collections / Legacy / Self Service
EntitySequence
1. Calendar
2. UOM
3. Trading Partners
-- for the above - message is misleading since we have not uploaded orgs yet -- All orgs were loaded successfully in trading partner load

-- for any other entities or data loaded later - the message persists

BUSINESS IMPACT
----------------------
The data loaded successfully - but this persistent false message is confusing to users

Cause

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