cancel
Showing results for 
Search instead for 
Did you mean: 

SAP starting up OK but ABAPDUMPS are coming regarding Oracle

Former Member
0 Kudos

Dear Desk,

I am really in caught in middle of a project. Please help.

Though my QA severs in shutting down and starting up normally with out any error (Stopsap and startsap in ok)

but my none of my background job is running being executed in DDIC user.

but when I went into STMS it doesnot opened queue giving me abap dump as follows

****

Runtime errors DBIF_RSQL_SQL_ERROR

Exception CX_SY_OPEN_SQL_DB

Occurred on 02.02.2011 at 17:34:34

An SQL error occurred when accessing a table.

What happened?

An exceptional situation has occurred in the ORACLE software,

possibly due to an error.

This is not an error in an application program.

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

****

then I check sm37 there I founf no job is running and giving SQL errors.

2.02.2011 03:31:41 Job started 00 516 S

2.02.2011 03:31:41 Step 001 started (program RSCOLL00, variant , user ID DDIC) 00 550 S

2.02.2011 03:31:44 ABAP/4 processor: DBIF_RSQL_SQL_ERROR 00 671 A

2.02.2011 03:31:44 Job cancelled 00 518 A

*****

even I not able to use SUIM transaction to see user lists. Means there is problem in Oralce Query

Kindly help me in this.

Regards

Waqas

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Check the log files in /usr/sap/SID/INSTANCE/work folder. e.g. dev_w0, std*.out files etc.

Former Member
0 Kudos

B ***LOG BY4=> sql error 600 performing FET on table USR02 [dbtran#4 @ 7275] [dbtran 7275 ]

B ***LOG BY0=> ORA-00600: internal error code, arguments: [12700], [62632], [105086225], [2], [105086233], [25], [], [] [dbtran#4 @

B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'FET'

B RSLT: {dbsl=99, tran=1}

B FHDR: {tab='USR02', fcode=225, mode=2, bpb=0, dbcnt=0, crsr=1,

B hold=0, keep=1, xfer=3, pkg=0, upto=0, init:b=0,

B init:p=0, init:#=226, wa:p=0, wa:#=226}

B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'FET'

B STMT:

B CRSR: {tab='USR02', id=1, hold=0, prop=0x10000, max.in@0=1, fae:blk=5,

B con:id=0, con:vndr=5, val=2,

B key:#=2, xfer=3, xin:#=0, row:#=0, upto=0, wa:p=10302d1b8}

A TH VERBOSE LEVEL FULL

M ***LOG R68=> ThIRollBack, roll back () [thxxhead.c 12337]

A

A Wed Feb 2 17:33:37 2011

A Wed Feb 2 17:33:37 2011

A

A ABAP/4 Program SAPLSUU1 .

A Source LSUU1U02 Line 136.

A Error Code DBIF_RSQL_KEY_NOT_FOUND.

A Module $Id: //bas/640_REL/src/krn/runt/absapsql.c#15 $ SAP.

A Function HandleRsqlErrors Line 756.

A No data found for specified key in the table..

A

C

C Wed Feb 2 17:34:33 2011

C *** ERROR => ORA-600 occurred when executing SQL statement (parse error offset=0)

[dbsloci.c 11440]

C sc_p=1055e2510,no=180,idc_p=0,con=0,act=1,slen=65,smax=256,#vars=2,stmt=10638a7e0,table=TMSBUFFER

C SELECT * FROM "TMSBUFFER" WHERE "DOMNAM" = :A0 AND "SYSNAM" = :A1;

C sc_p=1055e2510,no=180,idc_p=0,con=0,act=1,slen=65,smax=256,#vars=2,stmt=10638a7e0,table=TMSBUFFER

C prep=0,lit=0,nsql=0,lobret=0,#exec=1,dbcnt=0,upsh_p=0,ocistmth_p=10638b448

Former Member
0 Kudos

On trace files for w_1 we are getting

**************************************************

Wed Feb 2 17:16:46 2011

      • ERROR => ORA-600 occurred when executing SQL statement (parse error offset=0)

dbsloci.c 11278]

sc_p=1055e00f8,no=103,idc_p=1055f56f0,con=0,act=1,slen=156,smax=256,#vars=7,stmt=105ea8250,table=CSMBK_CL

DELETE FROM "CSMBK_CL" WHERE "RELID" = :A0 AND "SCHEME" = :A1 AND "CLASS" = :A2 AND "ACTIVE" = :A3 A\

ND "DOMVERS" = :A4 AND "SUBVERS" = :A5 AND "SRTF2" = :A6;

sc_p=1055e00f8,no=103,idc_p=1055f56f0,con=0,act=1,slen=156,smax=256,#vars=7,stmt=105ea8250,table=CSMBK_CL

prep=0,lit=0,nsql=0,lobret=0,#exec=2,dbcnt=0,upsh_p=0,ocistmth_p=105ea8eb8

IN : cols=7,rmax=1,xcnt=1,rpc=0,rowi=0,rtot=1,upto=4294967295,rsize=63,vmax=32,bound=1,iobuf_p=1057a03b0,vda_p=105eaa590

lobs=0,lmax=0,lpcnt=0,larr=0,lcurr_p=0,rret=0

OUT: cols=0,rmax=0,xcnt=0,rpc=0,rowi=0,rtot=0,upto=0,rsize=0,vmax=0,bound=0,iobuf_p=0,vda_p=0

lobs=0,lmax=0,lpcnt=0,larr=0,lcurr_p=0,rret=0

DELETE FROM "CSMBK_CL" WHERE "RELID" = :A0 AND "SCHEME" = :A1 AND "CLASS" = :A2 AND "ACTIVE" = :A3 A\

ND "DOMVERS" = :A4 AND "SUBVERS" = :A5 AND "SRTF2" = :A6;

***LOG BYL=> DBQ action required because of database error [dbsh#2 @ 1096] [dbsh 1096 ]

SQL code: 600, SQL text: ORA-00600: internal error code, arguments: [13011], [12291], [16793731], [3], [16793731], [17], [], []

***LOG BY4=> sql error 600 performing DEL on table CSMBK_CL [dbtrtab#1 @ 3948] [dbtrtab 3948 ]

***LOG BY0=> ORA-00600: internal error code, arguments: [13011], [12291], [16793731], [3], [16793731], [17], [], [] [dbtrtab#1 @

TH VERBOSE LEVEL FULL

***LOG R68=> ThIRollBack, roll back () [thxxhead.c 12337]

Wed Feb 2 17:16:47 2011

Wed Feb 2 17:16:47 2011

ABAP/4 Program CSM_CLEAN_CLASS_TABLES .

Source CSM_CLEAN_CLASS_TABLES Line 34.

Error Code DBIF_RSQL_SQL_ERROR.

Module $Id: //bas/640_REL/src/krn/runt/absapsql.c#15 $ SAP.

Function HandleRsqlErrors Line 781.

An SQL error occurred when accessing a table..

Former Member
0 Kudos

Please try running DB verify from DB13. If you get any problem, ask your DBA to run RMAN verification in your database.

This will help you to find the root cause.

Former Member
0 Kudos

Dear Arindam,

You are right. Initially on investigation I found corruption in redo logs. I cleaned them and then I ran DBVerify and found one of my datafile is also corrupted, now I am restoring that datafile from backup and applying archivelogs. Lets see how it goes.

I will update you. Thanks.

Regards

Former Member
0 Kudos

Yes, Due to data corruption and harddik issues dumps were coming though SAP was starting up cleanly.

I fixed storage system issues first and then restore oracle database and things are fine now.

Regards

Waqas

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Waqas,

Can you stop SAP/Oracle and restart it again to see if it fixes the issue.

Regards,

Neeraj