cancel
Showing results for 
Search instead for 
Did you mean: 

DBSL

Former Member
0 Kudos

Hi gurus,

For the past days, we encountered strange errors:

Runtime error "DBIF_RTAB_INTERNAL_ERROR"

It has something to do with DBSL 13 error, which I bold from errors below.

Any ideas what happen?

We're running ECC 6.0 EhP6 on Windows 2008R2, 721EXT kernel level 100, Oracle 11.2.0.3.

A Thu Aug 01 16:37:00 2013

A  ** RABAX: level LEV_RX_C_STACK completed.

A  ** RABAX: level LEV_RX_MEMO_CHECK entered.

A  ** RABAX: level LEV_RX_MEMO_CHECK completed.

A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.

A  ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.

A  ** RABAX: level LEV_RX_INTERFACES entered.

A  ** RABAX: level LEV_RX_INTERFACES completed.

A  ** RABAX: level LEV_RX_GET_MESS entered.

A  ** RABAX: level LEV_RX_GET_MESS completed.

A  ** RABAX: level LEV_RX_INIT_SNAP entered.

A  ** RABAX: level LEV_RX_INIT_SNAP completed.

A  ** RABAX: level LEV_RX_WRITE_SYSLOG entered.

A  ** RABAX: level LEV_RX_WRITE_SYSLOG completed.

A  ** RABAX: level LEV_RX_WRITE_SNAP_BEG entered.

A  ** RABAX: level LEV_RX_WRITE_SNAP_BEG completed.

A  ** RABAX: level LEV_RX_WRITE_SNAP entered.

C  dbsl err=13=DBSL_ERR_STMTID -> dbds err=4=DS_INTERNALERROR, dbdsoci.c:790

C  *** ERROR => ^^ Ds_exec() -> err=4=DS_INTERNALERROR

[dbdsoci.c    860]

C  {root-id=6C3BE5AC5B531EE2BED010BFB6813F9B}_{conn-id=00000000000000000000000000000000}_0

A  ** RABAX:  level LEV_SN_C_STACK failed.

A  ** RABAX: level LEV_RX_WRITE_SNAP entered.

A  ** RABAX: level LEV_RX_WRITE_SNAP completed.

A  ** RABAX: level LEV_RX_WRITE_SNAP_END entered.

A  ** RABAX: level LEV_RX_WRITE_SNAP_END completed.

A  ** RABAX: level LEV_RX_SET_ALERT entered.

C  dbsl err=13=DBSL_ERR_STMTID -> dbds err=4=DS_INTERNALERROR, dbdsoci.c:2201

C  *** ERROR => ^^ cursor_open() -> err=4=DS_INTERNALERROR

[dbdsoci.c    2209]

C  {root-id=6C3BE5AC5B531EE2BED010BFB6813F9B}_{conn-id=00000000000000000000000000000000}_0

C  dbsl err=13=DBSL_ERR_STMTID -> dbds err=4=DS_INTERNALERROR, dbdsoci.c:2201

C  *** ERROR => ^^ cursor_open() -> err=4=DS_INTERNALERROR

[dbdsoci.c    2209]

C  {root-id=6C3BE5AC5B531EE2BED010BFB6813F9B}_{conn-id=00000000000000000000000000000000}_0

C  dbsl err=13=DBSL_ERR_STMTID -> dbds err=4=DS_INTERNALERROR, dbdsoci.c:2201

C  *** ERROR => ^^ cursor_open() -> err=4=DS_INTERNALERROR

[dbdsoci.c    2209]

C  {root-id=6C3BE5AC5B531EE2BED010BFB6813F9B}_{conn-id=00000000000000000000000000000000}_0

Regards,

Accepted Solutions (0)

Answers (2)

Answers (2)

Reagan
Advisor
Advisor
0 Kudos

Hello

What is the version of Oracle Instant Client used on the system ?

Regards

RB

Former Member
0 Kudos

Hi,

Please find genezi -v:

Client Shared Library 64-bit - 11.2.0.3.0

Windows NT Version V6.1 Service Pack 1

CPU                 : 20 - type 8664, 19 Physical Cores

Process Affinity    : 0x0x0000000000000000

Memory (Avail/Total): Ph:258258M/327669M, Ph+PgF:87199M/357667M

Operating in ORACLE_HOME environment.

Small timezone file = F:\oracle\XXX\11203\oracore\zoneinfo\timezone_14.dat

Large timezone file = F:\oracle\XXX\11203\oracore\zoneinfo\timezlrg_14.dat

former_member206552
Active Contributor
0 Kudos

Hi Bobby,

has anything changed in the last couple of day ?

kernel ?

Because looking at it i would suggest by updating the Database Library lib_dbsl which can be found under the kernel location of SMP

Best Regards

Marius

Former Member
0 Kudos

nothing changed.

as i said, kernel and dbsl are currently at its latest level, trace has been set to level 2 for dbsl component.

regards,

former_member206552
Active Contributor
0 Kudos

ok thanx,

can you upload the ST22 dump ?

Best Regards

Marius

Former Member
0 Kudos

"short dump no longer exist" every time I check sm21.

maybe the dump is too large.

former_member206552
Active Contributor
0 Kudos

can you place the SM21 dump contents ?

stefan_koehler
Active Contributor
0 Kudos

Hi Bobby,

> trace has been set to level 2 for dbsl component.

That's the right approach for this issue, but have you also set the corresponding search pattern (parameter rdisp/TRACE_PATTERN_<X>) to deactivate the trace? DBSL tracing generates a lot of information and so you usually lose the important part very fast by "work process trace file rotation".

Regards

Stefan