ORA-00054
| Follow up by mail | Click here |
| Subject: | ORA-00054 |
| Author: | Balaji M, India |
| Date: | Feb 08, 2010, 207 days ago |
| Os info: | unix |
| Oracle info: | 10.2.0.4.0 |
| Message: | Hi,
I see below error in alert log file. I face this error when i execute schedule job in Tivoli. ORA-12012: error on auto execute of job 18294 ORA-20104: ORA-00054: resource busy and acquire with NOWAIT specified when gathering stats. ORA-06512: at "DEMO.UTL", line 100 Can someone suggest me how to fix the issue. Regards, |
| Goto: | Reply - Top of page |
| Subject: | Re: ORA-00054 |
| Author: | Maarten Hereijgers, Belgium |
| Date: | Feb 08, 2010, 207 days ago |
| Score: | |
| Message: | The resource is busy, meaning that there is a lock somewhere on the objects your process is trying to lock. You'll have to wait for the locks to be released.
V$LOCKED_OBJECT gives you information about locks. You can join that view with V$SESSION and DBA_OBJECTS to get more information. |
| Your rating?: | This reply is Good Excellent |
| Goto: | Reply - Top of page |
| Subject: | Re: ORA-00054 |
| Author: | Balaji M, India |
| Date: | Feb 08, 2010, 207 days ago |
| Message: | Thanks Maarten.
I see lots of other jobs running simultaneously at that time when i execute my job, also i guess some other sessions using the same object which i am using for executing the object as job in Tivoli. In this scenario , can i kill the other sessions which is using the same object ? so that my job would run successfully. Please advice. Regards, |
| Your rating?: | This reply is Good Excellent |
| Goto: | Reply - Top of page |
| Subject: | Re: ORA-00054 |
| Author: | Maarten Hereijgers, Belgium |
| Date: | Feb 08, 2010, 207 days ago |
| Message: | Short answer: if you have the privileges, than you can kill the jobs.
Long answer: Hold your horses! Are you sure that is a good idea? My first concern is that killing jobs might not resolve the error permanently. The second concern I have is that those other jobs might be as important as yours or even more important. Some jobs might even not be blocking you at all. And is your job that important that it needs all objects right now? Think this one over before you act: consult the people that have created the jobs and evaluate the different scenarios. |
| Your rating?: | This reply is Good Excellent |
| Goto: | Reply - Top of page |
| Subject: | Re: ORA-00054 |
| Author: | Balaji M, India |
| Date: | Feb 08, 2010, 207 days ago |
| Message: |
Ok i agree with you. What if other jobs are important? and developers wanted them also to run along with the job im executing. Regards, |
| Your rating?: | This reply is Good Excellent |
| Goto: | Reply - Top of page |
| Subject: | Re: ORA-00054 |
| Author: | Balaji M, India |
| Date: | Feb 08, 2010, 207 days ago |
| Message: |
I just want to know what will be the other solution without killing other jobs ? Thanks |
| Your rating?: | This reply is Good Excellent |
| Goto: | Reply - Top of page |
| Subject: | Re: ORA-00054 |
| Author: | Maarten Hereijgers, Belgium |
| Date: | Feb 08, 2010, 207 days ago |
| Score: | |
| Message: | The other solution is to wait until the locks are released. That's the reason why most of the maintenance jobs are scheduled outside office hours.
You could also check the jobs and see whether all locks are truly necessary. Perhaps there's a job that locks tables way too soon. |
| Your rating?: | This reply is Good Excellent |
| Goto: | Reply - Top of page |