Physical standby database standby redo log problem

Hello
We have a physical standby database , I've created some standby redo log files but my problem is that they aren't used,
their status in v$stanby_log view is UNASSIGNED
and I see this message (ORA-16086: standby database does not contain available standby log files) in primary database alert_log file
while when I run "alter system switch logfile" in the primary database it transfer redo logs to the physsical standby database
and archive log file will be created in standby database
I've even recreated the standby redo log files and I added new ones to them but the problem wasn't solved
Do you know what is problem ?
elect group#,THREAD#,BYTES,STATUS from V$STANDBY_LOG;
group#     THREAD#      BYTES       STATUS
1                   0                   524288000                   UNASSIGNED
2                   0                   524288000                   UNASSIGNED
3                   0                   524288000                   UNASSIGNED
8                   0                   524288000                   UNASSIGNED
9                   0                   524288000                   UNASSIGNED
10                   0                   524288000                   UNASSIGNED
select group#,THREAD#,BYTES,MEMBERS,STATUS from v$log;
group#                    THREAD#                    BYTES                    MEMBERS                    STATUS
4                   1                   524288000                   2                   CLEARING
7                   1                   524288000                   2                   CLEARING_CURRENT
6                   1                   524288000                   2                   CLEARING
5                   1                   524288000                   2                   CLEARING
thanks

Hello Anurag
Thank you for your reply
I have found some issue in the standby database alert_log too , in the standby database alert_log it has been written:
RFS[782]: Assigned to RFS process 3919
RFS[782]: Identified database type as 'physical standby'
Primary database is in MAXIMUM AVAILABILITY mode
Standby controlfile consistent with primary
Primary database is in MAXIMUM AVAILABILITY mode
Standby controlfile consistent with primary
RFS[782]: No standby redo logfiles selected (reason:6)
Sun Jan 31 13:59:43 2010
Errors in file /u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc:
ORA-16086: standby database does not contain available standby log files
Sun Jan 31 13:59:48 2010
RFS[781]: Archived Log: '/disks/sda/tehrep/archivelogs/1_6516_670414641.dbf'
Sun Jan 31 13:59:50 2010
and the context "/u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc" is below :
+/u01/app/oracle/admin/tehrep/udump/tehrep_rfs_3919.trc+
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /u01/app/oracle/product/10.2.0/db_1
System name:    Linux
Node name:      linserver2.com
Release:        2.6.9-42.ELsmp
Version:        #1 SMP Wed Jul 12 23:27:17 EDT 2006
Machine:        i686
Instance name: tehrep
Redo thread mounted by this instance: 1
Oracle process number: 58
Unix process pid: 3919, image: [email protected]
*** SERVICE NAME:() 2010-01-31 13:59:43.865
*** SESSION ID:(109.1225) 2010-01-31 13:59:43.865
KCRRFLAS
KCRRSNPS
No space in recovery area for active standby redo logs
The primary database is operating in MAXIMUM PROTECTION
or MAXIMUM AVAILABILITY mode, and the standby database
does not contain adequate disk space in the recovery area
to safely archive the contents of the standby redo logfiles.
ORA-16086: standby database does not contain available standby log files
when I saw this line "No space in recovery area for active standby redo logs" I thought that STANDBY_ARCHIVE_DEST parameter points where that there is no enough space , but when I consider I found out that points a directory on disk a "sda" that has enough space , I don't know what that means
by the way, at below I've written a section of the primary database alert_log context and "lgwr" trace file around Sun Jan 31 13:30:34 2010
alert_log :
ORA-16086: standby database does not contain available standby log files
Sun Jan 31 13:30:34 2010
LGWR: Failed to archive log 7 thread 1 sequence 6512 (16086)
Thread 1 advanced to log sequence 6512
Current log# 7 seq# 6512 mem# 0: /disks/sdb/tehrep/redo71.log
Current log# 7 seq# 6512 mem# 1: /disks/sdd/tehrep/redo72.log
LNSc started with pid=53, OS id=11451
Sun Jan 31 13:36:34 2010
Errors in file /u01/app/oracle/admin/tehrep/bdump/tehrep_lgwr_3692.trc:
ORA-16086: standby database does not contain available standby log files
Sun Jan 31 13:36:34 2010
LGWR: Failed to archive log 5 thread 1 sequence 6513 (16086)
Thread 1 advanced to log sequence 6513
Current log# 5 seq# 6513 mem# 0: /disks/sdb/tehrep/redo51.log
Current log# 5 seq# 6513 mem# 1: /disks/sdd/tehrep/redo52.log
*/u01/app/oracle/admin/tehrep/bdump/tehrep_lgwr_3692.trc file :*
Error 16086 creating standby archive log file at host '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com
+)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated)))'+
*** 2010-01-31 13:30:34.712 60679 kcrr.c
LGWR: Attempting destination LOG_ARCHIVE_DEST_3 network reconnect (16086)
*** 2010-01-31 13:30:34.712 60679 kcrr.c
LGWR: Destination LOG_ARCHIVE_DEST_3 network reconnect abandoned
ORA-16086: standby database does not contain available standby log files
*** 2010-01-31 13:30:34.712 60679 kcrr.c
LGWR: Error 16086 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1521
+)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated)))'+
*** 2010-01-31 13:30:34.712 58941 kcrr.c
kcrrfail: dest:3 err:16086 force:0 blast:1
Receiving message from LNSc
*** 2010-01-31 13:30:34.718 55444 kcrr.c
Making upidhs request to LNSc (ocis 0x0xb648db48). Begin time is <01/31/2010 13:30:30> and NET_TIMEOUT <180> seconds
NetServer pid:11196
*** 2010-01-31 13:30:38.718 55616 kcrr.c
upidhs done status 0
*** 2010-01-31 13:36:31.062
LGWR: Archivelog for thread 1 sequence 6513 will NOT be compressed
*** 2010-01-31 13:36:31.062 53681 kcrr.c
+Initializing NetServer[LNSc] for dest=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1521)))(CO+
NNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated))) mode SYNC
LNSc is not running anymore.
New SYNC LNSc needs to be started
Waiting for subscriber count on LGWR-LNSc channel to go to zero
Subscriber count went to zero - time now is <01/31/2010 13:36:31>
Starting LNSc ...
Waiting for LNSc to initialize itself
*** 2010-01-31 13:36:34.116 53972 kcrr.c
+Netserver LNSc [pid 11451] for mode SYNC has been initialized+
Performing a channel reset to ignore previous responses
+Successfully started LNSc [pid 11451] for dest (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=linserver2.com)(PORT=1+
+521)))(CONNECT_DATA=(SERVICE_NAME=tehrep_XPT.com)(INSTANCE_NAME=tehrep)(SERVER=dedicated))) mode SYNC ocis=0x0xb648db48+
*** 2010-01-31 13:36:34.116 54475 kcrr.c
+Making upiahm request to LNSc [pid 11451]: Begin Time is <01/31/2010 13:36:31>. NET_TIMEOUT = <180> seconds+
Waiting for LNSc to respond to upiahm
*** 2010-01-31 13:36:34.266 54639 kcrr.c
upiahm connect done status is 0
Receiving message from LNSc
Receiving message from LNSc
Destination LOG_ARCHIVE_DEST_3 is in STANDBY RESYNCHRONIZATION mode
Receiving message from LNSc

Similar Messages

Problem with Whole Database Online+Redo log Backup

Dear Marcus Sir,
I am facing while taking "Whole Database Online+Redo log Backup" through DB13 T-Code.
Below is the "Problem part of the Backup log", however if you need I will send you full log.
Hope you will find out problem soon
#FILE..... /oracle/ANP/sapdata2/sr3_8/sr3.data8
#SAVED.... sr3.data8 ANPB260810/12
BR0280I BRBACKUP time stamp: 2010-08-27 11.03.22
BR0063I 9 of 51 files processed - 19400.070 MB of 135986.469 MB done
BR0204I Percentage done: 14.27%, estimated end time: 11:47
BR0001I *******___________________________________________
BR0202I Saving /oracle/ANP/sapdata2/sr3_9/sr3.data9
BR0203I to /dev/rmt0.1 ...
BR0278E Command output of 'LANG=C dd obs=1024K bs=1024K if=/oracle/ANP/sapdata2/sr3_9/sr3.data9 of=/dev/rmt0.1':
dd read error: I/O error
462+0 records in
462+0 records out
BR0280I BRBACKUP time stamp: 2010-08-27 11.03.36
BR0279E Return code from 'LANG=C dd obs=1024K bs=1024K if=/oracle/ANP/sapdata2/sr3_9/sr3.data9 of=/dev/rmt0.1': 2
BR0222E Copying /oracle/ANP/sapdata2/sr3_9/sr3.data9 to/from /dev/rmt0.1 failed due to previous errors
BR0280I BRBACKUP time stamp: 2010-08-27 11.03.41
BR0317I 'Alter tablespace PSAPSR3 end backup' successful
BR0056I End of database backup: bedziydp.ant 2010-08-27 11.03.36
BR0280I BRBACKUP time stamp: 2010-08-27 11.03.41
BR0054I BRBACKUP terminated with errors
Warm Regards
Ahsan

Hi,
since you are getting a read error, it might as well be, that your datafile is defective.
Try the same dd-command to /dev/null, to see if it is possible to read the entire file.
First make sure that your null-device is existing, otherwise you might face a root-fs full problem.
dd obs=1024K bs=1024K if=/oracle/ANP/sapdata2/sr3_9/sr3.data9 of=/dev/null
or try a dbverify on it, which would also read the entire file and do a checksum test.
brbackup -c -u / -m /oracle/ANP/sapdata2/sr3_9/sr3.data9 -t online -w only_dbv
Good luck
Volker

Whole database online + redo log backup

Hello all,
we are running SAP on a Oracle Database and doing a daily backup.
In the DBA Planing Calendar, we do have the action
Whole database online + redo log backup
What exactly does that mean?
Thanks,
Anne

This backup will save the CONTENT of the database only, not the database software itself.
To get a full consistent backup you need to backup more things if you want to have everything - depending on the operating system:
On Unix you will need to backup the software directory (/oracle*, oraInventory, oratab (depending on the location)) etc.
On Windows you will need to backup <letter>:\oracle, the registry keys and more things.
However, in case of a recovery you can also install the software after an OS installation and then restore it from tape.
Markus

Whole database offline + redo log backup Scheduling failed

Hi Experts,
         In DB13 I have the following Issue, Whole database offline + redo log backup Scheduling failed.
How to solve this.

Hi,
        Below is the Log details,
BR0120I Control files
File                                                Size   Id.      Device Link    Type
/oracle/PRD/origlogA/cntrl/cntlrPRD.dbf         13975552    0      5578783 NOLINK FILE
/oracle/PRD/origlogB/cntrl/cntrlPRD.dbf         13975552    0      5578784 NOLINK FILE
/oracle/PRD/sapdata1/cntrl/cntrlPRD.dbf         13975552    0      5578772 NOLINK FILE
BR0616I Tablespaces in table TSORA for SAP owner SAPSR3:
PSAPSR3, PSAPSR3700, PSAPSR3USR
BR0227E Not enough disk space in /test123/PRDBK for backup, missing at least 149478.274 MB
BR0056I End of database backup: behzgxph.afd 2012-02-28 03.05.40
BR0280I BRBACKUP time stamp: 2012-02-28 03.05.40
BR0054I BRBACKUP terminated with errors
BR0280I BRBACKUP time stamp: 2012-02-28 03.05.40
BR0291I BRARCHIVE will be started with options '-U -jid ALGOF20110129030500 -d disk -c force -p initPRD.sap -sd'
BR0280I BRBACKUP time stamp: 2012-02-28 03.06.09
BR0292I Execution of BRARCHIVE finished with return code 0

Backup Not Starting for 'Whole database offline + redo log backup' @ DB13

Hi Experts,
I am not able to perform 'Whole database offline + redo log backup' by DB13.
I have recently configured my 'init<SID>.sap' to take 'Whole database online + redo log backup' and its working perfectly fine.
I tried taking test backup for 'Whole database offline + redo log backup' but it didn't even started.
Thus I created another profile with name init<SID>back.sap and changed the Parameter
from 'backup_type = online' to 'backup_type = offline' and also tried by 'backup_type = offline_force'
rest all parameters being same as the profile init<SID>.sap
Kindly Suggest as I need to take set the backup Strategy as Mon-Fri -> 'Whole database offline + redo log backup' and Sat -> 'Whole database offline + redo log backup'
One more Query : While taking the redo log backup by DB13 why is it that some times it only saves the Files and some time it
saves and delete the files from the '/oracle/<SID>/oraarch' location. Please throw some light over this matter also.
Thanks,
Jitesh

Hi Mr Bhavik,
Thanks for your reply.. Here are the details you have asked for.
1.My SAP BASIS Patch Level is : 10. ( We shall be updating it by the end of this Year)
2. Br*tools version is :
BRTOOLS   7.00 (11)
kernel release    700
patch level   11
3. I don't have any file with name alert<dbsid>.log file (located at /oracle/<SID>/saptrace/background/) but i do have alert_<SID>.log
I execute the command more -p G alert_JMD.log
after my 'Whole database offline + redo log backup' again failed at DB13 but I was not able to see any specific complains while executing the above action.
I got the Error Detailed Log in DB13 as :
Detail log:                    beeneedv.aft
BR0051I BRBACKUP 7.00 (20)
BR0055I Start of database backup: beeneedv.aft 2010-11-08 13.16.43
BR0484I BRBACKUP log file: /oracle/JMD/sapbackup/beeneedv.aft
BR0280I BRBACKUP time stamp: 2010-11-08 13.16.43
BR0261E BRBACKUP cancelled by signal 13
BR0056I End of database backup: beeneedv.aft 2010-11-08 13.16.44
BR0280I BRBACKUP time stamp: 2010-11-08 13.16.45
BR0054I BRBACKUP terminated with errors
4. No I have not yet Tried 'execute such Offline+REdo log backups using brback command', will Try and post it Definately
5. Query : select grantee, granted_role from dba_role_privs;
result :
SQL> select grantee, granted_role from dba_role_privs;
GRANTEE                        GRANTED_ROLE
SYS                            SAPDBA
SYS                            EXP_FULL_DATABASE
SYS                            CONNECT
IMP_FULL_DATABASE              SELECT_CATALOG_ROLE
DBSNMP                         OEM_MONITOR
SAPSR3                         CONNECT
OPS$SAPSERVICEJMD              SAPDBA
SYS                            SELECT_CATALOG_ROLE
DBA                            DELETE_CATALOG_ROLE
DBA                            EXECUTE_CATALOG_ROLE
SYSTEM                         DBA
GRANTEE                        GRANTED_ROLE
OPS$ORAJMD                     SAPDBA
SAPDBA                         GATHER_SYSTEM_STATISTICS
SYS                            SCHEDULER_ADMIN
SYS                            AQ_USER_ROLE
SYS                            GATHER_SYSTEM_STATISTICS
SYS                            DELETE_CATALOG_ROLE
DBA                            GATHER_SYSTEM_STATISTICS
DBA                            IMP_FULL_DATABASE
EXECUTE_CATALOG_ROLE           HS_ADMIN_ROLE
IMP_FULL_DATABASE              EXECUTE_CATALOG_ROLE
OPS$JMDADM                     CONNECT
GRANTEE                        GRANTED_ROLE
SYS                            LOGSTDBY_ADMINISTRATOR
SYS                            EXECUTE_CATALOG_ROLE
SYS                            RESOURCE
DBA                            SCHEDULER_ADMIN
DBA                            SELECT_CATALOG_ROLE
EXP_FULL_DATABASE              EXECUTE_CATALOG_ROLE
SAPDBA                         SELECT_CATALOG_ROLE
SYS                            SAPCONN
SYS                            OEM_ADVISOR
SYS                            IMP_FULL_DATABASE
SELECT_CATALOG_ROLE            HS_ADMIN_ROLE
GRANTEE                        GRANTED_ROLE
OUTLN                          RESOURCE
LOGSTDBY_ADMINISTRATOR         RESOURCE
SAPSR3                         RESOURCE
OPS$SAPSERVICEJMD              RESOURCE
SYS                            RECOVERY_CATALOG_OWNER
DBA                            EXP_FULL_DATABASE
EXP_FULL_DATABASE              SELECT_CATALOG_ROLE
TSMSYS                         RESOURCE
OPS$ORAJMD                     RESOURCE
SAPCONN                        SELECT_CATALOG_ROLE
SYS                            OEM_MONITOR
GRANTEE                        GRANTED_ROLE
SYS                            AQ_ADMINISTRATOR_ROLE
SYS                            DBA
SYSTEM                         AQ_ADMINISTRATOR_ROLE
OPS$ORAJMD                     CONNECT
OPS$JMDADM                     SAPDBA
OPS$JMDADM                     RESOURCE
SAPSR3                         SAPCONN
SYS                            HS_ADMIN_ROLE
SYSTEM                         SAPDBA
OPS$SAPSERVICEJMD              CONNECT

Standby database SRL & Online logs

Hi,
I have just tried my hand at building a Physical standby database in Oracle 10gR2 using RMAN. I will detail out the steps that i have performed before asking my question.
I configured every pre-requisite and i did not create any SRL's on primary before building a standby database. I am using LGWR ASYNC for redo transmission. I have configured FAL_CLIENT and FAL_SERVER. Protection mode is MAX PERFORMANCE and it is on Solaris 10 x86_64
1. Took a RMAN full backup
and created a standby control file as
SQL> alter database create standby controlfile as '/tmp/standby.ctl';
2. On another server, I copied the pfile, standby controlfile (renamed it) from primary and mounted the database.
sqlplus /as sysdba'
SQL> startup mount pfile='...';
rman target /
RMAN> restore database;
SQL> alter database recover managed standby database disconnect from session;
Everything worked and MRP was applying the archived logs as they were received from the primary. But, i have seen the SRL's created with default names on the primary database & standby database by Oracle even though i did not explicitly create them. Is this a normal behaviour? I saw them using v$standby_log.
As a Physical standby database will not use any ONLINE REDO LOGS and i haven't created any with the procedure i have used. i have performed a SWITCHOVER, which has worked with out any problem. My question here is
1. How did Oracle open the database database when there were no redo logs physically present on the standby site? Is this a normal behavior in a standby environment where Oracle creates ONLINE REDO LOG files for a Standby database being transitioned to Primary whenever a SWITCHOVER or FAILOVER occurs? If this is the case, it is obvious that Oracle will take the LOG SEQUENCE from the last applied ARCHIVED LOG and will start the ONLINE LOG from that sequence?
Please correct me if i have understood anything wrong here or if i have configured anything wrong. But with the above configuration the Standby database worked perfectly well and switchover was successful too.
Thanks,
Harris.

Correction: I have not created the Standby Database using RMAN but only performed a FULL backup, which i have restored before starting the MRP.

10gR2 Logical Standby database not applying logs

No errors are appearing in the logs and I've started the apply process :ALTER DATABASE START LOGICAL STANDBY APPLY but when I query dba_logstdby_log, none of the logs for the last 4 days shows as applied and the first SCN is still listed as current. Any thoughts on where I should start looking?
the latest event in DBA_LOGSTDBY_EVENTS is the startup of the log mining and apply.
I do not have standby redo logs so I cannot do real time apply, though I am looking to implementing this. Obviously, this is pretty new to me.

Sorry I didn't mention this before, the logs are being transferred, I verified their location on the os and it matches the location in the dba_logstdby_log view.

Problem in creating database -Missing Redo log file

I am try to create a new database using DBCA .While creating a database it shows the error oracle instance terminated.Force Disconnected.
My alert log file is
Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/u01/app/oracle/oradata/oracl/redo01.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Wed Nov 06 10:07:27 2013
Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/oracl/redo02.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/u01/app/oracle/oradata/oracl/redo03.log'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
Wed Nov 06 10:07:38 2013
Setting recovery target incarnation to 2
Wed Nov 06 10:07:38 2013
Assigning activation ID 1876274518 (0x6fd5ad56)
Thread 1 opened at log sequence 1
Current log# 1 seq# 1 mem# 0: /u01/app/oracle/oradata/oracl/redo01.log
Successful open of redo thread 1
Wed Nov 06 10:07:38 2013
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Wed Nov 06 10:07:38 2013
SMON: enabling cache recovery
Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc (incident=1345):
ORA-00600: internal error code, arguments: [kpotcgah-7], [12534], [ORA-12534: TNS:operation not supported
Incident details in: /u01/app/oracle/diag/rdbms/oracl/oracl/incident/incdir_1345/oracl_ora_5424_i1345.trc
Wed Nov 06 10:07:46 2013
Trace dumping is performing id=[cdmp_20131106100746]
Errors in file /u01/app/oracle/diag/rdbms/oracl/oracl/trace/oracl_ora_5424.trc:
ORA-00600: internal error code, arguments: [kpotcgah-7], [12534], [ORA-12534: TNS:operation not supported
Error 600 happened during db open, shutting down database
USER (ospid: 5424): terminating the instance due to error 600
Instance terminated by USER, pid = 5424
ORA-1092 signalled during: alter database "oracl" open resetlogs...
ORA-1092 : opiodr aborting process unknown ospid (5424_47935551851664)
Wed Nov 06 10:07:47 2013
ORA-1092 : opitsk aborting process
251,1 95%

>I am try to create a new database using DBCA
>Please help me to resolve this issue.My redo log file was missing
DROP and recreate the database. It is a *new* database without any data.
Check what datafile locations and redo log file locations you specify when creating the new database. Check if you have permissions and enough disk space.
Hemant K Chitale

Urgent Help - Redo Log problem

Hi,
I have an implementation of Oracle 9i. Presently I have got 3 redo log groups with 2 members each. There are lot of updation and insertion of records going on with few tables. When the load increases the DB lands in a hang state and in the Log I get this message
Thread 1 cannot allocate new log, sequence 234
All online logs needed archiving
Current log# 1 seq# 233 mem# 0: D:\ORACLE\ORADATA\ORCL\REDO01.LOG
Current log# 1 seq# 233 mem# 1: D:\ORACLE\ORADATA\ORCL\REDO04.LOG
Can any one help me in solving this problem. I tried to Switch the log files but as they already are waiting for archiving so no use.
Any help on this will be highly helpfull to me as I am in Live environment.
Arvind

The way the log groups work is.
Log Writer(lgwr) starts writing to group 1. When group 1 fills up, it switches to group 2. When lgwr starts writing to group 2, the Archiver (arc) wakes up and starts writing group 1 to the archive file. When group 2 fills up lgwr start writing group 3 and arc archives group 2 once it has finished writing group 1. When group 3 fills up, lgwr starts writing to group 1 again, assuming that arc has finished writing group 1 to the archive.
In your case, it appears that arc is still writing group 1 when lgwr wants to use it again, so the database stalls until arc is finished writing group 1.
Fundamentally you have two choices. You can increase the size of each file in each log group, so they will fill up less often. However, this will also make arc take longer to archive the group. If you can gain enough time based on slower filling to offset the slower writing you should be ok.
The other option is to add a few more groups of the same size as the existing groups. This will give lgwr more groups to use before needing to start re-using earlier groups.
Typically, in our systems we run between 4 and 6 64M log groups and never see these hangs.
HTH
John

Whole Database Online + redo log backup: How Long?

Hi gurus,
There's something I want to ask about online backup with redo log.
If i'm correct, redo log file is created everytime there's operation that change datafile right?
If i schedule this type of backup everyday, it means it will backup all datafiles, along with redo log file when transaction take places, at my pre-defined hours, right?
Then here's what i'm confused about. When will this backup process finished? Is it when all the datafiles have been backed up? Then how about the redo log files? If there are users that keep making transaction (therefore make change to datafiles), new redo log files will be created on disk, and that will prevent the backup process to finish. Then when will this cycle come to an end?
Please confirm if my grasp about oracle online backup is correct or not, and provide explanation to satisfy my curiousity.
Thanks gurus,
Edited by: Bobby Gunawan on Jan 6, 2009 10:16 AM

Hello Fidel,
i am feeling honored
> Keep in mind that the only thing where a DBA cannot make mistakes is restore/recovery and this depends on your backups
In general i would say you are right, but i have seen already one case where this statement is not true.
Some time ago i got a call from a colleague where his database crashed, the online redolog files were corrupted and the recovery was not working.
If you don't look really close at this point you are in trouble and can not continue the recovery. Let explain this on a example.
This demonstration is done on an oracle 10.2.0.4, but it work on every other version too.
Let's simulate a crash
SQL> shutdown abort;
Corrupt/delete a specifc redolog file
SQL> startup
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/oracle/TST/oradata/redolog/redo03.log'
ORA-27037: unable to obtain file status
Ok - so far so good, lets check the groups and files
SQL> select GROUP#, STATUS, MEMBER from v$logfile where TYPE = 'ONLINE';
    GROUP# STATUS MEMBER
         1         /oracle/TST/oradata/redolog/redo01.log
         2         /oracle/TST/oradata/redolog/redo02.log
         3         /oracle/TST/oradata/redolog/redo03.log
SQL> select * from v$log;
    GROUP#    THREAD# SEQUENCE#      BYTES    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIM
         1          1         95   52428800          1 NO CURRENT                5117817 06-JAN-09
         3          1         94   52428800          1 YES ACTIVE                 5117814 06-JAN-09
         2          1         93   52428800          1 YES ACTIVE                 5112855 15-DEC-08
What's the situation?
The online redolog file of group 3 is lost/corrupted and this group is needed to perform a complete recovery (see status ACTIVE).
But you are lucky, because of this group 3 is already archived - so you can perform a complete recovery.
Now let's perform a complete recovery but with UNTIL clause (because we need to jump between the online and archived redologfiles)
SQL> recover database until cancel;
ORA-00279: change 5116194 generated at 01/06/2009 21:06:48 needed for thread 1
ORA-00289: suggestion : /oracle/TST/oraarch/TST_1_93_6b8c0516_666969185.arc
ORA-00280: change 5116194 for thread 1 is in sequence #93
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 5117814 generated at 01/06/2009 21:08:47 needed for thread 1
ORA-00289: suggestion : /oracle/TST/oraarch/TST_1_94_6b8c0516_666969185.arc
ORA-00280: change 5117814 for thread 1 is in sequence #94
ORA-00278: log file '/oracle/TST/oraarch/TST_1_93_6b8c0516_666969185.arc' no longer needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 5117817 generated at 01/06/2009 21:08:51 needed for thread 1
ORA-00289: suggestion : /oracle/TST/oraarch/TST_1_95_6b8c0516_666969185.arc
ORA-00280: change 5117817 for thread 1 is in sequence #95
ORA-00278: log file '/oracle/TST/oraarch/TST_1_94_6b8c0516_666969185.arc' no longer needed for this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
/oracle/TST/oradata/redolog/redo01.log
Log applied.
Media recovery complete.
Now execute an OPEN NORESETLOGS accidentally (maybe the dba think it is not necessary because of the complete recovery) and try an OPEN RESETLOGS after:
SQL> alter database open noresetlogs;
alter database open noresetlogs
ERROR at line 1:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: '/oracle/TST/oradata/redolog/redo03.log'
ORA-27037: unable to obtain file status
SQL> alter database open resetlogs;
alter database open resetlogs
ERROR at line 1:
ORA-01139: RESETLOGS option only valid after an incomplete database recovery
So now you are lost.. you can't execute an UNTIL CANCEL anymore which would be needed to perform a successful OPEN RESETLOGS.
In this special case you can do mistakes and you have to restore the whole database and perform the same recovery again and end with OPEN RESETLOGS.
Just for information
Regards
Stefan

Emergency: cannot start database because redo logs have been deleted

Hi. Ok, so the redo logs are deleted and I don't have a backup. Fine, whatever. I am trying to just start my database and start the logging from scratch.
ORA-00320: cannot read file header from log 1 of thread 1
ORA-00312: online log 1 thread 1: '/u01/oradata/orcl/redo01.log'
ORA-27069: attempt to do I/O beyond the range of the file
Here's what my log files look like:
select group#, thread#, status from v$log;
GROUP# THREAD# STATUS
1 1 ACTIVE
4 1 UNUSED
3 1 UNUSED
2 1 CURRENT
I have group 3 and 4 just sitting there. I would love to switch logging from group 1 to group 4 (which I just created) so I can drop the corrupted group 1 but when I try:
SQL> alter system switch logfile;
alter system switch logfile
ERROR at line 1:
ORA-01109: database not open
Of course the database is not open because I can't get it started. So, I'm in kind of a catch 22.

I think you need to restore your database. http://download.oracle.com/docs/cd/E11882_01/backup.112/e10642/osadvsce.htm#CACFFJFB says:
>
Losing an Active Online Redo Log Group
If the database is still running and the lost active redo log is not the current log, then issue the ALTER SYSTEM CHECKPOINT statement. If the operation is successful, then the active redo log becomes inactive, and you can follow the procedure in "Losing an Inactive Online Redo Log Group". If the operation is unsuccessful, or if your database has halted, then perform one of procedures in this section, depending on the archiving mode.
The current log is the one LGWR is currently writing to. If a LGWR I/O operation fails, then LGWR terminates and the instance fails. In this case, you must restore a backup, perform incomplete recovery, and open the database with the RESETLOGS option.

RMAN-05001 - RMAN-03002 | Duplicating Database fails | Redo-Logs

Sorry guys,
first of all...my english is the worsteds you´ve ever seen...
I got some kind of problem using rman duplicating a DB called cs2t into cs2b.
Starting Duplicate Db at 17.05.2006 07:54:10
released channel: t1
released channel: t2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/17/2006 07:54:10
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo05.log conflicts with a file used by the target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo04.log conflicts with a file used by the target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo03.log conflicts with a file used by the target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo02.log conflicts with a file used by the target database
RMAN-05001: auxiliary filename /oracle/orasys/cs2t/redo01.log conflicts with a file used by the target database
Recovery Manager complete.
Therefore I found on metalink some informations about using UNTIL TIME.
I´ve tryed it....but now...there are some other erros on my rman.log
executing command: SET until clause
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of set command at 05/17/2006 08:22:14
ORA-01830: date format picture ends before converting entire input string
Recovery Manager complete.
and now: no ideas anymore...i´ve googled for it about 3hours...nothing found....may anybody help me - please?
P.S. I hope you´ll understand anything i´ve wrote into this message ;-)

hi,
you have to use db_file_name_convert and db_log-filename_convert parameter in the auxiliary database parameter file and use nofilenamecheck parameter with the duplicate command.
This is also recommended that you create new redo og files for auxiliary databse just like --
RMAN> run{
2> allocate auxiliary channel c1 device type disk;
3> duplicate target database to prod1 pfile='c:\oracle\ora92\database\initprod1.ora'
4> logfile 'c:\oracle\oradata\prod1\redo01.log' size 50m,
5> 'c:\oracle\oradata\prod1\redo02.log' size 50m,
6> 'c:\oracle\oradata\prod1\redo03.log' size 50m ;}
i hope it solve your problem..
Navneet

Redo log problem

Hello,
I had 12 log groups with 2 member in each group, size og 60mb.
I was adding new groups with larger members and deleting old groups .
I droped 10 old groups and i after some time while querying v$log , I found that those 2 old groups are constantly either in status current or active. so i cant drop them, I was getting ora message which says that i cant drop that group because its needed for instance recovery.
I tryied forcing log switch, i am getting message log switch succesfuly completed, but it wont help, they were still active or current.Like those 2 old groups are in some endles loop.
Please, I would be very greatful for any suggestions on this issue, that is how to get those groups in inactive status so i could drop them.
thx

I droped 10 old groups and i after some time while querying v$log , I found that those 2 old groups are constantly either in status current or active. so i cant drop them,Create other groups before droppping these two last. You cannot have less than two redolog group.
Anyway, 12 redolog group seems to me much, have you really need so much ?
Nicolas.

Redo log files are not applying to standby database

Hi everyone!!
I have created standby database on same server ( windows XP) and using oracle 11g . I want to synchronize my standby database with primary database . So I tried to apply redo logs from primary to standby database as follow .
My standby database is open and Primary database is not started (instance not started) because only one database can run in Exclusive Mode as DB_NAME is same for both database. I run the following command on the standby database.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
It returns "Database altered" . But when I checked the last archive log on primary database, its sequence is 189 while on standby database it is 177. That mean archived redo logs are not applied on standby database.
The tnsnames.ora file contains entry for both service primary & standby database and same service has been used to transmit and receive redo logs.
1. How to resolve this issue ?
2.Is it compulsory to have Primary database open ?
3. I have created standby control file by using command
SQL> ALTER DATABASE CREATE STANDBY CONTROLFILE AS ‘D:\APP\ORACLE\ORADATA\TESTCAT\CONTROLFILE\CONTROL_STAND1.CTL‘;
So database name in the standby control file is same as primary database name (PRIM). And hence init.ora file of standby database also contains DB_NAME = 'PRIM' parameter. I can't change it because it returns error of mismatch database name on startup. Should I have different database name for both or existing one is correct ?
Can anybody help me to come out from this stuck ?
Thanks & Regards
Tushar Lapani

Thank you Girish. It solved my redo apply problem. I set log_archive_dest parameter again and then I checked archive redo log sequence number. It was same for both primary and standby database. But still table on standby database is not being refresh.
I did following scenario.
1. Inserted 200000 rows in emp table of Scott user on Primary database and commit changes.
2. Then I synchronized standby database by using Alter database command. And I also verify that archive log sequence number is same for both database. It mean archived logs from primary database has been applied to standby database.
3. But when I count number of rows in emp table of scott user on standby database, it returns only 14 rows even of redo log has been applied.
So my question is why changes made to primary database is not reflected on standby database although redo logs has been applied ?
Thanks

The file structure online redo log, archived redo log and standby redo log

I have read some Oracle documentation for file structure and settings in Data Guard environment. But I still have some doubts. What is the best file structure or settings in Oracle 10.2.0.4 on UNIX for a data guard environment with 4 primary databases and 4 physical standby databases. Based on Oracle documents, there are 3 redo logs. They are: online redo logs, archived redo logs and standby redo logs. The basic settings are:
1. Online redo logs --- This redo log must be on Primary database and logical standby database. But it is not necessary to be on physical standby database because physical standby is not open. It doesn't generate redo log. However, if don't set up online redo log on physical standby, when primary failover and switch standby as primary. How can standby perform without online redo logs? In my standby databases, online redo logs have been set up.
2. Archived redo logs --- It is obviously that primary database, logical and physical standby database all need to have this log file being set up. Primary use it to archive log files and ship to standby. Standby use it to receive data from archived log and apply to database.
3. Standby redo logs --- In the document, it says A standby redo log is similar to an online redo log, except that a standby redo log is used to store redo data received from another database. A standby redo log is required if you want to implement: The maximum protection and maximum availability levels of data protection and Real-time apply as well as Cascaded destinations. So it seems that this standby redo log only should be set up on standby database, not on primary database. Am my understanding correct? Because I review current redo log settings on my environment, I have found that Standby redo log directory and files have been set up on both primary and standby databases. I would like to get more information and education from experts. What is the best setting or structure on primary and standby database?

FZheng:
Thanks for your input. It is clear that we need 3 type of redo logs on both databases. You answer my question.
But I have another one. In oracle ducument, it says If you have configured a standby redo log on one or more standby databases in the configuration, ensure the size of the current standby redo log file on each standby database exactly matches the size of the current online redo log file on the primary database. It says: At log switch time, if there are no available standby redo log files that match the size of the new current online redo log file on the primary database. The primary database will shut down
My current one data gurard envirnment setting is: On primary DB, online redo log group size is 512M and standby redo log group size is 500M. On the standby DB, online redo log group size is 500M and standby redo log group size is 750M.
This was setup by someone I don't know. Is this setting OK? or I should change Standby Redo Log on standby DB to 512M to exactly meatch with redo log size on primary?
Edited by: 853153 on Jun 22, 2011 9:42 AM

Physical standby database standby redo log problem

Similar Messages

Maybe you are looking for