OraFAQ Forum: Data Guard » Redo apply

Home » Server Options » Data Guard » Redo apply

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

Redo apply [message #243713]

Fri, 08 June 2007 10:48

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

Hey Masters

I have 10g dataguard installed between a primary and a standby.

My dataguard looks like working fine.

BUT when i run the following.

ON PRIMARY

select sequence#,applied from v$archived_log order by sequence#;

Result:--

SEQUENCE# APP
---------- ---
930 YES
931 NO
931 YES
932 NO
932 YES
933 NO
933 YES
934 NO
934 YES
935 NO
935 YES

SEQUENCE# APP
---------- ---
936 NO
936 YES
937 NO
937 YES

But when i run the same on standby the result is like:-

SEQUENCE# APP
---------- ---
928 YES
929 YES
930 YES
931 YES
932 YES
933 YES
934 YES
935 YES
936 YES
937 YES
Now the question is I am confused with
936 NO
936 YES
937 NO
937 YES

why NO and Then YES ..
Is it some problem or what.??
Does somebody Have come across the same ..
I would be grateful if somebody helps

Thanks
&
Regards

j singh

Report message to a moderator

Re: Redo apply [message #243715 is a reply to message #243713]

Fri, 08 June 2007 11:01

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

1: Your Dataguard is Real time or normal.
You can check working of your Datguard just do it to verify weather it works or not

If dataguard is Real Time.

ON PRIMARY
-----------
Create table test
(a  date);

insert into test
values
(sysdate);

commit;


ON STANDBY BY
-------------
     SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
     SQL>ALTER DATABASE OPEN READ ONLY;
     SQL>SELECT * FROM.test;

If Your dataguard is not in Real time mode
then after insertion data on primary in test table perform a manual switch
with

SQL> alter system switch logfile;

and then the same command for standby

after checking place your dataguard again in Recover mode by command.

     SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT
              LOGFILE DISCONNECT;

Report message to a moderator

Re: Redo apply [message #243722 is a reply to message #243715]

Fri, 08 June 2007 11:41

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

My datagurard is not in real time .
********
TESTING
*********
ON PRIMARY
-----------
Create table test
(a date);

insert into test
values
(sysdate);

commit;

ON STANDBY BY
-------------
SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
SQL>ALTER DATABASE OPEN READ ONLY;
SQL>SELECT * FROM.test;
*************************************
The Result Was Table or view does not exist
*******************************************

But When it Tried The other way:-

After inserting data on primary and I performed manual switch with

SQL> alter system switch logfile;

and then
SQL>select * from test;

I find the same table and same records have reached the standby.

Report message to a moderator

Re: Redo apply [message #243726 is a reply to message #243722]

Fri, 08 June 2007 12:00

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

Do you have Standby redolog groups?
Your redolog group size is same on both primary and standy ?

i guess it would not a problem because your DG works properly.

Report message to a moderator

Re: Redo apply [message #243734 is a reply to message #243726]

Fri, 08 June 2007 12:35

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

**********
STANDBY
**********
SQL> select member from v$logfile;

MEMBER
--------------------------------------------------------------------------------
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo03.log
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo02.log
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo01.log
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo04.log

SQL> select members,bytes/1024/1024,status from v$log;

MEMBERS BYTES/1024/1024 STATUS
---------- --------------- ----------------
1 50 CLEARING
1 50 CLEARING
1 50 CLEARING_CURRENT

*********
PRIMARY
*********

SQL> select member from v$logfile;

MEMBER
--------------------------------------------------------------------------------
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo03.log
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo02.log
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo01.log
/database/10gDR/sr11a.dbf

SQL> select members ,bytes/1024/1024 from v$log;

MEMBERS BYTES/1024/1024
---------- ---------------
1 50
1 50
1 50

1. I have created standby logfile groups on Standby NOT Primary, Does it matter.
2. I have added a standby logfile group on standby after i had already added 3 before when i configured it.And it is showing when i query V$LOGFILE but not in V$LOG( i dont know whats the problem)
3. Although i have added one group later it was already giving me YES NO like:--
SEQUENCE# APP
---------- ---
936 NO
936 YES
937 NO
937 YES

I have read some tutorials say create standby redologs on primary and some say on standby.

Regards

Jagmohan

Report message to a moderator

Re: Redo apply [message #243737 is a reply to message #243734]

Fri, 08 June 2007 12:40

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

Yes i would recommend too

and also read this

http://download-east.oracle.com/docs/cd/B10501_01/server.920/a96653/log_transport.htm#1038266

Report message to a moderator

Re: Redo apply [message #243751 is a reply to message #243713]

Fri, 08 June 2007 14:45

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

So Dreamzz.

should i recreate logfiles.

should i drop the old logfiles(which i created on standby) and then create online redo logfiles on standby. And then create logfiles on primary.( stanbdy redo logfiles.)

How should i proceed.??

Thanks for your help.

jsingh

Report message to a moderator

Re: Redo apply [message #243756 is a reply to message #243751]

Fri, 08 June 2007 15:39

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

Why you recreating your redologs group.

i didnt get you. please explain why.

[Updated on: Fri, 08 June 2007 15:40]

Report message to a moderator

Re: Redo apply [message #243761 is a reply to message #243756]

Fri, 08 June 2007 16:00

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

When i configured the Datguard, I have Created redo logs on STANDBY with the following syntax

ALTER DATABASE ADD STANDBY LOGFILE GROUP 4
(/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo01.log') SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 5 ('/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo02.log') SIZE 50M;
ALTER DATABASE ADD STANDBY LOGFILE GROUP 6 ('/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo03.log') SIZE 50M;

The documents say you should create standby redo logs on Primary Database.

Is It like this:-
1. We should have same number and size( or one more ) redo log group on STANDBY.
2 And Plus we should have Stanby redo logs created on PRIMARY too which can be used when switchover occurs.

Or is it something different.??

Thanks for your replies

Regards
J Singh

Report message to a moderator

Re: Redo apply [message #243763 is a reply to message #243761]

Fri, 08 June 2007 16:09

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

Quote:

We should have same number and size( or one more ) redo log group on STANDBY

READ THIS THREAD

http://www.orafaq.com/forum/t/82746/105911/

Quote:

And Plus we should have Stanby redo logs created on PRIMARY too which can be used when switchover occurs.

YES create the SRLs on primary.

In 10g the archiver (ARCn) process or the log writer (LGWR) process on the primary database can transmit redo data directly to remote standby redo logs.

Report message to a moderator

Re: Redo apply [message #244140 is a reply to message #243713]

Mon, 11 June 2007 13:27

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

Alright dreamzz now i undertood how the redo logs work .
I have also created redo logs on primary and standby.

But still i'm getting

SEQUENCE# APP
---------- ---
936 NO
936 YES
937 NO
937 YES

What could be reason.

regards

and

thanks

j singh

[Updated on: Mon, 11 June 2007 13:27]

Report message to a moderator

Re: Redo apply [message #244147 is a reply to message #244140]

Mon, 11 June 2007 13:41

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

did you put the database in force logging mode?

ALTER DATABASE force logging;

Report message to a moderator

Re: Redo apply [message #244150 is a reply to message #243713]

Mon, 11 June 2007 14:01

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

yes it is in force logging mode.

SQL> alter database force logging;
alter database force logging
*
ERROR at line 1:
ORA-12920: database is already in force logging mode

Report message to a moderator

Re: Redo apply [message #244152 is a reply to message #244150]

Mon, 11 June 2007 14:11

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

if you manullay switch some logfiles like

alter system switch logfile;

then what is the beahvior?is it same.

Report message to a moderator

Re: Redo apply [message #244153 is a reply to message #244152]

Mon, 11 June 2007 14:13

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

or thr this parameter

LOG_ARCHIVE_DEST_2='SERVICE=my_service LGWR ASYNC

Report message to a moderator

Re: Redo apply [message #244154 is a reply to message #244152]

Mon, 11 June 2007 14:18

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

SQL> alter system switch logfile;

System altered.

(Primary)*.log_archive_dest_2='SERVICE=OHIO1_204
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=OHIO1_204 LGWR ASYNC REOPEN=10'

(standby) *.log_archive_dest_2='SERVICE=OHIO1_203
VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE)
DB_UNIQUE_NAME=OHIO1_203 LGWR ASYNC REOPEN=10'

Report message to a moderator

Re: Redo apply [message #244155 is a reply to message #244154]

Mon, 11 June 2007 14:29

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

opss

when you manually switched did you check

select sequence#,applied
from v$archived_log;???

paste the result after 2 or 3 manual switches.

Report message to a moderator

Re: Redo apply [message #244158 is a reply to message #243713]

Mon, 11 June 2007 14:50

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

SQL> alter system switch logfile;

System altered.

SEQUENCE# APP
---------- ---
1108 NO
1108 YES
1109 NO
1109 YES
1110 NO
1110 NO
1111 NO
1111 YES

2156 rows selected.

SQL> alter system switch logfile;

System altered.

SEQUENCE# APP
---------- ---
1109 NO
1109 YES
1110 NO
1110 NO
1111 NO
1111 YES

SQL> alter system switch logfile;

System altered.

1111 NO
1111 YES

SEQUENCE# APP
---------- ---
1112 NO
1112 YES

SQL> alter system switch logfile;

System altered.

SEQUENCE# APP
---------- ---
1106 YES
1107 NO
1107 YES
1108 NO
1108 YES
1109 NO
1109 YES
1110 NO
1110 NO
1111 NO
1111 YES

SEQUENCE# APP
---------- ---
1112 NO
1112 YES
1113 NO
1113 NO

SQL> alter system switch logfile;

System altered.

SEQUENCE# APP
---------- ---
1106 YES
1107 NO
1107 YES
1108 NO
1108 YES
1109 NO
1109 YES
1110 NO
1110 NO
1111 NO
1111 YES

SEQUENCE# APP
---------- ---
1112 NO
1112 YES
1113 NO
1113 YES
1114 NO
1114 NO

2162 rows selected.

SQL> alter system switch logfile;

System altered.

SEQUENCE# APP
---------- ---
1112 NO
1112 YES
1113 NO
1113 YES
1114 NO
1114 YES
1115 NO
1115 NO

Report message to a moderator

Re: Redo apply [message #244159 is a reply to message #244158]

Mon, 11 June 2007 14:54

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

strange man.But i guess you checked your DG working properly.
if you have any confusion then go for SUPPORT.

[Updated on: Mon, 11 June 2007 14:54]

Report message to a moderator

Re: Redo apply [message #244162 is a reply to message #243713]

Mon, 11 June 2007 15:22

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

Yes my dataguard is working fine.
PLZ Check This thing .(standby)

SQL>select member,type from v$logfile;

MEMBER
--------------------------------------------------------------------------------
TYPE
-------
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo03.log
ONLINE

/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo02.log
ONLINE

/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo01.log
ONLINE

MEMBER
--------------------------------------------------------------------------------
TYPE
-------
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo04.log
STANDBY

SQL> select members,bytes/1024/1024,status from v$log;

MEMBERS BYTES/1024/1024 STATUS
---------- --------------- ----------------
1 50 CLEARING_CURRENT
1 50 CLEARING
1 50 CLEARING

I have created standby logfiles on standby with syntax

alter database add standby logfile '/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo01.log' size 50m;

initially i created 3 of them .

later on i added 4th one.

The type for 1st 3 is online but for the 4th one it is standby.

Report message to a moderator

Re: Redo apply [message #244163 is a reply to message #243713]

Mon, 11 June 2007 15:23

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

Primary
========
SQL> create table dreamzz ( a number);

Table created.

SQL> insert into dreamzz values(007);

1 row created.

SQL> commit;

Commit complete.

SQL> select * from dreamzz;

A
----------
7
7
7
7

SQL> alter system switch logfile;

System altered.

(standby)
=========
SQL> alter database recover managed standby database cancel;

Database altered.

SQL> alter database open read only;

Database altered.

SQL> select * from dreamzz;

A
----------
7
7
7
7

Report message to a moderator

Re: Redo apply [message #244165 is a reply to message #244163]

Mon, 11 June 2007 15:54

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

SQL> ;
  1* select member,type from v$logfile
SQL> /

MEMBER                                             TYPE
-------------------------------------------------- -------
/u42/oradata/flps/redolog1/FLPS_LOG1_1.DBF         ONLINE
/u43/oradata/flps/redolog2/FLPS_LOG1_2.DBF         ONLINE
/u42/oradata/flps/redolog1/FLPS_LOG2_1.DBF         ONLINE
/u43/oradata/flps/redolog2/FLPS_LOG2_2.DBF         ONLINE
/u42/oradata/flps/redolog1/FLPS_LOG3_1.DBF         ONLINE
/u43/oradata/flps/redolog2/FLPS_LOG3_2.DBF         ONLINE
/u42/oradata/flps/redolog1/FLPS_LOG4_1.DBF         ONLINE
/u43/oradata/flps/redolog2/FLPS_LOG4_2.DBF         ONLINE
/u42/oradata/flps/redolog1/FLPS_LOG5_1.DBF         ONLINE
/u43/oradata/flps/redolog2/FLPS_LOG5_2.DBF         ONLINE
/u42/oradata/flps/redolog1/FLPS_LOG6_1.DBF         ONLINE

MEMBER                                             TYPE
-------------------------------------------------- -------
/u43/oradata/flps/redolog2/FLPS_LOG6_2.DBF         ONLINE
/u42/oradata/flps/redolog1/FLPS_LOG7_1.DBF         ONLINE
/u43/oradata/flps/redolog2/FLPS_LOG7_2.DBF         ONLINE
/u42/oradata/flps/redolog1/FLPS_LOG8_1.DBF         ONLINE
/u43/oradata/flps/redolog2/FLPS_LOG8_2.DBF         ONLINE
/u42/oradata/flps/redolog1/FLPS_LOG9_1.DBF         ONLINE
/u43/oradata/flps/redolog2/FLPS_LOG9_2.DBF         ONLINE
/u42/oradata/flps/redolog1/FLPS_LOG10_1.DBF        ONLINE
/u43/oradata/flps/redolog2/FLPS_LOG10_2.DBF        ONLINE
/u42/oradata/flps/redolog1/FLPS_LOG_S1_1.DBF       STANDBY
/u43/oradata/flps/redolog2/FLPS_LOG_S1_2.DBF       STANDBY

MEMBER                                             TYPE
-------------------------------------------------- -------
/u42/oradata/flps/redolog1/FLPS_LOG_S10_1.DBF      STANDBY
/u43/oradata/flps/redolog2/FLPS_LOG_S10_2.DBF      STANDBY
/u42/oradata/flps/redolog1/FLPS_LOG_S2_1.DBF       STANDBY
/u43/oradata/flps/redolog2/FLPS_LOG_S2_2.DBF       STANDBY
/u42/oradata/flps/redolog1/FLPS_LOG_S3_1.DBF       STANDBY
/u43/oradata/flps/redolog2/FLPS_LOG_S3_2.DBF       STANDBY
/u42/oradata/flps/redolog1/FLPS_LOG_S4_1.DBF       STANDBY
/u43/oradata/flps/redolog2/FLPS_LOG_S4_2.DBF       STANDBY
/u42/oradata/flps/redolog1/FLPS_LOG_S5_1.DBF       STANDBY
/u43/oradata/flps/redolog2/FLPS_LOG_S5_2.DBF       STANDBY
/u42/oradata/flps/redolog1/FLPS_LOG_S6_1.DBF       STANDBY

MEMBER                                             TYPE
-------------------------------------------------- -------
/u43/oradata/flps/redolog2/FLPS_LOG_S6_2.DBF       STANDBY
/u42/oradata/flps/redolog1/FLPS_LOG_S7_1.DBF       STANDBY
/u43/oradata/flps/redolog2/FLPS_LOG_S7_2.DBF       STANDBY
/u42/oradata/flps/redolog1/FLPS_LOG_S8_1.DBF       STANDBY
/u43/oradata/flps/redolog2/FLPS_LOG_S8_2.DBF       STANDBY
/u42/oradata/flps/redolog1/FLPS_LOG_S9_1.DBF       STANDBY
/u43/oradata/flps/redolog2/FLPS_LOG_S9_2.DBF       STANDBY

40 rows selected.

SQL> select members,bytes/1024/1024,status from v$log;

   MEMBERS BYTES/1024/1024 STATUS
---------- --------------- ----------------
         2              32 CLEARING
         2              32 CLEARING_CURRENT
         2              32 CLEARING
         2              32 CLEARING
         2              32 CLEARING
         2              32 CLEARING
         2              32 CLEARING
         2              32 CLEARING
         2              32 CLEARING
         2              32 CLEARING

10 rows selected.

now i have confusion
how many redologs groups on your
PRIMARY AND STANDBY
and how many standby redo log groups on
PRIMARY AND STANDBY.

SQL> ;
  1* select sequence#,applied from v$archived_log
SQL> /


 SEQUENCE# APP
---------- ---
       354 YES
       355 YES
       356 YES
       357 YES
       358 YES
       359 YES
       360 YES
       361 YES
       362 YES
       363 YES
       364 YES


 SEQUENCE# APP
---------- ---
       365 YES
       366 YES
       367 YES
       368 YES
       369 YES
       370 YES
       371 YES
       372 YES
       373 YES
       374 YES
       375 YES


 SEQUENCE# APP
---------- ---
       376 YES
       377 YES
       378 YES
       379 YES
       380 YES
       381 YES
       382 YES
       383 YES
       384 YES
       385 YES
       386 YES

Report message to a moderator

Re: Redo apply [message #244167 is a reply to message #244163]

Mon, 11 June 2007 15:55

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

jsingh wrote on Mon, 11 June 2007 14:23

Primary
========
SQL> create table dreamzz ( a number);

Table created.

SQL> insert into dreamzz values(007);

1 row created.

SQL> commit;

Commit complete.

SQL> select * from dreamzz;

A
----------
7
7
7
7

SQL> alter system switch logfile;

System altered.

(standby)
=========
SQL> alter database recover managed standby database cancel;

Database altered.

SQL> alter database open read only;

Database altered.

SQL> select * from dreamzz;

A
----------
7
7
7
7

Woww sounds good working proper.

Report message to a moderator

Re: Redo apply [message #244172 is a reply to message #244165]

Mon, 11 June 2007 16:35

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

=========
PRIMARY
=========
SQL> select member,type from v$logfile;

MEMBER TYPE
-------
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo03.log ONLINE
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo02.log ONLINE
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo01.log ONLINE
database/10gDR/sr11a.dbf (I did't create this,Is this some feature in oracle 10g which automatically creates it) STANDBY
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/stdby_redo01.log STANDBY
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/stdby_redo02.log STANDBY
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/stdby_redo03.log STANDBY

SQL> select members,bytes/1024/1024 , status from v$log;

MEMBERS BYTES/1024/1024 STATUS
---------- --------------- ----------------
1 50 ACTIVE
1 50 CURRENT
1 50 INACTIVE
=========
STANDBY
=========
SQL> select member,type from v$logfile;

MEMBER TYPE
-------
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo03.log ONLINE
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo02.log ONLINE
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo01.log ONLINE
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo04.log STANDBY

SQL> select members,bytes/1024/1024,status from v$log;

MEMBERS BYTES/1024/1024 STATUS
---------- --------------- ----------------
1 50 CLEARING
1 50 CLEARING
1 50 CLEARING_CURRENT

Report message to a moderator

Re: Redo apply [message #244174 is a reply to message #244172]

Mon, 11 June 2007 16:49

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

/home/oracle/oracle/product/10.2.0/oradata/OHIO1/stdby_redo02.log STANDBY
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/stdby_redo03.log STANDBY

create these two groups on standby.
and then check.

Report message to a moderator

Re: Redo apply [message #244175 is a reply to message #243713]

Mon, 11 June 2007 17:19

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

STANDBY
---------
SQL> select member,type,status from v$logfile;

MEMBER
--------------------------------------------------------------------------------
TYPE STATUS
------- -------
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo03.log
ONLINE

/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo02.log
ONLINE

/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo01.log
ONLINE

MEMBER
--------------------------------------------------------------------------------
TYPE STATUS
------- -------
/home/oracle/oracle/product/10.2.0/oradata/OHIO1/redo04.log
STANDBY

/home/oracle/oracle/product/10.2.0/oradata/OHIO1/stdby_redo02.log
STANDBY

/home/oracle/oracle/product/10.2.0/oradata/OHIO1/stdby_redo03.log
STANDBY

Yes i have created these two groups ,still i see the same result
1130 NO
1130 YES
1131 NO
1131 YES

[Updated on: Mon, 11 June 2007 17:19]

Report message to a moderator

Re: Redo apply [message #244176 is a reply to message #244175]

Mon, 11 June 2007 17:21

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

Quote:

Yes i have created these two groups ,still i see the same result
1130 NO
1130 YES
1131 NO
1131 YES

did you manually switch before this command?
if not then try...
other wise call oracle support if you wants.

Report message to a moderator

Re: Redo apply [message #244177 is a reply to message #243713]

Mon, 11 June 2007 17:35

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

Yes i did manually switch before the command.

I know we (SPECIAL THANKS TO YOU) tried a lot to solve the problem , but were not successfull.

I Really want to thank you again for valueable time and technical support you have provided me.

Regards

j singh

Report message to a moderator

Re: Redo apply [message #244178 is a reply to message #244177]

Mon, 11 June 2007 17:37

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

Yvw.

Wink

Razz

Report message to a moderator

Re: Redo apply [message #244179 is a reply to message #244178]

Mon, 11 June 2007 17:41

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

One more thing your redolog members and standbyredo log members sizes are same on both primary and standby??

and check this also.

Quote:

- Identify the existing files on the standby
SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME
FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;

.......................
.......................
115 29-NOV-05 29-NOV-05
116 29-NOV-05 29-NOV-05

- Switch a log on the primary
SQL>ALTER SYSTEM SWITCH LOGFILE;

- Run the above sql again on the standby to see the new log that has arrived from the primary.
.......................
.......................
115 29-NOV-05 29-NOV-05
116 29-NOV-05 29-NOV-05
117 29-NOV-05 29-NOV-05

Verify that these logs were applied :
SQL> SELECT SEQUENCE#,APPLIED FROM V$ARCHIVED_LOG
ORDER BY SEQUENCE#;

...........
115 YES
116 YES
117 YES

Quote:

1130 NO
1130 YES
1131 NO
1131 YES

as its same on your both primary and standby i guess it would not be harmful.it would if it different on both.

[Updated on: Mon, 11 June 2007 17:46]

Report message to a moderator

Re: Redo apply [message #244180 is a reply to message #243713]

Mon, 11 June 2007 17:45

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

absolutely same size=50M

PRIMARY

SQL> select bytes/1024/1024,members,status from v$log;

BYTES/1024/1024 MEMBERS STATUS
--------------- ---------- ----------------
50 1 CURRENT
50 1 INACTIVE
50 1 INACTIVE

STANDBY

SQL> select bytes/1024/1024,members,status from v$log;

BYTES/1024/1024 MEMBERS STATUS
--------------- ---------- ----------------
50 1 CLEARING_CURRENT
50 1 CLEARING
50 1 CLEARING

SQL>

Report message to a moderator

Re: Redo apply [message #244181 is a reply to message #244180]

Mon, 11 June 2007 17:50

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

if its not in your production then switch a roll transition.

or
reconfigure it.

Attachment: DATAGUARD CONFIGURATION.doc
(Size: 100.50KB, Downloaded 2228 times)

[Updated on: Mon, 11 June 2007 17:51]

Report message to a moderator

Re: Redo apply [message #244182 is a reply to message #243713]

Mon, 11 June 2007 17:56

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

IT IS Production ,though not much active yet .

and reconfiguration ,, may be i will think about it soon ..

Right now it is working ok...

But still do u think it will create some problems in near future or not??

Report message to a moderator

Re: Redo apply [message #244183 is a reply to message #244182]

Mon, 11 June 2007 18:22

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

Quote:

IT IS Production ,though not much active yet

Reconfigure it using Real time mode.

Quote:

But still do u think it will create some problems in near future or not??

i guess it works sounds good..but cant say any thing lately.

Report message to a moderator

Re: Redo apply [message #244199 is a reply to message #243713]

Mon, 11 June 2007 22:59

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

Hey Dreamzz

Thanks for your patience and technical support.

I Really appreciate the time you devoted towards my problem.

Thanks
&
Regards

J singh

Report message to a moderator

Re: Redo apply [message #245220 is a reply to message #243713]

Fri, 15 June 2007 09:26

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

Hey Dreamz

Sorry to bother you once again regarding the same problem as discussed above.

The Answer to my question what i recieved from other forum was

1.Because you have two archive log destinations

And

2.its working fine

Hey do you understand what he mean to say??

Regards
&
Thanks

jsingh

Report message to a moderator

Re: Redo apply [message #245248 is a reply to message #245220]

Fri, 15 June 2007 11:32

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

Hi Jsingh
No man its ok.can you paste the result of this parameter??

SQL> show parameter log_archive_dest

Report message to a moderator

Re: Redo apply [message #245264 is a reply to message #243713]

Fri, 15 June 2007 12:53

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

***********
PRIMARY
***********

SQL> show parameter log_archive_dest

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest string
log_archive_dest_1 string location="/home/oracle/arch",
valid_for=(ONLINE_LOGFILE,ALL_
ROLES)
log_archive_dest_10 string
log_archive_dest_2 string service="(DESCRIPTION=(ADDRESS
_LIST=(ADDRESS=(PROTOCOL=tcp)(
HOST=clboh-iptv-dba-02)(PORT=1
521)))(CONNECT_DATA=(SERVICE_N
AME=OHIO1_204_XPT)(INSTANCE_NA
ME=OHIO1)(SERVER=dedicated)))"

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
, LGWR ASYNC NOAFFIRM delay
=0 OPTIONAL max_failure=0 max_
connections=1 reopen=300 db_
unique_name="OHIO1_204" regist
er net_timeout=180 valid_for=
(online_logfile,primary_role)
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string ENABLE
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string ENABLE
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_state_9 string enable

***********
STANDBY
***********

SQL> show parameter log_archive_dest;

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest string
log_archive_dest_1 string location="/home/oracle/arch",
valid_for=(ALL_LOGFILES,ALL_RO
LES)
log_archive_dest_10 string
log_archive_dest_2 string SERVICE=OHIO1_203

VALID_FOR=(ONLINE_LOGFILES,PRI
MARY_ROLE)

DB_UNIQUE_NAME=OHIO1_203 LGWR

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
ASYNC REOPEN=10
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
log_archive_dest_state_1 string ENABLE
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string enable

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
SQL>

[Updated on: Fri, 15 June 2007 12:54]

Report message to a moderator

Re: Redo apply [message #245269 is a reply to message #245264]

Fri, 15 June 2007 13:10

DreamzZ
Messages: 1666
Registered: May 2007
Location: Dreamzland

Senior Member

Quote:

The Answer to my question what i recieved from other forum was

1.Because you have two archive log destinations

i have the same configuration like you.

SQL> show parameter log_archive_dest;

NAME                                 TYPE                             VALUE
------------------------------------ -------------------------------- ------------------------------
log_archive_dest                     string
log_archive_dest_1                   string                           LOCATION=/u40/oracle/flps/oraa
                                                                      rc
                                                                                            VALID_FO
                                                                      R=(ALL_LOGFILES,ALL_ROLES)
                                                                                            DB_UNIQU
                                                                      E_NAME=FLPS1
log_archive_dest_10                  string
log_archive_dest_2                   string                           SERVICE=FLPS2 LGWR ASYNC
                                                                                            VALID_FO
                                                                      R=(ONLINE_LOGFILES,PRIMARY_ROL

NAME                                 TYPE                             VALUE
------------------------------------ -------------------------------- ------------------------------
                                                                      E)
                                                                                           DB_UNIQUE
                                                                      _NAME=FLPS2
log_archive_dest_3                   string
log_archive_dest_4                   string
log_archive_dest_5                   string
log_archive_dest_6                   string
log_archive_dest_7                   string
log_archive_dest_8                   string
log_archive_dest_9                   string
log_archive_dest_state_1             string                           ENABLE

NAME                                 TYPE                             VALUE
------------------------------------ -------------------------------- ------------------------------
log_archive_dest_state_10            string                           enable
log_archive_dest_state_2             string                           ENABLE
log_archive_dest_state_3             string                           enable
log_archive_dest_state_4             string                           enable
log_archive_dest_state_5             string                           enable
log_archive_dest_state_6             string                           enable
log_archive_dest_state_7             string                           enable
log_archive_dest_state_8             string                           enable
log_archive_dest_state_9             string                           enable

STANDBY

NAME                                 TYPE                             VALUE
------------------------------------ -------------------------------- ------------------------------
log_archive_dest                     string
log_archive_dest_1                   string                           LOCATION=/u40/oracle/flps/oraa
                                                                      rc
                                                                                           VALID_FOR
                                                                      =(ALL_LOGFILES,ALL_ROLES)
                                                                                           DB_UNIQUE
                                                                      _NAME=FLPS2
log_archive_dest_10                  string
log_archive_dest_2                   string                           SERVICE=FLPS1 LGWR ASYNC
                                                                                           VALID_FOR
                                                                      =(ONLINE_LOGFILES,PRIMARY_ROLE

NAME                                 TYPE                             VALUE
------------------------------------ -------------------------------- ------------------------------
                                                                      )
                                                                                           DB_UNIQUE
                                                                      _NAME=FLPS1
log_archive_dest_3                   string
log_archive_dest_4                   string
log_archive_dest_5                   string
log_archive_dest_6                   string
log_archive_dest_7                   string
log_archive_dest_8                   string
log_archive_dest_9                   string
log_archive_dest_state_1             string                           ENABLE

NAME                                 TYPE                             VALUE
------------------------------------ -------------------------------- ------------------------------
log_archive_dest_state_10            string                           enable
log_archive_dest_state_2             string                           ENABLE
log_archive_dest_state_3             string                           enable
log_archive_dest_state_4             string                           enable
log_archive_dest_state_5             string                           enable
log_archive_dest_state_6             string                           enable
log_archive_dest_state_7             string                           enable
log_archive_dest_state_8             string                           enable
log_archive_dest_state_9             string                           enable

i guess its not a Problem.

Report message to a moderator

Re: Redo apply [message #245270 is a reply to message #243713]

Fri, 15 June 2007 13:15

jsingh
Messages: 36
Registered: June 2007
Location: ny

Member

Hey Dreamzz ONCE AGAIN

THANKS A LOTTTTTT.

Regards

JSingh

Report message to a moderator

Pages (2): [1 2 › »]

Previous Topic:	lost standby controlfile
Next Topic:	Problem while mining archivelog in Logical Standby Database

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Feb 02 17:19:48 CST 2025