Home » Server Options » Data Guard » Error with shipping redo log from primary to standby (Oracle 11gr2, Linux RHEL 5)
Error with shipping redo log from primary to standby [message #601350] Tue, 19 November 2013 20:56 Go to next message
trantuananh24hg
Messages: 609
Registered: January 2007
Location: Ha Noi, Viet Nam
Senior Member
Good morning!
I've got error yesterday. Let me describe:

I configure DG successfully at 15/10/2013, both of them are Oracle 11gr2, ASM, RHEL 5 (single), they are fine till 19/11/2013 when system administrator change the IP of primary. So, I got error shipping redo log from primary to standby.

P/S: Because of long brief, so I device into 2 post. I'm sorry for inconvenience

Primary (RHEL 5.5, Oracle 11gr2 Grid Infrastructure, Enterprise)
Error:
Log Transport Services   Error                  2        1066      12504 YES 20-NOV-13
PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504.

Log Transport Services   Error                  0        1067      12504 YES 20-NOV-13
Error 12504 received logging on to the standby

Log Transport Services   Error                  2        1068      12504 YES 20-NOV-13
PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504.

Log Transport Services   Error                  0        1069      12504 YES 20-NOV-13
Error 12504 received logging on to the standby

Log Transport Services   Error                  2        1070      12504 YES 20-NOV-13
PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504.


- error log file

* alert log file:
Fatal NI connect error 12541, connecting to:
 (DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=)(CID=(PROGRAM=oracle)(HOST=webcharge)(USER=oracle)))(ADDRESS=(PROTOCOL=TCP)(HOST=10.54.5.
177)(PORT=1521)))

  VERSION INFORMATION:
        TNS for Linux: Version 11.2.0.1.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
  Time: 19-NOV-2013 01:16:44
  Tracing not turned on.
  Tns error struct:
    ns main err code: 12541
    
TNS-12541: TNS:no listener
    ns secondary err code: 12560
    nt main err code: 511

TNS-12564: TNS:connection refused
    ns secondary err code: 0
    nt main err code: 0
    nt secondary err code: 0
    nt OS err code: 0
    
TNS-00511: No listener
    nt secondary err code: 111
    nt OS err code: 0
Error 12541 received logging on to the standby
Check whether the listener is up and running.
Errors in file /webcharge/app/oracle/diag/rdbms/webcharge/webcharge/trace/webcharge_arc1_4980.trc:
ORA-12541: TNS:no listener
PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12541.


* dump file
[oracle@webcharge trace]$ more /webcharge/app/oracle/diag/rdbms/webcharge/webcharge/trace/webcharge_arc1_4980.trc
Trace file /webcharge/app/oracle/diag/rdbms/webcharge/webcharge/trace/webcharge_arc1_4980.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
ORACLE_HOME = /webcharge/app/oracle/product/11.2.0/webcharge
System name:    Linux
Node name:      webcharge
Release:        2.6.18-194.el5
Version:        #1 SMP Tue Mar 16 21:52:39 EDT 2010
Machine:        x86_64
Instance name: webcharge
Redo thread mounted by this instance: 1
Oracle process number: 32
Unix process pid: 4980, image: oracle@webcharge (ARC1)


*** 2013-11-19 01:22:44.934
*** SESSION ID:(3.5) 2013-11-19 01:22:44.934
*** CLIENT ID:() 2013-11-19 01:22:44.934
*** SERVICE NAME:(SYS$BACKGROUND) 2013-11-19 01:22:44.934
*** MODULE NAME:() 2013-11-19 01:22:44.934
*** ACTION NAME:() 2013-11-19 01:22:44.934
 

*** TRACE FILE RECREATED AFTER BEING REMOVED ***

Redo shipping client performing standby login
OCIServerAttach failed -1
.. Detailed OCI error val is 12504 and errmsg is 'ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA
'
OCIServerAttach failed -1
.. Detailed OCI error val is 12504 and errmsg is 'ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA
'
OCIServerAttach failed -1
.. Detailed OCI error val is 12504 and errmsg is 'ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA
'
*** 2013-11-19 01:22:44.940 4132 krsh.c
Error 12504 received logging on to the standby
*** 2013-11-19 01:22:44.940 869 krsu.c
Error 12504 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'wbstdby'
Error 12504 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'wbstdby'
ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA
*** 2013-11-19 01:22:44.941 4132 krsh.c
PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504.
*** 2013-11-19 01:22:44.941 2747 krsi.c
krsi_dst_fail: dest:2 err:12504 force:0 blast:1

*** 2013-11-19 01:27:45.072

- host file
[oracle@webcharge trace]$ cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1       localhost.localdomain localhost
10.54.5.147     webcharge
10.54.5.177     wbstdby
10.50.9.60      rtec_system


- ping
[oracle@webcharge trace]$ ping wbstdby
PING wbstdby (10.54.5.177) 56(84) bytes of data.
64 bytes from wbstdby (10.54.5.177): icmp_seq=1 ttl=64 time=0.107 ms
64 bytes from wbstdby (10.54.5.177): icmp_seq=2 ttl=64 time=0.096 ms
64 bytes from wbstdby (10.54.5.177): icmp_seq=3 ttl=64 time=0.103 ms
64 bytes from wbstdby (10.54.5.177): icmp_seq=4 ttl=64 time=0.093 ms
64 bytes from wbstdby (10.54.5.177): icmp_seq=5 ttl=64 time=0.107 ms

--- wbstdby ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4002ms
rtt min/avg/max/mdev = 0.093/0.101/0.107/0.008 ms


Re: Error with shipping redo log from primary to standby [message #601351 is a reply to message #601350] Tue, 19 November 2013 20:58 Go to previous messageGo to next message
trantuananh24hg
Messages: 609
Registered: January 2007
Location: Ha Noi, Viet Nam
Senior Member
Continue

Primary (RHEL 5.5, Oracle 11gr2 Grid Infrastructure)

- init file
sys@WEBCHARG> ! cat $HOME/initwebcharge.ora
...
*.compatible='11.2.0.0.0'
*.control_files='+DATA/webcharge/controlfile/current.260.831277819','+FRA/webcharge/controlfile/current.256.831277819'
*.cursor_sharing='FORCE'
*.db_block_size=8192
*.db_create_file_dest='+DATA'
*.db_domain=''
*.db_file_name_convert='+DATA/wbstdby/datafile/','+DATA/webcharge/datafile/'
*.db_name='webcharg'
*.db_recovery_file_dest='+FRA'
*.db_recovery_file_dest_size=10737418240
*.db_unique_name='webcharge'
*.diagnostic_dest='/webcharge/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=webchargeXDB)'
*.fal_client='WEBCHARGE'
*.fal_server='WBSTDBY'
*.fast_start_mttr_target=600
*.log_archive_config='DG_CONFIG=(webcharge,wbstdby)'
*.log_archive_dest_1='LOCATION=/webchargearc/archivelog/
valid_for=(all_logfiles,all_roles)
db_unique_name=webcharge'
*.log_archive_dest_2='SERVICE=wbstdby
lgwr async
valid_for=(online_logfiles,primary_role)
db_unique_name=wbstdby'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_format='webcharge_%t_%s_%r.arc'
*.log_file_name_convert='+DATA/wbstdby/onlinelog/','+DATA/webcharge/onlinelog/'
...


- network file
sys@WEBCHARG> ! cat $GRID_HOME/network/admin/listener.ora
# listener.ora Network Configuration File: /webcharge/app/oracle/product/11.2.0/grid/network/admin/listener.ora
# Generated by Oracle configuration tools.

LISTENER =
  (DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
      (ADDRESS = (PROTOCOL = TCP)(HOST = webcharge)(PORT = 1521))
    )
  )

ADR_BASE_LISTENER = /webcharge/app/oracle

ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON              # line added by Agent

[oracle@webcharge trace]$ cat $GRID_HOME/network/admin/tnsnames.ora
# tnsnames.ora Network Configuration File: /webcharge/app/oracle/product/11.2.0/grid/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.

WEBCHARGE =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = webcharge)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = webcharge)
    )
  )

WBSTDBY =
   (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = wbstdby)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = wbstdby)
    )
  )


- tnsping try
sys@WEBCHARG> ! tnsping wbstdby

TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 20-NOV-2013 09:27:45

Copyright (c) 1997, 2009, Oracle.  All rights reserved.

Used parameter files:
/webcharge/app/oracle/product/11.2.0/grid/network/admin/sqlnet.ora


Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = wbstdby)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = wbstdby)))
OK (0 msec)


- sqlplus connection & service, instance name
[oracle@webcharge trace]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Wed Nov 20 09:26:08 2013

Copyright (c) 1982, 2009, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options

sys@WEBCHARG> show parameter service

NAME                                 TYPE                             VALUE
------------------------------------ -------------------------------- ------------------------------
service_names                        string                           webcharge
sys@WEBCHARG> select instance_name, instance_number, status
  2  from v$instance;

INSTANCE_NAME    INSTANCE_NUMBER STATUS
---------------- --------------- ------------
webcharge                      1 OPEN

-- Physical standby connection from remote primary
sys@WEBCHARG> conn sys/xxx@wbstdby as sysdba
Connected.
idle> show parameter service

NAME                                 TYPE                             VALUE
------------------------------------ -------------------------------- ------------------------------
service_names                        string                           wbstdby
idle> select instance_name, instance_number, status
  2  from v$instance;

INSTANCE_NAME    INSTANCE_NUMBER STATUS
---------------- --------------- ------------
wbstdby                        1 MOUNTED

idle> select protection_mode from v$database;

PROTECTION_MODE
--------------------
MAXIMUM PERFORMANCE



Re: Error with shipping redo log from primary to standby [message #601352 is a reply to message #601351] Tue, 19 November 2013 20:58 Go to previous messageGo to next message
trantuananh24hg
Messages: 609
Registered: January 2007
Location: Ha Noi, Viet Nam
Senior Member
Continue

Physical standby (RHEL 5.5, Oracle 11gr2 Grid Infrastructrue, Enterprise)
- init file
...
*.control_files='+DATA/wbstdby/controlfile/current.ctl'
*.cursor_sharing='FORCE'
*.db_block_size=8192
*.db_create_file_dest='+DATA'
*.db_domain=''
*.db_file_name_convert='+DATA/webcharge/datafile/','+DATA/wbstdby/datafile/'
*.db_name='webcharg'
*.db_recovery_file_dest='+FRA'
*.db_recovery_file_dest_size=10737418240
*.db_unique_name='wbstdby'
*.diagnostic_dest='/webcharge/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=wbstdbyXDB)'
*.fal_server='WEBCHARGE'
*.fal_client='WBSTDBY'
*.fast_start_mttr_target=600
*.log_archive_config='DG_CONFIG=(webcharge,wbstdby)'
*.log_archive_dest_1='LOCATION=/webchargearc/archivelog/
valid_for=(all_logfiles,all_roles)
db_unique_name=wbstdby'
*.log_archive_dest_2='SERVICE=webcharge
lgwr async
valid_for=(online_logfiles,primary_role)
db_unique_name=webcharge'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_format='wbstdby_%t_%s_%r.arc'
*.log_file_name_convert='+DATA/webcharge/onlinelog/','+DATA/wbstdby/onlinelog/'
...


- host file
[oracle@wbstdby ~]$ cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1       localhost.localdomain localhost
10.54.5.177     wbstdby
10.54.5.147     webcharge
10.50.9.60      rtec_system


- ping try
[oracle@wbstdby ~]$ ping webcharge
PING webcharge (10.54.5.147) 56(84) bytes of data.
64 bytes from webcharge (10.54.5.147): icmp_seq=1 ttl=64 time=0.104 ms
64 bytes from webcharge (10.54.5.147): icmp_seq=2 ttl=64 time=0.117 ms
64 bytes from webcharge (10.54.5.147): icmp_seq=3 ttl=64 time=0.097 ms
64 bytes from webcharge (10.54.5.147): icmp_seq=4 ttl=64 time=0.095 ms
64 bytes from webcharge (10.54.5.147): icmp_seq=5 ttl=64 time=0.117 ms

--- webcharge ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3999ms
rtt min/avg/max/mdev = 0.095/0.106/0.117/0.009 ms


- tnsping try and sqlplus connection
[oracle@wbstdby ~]$ tnsping webcharge

TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 19-NOV-2013 09:33:19

Copyright (c) 1997, 2009, Oracle.  All rights reserved.

Used parameter files:
/webcharge/app/oracle/product/11.2.0/grid/network/admin/sqlnet.ora


Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = webcharge)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = webcharge)))
OK (0 msec)
[oracle@wbstdby ~]$ tnsping webcharge

TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 19-NOV-2013 09:33:44

Copyright (c) 1997, 2009, Oracle.  All rights reserved.

Used parameter files:
/webcharge/app/oracle/product/11.2.0/grid/network/admin/sqlnet.ora


Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = webcharge)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = webcharge)))
OK (0 msec)
[oracle@wbstdby ~]$ sqlplus system/xxx@webcharge

SQL*Plus: Release 11.2.0.1.0 Production on Tue Nov 19 09:33:53 2013

Copyright (c) 1982, 2009, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options

system@WEBCHARG> 


- network file
[oracle@wbstdby ~]$ cat $GRID_HOME/network/admin/listener.ora
# listener.ora Network Configuration File: /webcharge/app/oracle/product/11.2.0/grid/network/admin/listener.ora
# Generated by Oracle configuration tools.

LISTENER =
  (DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
      (ADDRESS = (PROTOCOL = TCP)(HOST = wbstdby)(PORT = 1521))
    )
  )

ADR_BASE_LISTENER = /webcharge/app/oracle

ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON

[oracle@wbstdby ~]$ cat $GRID_HOME/network/tnsnames.ora
cat: /webcharge/app/oracle/product/11.2.0/grid/network/tnsnames.ora: No such file or directory
[oracle@wbstdby ~]$ cat $GRID_HOME/network/admin/tnsnames.ora
# tnsnames.ora Network Configuration File: /webcharge/app/oracle/product/11.2.0/grid/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.

WBSTDBY =
   (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = wbstdby)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = wbstdby)
    )
  )

WEBCHARGE =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = webcharge)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = webcharge)
    )
  )
Re: Error with shipping redo log from primary to standby [message #601353 is a reply to message #601352] Tue, 19 November 2013 21:05 Go to previous messageGo to next message
trantuananh24hg
Messages: 609
Registered: January 2007
Location: Ha Noi, Viet Nam
Senior Member
Note: In the single mode, there nothing to do with Oracle HASD if change only IP without host-name, of coure, I must change the IP in network file, host file,. So, I look at the iflist when finish IP change:
Physical Standby:
[oracle@wbstdby ~]$ oifcfg iflist
eth0  10.54.5.0
eth1  10.50.124.0


Primary:
[oracle@webcharge ~]$ oifcfg iflist
eth0  10.54.5.0


Looking at listner log file (primary), I recorgnize one mistake

Fatal NI connect error 12504, connecting to:
 (DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=)(CID=(PROGRAM=oracle)(HOST=webcharge)(USER=oracle)))(ADDRESS=(PROTOCOL=TCP)(HOST=10.54.5.177)(PORT=1521)))

  VERSION INFORMATION:
        TNS for Linux: Version 11.2.0.1.0 - Production
        TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
  Time: 20-NOV-2013 10:01:10
  Tracing not turned on.
  Tns error struct:
    ns main err code: 12564


HOST=webcharge
IP=10.54.5.177

It's wrong, the webcharge host has got IP: 10.54.5.147, and the wbstdby host has got IP: 10.54.5.177
I think I restart listener to bounce, but the error is still.

At Primary:
sys@WEBCHARG> select to_char(timestamp,'YYYY-MON-DD HH24:MI:SS')||'   '||message
  2  from v$dataguard_status;

TO_CHAR(TIMESTAMP,'YYYY-MON-DDHH24:MI:SS')||''||MESSAGE
----------------------------------------------------------------------------------------------------
2013-NOV-19 22:45:55   Error 12504 received logging on to the standby
2013-NOV-19 22:45:55   PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504.
2013-NOV-19 22:51:55   Error 12504 received logging on to the standby
2013-NOV-19 22:51:55   PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504.
2013-NOV-19 22:57:55   Error 12504 received logging on to the standby
2013-NOV-19 22:57:55   PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504.
2013-NOV-19 23:03:56   Error 12504 received logging on to the standby
2013-NOV-19 23:03:56   PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504.
2013-NOV-19 23:09:56   Error 12504 received logging on to the standby
2013-NOV-19 23:09:56   PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504.
2013-NOV-19 23:15:56   Error 12504 received logging on to the standby
2013-NOV-19 23:15:56   PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504.
2013-NOV-19 23:21:56   Error 12504 received logging on to the standby
2013-NOV-19 23:21:56   PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504.
2013-NOV-19 23:27:56   Error 12504 received logging on to the standby
2013-NOV-19 23:27:56   PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504.
2013-NOV-19 23:33:56   Error 12504 received logging on to the standby
2013-NOV-19 23:33:56   PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504.
2013-NOV-19 23:39:56   Error 12504 received logging on to the standby
2013-NOV-19 23:39:56   PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504.
2013-NOV-19 23:45:56   Error 12504 received logging on to the standby
2013-NOV-19 23:45:56   PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504.
2013-NOV-19 23:48:00   ARC3: Beginning to archive thread 1 sequence 298 (2379697-2403118)
2013-NOV-19 23:48:01   ARC3: Completed archiving thread 1 sequence 298 (2379697-2403118)
2013-NOV-19 23:51:56   Error 12504 received logging on to the standby
2013-NOV-19 23:51:56   PING[ARC1]: Heartbeat failed to connect to standby 'wbstdby'. Error is 12504.
...
256 rows selected.


At Standby:
idle> select process,
  2  status,
  3  thread#,
  4  sequence#,
  5  block#,
  6  blocks
  7  from v$managed_standby;

PROCESS   STATUS          THREAD#  SEQUENCE#     BLOCK#     BLOCKS
--------- ------------ ---------- ---------- ---------- ----------
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
MRP0      WAIT_FOR_LOG          1        265          0          0

idle> select to_char(timestamp,'YYYY-MON-DD HH24:MI:SS')||'   '||message from v$dataguard_status;

TO_CHAR(TIMESTAMP,'YYYY-MON-DDHH24:MI:SS')||''||MESSAGE
----------------------------------------------------------------------------------------------------
2013-NOV-18 02:43:49   ARC0: Archival started
2013-NOV-18 02:43:49   ARC1: Archival started
2013-NOV-18 02:43:49   ARC2: Archival started
2013-NOV-18 02:43:49   ARC1: Becoming the 'no FAL' ARCH
2013-NOV-18 02:43:49   ARC1: Becoming the 'no SRL' ARCH
2013-NOV-18 02:43:49   ARC2: Becoming the heartbeat ARCH
2013-NOV-18 02:43:50   ARC3: Archival started
2013-NOV-18 02:44:14   Attempt to start background Managed Standby Recovery process
2013-NOV-18 02:44:14   MRP0: Background Managed Standby Recovery process started
2013-NOV-18 02:44:19   Managed Standby Recovery not using Real Time Apply
2013-NOV-18 02:44:20   Media Recovery Waiting for thread 1 sequence 265

11 rows selected.


I think the Physical site connected to Primary normally, but in opposite, the Pri did not send log to Physical because of network wrong. But I can not find anything wrong else from network file(!?)

May you suggest some thing to me?

Thank you very much!

[Updated on: Tue, 19 November 2013 22:04]

Report message to a moderator

Re: Error with shipping redo log from primary to standby [message #601720 is a reply to message #601353] Sun, 24 November 2013 21:15 Go to previous messageGo to next message
trantuananh24hg
Messages: 609
Registered: January 2007
Location: Ha Noi, Viet Nam
Senior Member
I reconfigure Physical standby but this error still ocurred, I apologized the host-name transfer log from tnsnames in Primary was "webcharge" but not "wbstdby" continue same as above.

Have someone got any idea?

Thank you!
Re: Error with shipping redo log from primary to standby [message #602017 is a reply to message #601720] Thu, 28 November 2013 20:28 Go to previous messageGo to next message
trantuananh24hg
Messages: 609
Registered: January 2007
Location: Ha Noi, Viet Nam
Senior Member
I've got solution for this problem, it causing by 11gr2 bug from net8. It requires restart primary database to apply the parameters, however, I've got not done it since OLTP, I'll take feedback as soon as possible. Still now, to force DG active normally, I must wrote some shell script to synchronization manually between them.

[Updated on: Thu, 28 November 2013 20:28]

Report message to a moderator

Re: Error with shipping redo log from primary to standby [message #602035 is a reply to message #602017] Fri, 29 November 2013 00:52 Go to previous messageGo to next message
Michel Cadot
Messages: 59143
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Quote:
it causing by 11gr2 bug from net8


Which bug? What is its number?

Quote:
It requires restart primary database to apply the parameters


The only parameter that needs to restart the primary is DB_UNIQUE_NAME is you didn't previously set it.
db_file_name_convert and log_file_name_convert require also the restart but not to apply the log, just when you have to create new files on the primary.
All the other parameters are dynamic.

Actually the only thing you had to do is to reload the listener.

Re: Error with shipping redo log from primary to standby [message #602038 is a reply to message #602035] Fri, 29 November 2013 01:05 Go to previous messageGo to next message
trantuananh24hg
Messages: 609
Registered: January 2007
Location: Ha Noi, Viet Nam
Senior Member
Michel Cadot wrote on Fri, 29 November 2013 06:52
Quote:
it causing by 11gr2 bug from net8


Which bug? What is its number?

Quote:
It requires restart primary database to apply the parameters


The only parameter that needs to restart the primary is DB_UNIQUE_NAME is you didn't previously set it.
db_file_name_convert and log_file_name_convert require also the restart but not to apply the log, just when you have to create new files on the primary.
All the other parameters are dynamic.

Actually the only thing you had to do is to reload the listener.



Dear, Michel!
It's not undocument parameter, so far I do not beleive it's successful still I restart database to make apply.
Of course, I've got test cased for listener before post here.
Please wait me until I fix it, or if fail or success I will feed back here.

db_unique_name parameter is set in both of primary and standby, please see above

Thank you!

[Updated on: Fri, 29 November 2013 01:07]

Report message to a moderator

Re: Error with shipping redo log from primary to standby [message #602042 is a reply to message #602038] Fri, 29 November 2013 01:19 Go to previous messageGo to next message
Michel Cadot
Messages: 59143
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

You didn't understand my post.
You said "I do not beleive it's successful still I restart database to make apply" but I claim that you don't need to restart the database unless you didn't PREVIOUSLY set db_unique_name on the primary database. This is the ONLY mandatory parameter that requires the primary database to be restarted. If this parameter was previously set then you don't need to restart the primary database.

I built several hundreds of standby databases and never has to restart the primary ones.

I see that you didn't statically declared the standby database in listener.ora, you should.
Also add the INSTANCE_NAME in the CONNECT_DATA in both tnsnames.ora.

Re: Error with shipping redo log from primary to standby [message #602050 is a reply to message #602042] Fri, 29 November 2013 01:29 Go to previous messageGo to next message
trantuananh24hg
Messages: 609
Registered: January 2007
Location: Ha Noi, Viet Nam
Senior Member
Thank you, Michel, for your immediate reply.
The Instance_name, host_name, sid ... parameters were set to test change before I posted here.

Regards!
Re: Error with shipping redo log from primary to standby [message #602054 is a reply to message #602050] Fri, 29 November 2013 01:44 Go to previous messageGo to next message
Michel Cadot
Messages: 59143
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Quote:
parameters were set to test change before I posted here.


So why is it not in the files you posted?
And what about listener.ora?

Anyway, as I said, if you do correctly do the creation you do not need to restart the primary database.

Re: Error with shipping redo log from primary to standby [message #602055 is a reply to message #602054] Fri, 29 November 2013 01:53 Go to previous messageGo to next message
trantuananh24hg
Messages: 609
Registered: January 2007
Location: Ha Noi, Viet Nam
Senior Member
Michel, thank you for your reply!
Of course, I removed them because they're not necessary while my DG error still occur.
So that, I can attached images (those parameters will be set, the DG situation after setting) if you want to see, do you agree?

[Updated on: Fri, 29 November 2013 02:06]

Report message to a moderator

Re: Error with shipping redo log from primary to standby [message #602768 is a reply to message #602055] Sun, 08 December 2013 20:50 Go to previous messageGo to next message
trantuananh24hg
Messages: 609
Registered: January 2007
Location: Ha Noi, Viet Nam
Senior Member
So, I've successful to take DG operation return.
Now, I take a brief of task lists following test case:

we stop all application and I've got 1 hour to make a solution from DG error 12504.

1- Try to make a solution arround network:

You known, an error occured to my DG is network problem, error 12504. It caused primary could not send log file to standby, however, when connection manually from primary to standby or oppsosite, it's successfully without any error. According to Grid_home/network/admin/*.ora in Primary, I made some changes such as
- Add instance_name to description inside tnsnames.ora
- Change service_name to sid
- Change host_name to IP inside listener.ora
- Trace log from listener whenever testing "log_archive_dest_2=defer; switch back to log_archive_dest_2=service ..."
- Add the parameter HOSTNAME.DEFAULT_SERVICE_IS_HOST=1 to sqlnet.ora (Bug 6374523)

Restart listener, re-bounce listener by srvctl command in Primary (the Standby connected to Primary without any error and it always in wait log state), but error was still occurred, the Primary did not send any log file to Standby.

2- Try to kill archivelog processing:

Sometime ago, I've got an error when archivelog did not send to phyical (of course, it's not network error 12504, and it's another DG), it took me ~2h to define and killing all archivelog processing was a solution. Now, I tried this, but Primary was not still connected to Standby and resent the log file. I saw archivelog, the archivelog process appeared after kill but there was not LSN processing.

3- Add hidden parameter _drop_flashback_logical_operations_enq and restart primary:

Both of Primary and Standby got Flash-back, but the Primary was configured Flash-back after changing IP from Primary. I though may be a trick. Why did I not remove flash_back* parameter in primary? Because the Primary need to use flash_back, adding the hidden parameter _drop_flashback_logical_operations_enq to make a test case, no-more. Finish to restart Primary, we've got DR normally. Last step, I remove the hidden parameter _drop_flashback_logical_operations_enq and restart Primary, open Physical Standby at read-only mode, and DG is good still now.

I'm sorry about the hidden parameter _drop_flashback_logical_operations_enq, I just only think a trick to corrupt flash back operation logical Primary's flashback, it may be a bug or not, it may be a reason or not. And I've not understood still now why that.

Regards!




[Updated on: Sun, 08 December 2013 20:53]

Report message to a moderator

Re: Error with shipping redo log from primary to standby [message #602773 is a reply to message #602768] Mon, 09 December 2013 00:08 Go to previous message
Michel Cadot
Messages: 59143
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Quote:
Restart listener, re-bounce listener by srvctl command in Primary


It is on the STANDBY you have to reload the listener (no need to restart).

Previous Topic: Log applied datetime
Next Topic: applied_scn is lagging behind too much (ODS)
Goto Forum:
  


Current Time: Fri Sep 19 21:31:16 CDT 2014

Total time taken to generate the page: 0.11000 seconds