Standby db: continue manualluy alter database register logfile

Hi,
in my standby db 10.2.0.4, on linux platform, some archive log are not register properly and i need to perform the register logfile manually.
Which test a can i do to solve this problem?
Thank you.

This is my standby alert log:
-- Connected User is Valid
RFS[10]: Assigned to RFS process 26620
RFS[10]: Identified database type as 'physical standby'
Tue Sep 14 05:05:58 2010
Errors in file /oracle/admin/orcl/udump/orcl1_rfs_26620.trc:
ORA-16401: archivelog rejected by RFS
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[11]: Assigned to RFS process 26622
RFS[11]: Identified database type as 'physical standby'
Tue Sep 14 05:05:58 2010
Errors in file /oracle/admin/orcl/udump/orcl1_rfs_26622.trc:
ORA-16401: archivelog rejected by RFS
Tue Sep 14 05:06:03 2010
Media Recovery Log /database/arch/orcl/arc1_16195_326468442.ARC
Media Recovery Waiting for thread 2 sequence 16536
Tue Sep 14 05:20:46 2010
alter database register logfile '/database/arch/orcl/arc2_16536_326468442.ARC'
Tue Sep 14 05:20:46 2010
There are 1 logfiles specified.
ALTER DATABASE REGISTER [PHYSICAL] LOGFILE
Resynchronizing thread 2 from sequence 16535 to 16536
Completed: alter database register logfile '/database/arch/orcl/arc2_16536_326468442.ARC'
Tue Sep 14 05:20:48 2010
Media Recovery Log /database/arch/orcl/arc2_16536_326468442.ARC
Tue Sep 14 05:21:07 2010
Media Recovery Log /database/arch/orcl/arc1_16196_326468442.ARC
Media Recovery Log /database/arch/orcl/arc1_16197_326468442.ARC
Media Recovery Log /database/arch/orcl/arc1_16198_326468442.ARC
Media Recovery Waiting for thread 1 sequence 16199
Tue Sep 14 05:45:29 2010
RFS[6]: Archived Log: '/database/arch/orcl/arc1_16199_326468442.ARC'
Tue Sep 14 05:45:29 2010
RFS[8]: Archived Log: '/database/arch/orcl/arc1_16200_326468442.ARC'
Tue Sep 14 05:45:29 2010
RFS[6]: Archived Log: '/database/arch/orcl/arc1_16201_326468442.ARC'
Tue Sep 14 05:45:40 2010
Media Recovery Log /database/arch/orcl/arc1_16199_326468442.ARC
Media Recovery Waiting for thread 2 sequence 16537
Tue Sep 14 06:00:05 2010
alter database register logfile '/database/arch/orcl/arc2_16537_326468442.ARC'
Tue Sep 14 06:00:05 2010
There are 1 logfiles specified.
ALTER DATABASE REGISTER [PHYSICAL] LOGFILE
alter database register are performed from a scheduled shell script that check log from V$ARCHIVED_LOG

Similar Messages

Alter database register logfile

Hi,
I just setup a dr site for our client for R/3 production system.
I had two options to automatically apply the logfiles in standby system.
Option 1: Wrote a script to automate the archive from primary to standby and then apply on standby.
Option 2: Just moved the archive from primary to standby and fired the command alter database managed standby database;
Here i had to fire one more command on different sql session to register the archive on standby system. Registering log file has to be done for all archive logs.
Currently the standby system is running based on option1.
My question is,
why do i need to register these archive files?
Is there any way, this registration can be skipped?
Regards,
Iyyappan

Hello Iyyappan,
at first we have to clarify: A logical or a physical standby database?
For example:
If the primary database is unavailable, you have to perform the register manually.
It is described by the oracle dataguard concepts:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/log_transport.htm#i1148216
And take a look at here what a "gap" is:
http://www.dba-oracle.com/t_oracledataguard_37_archive_gap_sequence_.htm
Regards
Stefan

Alter database switch logfile

Hi friends,
Oracle DB 9i
I am making a standby database backup (hi-brid), and keep updating every hour on top of the hour sked it with the archive logs generated.
I am just confused a little. If I have 3 logfiles, and if I command "alter database switch log files", does the 3 logfiles
be converted to the backup archive logs ? or only one of them only, and I have to issue the command 3x so that I will be able to get all the latest transaction inside the 3 redo logfiles to be applied at the standby server.
Thanks a lot,
Ms Inday

crystal wrote:
oh i see :D , so at any time there is one and only one redo log group that has data? all the other 2 are empty?not empty, but already archived. When an online redo log fills, there is an automatic switch to the next group. As soon as the switch is complete, the archiver will start archiving the group that was just filled. Archiving does not wait until all redo groups are filled.
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2010.12.17 14:54:47 =~=~=~=~=~=~=~=~=~=~=~=
login as: oracle
oracle@vmlnx01's password:
Last login: Fri Dec 17 14:49:39 2010 from 192.168.160.1
[oracle@vmlnx01 ~]$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.4.0 - Production on Fri Dec 17 14:55:08 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select group#, archived, status from v$log order by 1;
alter system switch logfile;
    GROUP# ARC STATUS
1 YES INACTIVE
2 YES INACTIVE
3 NO CURRENT
SQL>
System altered.
SQL> select group#, archived, status from v$log order by 1;
alter system switch logfile;
    GROUP# ARC STATUS
1 NO CURRENT
2 YES INACTIVE
3 YES ACTIVE
SQL>
System altered.
SQL> select group#, archived, status from v$log order by 1;
alter system switch logfile;
    GROUP# ARC STATUS
1 YES ACTIVE
2 NO CURRENT
3 YES ACTIVE
SQL>
System altered.
SQL> select group#, archived, status from v$log order by 1;
alter system switch logfile;
    GROUP# ARC STATUS
1 YES INACTIVE
2 YES INACTIVE
3 NO CURRENT
SQL>
System altered.
SQL> select group#, archived, status from v$log order by 1;
alter system switch logfile;
    GROUP# ARC STATUS
1 NO CURRENT
2 YES INACTIVE
3 YES ACTIVE
SQL>
System altered.
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@vmlnx01 ~]$ exit
logout

Delete standby redo log from primary database

Hi all,
I'm trying to drop standby logfiles on primary database (other database that I'm configuring the DG).
The members of the standby log groups don't exists on file system.
Somebody have deleted these files. Its old configuration where the files were in file system. Now they are in ASM.
When I try to drop the standby logfiles I got the following error:
SQL> alter database clear logfile group 7;
alter database clear logfile group 7
ERROR at line 1:
ORA-19528: redo logs being cleared may need access to files
SQL> select * from v$logfile order by 1;
    GROUP# STATUS TYPE    MEMBER                                                                           IS_
         1         ONLINE +REDO1/proj/onlinelog/group_1.256.340558657                                     NO
         1         ONLINE +REDO2/proj/onlinelog/group_1.256.340558659                                     NO
         2         ONLINE +REDO1/proj/onlinelog/group_2.257.340558879                                     NO
         2         ONLINE +REDO2/proj/onlinelog/group_2.259.340558879                                     NO
         3         ONLINE +REDO1/proj/onlinelog/group_3.258.340558707                                     NO
         3         ONLINE +REDO2/proj/onlinelog/group_3.257.340558709                                     NO
         4         ONLINE +REDO2/proj/onlinelog/group_4.258.340558713                                     NO
         4         ONLINE +REDO1/proj/onlinelog/group_4.259.340558711                                     NO
         5         ONLINE +REDO2/proj/onlinelog/group_5.260.340558965                                     NO
         5         ONLINE +REDO1/proj/onlinelog/group_5.260.340558963                                     NO
         6         ONLINE +REDO1/proj/onlinelog/group_6.261.340558967                                     NO
         6         ONLINE +REDO2/proj/onlinelog/group_6.261.340558967                                     NO
         7         STANDBY /oracle/proj/onlinelog2/redo_702.log                                            NO
         7         STANDBY /oracle/proj/onlinelog1/redo_701.log                                            NO
         8         STANDBY /oracle/proj/onlinelog2/redo_802.log                                            NO
         8         STANDBY /oracle/proj/onlinelog1/redo_801.log                                            NO
         9         STANDBY /oracle/proj/onlinelog2/redo_902.log                                            NO
         9         STANDBY /oracle/proj/onlinelog1/redo_901.log                                            NO
        10         STANDBY /oracle/proj/onlinelog1/redo_1001.log                                           NO
        10         STANDBY /oracle/proj/onlinelog2/redo_1002.log                                           NO
20 rows selected.
SQL> select * from v$standby_log order by 1;
    GROUP# DBID            THREAD# SEQUENCE#      BYTES       USED ARC STATUS     FIRST_CHANGE# FIRST_TIM LAST_CHANGE# LAST_TIME
         7 UNASSIGNED            0          0 104854601        512 YES UNASSIGNED             0                      0
         8 UNASSIGNED            0          0 104854601        512 YES UNASSIGNED             0                      0
         9 UNASSIGNED            0          0 104854601        512 YES UNASSIGNED             0                      0
        10 UNASSIGNED            0          0 104854601        512 YES UNASSIGNED             0                      0What can I do to drop these reference?
Any other solution instead of edit the controlfile and stop/start tghe database?
thank you!!!!

Hello;
Well Oracle thinks the files are there, but I remember a bug on metalink where the controlfile still had them, but they were not on the file system. Can you confirm they exist?
Meanwhile I check my notes for the Oracle doc nunber.
Bug 6128242: TRYING TO DROP STANDBY LOG FAILS WITH ORA-19528
So if you are Oracle 10 this might be the issue.
workaround is to re-create the controlfile without the incorrect logfile. ( Yuk!! )
ORA-01156 When Adding Or Dropping Redo Logs [ID 452152.1]
Best Regards
mseberg
Edited by: mseberg on Oct 31, 2011 5:09 PM

Alter database ... keep identity hangs

Does anyone know what could cause the "alter database recover to logical standby keep identity" statement to hang waiting on "MRP wait on archivelog arrival"? I have executed this exact statement in the past on another physical standby and it went through fine.
I ran "exec dbms_logstdby.build" on the primary db (Linux 11.1.0.7), did a couple of log switches and then canceled the recovery process on the physical standby and executed the alter database...keep identity statement but the alter statement hung indefinitely on the standby db. It was always waiting to receive the current log file from the primary db.
Thanks.

Ogan, thanks for your response.
All the archived logs appeared to have been applied so I'm not sure what "necessary archivelogs" are left to copy and apply. I could not find any archive gap. Any idea what may be the issue from the output (RAC primary -> physical standby) you requested? thanks.
From v$archived_log
THREAD# NAME SEQUENCE# ARC APPLIED
1 /flashrecovery/DBSB1/archivelog/2010_07_11/1_9133_832673014.arc 9133 YES YES
1 /u01/logs/dbsb1/1_9133_832673014.arc 9133 YES YES
1 /flashrecovery/DBSB1/archivelog/2010_07_11/1_9134_832673014.arc 9134 YES YES
1 /u01/logs/dbsb1/1_9134_832673014.arc 9134 YES YES
1 /flashrecovery/DBSB1/archivelog/2010_07_11/1_9135_832673014.arc 9135 YES YES
1 /u01/logs/dbsb1/1_9135_832673014.arc 9135 YES YES
1 /flashrecovery/DBSB1/archivelog/2010_07_11/1_9136_832673014.arc 9136 YES YES
1 /u01/logs/dbsb1/1_9136_832673014.arc 9136 YES YES
1 /flashrecovery/DBSB1/archivelog/2010_07_11/1_9137_832673014.arc 9137 YES NO
1 /u01/logs/dbsb1/1_9137_832673014.arc 9137 YES YES
1 /flashrecovery/DBSB1/archivelog/2010_07_11/1_9138_832673014.arc 9138 YES NO
1 /u01/logs/dbsb1/1_9138_832673014.arc 9138 YES YES
1 /flashrecovery/DBSB1/archivelog/2010_07_11/1_9139_832673014.arc 9139 YES NO
1 /u01/logs/dbsb1/1_9139_832673014.arc 9139 YES YES
1 /flashrecovery/DBSB1/archivelog/2010_07_12/1_9140_832673014.arc 9140 YES NO
1 /u01/logs/dbsb1/1_9140_832673014.arc 9140 YES YES
2 /flashrecovery/DBSB1/archivelog/2010_07_11/2_8192_832673014.arc 8192 YES YES
2 /u01/logs/dbsb1/2_8192_832673014.arc 8192 YES YES
2 /flashrecovery/DBSB1/archivelog/2010_07_11/2_8193_832673014.arc 8193 YES YES
2 /u01/logs/dbsb1/2_8193_832673014.arc 8193 YES YES
2 /flashrecovery/DBSB1/archivelog/2010_07_11/2_8194_832673014.arc 8194 YES YES
2 /u01/logs/dbsb1/2_8194_832673014.arc 8194 YES YES
2 /flashrecovery/DBSB1/archivelog/2010_07_11/2_8195_832673014.arc 8195 YES YES
2 /u01/logs/dbsb1/2_8195_832673014.arc 8195 YES YES
2 /flashrecovery/DBSB1/archivelog/2010_07_11/2_8196_832673014.arc 8196 YES NO
2 /u01/logs/dbsb1/2_8196_832673014.arc 8196 YES YES
2 /flashrecovery/DBSB1/archivelog/2010_07_12/2_8197_832673014.arc 8197 YES NO
2 /u01/logs/dbsb1/2_8197_832673014.arc 8197 YES YES
2 /flashrecovery/DBSB1/archivelog/2010_07_12/2_8198_832673014.arc 8198 YES NO
2 /u01/logs/dbsb1/2_8198_832673014.arc 8198 YES YES
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 9140
Next log sequence to archive 0
Current log sequence 9141

Alter database OR alter system?? what is the logic?

Hi,
this is just a general question not related to any particular issue. I seem to be missing the logic behind when we need to use the "alter system ... " statements and when we need to use the "alter database ..." statements. Is there a logic I can use to guess ? Or we only need to remember them (or look up for them)?
Let's take an example.
alter database archivelog; & alter system checkpoint;
OR
alter database add logfile; & alter system set undo_retention=800;
If you have a key that can be generally applied please let me know as I am not able to find it. Thank you,
enrico

I am not sure if there is a general rule but this is what I use:
alter database is about modifying the database architecture, like data files, archived log files etc.
alter system is about modifying the instance. so, you are modifying the way oracle runs. Remember that all parameters should be done with alter system (like undo_retention)
hope this will help you.

ALTER DATABASE ADD STANDBY LOGFILE GROUP

version 10 & 11g
creating standby logfile groups on primary db is optional or needed? what could be advantages of both?
I am reading 2 articles one is creating that other not?
http://www.orafaq.com/node/2030
& 736863.1 Notes

DBA2008 wrote:
version 10 & 11g
creating standby logfile groups on primary db is optional or needed? what could be advantages of both? at primary database it is optional ,but it would be good candidate for switchover activity , it makes ensure that if you make any planned maintenance activity at primary site and switchover within yours data guard environment from primary database to physcial standby database ,if you create standby redo log at primary database it is not in use right now but it will be used when yours primary database switch to standby database after switching to physical standby databsae as a primary database.
Khurram

Standby database errors - Alter database open read only

alter database open read only
AUDIT_TRAIL initialization parameter is changed to OS, as DB is NOT compatible for database opened with read-only access
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 216
Mon Dec 20 11:58:18 2010
Standby crash recovery need archive log for thread 1 sequence 216 to continue.
Please verify that primary database is transporting redo logs to the standby database.
Wait timeout: thread 1 sequence 216
Standby crash recovery aborted due to error 16016.
Errors in file /u01/app/oracle/diag/rdbms/mdm2/MDM2/trace/MDM2_ora_17442.trc:
ORA-16016: archived log for thread 1 sequence# 216 unavailable
Recovery interrupted!
Completed standby crash recovery.
Signalling error 1152 for datafile 1!
Errors in file /u01/app/oracle/diag/rdbms/mdm2/MDM2/trace/MDM2_ora_17442.trc:
ORA-10458: standby database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '+MDMDG1/mdm2/datafile/system.280.738243341'
ORA-10458 signalled during: alter database open read only...
Mon Dec 20 12:13:46 2010
ALTER DATABASE RECOVER managed standby database using current logfile disconnect
Attempt to start background Managed Standby Recovery process (MDM2)
Mon Dec 20 12:13:46 2010
MRP0 started with pid=23, OS id=18974
MRP0: Background Managed Standby Recovery process started (MDM2)
started logmerger process
Mon Dec 20 12:13:51 2010
Managed Standby Recovery starting Real Time Apply
Parallel Media Recovery started with 2 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Waiting for thread 1 sequence 216
Completed: ALTER DATABASE RECOVER managed standby database using current logfile disconnect
The above lines are from alert log of standby database.
Standby standbase
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-10458: standby database requires recovery
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '+MDMDG1/mdm2/datafile/system.280.738243341'
Parameters set on primary are
log_archive_dest_1 LOCATION=+MDMDG3/MDM1/ARCH VALID_FOR=(ALL_LOGFILES,ALL_ROLE ) DB_UNIQUE_NAME=MDM1
log_archive_dest_state_1 ENABLE
log_archive_dest_2 SERVICE=MDM2 SYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=MDM2
log_archive_dest_state_2 ENABLE
dg_broker_config_file1 +MDMDG2/mdm/dg_config/dgconfig1_mdm.dat
dg_broker_config_file2 +MDMDG2/mdm/dg_config/dgconfig2_mdm.dat
fal_server MDM2
standby_file_management AUTO
log_archive_config dg_config=(MDM1,MDM2)
db_file_name_convert MDM2, MDM1
ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE availability ;
Standby pfile
*.archive_lag_target=900
*.audit_file_dest='/u01/app/oracle/admin/MDM2/adump'
*.audit_trail='db'
*.compatible='11.2.0.0.0'
*.control_files='+MDMDG1/MDM2/CONTROLFILE/controlfile01.ctl','+MDMDG2/MDM2/CONTROLFILE/controlfile02.ctl'
*.db_block_size=8192
*.db_create_file_dest='+MDMDG1'
*.db_domain=''
*.db_file_name_convert='MDM1','MDM2'
*.db_name='MDM'
*.db_recovery_file_dest='+MDMDG2'
*.db_recovery_file_dest_size=10485760000
*.db_unique_name='MDM2'
*.dg_broker_config_file1='+MDMDG2/MDM/DG_CONFIG/dgconfig1_MDM.dat'
*.dg_broker_config_file2='+MDMDG2/MDM/DG_CONFIG/dgconfig2_MDM.dat'
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=MDM2XDB)'
*.fal_server='MDM11','MDM12'
*.instance_name='MDM2'
*.log_archive_config='dg_config=(MDM1,MDM2)'
*.log_archive_dest_1='LOCATION=+MDMDG3/MDM2/ARCH VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=MDM2'
*.log_archive_dest_2='SERVICE=MDM1 ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=MDM1'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_format='MDM_%t_%s_%r.arc'
*.log_file_name_convert='MDM1','MDM2'
*.memory_target=838860800
*.nls_language='ENGLISH'
*.nls_territory='UNITED KINGDOM'
*.open_cursors=300
*.processes=500
*.remote_login_passwordfile='exclusive'
*.sessions=555
*.standby_file_management='AUTO'
*.undo_tablespace='UNDOTBS1'
On standby ASM
ASMCMD [+] > find * *
+MDMDG1/ASM/
+MDMDG1/ASM/ASMPARAMETERFILE/
+MDMDG1/ASM/ASMPARAMETERFILE/REGISTRY.253.737811541
+MDMDG1/MDM/
+MDMDG1/MDM2/
+MDMDG1/MDM2/CONTROLFILE/
+MDMDG1/MDM2/CONTROLFILE/controlfile01.ctl
+MDMDG1/MDM2/CONTROLFILE/current.265.738243333
+MDMDG1/MDM2/DATAFILE/
+MDMDG1/MDM2/DATAFILE/CANVAS_POPULARITY_DATA.264.738243343
+MDMDG1/MDM2/DATAFILE/CANVAS_POPULARITY_IDX.277.738243343
+MDMDG1/MDM2/DATAFILE/MDM_SRC_DATA.282.738243343
+MDMDG1/MDM2/DATAFILE/MDM_SRC_IDX.275.738243343
+MDMDG1/MDM2/DATAFILE/MIPS_MDM_DATA.283.738243341
+MDMDG1/MDM2/DATAFILE/MIPS_MDM_IDX.276.738243343
+MDMDG1/MDM2/DATAFILE/SYSAUX.281.738243341
+MDMDG1/MDM2/DATAFILE/SYSTEM.280.738243341
+MDMDG1/MDM2/DATAFILE/TEST_TBSP1.273.738243345
+MDMDG1/MDM2/DATAFILE/TEST_TBSP2.272.738243345
+MDMDG1/MDM2/DATAFILE/UNDOTBS1.256.738243343
+MDMDG1/MDM2/DATAFILE/UNDOTBS2.279.738243343
+MDMDG1/MDM2/DATAFILE/USERS.278.738243347
+MDMDG1/MDM2/ONLINELOG/
+MDMDG1/MDM2/ONLINELOG/group_1.259.738243429
+MDMDG1/MDM2/ONLINELOG/group_2.257.738243431
+MDMDG1/MDM2/ONLINELOG/group_21.284.738243505
+MDMDG1/MDM2/ONLINELOG/group_22.261.738243505
+MDMDG1/MDM2/ONLINELOG/group_23.274.738243505
+MDMDG1/MDM2/ONLINELOG/group_3.258.738243431
+MDMDG1/MDM2/ONLINELOG/group_31.262.738243513
+MDMDG1/MDM2/ONLINELOG/group_32.270.738243513
+MDMDG1/MDM2/ONLINELOG/group_33.263.738243513
+MDMDG1/MDM2/ONLINELOG/group_4.260.738243431
+MDMDG2/MDM/
+MDMDG2/MDM/DG_CONFIG/
+MDMDG2/MDM2/
+MDMDG2/MDM2/AUTOBACKUP/
+MDMDG2/MDM2/AUTOBACKUP/2010_12_20/
+MDMDG2/MDM2/AUTOBACKUP/2010_12_20/s_738242861.263.738244155
+MDMDG2/MDM2/CONTROLFILE/
+MDMDG2/MDM2/CONTROLFILE/controlfile02.ctl
+MDMDG2/MDM2/CONTROLFILE/current.271.738243335
+MDMDG2/MDM2/ONLINELOG/
+MDMDG2/MDM2/ONLINELOG/group_1.270.738243429
+MDMDG2/MDM2/ONLINELOG/group_2.269.738243431
+MDMDG2/MDM2/ONLINELOG/group_21.268.738243505
+MDMDG2/MDM2/ONLINELOG/group_22.272.738243505
+MDMDG2/MDM2/ONLINELOG/group_23.262.738243505
+MDMDG2/MDM2/ONLINELOG/group_3.273.738243431
+MDMDG2/MDM2/ONLINELOG/group_31.266.738243513
+MDMDG2/MDM2/ONLINELOG/group_32.265.738243513
+MDMDG2/MDM2/ONLINELOG/group_33.264.738243513
+MDMDG2/MDM2/ONLINELOG/group_4.261.738243431
+MDMDG3/MDM/
+MDMDG3/MDM/ARCH/
+MDMDG3/MDM2/
+MDMDG3/MDM2/ARCH/
-- Please can I know how to open read only standby database.

user5846399 wrote:
ORA-16016: archived log for thread 1 sequence# 216 unavailable
Recovery interrupted!archived log for thread 1 sequence# 216
This file is needed for recovery, Find it and move it to the standby database side.

ORA-279 signalled during: ALTER DATABASE RECOVER automatic standby databas

Hi,
oracle server:8.1.7.0.0
os:solaris 5.9
we created standby server by taking coldbackup of primary server and we are using rsync to syschronize the archive log files between production and standby servers but every over we recover the standby server by executing
sql>recover automatic standby database:
but in alert log file i am getting the following error :
but when i googled for ora-279 error some people says it is default behaviour and can it be ignored and why it is asking next logfile.
Media Recovery Log /oratranslog/arch_1_1701118.arc
Wed Mar 26 21:35:34 2008
Media Recovery Log /oratranslog/arch_1_1701119.arc
Wed Mar 26 21:35:54 2008
Media Recovery Log /oratranslog/arch_1_1701120.arc
ORA-279 signalled during: ALTER DATABASE RECOVER automatic standby database...
Wed Mar 26 21:36:24 2008
ALTER DATABASE RECOVER CANCEL
Wed Mar 26 21:36:24 2008
Media Recovery Cancelled
Completed: ALTER DATABASE RECOVER CANCEL
Thanks and Regards
Prakash
juniour oracle dba

damorgan,
He is running 8.1.7.0. "DataGuard" scripts were initially available for 9i and then
backported (and available as a seperate download) for 8i. Many 8i implementations
did not and do not use DataGuard.
Even if it is "Jurassic" {which it certainly is NOT}, they obviously do have a good
reason for setting up a standby -- they DO have data of value. So, maybe they have
not upgraded to 9i or 10g. There could be a dozen reasons
1. Server HW/OS doesn't support 9i/10g, not budgetting for Server upgrade
2. Application using Forms 2.x or 4.5 and not tested on 9i / 10g (4.5 not certified
on 9i)
3. Low end client PCs working perfectly with Character-mode forms, not powerful
enought to run Jinitiator and Forms 6i / 9i
Just because someone hasn't upgraded to 10g doesn't mean that they are at fault
when you do NOT know the reason why they have not upgraded.
Surely, they do know that 8i is desupported. Don't you think that their management
has undertaken due diligence / cost-benefit analysis in considering whether they
should upgrade to 10g ?
Maybe they have another project implementing 10g in parallel and will be able
to shutdown this environment soon. Maybe they don't need to do so.
Do understand that people are intelligent enough to make their own decisions
considering their particular circumstances and don't go shooting off with your
assumption that anyone not running 10g is a dinosaur.

"Alter Database" command in Database Standby

Hi community.
I have the following situation:
I've ASE 15.7 CE SP121 in two enviroments: System Production and System Standby. The Standby is maintained with load of dump transaction generated in production every 10 minutes.
Now I need increase a database in data portion in 100GB. I know that I must make this in each enviroment (Production and Standby), also I know that I can execute alter database command while the database in the System Standby is offline.
The process that I make is:
Stop dump transaction in production.
Stop Load transaction in Standby.
Alter database "on" in Production. Result is Sucessfull.
Alter database "on" in Standby. Result is error:
In this step, I receipt the following error:
The database DBUSER is in the middle of a load sequence. Altering it will not let you load other transaction dumps in the dump-set. If you still prefer to do it please use OVERRIDE option.
In this situation I have that put online database and increase the size. Obiously, I can't load more dump transaction and I should generate a full dump database in production, load this dump in standby and load dump transations after to load of dump database (full).
I simulate my situation in a enviorement of test with pubs3 and then of load the last dump transaction, I can do alter database in my DB standby without problems and after of this process I continue load dump transaction.
I don't understand why receipt this error?
Any recomendation?
Thanks!
Cristian Lopez.

I can't recall trying to extend an offline database so what I'd probably do (short of waiting for a definitive answer from someone @ SAP/Sybase ... either here in the forum or from tech support) ...
1 - Assuming you have to perform a full database dump/load after issuing 'alter database', decide on a good time to perform the full database dump/load and then ...
2 - follow your steps (above) and then try restarting the log dump/load and ...
3a - if the log dump/load succeeds ... you've got nothing else to do
3b - if the log dump/load fails, then proceed with the full database dump/load

What happens at backend when we fire alter database commit to switchover to physical standby

Hi,
What exactly happens at backend when we fire alter database commit to switchover to physical standby.
how the transition happens?
Thanks

Hi,
The following will happen at the backend
1.) Notifies the primary database that a switchover is about to occur
2.) Disconnect all users from the primary database
3.) Generate a special redo record that signals the End of Redo (EOR)
4.) Converts the primary database into a standby database
5.) Once the standby database applies the final EOR record, guaranteeing that no data loss has been lost, converts the standby database into the primary database.
The new standby database (old primary) starts to receive the redo records and continues process until we switch back again. It is important to remember that both databases receive the EOR record so both databases know the next redo that will be received.
Regards,
Pradeep. V

RMAN-11001: alter database mount standby database

I'm doing a duplicate for a standby database and I'm getting this error
Oracle 8i Tru64
RMAN-03002: failure during compilation of command
RMAN-03013: command type: Duplicate Db
RMAN-03015: error occurred in stored script Memory Script
RMAN-03006: non-retryable error occurred during execution of command: sql
RMAN-07004: unhandled exception during command execution on channel clone_defaul
t
RMAN-20000: abnormal termination of job step
RMAN-11003: failure during parse/execution of SQL statement: alter database moun
t standby database
RMAN-11001: Oracle Error: ORA-03113: end-of-file on communication channel
Recovery Manager complete.
Any help please

Check for parameter mismatches between parameter file and control file.
Check your parameter file. Check db_name paramter in paramter file used in the standby database.

Alter database recover to logical standby is hanging

Hi,
when I try to convert my physical standby to logical standby using
alter database recover to logical standby STANDBYL;
the command just hangs
I have seen the usual hit on this which is to create the Redo Dictionary on the Primary using
execute dbms_logstdby.build;
which I did but the alter database command still keeps hanging on my Standby
Any ideas,
thanks
Jim

Hello;
Does your Standby alert log have any lines like this:
RECOVER TO LOGICAL ...
If yes look for the message ( after this )
Starting datafile conversion
and post any errors or warnings you have.
Best Regards
mseberg

What is the Use of "Alter database activate standby database"

Hi ,
I appreciate your time.
I just wanted to know what is the use of "Alter database activate standby database" command when doing the failover. How different it will act in failover process. Can we use this command in SwitchOver.
Thanks in advance.

Hi Uwe Hesse,
Wonderfull... good info....
So my understanding is that the use of "ACTIVATE PHYSICAL STANDBY DATABASE" is conditional and depends on the redo log gap and the Database status(Able to mount or not).
Condition 1: If the Db is in Mount state and Redo log gap is successfully filled.
1) Flush any unsent redo from the primary database to the target standby database.
SQL> ALTER SYSTEM FLUSH REDO TO target_db_name;
Note: If the above Statement Completes successfully without any errors.
2) Stop Redo Apply.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
3) Finish applying all received redo data.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH;
4) Verify that the target standby database is ready to become a primary database.
SQL> SELECT SWITCHOVER_STATUS FROM V$DATABASE;
5) Switch the physical standby database to the primary role.
SQL> ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WITH SESSION SHUTDOWN;
Condition 2: If the DB is not able Mount and Redo Gap can't be filled.
Important Note: If the the above command in STEP3 gives error, some received redo data was not applied. Try to resolve the cause of the error and re-issue the statement before proceeding.
If the error condition cannot be resolved, a failover can still be performed (with some data loss) by issuing the following SQL statement on the target standby database:
SQL> ALTER DATABASE ACTIVATE PHYSICAL STANDBY DATABASE;
Thanks in advance.

ALTER DATABASE START LOGICAL STANDBY APPLY INITIAL

I am using oracle 9.2.0.8 db version. I am trying to configure logical standby database. When I issue "ALTER DATABASE START LOGICAL STANDBY APPLY INITIAL" i get following error.
ERROR at line 1:
ORA-01427: single-row subquery returns more than one row
ORA-06512: at line 1

Hello,
Please, have a look on the Alert log fille, and post the error message if any.
May be you'll have more information about the offending subquery.
Best regards,
Jean-Valentin

Standby db: continue manualluy alter database register logfile

Similar Messages

Maybe you are looking for