01-27-2017 12:03 AM
I had to try restoring oracle db
this is detailed status of restore
01/26/2017 10:47:46 - begin Restore
01/26/2017 10:47:46 - number of images required: 1
01/26/2017 10:47:46 - media needed: P025L6
01/26/2017 10:47:47 - restoring from image xldb1_1483837071
01/26/2017 10:47:47 - Info bpbrm (pid=9830) xldbcatalog is the host to restore to
01/26/2017 10:47:47 - Info bpbrm (pid=9830) telling media manager to start restore on client
01/26/2017 10:47:47 - Info bpbrm (pid=9830) spawning a brm child process
01/26/2017 10:47:47 - Info bpbrm (pid=9830) child pid: 9848
01/26/2017 10:47:47 - Info bpbrm (pid=9830) listening for client connection
01/26/2017 10:47:48 - Info bptm (pid=9837) Waiting for mount of media id P025L6 (copy 1) on server xlbackup1.
01/26/2017 10:47:48 - started process bptm (pid=9837)
01/26/2017 10:47:48 - mounting P025L6
01/26/2017 10:47:48 - Info bptm (pid=9837) INF - Waiting for mount of media id P025L6 on server xlbackup1 for reading.
01/26/2017 10:47:48 - requesting resource P025L6
01/26/2017 10:47:48 - granted resource P025L6
01/26/2017 10:47:48 - granted resource HP.ULTRIUM6-SCSI.001
01/26/2017 10:47:49 - Info bpbrm (pid=9830) accepted connection from client
01/26/2017 10:47:49 - Info tar (pid=6287) Restore started.
01/26/2017 10:49:57 - mounted P025L6; mount time: 0:02:09
01/26/2017 10:49:57 - Info bptm (pid=9837) P025L6
01/26/2017 10:49:57 - Info bptm (pid=9837) INF - Waiting for positioning of media id P025L6 on server xlbackup1 for reading.
01/26/2017 10:49:57 - positioning P025L6 to file 107
01/26/2017 10:50:31 - positioned P025L6; position time: 0:00:34
01/26/2017 10:50:31 - begin reading
01/26/2017 12:12:01 - Error bptm (pid=9847) cannot write data to socket, Connection reset by peer
01/26/2017 12:12:02 - Error bptm (pid=9847) The following files/folders were not restored:
01/26/2017 12:12:02 - Error bptm (pid=9847) UTF - /bk_65395_1_932716659
01/26/2017 12:12:02 - Info bpbrm (pid=9830) media manager for backup id xldb1_1483837071 exited with status 24: socket write failed
01/26/2017 12:12:02 - Info bpbrm (pid=9830) terminating bpbrm child 9848 jobid=78567
01/26/2017 12:12:02 - restored from image xldb1_1483837071; restore time: 1:24:15
01/26/2017 12:12:02 - end Restore; elapsed time 1:24:16
Failed to get status code information (2850)
"status 24: socket write failed"
is that the problem with buffer size ?
Solved! Go to Solution.
01-27-2017 01:04 AM
Status 24 is network error between server and client (not buffer issue).
Unfortunately there is no quick fix for status 24, as initial connection is fine and data transfer is started. 'Something' outside of NBU at OS or network level then breaks the connection.
Is there a firewall anywhere in the picture?
There could be a firewall timeout that is terminating the connection.
You may want to check KeepAlive settings on master, media server and Oracle client - all should be the same.
KeepAlive setting that is lower than firewall timeout should help.
01-27-2017 01:54 AM
Some times increasing the CLIENT_READ_TIMEOUT can help on Oracle restores.
Have also seen status 24, when the disk on the client has run full when restoring.
01-27-2017 01:04 AM
Status 24 is network error between server and client (not buffer issue).
Unfortunately there is no quick fix for status 24, as initial connection is fine and data transfer is started. 'Something' outside of NBU at OS or network level then breaks the connection.
Is there a firewall anywhere in the picture?
There could be a firewall timeout that is terminating the connection.
You may want to check KeepAlive settings on master, media server and Oracle client - all should be the same.
KeepAlive setting that is lower than firewall timeout should help.
01-27-2017 01:54 AM
Some times increasing the CLIENT_READ_TIMEOUT can help on Oracle restores.
Have also seen status 24, when the disk on the client has run full when restoring.