Gavin,
 
I too faced a similar kind of problem in the past. Probably there are some uncommited data in your database (that are related to this package) or somebody might have closed a sql session manually while executing this package. This will create a lock on some of the tables accessed by this package. So make sure you give an explixit commit before compiling this package and also make sure that nobody closes an sql session manually (by using Ctrl+Alt+Del) while this package is executed.
 
Hope it helps.
 
K. 

 
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 01, 2002 3:03 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: Oracle Performance Tuning steps[Scanned]

Gavin,
 
You need to monitor who is locking the object. v$locked_object could be queried for this info.
 
Long
-----Original Message-----
From: Gavin D'Mello [mailto:[EMAIL PROTECTED]]
Sent: Monday, 1 July 2002 6:03 PM
To: Multiple recipients of list ORACLE-L
Subject: Re: Oracle Performance Tuning steps

Hi,
        I'm working on a pidley sized db ( about 100mb) but sometimes when I try compiling a decent sized package i get a time out error saying the object is locked, while at other times the package compiles on the fly.
        I'm trying to figure out why i get this error randomly. Some suggestions maybe that the compiler is going into a loop in my code which i seriously doubt. Is there any way I can find out what is causing the compile to hang up .... yes i know it says the object is locked but when no one is using the db ( that's when I update) why should the object (i.e. my package) lock ?
any help would be really appreciated,
 
thank you,
 
Gavin
 

Reply via email to