SQL error 3113 occurred when executing EXEC SQL.

Question

Hi,
We are facing one typical problem, One background is failing regularly with
below dump. as we now got all notes giving information, if database  restarted
taking backup, these type of failures occur, but our database is only down for backup once in a week, but it is failing with frequenly.
in this two servers are located in different place, in this job tries to connect
another server to get material statistics.
It is giving some error message in sm21 with
SQL error 3113 occurred when executing EXEC SQL.
work procees in reconnect mode.
all notes saying these types of dump occur when database restared, but this dump
even though database is up.
below is short dump, please can anyone help me from this problem.
ABAP runtime errors    DBIF_DSQL2_SQL_ERROR
      Occurred on    08.01.2007 at 00:30:28
>> Short dump has not been completely stored. It is too big.
SQL error 3113 occurred when executing EXEC SQL.
What happened?
The error occurred in the current database connection "AZ1".
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
How to correct the error
Database error text........: "ORA-03113: end-of-file on communication channel#"
Triggering SQL statement...: "select mara.groes, mara.brgew, mara.ntgew,
mara.gewei, mara.volum, mara.voleh, mara.mstae, mara.mstde, mara.prdha,
marc.matnr, marc.werks, marc.mmsta, marc.mmstd from sapr3.mara, sapr3.m
where sapr3.mara.mandt = sapr3.marc.mandt and sapr3.mara.matnr =
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"DBIF_DSQL2_SQL_ERROR"
"ZM2431216 " or "ZM2431216 "
"EXTRACT_GENERAL_DATA"
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 th
  print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error o
  or which actions and input led to the error.
System environment
SAP Release.............. "46C"
Application server....... "essceu3"
Network address.......... "172.19.119.198"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "00C7ADBD4C00"
Database server.......... "ukblx176"
Database type............ "ORACLE"
Database name............ "EU3"
Database owner........... "SAPR3"
Character set............ "es_ES.ISO8859-1"
SAP kernel............... "46D"
Created on............... "Jul 9 2006 20:26:33"
Created in............... "AIX 1 5 00447C4A4C00"
Database version......... "OCI_920__OCI_7_API "
Patch level.............. "2257"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.0.5.., ORACLE 8.0.6.., ORACLE
8.1.6.., ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE 10.2.0.."
SAP database version..... "46D"
Operating system......... "AIX 1 4, AIX 2 4, AIX 3 4, AIX 1 5, AIX 2 5, AIX 3
5, , System build information:,                                      , LCHN :
841480"
User, transaction...
Client.............. 600
User................ "MPZMMES"
Language key........ "S"
Transaction......... " "
Program............. "ZM2431216 "
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where termination occurred
The termination occurred in the ABAP/4 program "ZM2431216 " in
"EXTRACT_GENERAL_DATA".
The main program was "ZM2431216 ".
The termination occurred in line 980
of the source code of program "ZM2431216 " (when callin
The program "ZM2431216 " was started as a background jo
Source code extract
009500              mara.ntgew,
009510              mara.gewei,
009520              mara.volum,
009530              mara.voleh,
009540              mara.mstae,
009550              mara.mstde,
009560              mara.prdha,
009570              marc.matnr,
009580              marc.werks,
009590              marc.mmsta,
009600              marc.mmstd
009610        into :w_ops-groes,
009620              :w_ops-brgew,
009630              :w_ops-ntgew,
009640              :w_ops-gewei,
009650              :w_ops-volum,
009660              :w_ops-voleh,
009670              :w_ops-mstae,
009680              :w_ops-mstde,
009690              :w_ops-prdha,
009700              :w_ops-matnr,
009710              :w_ops-werks,
009720              :w_ops-mmsta,
009730              :w_ops-mmstd
009740        from sapr3.mara, sapr3.marc
009750        where sapr3.mara.mandt = sapr3.marc.mandt
009760          and sapr3.mara.matnr = sapr3.marc.matnr
009770          and sapr3.mara.mandt = :p_mandt
009780          and sapr3.mara.matnr = :w_ebs-matnr
009790          and sapr3.marc.werks = :p_owerks
    >    ENDEXEC.
009810  endform.                    " extract_general_data
009820  *&
009830  *&      Form  append_i_ops
009840  *&
009850  *      Appends W_OPS to I_OPS
009860  *
009870  form append_i_ops.
009880    append w_ops to i_ops.
009890  endform.                    " append_i_ops
009900  *&
009910  *&      Form  extract_material_description
009920  *&
009930  *      Extracts a Material Description from the remote database an
009940  *      modifies the current record in I_OPS.
009950  *
009960  *        >P_SPRAS  Language Key
009970  *
009980  form extract_material_description using    p_spras.
009990    EXEC sql performing set_langauge.
Contents of system fields
SY field contents..................... SY field contents............
SY-SUBRC 0                            SY-INDEX 0
SY-TABIX 1                            SY-DBCNT 1
SY-FDPOS 18                            SY-LSIND 0
SY-PAGNO 0                            SY-LINNO 1
SY-COLNO 1
Chosen variables
Name.......................... Contents.1........2........3....+..
W_EBS-PRAT4
                              2
                              0
W_OPS-GROES
                              22222222222222222222222222222222
                              00000000000000000000000000000000
W_OPS-BRGEW                    #######
                              0000000
                              000000C
W_OPS-NTGEW                    #######
                              0000000
                              000000C
regards,
krishnaiah.

Answer 1

Hi,
This is usually a SERVER SIDE DATABASE PROBLEM or SQLNET LISTENER (server side) PROBLEM.  The client side should initially be ignored and instead the server should be investigated. In rare cases, this can be caused by client
side memory or other resource problem, or a DLL version mismatch, but this is
unlikely.
Enlist the assistance of your DBA.  Then reproduce the ORA-3113 error on your
client application.  Ask your DBA to look at the database side Alert.log and
trace files and look for ANY activity.  Any activity that coincides with your
ORA-3113 will be a clue.
REgards
Vinod