Error 12545 Received Logging On To The Standby
Contents |
Broker fails error 12154 received logging on to the standby to enable databse [message #501166] Sat, 26 error 12154 received logging on to the standby 11g March 2011 12:27 farnaw4u Messages: 22Registered: October 2006 Location: pakistan Junior Member
Error 12154 Received Logging On To The Standby Rac
Dear all I have configuring oracle data Physical standby data Guard on Linux i did configure the same three
Error 1031 Received Logging On To The Standby
times fails in data guard Broker. Primary database name PRIM Physical Standby name STAN tnsping PRIM ......OK tnsping STAN ........OK Initially every was fine redo was successfully was being transmitted to standby the Problem starts when i enable error 1031 received logging on to the standby ora-01031 insufficient privileges DG broker configuration and after this redo transmission become STOPPED and i dont know where is problem and how to solve it..... here are files to look at PRIMARY init.ora file ########################################### db_block_size=8192 db_file_multiblock_read_count=16 ########################################### # Cursors and Library Cache ########################################### open_cursors=300 ########################################### # Database Identification ########################################### db_domain="" db_name=PRIM ########################################### # Diagnostics and Statistics ########################################### background_dump_dest=/u01/app/oracle/admin/PRIM/bdump core_dump_dest=/u01/app/oracle/admin/PRIM/cdump user_dump_dest=/u01/app/oracle/admin/PRIM/udump ########################################### # File Configuration ########################################### control_files=("/u01/app/oracle/oradata/PRIM/control01.ctl", "/u01/app/oracle/oradata/PRIM/control02.ctl", "/u01/app/oracle/oradata/PRIM/control03.ctl") db_recovery_file_dest=/u01/app/oracle/flash_recovery_area db_recovery_file_dest_size=2147483648 ########################################### # Job Queues ########################################### job_queue_processes=10 ########################################### # Miscellaneous ########################################### compatible=10.2.0.1.0 ########################################### # Network Registration ########################################### local_listener=LISTENER_PRIM ########################################### # Processes and Sessions ########################################### processes=150 ########################################### # SGA Memory ########################################### sga_target=283115520 ########################################### # Security and Auditing ########################################### audit_file_dest=/u01/app/oracle/admin/PRIM/adump remote_login_passwordfile=EXCLUSIVE ########################################### # Shared Server ########################################### dispa
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 http://www.dbasupport.com/forums/showthread.php?57868-Oracle-Dataguard-errors-confusion the register link above to proceed. To start viewing messages, select the forum http://adarshkumarusa.blogspot.com/2014/09/standby-dataguard-issues.html 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 received logging 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 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[ARC0]: Heartbeat failed to connect to standby 'mmgdrs'. Error is 1031. Error 1031 received logging on to the standby PING[ARC0]: Heartbeat failed to connect to standby 'mmgdrs'. Error is 1031. Error 1031 recei
Check#: if Main is sending logs and Standby is Receiving Logs Check#: if at standby mrp is active Check# primary DG_COFIG see example below ALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG=(DB11G,DB11G_STBY)'; Disable/Enable archive log destinations Primary alter system set log_archive_dest_state_2 = 'defer'; alter system set log_archive_dest_state_2 = 'enable'; Stop the Data Guard broker [both] alter system set dg_broker_start=false; alter system set dg_broker_start=true; ALTER SYSTEM SET LOG_ARCHIVE_FORMAT='%t_%s_%r.arc' SCOPE=SPFILE; ALTER SYSTEM SET LOG_ARCHIVE_MAX_PROCESSES=30; ALTER SYSTEM SET REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE SCOPE=SPFILE; #Check if primary has errors shipping logs Select Status, Error from v$Archive_dest where dest_id=2; < Change this number when applicable> #Resolving GAP or MRP is not applying or log is not getting shipped Try Killing Arc Proces on both Databases primary & Stby , Try Disabling and enabling Dest to start the process ( in Primary Database) # Archivelog Gaps in Standby select * from v$archive_gap; # Monitor in Standby database Check for MRP & Arch Processes, Which node MRP is active select inst_id,process, status, thread#, sequence#, block#, blocks from gv$managed_standby; #which standby node is applying the Logs (run this on Standby ,Check for MRP process and Node) select INST_ID,PROCESS, STATUS FROM GV$MANAGED_STANDBY; SELECT DEST_ID,dest_name,status,type,srl,RECOVERY_MODE FROM V$ARCHIVE_DEST_STATUS; RECOVERY_MODE ----------------------- MANAGED REAL TIME APPLY RECOVERY_MODE ------------- MANAGED -- query dest Error run from Primary select dest_name,status,type,archived_seq#,applied_seq#,applied_thread#,error,destination from v$archive_dest_status where destination is not null; Tables v$logfile V$log_history v$archived_log v$archive_gap V$ARCHIVE_DEST V$ARCHIVE_DEST_STATUS select name,database_role role,log_mode, protection_mode,protection_level from v$database; select force_logging,remote_archive, supplemental_log_data_pk, supplemental_log_data_ui, switchover_status,dataguard_broker from v$database; Finding Missing Logs on Standby select local.thread#,local.sequence# from (select thread#,sequence# from v$archived_log where dest_id=1) local where local.sequence# not in (select sequence# from v$archived_log where dest_id=2 and thread#