Screencasts - Hilfsvideos

Oracle backups failing with status code 636

Created: 05 Aug. 2013 • Aktualisiert: 02 Dez. 2013 | 4 Kommentare
Dieses Problem wurde gelöst. Siehe Lösung.

Oracle backups failing intermittenly with status code 636(read from input socket failed). Few backups are successful and few backups are failing. Has anyone noticed this kind of issue ? Backups are using the appliance.

Oracle client -- Solaris and NetBackup version 7.0

Master server -- Linux and NetBackup version 7.5.0.5

Media server -- 5220 appliance

Kommentare KommentareZum neuesten Kommentar

das Bild der Will Restores

Status 636 relates to synthetic backups.  I've not seen that feature used with Oracle backup.  Please attach information on your environment (policy details, rman script, etc.)

Will Restore -- where there is a Will there is a way

das Bild der Ashok Ks

We have not confiured synthetic backups... And we recently migrated the client from master server 7.1.0.3 to 7.5.0.5. It was working fine on old server. On new server also it works fine for sometime.

das Bild der Will Restores

also please attach dbclient log from the Oracle server

Will Restore -- where there is a Will there is a way

das Bild der Ashok Ks

The issue was resolved after making TCP keepalive value to 15 mins. Actually the client is behind firewall.

LÖSUNG