Enabling DATAGUARD causes Primary Database to crash
420083Jan 12 2012 — edited Feb 20 2012I have a primary and standby database configured on my laptop using oracle 11.2.0.1. The primary database is shipping the archivelogs to the designated archivelog destination for my standby database and applying the archivelog files. However, as soon as I enable dataguard broker, the primary database crashes. This happens everytime I enable dataguard. Does anyone have any ideas on why this is happening? Below are the steps I took.
1. modify parameter file on the primary database and added the following parameters.
LOG_ARCHIVE_CONFIG='DG_CONFIG=(prmy,stby)'
LOG_ARCHIVE_DEST_1='LOCATION=C:\arch\prmy VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=prmy'
LOG_ARCHIVE_DEST_2='SERVICE=stby ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=stby'
LOG_ARCHIVE_DEST_STATE_1=ENABLE
LOG_ARCHIVE_DEST_STATE_2=ENABLE
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
LOG_ARCHIVE_MAX_PROCESSES=30
FAL_SERVER=stby
DB_FILE_NAME_CONVERT='C:\app\oracle\oradata\stby','C:\app\oracle\oradata\prmy'
LOG_FILE_NAME_CONVERT='C:\arch\stby','C:\arch\prmy'
STANDBY_FILE_MANAGEMENT=AUTO
2. shutdown the primary database and create a cold backup.
3. oradim -new -sid -stby -syspwd change_on_install
4. modify the parameter file for standby database with the following
DB_UNIQUE_NAME=stby
control_files='C:\app\oracle\oradata\stby\stby.ctl'
DB_FILE_NAME_CONVERT='C:\app\oracle\oradata\prmy','C:\app\oracle\oradata\stby'
LOG_FILE_NAME_CONVERT='C:\arch\prmy','C:\arch\stby'
LOG_ARCHIVE_DEST_1='LOCATION=C:\arch\stby\ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=stby'
LOG_ARCHIVE_DEST_2='SERVICE=prmy ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=prmy'
LOG_ARCHIVE_DEST_STATE_1=ENABLE
LOG_ARCHIVE_DEST_STATE_2=ENABLE
STANDBY_FILE_MANAGEMENT=AUTO
FAL_SERVER=prmy
5. moved backup files onto standby area on laptop.
6. alter database create standby controlfile as 'C:\app\oracle\oradata\stby\stby.ctl';
6. create spfile from pfile
7. create standby logs on both primary and standby database.
8. enable archiving on both primary and standby
9. open primary database.
10. issue this on standby database in while in mount mode.
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE;
11. Verified the logfiles were getting shipped.
12. set up dataguard broker.
CREATE CONFIGURATION 'PRODDR'
AS
PRIMARY DATABASE IS 'prmy'
CONNECT IDENTIFIER IS 'prmy';
Configuration Status:
SUCCESS
ADD DATABASE 'stby' AS
CONNECT IDENTIFIER IS 'stby';
Configuration Status:
SUCCESS
ENABLE CONFIGURATION
Configuration Status:
SUCCESS
ENABLED DATABASE STANDBY