ATTENTION: All workers either have failed or are waiting:
FAILED: file payzzcncprg01138.ldt on worker 1.
FAILED: file bomprg.ldt on worker 6.
ATTENTION: Please fix the above failed worker(s) so the manager can continue.
Error Logs from US_bomprg_ldt.log and loc_jp_payzzcncprg01138_ldt.log.
worker 1:-
Loading data using FNDLOAD function.
FNDLOAD APPS/***** 0 Y UPLOAD @FND:patch/115/import/afcpprog.lct @PAY:patch/115/import/US/loc_jp/payzzcncprg01138.ldt -
Connecting to APPS......Connected successfully.
Calling FNDLOAD function.
Returned from FNDLOAD function.
Log file: /data05/EBS_FS_12.2.5/fs1/EBSapps/appl/admin/PHASE1/log/loc_jp_payzzcncprg01138_ldt.log
Error calling FNDLOAD function.
--------------
A database error occurred:
ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column
==========
worker 6:-
Loading data using FNDLOAD function.
FNDLOAD APPS/***** 0 Y UPLOAD @FND:patch/115/import/afcpprog.lct @BOM:patch/115/import/US/bomprg.ldt -
Connecting to APPS......Connected successfully.
Calling FNDLOAD function.
Returned from FNDLOAD function.
Log file: /data05/EBS_FS_12.2.5/fs1/EBSapps/appl/admin/PHASE1/log/US_bomprg_ldt.log
Error calling FNDLOAD function.
The value for environment variable NLS_LANG is different than the database characterset (NLS_CHARACTERSET) when invoking FNDLOAD.
Please use the following command to verify the cause:
Environment setup:
#echo $NLS_LANG (Unix)
>echo %NLS_LANG% (Windows)
Database characterset:
Using sqlplus client query:
SQL> SELECT VALUE FROM V$NLS_PARAMETERS WHERE PARAMETER = 'NLS_CHARACTERSET';
To implement the solution, please execute the following steps:
If the Patch is stopped please just change setup for environment variable NLS_LANG to proper value and restart adpatch (continue previous session).
For example:
If the database characterset is UTF8 set NLS_LANG to American_America.UTF8.
a. Execute 'export' as follows.
# export NLS_LANG=American_America.UTF8
b. Query value for NLS_LANG to verify it.
#echo $NLS_LANG (Unix)
>echo %NLS_LANG% (Windows)
OR
If adpatch is still running but hanging due to failed workers:
1. Stop adpatch.
Please use adctrl utility to stop adpatch.
The best way to do this is to shut down the workers manually, which
also causes the AD utility to quit in an orderly fashion.
Action:-
a. Select AD Controller(adctrl) Option 3 and enter all for the worker number. Each worker
stops once it completes or fails its current job.
b. Verify that no worker processes are running. Use a command similar to the one
in the following example. The command arguments may vary on different
platforms.
UNIX:
$ ps -a | grep adworker
Windows:
Invoke the Task Manager (Ctrl-Alt-Delete) to view processes.
c. When all workers have shut down, the manager and the AD utility quits.
2. Change NLS_LANG setup.
Please refer to the example above.
3. Start adpatch again, continue previous session.
Check if AutoPatch is progressing, if not use adctrl utility, option 2 to restart failing worker.
4. How to avoid similar issue in the future.
Verify NLS_LANG setup in the Autoconfig Context file.
Edit the context file using Oracle Applications Manager(OAM) or Context Editor and find value for NLS_LANG:
If the database characterset is UTF8 it should be:
<NLS_LANG oa_var="s_tools_nlslang">American_America.UTF8</NLS_LANG>
<NLS_LANG oa_var="s_weboh_nlslang">American_America.UTF8</NLS_LANG>
<NLS_LANG oa_var="s_nlslang">American_America.UTF8</NLS_LANG>
If NLS_LANG parameters have different values than expected please apply corrections. Then execute Autoconfig and make sure it was successful.
5. Test if the changes to NLS_LANG were successful.
Source the env file and query:
#echo $NLS_LANG (Unix)
>echo %NLS_LANG% (Windows)
If the Patch is stopped please just change setup for environment variable NLS_LANG to proper value and restart adpatch (continue previous session).
For example:
If the database characterset is UTF8 set NLS_LANG to American_America.UTF8.
a. Execute 'export' as follows.
# export NLS_LANG=American_America.UTF8
b. Query value for NLS_LANG to verify it.
#echo $NLS_LANG (Unix)
>echo %NLS_LANG% (Windows)
OR
If adpatch is still running but hanging due to failed workers:
1. Stop adpatch.
Please use adctrl utility to stop adpatch.
The best way to do this is to shut down the workers manually, which
also causes the AD utility to quit in an orderly fashion.
Action:-
a. Select AD Controller(adctrl) Option 3 and enter all for the worker number. Each worker
stops once it completes or fails its current job.
b. Verify that no worker processes are running. Use a command similar to the one
in the following example. The command arguments may vary on different
platforms.
UNIX:
$ ps -a | grep adworker
Windows:
Invoke the Task Manager (Ctrl-Alt-Delete) to view processes.
c. When all workers have shut down, the manager and the AD utility quits.
2. Change NLS_LANG setup.
Please refer to the example above.
3. Start adpatch again, continue previous session.
Check if AutoPatch is progressing, if not use adctrl utility, option 2 to restart failing worker.
4. How to avoid similar issue in the future.
Verify NLS_LANG setup in the Autoconfig Context file.
Edit the context file using Oracle Applications Manager(OAM) or Context Editor and find value for NLS_LANG:
If the database characterset is UTF8 it should be:
<NLS_LANG oa_var="s_tools_nlslang">American_America.UTF8</NLS_LANG>
<NLS_LANG oa_var="s_weboh_nlslang">American_America.UTF8</NLS_LANG>
<NLS_LANG oa_var="s_nlslang">American_America.UTF8</NLS_LANG>
If NLS_LANG parameters have different values than expected please apply corrections. Then execute Autoconfig and make sure it was successful.
5. Test if the changes to NLS_LANG were successful.
Source the env file and query:
#echo $NLS_LANG (Unix)
>echo %NLS_LANG% (Windows)
