Re: How to set Archivelog mod ?

"vigi98" <vigi98_at_caramail.com> wrote in message news:3CF343FB.70606_at_caramail.com...
> Adam Buczynski wrote:
> > Didn`t you forget to:
> >
> > SHUTDOWN IMMEDIATE
> >
> > STARTUP MOUNT
> >
> > ALTER DATABASE ARCHIVELOG
> >
> > ALTER DATABASE OPEN
> >
> > Adam
>
> I know this command line in mounted state. But, isn't it possible to set
> archivelog mode in init.ora and simply restart the database ?
>
> Second question : I tried what you propose, but sqlplus answered me :
> ORA-00265 : instance recovery required, cannot set ARCHIVELOG mode
>
> What does that mean ?

It really means (in the nicest possible way) that you haven't got a clue what you're doing. There is *no* init.ora to switch a database into archivelog mode dynamically. Think about it: it wouldn't make any sense if there were. You are about to start producing archives of your redo. That stream of archived redo needs to be continuous and uninterrupted, otherwise you can't guarantee to recover the database when the dread day comes. What would happen if you could switch archiving on and off at the drop of a hat? Er, there'd be an awful lot of gaps in the archive sequence, and an awful lot of unrecoverable databases as a result. Oracle just isn't going to let you stuff things up like that.

You can switch ARCH, the background process, on and off, for sure. But that's a very different matter. The worst that can happen there is that your database will hang until you give in and switch ARCH back on... at which point, he catches up by archiving everything that he didn't do whilst switched off. Switching ARCH on and off does *not* result in archive gaps. Switching on and off archivelog mode does.

As for what was proposed, it was entirely accurate. As for the error message you got, the answer is simple: stop doing shutdown aborts immediately! Again: you are about to start generating archives. They will be applied to something. That something must be a clean and consistent something, otherwise we shouldn't be bothering. A shutdown abort guarantees that you need to perform instance recovery. You have a messy database. It is not clean and consistent. Therefore, you can't announce to the database that you want to take that mess as the base from which to start taking archives.

Have another go, but this time issuing a shutdown immediate before trying to get to the mount stage.

You really need to read up about this. In the past, I would have pointed you to a backup and recovery document I wrote which would have given you a good basis from which to proceed, but I can't do that any more. Someone may have a copy that they can email you.

Regards
HJR
>
> >
> > "vigi98" <vigi98_at_caramail.com> wrote in message
> > news:cafa5ee3.0205272338.41ad1985_at_posting.google.com...
> >
> >>Hi all,
> >>
> >>In my init.ora, I tried lots of parameters in order to set my database
> >>in archivelog mode. There's nothing to do : I always have this :
> >>
> >>SQL> archive log list;
> >>Database log mode No Archive Mode
> >>Automatic archival Enabled
> >>Archive destination /u08/backup
> >>Oldest online log sequence 4771
> >>Current log sequence 4778
> >>
> >>As you can see, something is enabled (I wonder what it means...) but
> >>I'm not in archivelog mode. So what have I to do ?
> >>
> >>Following, the archive section of my init.ora :
> >>#--- Archive Mode ---
> >> log_archive_start = true
> >> #log_archive_dest_1 = "location=/u08/backup/"
> >> log_archive_dest_1 = "LOCATION=/u08/backup MANDATORY"
> >> #log_archive_dest = "location=/u08/backup/"
> >> log_archive_format = arch_%t_%s.arc
> >> log_archive_max_processes = 1 #AHU
> >> log_archive_dest_state_1 = ENABLE
> >>
> >>
> >>Thanks in advance for your help.
> >
> >
> >
>
>
Received on Tue May 28 2002 - 04:28:19 CDT