Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Sun Solaris Close - cannot turn archive log on

Re: Sun Solaris Close - cannot turn archive log on

From: Eva Haiden <eva.haiden_at_engnetworld.com>
Date: 10 Jun 2002 04:30:13 -0700
Message-ID: <52046b21.0206100330.34dcf777@posting.google.com>


Howard,

Thank you very much for your help! It fixed the problem!

Eva

"Howard J. Rogers" <dba_at_hjrdba.com> wrote in message news:<aduile$eep$1_at_lust.ihug.co.nz>...
> I expect you are using the log_archive_dest_1, log_archive_dest_2 etc
> parameters. Yet these are specifically only for the Enterprise Edition of
> the database, and it would appear from your ORA-00439 error that you only
> have the Standard Edition of the database installed.
>
> Try using log_archive_dest and log_archive_min_succeed_dest instead: those
> parameters (without the numbers at the end of them) work for both Enterprise
> *and* Standard editions.
>
> There is also a fair amount of confusion apparent from what you have
> written. Putting a database into archivelog mode is one thing (and is done
> with an alter database command in the MOUNT state, after database creation,
> and after a clean shutdown). Switching on the automatic archiving of redo
> (by switch on ARCH) is quite another operation altogether, and is done by
> setting init.ora parameters (as I've described above) or by the issuing of
> 'alter system' commands.
>
> The former (use of 'alter database' commands) is permanent, however many
> database startups and shutdowns you then go through -because it sets a bit
> in the Control File. The latter (use of 'alter system' commands) is
> temporary, because whatever it is that you have set is set only for the
> lifetime of the current instance: nothing is written permanently to a
> physical database file.
>
> Therefore, a phrase such as "With the next start of the instance the archive
> log mode is turned off again." doesn't ring true: you might well mean that
> ARCH is turned off again, but that should not mean that your database is out
> of archivelog mode. Check which is which with an 'archive log list' command
> in SQL Plus.
>
> Anyway: once you've sorted out the distinction between archivelog mode and
> automatic archiving in your head, make sure you use the archiving init.ora
> parameters that work for the Edition of the database you've installed.
>
> Regards
> HJR
>
> "Eva Haiden" <eva.haiden_at_engnetworld.com> wrote in message
> news:52046b21.0206070058.12778413_at_posting.google.com...
> > Dear Oracle users,
> >
> > I have the following problem: I am running Oracle 8.1.7 on a Sun
> > Solaris Sparc Clone. Using the Database Assistent I am trying to
> > create a database instance with archive mode enabled.
> >
> > If I turn the archive log on, the database instance will not be
> > created. When starting the instance, I receive the error message:
> > "ORA-01034 Oracle not available".
> >
> > If I turn the archive log off, the database instance is created fine.
> > But if I try to turn on the archive log after the instance has been
> > created with ALTER DATABASE it lasts only as long as the database is
> > not shutdown. With the next start of the instance the archive log mode
> > is turned off again.
> >
> > If I modify the init<instance name>.ora file to enable the archive
> > mode, the database instance starts with the error message: "ORA-00439
> > feature not enabled Managed standby" and acts like a standby database
> > even it is the initial database.
> >
> > I appreciate any help!
Received on Mon Jun 10 2002 - 06:30:13 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US