ORA-00054: resource busy and acquire with NOWAIT specified

We are frequently getting ORA-00054: resource busy and acquire with NOWAIT specified error in production database for a application user group. Production database is oracle 10g R 10.2.0.5.0 on sun solaris. The app user group is telling that the code is not changed from many years. They wants this to be resolved on h.priority. The tables which are getting this error has clob fields. I rebuilded indexes in QA environment & they ran it again they are getting the same error.
I asked to see select for update nowait clause's carefully. They said everything is fine. Please let me know any solution if any one is getting this kind of error. Thanks.

Has anything changed compared to previously when these errors didn't happen?
Not necessarily application code but
- Database version
- patches
- indexes
- data volumes
- number of clients
etc, etc
What led you to rebuild the indexes?
As for suggested solutions, they completely depend on the specifics of your situation.
Do you know that the SELECT FOR UPDATE is raising the ORA-00054?
Something else has the relevant resource locked in a non-shareable way - you need to find out what.
It sounds like the most likely candidate is another session that has issued a SELECT FOR UPDATE and locked some of the same row(s).
It's good that you can reproduce on QA rather than just production.
Maybe you can manually issue the failing SELECT FOR UPDATE statement but with WAIT rather than NOWAIT and see if that helps you figure out blockers, etc.
Further analysis required at your end.

Similar Messages

How to find process causing "ORA-00054: resource busy and acquire with NOWAIT specified"

Hello there,
ENV: Oracle 10gR2 64bit on ASM, RHEL 64bit
Application team has reported "ORA-00054: resource busy and acquire with NOWAIT specified" during the batch process in production env. This is happening for last couple of days. When this batch process is restarted in the morning, this error does not appear.
I understand that this error is raised when one process tries to eecute some DDL on a table while another process is performing DML (or hasn't issued COMMIT/ROLLBACK after the DDL).
Since this error is occurring at night (around 3:00am) during the batch process, is there a way to find out on table/object is contention happening OR which process is causing this error? The batch process cannot be modified to add debug messages because it is in Production.
Please advise.
Best regards

user130038 wrote:
Hello there,
ENV: Oracle 10gR2 64bit on ASM, RHEL 64bit
Application team has reported "ORA-00054: resource busy and acquire with NOWAIT specified" during the batch process in production env. This is happening for last couple of days. When this batch process is restarted in the morning, this error does not appear.
I understand that this error is raised when one process tries to eecute some DDL on a table while another process is performing DML (or hasn't issued COMMIT/ROLLBACK after the DDL).
Since this error is occurring at night (around 3:00am) during the batch process, is there a way to find out on table/object is contention happening OR which process is causing this error? The batch process cannot be modified to add debug messages because it is in Production.
Please advise.
Best regards
>The batch process cannot be modified to add debug messages because it is in Production.
I suspect more than one job is running concurrently against the DB; otherwise not error would occur.
Of course the batch process CAN be modified, but some PHB has decided to eliminate that option.
The Oracle database is at the mercy of the application code.
If the application code is poorly instrumented, then live with what exists or improved the code to facilitate isolating the bug.
You could delay the start of one of the jobs & then hope the error no longer occurs.

Sqlldr direct got ORA-00054: resource busy and acquire with NOWAIT specifie

I have multi-threaded application to kick off multiple sqlldr sessions that will try to insert 200K rows of data into same table from each session. I am using direct path with parallel enabled. The target table has no index, not even a PK, but I got this ORA-00054 error.
Sample control file template:
OPTIONS (SKIP=1, DIRECT=TRUE, PARALLEL=TRUE, SILENT=ALL, MULTITHREADING=TRUE, SKIP_INDEX_MAINTENANCE=TRUE, SKIP_UNUSABLE_INDEXES=TRUE)
UNRECOVERABLE
LOAD DATA
INFILE '&DATA_FILE_NAME'
BADFILE '&BAD_FILE_NAME'
DISCARDFILE '&DISCARD_FILE_NAME'
INTO TABLE TARGET_TABLE
APPEND
FIELDS TERMINATED BY "," OPTIONALLY ENCLOSED BY '"' TRAILING NULLCOLS
( SESSION_ID CONSTANT &SESSION_ID,
FIELD00,
FIELD01,
FIELD02,
FIELD03,
FIELD04,
FIELD05,
FIELD06
The definition of TARGET_TABLE:
CREATE TABLE TARGET_TABLE
SESSION_ID NUMBER(12),
FIELD00 VARCHAR2(4000 BYTE),
FIELD01 VARCHAR2(4000 BYTE),
FIELD02 VARCHAR2(4000 BYTE),
FIELD03 VARCHAR2(4000 BYTE),
FIELD04 VARCHAR2(4000 BYTE),
FIELD05 VARCHAR2(4000 BYTE),
FIELD06 VARCHAR2(4000 BYTE),
FIELD07 VARCHAR2(4000 BYTE),
FIELD08 VARCHAR2(4000 BYTE),
FIELD09 VARCHAR2(4000 BYTE),
FIELD10 VARCHAR2(4000 BYTE),
FIELD11 VARCHAR2(4000 BYTE)
I want to WAIT if there's any race. How can I make it WAIT? Most of the time, WAIT should be the default, but somehow, it acts differently here.
Any help will be highly appreciated.

Looking at the same manual, you can see here that you need exclusive access to the table:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14215/ldr_modes.htm#sthref1449
And here, you can see that if other DML is happening on a table, Oracle says you need to do conventional path load:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14215/ldr_modes.htm#sthref1432
In the case of parallelization, yes, you must set parallel=true. This allows SQL*Loader to manage the parallel inserts. If you were to try to do multiple, concurrent direct path loads yourself by running multiple instances of SQL*Loader, you'd run into the same TM enqueue problem.
The question as to why the TM enqueue is taken in exclusive mode, has to do with how direct path load works. Oracle loads data into previously unformatted, completely empty data blocks from above the HWM. When the load is complete, the HWM is adjusted, and the data is available. Well, Oracle can't allow for multiple concurrent direct loads, all allocating space from above the HWM, and all messing w/ the HWM. This would cause a bit of a problem. And really, you don't want non-direct load DML going on either. So, Oracle disallows it, by taking the TM enqueue in exclusive mode. (Normal DML, non-direct load, takes the TM enqueue in a sharable mode, allowing for other concurrent DML.)
Hope that's clear,
-Mark
Message was edited by:
Mark J. Bobak

Resource busy and acquire with NOWAIT exception

Dears frnds,
I have faced this exception many times.But unable find out the Root cause of this exception.If anyone suggest why this exception arise,it will help to avoid this
Exception
java.sql.SQLException: ORA-00054: resource busy and acquire with NOWAIT specified ORA-06512: a

It's somewhat hard to offer suggestions without understanding what the procedure is doing.
Normally, an INSERT or an UPDATE will block indefinitely waiting to lock the row(s) in question. The error you are getting generally requires that you are doing an explicit SELECT ... FOR UPDATE NOWAIT or DDL. Doing DDL in an OLTP application is a bad idea, so you'd want to figure out what problem you're trying to solve and find a way to solve the problem without DDL. If you are doing an explicit SELECT ... FOR UPDATE NOWAIT, you'll need to understand why NOWAIT is being specified and figure out whether you should be handling the error. If someone added a SELECT ... FOR UPDATE NOWAIT because they don't want users to block waiting for access to a row, it may be perfectly reasonable to return this exception.
Justin

Resource Busy and acqire with NOWAIT specified

I could not do any operation(select,insert,alter....) of a specified table.
always give following error
ORA-00054:Resource busy and acqire with NOWAIT specified.
Give the way out.

Hi,
>>ORA-00054:Resource busy and acqire with NOWAIT specified.
You can try to find out which session is holding the lock ... and depending of the situation, kill the session that is holding the lock. Just kill a session as last case.
SESSION 1
C:\>sqlplus legatti/pass
SQL*Plus: Release 10.1.0.2.0 - Production on Tue Jan 22 08:40:05 2008
Copyright (c) 1982, 2004, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> create table t1 (id number);
Table created.
SQL> insert into t1 values (1);
1 row created.
SESSION 2
C:\>sqlplus legatti/pass
SQL*Plus: Release 10.1.0.2.0 - Production on Tue Jan 22 08:40:43 2008
Copyright (c) 1982, 2004, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> truncate table t1;
truncate table t1
ERROR at line 1:
ORA-00054: resource busy and acquire with NOWAIT specified
TRY TO FIND OUT THE SOURCE OF THE LOCK
C:\>sqlplus system/pass
SQL> select S.osuser,
2    O.object_name,
3    O.object_type,
4    S.sid,
5    S.serial#,
6    S.username,
7    L.type,
8    S.machine,
9    Decode( L.lmode,
10            0, 'None',
11            1, 'Null',
12            2, 'Row Share',
13            3, 'Row Exclu',
14            4, 'Share',
15            5, 'Sh Row Ex',
16            6, 'Exclusive',
17            'Null' ) "LOCK_MODE"
18 from dba_objects O,
19 v$lock L,
20 v$session S
21 where L.id1 = + O.object_id
22    and S.sid = L.sid
23    and S.username Is Not Null;
OSUSER    OBJECT_NAME     OBJECT_TYPE                SID    SERIAL# USERNAME       TY MACHINE   LOCK_MODE
legatti   T1              TABLE                       255 24461 LEGATTI       TM DOM\M001 Row Exclu
SQL> alter system kill session '255,24461';
System altered.
BACK TO SESSION 1
SQL> select sysdate from dual;
select sysdate from dual
ERROR at line 1:
ORA-00028: your session has been killed
BACK TO SESSION 2
SQL> truncate table t1;
Table truncated.Cheers
Legatti

Can't drop text index (ORA-00054: resource busy) - causes?

Thanks, you were right! It works now, but I have another issue. I only added about 75 MB of PDFs (20 files) into my table, and indexed it. Indexing took about 4 minutes. But now, whenever I try to drop the index, I get this error:
ORA-00054: resource busy and acquire with NOWAIT specified
I tried waiting an hour, and it still gives me the error - it really shouldn't be doing anything. Would a memory or storage space issue cause this? I'd appreciate any help you could give. Thanks.

Try drop index <name> force

"ORA-00054 Resource Busy Error" when running SQL*Loader in Parallel

Hi all,
Please help me on an issue. We are using Datastage which uses sql*loader to load data into an Oracle Table. SQL*Loader invokes 8 parallel sessions for insert on the table. When doing so, we are facing the following error intermittently:
SQL*Loader-951: Error calling once/load initialization
ORA-00604: error occurred at recursive SQL level 1
ORA-00054: resource busy and acquire with NOWAIT specifiedSince the control file is generated automatically by datastage, we cannot modify/change the options and test. Control File for the same is:
OPTIONS(DIRECT=TRUE, PARALLEL=TRUE, SKIP_INDEX_MAINTENANCE=YES)
LOAD DATA INFILE 'ora.2958.371909.fifo.1' "FIX 1358"
APPEND INTO TABLE X
x1 POSITION(1:8) DECIMAL(15,0) NULLIF (1:8) = X'0000000000000000',
x2 POSITION(9:16) DECIMAL(15,0) NULLIF (9:16) = X'0000000000000000',
x3 POSITION(17:20) INTEGER NULLIF (17:20) = X'80000000',
IDNTFR POSITION(21:40)   NULLIF (21:40) = BLANKS,
IDNTFR_DTLS POSITION(41:240)   NULLIF (41:240) = BLANKS,
FROM_DATE POSITION(241:259) DATE "YYYY-MM-DD HH24:MI:SS" NULLIF (241:259) = BLANKS,
TO_DATE POSITION(260:278) DATE "YYYY-MM-DD HH24:MI:SS" NULLIF (260:278) = BLANKS,
DATA_SOURCE_LKPCD POSITION(279:283)   NULLIF (279:283) = BLANKS,
EFFECTIVE_DATE POSITION(284:302) DATE "YYYY-MM-DD HH24:MI:SS" NULLIF (284:302) = BLANKS,
REMARK POSITION(303:1302)   NULLIF (303:1302) = BLANKS,
OPRTNL_FLAG POSITION(1303:1303)   NULLIF (1303:1303) = BLANKS,
CREATED_BY POSITION(1304:1311) DECIMAL(15,0) NULLIF (1304:1311) = X'0000000000000000',
CREATED_DATE POSITION(1312:1330) DATE "YYYY-MM-DD HH24:MI:SS" NULLIF (1312:1330) = BLANKS,
MODIFIED_BY POSITION(1331:1338) DECIMAL(15,0) NULLIF (1331:1338) = X'0000000000000000',
MODIFIED_DATE POSITION(1339:1357) DATE "YYYY-MM-DD HH24:MI:SS" NULLIF (1339:1357) = BLANKS
)- it occurs intermittently. When this job runs, no one will be accessing the database or the tables.
- When we do not run in parallel, then we are not facing the error but it is very slow (obviously).

Just in case, I am also attaching the Datastage Logs:
   Item #: 466
   Event ID: 1467
   Timestamp: 2009-06-02 23:03:19
   Type: Info
   User Name: dsadm
   Message: main_program: APT configuration file: /clu01/datastage/Ascential/DataStage/Configurations/default.apt
     node "node1"
          fastname "machine_name"
          pools ""
          resource disk "/clu01/datastage/Ascential/DataStage/Datasets" {pools ""}
          resource scratchdisk "/clu01/datastage/Ascential/DataStage/Scratch" {pools ""}
     node "node2"
          fastname "machine_name"
          pools ""
          resource disk "/clu01/datastage/Ascential/DataStage/Datasets" {pools ""}
          resource scratchdisk "/clu01/datastage/Ascential/DataStage/Scratch" {pools ""}
     node "node3"
          fastname "machine_name"
          pools ""
          resource disk "/clu01/datastage/Ascential/DataStage/Datasets" {pools ""}
          resource scratchdisk "/clu01/datastage/Ascential/DataStage/Scratch" {pools ""}
     node "node4"
          fastname "machine_name"
          pools ""
          resource disk "/clu01/datastage/Ascential/DataStage/Datasets" {pools ""}
          resource scratchdisk "/clu01/datastage/Ascential/DataStage/Scratch" {pools ""}
      node "node5"
          fastname "machine_name"
          pools ""
          resource disk "/clu01/datastage/Ascential/DataStage/Datasets" {pools ""}
          resource scratchdisk "/clu01/datastage/Ascential/DataStage/Scratch" {pools ""}
     node "node6"
          fastname "machine_name"
          pools ""
          resource disk "/clu01/datastage/Ascential/DataStage/Datasets" {pools ""}
          resource scratchdisk "/clu01/datastage/Ascential/DataStage/Scratch" {pools ""}
    node "node7"
          fastname "machine_name"
          pools ""
          resource disk "/clu01/datastage/Ascential/DataStage/Datasets" {pools ""}
          resource scratchdisk "/clu01/datastage/Ascential/DataStage/Scratch" {pools ""}
   node "node8"
          fastname "machine_name"
          pools ""
          resource disk "/clu01/datastage/Ascential/DataStage/Datasets" {pools ""}
          resource scratchdisk "/clu01/datastage/Ascential/DataStage/Scratch" {pools ""}
   Item #: 467
   Event ID: 1468
   Timestamp: 2009-06-02 23:03:20
   Type: Warning
   User Name: dsadm
   Message: main_program: Warning: the value of the PWD environment variable (/clu01/datastage/Ascential/DataStage/DSEngine) does not appear to be a synonym for the current working directory (/clu01/datastage/Ascential/DataStage/Projects/Production). The current working directory will be used, but if your ORCHESTRATE job does not start up correctly, you should set your PWD environment variable to a value that will work on all nodes of your system.
   Item #: 468
   Event ID: 1469
   Timestamp: 2009-06-02 23:03:32
   Type: Warning
   User Name: dsadm
   Message: Lkp_1: Input dataset 1 has a partitioning method other than entire specified; disabling memory sharing.
   Item #: 469
   Event ID: 1470
   Timestamp: 2009-06-02 23:04:22
   Type: Warning
   User Name: dsadm
   Message: Lkp_2: Input dataset 1 has a partitioning method other than entire specified; disabling memory sharing.
   Item #: 470
   Event ID: 1471
   Timestamp: 2009-06-02 23:04:30
   Type: Warning
   User Name: dsadm
   Message: Xfmer1: Input dataset 0 has a partitioning method other than entire specified; disabling memory sharing.
   Item #: 471
   Event ID: 1472
   Timestamp: 2009-06-02 23:04:30
   Type: Warning
   User Name: dsadm
   Message: Lkp_2: When checking operator: Operator of type "APT_LUTProcessOp": will partition despite the
preserve-partitioning flag on the data set on input port 0.
   Item #: 472
   Event ID: 1473
   Timestamp: 2009-06-02 23:04:30
   Type: Warning
   User Name: dsadm
   Message: SKey_1: When checking operator: A sequential operator cannot preserve the partitioning
of the parallel data set on input port 0.
   Item #: 473
   Event ID: 1474
   Timestamp: 2009-06-02 23:04:30
   Type: Warning
   User Name: dsadm
   Message: SKey_2: When checking operator: Operator of type "APT_GeneratorOperator": will partition despite the
preserve-partitioning flag on the data set on input port 0.
   Item #: 474
   Event ID: 1475
   Timestamp: 2009-06-02 23:04:30
   Type: Warning
   User Name: dsadm
   Message: buffer(1): When checking operator: Operator of type "APT_BufferOperator": will partition despite the
preserve-partitioning flag on the data set on input port 0.
   Item #: 475
   Event ID: 1476
   Timestamp: 2009-06-02 23:04:30
   Type: Info
   User Name: dsadm
   Message: Tgt_member: When checking operator: The -index rebuild option has been included; in order for this option to be
applicable and to work properly, the environment variable APT_ORACLE_LOAD_OPTIONS should contain the options
DIRECT and PARALLEL set to TRUE, and the option SKIP_INDEX_MAINTENANCE set to YES;
this variable has been set by the user to `OPTIONS(DIRECT=TRUE, PARALLEL=TRUE, SKIP_INDEX_MAINTENANCE=YES)'.
   Item #: 476
   Event ID: 1477
   Timestamp: 2009-06-02 23:04:35
   Type: Info
   User Name: dsadm
   Message: Tgt_member_idtfr: When checking operator: The -index rebuild option has been included; in order for this option to be
applicable and to work properly, the environment variable APT_ORACLE_LOAD_OPTIONS should contain the options
DIRECT and PARALLEL set to TRUE, and the option SKIP_INDEX_MAINTENANCE set to YES;
this variable has been set by the user to `OPTIONS(DIRECT=TRUE, PARALLEL=TRUE, SKIP_INDEX_MAINTENANCE=YES)'.
   Item #: 477
   Event ID: 1478
   Timestamp: 2009-06-02 23:04:41
   Type: Warning
   User Name: dsadm
   Message: Lkp_2,6: Ignoring duplicate entry at table record 1; no further warnings will be issued for this table
   Item #: 478
   Event ID: 1479
   Timestamp: 2009-06-02 23:04:41
   Type: Warning
   User Name: dsadm
   Message: Tgt_member_idtfr,0: SQL*Loader-951: Error calling once/load initialization
   Item #: 479
   Event ID: 1480
   Timestamp: 2009-06-02 23:04:41
   Type: Warning
   User Name: dsadm
   Message: Tgt_member_idtfr,0: ORA-00604: error occurred at recursive SQL level 1
   Item #: 480
   Event ID: 1481
   Timestamp: 2009-06-02 23:04:41
   Type: Warning
   User Name: dsadm
   Message: Tgt_member_idtfr,0: ORA-00054: resource busy and acquire with NOWAIT specified
   Item #: 481
   Event ID: 1482
   Timestamp: 2009-06-02 23:04:41
   Type: Warning
   User Name: dsadm
   Message: Tgt_member_idtfr,6: SQL*Loader-951: Error calling once/load initialization
   Item #: 482
   Event ID: 1483
   Timestamp: 2009-06-02 23:04:41
   Type: Warning
   User Name: dsadm
   Message: Tgt_member_idtfr,6: ORA-00604: error occurred at recursive SQL level 1
   Item #: 483
   Event ID: 1484
   Timestamp: 2009-06-02 23:04:41
   Type: Warning
   User Name: dsadm
   Message: Tgt_member_idtfr,6: ORA-00054: resource busy and acquire with NOWAIT specified
   Item #: 484
   Event ID: 1485
   Timestamp: 2009-06-02 23:04:41
   Type: Fatal
   User Name: dsadm
   Message: Tgt_member_idtfr,6: The call to sqlldr failed; the return code = 256;
please see the loader logfile: /clu01/datastage/Ascential/DataStage/Scratch/ora.23335.478434.6.log for details.
   Item #: 485
   Event ID: 1486
   Timestamp: 2009-06-02 23:04:41
   Type: Fatal
   User Name: dsadm
   Message: Tgt_member_idtfr,0: The call to sqlldr failed; the return code = 256;
please see the loader logfile: /clu01/datastage/Ascential/DataStage/Scratch/ora.23335.478434.0.log for details.

Adding default constraint causes ORA-00054: resource busy

Hi,
i ran a script and got error below. Why am i getting error "ORA-00054: resource busy" when adding a default constraint to table? On other evironments such error didn't occure, only in particualr special one the error occured.
Is it possible that table has too much traffic/locks i nthat environment? How can i rewrite my script?
Should i instal lthe script in OFFLINE mode?
In Oracle 11g, Linux Os i runned such script (in Online mode, system not offline):
ALTER TABLE Casino.Physicaltables ADD WinnerListEnabled NUMBER(1);
COMMENT ON COLUMN Casino.Physicaltables.WinnerListEnabled IS '<BOOLEAN> Defines if winner list is turned on or off.';
ALTER TABLE Casino.Physicaltables MODIFY WinnerListEnabled DEFAULT 0;
ALTER TABLE Casino.Physicaltables MODIFY (WinnerListEnabled CONSTRAINT NC_Pts_WinnerListEnabled NOT NULL NOVALIDATE);
UPDATE Casino.Physicaltables SET WinnerListEnabled = 0 WHERE WinnerListEnabled IS NULL;
COMMIT;
ALTER TABLE Casino.Physicaltables MODIFY CONSTRAINT NC_Pts_WinnerListEnabled ENABLE VALIDATE;And output was such:
\\dserver\Live\release\12.6\0.10\sql\live_sql_12.4.0.5_to_12.6.0.10.zip
Elapsed: 00:00:00.09
ALTER TABLE Casino.Physicaltables MODIFY WinnerListEnabled DEFAULT 0
ERROR at line 1:
ORA-00054: resource busy and acquire with NOWAIT specified

Any DDL will cause an exclusive lock on the corresponding record in the dictionary. The error message indicates the object is in use by someone else.
Solutions:
1 Apply the code in a maintenance window when no one is there. DDL should NOT be run in a live system during production.
2 Put the database in restricted mode, provided no one has the restricted session privilege
3 Make sure your application uses a non-default service (ie service <> database name) and shut down that service using srvctl and/or dbms_service.
There is no such thing as 'OFFLINE mode'
Sybrand Bakker
Senior Oracle DBA

Acquire with NOWAIT error and TRUNCATE command

Why is it that, sometimes when i try to TRUNCATE a table. I would get
ORA-00054: resource busy and acquire with NOWAIT specified error. And i would be able to DELETE the same table using DELETE FROM table_name;
Message was edited by:
C. Boutet

Because some other session has a lock on that table, you can delete it because you are in fact deleting your read consistent view of the table. See this test case:
In session 1:
YAS@10G>create table t as select * from dual;
Table created.
YAS@10G>insert into t values(2);
1 row created.In session 2:
YAS@10G>truncate table t;
truncate table t
ERROR at line 1:
ORA-00054: resource busy and acquire with NOWAIT specified
YAS@10G>delete from t;
1 row deleted.
YAS@10G>commit;
Commit complete.
YAS@10G>select * from t;
no rows selectedI was not able to truncate it because session 1 inserted a row and it is holding a lock on the table. I could delete from the table because the rows I want to delete are not locked.
TRUNCATE is DDL and it needs an exclusive lock on the table. Session 1 is holding a shared lock on the table which does not permit the other session to get an exclusive lock.

Disk Utility reports "resource busy" and can't create an disk image

HI,
Just succesfully updated to Mountain Lion on my MBA and iMac. No problems. A very smooth proces.
But, on my iMac the Disk Utility are not able to create new images at all! I'm not sure if this relates directly to the update, as
DU works fine on the MBA.
I have tried to create a simple disk image from a folder, sparse bundle disk images and sparse disk images - with and without encryption.
They al gave this output from DU: "Unable to create "MYDiskImage.sparsebundle." (Resource busy).
I understand from other postings on the web that others have experienced the same message from time to time, but have not seen a fix for it anywhere.
I can see the "disk iamge" in the DU window (left pane) but are not able to locate it with Finder or on the computer anywhere, but are even able to "repair the
disk image with DU, but then there is actually no disk image when trying to locate it. Very strange.
Any help?
The DU log has this info:
1. Creating a sparsebundle
2012-08-01 07:46:16 +0200: Creating Image “MyDiskImage.sparsebundle”
2012-08-01 07:46:16 +0200: Initializing…
2012-08-01 07:46:16 +0200: Creating…
2012-08-01 07:46:27 +0200: Formatting…
2012-08-01 07:46:28 +0200: Finishing…
2012-08-01 07:46:29 +0200: Unable to create “MyDiskImage.sparsebundle.” (Resource busy)
2012-08-01 07:46:29 +0200:
2012-08-01 07:47:01 +0200: Verify and Repair volume “disk3s2”
2012-08-01 07:47:01 +0200: Starting repair tool:
2012-08-01 07:47:01 +0200: Checking file system2012-08-01 07:47:01 +0200: Checking Journaled HFS Plus volume.
2. Creating a disk image from a folder
2012-08-01 07:59:10 +0200: Creating Image “Parallels køb juli 2012.dmg”
2012-08-01 07:59:10 +0200: Initializing…
2012-08-01 07:59:11 +0200: Creating…
2012-08-01 07:59:20 +0200: Finishing…
2012-08-01 07:59:21 +0200: Unable to create “Parallels køb juli 2012.” (Resource busy)
2012-08-01 07:59:21 +0200:

Hi Darth,
Thanks for the suggestion. Somehow I managed to solve the issue (the question was posted in July), I think I restarted the computer a couple of times, but it's interesting that you mention Drive Genius and Drive Pulse, as I also had that app running!
Maybe Drive Pulse was also turned of here in my process and helped to solve the issue.
Anyhow, thanks.

Skype for business and integration with my pabx

how much would it cost for me to get skype-for-business for 500 users ? who can assist me with the information?

how much would it cost for me to get skype-for-business for 500 users ? who can assist me with the information?

I have windows vista home premium phot shop elements 6 recent repairs deleted program and even with now I can not even find a p. elements that can be used with w.vista..... HELP

Any ideas??? Have windows vista home premuim and can not find a phot shop that will work with it.

You can download a free trial version for PSE 10, 11 or 12 from this link:
<Download Photoshop Elements products | 13, 12, 11, 10>
You can use this trial version for 30 days after which you will need to buy a boxed version from Amazon and use the serial number from the box to activate your trial version.
If, however, you complete your project in the next 30 days then you don't need to buy anything. Money saved for something else.
Good luck.

FOR UPDATE NOWAIT and ora-00054

Dears
my scenario is :-
In a busy transaction system,in a procedure i am making first lock the transaction with FOR UPDATE NOWAIT in a query.
Then I am checking some status and then i am doing the transaction.
It was ok but sometimes i am facing "ORA-00054: Resource Busy and Acquire with NOWAIT Specified" this error.
so, now how can i overcome this. or any alternative way please?
Regards
Halim
Edited by: Abdul Halim on Mar 1, 2011 1:11 PM

Abdul Halim wrote:
Dears
my scenario is :-
In a busy transaction system,in a procedure i am making first lock the transaction with FOR UPDATE NOWAIT in a query.
Then I am checking some status and then i am doing the transaction.
It was ok but sometimes i am facing "ORA-00054: Resource Busy and Acquire with NOWAIT Specified" this error.
so, now how can i overcome this. or any alternative way please?
Regards
Halim
Edited by: Abdul Halim on Mar 1, 2011 1:11 PMThis is normal behavior.So when you use SELECT FOR UPDATE statement in this case oracle will exclusive row level lock according records.And if you use NOWAIT clause in this case oracle will not wait if these records/table locked by another users.In additionally you can use without NOWAIT clause then other users will wait(without errors) also you can set limit this waiting using DISTRIBUTED_LOCK_TIMEOUT initialization parameter.

JBO-26030 and ORA-00054 error when updating a certain row

I have a page that saves data when you leave a cell in a table. Everything seems to work fine, but when you get to some cells the JBO-26030 error pops up and then no matter what you do you can't ever save anything on that cell. You can close everything down and reopen and change other cells, but when you go back to that cell the error message always pops up. I think it's mainly happening on the cell that is a drop down with 3 values (P, F, and NT). P is the value and key for the drop down.
Then when I go into the database through Toad I try to change the value just so see what happens and that's when I get the ORA-00054: resource busy and acquire with NOWAIT specified error. This again only happens when editing that row.
Any help is appreciated...Thanks!
Edited by: user10942416 on Aug 6, 2009 6:16 AM

This error is caused when the block property 'DML returning values' equals YES. This property was introduced as of forms 6. What does it do ? As per the on-line help of Forms, "A database update or insert action may initiate server-side triggers that cause alterations or additional changes in the data. In Release 6, when using an Oracle8 database server, Forms uses the DML Returning clause to immediately bring back any such changes. When this property is set to Yes, Forms will automatically update the client-side version of the data, and the user will not need to re-query the database to obtain the changed values". When this property is switched to yes the generated insert/update statement will contain the 'returning clause' and this clause is causing the error.
As far as I have tested, the only way at present, to get rid of this error is to set 'DML returing values' to NO. So, not to use this functionality.
See also:
http://support.oracle.co.uk/metalink/plsql/ml2_documents.showFrameDocument?p_database_id=NOT&p_id=143395.1
Please respond if this solution works for you.
Greets,
Guido Zeelen

Problem with truncate table in procedure ora -00054

hi do anybody know where is mistake ???
the procedure has problem with truncate table
ora - 00054: resource busy and acquire with NOWAIT specified
ora - 06512 at "POVAPSYS.HMAN_P_REFRESH", line 6
ora - 06512 at "POVAPSYS.POVAPSYS", line 6
ora - 06512 at line 1
this is my procedure....
AS
BEGIN
execute immediate 'TRUNCATE TABLE hman_t_max';
INSERT INTO hman_t_max SELECT * FROM hman_v_max;
COMMIT;
END;

2.MAKE SURE THAT OTHER THAN YOU ANYBODY IS TRYING TO
COMPILE AND RUN THE PROCEDUREShould he make sure that anybody is running the procedure?
3.MAKE SURE THAT ANY PARALLEL QUERY IS RUNNING IN THE
SERVER SIDE,THATS KEEPS THE RESOURCE BUSYShould he make sure any parallel query is running in the server side to keep the resource busy?
Gita,
I COULDN'T RESIST HAVING ONE SUGGESTION FOR YOU. Please look at the impact of your English in the reply before posting. Check if that sends reverse message!
Cheers
Sarma.

ORA-00054: resource busy and acquire with NOWAIT specified

Similar Messages

Maybe you are looking for