OK, found the default dump devices in a client's Windows dataserver:
1> sp_helpdevice
2> go
device_name physical_name description
-------------- -------------- -----------------------------------------------
tapedump1 \\.\TAPE0 disk, dump device
tapedump2 \\.\TAPE1 tape, 625 MB, dump device
The device_name is the logical name for a physical dump device. device_name is referenced in 'dump' and 'load'
commands. The dataserver will look for device_name's in the 'dump' command and if it finds one will replace the
reference in the 'dump' command with it's associated physical_name value.
NOTE: The value in device_name can be anything you want (eg, cookie_dough, sushi, etc).
The physical_name is the physical name of the dump device and should reference a valid location for a file (disk or
tape) in your OS. The values listed above (in the default dump devices provided at ASE creation time) are typically
bogus locations on most (all?) OS's.
The description is automatically generated by Sybase based on the arguments provided to sp_addumpdevice
---------------------
In your case you're referencing a bogus definition for 'tapedump1'.
Also notice that 'tapedump1' has been defined as a disk dump device ... which may be causing heartburn for Sybase if
it's trying to issue tape-related commands to what it expects is a disk device.
I'd suggest dropping 'tapedump1' (and 'tapedump2'), and then redefine them to point at valid dump devices in your OS.
Alternatively, skip the creation/use of dump devices and just reference them directly in your 'dump' (and 'load') commands.
Post by Mark A. ParsonsWhen ASE is initially installed a couple bogus tape dump devices are
defined in sysdevices (sp_helpdevice).
I usually drop these (since I don't use them) and as such I don't recall
the exact definition of said devices.
Have you redefined the 'tapedump1' device? If not, then I suspect your
problem is the bogus definition for tapedump1.
Can you provide the output for 'sp_helpdevice tapedump1'?
Post by unknownHi Manish,
Sybase Version is Adaptive Server Enterprise/12.5.3
Operating System Windows Server 2003
without compress mode the backup works fine
dump database master to tapedump1 with init
A) First Attempt
dump database master to tapedump1 with compression=2
Following error shown
The 'WriteFile' call failed for device '\\.\TAPE0' with
error number 87 (The parameter is incorrect).
So 'tapedump1' appears to be defined as '\\.\TAPE0' ... probably not a
valid device on your system, no?
Post by unknownB) Second Attempt
dump database master to 'compress::2::tapedump1' with init
This works fine but does not dump to tape!!!!
OK, it works, but do you get a dump file and if so where is the dump
file placed ($SYBASE\ASE*\install?, c:\windows\system32?) and what is
it's name (tapedump1? TAPE0?)?
Post by unknownBackup Server: 4.132.1.1: Attempting to open byte stream
device: 'compress::2::tapedump1::00'
Server Message: Number 602801, Severity 1
Server 'DEVELOPMENT01_BS', Procedure 'bs_write_header', Line
Backup Server: 6.28.1.1: Dumpfile name 'master081410BB8B '
section number 1 mounted on byte stream
'compress::2::tapedump1::00'
Can you explain this?
While you could look at redefining the 'tapedump1' device
(sp_dropdevice, sp_addevice, sp_helpdevice), you can also directly
reference the tape device using its OS path/name in the dump command, eg,
dump database master to j:\tape1
NOTE: I have no idea how a tape device would be referenced in the
Windows OS. Is it as easy as using the same name that shows up in the
explorer window for the device?