The executable form of the Adaptive Server program, located in $SYBASE/ASE-12_5/bin.
This utility is not available for Windows NT.
dataserver [-f] [-g] [-G] [-h] [-H] [-m] [-q] [-v] [-X] [-a path_to_CAPs_directive_file] -b master_device_size [k|K|m|M|g|G] [-c config_file_for_server] [-d device_name] [-e path_to_error_log] [-i interfaces_file_directory] [-K keytab_file] [-L config_file_name_for_connectivity] [-M shared_memory_repository_directory] [-p sa_login_name] [-r mirror_disk_name] [-s server_name] [-T trace_flag] [-u sa/sso_name] [-w master | model database] [-y [password] ] [-z page_size [ k | K ] ]
Or
dataserver -v
forces initialization of a device or database. -f is valid only when used with -b and/or -w. The server fails to boot if you use -f without either -b or -w. -f forces the server in different ways, depending whether -w is present. See -b and -w in the following Usage section.
turns off event-logging.
specifies the name of the event log server.
prints this help message, then exists.
starts the High Availability (HA) server, if you have the HA feature installed on your Adaptive Server.
starts Adaptive Server in single-user mode.
treats quiesced databases as “in recovery.”
prints the version number and copyright message for dataserver, then exits.
starts this server as sybmon, not dataserver.
specifies the path to the CAPs directive file.
specifies the size of the master device or database you want to build. The server calculates the sizes, so you can use “K”, “M”, and “G” instead of exact byte numbers.
specifies the full path name of an Adaptive Server configuration file. Use this parameter to start Adaptive Server with the configuration values in the specified configuration file. If you specify a configuration file with the dataserver -c parameter, make sure all the parameters in this configuration file are compatible before you boot the server. If some of the configuration parameters are incompatible, the server may not boot. To avoid this, do not specify a configuration file when you build the master device. The build phase uses all default settings when you do not specify a configuration file.For more information, see the System Administration Guide.
is the full path name of the device for the master database. The master database device must be writable by the user who starts Adaptive Server. The default master database device name is d_master.
is the full path name of the error log file for Adaptive Server system-level error messages.
specifies the directory location of the interfaces file to search when connecting Adaptive Server. If -I is omitted, dataserver looks for a file named interfaces in the directory pointed to by your SYBASE environment variable.
specifies the path to the keytab file used for authentication in DCE.
specifies the name the configuration file for connectivity.
places shared memory files in the specified directory instead of in the default location, $SYBASE. If sharedmem_directory starts with “/”, the directory name is assumed to be absolute. Otherwise, the directory name is interpreted relative to $SYBASE.
specifies the login name of a System Security Officer when starting Adaptive Server, for the purposes of getting a new password for that account. Adaptive Server generates a random password, displays it, encrypts it, and saves it in master..syslogins as that account’s new password.
starts the mirror of the master device. Use this parameter to start Adaptive Server if the master device has been damaged.
specifies the name of the Adaptive Server to start. If -s is omitted, a server named SYBASE is started.
specifies the System Administrator or System Security Officer’s name you want to unlock.
specifies whether you want to write a master or model database.
allows you to assign a password for the encrypted private key, so that the server prompts the user for a password. This password should match the password you used to encrypt the private key when it was created. You cannot use this parameter when you are running the server in the background.
Although you can set a password with -y,
for security reasons Sybase strongly discourages you from doing
so.
A private key is included with your server's digital certificate. By default, the certificate file located:
/usr/local/sybase/certificates/servername.crt
The location of the certificate file changes if you invoke the sp_ssladmin addcert command.
specifies the page size of the server. You must use -b and -w to use this flag, and name an even power of two between 2k and 16k, or else the server does not boot.
Creates a new installation with a 100 MB master device and a 4k page:
dataserver -d d_master -z 4k -b 100.02M
The spaces between options and their following arguments are optional and acceptable. This example specifies “100.02M” for a 100MB master device because the server requires 16KB of overhead for its configuration area.
Rewrites a corrupt model database:
dataserver -d d_master -w model
Rewrites a corrupt master database, specifying device size:
dataserver -d d_master -w master -z 4k
Rewrites a corrupt master database, specifying device and page sizes, forcing the server to accept these values in preference to what it may find in the config block:
dataserver -d d_master -w master -z 4k -b 100.02M -f
Rewrites a corrupt master database, specifying a page size that does not match what the server finds in its config block. This produces a failure:
dataserver -d d_master -w master -z 8k
00:00000:00000:2001/01/19 12:01:26.94 server The configured server page size does not match that specified on the command line. To use the configured size, omit the command line size; to use the command line size, specify 'force' (-f).
Rewrites a corrupt master database, specifying an incorrect page size, even in a normal boot. This produces a failure:
dataserver -d d_master -z4000
dataserver: the 'z' flag may not be used without 'b' or 'w'. dataserver: server will ignore the 'z' flag. dataserver: the 'z' flag contained an invalid page size. dataserver: the page size must be an even power of two between 2048 and 16384 bytes, inclusive.
dataserver allows you to create devices and databases that are up to 32Gb in size, depending on the limitation of your operating system. For more information on size limits, see the Installation Guide for your platform.
Start Adaptive Server with the startserver command rather than by directly executing the dataserver program. If you need to change any of the default values, edit the RUN_servername file in your Sybase installation directory. See the startserver reference page for details.
Because Adaptive Server passwords are encrypted, you cannot recover forgotten passwords. If all System Security Officers lose their passwords, the -p parameter generates a new password for a System Security Officer account. Start Adaptive Server with -p, immediately log in to Adaptive Server with the new random password, and execute sp_password to reset your password to a more secure one.
After you have finished running the Adaptive Server installation program, set the file permissions on the dataserver executable to limit who can execute it.
If you do not specify an Adaptive Server name with the -s parameter, and you have not set the DSLISTEN environment variable, dataserver uses the default Adaptive Server name SYBASE. The value of the DSLISTEN environment variable overrides this default value, and the -s parameter overrides both the default and the DSLISTEN environment variable.
Automatic login lockouts can cause a site to end up in a situation in which all accounts capable of unlocking logins (System Administrators and System Security Officers) are locked. If this occurs, use the dataserver utility with the -u parameter to check the specified login for System Administrator or System Security Officer authorization, unlock the account, and reset the value of the current failed logins counter to zero.
The effect of -b changes depending on whether -w is present:
-b without -w creates a new master device as named by -d (the default is d_master) and with the page size as specified by -z (the default is 2048):
If the named device already exists as an OS file, the attempt fails, and you see a message such as:
File already exists. You must remove the existing file before attempting to create a new one using the server's -b option.
Unable to create master device.
If the named device names an existing raw partition, the attempt fails unless you include the -f flag. This reinitializes the raw partition as a server master device.
-b with -w master tells dataserver to use the size specified in -z for the master device when recreating the master database. It implies nothing about creating a new device.
-w may or may not require additional flags:
If you use -w model, the -z and -b flags are accepted but ignored.
If you use -w master for new installations, -z and -b are not required because the device size information is stored in the config_block.
If you use -w master to upgrade older installations:
The server requires -b and/or -z if the config_block does not contain a valid entry for the associated size(s). The command fails if it can't get valid data for the page size or device size.
You may provide -b and/or -z when the config_block contains valid entries for the size(s) they represent. However if the sizes do not match what is in the config_block, you must add -f to force your new size preferences.
Anyone with execute permission on the binary, and who has read/write access to all the files.
Commands – disk mirror, disk remirror, disk unmirror
System procedures – sp_ssladmin addcert
Utilities – startserver
