Discussion:
Getting Disk read failed for database device during dump
(too old to reply)
unknown
2005-09-22 15:23:47 UTC
Permalink
Hi,
I am getting the following error when one of my cron job
runs for backup...

Sep 21 19:07:48 2005: D00: SYBMULTBUF ERROR: Disk read
failed for database device
Sep 21 19:07:48 2005: Backup Server: 4.139.2.22: [29] The
'read' call failed for device '/exp/dbbackup/CUSTOM_DB.dmp'
with error number 5 (I/O error). Refer to your operating
system documentation for further details. Look for 'Sep 21
19:07:48 2005: D00: SYBMULTBUF ERROR: ' i
n the backup server errorlog for additional information from
SYBMULTBUF.
Can somebody give me any direction as to what might be
happening here? TIA
Mark A. Parsons
2005-09-22 15:51:56 UTC
Permalink
"The 'read' call failed ..."

The SYBMULTBUF process is having a problem reading from a disk ("Duh,
Mark!" ?).

Has this cron job worked before for this same dataserver/database combo?

If you run the cron job again, does it fail at the same point, ie, is
the backupserver log showing the error message at/near the same point in
the dump (load?) every time?

Assuming you're doing a database (or transaction log) dump, you may have
a problem with one of your database devices (these have to be 'read' by
SYBMULTBUF).

Get a list of the devices that your database resides on then have the OS
administrator check said devices for i/o errors/problems.

[If your cron job is performing a load database (or transaction log)
you'll want to take a look at the file system on which the dump file
resides, ie, this is what's being 'read' by the SYBMULTBUF process.]
Post by unknown
Hi,
I am getting the following error when one of my cron job
runs for backup...
Sep 21 19:07:48 2005: D00: SYBMULTBUF ERROR: Disk read
failed for database device
Sep 21 19:07:48 2005: Backup Server: 4.139.2.22: [29] The
'read' call failed for device '/exp/dbbackup/CUSTOM_DB.dmp'
with error number 5 (I/O error). Refer to your operating
system documentation for further details. Look for 'Sep 21
19:07:48 2005: D00: SYBMULTBUF ERROR: ' i
n the backup server errorlog for additional information from
SYBMULTBUF.
Can somebody give me any direction as to what might be
happening here? TIA
unknown
2005-09-22 17:43:32 UTC
Permalink
This cron job always worked before and We ran the cron
several times , it is taking place at the same point since
last 3 days. By the way, we are doing a dump onto a disk
file. TIA
Post by Mark A. Parsons
"The 'read' call failed ..."
The SYBMULTBUF process is having a problem reading from a
disk ("Duh, Mark!" ?).
Has this cron job worked before for this same
dataserver/database combo?
If you run the cron job again, does it fail at the same
point, ie, is the backupserver log showing the error
message at/near the same point in the dump (load?) every
time?
Assuming you're doing a database (or transaction log) dump
, you may have a problem with one of your database
devices (these have to be 'read' by SYBMULTBUF).
Get a list of the devices that your database resides on
then have the OS administrator check said devices for i/o
errors/problems.
[If your cron job is performing a load database (or
transaction log) you'll want to take a look at the file
system on which the dump file resides, ie, this is what's
being 'read' by the SYBMULTBUF process.]
Post by unknown
Hi,
I am getting the following error when one of my cron job
runs for backup...
Sep 21 19:07:48 2005: D00: SYBMULTBUF ERROR: Disk read
failed for database device
Sep 21 19:07:48 2005: Backup Server: 4.139.2.22: [29]
The 'read' call failed for device
'/exp/dbbackup/CUSTOM_DB.dmp' with error number 5 (I/O
error). Refer to your operating system documentation
D00: SYBMULTBUF ERROR: ' i n the backup server errorlog
for additional information from SYBMULTBUF.
Can somebody give me any direction as to what might be
happening here? TIA
RJha
2005-09-26 09:03:30 UTC
Permalink
Hi ,

It looks like a hardware problem .
Check your unix/OS server log for hard/soft error . In case of solaris
it is /var/adm/messages.
It might be give you some hints .


Regards

Loading...