Archive Log Shipments Failing in Environment With Juniper Firewall
(Doc ID 1075432.1)
Last updated on FEBRUARY 18, 2020
Applies to:
Oracle Net Services - Version 9.2.0.6.0 to 12.1.0.2 [Release 9.2 to 12.1]Information in this document applies to any platform.
Symptoms
Archive log shipments are failing between primary and standby. The connection traverses a Juniper firewall.
An Oracle Net server trace generated at the standby database might show:
[000001 03-MAR-2010 04:12:15:528] ntt2err: Read unexpected EOF ERROR on 14
[000001 03-MAR-2010 04:12:15:528] ntt2err: exit
[000001 03-MAR-2010 04:12:15:528] nsprecv: transport read error
[000001 03-MAR-2010 04:12:15:528] nsprecv: error exit
[000001 03-MAR-2010 04:12:15:528] nserror: entry
[000001 03-MAR-2010 04:12:15:529] nserror: nsres: id=0, op=68, ns=12537, ns2=12560; nt[0]=507, nt[1]=0, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
[000001 03-MAR-2010 04:12:15:528] ntt2err: exit
[000001 03-MAR-2010 04:12:15:528] nsprecv: transport read error
[000001 03-MAR-2010 04:12:15:528] nsprecv: error exit
[000001 03-MAR-2010 04:12:15:528] nserror: entry
[000001 03-MAR-2010 04:12:15:529] nserror: nsres: id=0, op=68, ns=12537, ns2=12560; nt[0]=507, nt[1]=0, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
The primary database may throw errors in the alert.log or hang altogether during the log shipment failure.
Changes
Changes to the network that may have required a restart of the Juniper firewall or firewall is new to the environment.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |