Quick fix for ORA 24816 Expanded Non Long Bind Data Supplied

Introduction:-

Ora 24816 expanded non long bind data supplied After Actual Long Or Lob Column| In this post we will fix ora 24816 while applying patch in ebs r12.

Ora 24816 expanded non long bind data supplied

Error:- 

Check error in log.

worker 1:- 

Solution:-

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)

Related/Useful posts:-

• Opatch apply| Cannot set up OUI inventory session. ERROR: OPatch failed because of Inventory problem
  
• How to fix in best way runInstaller checking operating system version failed 
• Steps to create physical standby database using rman backup 

ORA-24816: Expanded Non Long Bind Data Supplied