Renewing of TEST or Development environments , clone of standby database , can be used. At my last renew process for TEST , i have used last backup of production system which was used to open standby database . Production system has been backed up and standby controlfile created . After successfull standby database creation , by using same backup sets new TEST environment has been restored to another location.
Whenever with command "alter database activate standby database" to open standby database as active database , below error encountered.
alter database activate standby database
ALTER DATABASE ACTIVATE [PHYSICAL] STANDBY DATABASE (XXX)
Begin: Standby Redo Logfile archival
End: Standby Redo Logfile archival
Signalling error 1152 for datafile 1!
Beginning standby crash recovery.
Serial Media Recovery started
Managed Standby Recovery starting Real Time Apply
Media Recovery Waiting for thread 1 sequence 318427
Fetching gap sequence in thread 1, gap sequence 318427-318427
FAL[client]: Error fetching gap sequence, no FAL server specified
Wed Jan 24 23:54:19 2018
FAL[client]: Error fetching gap sequence, no FAL server specified
Wed Jan 24 23:54:29 2018
FAL[client]: Error fetching gap sequence, no FAL server specified
Wed Jan 24 23:54:39 2018
FAL[client]: Error fetching gap sequence, no FAL server specified
Wed Jan 24 23:54:49 2018
FAL[client]: Error fetching gap sequence, no FAL server specified
Wed Jan 24 23:54:59 2018
FAL[client]: Error fetching gap sequence, no FAL server specified
Wed Jan 24 23:55:09 2018
FAL[client]: Error fetching gap sequence, no FAL server specified
Standby crash recovery need archive log for thread 1 sequence 318427 to continue.
Please verify that primary database is transporting redo logs to the standby database.
Wait timeout: thread 1 sequence 318427
Standby crash recovery aborted due to error 16016.
ORA-16016: archived log for thread 1 sequence# 318427 unavailable
Recovery interrupted!
Completed standby crash recovery.
Signalling error 1152 for datafile 1!
ORA-1152 signalled during: alter database activate standby database...
Database has requested archivelog (318427) and could not get from primary system and finally timed out.
Actually database has been restored and recovered with last backup sets and archivelogs and at this point database can be used as TEST environment.
Because of type of controlfile which was standby , could cause this situation and thought recreate controlfile as primary controlfile.
Got controlfile script by using below command
"alter database backup controlfile to trace"
Created controlfile with above output of command with resetlogs and opened .
No comments:
Post a Comment