MSCPLD:Loader Worker With Direct Load Option Fails SQL*Loader-2026: The Load Was Aborted Because SQL Loader cannot continue
(Doc ID 2494352.1)
Last updated on OCTOBER 19, 2019
Applies to:Oracle Advanced Supply Chain Planning - Version 126.96.36.199.2 and later
Information in this document applies to any platform.
On : 188.8.131.52.2 version, Memory Based Planner in Pre Production
Users are upgrading both source and destination to 184.108.40.206.2 code line. Users are on 12.1.3 and have applied VCP 220.127.116.11.2 aka R12.SCP_PF.B.Delta.4 - Patch 22706126 - Users are using 64 bit Linux MBP. They also have patch 29011993 which gave them MSONWL64.ppc 120.3.12010000.497 - They are running into an error in MSCPLD:Loader Worker With Direct Load Option
value used for ROWS parameter changed from 1000 to 53
SQL*Loader-510: Physical record in data file (/vcp/oracle/inst/apps/VCPDEV6_peluvcpdev6/logs/appl/conc/out/data24/mbpoutput/MSLD_RES_REQS.dat) is longer than the maximum(1048576)
SQL*Loader-2026: the load was aborted because SQL Loader cannot continue.
Specify SKIP=1640124 when continuing the load.
1640124 Rows successfully loaded.
0 Rows not loaded due to data errors.
0 Rows not loaded because all WHEN clauses were failed.
0 Rows not loaded because all fields were null.
The issue can be reproduced at will with the following steps:
1. Upgrade to 18.104.22.168.2 both source and destination
2. Run ASCP plan
3. Plan fails
Upgraded from 22.214.171.124.1 to 126.96.36.199.2 in both source and destination instances
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document