Register Login

ORA-00054: resource busy and acquire with NOWAIT specified

Updated May 18, 2018

SDF/UPL_PERIODIC_EXT_JOB Batchjob Failed

Hello SAP Experts,

The batchjob /SDF/UPL_PERIODIC_EXT_JOB is failing frequently with error ORA-00054.

In the developer trace (dev_w* files), the errors are similar to the following:

C  check2: OCIStmtExecute() failed with -1=OCI_ERROR
C  SQL error 54:
C  *** ERROR => Error 54 in exec_immediate() from oci_execute_stmt(), orpc=0
 [dbsloci.c    12534]
C  {root-id=00314A7B04A1EG6CA911FU9FFA6347}_{conn-id=462434F22S3615F7G10000000IJL1K34}_5
C  *** ERROR => ORA-00054 occurred at SQL stmt (parse error offset=15)
 [dbsloci.c    12535]
C  {root-id=00314A7B04A1EG6CA911FU9FFA6347}_{conn-id=462434F22S3615F7G10000000IJL1K34}_5
C  Dump statement cache (after SQL error):
C  sc_p=7e019f8,no=125,idc_p=(nil),con=0,act=0,slen=24,smax=1024,#vars=0,stmt=86bb3d0,table=
C  TRUNCATE TABLE "COVRES" ;
C     statement (len=24) for table '                              ':
C    TRUNCATE TABLE "COVRES"
C     exec_immediate() -> orc=54, 99=DBSL_ERR_DB
C  head_p=7ffdf07f33b0, cid=0: dbsl err=99=DBSL_ERR_DB-> dbds err=1=DS_SQLERR,dbdsoci.c:1011
C  *** ERROR => ^^ Ds_exec_imm() -> err=1=DS_SQLERR
 [dbdsoci.c    1034]
C  {root-id=00215A9B03A81ED6BA811FE49FFA6257}_{conn-id=587665F33E3605F7E10000000ABD1C23}_5
B  ***LOG BY2=> sql error 54 performing EXE [dbds 536]
B  ***LOG BY0=> ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired [dbds 536]
B  ***LOG BY2=> sql error 54 performing EXE [dbacds 1154]


Comments

  • 10 May 2017 5:26 pm Chandan Singh Parihar Helpful Answer

    Error 'ORA-00054: resource busy and acquire with NOWAIT specified' occurs if an enqueue with NOWAIT is requested by user whereas the enqueue is already being used by another session. Whereas the issue with /SDF/UPL_PERIODIC_EXT_JOB job happens when it runs concurrently, right after, right before another job which modifies the table COVRES.

    You can also follow the below steps to avoid this issue:

    • Please make sure that the job /SDF/UPL_PERIODIC_EXT_JOB is only running once per day.
    • Also please make sure that the job RSCVR_TRIGGER_COLLECT  is not run concurrent to /SDF/UPL_PERIODIC_EXT_JOB or close to midnight
       

×