cancel
Showing results for 
Search instead for 
Did you mean: 

Short Dump: DBIF_RSQL_SQL_ERROR

Former Member
0 Kudos

Hello experts,

I am getting lot of dumps in my BI system (Windows+ Oracle 10.2)

How to correct part is :

Database error text........: "ORA-00600: internal error code,

[20084], [29798105], [7], [29798105], [7], [], [], []"

Internal call code.........: "[RSQL/FTCH/TBTCO ]"

Please check the entries in the system log (Transaction SM21).

And System log is :

Database error 600 requires database administrator to intervene

Database error 600 at FET access to table TBTCO

> ORA-00600: internal error code, arguments: [20084],

> [29798105], [7], [29798105], [7], [], [], []

Run-time error "DBIF_RSQL_SQL_ERROR" occurred

> Short dump "081006 160347 NW04SBI7 B7I00 " generated

How will I proceed in this scenario ?

Waiting for your guidance!

Thanks in advance!

Abhilash

Accepted Solutions (0)

Answers (4)

Answers (4)

uwe_theisinger
Explorer
0 Kudos

Hi,

have a look at Oracle description to this error:

Note: For additional ORA-600 related information please read Note 146580.1

PURPOSE:

This article discusses the internal error "ORA-600 [20084]", what

it means and possible actions. The information here is only applicable

to the versions listed and is provided only for guidance.

ERROR:

ORA-600 [20084] [a] <b> [c] [d] [e]

VERSIONS:

versions 7.3 to 10.1

DESCRIPTION:

This error can be reported from two different locations in the code.

While unpacking a row source we find that the rowid is not in

asscending order and generate this exception.

The number of additional arguments vary depending on the Oracle release

and the area of code that reports the error.

ARGUMENTS:

For Oracle 9.2 and earlier :

Arg [a] Dba of Current bit stream

Arg <b> Rowid of Current bit stream

Arg [c] Dba of Next bit stream

Arg [d] Rowid of Next bit stream

For Oracle 10.1 there are two formats :

4 additional arguments :

Arg [a] Dba of Current bit stream

Arg <b> Rowid of Current bit stream

Arg [c] Dba of Next bit stream

Arg [d] Rowid of Next bit stream

5 additional arguments :

Arg [a] Flag indicating bitmap type

Arg <b> Dba of Current bit stream

Arg [c] Rowid of Current bit stream

Arg [d] Dba of Next bit stream

Arg [e] Rowid of Next bit stream

FUNCTIONALITY:

Kernel Kompile Row source

Bitmap index creation - row source.

IMPACT:

PROCESS FAILURE

NON DATA CORRUPTIVE - No underlying data corruption.

SUGGESTIONS:

If the Known Issues section below does not help in terms of identifying

a solution, please submit the trace files and alert.log to Oracle

Support Services for further analysis.

Known Issues:

Bug# 4006624 See Note 4006624.8

OERI [20084] from a CATSEARCH query that uses wildcards

Fixed: 9.2.0.8, 10.1.0.5, 10.2.0.1

Bug# 3072094 See Note 3072094.8

CATSEARCH query through a view fails with OERI [20084]

Fixed: 9.2.0.6, 10.1.0.4, 10.2.0.1

Bug# 2394273 See Note 2394273.8

OERI:20084 possible from BITMAP MERGE over BITMAP CONVERSION to ROWIDS

Fixed: 9.2.0.2, 10.1.0.2

Bug# 1555845 See Note 1555845.8

ITEXT: OERI:20084 / duplicate rows from CATSEARCH() with > 5 terms

Fixed: 8.1.7.1B, 9.0.1.0

Historic issues:

Bug# 413657

ORA-600 [20084] WHEN CREATING BITMAP INDEX

fixed in the 7.3.3 release.

create a bitmap index on muliple files(file number > 64) would cause

20084 error.

Workaround: make sure your table lives on file number < 64.

Bug# 531947

ORA-600 [20084] DOING ALTER INDEX REBUILD PARTITION XX PARALLEL X;

fixed in 8.0.4 release.

Workaround: ALTER the INDEX REBUILD without the parallel clause.

regards

Uwe

debasissahoo
Active Contributor
0 Kudos

Hi Abhilash,

Follow the below note,

https://service.sap.com/support/note/1042182

This deals with 'DBIF_RSQL_SQL_ERROR' with reference to database error 'ORA-600' for Oracle based systems..

hope this will help,

Debasis.

Former Member
0 Kudos

Hello Debasis,

I have imported the BW14 SP as per the note given by you.

But still I am getting this runtime error.

Please let me know if there is anyother workaround.

Regards,

Abhilash

former_member204746
Active Contributor
0 Kudos

check in alert_SID.log file for more info on that ORA-00600 error. provide fill error info here.

Last time I had a similar problem, it was caused by a SAN issue and I had to restore from backup to resolve this.

Former Member
0 Kudos

Hello Eric,

From the alert file, i could find the below info,

Tue Oct 07 09:41:37 2008

Incremental checkpoint up to RBA [0xb56.13739.0], current log tail at RBA [0xb56.1379b.0]

Tue Oct 07 10:00:59 2008

Errors in file h:\oracle\b7i\saptrace\usertrace\b7i_ora_40332.trc:

ORA-00600: internal error code, arguments: [20084], [29798105], [7], [29798105], [7], [], [], []

Tue Oct 07 10:11:37 2008

Incremental checkpoint up to RBA [0xb56.15868.0], current log tail at RBA [0xb56.159b7.0]

Tue Oct 07 10:18:26 2008

Errors in file h:\oracle\b7i\saptrace\usertrace\b7i_ora_40332.trc:

ORA-00600: internal error code, arguments: [20084], [29798105], [7], [29798105], [7], [], [], []

Tue Oct 07 10:19:45 2008

Errors in file h:\oracle\b7i\saptrace\usertrace\b7i_ora_4640.trc:

ORA-00600: internal error code, arguments: [20084], [29798105], [7], [29798105], [7], [], [], []

Please let me know how to solve this issue.

Thanks,

Abhilash

Former Member
0 Kudos

And the trace file would be:

      • ACTION NAME:(55090) 2008-10-07 10:00:59.826

      • MODULE NAME:(SAPLBTCH ) 2008-10-07 10:00:59.826

      • SERVICE NAME:(SYS$USERS) 2008-10-07 10:00:59.826

      • SESSION ID:(58.401) 2008-10-07 10:00:59.826

      • 2008-10-07 10:00:59.826

ksedmp: internal or fatal error

ORA-00600: internal error code, arguments: [20084], [29798105], [7], [29798105], [7], [], [], []

Current SQL statement for this session:

SELECT "JOBNAME" , "JOBCOUNT" , "JOBGROUP" , "INTREPORT" , "STEPCOUNT" , "SDLSTRTDT" , "SDLSTRTTM" , "BTCSYSTEM" , "SDLDATE" , "SDLTIME" , "SDLUNAME" , "LASTCHDATE" , "LASTCHTIME" , "LASTCHNAME" , "RELDATE" , "RELTIME" , "RELUNAME" , "STRTDATE" , "STRTTIME" , "ENDDATE" , "ENDTIME" , "PRDMINS" , "PRDHOURS" , "PRDDAYS" , "PRDWEEKS" , "PRDMONTHS" , "PERIODIC" , "DELANFREP" , "EMERGMODE" , "STATUS" , "NEWFLAG" , "AUTHCKNAM" , "AUTHCKMAN" , "SUCCNUM" , "PREDNUM" , "JOBLOG" , "LASTSTRTDT" , "LASTSTRTTM" , "WPNUMBER" , "WPPROCID" , "EVENTID" , "EVENTPARM" , "BTCSYSREAX" , "JOBCLASS" , "PRIORITY" , "EVENTCOUNT" , "CHECKSTAT" , "CALENDARID" , "PRDBEHAV" , "EXECSERVER" , "EOMCORRECT" , "CALCORRECT" , "REAXSERVER" , "RECLOGSYS" , "RECOBJTYPE" , "RECOBJKEY" , "RECDESCRIB" , "TGTSRVGRP" FROM "TBTCO" WHERE "JOBNAME" LIKE :A0 ESCAPE '#' AND ( "STATUS" = :A1 OR "STATUS" = :A2 ) AND "STRTDATE" >= :A3 AND ( "STRTDATE" < :A4 OR "STRTDATE" = :A5 AND "STRTTIME" <= :A6 )

-


Call Stack Trace -


calling call entry argument values in hex

location type point (? means dubious value)

-


-


-


-


_ksedst38 CALLrel _ksedst10 0 1

_ksedmp898 CALLrel _ksedst0 0

_ksfdmp14 CALLrel _ksedmp0 3

_kgeriv+146 CALLreg 00000000 B5863A8 3

_kgeasi92 CALLrel _kgeriv0 B5863A8 76720C4 4E74 4

E80D310

_qerbtRop346 CALLrel _kgeasi0 B5863A8 76720C4 4E74 2 4 0

1C6AED9 0 0 7 0 0 1C6AED9 0 0

7 0

_qersoFetch+366 CALLptr 00000000

_qerbtFetch+607 CALL??? 00000000

_kdibr1sf+55 CALL??? 00000000 317EC790 0 0 1 317EC790

E80D498

_qerbaFndOl125 CALLrel _kdibr1sf0 EBC8198 317EC790 E80D498

DDC51C4

_qerbaStrmAnd145 CALLrel _qerbaFndOl0

_qerbaFetch121 CALLrel _qerbaStrmAnd0

_kdibr1sf+55 CALL??? 00000000 317EC61C 0 0 1 317EC61C 0

_qerbtFetch1448 CALLrel _kdibr1sf0 ECB3F54 317EC61C 0 ECB3F68

_qertbFetchByRowID+ CALL??? 00000000 317EC464 0 E80D828 1

475

_qeruaFetch+253 CALL??? 00000000

_opifch2+3115 CALL??? 00000000 317EC0FC 1E9B2F4 E80D9D8 18

_opiefn0348 CALLrel _opifch20 89 4 E80DB7C

_opiefn21 CALLrel _opiefn00 4E 4 E80F698 0 0 0 0 0 0 0

_opiodr+1099 CALLreg 00000000 4E 4 E80F698

_ttcpip+1273 CALLreg 00000000 4E 4 E80F698 C9

_opitsk+1017 CALL??? 00000000

_opiino1087 CALLrel _opitsk0 0 0

_opiodr+1099 CALLreg 00000000 3C 4 E80FC30

_opidrv819 CALLrel _opiodr0 3C 4 E80FC30 0

_sou2o45 CALLrel _opidrv0 3C 4 E80FC30

opimaireal112 CALLrel _sou2o0 E80FC24 3C 4 E80FC30

_opimai92 CALLrel opimaireal0 2 E80FC5C

_OracleThreadStart@ CALLrel _opimai+0

4+708

77E64826 CALLreg 00000000

Thanks,

Abhilash

markus_doehr2
Active Contributor
0 Kudos

What exact Oracle version and minipatch are you using?

Markus