ORA-27192 Tips

Question:  I am getting the ORA-27192 error in RMAN

ORA-27192: skgfcls: sbtclose2 returned error - failed to close file
ORA-19511: Error received from media manager layer, error text:
Failed to process backup file
ORA-19502: write error on file "iwhdbqa_20120529210533_db_iqnc7n6o_1_1", blockno 43110913 (blocksize=512)
ORA-27030: skgfwrt: sbtwrite2 returned error
ORA-19511: Error received from media manager layer, error text:
VxBSASendData: Failed with error:

How do I fix this ORA-27192 error?

Answer: The oerr utility shows this for the ORA-27192 error:

ORA-27192:  Skgfcls: sbtclose2 returned error - failed to close file

Cause: Sbtclose2 returned an error. This happens while closing a backup file during a backup or restore operation.

Action:  This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

This is not an Oracle error per-se, it has to do with the disk or tape.  You need to look for further messages.

On Linux RHEL5 with IBM tapes for LAN free backup and Oracle database - frequent/random errors like below were resolved by tuning the OS:

ORA-27192: skgfcls: sbtclose2 returned error - failed to close file
Error received from media manager layer, error text:

ANS1301E (RC1) This operation cannot continue due to an error on the TSM server. See your TSM server administrator for assistance.

For 32 GB RAM and 1GB LAN network these new setting helped and eliminated these errors

- kernel params:
net.ipv4.tcp_keepalive_time = 1800
net.ipv4.tcp_retries2=7
net.ipv4.tcp_syn_retries=1
net.ipv4.tcp_rmem = 4096 87380 16777216
net.ipv4.tcp_wmem = 4096 65536 16777216
net.ipv4.tcp_mem = 4096 87380 16777216
net.ipv4.udp_mem = 4096 87380 16777216
- network txqueuelen:5000
- open files for root and oracle 16384.

But everybody may adjust its depending on server and oracle demand. What I wanted to say is even though this error seems to come from TSM server - it was resolved from the client.