Monday, December 29, 2014

EBS 12.2 -- Create Accounting error ORA-14411

Concurrent Programs like Create accounting may encounter ORA-14411: The DDL cannot be run concurrently with other DDLs errors.
Like the following Journal Import;
General Ledger: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
GLLEZL module: Journal Import
+---------------------------------------------------------------------------+
>> gluddl() 26-DEC-2014 20:45:58
-- gluddl ad.do_ddl error buffer begin
do_ddl(APPLSYS, SQLGL, 17, $statement$, GL_INTERFACE): private_do_ddl(APPS, APPLSYS, GL, 17, $statement$, GL_INTERFACE): do_at_tab_a_seq_acd_ind(GL, $statement$): : do_apps_ddl(GL, $statement$): : substr($statement$,1,255)='Alter table GL_INTERFACE add (code_combination_id_interim NUMBER(15))'
-- gluddl ad.do_ddl error buffer end
-- gluddl Message Dictionary Start:
do_ddl(APPLSYS, SQLGL, 17, $statement$, GL_INTERFACE): private_do_ddl(APPS, APPLSYS, GL, 17, $statement$, GL_INTERFACE): do_at_tab_a_seq_acd_ind(GL, $statement$): : do_apps_ddl(GL, $statement$): : substr($statement$,1,255)='Alter table GL_INTERFACE add (code_combination_id_interim NUMBER(15))'
APP-FND-01388: Cannot read value for profile option GL_GLLEZL_ARCHIVE_ROWS in routine &ROUTINE.
APP-FND-01388: Cannot read value for profile option GL_RECORDS_TO_PROCESS in routine &ROUTINE.
APP-FND-01388: Cannot read value for profile option GL_JI_ALWAYS_GROUP_BY_DATE in routine &ROUTINE.
APP-FND-01388: Cannot read value for profile option GL_DEBUG_MODE in routine &ROUTINE.
 
-- gluddl Message Dictionary End
<x gluddl() 26-DEC-2014 20:45:58
ORA-14411: The DDL cannot be run concurrently with other DDLs
ORA-0651
<x gllcnt() 26-DEC-2014 20:45:58

Error in: gllcnt
Function return status: 0
Function Err Message: gluddl failed
....
These concurrent programs do ddl operations using their routines like gluddl , do_ddl, do_apps_ddl and etc.. Normally, these ddl operations are database ddl operations, in other words , these operations are done in the database . Thus they are dependet to the rules of the underlying database.. (For EBS this database is Oracle ,as known)

So , the ORA-14411 error arises when multiple sessions try to do the ddl on the same table..
In such situation, you need to connect to the database, and look for the active sessions to find the session that does the ddl on relevant tables, thus preventing your concurrent programs to do their jobs..
Once you find out the problematic session, we identify its source and take the corrective actions..
I m saying "we need to identify its source" , because we don't usually do ddls on this kind of Standart tables!
What I m trying to say is; the session that does the ddl on the standart table and blocks the ddls against that standart table may belong to anohter Create Accounting  process which left behind or forgotten.. Maybe the problem is running the same process again and again concurrently..  So , If you Identify such a session, contact your Functional Team, there may be someting functionally broke.
Lastly, once the cause of issue is found, just kill the session or  cancel the concurrent request which the blocker session belongs.

No comments :

Post a Comment