RE: library cache lock waits
- From: "Gogala, Mladen" <Mladen.Gogala@xxxxxxxx>
- To: "'geraldine_2@xxxxxxxxxxx'" <geraldine_2@xxxxxxxxxxx>, oracle-l@xxxxxxxxxxxxx
- Date: Wed, 17 Nov 2004 12:44:28 -0500
Well, someone is probably using the package. You need to obtain an exclusive
lock
on the library cache area where your package resides in order to compile it.
It is
the same error as "text file busy", sometimes reported by Unix.The solution
is to log inas sysdba "sqlplus "/ as sysdba", run command "startup force
restrict"
and retry. That is a good procedure, especially on 7x24 sites that have to
be
continiously avaiable. It's called "Baldrick instalation method" to honor
Baldrick,
the greatest among helpers, who has always had a cunning plan.
--
Mladen Gogala
A & E TV Network
Ext. 1216
> -----Original Message-----
> From: geraldine_2@xxxxxxxxxxx [mailto:geraldine_2@xxxxxxxxxxx]
> Sent: Wednesday, November 17, 2004 11:58 AM
> To: oracle-l@xxxxxxxxxxxxx
> Subject: library cache lock waits
>
>
> Hi,
> On my test database, I noticed that when I tried to compile a
> package while I'm adding a constraint (alter table add
> constraint) on a huge table XYZ (3GB), the package would not
> compile and waits on library cache lock. The package I'm
> compiling does not referenced table XYZ. The package compiles
> instantaneously after the constraint was added. I don't
> understand why I'm waiting on library cache lock? Anyone? Let
> me know if you need additional information.
>
> DB - 9.2.0.4 on HPUX
> db_cache_size=8GB
> shared_pool_size=500MB
>
> thanks.
>
> geraldine
> --
> //www.freelists.org/webpage/oracle-l
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
