Optim loader job behaves very weird. Optim loader job used to load multiple tables in conventional oracle method. Before load, truncate data and disable constraints & triggers. Optim loader job fails with error as "Loader ended with ExitCode 1" with different table at different time in LINUX

Note:

• There is no issue, if we use same extract file and run through windows Optim server. We are getting issue only when run through the LINUX server.

• Optim generates loader script during runtime. So we are able run the same loader script manually but getting error while trigger loader job in Optim.

Optim 11.3.0.7 (32bit) and Oracle 12.1 32bit client installed on Linux server.

When we run in Linux, below error in optim report:

Load Process Errors

   Loader ended with ExitCode 1, for table A

   Loader ended with ExitCode 1, for table B

When check for specific tables, it says "SQL*Loader-101: Invalid argument for username/password"

Optim loader job behaves very weird. Optim loader job used to load multiple tables in conventional oracle method. Before load, truncate data and disable constraints & triggers. Optim loader job fails with error as "Loader ended with ExitCode 1" with different table at different time in LINUX

Note:

• There is no issue, if we use same extract file and run through windows Optim server. We are getting issue only when run through the LINUX server.

• Optim generates loader script during runtime. So we are able run the same loader script manually but getting error while trigger loader job in Optim.

Optim 11.3.0.7 (32bit) and Oracle 12.1 32bit client installed on Linux server.

When we run in Linux, below error in optim report:

Load Process Errors

   Loader ended with ExitCode 1, for table A

   Loader ended with ExitCode 1, for table B

When check for specific tables, it says "SQL*Loader-101: Invalid argument for username/password"

Optim loader job behaves very weird. Optim loader job used to load multiple tables in conventional oracle method. Before load, truncate data and disable constraints & triggers. Optim loader job fails with error as "Loader ended with ExitCode 1" with different table at different time in LINUX

Note:

• There is no issue, if we use same extract file and run through windows Optim server. We are getting issue only when run through the LINUX server.

• Optim generates loader script during runtime. So we are able run the same loader script manually but getting error while trigger loader job in Optim.

Optim 11.3.0.7 (32bit) and Oracle 12.1 32bit client installed on Linux server.

When we run in Linux, below error in optim report:

Load Process Errors

   Loader ended with ExitCode 1, for table A

   Loader ended with ExitCode 1, for table B

When check for specific tables, it says "SQL*Loader-101: Invalid argument for username/password"