Tuesday, December 21, 2010

PATCH 9239090

Adworker fails with below error

ATTENTION: All workers either have failed or are waiting:

FAILED: file bomprg.ldt on worker 2.

FAILED: file jg12acp.ldt on worker 3.

Dumping LCT file /db2/oracle/EBS/DEV1/apps/apps_st/appl/fnd/12.0.0/patch/115/import/afcpprog.lct(120.2.12010000.2) into FND_SEED_STAGE_CONFIG

Dumping LDT file /db2/oracle/EBS/DEV1/apps/apps_st/appl/bom/12.0.0/patch/115/import/US/bomprg.ldt into FND_SEED_STAGE_ENTITY

A database error occurred:

ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column

Solution: Set the env and run the program manually or

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)


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.


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



$ ps -a
grep adworker


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:




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)

No comments: