An update on this. I killed the session waiting on SQLNet break/reset to
client, and RMAN picked back up with the following information:
RMAN-03009: failure of backup command on c1 channel at 01/04/2018 13:04:28
RMAN-10038: database session for channel c1 terminated unexpectedly
channel c1 disabled, job failed on it will be run on another channel
channel c3: starting compressed incremental level 0 datafile backup set
channel c3: specifying datafile(s) in backup set
input datafile file number=00461
name=/oradata/sentry/sentinel/sentinel_nir_111.dbf
input datafile file number=00480
name=/oradata/sentry/sentinel/sentinel_nir_127.dbf
input datafile file number=00967
name=/oradata/sentry/sentinel/sentinel_nir_139.dbf
input datafile file number=01422
name=/oradata/sentry/sentinel/sentinel_nir_160.dbf
channel c3: starting piece 1 at 2018-01-04 13:04:29
I still have no idea why that session "hung" on a sqlnet break/reset to
client however.
Chris
On Thu, Jan 4, 2018 at 10:51 AM, Chris Taylor <
christopherdtaylor1994@xxxxxxxxx> wrote:
12.1.0.2
RHEL 7 64-bit
backup location = NAS storage
Backup Type = Level 0
Backup is of Production Standby DB
Backup does NOT use catalog
I need to know how to dig into this - specifically sid 2269. Can I strace
this or something on linux - how would YOU go about investigating this?
V$SESSION shows:
SID SERIAL# USERNAME PROGRAM
EVENT
WAIT_TIME_SECS WAIT_CLASS
6
2269 28738 SYS rman@hostname.redacted SQL*Net break/reset to client
45461.506918 Application
