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

Home -> Community -> Mailing Lists -> Oracle-L -> RE: ARCHIVELOG start

RE: ARCHIVELOG start

From: Steve Orr <sorr_at_arzoo.com>
Date: Thu, 15 Jun 2000 11:35:17 -0700
Message-Id: <10529.109447@fatcity.com>


Winnie,

I guess I missed the context somewhere and had an RMAN-like reaction...

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input

:-)

We really do need a frequently asked questions and frequently given answers message board.

Steve Orr

-----Original Message-----
From: root_at_fatcity.com [mailto:root_at_fatcity.com]On Behalf Of Winnie_Liu_at_infonet.com
Sent: Wednesday, June 14, 2000 5:06 PM
To: Multiple recipients of list ORACLE-L Subject: RE: ARCHIVELOG start

Steve,

I think that when I am saying it, I am telling Jared that, either 1,2 or 2,3 will work, not 1 and 2 and 3.

But anyway... I hope all people will understand this by now that by changing that parameter in init.ora file will not put it in archivelog mode.

And I guess we have been getting this question about once every two weeks? Can we put it in a FAQ? hehe :P

Winnie

"Steve Orr" <sorr_at_arzoo.com> on 06/13/2000 08:04:21 PM

Please respond to ORACLE-L_at_fatcity.com

To: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com> cc: (bcc: Winnie Liu/HQ/ISC)

Winnie said...
> You only have to do either 1. or 3. to make the database into
> archivelog mode.

(legend:

1= set init.ora parm as log_archive_start = true
2= alter database archivelog
3= alter system archive log start

)

Actually, neither 1 nor 3 put the database into archivelog mode. You just have to do 2 to put the database into archivelog mode. Database archivelog mode and automatic archiving are two different things. You can manually archive (does anybody ever really?) or start automatic archiving with either
1 or 3. But since you have to shut down the database to do 2 (shutdown=> alter database mount=> alter database archivelog=> alter database open) then
you can just use the init.ora method. But I usually do 2 to set the database
archive mode, then do 3 to immediately start automatic archiving, then I also do 1 so I don't have to wonder whether the database is archiving automatically after each startup.

Steve Orr
The Wilderness of Silicon Valley

-----Original Message-----
Deepak
Sent: Tuesday, June 13, 2000 7:05 PM
To: Multiple recipients of list ORACLE-L

if database is in no archive log mode and you have automatic archival enabled(init para) .. oracle simply ignores it .. atleast for 8i

deepAk

-----Original Message-----
Sent: Tuesday, June 13, 2000 6:16 PM
To: Multiple recipients of list ORACLE-L

Let's backup a minute... To start automatic archiving you need to either: 1)
change the init.ora parm and restart the database; or 2) issue "archive log start" from svrmgrl. You can have archiving started but not have the database in archivelog mode. See the below listing:



SVRMGR> archive log start
Statement processed.
SVRMGR> archive log list
Database log mode              No Archive Mode
Automatic archival             Enabled
Archive destination            /u01/oracle/product/8.1.6/dbs/arch
Oldest online log sequence     2140
Current log sequence           2142

SVRMGR>

But to implement archiving you need to shutdown the database, startup mount,
alter database archivelog, archive log start, alter database open, then do an "archive log list" to make sure both the database is in log mode AND automatic archiving is enabled.

I once left automatic archiving enabled on a database that wasn't in archivelog mode. Eventually when it wrapped around and started having "recursive SQL errors" until it crashed. At least that's the way it was in Oracle 7.3. Right?

Steve Orr
Silicon Valley

-----Original Message-----
Winnie_Liu_at_infonet.com
Sent: Tuesday, June 13, 2000 5:14 PM
To: Multiple recipients of list ORACLE-L

Jared,

The backup and recovery book is right. You only have to do either 1. or 3. to make the database into archivelog mode.

If you don't have that init.ora parameter set (log_archive_start) during startup, the archiver process is not started. Then even though you put the database in archivelog mode, there is no process to do the archive. That is why you will need to last one (alter system archive log start).

Winnie

Jared Still <jkstill_at_bcbso.com> on 06/13/2000 02:58:32 PM

Please respond to ORACLE-L_at_fatcity.com

To: Multiple recipients of list ORACLE-L <ORACLE-L_at_fatcity.com> cc: (bcc: Winnie Liu/HQ/ISC)

Confusing at first isn't it?

  1. The init.ora parameter log_archive_start is to start the archiver process(es) when the database starts.
  2. 'alter database archivelog' puts the database in archive log mode.
  3. 'alter system archive log start' starts automatic archiving.

'Oracle Backup and Recovery Handbook' states that either of 1 or 3 is necessary.

I must confess that I do all 3 when putting a database in archive mode.

Jared

On Tue, 13 Jun 2000 Lisa_Koivu_at_gelco.com wrote:

> Good morning -

>

> I've created about 5 databases in the last week. Why is it that I can set
> log_archive_start=TRUE but when the database comes up the first time it's
in
> noarchive mode? I have to manually put it in archive mode - after I do
Received on Thu Jun 15 2000 - 13:35:17 CDT

Original text of this message

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