MSCPLD Loader Worker With Direct Load Option Errors With RAC Scenario (Doc ID 1475156.1)

Last updated on MAY 01, 2017

Applies to:

Oracle Advanced Supply Chain Planning - Version 12.0 and later
Information in this document applies to any platform.

Symptoms

 1. Users have a new instance setup with RAC and they're running an ASCP plan for the first time. However it fails in MSCPLD module: Loader Worker With Direct Load Option

Username:SQL*Loader-500: Unable to open file (/prd/uat/inst/apps/uat_renebus1/logs/appl/conc/out/data1/mbpoutput/MSLD_ITEMS.ctl)
SQL*Loader-553: file not found
SQL*Loader-509: System error: No such file or directory

SQL*Loader: Release 10.1.0.5.0 - Production on Fri Jul 6 14:12:29 2012

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Program exited with status 1

SQL*Loader: Release 10.1.0.5.0 - Production on Fri Jul 6 14:12:29 2012

Copyright (c) 1982, 2005, Oracle. All rights reserved.

SQL*Loader-500: Unable to open file (/prd/uat/inst/apps/uat_renebus1/logs/appl/conc/out/data1/mbpoutput/MSLD_ITEMS.ctl)
SQL*Loader-553: file not found
SQL*Loader-509: System error: No such file or directory

APP-FND-01388: Cannot read value for profile option RPM_CONC_PROCESS_ID in routine &ROUT (This last error itself can be ignored)


2. When running the same ASCP plan again with profile MRP:Use Direct Load Option from No to Yes and the log file failed with different error:

MSCPLD module: Loader Worker With Direct Load Option

Parent Program Name: MSCMON
This IS part of a Plan run.
MSCSLD : unable open control file : 505 : /prd/uat/inst/apps/uat_renebus1/logs/appl/conc/out/data1/mbpoutput/MSLD_ITEMS.ctl
MSCSLD : Error in main 101 : /prd/uat/inst/apps/uat_renebus1/logs/appl/conc/out/data1/mbpoutput/MSLD_ITEMS.ctl /prd/uat/inst/apps/uat_renebus1/logs/appl/conc/out/data1/mbpoutput/MSLD_ITEMS.ctl.x
APP-FND-01630: Cannot open file /prd/uat/inst/apps/uat_renebus2/appltmp/OFAAAdoaO6L.t for reading

Cause: USDINS encountered an error when attempting to open file /prd/uat/inst/apps/uat_renebus2/appltmp/OFAAAdoaO6L.t for reading.

Action: Verify that the filename is correct and that the environment variables controlling that filename are correct.

Action: If the file is opened in read mode, check that the file exists. Check that you have privileges to read the file in the file directory. Contact your system administrator to obtain read privileges.

Action: If the file is opened in write or append mode, check that you have privileges to create and write files in the file directory. Contact your system administrator to obtain create and write privileges.

 
Steps:

1. Launch Plan.

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