My Oracle Support Banner

ODI Jobs Fail with 128 and 143 System Error Codes (Doc ID 787447.1)

Last updated on DECEMBER 23, 2019

Applies to:

Oracle Data Integrator - Version 3.2.03.01 and later
Information in this document applies to any platform.
This problem can occur on any platform.

Symptoms

A Perl script that invokes the Teradata Bteq tool and executes Oracle Data Integrator (ODI) Scenarios with the startscen.bat script, randomly stops with 128 or 143 System errors.

The failure occurs when the Perl script (parent) attempts to communicate with the Java process (child) that executes the ODI Scenario, as if it has lost the "pointer" to that child.

Note that 128 and 143 System error codes are not ODI specific.

According to:

https://msdn.microsoft.com/en-us/library/ms681382(VS.85).aspx

... 128 (ERROR_WAIT_NO_CHILDREN) states for "There are no child processes to wait for" and
... 143 (ERROR_SAME_DRIVE) states for "The system cannot join or substitute a drive to or for a directory on the same drive".

Note: Oracle is not responsible for any instructions/information/drivers obtained from 3rd party site.

Cause

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
Symptoms
Cause
Solution


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