Error 1031 Received Logging On To The Standby Ora 01031
Contents |
ourselves. Always be positive and keep smiling..have a great day friends error 1031 received logging on to the standby ora-01031 insufficient privileges :) Source: Internet March 05, 2013 Error 1031 received logging
Error 1031 Received Logging On To The Standby Rac
on to the standby ISSUE Error 1031 received logging on to the standby ORA-01031: insufficient ping arc1 heartbeat failed to connect to standby error is 1033 privileges PING[ARC0]: Heartbeat failed to connect to standby 'dgp'. Error is 1031. PRIMARY======= Primary database Alert log error:-------------------------------- Error 1031 received logging on to ping arc2 heartbeat failed to connect to standby error is 1031 the standby ORA-01031: insufficient privileges PING[ARC0]: Heartbeat failed to connect to standby 'dgp'. Error is 1031. Chech DR sync and see the difference. THREAD PR-ARCHIVED STBY-ARCHIVED STBY-APPLIED SHIPPING GAP(PR -> STBY) APPLIED GAP(STBY -> STBY) ------ ----------- ------------- ------------ ------------------------ ------------------------- set pages 999 lines 999 col MESSAGE for a100
Error 1033 Received Logging On To The Standby Rac
select to_char(timestamp,'YYYY-MON-DD HH24:MI:SS')||' '||message||severity from gv$dataguard_status where severity in ('Error','Fatal') order by timestamp; show parameter log_archive_dest_state_2; LISTNER VERIFICATION FROM PRIMATY DB ------------------------------------ select dest_id,status,error from v$archive_dest where dest_name='LOG_ARCHIVE_DEST_2'; FIND GAP -------- select thread#,low_sequence#,high_sequence# from gv$archive_log; ps -ef |grep tns lsnrctl status DR== DR database Alert log error: ---------------------------- Error 1031 received logging on to the standby set pages 999 lines 999 col MESSAGE for a100 select to_char(timestamp,'YYYY-MON-DD HH24:MI:SS')||' '||message||severity from gv$dataguard_status where severity in ('Error','Fatal') order by timestamp; select inst_id,process,status,thread#,sequence#,block#,blocks from gv$managed_standby; PROCESS STATUS ------- ------------ RFS IDLE RFS IDLE RFS IDLE MRP0 WAIT_FOR_LOG checking log transfer and apply ------------------------------- SELECT SEQUENCE#,FIRST_TIME,NEXT_TIME,APPLIED FROM gV$ARCHIVED_LOG ORDER BY SEQUENCE#; select count(*) from GV$ARCHIVED_LOG where applied='NO'; Redo transfer was not happening. When we checked in the v$managed_process data dictionary view, we could see that RFS was not starting. Here, ora-01031 usually appears when some sysdba session failes to authent
Post #1 Advanced Member Group: Members Posts: 229 Joined: 15-November 06 Member No.: 5,636 Hi, i am making a standby in a Oracle 10gR2 v$pwd_file_users in Windows 2003 Server R1.I am getting the following error in the alert of error 1034 received logging on to the standby primary database:Error 1031 connecting to destination LOG_ARCHIVE_DEST_2 standby host*** 2008-09-14 20:33:04.359 60680 kcrr.cError 1031 received logging on to the standbyError 1031 connecting
Error 1033 Creating Remote Archivelog File
to destination LOG_ARCHIVE_DEST_2 standby host 'ORCLSTBY'Error 1031 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'ORCLSTBY'ORA-01031: insufficient privileges*** 2008-09-14 20:33:04.359 60680 kcrr.cPING[ARC0]: Heartbeat failed to connect to standby 'ORCLSTBY'. Error is 1031.*** 2008-09-14 20:33:04.359 58942 kcrr.ckcrrfail: dest:2 http://select-star-from.blogspot.com/2013/03/error-1031-received-logging-on-to.html err:1031 force:0 blast:1kcrrwkx: nothing to do (end)*** 2008-09-14 20:34:04.406kcrrwkx: nothing to do (end)I can do tnsping and connect since primary to standby and of standby to primary.Too i see that my process of archiving in the standby is good:SQL> select process,status,thread#,sequence# from v$managed_standby;PROCESS STATUS THREAD# SEQUENCE#--------- ------------ ---------- ----------ARCH CONNECTED 0 0ARCH CONNECTED 0 0MRP0 WAIT_FOR_LOG 1 52I read in metalink that is for password file, but i have a passwordfile in http://dbaforums.org/oracle/index.php?showtopic=15677 each node and the password is the same that sys user.So i don't know where is the problem?.Regards. SteveC View Member Profile Sep 14 2008, 09:25 PM Post #2 Advanced Member Group: Members Posts: 2,836 Joined: 11-March 08 Member No.: 18,933 What about DB_ALLOWED_LOGON_VERSION? Francisco Riccio View Member Profile Sep 15 2008, 11:32 AM Post #3 Advanced Member Group: Members Posts: 229 Joined: 15-November 06 Member No.: 5,636 QUOTE (SteveC @ Sep 14 2008, 09:26 PM) What about DB_ALLOWED_LOGON_VERSION?It is set up in the sqlnet.ora in both nodes as:SQLNET.ALLOWED_LOGON_VERSION=10 SteveC View Member Profile Sep 15 2008, 12:57 PM Post #4 Advanced Member Group: Members Posts: 2,836 Joined: 11-March 08 Member No.: 18,933 Apparently Oracle doesn't know what to name this parameter as various forms of it appear in several sources.From the Net ref guildeSQLNET_ALLOWED_LOGON_VERSIONS=(10,9,8)From MetaLink note 402193.1SQLNET.ALLOWED_LOGON_VERSIONFrom another MetaLink notethe parameter from other postGuess you may have to try all of them « Next Oldest · Oracle Forum · Next Newest » 6 User(s) are reading this topic (6 Guests and 0 Anonymous Users) 0 Members: Forum Home Search Help Oracle |-- Oracle Forum Display Mode: Standard · Switch to: Linear+ · Switch to: Outline Track this topic · Email this topic · Print this topic
Dataguard errors/confusion If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Page 1 of 2 12 Last Jump to page: Results 1 to 10 of 12 Thread: Oracle Dataguard errors/confusion Tweet Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 05-06-2008,07:11 PM #1 Chucks_k View Profile View Forum Posts Senior Member Join Date Dec 2001 Posts 337 Oracle Dataguard errors/confusion Hi all, I am trying to build a single standby db for a 2 node RAC db on RHEL 4 using Oracle 10.2.0.1 I am having the following errors: In node1 of the LIVE RAC db: Code: select message from v$dataguard_status; Error 1017 received logging on to the standby PING[ARC0]: Heartbeat failed to connect to standby 'mmgdrs'. Error is 16191. Error 1017 received logging on to the standby PING[ARC0]: Heartbeat failed to connect to standby 'mmgdrs'. Error is 16191. Error 1017 received logging on to the standby PING[ARC0]: Heartbeat failed to connect to standby 'mmgdrs'. Error is 16191. Error 1017 received logging on to the standby PING[ARC0]: Heartbeat failed to connect to standby 'mmgdrs'. Error is 16191. Error 1017 received logging on to the standby PING[ARC0]: Heartbeat failed to connect to standby 'mmgdrs'. Error is 16191. Error 1017 received logging on to the standby I understand one of the causes for the the above is not having the same password for sys in the password file. I have ensured that this is the same. When I ty a remote connect from node 1 to DRS i can occasionally log in but sometimes I get SQL connection timeout errors! On node 2 I am seeing the following errors: Code: PING[AR