Skip to Content
avatar image
Former Member

Database error 604 at INS when accessing table ALCLASTOOL

Hi all,

Recently, I've been getting this error message in my (DEV) SAP's system log (interval of 30min).

Database error 604 at INS access to table ALCLASTOOL

> ORA-00604: error occurred at recursive SQL level 1#ORA-01013

> user requested cancel of current operation

Run-time error "DBIF_RSQL_SQL_ERROR" occurred

> Short dump "091103 094439 sapdev_D EV_00 " generated

I'm not sure how to trace the table ALCASTOOL or how to solve this problem.

The solution I've tried so far:

1. check dataspace and extend files that has reach >90% usage.

2. check if any background job running that have failed.

3. restarted the Oracle Database and Operation system (windows 2003)

Anyone have any idea on this issue or how I can debug deeper to the problem I'm facing?

Thank you

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Nov 03, 2009 at 02:31 AM

    Hi Sek

    What is the value of parameter rdisp/max_wprun_time ? 30 minutes? If yes , can you please increase the value?

    Please also check https://service.sap.com/sap/support/notes/618861 if you havent already.

    Regards

    Anindya

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Anindya Bose

      I'm using Ecc6.0

      p/s: the one thing I dont understand is how come background jobs could have impact with a dialog-based profile parameter?

      Edited by: Sek Yao Ooi on Nov 3, 2009 6:24 AM

      edit2:

      I notice that somehow (despite) being a background job(sm37), it still uses the dialog process (sm50) to execute. Could this be the reason why the issue is affected by parameter "rdisp/max_wprun_time" ?

      Also, the table ALCLASTOOL (Alert: Assignment of tools to object class) is contantly updated (INS statement), but there is no new entry nor is there any new update to the table. At least, there is no new entry/update in se16n. Do I need to go into database level in order to check ?

      Edited by: Sek Yao Ooi on Nov 4, 2009 2:10 AM

  • avatar image
    Former Member
    Nov 04, 2009 at 04:11 AM

    In addition, I got this log from sm50

    Wed Nov 04 11:27:31 2009

    ThAlarmHandler (1)

    ThAlarmHandler: set CONTROL_TIMEOUT/DP_CONTROL_JAVA_EXIT and break sql

    User requested cancel of current SQL on connection 0

    db_sqlbreak() = 0

    program canceled

    reason = max run time exceeded

    user = SAPSYS

    client = 000

    terminal =

    report = SAPLSALU

    ThAlarmHandler: return from signal handler

    OCIStmtExecute() failed with -1=OCI_ERROR

    SQL error 604:

    • ERROR => Error 604 in stmt_execute() from oci_execute_stmt(), orpc=0

    [dbsloci.c 12781]

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

    [dbsloci.c 12783]

    sc_p=05FBA154,no=193,idc_p=05FC9794,con=0,act=1,slen=80,smax=256,#vars=8,stmt=2EE2E018,table=ALCLASTOOL

    INSERT INTO "ALCLASTOOL" VALUES( :A0 , :A1 , :A2 , :A3 , :A4 , :A5 , :A6 , :A7 );

    sc_p=05FBA154,no=193,idc_p=05FC9794,con=0,act=1,slen=80,smax=256,#vars=8,stmt=2EE2E018,table=ALCLASTOOL

    prep=0,lit=0,nsql=0,lobret=0,#exec=1848,dbcnt=0,upsh_p=00000000,ocistmth_p=2EE86AA4

    IN : cols=8,rmax=1,xcnt=1,rpc=0,rowi=0,rtot=1,upto=-1,rsize=262,vmax=32,bound=1,iobuf_p=0B5B72A8,vda_p=2EDEE198

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

    OUT: cols=8,rmax=325,xcnt=0,rpc=0,rowi=0,rtot=0,upto=0,rsize=184,vmax=32,bound=0,iobuf_p=00000000,vda_p=2EDEE608

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

    INSERT INTO "ALCLASTOOL" VALUES( :A0 , :A1 , :A2 , :A3 , :A4 , :A5 , :A6 , :A7 );

    ***LOG BY4=> sql error 604 performing INS on table ALCLASTOOL [dbtran#14 @ 7588] [dbtran 7588 ]

    ***LOG BY0=> ORA-00604: error occurred at recursive SQL level 1

    ORA-01013: user requested cancel of current operation [dbtran#14 @ 7588] [dbtran 7588 ]

    dbtran ERROR LOG (hdl_dbsl_error): DbSl 'INS'

    RSLT: {dbsl=99, tran=1}

    FHDR: {tab='ALCLASTOOL', fcode=130, mode=1, bpb=0, dbcnt=0, crsr=0,

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

    init:p=00000000, init:#=0, wa:p=0X304B8990, wa:#=264}

    dbtran ERROR LOG (hdl_dbsl_error): DbSl 'INS'

    STMT:

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

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

    key:#=3, xfer=0, xin:#=0, row:#=0, upto=0, wa:p=0X304B8990}

    Wed Nov 04 11:27:32 2009

    ABAP Program SAPLSALU .

    Source LSALUU26 Line 306.

    Error Code DBIF_RSQL_SQL_ERROR.

    Module $Id: //bas/700_REL/src/krn/runt/absapsql.c#14 $ SAP.

    Function HandleRsqlErrors Line 786.

    • RABAX: level LEV_RX_STDERR completed.

    • RABAX: level LEV_RX_RFC_ERROR entered.

    • RABAX: level LEV_RX_RFC_ERROR completed.

    • RABAX: level LEV_RX_RFC_CLOSE entered.

    • RABAX: level LEV_RX_RFC_CLOSE completed.

    • RABAX: level LEV_RX_IMC_ERROR entered.

    • RABAX: level LEV_RX_IMC_ERROR completed.

    • RABAX: level LEV_RX_DATASET_CLOSE entered.

    • RABAX: level LEV_RX_DATASET_CLOSE completed.

    • RABAX: level LEV_RX_ERROR_SAVE entered.

    • RABAX: level LEV_RX_ERROR_SAVE completed.

    • RABAX: level LEV_RX_ERROR_TPDA entered.

    • RABAX: level LEV_RX_ERROR_TPDA completed.

    • RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.

    • RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.

    • RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.

    • RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.

    • RABAX: level LEV_RX_END entered.

    • RABAX: level LEV_RX_END completed.

    • RABAX: end no http/smtp

    • RABAX: end RX_BTCHLOG RX_VBLOG

    SQL error in the database when accessing a table..

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 20, 2010 at 07:35 AM

    As this issue only occurred to my DEV system, I will close the issue until it duplicated on my other system. Reason being that DEV is used for a number of testing-and-enhancement where failed enhancement/testing will not be transported to our production environment.

    Thank you.

    Add comment
    10|10000 characters needed characters exceeded