I'd start with looking at the nw nmda guide to see if all steps regarding installing and configuring the NW nmda module on client end are followed.
as there is also no info what the rman script contents are or what kind of configuration for the client exists on the nw server, it is difficult to make anything from this, except for the error?
indeed I see one KB article regarding "ORA-27192: skgfcls: sbtclose2 returned error - failed to close file" from 2020
Cause
Cause for RMAN reported error-
Inactivity timeout on backup action/policy
Cause for job indication-
Oracle backup level shall be specified as full on the backup action level on policy regardless of the actual backup level to be taken. Incremental backup level for Oracle backups is specified on RMAN script.
Resolution
On the Incremental Backup Action on Policy for problematic client:
Modify backup level from Incr to Full (after making sure incremental backup is specified as "Incremental level 1" on script)
Modify "Inactivity Timeout" from 30 to 0
Modify "Retries" from 1 to 3
But as said, with more input and further verification from your end, what is done and what is set, would help, especially for yourself if you are new to NW.
In general, this error means that RMAN cannot properly work with NW.
If you google "ora-19511 networker" you will find lots of potential causes - from a NW related error or timeout to RMAN script errors.
So you better sit down with the DB admin who wrote the script (if this has already run) and see how far it will get. If this is a new script you better compare it with a working one.
barry_beckers
393 Posts
2646
0
Posted July 12th, 2022 10:00
I'd start with looking at the nw nmda guide to see if all steps regarding installing and configuring the NW nmda module on client end are followed.
as there is also no info what the rman script contents are or what kind of configuration for the client exists on the nw server, it is difficult to make anything from this, except for the error?