Error 1017 Received Logging On To The Standby Oracle
Contents |
:: Message Navigator E-mail to friend Standby database error: primary failed to connect to standby [message #321206] Mon, 19 May 2008 07:29 tomvdduin Messages: 3Registered: May 2008 error 1017 received logging on to the standby ora 16191 Location: Huizen Junior Member This is my first attempt to create a error 1017 received logging on to the standby 11g standby server configuration. I don't know what I'm doing wrong, but this is what I'm doing: primary database:
Error 12514 Received Logging On To The Standby Oracle
- perform command 'alter database begin backup' - perform command 'alter database create standby controlfile as '
Error 12154 Received Logging On To The Standby
file to temporary location - copy datafiles (all datafiles known in v$datafile) to temporary location - perform command 'alter database end backup' standby database (same hardware/oracle installation/file and folder structure as primary database) - copy the passwordfile in \database\ folder - copy the pfile created above in \database\ folder - create service - perform command 'startup nomount' - perform error 12154 received logging on to the standby rac command 'create spfile from pfile' - copy controlfile created above to correct locations - copy datafiles created above to correct location - perform command 'alter database mount standby database;' - perform command 'alter database recover managed standby database disconnect from session;' all command are executed as sys (sysdba) and execute without error. The SID is identical on both databases, I can perform 'sqlplus /nolog' and 'conn sys/
standby 'STBYKOL'. Error is 1034) Hi Guys, Here is an Interesting case and I was stuck with the problem since last 2 days and a half. In fact I was almost done with
Error 1031 Received Logging On To The Standby
everything to resolve the mentioned problem but I could not able to solve almost. error 1031 received logging on to the standby ora-01031 insufficient privileges Then I left it as I became exhausted, But I kept on thinking Where could be the problem, at last error 12541 received logging on to the standby I got it. Here was my case: -------------------- I have 2 node rac as primary and a standby was intended to create on single node. I changed parameter file, created passwords, tns entries http://www.orafaq.com/forum/t/119021/ accordingly. Then I did duplicate target and restored database as standby. After doing everything I saw, RAC node1 was able to send archive logs to dest_2 which is my standby but unfortunately node2 was unable to enter into standy database. Here are Problem Statement: ---------------------------- Standby was receiving node1's log files but node2 was unable to send logfiles due to the below error Error 1017 received logging on to https://viewssharings.blogspot.com/2014/03/troubleshooting-error-1017-received.html the standby ------------------------------------------------------------ Check that the primary and standby are using a password file and remote_login_passwordfile is set to SHARED or EXCLUSIVE, and that the SYS password is same in the password files. Steps for diagnosing ---------------------------- step-1 when I checked query on node 2 sql>select DEST_ID,DEST_NAME,STATUS,BINDING,ERROR from v$ARCHIVE_DEST where status<>'INACTIVE'; all log file location were valid Sql> SELECT DESTINATION, STATUS, ERROR FROM V$ARCHIVE_DEST WHERE DEST_ID=2; dest2 for archive log dest is valid sql> select error_code,message from v$dataguard_status; Error 1034 received logging on to the standby PING[ARC2]: Heartbeat failed to connect to standby 'STBYDB'. Error is 1034. Then I have done the below steps to resolve the problem 1.) alter system set log_archive_dest_state_2=defer scope=both sid='*'; (on primary RAC any node ) Sql>recover managed standby database cancel; (on standby side) 2) alter database set SEC_CASE_SENSITIVE_LOGON=FALSE scope=both sid='*'; (on RAC side) 3) shutdown the standby database infact if possible primary also then remove password files for all primary rac nodes and standby nodes and then created the password file on their respective server orapwd file=$ORACLE_HOME/dbs/orapw$ORACLE_SID password=system entries=5 force=y ignorecase=Y Then start the primary db (rac nodes by srvctl start database -d primaryDB ) 4) alter system set LOG_ARCHIVE_DEST_2='SERVICE=STBYKOL ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=STBYDB' scope=both sid='*'; (
RMAN. Tags: ASM, backup, Dataguard, Exadata, Oracle 11.2, RAC, RMAN, Standby 2 comments This is a quick post regarding the error on the subject. This is https://davidalejomarcos.wordpress.com/tag/dataguard/ the second time it happens to me, so I thought I will write a bit about it. The problem: I am refreshing one of my UAT environments (happens to be a Full Rack Exadata) using Oracle RMAN duplicate command. Then the following happens (on both occasions). 1.- Duplicate command fails (lack of space for restoring archivelogs, or any other error). This is received logging can be fixed quite easy. 2.- following error while trying to open the database after restore and recover has finished: SQL> alter database open; alter database open * ERROR at line 1: ORA-03113: end-of-file on communication channel Process ID: 13710 Session ID: 1250 Serial number: 5 SQL> exit On the alert.log file we can read the following: Wed Aug 24 13:32:48 2011 received logging on alter database open Wed Aug 24 13:32:49 2011 LGWR: STARTING ARCH PROCESSES Wed Aug 24 13:32:49 2011 ARC0 started with pid=49, OS id=13950 ARC0: Archival started LGWR: STARTING ARCH PROCESSES COMPLETE ARC0: STARTING ARCH PROCESSES LGWR: Primary database is in MAXIMUM AVAILABILITY mode LGWR: Destination LOG_ARCHIVE_DEST_1 is not serviced by LGWR LGWR: Minimum of 1 LGWR standby database required Errors in file /apps/oracle/server/diag/rdbms/xxxx04/xxxx041/trace/xxxx041_lgwr_13465.trc: ORA-16072: a minimum of one standby database destination is required Errors in file /apps/oracle/server/diag/rdbms/xxxx04/xxxx041/trace/xxxx041_lgwr_13465.trc: ORA-16072: a minimum of one standby database destination is required LGWR (ospid: 13465): terminating the instance due to error 16072 Wed Aug 24 13:32:50 2011 ARC1 started with pid=48, OS id=13952 Wed Aug 24 13:32:50 2011 System state dump is made for local instance System State dumped to trace file /apps/oracle/server/diag/rdbms/xxxx04/xxxx041/trace/xxxx041_diag_13137.trc Trace dumping is performing id=[cdmp_20110824133250] Instance terminated by LGWR, pid = 13465 The Solution: Quite simple: 1.- Start up database in mount mode: SQL> startup mount ORACLE instance started. Total System Global Area 1.7103E+10 bytes Fixed Size 2230472 bytes Variable Size 4731176760 bytes Database Buffers 1.2180E+10 bytes Redo Buffers 189497344 bytes Database mounted. SQL> select ope