My Oracle Support Banner

OCM EBS Collections May Fail If ORA_NLS10 Parameter Is Set Incorrectly (Doc ID 785199.1)

Last updated on OCTOBER 30, 2019

Applies to:

Oracle Configuration Manager - Version and later
Information in this document applies to any platform.


There are two possible symptoms:

1) During the instrumentation of OCM within a database environment where EBS is running, the following error output will be logged in the EBS_CollectConfog.log as well as in the Alert.log of the Database:
ORA-12012: error on auto execute of job 512
ORA-20000: SQLERRM: ORA-29283: invalid file operation
ORA-06512: at "SYS.UTL_FILE", line 488
ORA-29283: invalid file operation SQLCODE: -29283
ORA-06512: at "APPS.MGMT_EBS_LL_METRICS", line 1533
ORA-06512: at line 1


SQL> execute MGMT_EBS_CONFIG.install_job;
PL/SQL procedure successfully completed.
SQL> execute MGMT_EBS_CONFIG.run_now;
ERROR at line 1:
ORA-12011: execution of 1 jobs failed
ORA-06512: at "SYS.DBMS_IJOB", line 406
ORA-06512: at "SYS.DBMS_JOB", line 272
ORA-06512: at "APPS.MGMT_EBS_CONFIG", line 90
ORA-06512: at line 1

2) The running of MGMT_EBS_LL_METRICS.COLLECT_CONFIG_METRICS.  In this case, a Core Dump may occur.  The core dumps are from lxcsu22m() which is doing some mapping of multibyte characters at the time.



Setting of the ORA_NLS10 environmental parameter during OCM EBS Configuration to a non- ${ORACLE_HOME}/nls/data directory location.


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

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