Errors in gluddl drop_object When Journal Import is Triggered from Consolidation Transfer (Doc ID 2051981.1)

Last updated on OCTOBER 20, 2015

Applies to:

Oracle General Ledger - Version 12.1.1 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.1 version, Journal Import

Error in Journal Import when kicked off from consolidation transfer

ERROR
-----------------------
-- gluddl ad.do_ddl error buffer begin
do_ddl(APPLSYS, SQLGL, 12, $statement$, GL_CONS_INTERFACE_276522): private_do_ddl(APPS, APPLSYS, GL, 12, $statement$, GL_CONS_INTERFACE_276522): do_cd_tab_cd_seq(0, APPS, GL, 12, GL_CONS_INTERFACE_276522, $statement$): : drop_object(GL,GL_CONS_INTERFACE_276522,TABLE): : substr($statement$,1,255)='Drop Table GL_CONS_INTERFACE_276522'
-- gluddl ad.do_ddl error buffer end
-- gluddl Message Dictionary Start:
do_ddl(APPLSYS, SQLGL, 12, $statement$, GL_CONS_INTERFACE_276522): private_do_ddl(APPS, APPLSYS, GL, 12, $statement$, GL_CONS_INTERFACE_276522): do_cd_tab_cd_seq(0, APPS, GL, 12, GL_CONS_INTERFACE_276522, $statement$): : drop_object(GL,GL_CONS_INTERFACE_276522,TABLE): : substr($statement$,1,255)='Drop Table GL_CONS_INTERFACE_276522'
APP-FND-01388: Cannot read value for profile option GL_JI_IGNORE_CURRENCY_DATE in routine &ROUTINE.
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_DEBUG_MODE in routine &ROUTINE.
 
-- gluddl Message Dictionary End


<< gllaar() 07-AUG-2015 17:21:40

Error in: gllaar
Function return status: 0
Function Err Message: unable to drop table
Function warning number: -1
*****************************************************
sqlcaid: sqlabc: 0 sqlcode: 0 sqlerrml: 0
sqlerrmc:
ORA-01422: exact fetch returns more than requested number of rows
ORA-
sqlerrp: sqlerrd: 0 1 0 0 0 538976288
sqlwarn: sqltext:
*****************************************************SHRD0044: Process logging off database and exiting ...

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Login to General Ledger responsibility
2. Run Consolidation Transfer

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot get clarity whether journal got transferred successfully or not

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms