Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: standby db problems
btw oracle 8.1.7 on w2k
"clueless" <ro_cright_at_hotmail.com> wrote in message
news:T2Yq8.10147$f5.764939_at_news...
> Hi gang,
> I have created a non-managed oracle standby database in the following
> manner:
>
> from PRODUCTION
> 1) ran 'alter database create standby controlfile as blah...'
> 2) ran 'alter system archive log current'
> 3) shutdown normal
> 4) moved all datafiles, then init.ora, and archived redo logs over to
> standby host
>
> from STANDBY
> 5) updated the standby init file with the following parms:
> 5.1) standby_archive_dest = "d:\Oracle\oradata\cisprod\log\archive"
> log_archive_format = %%ORACLE_SID%%T%TS%S.ARC
> log_archive_dest_1 =
> "location=d:\Oracle\oradata\cisprod\log\archive MANDATORY"
> log_archive_dest_state_1 = enable
> log_archive_min_succeed_dest = 1
> 6) moved and renamed (is this a problem) the standby control file to the
> correct location
> 7) started up new instance (stanby instance)
> 8) ran 'startup nomount' on new db: success
> 9) ran 'alter database mount standby database': success
> 10) ran 'alter database recover standby database'
> I get this error:
> ORA-00279: change 76601141 generated at 04/01/2002 12:01:45 needed for
> thread 1
> ORA-00289: suggestion :
> D:\ORACLE\ORADATA\CISPROD\LOG\ARCHIVE\CISPRODT001S27021.arc
> ORA-00280: change 76601141 for thread 1 is in sequence #27021
> This archived redo log was manually shipped over to the standby location
> in step 4. I am assuming that in order for the standby instance to be
> capable of 'reading' this archived redo log it has to be shipped by the
> archiver process. Is this correct? If so is there a way of forcing the
> read or the arch redo log? BTW I cannot shut down the production instance
> for the next few weeks.
>
> Clueless
> a.k.a. knucklehead when it comes to stanby instances...
>
>
Received on Thu Apr 04 2002 - 07:11:58 CST