Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Problem while compiling packages
Also, if you have the database set to archive mode, make sure that your
initxxx.ora has "log_archive_start = true" or that you have started archive
logging manually with "ARCHIVE LOG START" - otherwise once you fill the
online redo logs the database will just hang because it expects to be able
to archive the filled redo logs.
Ken
Sybrand Bakker wrote:
> > Hi Venkatesh > > If the problem seems to be related to archivelog, you should look in your > alert<sid>.log for any 'cannot allocate log archival required' messages. If > your online redo logs are small ( < 5M), and you have a burst of changes, > you will fill ALL your archive logs in one sweep, and the database will just > hang! until it did archive those files. In noarchivelog they will simply be > overwritten. > I have seen frequent problems when packages are mutual dependent of each > other. I have never been able to proof dead-lock on the data dictionary, > though that is the most likely explanation. > There is a package named DBMS_APPLICATION_INFO, which is very useful to see > what is happening. It's output will appear in the client_info column of > v$session. This package is Oracle-provided and it's source should be located > in $ORACLE_HOME/rdbms/admin (I don't know the exact name of the file, but a > grep will probably do). > If you decide to recompile that manually be aware most packages have an > accompanying prvt<package abbrev>.plb that also needs to be reapplied. > If there is an error validating that file, you should post the exact error > message. > > Hth, > -- > Sybrand Bakker, Oracle DBA > Venkatesh Kumar <vkumar_at_fundu.com> wrote in message > news:37F63AB7.FA335F37_at_fundu.com... > > Hi guys, > > An additional thingthat I found. We had this problem when we are running > > the database in the Archive Log mode. When we run it in the noarchive > > mode, it seems to be fine. Any ideas wh it behaves like that in Archivelog > > mode. If that is the normal behaviour, how does one makes updates to > > packages in a production environment ? > >Received on Mon Oct 04 1999 - 12:20:35 CDT
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................