sp_addumpdevice

Adds a dump device to the SAP ASE server.

Syntax

sp_addumpdevice {"tape" | "disk"}, logicalname,
	physicalname [, tapesize]

"tape" – for tape drives. Enclose tape in quotes.
"disk" – is for a disk or a file device. Enclose disk in quotes.
logicalname – is the “logical” dump device name. It must be a valid identifier. Once you add a dump device to sysdevices, you can specify its logical name in the load and dump commands.
physicalname – is the physical name of the device. You can specify either an absolute path name or a relative path name. During dumps and loads, the Backup Server resolves relative path names by looking in the SAP ASE server’s current working directory. Enclose names containing non-alphanumeric characters in quotation marks. For UNIX platforms, specify a non-rewinding tape device name.
tapesize – is the capacity of the tape dump device, specified in megabytes. Platforms require this parameter for tape devices but ignore it for disk devices. The tapesize should be at least five database pages (each page requires 2048 bytes). You should specify a capacity that is slightly below the rated capacity for your device.

Example 1 – Adds a 40MB tape device. Dump and load commands can reference the device by its physical name, /dev/nrmt8, or its logical name, mytapedump:
```
sp_addumpdevice "tape", mytapedump, "/dev/nrmt8", 40
```
Example 2 – Adds a disk device named mydiskdump. Specify an absolute or relative path name and a file name:
```
sp_addumpdevice "disk", mydiskdump, "/dev/rxy1d/dump.dat"
```

There are additional considerations when using sp_addumpdevice:

sp_addumpdevice adds a dump device to the master.dbo.sysdevices table. Tape devices are assigned a cntrltype of 3; disk devices are assigned a cntrltype of 2.
To use an operating system file as a dump device, specify a device of type disk and an absolute or relative path name for the physicalname. Omit the tapesize parameter. If you specify a relative path name, dumps are made to—or loaded from—the current SAP ASE server working directory at the time the dump or load command executes.
Ownership and permission problems can interfere with the use of disk or file dump devices. sp_addumpdevice adds the device to the sysdevices table, but does not guarantee that you can create a file as a dump device or that users can dump to a particular device.
The with capacity = megabytes clause of the dump database and dump transaction commands can override the tapesize specified with sp_addumpdevice. On platforms that do not reliably detect the end-of-tape marker, the Backup Server issues a volume change request after the specified number of megabytes have been dumped.
When a dump device fails, use sp_dropdevice to drop it from sysdevices. After replacing the device, use sp_addumpdevice to associate the logical device name with the new physical device. This avoids updating backup scripts and threshold procedures each time a dump device fails.
To add database devices to sysdevices, use the disk init command.

See also disk init, dump database, dump transaction, load database, load transaction in Reference Manual: Commands.

The permission checks for sp_addumpdevice differ based on your granular permissions settings.

Setting	Description
Enabled	With granular permissions enabled, you must be a user with `manage disk` privilege.
Disabled	With granular permissions disabled, you must be a user with sso_role.

Values in event and extrainfo columns from the sysaudits table are:

Information	Values
Event	38
Audit option	exec_procedure
Command or access audited	Execution of a procedure
Information in `extrainfo`	Roles – Current active roles Keywords or options – NULL Previous value – NULL Current value – NULL Other information – All input parameters Proxy information – Original login name, if set proxy in effect