![]() The plan crossed the Loader worker stage but failed during Memory Based Planner MSONWS64: So this time, I removed APS64_ORA_NLS33 and set ORA_NLS33, which is how it runs in Production: The SQL statement being executed at the time of the error was: and was executed from the file. However it failed during Loader Worker with this error:ĪPP-MRP-22130: Cannot connect to databaseĬause: The current routine cannot connect to the database.Īction: Contact your system administrator or customer support representative.Ĭoncurrent program returned no reason for failure.Ĭause: FDPCLS failed due to ORA-01012: not logged on The ASCP Plan crossed the stage where MSCNPS64 is called. So I removed ORA_NLS33 and bounced the Concurrent Manager with only these set: However Oracle recommends that only APS64_ORACLE_HOME and APS64_ORA_NLS33 needs to be set. ![]() ![]() Memory Based Snapshot 64 bit Sun –program errors out in apps11i.īased on previous experience, I checked the values of these environment variables: Maran reported this error in ASCP after a fresh clone: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |