How to set SQLNet trace on RMAN processes
(Doc ID 1230493.1)
Last updated on APRIL 03, 2020
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 188.8.131.52 [Release 10.1 to 11.2]
Information in this document applies to any platform.
SQLNet tracing may be requested by Oracle Support when RMAN hangs and:
- 10046 trace on the target and catalog show both connections are idle with high waits on 'SQLNet message to/from client'
- RMAN debug trace shows a hang calling an internal routine (one that is NOT being executed AT TARGET or AT RCVCAT) eg
DBGRPC: CMD type=partial resync id=1 status=STARTED
DBGRPC: 1 STEP id=1 status=STARTED chid=default
DBGRPC: krmqgns: no work found for channel d1 (krmqgns)
DBGRPC: EXITED krmqgns with status 1
DBGRPC: krmxcis: xc=436847736 chid=default calling pcicmp
Typically, rman will be making a remote connection to a target or catalog but even a local connection will still use a BEQUEATH SQLNet protocol.
One of the main problems when generating sqlnet tracing is the large number of trace files generated - when tracing rman we are only interested in certain specific processes.
This article will show how to set SQLNet tracing and determine the exact sqlnet trace files to upload to support.
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