-
My production database is running on 8.1.6.0 .I created a standby and it was working fine for about a month .Today suddenly the production database went down where as the standby database was doing the managed recovery .
when I saw the alert log it show that arch ora 600 errors ..
The fix is to apply patch set 8.1.6.3 which the oracle support has said .
Till sunday I will not be able to do this since i have to bring other database also down .
What should i do to remove the link between the primary and the standby database
And have only the the primary database alone ..
I want to have only the primary database only for the time being ...
-
You really don't have to do anything to get rid of STANDBY database. Primary Database is not dependent on Standby at any time.
When you need standby database again, you need to recreate it.
-
Actually I was reading oracle documentation on creating managed recovery standby database.
I think you have to change your initSID.ora file on your primary database. i.e. log_archive_dest_2. (Not to through archivelog files onto your standby server.
Farrukh
-
The problem is I have a standby database created .Now in the primary database i have these parameters
log_archive_dest_2 ='SERVICE=standby'
log_archive_dest_state_2 =ENABLE
log_archive_dest_state_1 =ENABLE
standby_archive_dest =/oradata/archive/sprdprod
Can i comment these parameters and restart the database .
Will that solve my problem
-
If arch can not trasfer to standby database your primary database will stop.
Check listener file in which transfer of arch automaticlly to standby site is specified via parameters. ARCH =
SID_LIST_ARCH =
Also parameter, Lock_name_space in init files.
-
by doing: ALTER SYSTEM set log_archive_dest_state_2=disable;
you will no longer transfer the archived redo logs to the standby database.
also check v$archive_dest, look at the STATUS of the standby destination (TARGET = 'STANDBY') to make sure that it is in fact disabled.
