1 Rookie
•
26 Posts
0
4586
non RMAN, but media manager or vendor specific failure,
Hello Experts.
I am completely new to the networker, I have one query regarding the below error
can any one explain me about it?
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 07/05/2022 01:40:52
ORA-27192: skgfcls: sbtclose2 returned error - failed to close file
ORA-19511: non RMAN, but media manager or vendor specific failure, error text:
Save session with saveset id 05fb22ab-00000006-23c36c70-62c36c70-30de0568-85851eca terminated
(0:5:2)
SQL> show parameter db_name;
NAME TYPE VALUE
------------------------------------ -------------------------------------------- ------------------------------
barry_beckers
393 Posts
0
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?
barry_beckers
393 Posts
1
July 12th, 2022 10:00
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
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.
(edited)
bingo.1
2.4K Posts
0
July 7th, 2022 07:00
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.