Update Database Design Error: "ORA-00054: resource busy and acquire with NOWAIT specified"
(Doc ID 1329786.1)
Last updated on MARCH 05, 2024
Applies to:
Oracle WebCenter Content - Version 11.1.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
In the Configuration Manager applet, the "Update Database Design" button is enabled, but clicking it produces the following error:
ORA-00054: resource busy and acquire with NOWAIT specified
In addition, when this error occurs, a collection rebuild may be hung and failing with the following errors.
In addition, when this error occurs, a collection rebuild may be hung and failing with the following errors.
The indexing thread may show a lock issue occurring in the database.
Thread Dump of index rebuild work:
index rebuild work" id=224 idx=0x21c tid=136 prio=5 alive, in native, daemon
at jrockit/net/SocketNativeIO.readBytesPinned(Ljava/io/FileDescriptor;[BIII)I(Native Method)
at jrockit/net/SocketNativeIO.socketRead(SocketNativeIO.java:32)
at java/net/SocketInputStream.socketRead0(Ljava/io/FileDescriptor;[BIII)I(SocketInputStream.java)
at java/net/SocketInputStream.read(SocketInputStream.java:129)
at oracle/net/nt/MetricsEnabledInputStream.read(TcpNTAdapter.java:718)
at oracle/net/ns/Packet.receive(Packet.java:295)
at oracle/net/ns/DataPacket.receive(DataPacket.java:106)
at oracle/net/ns/NetInputStream.getNextPacket(NetInputStream.java:317)
at oracle/net/ns/NetInputStream.read(NetInputStream.java:262)
at oracle/net/ns/NetInputStream.read(NetInputStream.java:187)
at oracle/net/ns/NetInputStream.read(NetInputStream.java:104)
at oracle/jdbc/driver/T4CSocketInputStreamWrapper.readNextPacket(T4CSocketInputStreamWrapper.java:126)
at oracle/jdbc/driver/T4CSocketInputStreamWrapper.read(T4CSocketInputStreamWrapper.java:82)
at oracle/jdbc/driver/T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1177)
at oracle/jdbc/driver/T4CMAREngine.unmarshalSB1(T4CMAREngine.java:1153)
at oracle/jdbc/driver/T4CTTIfun.receive(T4CTTIfun.java:312)
at oracle/jdbc/driver/T4CTTIfun.doRPC(T4CTTIfun.java:204)
at oracle/jdbc/driver/T4C8Oall.doOALL(T4C8Oall.java:540)
at oracle/jdbc/driver/T4CStatement.doOall8(T4CStatement.java:202)
at oracle/jdbc/driver/T4CStatement.executeForRows(T4CStatement.java:1074)
at oracle/jdbc/driver/OracleStatement.executeBatch(OracleStatement.java:6281)
^-- Holding lock: oracle/jdbc/driver/T4CConnection@0xc2c69e00[thin lock]
at oracle/jdbc/driver/OracleStatementWrapper.executeBatch(OracleStatementWrapper.java:234)
at weblogic/jdbc/wrapper/Statement_oracle_jdbc_driver_OracleStatementWrapper.executeBatch()[I(Unknown Source)
at intradoc/jdbc/JdbcWorkspace.executeBatch(JdbcWorkspace.java:435)
at intradoc/indexer/IndexerBuildChanges.loadChanges(IndexerBuildChanges.java:515)
at intradoc/indexer/IndexerBuildChanges.buildChanges(IndexerBuildChanges.java:223)
at intradoc/indexer/IndexerBuildChanges.doWork(IndexerBuildChanges.java:167)
at intradoc/indexer/Indexer.doIndexing(Indexer.java:411)
at intradoc/indexer/Indexer.buildIndex(Indexer.java:319)
at intradoc/server/IndexerMonitor.doIndexing(IndexerMonitor.java:1021)
at intradoc/server/IndexerMonitor$4.run(IndexerMonitor.java:841)
at jrockit/vm/RNI.c2java(JJJJJ)V(Native Method)
-- end of trace
The corresponding exception in the UCM daily logs show the following for the hanging collection rebuild:
<Jun 11, 2011 8:10:17 PM PDT> <Error> <oracle.ucm.idccs> <UCM-CS-060009> <Indexing aborted.>
<Jun 11, 2011 8:10:17 PM PDT> <Error> <oracle.ucm.idccs> <UCM-CS-000001> <general exception
intradoc.common.ServiceException: !csIndexerUnableToBuildChanges
at intradoc.indexer.IndexerBuildChanges.buildChanges(IndexerBuildChanges.java:230)
at intradoc.indexer.IndexerBuildChanges.doWork(IndexerBuildChanges.java:167)
at intradoc.indexer.Indexer.doIndexing(Indexer.java:411)
at intradoc.indexer.Indexer.buildIndex(Indexer.java:319)
at intradoc.server.IndexerMonitor.doIndexing(IndexerMonitor.java:1021)
at intradoc.server.IndexerMonitor$4.run(IndexerMonitor.java:842)
Caused By: intradoc.data.DataException: !csDbUnableToExecuteBatch,!$error occurred during batching: ORA-01013: user requested cancel of current operation
at intradoc.jdbc.JdbcWorkspace.handleSQLException(JdbcWorkspace.java:2461)
at intradoc.jdbc.JdbcWorkspace.executeBatch(JdbcWorkspace.java:441)
at intradoc.indexer.IndexerBuildChanges.loadChanges(IndexerBuildChanges.java:515)
at intradoc.indexer.IndexerBuildChanges.buildChanges(IndexerBuildChanges.java:224)
at intradoc.indexer.IndexerBuildChanges.doWork(IndexerBuildChanges.java:167)
at intradoc.indexer.Indexer.doIndexing(Indexer.java:411)
at intradoc.indexer.Indexer.buildIndex(Indexer.java:319)
at intradoc.server.IndexerMonitor.doIndexing(IndexerMonitor.java:1021)
at intradoc.server.IndexerMonitor$4.run(IndexerMonitor.java:842)
Caused By: java.sql.BatchUpdateException: error occurred during batching: ORA-01013: user requested cancel of current operation
at oracle.jdbc.driver.OracleStatement.executeBatch(OracleStatement.java:6346)
at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(OracleStatementWrapper.java:234)
at weblogic.jdbc.wrapper.Statement_oracle_jdbc_driver_OracleStatementWrapper.executeBatch(Unknown Source)
at intradoc.jdbc.JdbcWorkspace.executeBatch(JdbcWorkspace.java:435)
at intradoc.indexer.IndexerBuildChanges.loadChanges(IndexerBuildChanges.java:515)
at intradoc.indexer.IndexerBuildChanges.buildChanges(IndexerBuildChanges.java:223)
at intradoc.indexer.IndexerBuildChanges.doWork(IndexerBuildChanges.java:167)
at intradoc.indexer.Indexer.doIndexing(Indexer.java:411)
at intradoc.indexer.Indexer.buildIndex(Indexer.java:319)
at intradoc.server.IndexerMonitor.doIndexing(IndexerMonitor.java:1021)
at intradoc.server.IndexerMonitor$4.run(IndexerMonitor.java:841)
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 |