谁有关于startserver实用程序的资料

杉菜

要详细的，谢谢！

freebob

startserver
Description
Starts an Adaptive Server or a Backup Server. startserver is located in $SYBASE/ASE-12_5/bin.

This utility is not available for Windows NT.

Syntax
startserver [[-f runserverfile] [-m]] ...
Parameters
-f runserverfile

specifies the relative path name of a runserver file, which is used as a reference each time you start an Adaptive Server or Backup Server. By default, the runserver file is in the current directory and is named RUN_servername. If you start a second Adaptive Server on the same machine, startserver creates a new runserver file named RUN_servername.

-m

starts Adaptive Server in single-user mode, allowing only one System Administrator to log in, and turns the allow updates to system tables configuration parameter on. Use this mode to restore the master database. The System Administrator can use the dbo use only parameter of sp_dboption for system administration activities that require more than one process, such as bulk copying or using the data dictionary. startserver normally starts up only one server per node.

The -m parameter creates an m_RUNSERVER file and overwrites any existing m_RUNSERVER file.

Examples
Example 1

Starts an Adaptive Server named SYBASE from the runserver file named RUN_servername in the current directory:


startserver

Example 2

Starts an Adaptive Server named MYSERVER and a Backup Server named SYB_BACKUP:


startserver -f RUN_MYSERVER -f RUN_SYB_BACKUP

Example 3

Starts only the Backup Server SYB_BACKUP:


startserver -f RUN_SYB_BACKUP

Usage

startserver uses the information in the runserver file to start an Adaptive Server or Backup Server. The master device must be writable by the user who starts Adaptive Server.

The startserver command creates the Adaptive Server error log file (named errorlog) in the directory where the server is started, and adds this information as part of the -e parameter in the Adaptive Server executable line in the runserver file. If a second Adaptive Server is started on the same machine, a new error log named errorlog_servername is created&#59; this information is added to that server's runserver file. The user must have execute permission on the specified runserver file.

You can start multiple servers by specifying more than one runserver file, as shown in example 2. You can specify -m after each -f runserverfile.

Adaptive Server derives its running environment from values in the config file. Run sp_configure or edit the config file to see or change configuration parameters.

To ensure the integrity of your Adaptive Server, it is important that you apply appropriate operating-system protections to the startserver executable and the runserver file.


The runserver file

The runserver file, which is created by srvbuild during installation, contains the dataserver command to start Adaptive Server or the backupserver command to start Backup Server. By default, the runserver file is in the current directory and is named RUN_servername. You can edit the runserver file to correct the options and parameters for the commands. The following example shows two sample runserver files.

Runserver file for server MYSERVER:

&num&#59;!/bin/sh&num&#59;&num&#59;
Adaptive Server Information:&num&#59;
  name:                          /MYSERVER&num&#59;
  master device:                 /remote/Masters/myserver_dat&num&#59;
  master device size:                    10752&num&#59;
  errorlog:                      /remote/serverdev/install/errorlog&num&#59;
  interfaces:                    /remote/serverdev/interfaces&num&#59;&num&#59;

/remote/serverdev/bin/dataserver -d/remote/Masters/myserver_dat \
-sMYSERVER -e/remote/serverdev/install/MYSERVER_errorlog \
-i/remote/serverdev &

Runserver file for backup server SYB_BACKUP:

&num&#59;!/bin/sh&num&#59;&num&#59;
Backup Server Information:&num&#59;
  name:                          SYB_BACKUP&num&#59;
  errorlog:                      /remote/serverdev/install/backup.log&num&#59;
  interfaces:                    /remote/serverdev/interfaces&num&#59;
  location of multibuf:          /remote/serverdev/bin/sybmultbuf&num&#59;
  language:                      us_english&num&#59;
  character set:                 iso_1&num&#59;
  tape configuration file:       /remote/serverdev/backup_tape.cfg&num&#59;&num&#59;

/remote/serverdev/bin/backupserver -SSYB_BACKUP \
-e/remote/serverdev/install/backup.log \
-I/remote/serverdev/interfaces \
-M/remote/serverdev/bin/sybmultbuf -Lus_english -Jiso_1 \
-c/remote/serverdev/backup_tape.cfg

杉菜

谢谢，不过好象还有参数-T，怎么没有详细说明，比如-T3604是不检查日志启动，我想要这方面的资料

freebob

Trace flags

我可以贴出来，不过这些都是unsupported functionility,
如果因为这出问题了，sybase是不会帮你的

一定要小心使用!!!!!!!!!!!!!!!!!!!!!!!!!!

Trace flags can be set through dbcc traceon/traceoff or added to the
RUN_SERVER file (i.e. "-T292&quot, depending on their function and the desired effect.

292 - reduces network traffic by suppressing server-to-client "done-in-proc" network
packets in combination with dbcc tune(“doneinproc”,0). (Note: in previous
versions of this QuickRef, trace flag 260 was mistakenly mentioned here&#59; however,
260 was for ASE version 10, and has been replaced with trace flag 292).
299 - don't recompile stored procs inheriting a temp table from a parent proc
302 - print info about the optimizer's index selection
310 - print info about the optimizer's join selection (for better join orders)
317 - print info about the optimizer's join selection (for rejected join orders)
319 - print info on reformatting decisions during query processing
1204 - replaced by config option "print deadlock information"
1213 - used with dbcc object_stats&#59; see there
(12.0) 1608 - starts only engine 0 &#59; for use with dbcc engine ( "online" )
1610 - replaced by config option "tcp no delay"
2512 - dbcc checkalloc will skip syslogs to suppress spurious alloc. errors
3300 - prints detailed info when performing recovery (can be voluminous)
3502 - log checkpointing of databases in the server errorlog
3604 - redirect dbcc output to client session
3605 - redirect dbcc output to the server errorlog
3607 - opens only master device&#59; "master" db is accessible but not recovered
3608 - recovering only "master" db&#59; other databases are accessible but not
recovered&#59; to avoid "log suicide", use "shutdown with nowait" and do not checkpoint.
3609 - all databases are recovered, but tempdb is not re-initialised
3610 - divide-by-zero results in NULL (as in version 4.x), instead of an error
4001 - write every login record to the server errorlog
4012 - don't start checkpoint process
4013 - write loginname, spid and kpid to the server errorlog for every login
4044 - allows to log into server as "sa" when this login is locked
8003 - prints info on RPC calls
8203 - display locking info when deadlock occurs
8399 - used by dbcc monitor to fill sysmonitors table
11201 - Logs CIS client connect- / disconnect- and attention events
11202 - Logs CIS client language, cursor declare, dynamic prepare, and dynamic
execute-immediate text
11203 - Logs CIS client rpc events
11204 - Logs all CIS messages routed to client
11205 - Logs all CIS interaction with remote servers
11209 - For "update statistics" on proxy tables, only get row counts, not complete
distribution statistics
11218 - Cursors involving proxy tables will be "read only" by default

杉菜

太感谢了，这方面的资料太少了，一般都找不到的

jazy

好！真是好资料！谢谢FreeBob兄！
置为精华了！