Skip to Content
0
Former Member
Sep 09, 2009 at 05:54 AM

Runtime error DBIF_REPO_SQL_ERROR in production server

1517 Views

Hello All,

I am recieving the following running time error in my Production system. Any help would be really appreciated.

-----------------------------------------------------------------------------------------
Runtime Error          DBIF_REPO_SQL_ERROR
       Occurred on     06.09.2009 at   19:16:45
------------------------------------------------------------------------------------------

*SQL error 3114 occurred when accessing program*

--------------
What happened?
--------------

The system is no longer linked to an ORACLE instance.
No further operations can be performed on the database.

----------------
What can you do?
----------------

You cannot eliminate this error yourself.
Please inform your database administrator.
Make a note of the actions and input which caused the error.
-

To resolve the problem, contact your
SAP system administrator.

With transaction ST22, for dump analysis, you can see and manage
termination messages and, in particular, save them for longer periods of
 time.

Make a note of the actions and input which caused the error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.


--------------
Error analysis
--------------

The system attempted to access an ORACLE instance to which it is
no longer linked.
This can occur if the ORACLE instance has been stopped due to an
error or an external operation.

------------------------
How to correct the error
------------------------

Database error text........: "ORA-03114: not connected to ORACLE"
Triggering SQL statement...: "CX_SY_OPEN_SQL_DB=============CP "
The current status of the ORACLE instance cannot be determined.
It may still be inactive or the database administrator may have
restarted it.
In any case, all systems that have accessed the ORACLE instance
must be restarted after the ORACLE instance has been restarted.
-
If you were working on a central system, inform
your system administrator.
If you were working on an external local system, inform
the person responsible for this system.
If you were working on your own local system, restart
the system yourself.

You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:

------------------------------------------------------------------------
"DBIF_REPO_SQL_ERROR" C
"SAPLSALA" or "LSALAU01"
"SALA_UPDATE_TRANS_SPEZ_MON"
------------------------------------------------------------------------
If you cannot solve the problem yourself, please send the
following documents to SAP:

1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
-

2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.

3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.

4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.

You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:

------------------------------------------------------------------------
"DBIF_REPO_SQL_ERROR" C
"SAPLSALA" or "LSALAU01"
"SALA_UPDATE_TRANS_SPEZ_MON"
------------------------------------------------------------------------
If you cannot solve the problem yourself, please send the
following documents to SAP:

1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
-

2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.

3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.

4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
Internal call code.........: "[REPO/*/43/LOAD/CX_SY_OPEN_SQL_DB=============CP
 ]"
Please check the entries in the system log (Transaction SM21).

You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:

------------------------------------------------------------------------
"DBIF_REPO_SQL_ERROR" C
"SAPLSALA" or "LSALAU01"
"SALA_UPDATE_TRANS_SPEZ_MON"
------------------------------------------------------------------------
If you cannot solve the problem yourself, please send the
following documents to SAP:
------------------------------------------------------------------------

Already we have checked the SAPnotes 534729, 135942 and 112266 advice to configure all network

components on the same fixed speed and full-duplex, instead of using the auto-negotiating.

Please suggest... thanks in advace.

Regards,

Suresh

Edited by: Suresh Kalagarla on Sep 9, 2009 11:27 AM