'Resouce busy' means you are attempting an operation that requires exclusive access to the table and you don't have it. Something like a 'truncate' for example. Your assertation that 'no one is working with the database' cannot be true. Perhaps this other person... is you? Do you have jobs or process that terminate abnormally before this error starts?
Work with your DBA, they can trace the processes, check for blocking locks or all of that fun stuff to figure out what process is causing you grief.
-craig
"You can never have too many knives" -- Logan Nine Fingers
Chulet is right. One process might require exclusive access to the table (Might be for truncate table) but another process might have hold the table for inserting record. So the first process waits for the table for the specific period, if it didn't get the acess then it will result to your error. Still if you fell it's not right, Don't run any jobs from DS and run the job which gives error alone for 'N' times. Let us know what the result is.
Good Thought.
I am infact 'Truncating the tables'.
However, these effects are committed before I restart my ETL job.
Can 'COMMIT' command be insufficient to release the locks on those tables ???
As noted, truncates are not committed and by the same token they cannot be rolled back. Once done, it's done and there ain't no going back. Now, if you are talking about other people issuing a 'commit' on their changes then yes, that will release any of those pesky locks that get in the way of things like a TRUNCATE. A rollback will do the same.
-craig
"You can never have too many knives" -- Logan Nine Fingers
