Enginemanager Is Unable To Connect To Oracle. (Doc ID 558394.1)

Last updated on APRIL 04, 2025

Applies to:

Symptoms

During the Demantra Forecast engine run, the client receives an ORA-03114: not connected to ORACLE error message similar to the following:  

 Snap shot from the Demantra Engine Manager Log with Debugging Turned On 

    11:35:29:536 *** Query 272 Started ***
    11:35:29:536   ---SQL Start: ----------------------------------------------
    11:35:29:536 UPDATE INIT_PARAMS_0 SET value_date = SYSDATE WHERE pname = 'work_status'
    11:35:29:536   ---SQL   End: ----------------------------------------------
    11:35:29:552 *** Query 272 Ended ***
    11:35:39:615 *** Query 273 Started ***
    11:35:39:615   ---SQL Start: ----------------------------------------------
    11:35:39:615 UPDATE INIT_PARAMS_0 SET value_date = SYSDATE WHERE pname = 'work_status'
    11:35:39:615   ---SQL   End: ----------------------------------------------
    11:35:39:615 *** Query 273 Ended ***
    11:35:49:631 *** Query 274 Started ***
    11:35:49:631   ---SQL Start: ----------------------------------------------
    11:35:49:631 UPDATE INIT_PARAMS_0 SET value_date = SYSDATE WHERE pname = 'work_status'
    11:35:49:631   ---SQL   End: ----------------------------------------------
    11:35:49:631 *** Query 274 Ended ***
    11:35:53:631 Engines have finished executing.
    11:35:56:100 Engine on machine localhost finished execution successfully
    11:35:56:147 *** Query 275 Started ***
    11:35:56:147   ---SQL Start: ----------------------------------------------
    11:35:56:147 UPDATE forecast_history SET status = 1, with_optimization = 0 WHERE FORE_COLUMN_NAME
    = 'FORE_0'
    11:35:56:147   ---SQL   End: ----------------------------------------------
    11:35:56:163 ERROR ---------------------------------------------------------------
    11:35:56:163 ERROR   DB_Connection::Execute threw an exception:
    11:35:56:163 ERROR   UPDATE forecast_history SET status = 1, with_optimization = 0 WHERE
    FORE_COLUMN_NAME = 'FORE_0'
    11:35:56:163 ERROR   - ErrorDescription: ORA-03114: not connected to ORACLE
    11:35:56:163 ERROR   - ErrorNumber: 0x80004005 - Unspecified error
    11:35:56:163 ERROR   - NativeErrorNumber: 3114
    11:35:56:163 ERROR   - ErrorDescription: Unspecified error
    11:35:56:163 ERROR   - ErrorNumber: 0x80004005 - Unspecified error
    11:35:56:163 ERROR   - NativeErrorNumber: 0
    11:35:56:163 ERROR ---------------------------------------------------------------
    11:35:56:163 ERROR ExecuteSQL failed: UPDATE forecast_history SET status = 1, with_optimization =
    0 WHERE FORE_COLUMN_NAME = 'FORE_0'
   11:35:56:163 ERROR ---------------------------------------------------------------
   11:35:56:163 ERROR Database Error [EngineManager.cpp,1294]
   11:35:56:163 ERROR   - Source: Microsoft OLE DB Provider for Oracle
   11:35:56:163 ERROR   - Description: ORA-03114: not connected to ORACLE
   11:35:56:163 ERROR   - Message: Unspecified error
   11:35:56:163 ERROR   - Error Number: 0x80004005 - Unspecified error
   11:35:56:163 ERROR ---------------------------------------------------------------
   11:35:56:163 *** Query 276 Started ***
   11:35:56:163   ---SQL Start: ----------------------------------------------
   11:35:56:163 UPDATE forecast_history SET TOTAL_RUN_TIME  = '0:20' WHERE FORE_COLUMN_NAME = 'FORE_0'
   11:35:56:163   ---SQL   End: ----------------------------------------------
   11:35:56:163 ERROR ---------------------------------------------------------------
   11:35:56:163 ERROR   DB_Connection::Execute threw an exception:
   11:35:56:163 ERROR   UPDATE forecast_history SET TOTAL_RUN_TIME  = '0:20' WHERE FORE_COLUMN_NAME = 
   'FORE_0' 
   11:35:56:163 ERROR   - ErrorDescription: ORA-03114: not connected to ORACLE
   11:35:56:163 ERROR   - ErrorNumber: 0x80004005 - Unspecified error
   11:35:56:163 ERROR   - NativeErrorNumber: 3114
   11:35:56:163 ERROR   - ErrorDescription: Unspecified error
   11:35:56:163 ERROR   - ErrorNumber: 0x80004005 - Unspecified error
   11:35:56:163 ERROR   - NativeErrorNumber: 0
   11:35:56:163 ERROR ---------------------------------------------------------------
   11:35:56:163 ERROR ExecuteSQL failed: UPDATE forecast_history SET TOTAL_RUN_TIME  = '0:20' WHERE
   FORE_COLUMN_NAME = 'FORE_0'

   The sqlnet.ora log shows the following error at the time of the Demantra Oracle error:   

***********************************************************************
    Fatal NI connect error 12560, connecting to:

    (DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle)(ARGV0=oracleORCL)(ARGS='(DESCRIPTION=(LOCAL=YES)
    (ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(SID=ORCL)(CID=(PROGRAM=D:\Demantra\Spectrum\V711\Demand
    Planner\Analytical Engines\bin\EngineManager.exe)(HOST=XXX)(USER=XXX))))
      VERSION INFORMATION:
      TNS for 32-bit Windows: Version 9.2.0.1.0 - Production
      Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 9.2.0.1.0 - Production
      Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version 9.2.0.1.0 - Production
      Time: 20-FEB-2008 16:28:21
      Tracing not turned on.
      Tns error struct:
        nr err code: 0
        ns main err code: 12560
        TNS-12560: TNS:protocol adapter error
        ns secondary err code: 0
        nt main err code: 530
        TNS-00530: Protocol adapter error
        nt secondary err code: 126
        nt OS err code: 0

Alert.log

    Errors in file /var/opt/oracle/admin/tfdmp/udump/tfdmp_ora_18438.trc:

    ORA-07445: exception encountered: core dump [opidsa()+386] [SIGSEGV] [Address not mapped to
 
   object] [0x000000000] [] []

    Thread 1 advanced to log sequence 935

Error seems to occur on Demantra versions v711 and higher (but may not be limited to these versions)

Cause

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