My Oracle Support Banner

Siebel Upgrade: Upgrep Process is Failing with Error ORA-00054: Resource Busy and Acquire with NOWAIT Specified or Timeout Expired (Doc ID 1921493.1)

Last updated on APRIL 30, 2018

Applies to:

Siebel CRM - Version 8.2.1 SIA[22220] and later
Information in this document applies to any platform.

Symptoms

Upgrep process is failing during ddlimp process execution, because Oracle database client timed-out and returned error "ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired".

This was noticed in the traces from the upgwiz.log and ddlctl_indx1.log

  During the current upgrade attempt, the Oracle database client timed-out while processing the S_EVT_ACT table, during index creation.
       2014-08-21 16:03:58    Merging   table                   S_EVT_ACT ...  
       ...
       2014-08-21 16:32:40    Creating  index                   S_EVT_ACT_F26 ... 28:41.969m
       ...
   Notice that it was taking longer, and longer to create the indexes, until the error was returned...
       2014-08-21 22:22:20      Creating  index               S_EVT_ACT_F65 ... 32:53.531m

This trace clearly indicates the issue that occurred during the upgrade process:
       2014-08-21 22:22:20 [tp][ODBC Oracle driver][Oracle]ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired


Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.