weird standby database problem

From: Carsten Grammes <cgrammes_at_gmx.net>
Date: Fri, 14 Feb 2003 13:50:12 GMT
Message-ID: <3e4cefd2.622228076@gandalf.dialogika.de>

Hello world,

I'm trying to set up a standby database.

I did the following on master:

1) alter system archive log current;
2) alter database create standby controlfile as 'c:\tmp\stby.ctl'
3) shutdown master; standby is also down.
4) copy init.ora from master to standby
5) add the statement 
	standby_archive_dest = 'c:\oracle\archive\von_rot'

to standby init.ora
6) add the statement

log_archive_dest_2 = 'SERVICE=rotstby.dialogika.de' to the master init.ora
7) copy all *.dbf *.log files from master to standby

(filesystem structure is identical)
8) copy c:\tmp\stby.ctl to standby as control01.ctl, control02.ctl, control03.ctl
9) I'm starting the standby database (restart W2K service) and connect

with sqlplus to it

	connect sys as sysdba
	startup nomount
	lter database mount standby database
	lter database recover managed standby database

10) restart master db.

What happens: at any log switch the archived redo logs get transferred neatly to the standby site. The standby db receives the logs but does not apply them because it thinks it needs seq #1 (which should be nonsense).

See:
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS ------- ------------ ---------- ---------- ---------- ----------

ARCH    CONNECTED             0          0          0          0
ARCH    CONNECTED             0          0          0          0
MR(fg)  WAIT_FOR_LOG       6918          1          0          0
RFS     RECEIVING             0          0          0          0
RFS     RECEIVING             1         25        350        350

This is also reflected in the standby alert log: Starting up ORACLE RDBMS Version: 9.2.0.1.0. System parameters with non-default values:

  processes                = 150
  timed_statistics         = TRUE
  shared_pool_size         = 33554432
  large_pool_size          = 8388608
  java_pool_size           = 33554432
  control_files            = C:\ORACLE\ORADATA\BLAUDB\CONTROL01.CTL,

C:\ORACLE\ORADATA\BLAUDB\CONTROL02.CTL,
C:\ORACLE\ORADATA\BLAUDB\CONTROL03.CTL

  db_block_size            = 8192
  db_cache_size            = 20971520
  compatible               = 9.2.0.0.0
  log_archive_start        = TRUE
  log_archive_dest_1       = LOCATION=c:\oracle\archive
  standby_archive_dest     = c:\oracle\archive\von_rot
  log_archive_format       = rotdb_%S.arc

db_file_multiblock_read_count= 16

  fast_start_mttr_target   = 300
  undo_management          = AUTO
  undo_tablespace          = UNDOTBS1
  undo_retention           = 10800
  remote_login_passwordfile= EXCLUSIVE
  db_domain                = dialogika.de
  global_names             = TRUE
  instance_name            = rotdb
  dispatchers              = (PROTOCOL=TCP) (SERVICE=blaudbXDB)
  job_queue_processes      = 10
  hash_join_enabled        = TRUE
  background_dump_dest     = C:\oracle\admin\blaudb\bdump
  user_dump_dest           = C:\oracle\admin\blaudb\udump
  core_dump_dest           = C:\oracle\admin\blaudb\cdump
  sort_area_size           = 524288
  db_name                  = rotdb
  open_cursors             = 300

star_transformation_enabled= FALSE

  query_rewrite_enabled    = FALSE
  pga_aggregate_target     = 18874368
  aq_tm_processes          = 1
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7

CJQ0 started with pid=8
QMN0 started with pid=9
Fri Feb 14 11:29:34 2003
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'... ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=12
ARC0: Archival started
ARC1 started with pid=13
ARC1: Archival started
Fri Feb 14 11:29:35 2003
ARCH: STARTING ARCH PROCESSES COMPLETE
Fri Feb 14 11:29:35 2003
ARC0: Thread not mounted
Fri Feb 14 11:29:35 2003
ARC1: Thread not mounted
Fri Feb 14 11:29:51 2003
alter database mount standby database
Fri Feb 14 11:29:56 2003
Successful mount of redo thread 1, with mount id 3025341487. Fri Feb 14 11:29:56 2003
Standby Database mounted.
Completed: alter database mount standby database Fri Feb 14 11:30:21 2003
alter database recover managed standby database Media Recovery Start: Managed Standby Recovery Starting datafile 1 recovery in thread 1 sequence 25 Datafile 1: 'C:\ORACLE\ORADATA\BLAUDB\SYSTEM01.DBF' Starting datafile 2 recovery in thread 1 sequence 25 Datafile 2: 'C:\ORACLE\ORADATA\BLAUDB\UNDOTBS01.DBF' Starting datafile 3 recovery in thread 1 sequence 25 Datafile 3: 'C:\ORACLE\ORADATA\BLAUDB\CWMLITE01.DBF' Starting datafile 4 recovery in thread 1 sequence 25 Datafile 4: 'C:\ORACLE\ORADATA\BLAUDB\DRSYS01.DBF' Starting datafile 5 recovery in thread 1 sequence 25 Datafile 5: 'C:\ORACLE\ORADATA\BLAUDB\EXAMPLE01.DBF' Starting datafile 6 recovery in thread 1 sequence 25 Datafile 6: 'C:\ORACLE\ORADATA\BLAUDB\INDX01.DBF' Starting datafile 7 recovery in thread 1 sequence 25 Datafile 7: 'C:\ORACLE\ORADATA\BLAUDB\ODM01.DBF' Starting datafile 8 recovery in thread 1 sequence 25 Datafile 8: 'C:\ORACLE\ORADATA\BLAUDB\TOOLS01.DBF' Starting datafile 9 recovery in thread 1 sequence 25 Datafile 9: 'C:\ORACLE\ORADATA\BLAUDB\USERS01.DBF' Starting datafile 10 recovery in thread 1 sequence 25 Datafile 10: 'C:\ORACLE\ORADATA\BLAUDB\XDB01.DBF' Media Recovery Log
Media Recovery Waiting for thread 6918 seq# 1

What might be wrong? Why is it waiting for log seq# 1?

Thanks for help
Carsten.

---
I want to die peacefully in sleep like my grandfather.
Not screaming in terror like his passengers!

Received on Fri Feb 14 2003 - 07:50:12 CST