dataserver

(UNIX only) The executable form of the SAP ASE program, located in $SYBASE/$SYBASE_ASE/bin.

Syntax

dataserver [-f] [-g] [-G] [-h] [-H] [-m] [-q] [-v] [-X]
	[-A system_role
	[-a path_to_CAPs_directive_file]
	[-b master_device_size [k | K | m | M | g | G | t | T] ]
	[-c config_file_for_server]
	[-d device_name]
	[-D default_db_size]
	[-e path_to_error_log]
	[-i interfaces_file_directory]
	[-K keytab_file]
	[-L config_file_name_for_connectivity]
	[-M shared_memory_repository_directory]
	[-N licinstant]
	[-n system_privileges
	[-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 ] ]
	[-Z initial_master_db_size]

Syntax for the Cluster Edition:

dataserver
-u, --admin-name=sa/sso_name 
	--buildquorum=[force] 
-a, --caps-file=filename 
-F, --cluster-input=filename 
	--cluster-takeover 
-L, --conn-config-file=[filename] 
	--create-cluster-id [=quorum]
-D, --default-db-size=size_spec 
-e, --error-log=[filename] 
-G, --event-log-server=logserv_name 
-f, --forcebuild 
-H, --ha-server 
-h, --help=[{0|1|2|3}[,display_width]]
	--instance=instance_name  
-y, --key-password=[key_password]  
-K, --keytab-file=filename
-N, --license-prop-file=filename 
-z, --logical-page-size=page_size 
-Z, --master-db-size=size_spec 
-d, --master-dev=master_device_name 
-b, --master-dev-size=[size_spec] 
	--master_key_password [=password]
-r, --master-mirror=filename 
-m, --masterrecover 
-g, --no-event-logging 
-n, --permission-login=system_privilege 
-Q, --quorum-dev=quorum_dev 
-q, --recover-quiesced 
-w, --rewrite-db=database_name
-A, --role-logins=system_role
-p, --sa-name={SSO_login_account | sso_role | sa_role} 
-k, --server-principal=s_principal 
-M, --shared-mem-dir=directory_name 
-X, --sybmon 
-T, --trace=trace_flag 
-v, --version

dataserver -v

Parameters

-A system_role – when enable granular permissions is set to 0, and all users are unable to log into the SAP ASE server, provides the server administrator with a login account with sso_role.
-a path_to_CAPs_directive_file – specifies the path to the CAPs directive file.
-b master_device_size [ k | K | m | M | g | G | t | T ] – specifies the size of the master device or database you want to build. The server calculates the sizes, so you can use “K”, “M”, “G”, and “T” instead of exact byte numbers.
-c config_file_for_server – specifies the full path name of an SAP ASE configuration file. Use this parameter to start the SAP ASE 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.
-D default_db_size – declares how large the model database should be when creating a new installation. This sets the size of the smallest permitted database. Syntax is identical to the -b size parameter. -D is only valid when used in conjunction with -b. Default varies by server page size, because the smallest acceptable size is 1024 logical pages: 2 Mb on a 2k page, 4 Mb on an 8k page, and so on. If the flag provides a size smaller than the minimum, the server adjusts it up to the minimum.
-d device_name – is the full path name of the device for the master database. The master database device must be writable by the user who starts the SAP ASE server. If you do not use the -d parameter, the default master database device name is d_master.
-e errorlogfile – is the full path name of the error log file for SAP ASE system-level error messages.
-f – 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.
-G logserv_name – specifies the name of the event log server.
-g – turns off event-logging.
-H – starts the high availability (HA) server, if you have the HA feature installed on your SAP ASE server.
-h – prints this help message, then exists.
-i interfaces_file_directory – specifies the directory location of the interfaces file to search when connecting SAP ASE. If -I is omitted, dataserver looks for a file named interfaces in the directory pointed to by your SYBASE environment variable.
-K keytab_file – specifies the path to the keytab file used for authentication in DCE.
-k, --server-principal=s_principal – specifies the server principal name.
-L config_file_name_for_connectivity – specifies the name the configuration file for connectivity.
-M sharedmem_directory – 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.
--master_key_password [=password] – specifies the master key password when you provide the password on the command line or prompts for a master key password during SAP ASE startup. The password characters are not displayed, and the password is not validated until later in the SAP ASE startup sequence.
If you include the password on the command line, it is visible until the memory is read and used.
-m – starts the SAP ASE server in single-user mode.
-N licinstant – specifies a nondefault directory location for the license cache file. The default location is $SYBASE/$SYBASE_ASE/sysam/server_name.properties.
-n system_privileges – when enable granular permissions is set to 1, and all users are unable to log into the SAP ASE server, provides the server administrator with a login account with change password privilege.
-p sso_login_name – specifies the login name of a system security officer when starting the SAP ASE server, for the purposes of getting a new password for that account. SAP ASE generates a random password, displays it, encrypts it, and saves it in master..syslogins as that account’s new password.
Because SAP ASE 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 the SAP ASE server with -p, immediately log in to the SAP ASE server with the new random password, and execute sp_password to reset your password to a more secure one.
-q – treats quiesced databases as “in recovery.”
-r mastermirror – starts the mirror of the master device. Use this parameter to start the SAP ASE server if the master device has been damaged.
-s servername – specifies the name of the SAP ASE server to start.
If you do not specify an SAP ASE name with the -s parameter, and you have not set the DSLISTEN environment variable, dataserver uses the default SAP ASE 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.
-T trace_flag – specifies a trace flag number.
-u sa/sso_name – specifies the system administrator or system security officer’s name you want to unlock.
-v – prints the version number and copyright message for dataserver, then exits.
-w [master | model] – specifies whether you want to write a master or model database.
When you use the -w parameter, dataserver uses the ascii-8 character set instead of the iso_1 character set. If you require the iso_8 character set for master, load a dump of the master database or change the character set with sqlloc (sqlloc requires the sybsystemprocs database.)
-X – starts this server as sybmon, not dataserver.
-y [password] – 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.
Note: 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 at /usr/local/sybase/certificates/<servername>.crt.

The location of the certificate file changes if you invoke the sp_ssladmin addcert command.
-Z [initial_master_db_size] – declares how large the master database should be when creating a new installation, setting the size of the smallest permitted database. Syntax is identical to the -b size parameter. -D is only valid when used in conjunction with -b. Default varies by server page size, because the smallest acceptable size is 3072 logical pages: 6MB on a 2K page, 12MB on an 8K page, and so on. If the flag provides a size smaller than the minimum, the server adjusts it up to the minimum.
-z page_size [ k | K ] – specifies the page size of the server. 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.

Examples

Create new installation – Creates a new installation with a 100MB master device and a 4K page:
```
dataserver -d my_master_device -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 16K of overhead for its configuration area.
Rewrite database – Rewrites a corrupt model database:
```
dataserver -d d_master -w model -s server_name
```
Rewrite database with device size – Rewrites a corrupt master database, specifying device size:
```
dataserver -d my_master_device -w master -z 4k
```
Rewrite database with device and page sizes – 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 my_master_device -w master -z 4k -b
    100.02M -f
```
Rewrite database with nonmatching page size (generates error) – 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 my_master_device -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).
```
Rewrite database with incorrect page size (generates error) – Rewrites a corrupt master database, specifying an incorrect page size, even in a normal restart. This produces a failure:
```
dataserver -d my_master_device -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.
```
Specify principal name – Specifies the “aseprincipal@myrealm.com” principal name:
```
$SYBASE/$SYBASE_ASE/bin/dataserver -dmaster.dat 
-s secure_ase -k aseprincipal@myrealm.com
```
Prompt for password – Prompts for a master key password:
```
dataserver --master_key_passwd  -dd_master  -eerrorlog
```
List with role – List account names with role sso_role:
```
$SYBASE/$SYBASE_ASE/bin/dataserver 
-d master.dat 
-s server_name
-A sso_role
```
(Cluster Edition) To list account names with role login for sso_role:
```
$SYBASE/$SYBASE_ASE/bin/dataserver 
-d master.dat 
-s server_name
--role-logins sso_role
```

List with change password privilege – List account names with privilege change password:

$SYBASE/$SYBASE_ASE/bin/dataserver 
-d master.dat 
-s server_name
-n "change password"

(Cluster Edition) To list account names with permission logins change password:

$SYBASE/$SYBASE_ASE/bin/dataserver 
-d master.dat 
-s server_name
--permission-logins "change password"

Permissions

Anyone with execute permission on the binary, and who has read/write access to all the files.

After you have finished running the SAP ASE installation program, set the file permissions on the dataserver executable to limit who can execute it.