STANDBY LOGFILE SIZE

Hi
How much the size of Standby Log files should be espically on 10g while Configuring Data Guard?
Regards
Thunder2777

The size of the current standby redo log files must exactly match the size of the current primary database online redo log filesFrom:
http://docs.oracle.com/cd/B19306_01/server.102/b14239/create_ps.htm

Similar Messages

How to specify logfile size at the time of adding to a member.

Hi All,
I am in the process of upgrading Oracle 9.0 to 10.1.
I am following manual upgrad process.As per the recomendation from the pre-upgrade information script,i need to recreate redo-log files.
Logfiles: [make adjustments in the current environment]
--> E:\ORACLE\ORADATA\PRODB229\REDO03.LOG
.... status="INACTIVE", group#="1"
.... current size="1024" KB
.... suggested new size="10" MB
--> E:\ORACLE\ORADATA\PRODB229\REDO02.LOG
.... status="INACTIVE", group#="2"
.... current size="1024" KB
.... suggested new size="10" MB
--> E:\ORACLE\ORADATA\PRODB229\REDO01.LOG
.... status="CURRENT", group#="3"
.... current size="1024" KB
.... suggested new size="10" MB
WARNING: one or more log files is less than 4MB.
Create additional log files larger than 4MB, drop the smaller ones and then
upgrade.i can add redo member by the below command,but not able to specicy the size as 10M.I did some googling but no luck with that..
SQL> ALTER DATABASE ADD LOGFILE MEMBER 'E:\oracle\oradata\prodb229\REDO01.rdo' T
O GROUP 1;
but it fails
ALTER DATABASE ADD LOGFILE MEMBER 'E:\oracle\oradata\prodb229\REDO01.rdo' TO GROUP 2 SIZE 10M;
ERROR at line 1:
ORA-00933: SQL command not properly ended
~Thnx

If you add a logfile to an existing group, you cannot specify the size for that file.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_1004.htm#i2079942
<quote>
ADD [STANDBY] LOGFILE MEMBER Clause Use the ADD LOGFILE MEMBER clause to add new members to existing redo log file groups. Each new member is specified by 'filename'. If the file already exists, it must be the same size as the other group members, and you must specify REUSE. If the file does not exist, Oracle Database creates a file of the correct size. You cannot add a member to a group if all of the members of the group have been lost through media failure.
<quote>

Can't switch standby logfiles to status=active

Hi DBA's
I'm trying to create logical standby on 10.2 on fedora 6 on manual http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/create_ps.htm#g88234
I can't create proper working standby redo logs.
ALTER DATABASE ADD STANDBY LOGFILE GROUP 4
('/u01/app/oracle/oradata/ORCL/onlinelog/log4a.log',
'/u01/app/oracle/flash_recovery_area/ORCL/onlinelog/log4b.log') SIZE 50M;
then create the rest of standby redos and switch logfile:
ALTER SYSTEM SWITCH LOGFILE;
when:
SQL> SELECT GROUP#,THREAD#,SEQUENCE#,ARCHIVED,STATUS FROM V$STANDBY_LOG;
GROUP# THREAD# SEQUENCE# ARC STATUS
4 0 0 YES UNASSIGNED
5 0 0 YES UNASSIGNED
6 0 0 YES UNASSIGNED
What to do?
Edited by: val75 on Jun 21, 2009 11:08 PM

try switch log at primay
please try to run this Command and then open the primary database.
alter database set standby database to maximize performance;
alter database open;

Standby logfiles

In the following doc: http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/log_transport.htm#BABCBEGJ
it says:
For example, assume that the redo log on the redo source database has two redo log groups and that each of those contain one 500 MB redo log file. In this case, the standby redo log should have at least 3 standby redo log groups to satisfy the requirement that a standby redo log must have at least one more redo log group than the redo log at the redo source database.
The following SQL statements might be used to create a standby redo log that is appropriate for the previous scenario:
ALTER DATABASE ADD STANDBY LOGFILE
('/oracle/dbs/slog1.rdo') SIZE 500M;
ALTER DATABASE ADD STANDBY LOGFILE
('/oracle/dbs/slog2.rdo') SIZE 500M;
ALTER DATABASE ADD STANDBY LOGFILE
('/oracle/dbs/slog3.rdo') SIZE 500M;
The doc says there needs to be one more group and then demonstrates creating no seperate groups. Did they mean to say one more file or did they mean to create groups such as this:
ALTER DATABASE ADD STANDBY LOGFILE GROUP 1...
ALTER DATABASE ADD STANDBY LOGFILE GROUP 2...
ALTER DATABASE ADD STANDBY LOGFILE GROUP 3....

In the example the primary database has two log groups, and then they create 3 standby log groups on the standby. This is exactly what they recommend (standby = primary + 1).

Standby logfile missing error

Hello all,
I am getting this following error in standby alertlog file.
ORA-00313: open failed for members of log group 8 of thread 2
ORA-00312: online log 8 thread 2: '+DG_FLASH/hsstl/onlinelog/group_8.273.779638759'
ORA-17503: ksfdopn:2 Failed to open file +DG_FLASH/hsstl/onlinelog/group_8.273.779638759
ORA-15012: ASM file '+DG_FLASH/hsipstl/onlinelog/group_8.273.779638759' does not exist
ORA-00312: online log 8 thread 2: '+DG_DATA/hsstl/onlinelog/group_8.1766.779638759'
ORA-17503: ksfdopn:2 Failed to open file +DG_DATA/hsstl/onlinelog/group_8.1766.779638759
ORA-15012: ASM file '+DG_DATA/hsipstl/onlinelog/group_8.1766.779638759' does not exist
When i manually check the diskgroup '+DG_FLASH, +DG_DATA, i can see the group_8 file with some other numbers.
Kindly let me know how to proceed for that. oracle 11g database, standalone standby database in aix box
My guess is control file is still thinking that the group 8 file is present and looks for it when starting the standby, but actually that file is not there in the diskgroup. instead some other filename is there for the same group.
Either i want to update the control file about the new log group 8, or drop the log 8 group, delete the log 8 group files from the disgroups +DG_FLASH, +DG_DATA and create a new log 8 group
Kindly suggest
Regards,

Test
SQL> Select GROUP#, THREAD#, SEQUENCE#, BYTES from v$standby_log;
GROUP# THREAD# SEQUENCE# BYTES
4 1 0 52428800
5 1 1327 52428800
6 1 0 52428800
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> ALTER DATABASE ADD STANDBY LOGFILE GROUP 7 '/u01/app/oracle/oradata//redo07.log' SIZE 50M;
Database altered.
SQL> alter database recover managed standby database disconnect from session;
Database altered.
SQL> Select GROUP#, THREAD#, SEQUENCE#, BYTES from v$standby_log;
GROUP# THREAD# SEQUENCE# BYTES
4 1 0 52428800
5 1 1327 52428800
6 1 0 52428800
7 0 0 52428800
ALTER DATABASE CLEAR LOGFILE GROUP 7;
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 7;
Database altered.
SQL> alter database recover managed standby database disconnect from session;
Database altered.
SQL> Select GROUP#, THREAD#, SEQUENCE#, BYTES from v$standby_log;
GROUP# THREAD# SEQUENCE# BYTES
4 1 0 52428800
5 1 1327 52428800
6 1 0 52428800
7 0 0 52428800
SQL> /
GROUP# THREAD# SEQUENCE# BYTES
4 1 1330 52428800
5 1 0 52428800
6 1 0 52428800
7 0 0 52428800
What I noticed is no matter how many switches I do the Standby only uses group 4 and 5. If I recreate with a Thread number it seems to work.
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> ALTER DATABASE DROP STANDBY LOGFILE GROUP 7;
Database altered.
SQL> !rm /u01/app/oracle/oradata//redo07.log
SQL> ALTER DATABASE ADD STANDBY LOGFILE THREAD 1 GROUP 7 '/u01/app/oracle/oradata//redo07.log' SIZE 50M;
Database altered.
SQL> alter database recover managed standby database disconnect from session;
Database altered.
SQL> Select GROUP#, THREAD#, SEQUENCE#, BYTES from v$standby_log;
GROUP# THREAD# SEQUENCE# BYTES
4 1 0 52428800
5 1 1343 52428800
6 1 0 52428800
7 1 0 52428800
SQL>
Check
SQL> select GROUP#,BYTES/1024/1024/1024 , STATUS, FIRST_TIME,NEXT_TIME from v$standby_log;
GROUP# BYTES/1024/1024/1024 STATUS FIRST_TIM NEXT_TIME
4 .048828125 UNASSIGNED
5 .048828125 ACTIVE 29-NOV-13
6 .048828125 UNASSIGNED
7 .048828125 UNASSIGNED
SQL>

Standby logfile issue

I created a dataguard, one primary database and one physical standby. The protection mode is maximum protection. My issue is: everytime when I archive a logfile in primary, it will write to standby logfile in standby logfile. Then the standby logfile status will show 'ACTIVE', and can't reuse it. if I need archive standby logfile in standby database, then I can get the standby logfile reuse?
Now if I add one more standby logfile in standby database, I can archive a logfile in primary. Then I can't archive another more in primary, unless i add one more standby logfile in standby.
thanks a lot,
kelvin

Thank you everyone. Yes mike, I already 'recover managed standby database using current logfile disconnect from session'. And Emre, I have 3 logfile groups in primary, every group has 2 members. I am using ASM for storage. in standby, at beginning, I created 4 standby groups(every one has 2 members and same size with primary logfile). But after a while, the primary database shut down. I checked alert log in primary, mention 'no available standby logfile to use'. So I added another 4 standby logfiles ......
So anybody know, for the standby logfile, if we need archive those logfiles. So primary can reuse and write log to these standby logfile when primary database do a 'archive log current'. Now I believe my primary database can't reuse those standby logfile in standby database, so I need to add one more, one more standby logfile..
Thanks a lot,
kelvin

Standby logfile

Since setting up RMAN control file autobckup on a dataguard set up I get the following message in the alertlog:-
Starting control autobackup
Sat May 07 01:04:27 2005
Control autobackup written to DISK device
handle 'CF_C-00'
Clearing standby activation ID 2115378951 (0x7e161f07)
The primary database controlfile was created using the
'MAXLOGFILES 9' clause.
There is space for up to 6 standby redo logfiles
Use the following SQL commands on the standby database to create
standby redo logfiles that match the primary database:
ALTER DATABASE ADD STANDBY LOGFILE 'srl1.f' SIZE 104857600;
ALTER DATABASE ADD STANDBY LOGFILE 'srl2.f' SIZE 104857600;
ALTER DATABASE ADD STANDBY LOGFILE 'srl3.f' SIZE 104857600;
ALTER DATABASE ADD STANDBY LOGFILE 'srl4.f' SIZE 104857600;
Can anyone tell me a bit more a bit what this message is saying and explain the pros/cons of adding these standby log files to the standby database??

Thanks for reply..I am really confused by this both the primary and standby have the same redologs set up (3 groups of 2 logs) so dont understand why it is asking me to add 4 logs to the standby? are these the same or different from the normal redo log groups? why is this message only appearing when the control file is autbacked up?

I missed to add Standby Logfile groups? What now?

Hi there
I have created a Standby database in a test environment using RMAN   (followed the procedure given here -> URL: Creating a Standby Database with Recovery Manager).
When I tried to start the recovery on Standby, I got the following error:
[code]
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT
ERROR at line 1:
ORA-38500: USING CURRENT LOGFILE option not available without stand
SQL> select NAME, OPEN_MODE, GUARD_STATUS, DATABASE_ROLE from v$database;
NAME      OPEN_MODE GUARD_S DATABASE_ROLE
PRIM      MOUNTED    NONE    PHYSICAL STANDBY
SQL>
[/code]
I missed the step to add standby logfile groups. Do I need to recreate the Standby database now? I mean, add standby logfile groups to Primary, then take full RMAN backup and recreate the standby database (following the procedure described in the URL above)?
I am using Oracle 10gR2 on OEL 5.8.
Please advise!
Best regards

OK thank you both - I have added the standby logfile groups both on Primary and Standby (mounted) database and I was able to successfully issue the following command:
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;
I hope this was the right thing to do under the circumstances, right?
And now there seems to be a gap:
PRIM_SQL> SELECT MAX(SEQUENCE#) FROM V$ARCHIVED_LOG;
MAX(SEQUENCE#)
            11
STDBY_SQL> SELECT MAX(SEQUENCE#) FROM V$LOG_HISTORY;
MAX(SEQUENCE#)
             9
I issued "alter system switch logfile" few times on the Primary but logs don't seem to be shipping? How to check this and fix?
EDIT: OK I checked the Primary alert log file and see following messages:
Error 1031 received logging on to the standby
Tue Jun 25 15:22:43 2013
Errors in file /u01/app/oracle/admin/prim/bdump/prim_arc0_6880.trc:
ORA-01031: insufficient privileges
PING[ARC0]: Heartbeat failed to connect to standby 'stan'. Error is 1031.
Tue Jun 25 15:27:43 2013
Error 1031 received logging on to the standby
Tue Jun 25 15:27:43 2013
Errors in file /u01/app/oracle/admin/prim/bdump/prim_arc0_6880.trc:
ORA-01031: insufficient privileges
PING[ARC0]: Heartbeat failed to connect to standby 'stan'. Error is 1031.
Tue Jun 25 15:32:43 2013
I do have password file both on Primary and Standby servers. What is this "ORA-01031: insufficient privileges" referring to?
EDIT#2:
I copied the password file from Primary DB server to Standby server (with same name "orapwprim" - previously I used "orapwstan" name for standby password file) and the "login issue" is resolved. But now I see following error in the alert log file on Primary:
PING[ARC0]: Heartbeat failed to connect to standby 'stan'. Error is 1031.
Tue Jun 25 15:48:08 2013
ARCH: Possible network disconnect with primary database
Any clues here?
EDIT#3:
Sorry I was a bit impatient I guess.The logs a re being shipped and applied now.
Thank you both!
Best regards
Message was edited by: user130038 (added alert log file info)
Message was edited by: user130038 (Added EDIT#2)
Message was edited by: user130038 (added EDIT#3)

Logfile size limit reached - logging stopped

From time to time, quite often, a pop-up window appears on my screen and says:Logfile size limit reached - logging stopped. I only can push "Accept" button or close it, but it rises again some time later. I haven't found any information on the web.

Hello,
I had this problem too, but I found the cause of it. It's comes from the extension 'IPLogger 1.6'.
This extension store, for every connexion, your IP adresse in a logfile, so after some times the file is full and the message "Logfile size limit reached" is displayed.
The best solution is to completely remove this extension, and replace it by similar one, like 'External IP'.
Now, the problem is solved for me :)
p.s. This problem should be considered as a bug for extension IPLogger. The logfile should be cleared when full instead of diplaying this annoyinf message !

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

I want to increase logfile size?

Good day,
frequent log switches occuer in the database. the following message displays in OEM recommendations
Increase the size of the log files to 327 M to hold at least 20 minutes of redo information.
kindly telll me how to increase file size of logfile?
thanks & Regards.

to increase the size, create new log files, check point the old and drop.
sql>select * from v$log
sql>select * from v$controlfile_record_section where type ='REDO LOG'
sql>alter database add logfile group 4 '/app/oracle/oradata/xxxx/redo04.log'
size 350M reuse;
sql>alter system switch logfile;
sql>alter system checkpoint;
Drop old logfiles.
Alter database drop logfile group 1;
note: if there are more than one gropus add same number of groups and delete all older groups

Increased logfile size and now get cannot allocate new log

Because we were archiving up to 6 and 7 times per minute, I increased our logfiles from size from 13M to 150M. I also increased the number of groups from 3 to 5.
Because we want to ensure recoverability within a certain timeframe, I also have a script that runs every 15 minutes and issues 2 commands: ALTER SYSTEM SWITCH LOGFILE; and ALTER SYSTEM CHECKPOINT;
I am now seeing in my alert.log file the following, almost every time we do a log switch.
Thread 1 cannot allocate new log, sequence 12380
Private strand flush not complete
No other changes have been made to the database.
Why would this now be doing this?
Should I not be doing both the ALTER SYSTEM SWITCH LOGFILE and the ALTER SYSTEM CHECKPOINT?
Is there something else I should be looking at?
Any suggestions/answers would be greatly appreciated.
Db version: 11.1.0.7
OS: OEL 5.5

Set the FAST_START_MTTR_TARGET parameter to the instance recovery time in seconds that you want...
ALTER SYSTEM SET LOG_ARCHIVE_MAX_PROCESSES=upto 10; this will make sure that the redo logs are copied faster....
The sizing redo log files can influence performance because DBWR, LGWR and ARCH are all working during high DML periods.
A too small online redo log file size can cause slowdowns from excessive DBWR and checkpointing behavior. A high checkpointing frequency and the "log file switch (checkpoint incomplete) can also cause slowdowns.
Add additional log writer processes (LGWR).
Ensure that the archived redo log filesystem resides on a separate physical disk spindle.
Put the archived redo log filesystem on super-fast solid-state disks.

Logfile size

i want shrink my logfile member size , so i do follow steps
first, add two groups as new which has one logfile member
second, switch logfile to new groups
third, drop old logfile groups
but there is an error 'ora-00312 group which deleted must archive' , how can i archive this group .

Hi
You can use any of these depending upon the requirement:
alter system archive log all;
alter system archive log current;
alter system archive log sequence 104;
Regards
null

Create ONLINE logfile in physical standby database

We have created a physical standby database with rman duplicate command on a remote server
"duplicate target database for standby dorecover nofilenamecheck"
When I see the standby server...Online logfiles are not created however its relevant entries are there in V$LOG and V$LOGFILE views.
I guess it is the default behaviour of duplicate command in RMAN and we can not specify LOGFILE clause when we create standby database.
Now the problem is we could not drop the online logfile on standby database since it's status is "CURRENT", "ACTIVE".
Since the ONLINE LOGFILE are not actually created , "ALTER DATABASE CLEAR LOGFILE GROUP " command returns with error as it could not find the file in the server.
So How we can drop the current/active online logfile and add new ones in standby db?

I'm assuming you have physical standby. Here are step I did in the past.
1) create a backup control file
2) bring the database back using the "recreate control file" it the trace file BUT you need to remove or comment out the line that has the corrupt or missing redo log file. And don't forget to add the tempfile after you recreate the controlfile
example:
alter database backup controlfile to trace;
STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "ORCL" NORESETLOGS FORCE LOGGING ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 '/oracledata/orcl/redo01.log' SIZE 200M,
GROUP 2 '/oracledata/orcl/redo02.log' SIZE 200M,
GROUP 3 '/oracledata/orcl/redo03.log' SIZE 200M,
# GROUP 3 '/oracledata/orcl/redo03.log' SIZE 200M
-- STANDBY LOGFILE
-- GROUP 10 '/oracledata/orcl/redostdby04.log' SIZE 200M,
-- GROUP 11 '/oracledata/orcl/redostdby05.log' SIZE 200M
DATAFILE
'/oracledata/orcl/system01.dbf',
'/oracledata/orcl/undotbs01.dbf',
'/oracledata/orcl/sysaux01.dbf',
'/oracledata/orcl/users01.dbf'
CHARACTER SET WE8ISO8859P1
If you just want to add the standby redo log then using this command.
alter database add standby logfile
'/<your_path>/redostdby01.log' size 200M reuse,

Adding logfile to primary/standby

Hi: I am on 10.2.0.3.
I have physiacl standby for my primary. Now for the performance reason I'm adding a few redo log groups (and increasing the size of each one) to the primary.
As far as I understand:
- I need to add one standby log file on the primary for each online log (group) I am adding.
- I need to add online log and standby log on the standby for each primary online log I am adding.
Question: since adding logs need to be done in the open mode, would read only be good for standby? Or I need to do something else?
TIA.

Standby Redo Logs Creation:
On primary database, execute --
sql> SELECT max (group#) from v$logfile;
sql> SELECT bytes from v$log;
sql> ALTER DATABASE ADD STANDBY LOGFILE GROUP 4 '/u01/app/oracle/oradata/abcredo4.log' SIZE 52428800;
sql> ALTER DATABASE ADD STANDBY LOGFILE GROUP 5 '/u01/app/oracle/oradata/abc/redo5.log' SIZE 52428800;
sql> ALTER DATABASE ADD STANDBY LOGFILE GROUP 6 '/u01/app/oracle/oradata/abc/redo6.log' SIZE 52428800;
You can create standby redo log files when primary database is open as well.
:)

STANDBY LOGFILE SIZE

Similar Messages

Maybe you are looking for