cancel
Showing results for 
Search instead for 
Did you mean: 

Dumps on PRD system

Former Member
0 Kudos

Hi All,

We are having ECC 6.0 PRD system on Windows 2003 MSSQL 2005 platform with Kernel patch level 102.

We are getting multiple dumps on multiple application servers as DBIF_REPO_INTERNAL_ERROR from last one week.

Below are details :

Dump:

Runtime Errors DBIF_REPO_INTERNAL_ERROR

Date and Time 06.12.2007 13:34:53

Short text

Internal error when accessing program "CX_SY_OPEN_SQL_DB=============CP ".

What happened?

The current ABAP/4 program terminated due to

an internal error in the database interface.

What can you do?

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

Error analysis

An unspecified internal error occurred in the SAP-internal

database interface.

For further analysis the SAP system log should be examined

(transaction SM21).

Check the entries in the developer trace of the relevant work process

(transaction ST11).

Attempted to access component "LOAD" of program

"CX_SY_OPEN_SQL_DB=============CP ".

How to correct the error

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"DBIF_REPO_INTERNAL_ERROR" " "

"SAPLSF01" or "LSF01U12"

"BM_COMPONENTS_SELECT"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

Information on where terminated

Termination occurred in the ABAP program "SAPLSF01" - in

"BM_COMPONENTS_SELECT".

The main program was "SAPMSSY1 ".

In the source code you have the termination point in line 155

of the (Include) program "LSF01U12".

<b>SM21 logs as below :</b>

Database error 64 at SEL access to table DF14L

> [64] TCP Provider: The specified network name is no longer

> available.#[64] Communication link failure

Unexpected return value 8 when calling up

Work process has left reconnect status

Run-time error "DBIF_REPO_INTERNAL_ERROR" occurred

> Short dump "071206 123131 dtinsap6 PRD02 " generated

Operating system call recv failed (error no. 10054)

Connection to user 8937 (21 ), terminal 62 (dtdcssapwms0) lost

Database error 64 at SEL access to table DF14T

> [64] TCP Provider: The specified network name is no longer

> available.#[64] Communication link failure

Unexpected return value 8 when calling up

Work process has left reconnect status

Run-time error "DBIF_REPO_INTERNAL_ERROR" occurred

> Short dump "071206 123412 dtinsap6 PRD02 " generated

Database error 64 at DEL access to table ARFCSSTATE

Database error 64 at SEL access to table STXH

> [64] TCP Provider: The specified network name is no longer

> available.#[64] Communication link failure

> [64] TCP Provider: The specified network name is no longer

> available.#[64] Communication link failure

Unexpected return value 8 when calling up

Unexpected return value 8 when calling up

Unexpected return value 8 when calling up DbSlR

Function ROLLBACK on connection R/3 failed

Error in DB rollback/SyFlush, return code 016384

Work process has left reconnect status

Stop Workproc11, PID 1744

Operating system call recv failed (error no. 10054)

Run-time error "DBIF_REPO_INTERNAL_ERROR" occurred

Start Workproc11, Pid 4840

> Short dump "071206 123523 dtinsap6 PRD02 " generated

Transaction Canceled 00 671 ( DBIF_REPO_INTERNAL_ERROR 20071206123523dtinsap6_PRD_02 PAR

Delete session 001 after error 023

Database error 64 at SEL access to table USR41

Can anybody help me regarding the same.

Best Regards,

AjitR

Accepted Solutions (0)

Answers (3)

Answers (3)

markus_doehr2
Active Contributor
0 Kudos

It seems, that the system can't resolve the hostname any more.

Did you change any configuration? Is your DNS server reachable from the application servers?

--

Markus

Former Member
0 Kudos

Markus ,

No settings has been changed but i would like to know where did you find hostname resolve problem . please let me know so that i can take it up with SAP OSS message at least.

Best Regards,

AjitR

markus_doehr2
Active Contributor
0 Kudos

you posted from syslog:

Database error 64 at SEL access to table DF14L

> [64] TCP Provider: The specified network name is no longer

> available.#[64] Communication link failure

Unexpected return value 8 when calling up

It seems, that the network switch/hub has a problem or you have some operating system issues. This is not a SAP problem, you just see the consequences.

--

Markus

Former Member
0 Kudos

Markus,

As requsted by OSS folks i have carried out NIPING test from application server to database server.

Below are results , appreciate if you can throw some light on the same.

As OSS folks are concern about Max and Avg values and they say those values are too high.But i have no clue about suddent issue.

-


trc file: "traceniping", trc level: 2, release: "700"

-


Tue Dec 11 10:13:46 2007

NiIInit: allocated nitab (4096 at 00280020)

NiHsLInit: alloc host/serv bufs (100/100 entries)

command line arg 0: niping

command line arg 1: -c

command line arg 2: -H

command line arg 3: sapprd2

command line arg 4: -V

command line arg 5: 2

command line arg 6: -T

command line arg 7: traceniping

realloc origbuf from 0 to 1000 bytes

filling buffer with test data ...

NiHsLGetNodeAddr: got hostname 'sapprd2' from operation system

NiIGetNodeAddr: hostname 'sapprd2' = addr 192.168.170.205

NiIGetServNo: servicename '3298' = port 0C.E2/3298

NiICreateHandle: hdl 0 state NI_INITIAL

NiIInitSocket: set default settings for new hdl 0 / sock 1932 (I4; ST)

NiIBlockMode: set blockmode for hdl 0 FALSE

NiITraceByteOrder: CPU byte order: little endian, reverse network, low val .. high val

NiICheckPendConnection: connection of hdl 0 to 192.168.170.205:3298 established

NiIConnect: hdl 0 took local address 192.168.170.234:3267

NiIConnect: state of hdl 0 NI_CONNECTED

connect to server o.k.

NiIWrite: hdl 0 sent data (wrt=1000,pac=1,MESG_IO)

NiIRead: hdl 0 recv would block (errno=EAGAIN)

realloc netin buf from 0 to 1000 bytes

NiIRead: hdl 0 received data (rcd=1000,pac=1,MESG_IO)

NiIWrite: hdl 0 sent data (wrt=1000,pac=1,MESG_IO)

NiIRead: hdl 0 recv would block (errno=EAGAIN)

NiIRead: hdl 0 received data (rcd=1000,pac=2,MESG_IO)

NiIWrite: hdl 0 sent data (wrt=1000,pac=1,MESG_IO)

NiIRead: hdl 0 recv would block (errno=EAGAIN)

NiIRead: hdl 0 received data (rcd=1000,pac=2,MESG_IO)

NiIWrite: hdl 0 sent data (wrt=1000,pac=1,MESG_IO)

NiIRead: hdl 0 recv would block (errno=EAGAIN)

NiIRead: hdl 0 received data (rcd=1000,pac=2,MESG_IO)

NiIWrite: hdl 0 sent data (wrt=1000,pac=1,MESG_IO)

NiIRead: hdl 0 recv would block (errno=EAGAIN)

NiIRead: hdl 0 received data (rcd=1000,pac=2,MESG_IO)

NiIWrite: hdl 0 sent data (wrt=1000,pac=1,MESG_IO)

NiIRead: hdl 0 recv would block (errno=EAGAIN)

NiIRead: hdl 0 received data (rcd=1000,pac=2,MESG_IO)

NiIWrite: hdl 0 sent data (wrt=1000,pac=1,MESG_IO)

NiIRead: hdl 0 recv would block (errno=EAGAIN)

NiIRead: hdl 0 received data (rcd=1000,pac=2,MESG_IO)

NiIWrite: hdl 0 sent data (wrt=1000,pac=1,MESG_IO)

NiIRead: hdl 0 recv would block (errno=EAGAIN)

NiIRead: hdl 0 received data (rcd=1000,pac=2,MESG_IO)

NiIWrite: hdl 0 sent data (wrt=1000,pac=1,MESG_IO)

NiIRead: hdl 0 recv would block (errno=EAGAIN)

NiIRead: hdl 0 received data (rcd=1000,pac=2,MESG_IO)

NiIWrite: hdl 0 sent data (wrt=1000,pac=1,MESG_IO)

NiIRead: hdl 0 recv would block (errno=EAGAIN)

NiIRead: hdl 0 received data (rcd=1000,pac=2,MESG_IO)

send and receive 10 messages (len 1000)

-


times -


<b>avg 1.384 ms

max 12.179 ms

min 0.173 ms

tr 1410.912 kB/s

excluding max and min:

av2 0.186 ms

tr2 10479.544 kB/s</b>

NiIWrite: hdl 0 sent data (wrt=0,pac=1,MESG_IO)

NiICloseHandle: shutdown and close hdl 0 / sock 1932

markus_doehr2
Active Contributor
0 Kudos

Check your network components (the activate components the servers are attached to).

--

Markus

Former Member
0 Kudos

Hi Ajju,

Was this a temporary problem or is it occurring again and again (even after app server restart)?

Do you see any related entries in the SQL Server error log at the time of the problem? Any network related entries in the event log of the app server or the db server?

What SQL Server release are you using?

Run at next possible time a database consistency check.

Regards,

Guenther

Former Member
0 Kudos

Hi guys ,

I have applied latest DBSL patch and upgraded to latest kernel .

There are no critical Mssql server log entries or any network problem detected.

As suggested by SAP i will go for DBCC consistency check coming weekend.

Any other thing i should check , as i am Oracle DBA i am not much aware of what all things we should check at mssql database depth level.

My version is mssql 2005

Former Member
0 Kudos

Appreciate your quick help.

Former Member
0 Kudos

Hi,

Apply the latest DBSL patch from the SAP Service Marketplace

regards,

kaushal