MSCPDC MSCPDCW PLANNING ODS LOAD ERRORS WITH TIMEOUT ERROR - POOR PERFORMANCE

(Doc ID 417633.1)

Last updated on JUNE 28, 2017

Applies to:

Oracle Advanced Supply Chain Planning - Version 11.5.10 and later
Information in this document applies to any platform.
***Checked for relevance on 18-Jun-2014***

EXECUTABLE:MSCPDC - Planning ODS Load
EXECUTABLE:MSCPDCW - Planning ODS Load Worker


Symptoms

On 11.5.10 in a Cloned Test Instance:
Users are testing out the Daylight Savings Patches per note 403311.1 and 397281.1. In order to
test these patches they cloned the decentalized Production Source instance and made it into a centralized architecture so they could perform data collections and testing all in one instance. This has the net effect of a new install since the MSC_* tables are completely emptied. Therefore data collections must
repopulate all of the data in the MSC_* tables. The users successfully collected data for 20 organizations. They then added 300 more and ran data collections. However data collections errored in the MSCPDC - Planning ODS Load with the following after 6 hours:

**Starts**01-MAR-2007 11:54:41
**Ends**01-MAR-2007 18:54:54
Timeout error.

The sql statement being executed at the time is the following (truncated most of it to save space):

INSERT INTO msc_item_suppliers
(using_organization_id, supplier_id, supplier_site_id,
inventory_item_id, processing_lead_time, minimum_order_quantity,
fixed_lot_multiplier, delivery_calendar_code,
supplier_cap_over_util_cost, purchasing_unit_of_measure,
sr_instance_id2, item_price, sr_instance_id, supplier_item_name,
planner_code, vmi_flag, min_minmax_quantity, max_minmax_quantity,
maximum_order_quantity, uom_code, vmi_replenishment_approval,
enable_vmi_auto_replenish_flag, replenishment_method,
min_minmax_days, max_minmax_days, forecast_horizon,
fixed_order_quantity, vmi_refresh_flag, plan_id, organization_id,
refresh_number, last_update_date, last_updated_by, creation_date,
created_by)
SELECT a.using_organization_id, a.supplier_id, a.supplier_site_id,
a.inventory_item_id, a.processing_lead_time,

ERROR
Timeout error

STEPS
The issue can be reproduced at will with the following steps:
1. Clone source instance and make it into a centralized architecture
2. Add 300 organizations
3. Run a complete refresh of data collections

Changes

Applied Daylight Savings Patches per note 403311.1 and 397281.1

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