Standby db-EE edition and Standard edition

Question

Dear friends,
10g on solaris 10.
What are the differences in standby db when using a enterprise edition and standard edition ?..
Any input will be of great help
Kai

Answer 1

Niall and team
I have read your presentation - "You Probably Don't need dataguard" and I tried it out on test database. I setup a manual standby database, archivelog is manually copied to standby db.
Maybe you have an idea on regarding SCN or archivelog that is not present but Oracle is asking/suggestion during recovery procedure..
environment:
2 virtual box - Solaris 10 Virtual Machine host on Windows XP
Oracle 10.2.0 Standard Edition
Primary DB host name: SE
Standby DB host name: SE2
archive dest = /export/home/oracle/archive (same on both machine)
db file = /export/home/oracle/oradata/se , /export/home/oracle/oradata/se2 --> so I used db_file convert parameter in init.ora
Steps:
On the newly created database, create a test table and insert values.
SQL> create table test(a number) tablespace users;
Table created.
SQL> insert into test values(&a);
Enter value for a: 1
old 1: insert into test values(&a)
new 1: insert into test values(1)
1 row created.
SQL> /
Enter value for a: 21
old 1: insert into test values(&a)
new 1: insert into test values(21)
1 row created.
SQL> /
Enter value for a: 31
old 1: insert into test values(&a)
new 1: insert into test values(31)
1 row created.
SQL> /
Enter value for a: 41
old 1: insert into test values(&a)
new 1: insert into test values(41)
1 row created.
SQL> commit;
Commit complete.
SQL> alter system archive log current;
System altered.
SQL>
$ ls -lrt
total 41808
-rw-r----- 1 oracle oinstall 21378048 Feb 24 15:52 1_2_711819574.dbf
$
Again, insert some values to test table,
SQL> insert into test values(&a);
Enter value for a: 33
old 1: insert into test values(&a)
new 1: insert into test values(33)
1 row created.
SQL> /
Enter value for a: 44
old 1: insert into test values(&a)
new 1: insert into test values(44)
1 row created.
SQL> /
Enter value for a: 55
old 1: insert into test values(&a)
new 1: insert into test values(55)
1 row created.
SQL> /
Enter value for a: 11
old 1: insert into test values(&a)
new 1: insert into test values(11)
1 row created.
SQL> commit;
Commit complete.
SQL> alter system archive log current;
System altered.
SQL> select * from test;
A
1
21
31
41
33
44
55
11
8 rows selected.
check archivelog dir,
$ ls -lrt
total 41816
-rw-r----- 1 oracle oinstall 21378048 Feb 24 15:52 1_2_711819574.dbf
-rw-r----- 1 oracle oinstall 4096 Feb 24 15:55 1_3_711819574.dbf
$
Then,
1. shutdown immediate (primary)
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL>
2. copy datafile, redo, archive log to SE2 node.
$ pwd
/export/home/oracle/oradata/se
$ ls
control01.ctl control03.ctl redo02.log sysaux01.dbf temp01.dbf users01.dbf
control02.ctl redo01.log redo03.log system01.dbf undotbs01.dbf
$ scp * [email protected]:/export/home/oracle/oradata/se2
Password:
control01.ctl 100% |******************************************************| 6896 KB 00:01
control02.ctl 100% |******************************************************| 6896 KB 00:01
control03.ctl 100% |******************************************************| 6896 KB 00:00
redo01.log 100% |******************************************************| 51200 KB 00:09
redo02.log 100% |******************************************************| 51200 KB 00:11
redo03.log 100% |******************************************************| 51200 KB 00:08
sysaux01.dbf 100% |******************************************************| 240 MB 00:54
system01.dbf 100% |******************************************************| 480 MB 01:35
temp01.dbf 100% |******************************************************| 20488 KB 00:04
undotbs01.dbf 100% |******************************************************| 25608 KB 00:05
users01.dbf 100% |******************************************************| 5128 KB 00:01
$
$ ls -lrt
total 41816
-rw-r----- 1 oracle oinstall 21378048 Feb 24 15:52 1_2_711819574.dbf
-rw-r----- 1 oracle oinstall 4096 Feb 24 15:55 1_3_711819574.dbf
$ scp 1_2_711819574.dbf [email protected]:/export/home/oracle/archive
Password:
1_2_711819574.dbf 100% |******************************************************| 20877 KB 00:04
$
3. startup (primary)
4. create standby control file
SQL> startup
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1279120 bytes
Variable Size 62917488 bytes
Database Buffers 100663296 bytes
Redo Buffers 2912256 bytes
Database mounted.
Database opened.
SQL> alter database create standby controlfile as '/export/home/oracle/standby.ctl';
Database altered.
5. copy standby control file to SE2
$ pwd
/export/home/oracle
$ scp standby.ctl [email protected]:/export/home/oracle
Password:
standby.ctl 100% |******************************************************| 6896 KB 00:01
$
6. edit init.ora, specify location of control file - use standby control file
*.control_files='/export/home/oracle/standby.ctl'
7. SE2,
SQL> startup nomount pfile=/export/home/oracle/product/10.2.0/db_1/dbs/initse.ora
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1279120 bytes
Variable Size 62917488 bytes
Database Buffers 100663296 bytes
Redo Buffers 2912256 bytes
8. alter database mount standby database;
SQL> alter database mount standby database;
Database altered.
SQL>
9. we'll try to open as read only without recovery,
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-16004: backup database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/export/home/oracle/oradata/se2/system01.dbf'
10. then, we recover by - recover standby database;
SQL> recover standby database;
ORA-00279: change 540274 generated at 02/24/2010 15:58:26 needed for thread 1
ORA-00289: suggestion : /export/home/oracle/archive/1_4_711819574.dbf
ORA-00280: change 540274 for thread 1 is in sequence #4
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00308: cannot open archived log
'/export/home/oracle/archive/1_4_711819574.dbf'
ORA-27037: unable to obtain file status
Intel SVR4 UNIX Error: 2: No such file or directory
Additional information: 3
ORA-00308: cannot open archived log
'/export/home/oracle/archive/1_4_711819574.dbf'
ORA-27037: unable to obtain file status
Intel SVR4 UNIX Error: 2: No such file or directory
Additional information: 3
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/export/home/oracle/oradata/se2/system01.dbf'
<observation> notice that archive log 4 is not yet present in Primary DB and STBY DB.
Question: Why Oracle is asking archivelog that does not exist? I noticed in other exercise that you can use the redo log instead of archive log that does not exist. Is this because when we create the standby control file, the SCN is in sync with redo log.
10. Now, we will copy archive log 3 to STDB,
$ cd archive
$ ls
1_2_711819574.dbf 1_3_711819574.dbf
$ scp 1_3_*711819574.dbf [email protected]:/export/home/oracle/archive
Password:
1_3_711819574.dbf 100% |******************************************************| 4096 00:00
$
11. on SE2, recover
SQL> recover automatic standby database until cancel;
ORA-00279: change 540274 generated at 02/24/2010 15:58:26 needed for thread 1
ORA-00289: suggestion : /export/home/oracle/archive/1_4_711819574.dbf
ORA-00280: change 540274 for thread 1 is in sequence #4
ORA-00278: log file '/export/home/oracle/archive/1_4_711819574.dbf' no longer
needed for this recovery
ORA-00308: cannot open archived log
'/export/home/oracle/archive/1_4_711819574.dbf'
ORA-27037: unable to obtain file status
Intel SVR4 UNIX Error: 2: No such file or directory
Additional information: 3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/export/home/oracle/oradata/se2/system01.dbf'
ORA-01112: media recovery not started
12. Now, to generate the archivelog 4 and get the SCN that is indicated above, from one of our redo log. we will go to PRIMARY DB, and insert some rows to TEST TABLE and switch log file.
SQL>
SQL> insert into test values(&a);
Enter value for a: 99
old 1: insert into test values(&a)
new 1: insert into test values(99)
1 row created.
SQL> /
Enter value for a: 100
old 1: insert into test values(&a)
new 1: insert into test values(100)
1 row created.
SQL> /
Enter value for a: 101
old 1: insert into test values(&a)
new 1: insert into test values(101)
1 row created.
SQL> commit;
Commit complete.
SQL> alter system switch logfile;
System altered.
$ ls -lrt
total 42568
-rw-r----- 1 oracle oinstall 21378048 Feb 24 15:52 1_2_711819574.dbf
-rw-r----- 1 oracle oinstall 4096 Feb 24 15:55 1_3_711819574.dbf
-rw-r----- 1 oracle oinstall 376832 Feb 24 16:28 1_4_711819574.dbf
13. We will again, switch logfile, to generate archive 5, before we copied archive 4 to STBY, we are sure that arch 5 is the active archivelog.
SQL> alter system switch logfile;
System altered.
SQL> exit
Disconnected from Oracle Database 10g Release 10.2.0.2.0 - Production
$ ls -lrt
total 42570
-rw-r----- 1 oracle oinstall 21378048 Feb 24 15:52 1_2_711819574.dbf
-rw-r----- 1 oracle oinstall 4096 Feb 24 15:55 1_3_711819574.dbf
-rw-r----- 1 oracle oinstall 376832 Feb 24 16:28 1_4_711819574.dbf
-rw-r----- 1 oracle oinstall 1024 Feb 24 16:31 1_5_711819574.dbf
$
14. copy archive log 4 to STBY (SE2)
$ scp 1_4_711819574.dbf [email protected]:/export/home/oracle/archive
Password:
1_4_711819574.dbf 100% |********************************************| 368 KB 00:00
$
15. In SE2, recover
SQL> recover automatic standby database until cancel;
ORA-00279: change 540985 generated at 02/24/2010 16:28:36 needed for thread 1
ORA-00289: suggestion : /export/home/oracle/archive/1_5_711819574.dbf
ORA-00280: change 540985 for thread 1 is in sequence #5
ORA-00278: log file '/export/home/oracle/archive/1_5_711819574.dbf' no longer
needed for this recovery
ORA-00308: cannot open archived log
'/export/home/oracle/archive/1_5_711819574.dbf'
ORA-27037: unable to obtain file status
Intel SVR4 UNIX Error: 2: No such file or directory
Additional information: 3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
15. Now let's see if we can open as read only and check test table.
SQL> alter database open read only;
Database altered.
SQL> select * from test;
A
1
21
31
41
33
44
55
11
99
100
101
11 rows selected.
16. Now shutdown STBY database,
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL>
17. On SE (PRIMARY), insert some records to TEST table, please take note that current archivelog is no. 5. We want to generate archivelog 6 and archivelog 7. Then only archivelog 5 and 6 will be copied to STBY.
SQL> insert into test values(&a);
Enter value for a: 1000
old 1: insert into test values(&a)
new 1: insert into test values(1000)
1 row created.
SQL> /
Enter value for a: 1001
old 1: insert into test values(&a)
new 1: insert into test values(1001)
1 row created.
SQL> /
Enter value for a: 1002
old 1: insert into test values(&a)
new 1: insert into test values(1002)
1 row created.
SQL> commit;
Commit complete.
SQL> alter system archive log current;
System altered.
SQL> exit
Disconnected from Oracle Database 10g Release 10.2.0.2.0 - Production
$ ls -lrt
total 42632
-rw-r----- 1 oracle oinstall 21378048 Feb 24 15:52 1_2_711819574.dbf
-rw-r----- 1 oracle oinstall 4096 Feb 24 15:55 1_3_711819574.dbf
-rw-r----- 1 oracle oinstall 376832 Feb 24 16:28 1_4_711819574.dbf
-rw-r----- 1 oracle oinstall 1024 Feb 24 16:31 1_5_711819574.dbf
-rw-r----- 1 oracle oinstall 31744 Feb 24 16:41 1_6_711819574.dbf
we will do, log switch to create archive log 7,
SQL> alter system switch logfile;
System altered.
SQL> exit
Disconnected from Oracle Database 10g Release 10.2.0.2.0 - Production
$ ls -lrt
total 42634
-rw-r----- 1 oracle oinstall 21378048 Feb 24 15:52 1_2_711819574.dbf
-rw-r----- 1 oracle oinstall 4096 Feb 24 15:55 1_3_711819574.dbf
-rw-r----- 1 oracle oinstall 376832 Feb 24 16:28 1_4_711819574.dbf
-rw-r----- 1 oracle oinstall 1024 Feb 24 16:31 1_5_711819574.dbf
-rw-r----- 1 oracle oinstall 31744 Feb 24 16:41 1_6_711819574.dbf
-rw-r----- 1 oracle oinstall 1024 Feb 24 16:42 1_7_711819574.dbf
Then copy, arc 5 and arc 6 to SE2 (STBY)
$ scp 1_5_711819574.dbf 1_6_711819574.dbf [email protected]:/export/home/oracle/archive
Password:
1_5_711819574.dbf 100% |*********************************************************| 1024 00:00
1_6_711819574.dbf 100% |*********************************************************| 31744 00:00
$
17. in SE2, recover
SQL> startup nomount pfile=/export/home/oracle/product/10.2.0/db_1/dbs/initse.ora
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1279120 bytes
Variable Size 62917488 bytes
Database Buffers 100663296 bytes
Redo Buffers 2912256 bytes
SQL> alter database mount standby database;
Database altered.
SQL> recover automatic standby database until cancel;
ORA-00279: change 541270 generated at 02/24/2010 16:41:26 needed for thread 1
ORA-00289: suggestion : /export/home/oracle/archive/1_7_711819574.dbf
ORA-00280: change 541270 for thread 1 is in sequence #7
ORA-00278: log file '/export/home/oracle/archive/1_7_711819574.dbf' no longer
needed for this recovery
ORA-00308: cannot open archived log
'/export/home/oracle/archive/1_7_711819574.dbf'
ORA-27037: unable to obtain file status
Intel SVR4 UNIX Error: 2: No such file or directory
Additional information: 3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
18. open as read only, to check if the newly inserted records can be view,
SQL> alter database open read only;
Database altered.
SQL> select * from test;
A
1
21
31
41
33
44
55
11
99
100
101
A
1000
1001
1002
14 rows selected.
OK, that means that archive log 5 and archivelog 6 are applied to STBY database.
Question. Why Oracle is asking the arc 7 , is it correct to say that last SCN is based on arc 5 and arc 6. Or is it Oracle behavior to ask the "next" SCN, after the arc 6. when performing recovery? ... that's why we have CANCEL.
Appreciate your response on this..
Thanks..
19. For the sake of curiosity, lets try if we can use - recover managed standby database; (archivelog is still manually copied)
on SE2, we will put it on "recovery mode"
shutdown immediate,
startup nomount pfile =
alter database mount standby database
recover managed standby database; (though the archivelogs are still copied manually )
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup nomount pfile=/export/home/oracle/product/10.2.0/db_1/dbs/initse.ora
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1279120 bytes
Variable Size 62917488 bytes
Database Buffers 100663296 bytes
Redo Buffers 2912256 bytes
SQL> alter database mount standby database;
Database altered.
SQL> recover managed standby database; (it will "hang", if you need to CANCEL open new session and use - recover managed standby database cancel)
our current arch is 7, we will insert records to test table, and generate arch 8 and arch 9, then we will transfer arch 7 and arch 8 to SE2,
on SE,
Connected to:
Oracle Database 10g Release 10.2.0.2.0 - Production
SQL> insert into test values(&a);
Enter value for a: 2000
old 1: insert into test values(&a)
new 1: insert into test values(2000)
1 row created.
SQL> /
Enter value for a: 2001
old 1: insert into test values(&a)
new 1: insert into test values(2001)
1 row created.
SQL> /
Enter value for a: 2003
old 1: insert into test values(&a)
new 1: insert into test values(2003)
1 row created.
SQL> commit;
Commit complete.
SQL> alter system archive log current;
System altered.
SQL> alter system switch logfile;
System altered.
SQL> exit
Disconnected from Oracle Database 10g Release 10.2.0.2.0 - Production
$ pwd
/export/home/oracle/archive
$ ls -lrt
total 45758
-rw-r----- 1 oracle oinstall 21378048 Feb 24 15:52 1_2_711819574.dbf
-rw-r----- 1 oracle oinstall 4096 Feb 24 15:55 1_3_711819574.dbf
-rw-r----- 1 oracle oinstall 376832 Feb 24 16:28 1_4_711819574.dbf
-rw-r----- 1 oracle oinstall 1024 Feb 24 16:31 1_5_711819574.dbf
-rw-r----- 1 oracle oinstall 31744 Feb 24 16:41 1_6_711819574.dbf
-rw-r----- 1 oracle oinstall 1024 Feb 24 16:42 1_7_711819574.dbf
-rw-r----- 1 oracle oinstall 1584640 Feb 24 17:02 1_8_711819574.dbf
-rw-r----- 1 oracle oinstall 2048 Feb 24 17:02 1_9_711819574.dbf
$
$ scp 1_7_711819574.dbf 1_8_711819574.dbf [email protected]:/export/home/oracle/archive
Password:
1_7_711819574.dbf 100% |*********************************************************| 1024 00:00
1_8_711819574.dbf 100% |*********************************************************| 1547 KB 00:00
$
Please take note that in SE2 initse.ora file, we also set standby_control_file = /export/home/oracle/archive parameter.
19. On SE2, open new session, and cancel recovery,
session 2,
SQL> recover managed standby database cancel;
Media recovery complete.
SQL>
session 1,
SQL> recover managed standby database;
ORA-16043: managed recovery session canceled
ORA-16037: user requested cancel of managed recovery operation
Lets check if archivelog is applied, by checking test table,
SQL> alter database open read only;
Database altered.
SQL> select * from test;
A
1
21
31
41
33
44
55
11
99
100
101
A
1000
1001
1002
14 rows selected.
Notice that 2000, 2001, 2002 are not added in TEST table.
Lets do manual recovery,
SQL> startup nomount pfile=/export/home/oracle/product/10.2.0/db_1/dbs/initse.ora
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1279120 bytes
Variable Size 62917488 bytes
Database Buffers 100663296 bytes
Redo Buffers 2912256 bytes
SQL> alter database mount standby database;
Database altered.
SQL> recover automatic standby database until cancel;
ORA-00279: change 541804 generated at 02/24/2010 17:02:34 needed for thread 1
ORA-00289: suggestion : /export/home/oracle/archive/1_9_711819574.dbf
ORA-00280: change 541804 for thread 1 is in sequence #9
ORA-00278: log file '/export/home/oracle/archive/1_9_711819574.dbf' no longer
needed for this recovery
ORA-00308: cannot open archived log
'/export/home/oracle/archive/1_9_711819574.dbf'
ORA-27037: unable to obtain file status
Intel SVR4 UNIX Error: 2: No such file or directory
Additional information: 3
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.
SQL> select * from test;
select * from test
ERROR at line 1:
ORA-01219: database not open: queries allowed on fixed tables/views only
SQL> alter database open read only;
Database altered.
SQL> select * from test;
A
1
21
31
41
33
44
55
11
99
100
101
A
1000
1001
1002
2000
2001
2003
17 rows selected.