Batch Fails with 'Could Not Connect to the Database from Login Information' in New Infodom (Doc ID 1485792.1)

Last updated on APRIL 07, 2017

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version 7.3 and later
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)

Symptoms

In Oracle Financial Services Analytical Applications (OFSAA), when running a Batch that contains at Data Transformation (ex. Batch_Table_Class_Req, fn_drmDataLoader, Product_Inst_Mapping, etc.) in a newly created Infodom, the batch fails and the following error is in the "RunProc" log in $FIC_DB_HOME/log/date:

-------------------------------------LOG FILE FOR DATESERVER--------------------------------------
----------------------------------------------------------------------------------------------------
GENERATION OF RUNPROCEDURE.LOG STARTED ON : Mon Aug 20 16:07:39 2012
----------------------------------------------------------------------------------------------------

Log Message here 1: Mon 20 Aug 2012 04:07:39 PM EDT||INFO||Invoking execProc
Log Message here 1: Mon 20 Aug 2012 04:07:39 PM EDT||INFO||Dsn Id :
ClsUSmsConnect::ClsUSmsConnect, Forming Login Info statement
Log Message here 1: Mon 20 Aug 2012 04:07:39 PM EDT||INFO||Database Type : ORACLE
Log Message here 1: Mon 20 Aug 2012 04:07:39 PM EDT||INFO||NLS Value : AMERICAN_AMERICA.UTF8
FAILED: log_on()
Log Message here 1: Mon 20 Aug 2012 04:07:40 PM EDT||SEVERE||Could not Connect to the Database from Login Information
OCI_NO_DATA
Warning : Could not log off 0
Log Message here 1: Mon 20 Aug 2012 04:07:40 PM EDT||INFO||After Calling execProc
Log Message here 1: Mon 20 Aug 2012 04:07:40 PM EDT||SEVERE||Stored procedure execution failed

----------------------------------------------------------------------------------------------------
END OF RUNPROCEDURE OPERATIONS : Mon Aug 20 16:07:40 2012
----------------------------------------------------------------------------------------------------


This connect error only occurs when running batches in the newly created Information Domain.  Batches in the original infodom work as expected.

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