Home » Server Options » Data Guard » Logical stand by log apply - ORA-01031
Logical stand by log apply - ORA-01031 [message #163365] Thu, 16 March 2006 07:36 Go to next message
prabhueman
Messages: 1
Registered: March 2006
Junior Member
Hi
I am having a problem in log apply acivity on logical standby database. The following are the steps that i have monitored. Any Help!

Thanks,

----------------------------------------------------------

1. select event_time, status, event from dba_logstdby_events order by event_time, commit_scn;

----------------------------------------

15-MAR-06 11:44:09 ORA-16111: log mining and apply setting up


15-MAR-06 11:44:09 ORA-16111: log mining and apply setting up


15-MAR-06 11:44:12 ORA-01031: insufficient privileges (metalink is not displaying rlated document 246644.1 -https://metalink.oracle.com/metalink/plsql/f?p=130:3:3031134073714009737::::p3_database_id,p3_docid,p3_show_header,p3_show_help,p3_b lack_frame,p3_font:NOT,246644.1,1,0,0,helvetica)
grant sysdba to system

----------------------------------------
2. select file_name, sequence#, first_change#, next_change#, timestamp, dict_begin, dict_end, thread# from dba_logstdby_log order by sequence#;
------------------------------------------------

/u08/oradata/archlogs/standby/xxxxx_archlog_1_102.dbf
102 213605861 213606212 10-MAR-06 14:09:16 YES YES 1

/u08/oradata/archlogs/standby/yyyyyy_archlog_1_103.dbf
103 213606212 213606576 13-MAR-06 17:12:20 NO NO 1 (NOTICE THERE WAS A CHANGE IN FILE FORMAT)

-----upto 15 records with NO NO

------------------------------------------------------------------------------------
3. select applied_scn, newest_scn from dba_logstdby_progress;
------------------------------------------------------------------------------

APPLIED_SCN NEWEST_SCN
----------- ----------
213617026 214640916


------------------------------------------------------------------------------------------------------------------------
4. select L.sequence#, L.first_time, (case when L.next_change# < P.read_scn then 'yes' when L.first_change# < P.applied_scn then 'CURRENT' else 'NO' end)
applied from dba_logstdby_log L, dba_logstdby_progress P order by sequence#;
----------------------------------------------------------------------------------------------------

SEQUENCE# FIRST_TIME APPLIED
---------- ------------------ -------
102 10-MAR-06 10:52:23 yes
103 10-MAR-06 10:52:47 CURRENT
104 10-MAR-06 10:54:55 CURRENT
105 11-MAR-06 21:07:54 NO
106 13-MAR-06 02:55:52 NO
107 13-MAR-06 15:39:54 NO
108 13-MAR-06 17:10:38 NO
109 13-MAR-06 17:14:15 NO
110 13-MAR-06 17:14:31 NO
111 13-MAR-06 17:26:28 NO
112 14-MAR-06 13:54:59 NO

SEQUENCE# FIRST_TIME APPLIED
---------- ------------------ -------
113 14-MAR-06 15:12:44 NO
114 14-MAR-06 15:22:59 NO
115 14-MAR-06 18:39:04 NO
116 15-MAR-06 10:16:08 NO

15 rows selected.
Re: Logical stand by log apply - ORA-01031 [message #629696 is a reply to message #163365] Mon, 15 December 2014 04:43 Go to previous messageGo to next message
leoinfo
Messages: 2
Registered: December 2014
Location: London
Junior Member
Hi Guys
I am getting the same error, any help?
I am new to Oracle so please help me
Re: Logical stand by log apply - ORA-01031 [message #629698 is a reply to message #629696] Mon, 15 December 2014 04:58 Go to previous messageGo to next message
John Watson
Messages: 8319
Registered: January 2010
Location: Global Village
Senior Member
Welcome to the forum.

There is little point in replying to a question placed eight years ago. Furthermore, you have provided no information regarding your problem.

Please read our OraFAQ Forum Guide and please read How to use [code] tags and make your code easier to read Then create a new topic with full details.



Re: Logical stand by log apply - ORA-01031 [message #629700 is a reply to message #629696] Mon, 15 December 2014 05:09 Go to previous messageGo to next message
leoinfo
Messages: 2
Registered: December 2014
Location: London
Junior Member
sorry i know this topick was old.
some information

nothing is replicationg and it got stoped sunday
when i query this-->
SELECT TYPE,STATUS FROM V$LOGSTDBY;
i get
COORDINATOR
ORA-16240: Waiting for log file (thread# 1, sequence# 15014)

SEQUENCE# FIRST_TIME APPLIED
---------- ------------------- -------
15006 14-12-12 01:01:54 yes
15007 14-12-12 01:02:08 yes
15008 14-12-12 01:02:30 yes
15009 14-12-12 03:01:15 yes
15010 14-12-12 05:00:03 yes
15011 14-12-12 07:36:11 yes
15012 14-12-12 07:39:44 yes
15013 14-12-12 07:43:32 yes
15014 14-12-12 09:34:38 CURRENT
15015 14-12-12 10:30:04 NO
15016 14-12-12 11:02:23 NO
15017 14-12-12 11:28:12 NO
15018 14-12-12 12:06:08 NO
15019 14-12-12 12:51:52 NO

[Updated on: Mon, 15 December 2014 05:09]

Report message to a moderator

Re: Logical stand by log apply - ORA-01031 [message #629701 is a reply to message #629700] Mon, 15 December 2014 05:15 Go to previous messageGo to next message
John Watson
Messages: 8319
Registered: January 2010
Location: Global Village
Senior Member
You haven't read the links I asked you to look at, have you? You haven;t even bothered to create a new topic.

And you haven't provided enough information. You need to query v$logstdby_progress and v$logstdby_process. Look at the alert log and and any trace files generated by the various LSP processes. What happens when try to start SQL apply?

[Updated on: Mon, 15 December 2014 05:16]

Report message to a moderator

Re: Logical stand by log apply - ORA-01031 [message #629708 is a reply to message #629700] Mon, 15 December 2014 06:37 Go to previous message
Michel Cadot
Messages: 67294
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

ORA-16240: Waiting for log file (thread# %s, sequence# %s)
 *Cause:  Process is idle waiting for additional log file to be available.
 *Action: No action necessary. This informational statement is provided
          to record the event for diagnostic purposes.
Previous Topic: Data Guard Broker warning
Next Topic: data guard configuration on windows
Goto Forum:
  


Current Time: Mon Aug 10 03:59:39 CDT 2020