ORA-16635: NetSlave connection was broken in the middle of a
transmission session.



ORA-16635: NetSlave connection was broken in the middle of a transmission session...

Answer / guest

Cause: The Data Guard NetSlave process detected a connection
failure to a remote database in the broker configuration.
This failure happened in the middle of a transmission
session. A transmission session usually requires more than
one send operation for sending a large amount of data (e.g.
the broker configuration file) to the remote database. This
error implies the transmission has to be re-started from the
beginning.

Action: In most cases, no user action is required. The Data
Guard broker always tries to re-send the data from the
beginning. If the problem persists, the user will eventually
see this error reported. This will indicate there are some
problems with the network connection between broker managed
databases. Further network troubleshooting should be done to
identify and address the actual problem.

Please add more information about this Error

Is This Answer Correct ?    0 Yes 0 No

Post New Answer

More Oracle Errors Interview Questions

QSM-02051: subquery using the NOT EXISTS clause in mv

1 Answers  


ORA-28140: Invalid column specified

1 Answers  


TNS-00514: Contexts have different wait/test functions

1 Answers  


ORA-39083: Object type string failed to create with error: string Failing sql is: string

1 Answers  


RMAN-08503: piece handle=string comment=string

1 Answers  






ORA-00820: Specified value of sga_max_size is too small, needs to be at least stringM

1 Answers  


RMAN-08055: media recovery complete

1 Answers  


PCC-02400: This host variable must be declared as a pointer type

1 Answers  


NNL-00857: Total rename processing time: string

1 Answers  


ORA-14253: table is not partitioned by Composite Range method

1 Answers  


ORA-33066: (XSAGDNGL32) In AGGMAP workspace object, the hierarchy dimension QDR workspace object must be a hierarchy dimension of the relation.

1 Answers  


NNL-00018: warning: could not contact default name server

1 Answers  


Categories