ORA-03135 on TTnn process in Standby Database With Sqlnet.send_timeout
(Doc ID 2285110.1)
Last updated on MARCH 09, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.1 to 12.1.0.2 [Release 12.1]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
If SQLNET.SEND_TIMEOUT is set in the sqlnet.ora file of the Physical Standby Database and the specified timeout has been passed, the connection between TTnn process of the primary database and RFS on standby database disconnected. This issue occurs only on LGWR/ASYNC log transportation. The alert.log reports ORA-3135 on TTnn and TNS-12535 on RFS.
Changes
This problem is reported when following all conditions are satisfied.
- SQLNET.SEND_TIMEOUT is set in sqlnet.ora on Standby Database
- Log Transportation is configured by LGWR / ASYNC (not reproduces with LGWR SYNC)
- Version of Database is 12.1.0.1 or 12.1.0.2 (not reproduces on 11g and 12cR2)
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 |