Configuration Guide Adaptive Server® Enterprise 15.
DOCUMENT ID: DC35823-01-1500-04 LAST REVISED: March 2007 Copyright © 1987-2007 by Sybase, Inc. All rights reserved. This publication pertains to Sybase software and to any subsequent release until otherwise indicated in new editions or technical notes. Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of that agreement. To order additional documents, U.S.
Contents About This Book .......................................................................................................................... vii CHAPTER 1 Introduction ..................................................................................... 1 About Adaptive Server ..................................................................... 1 System-specific issues ..................................................................... 2 System user roles .......................................
Contents Stopping Adaptive Server........................................................ Stopping Backup Server.......................................................... Stopping Monitor Server.......................................................... Using the kill command ........................................................... Shutdown and shared memory files ........................................ 24 25 26 26 27 CHAPTER 3 Configuring the Operating System ........................................
Contents 50 How a client uses directory services .............................................. Creating a directory services entry................................................. Supported directory drivers ............................................................ Contents of an interfaces file.......................................................... Heterogeneous and homogeneous environments ......................... Understanding the format of the interfaces file ..............................
Contents Available sort orders................................................................ 90 Language modules......................................................................... 93 Installing a new language module ........................................... 93 Message languages ................................................................ 93 Localization .................................................................................... 94 Localization directories.............................
About This Book This manual, the Configuration Guide, provides instructions for performing specific configuration tasks for Sybase® Adaptive Server® Enterprise on UNIX platforms. The operating system release levels for the UNIX platforms on which Adaptive Server is certified to execute is in the installation documentation or release bulletin for your platform.
Related documents • Chapter 2, “Starting and Stopping Servers” describes how to start and stop Adaptive Server, Backup Server, Monitor Server, and XP Server. • Chapter 3, “Configuring the Operating System” describes how to set up your operating system to work with Adaptive Server. • Chapter 4, “Adaptive Server Default Configuration” provides information about the default parameter settings of Adaptive Server.
About This Book • What’s New in Adaptive Server Enterprise? – describes the new features in Adaptive Server version 15.0, the system changes added to support those features, and changes that may affect your existing applications. • ASE Replicator User’s Guide – describes how to use the Adaptive Server Replicator feature of Adaptive Server to implement basic replication from a primary server to one or more remote Adaptive Servers.
x • Locking – describes how the various locking schemas can be used for improving performance in Adaptive Server. • Optimizer and Abstract Plans – describes how the optimizer processes queries and how abstract plans can be used to change some of the optimizer plans. • Monitoring and Analyzing – explains how statistics are obtained and used for monitoring and optimizing performance.
About This Book Other sources of information • Using Sybase Failover in a High Availability System – provides instructions for using Sybase’s Failover to configure an Adaptive Server as a companion server in a high availability system. • Unified Agent and Agent Management Console – Describes the Unified Agent, which provides runtime services to manage, monitor and control distributed Sybase resources.
• The Sybase Product Manuals Web site is an online version of the SyBooks CD that you can access using a standard Web browser. In addition to product manuals, you will find links to EBFs/Maintenance, Technical Documents, Case Management, Solved Cases, newsgroups, and the Sybase Developer Network. To access the Sybase Product Manuals Web site, go to Product Manuals at http://www.sybase.com/support/manuals/.
About This Book Sybase EBFs and software maintenance v Finding the latest information on EBFs and software maintenance 1 Point your Web browser to the Sybase Support Page at http://www.sybase.com/support. 2 Select EBFs/Maintenance. If prompted, enter your MySybase user name and password. 3 Select a product. 4 Specify a time frame and click Go. A list of EBF/Maintenance releases is displayed.
Element Example Variables—or words that stand for values that you fill in—when they are part of a query or statement, are in italics in Courier font. Type parentheses as part of the command. select column_name from table_name where search_conditions Double colon, equals sign indicates that the syntax is written in BNF notation. Do not type this symbol. Indicates “is defined as”. ::= Curly braces mean that you must choose at least one of the enclosed options. Do not type the braces.
About This Book • pub_id ------0736 0877 1389 Examples of output from the computer appear as follows: pub_name --------------------New Age Books Binnet & Hardley Algodata Infosystems city ----------Boston Washington Berkeley state ----MA DC CA (3 rows affected) In this manual, most of the examples are in lowercase. However, you can disregard case when typing Transact-SQL keywords. For example, SELECT, Select, and select are the same.
For information about how Sybase supports accessibility, see Sybase Accessibility at http://www.sybase.com/accessibility. The Sybase Accessibility site includes links to information on Section 508 and W3C standards. If you need help xvi Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support.
CH A PTE R 1 Introduction Sybase Adaptive Server Enterprise for UNIX is a full-featured Adaptive Server that runs on the following platforms: • HP-UX • IBM AIX • Sun Solaris • Linux 32-bit Note The instructions in this book assume that Adaptive Server is installed and running. For information about installing and starting Adaptive Server, as well as for an overview of Adaptive Server, see the Adaptive Server Installation Guide for your platform.
System-specific issues Adaptive Server also: • Manages multiple databases and multiple users • Keeps track of the data’s location on disks • Maintains the mapping of logical data description to physical data storage • Maintains data and procedure caches in memory Adaptive Server uses these auxiliary programs to perform dedicated tasks: • Backup Server manages database load, dump, backup, and restoration activities. • Monitor Server keeps track of performance data.
CHAPTER 1 Introduction System user roles The Adaptive Server installation and setup process defines various user roles. Different user roles have different responsibilities and privileges. These user roles clarify the way Adaptive Server is to be integrated into your system: • Operating system administrator – the individual who maintains the operating system. This individual has superuser or “root” privileges.
Environment variables • DSQUERY – defines the Adaptive Server name that client programs attempt to connect to if no Adaptive Server is specified with a command line option. If DSQUERY is not set, and you do not supply the Adaptive Server name with a command line option, clients attempt to connect to SYBASE. • SYBASE – defines the path of the Sybase installation directory. The installation program sets up the variable SYBASE to point to the release directory specified during installation.
CHAPTER 1 Introduction When using the source files: SYBASE.csh or SYBASE.sh, the following paths are prepended to the LIBPATH environment variable: $SYBASE/$SYBASE_ASE/lib:$SYBASE/$SYBASE_OCS/ lib: $SYBASE/SYBASE_FTS/lib, etc. Adaptive Server devices and system databases Devices are files or portions of a disk that are used to store databases and database objects. You can initialize devices using raw disk partitions or operating system files.
Adaptive Server devices and system databases • The sample databases, pubs2 and pubs 3, are stored on the master device at installation, but should be moved to a user-defined device after installation. Note For recovery purposes, Sybase recommends that you do not create other system or user databases or user objects on the master device. The sybsystemdb device For new installations the master device also contains the sybsystemdb database.
CHAPTER 1 • Introduction pubs2 and pubs3 – provided as learning tools for Adaptive Server. pubs2 is used for most of the examples in the Adaptive Server documentation; other examples use the pubs3 database. Both are available in U.S. English versions of Adaptive Server. • interpubs – contains French and German data. • jpubs – contains Japanese data. For information about installing the sample databases, see the Installation Guide for your platform, Chapter 3, “Post-Installation Tasks.
Adaptive Server devices and system databases All the job, schedule, and scheduled job information, and data needed by the Job Scheduler task for internal processing is stored in the sybmgmtdb database. Most access to data in the sybmgmtdb database is via stored procedures. The stored procedures make the data available to the GUI, the JS Agent and the command-line interface. Only the Job Scheduler task accesses data directly from the sybmgmtdb database.
CHAPTER 1 Introduction Determining the location, type, and size of a database device Adaptive Server requires several database devices. Table 1-1 below shows baseline values for each of the devices. See the release bulletin for any last minute changes to these values.
Adaptive Server devices and system databases When preparing a raw partition device, follow these guidelines: v • Do not initialize a database device on the partition that contains your Sybase installation software. Doing so destroys all existing files on that partition. • A raw partition designated for use by Sybase cannot be mounted for use by the operating system for any other purpose, such as for file systems or swap space.
CHAPTER 1 Introduction Client/server communication Adaptive Server communicates with other Adaptive Servers, Open Server™ applications (such as Backup Server), and client software on your network. Clients can talk to one or more servers, and servers can communicate with other servers by remote procedure calls. For Sybase products to interact with one another, each product needs to know where the others reside on the network.
Changing Adaptive Server configuration Figure 1-1: Communicating with a server using interfaces file During installation, you use the srvbuild utility to create and configure a new server. The srvbuild process adds entries to the interfaces file for your new Adaptive Server, Backup Server, Monitor Server, and XP Server.
CHAPTER 1 Introduction Languages other than U.S. English If you are running srvbuild in a language other than U.S. English, verify that any input you provide uses a character set that is supported by the us_english character set. Note The us_english character set does not support accent marks, such as tildes (~) and umlauts (ü). This prevents srvbuild from supporting the character sets that use these characters.
Adaptive Server specifications Maximum number of users per database Maximum number of groups per database Table specifications User objects per database Indexes per table Rows per table Columns per composite index 2146484223 1032193 231 – 255 250 (one clustered index) Limited by available storage 31 Creation of clustered index 1.
CHAPTER 1 Practical number of databases participating in one query 16 Maximum number of tables with referential integrity constraints for a query 192 Introduction Includes each occurrence of each database queried and tempdb, if it is used for results or worktables Procedure specifications Number of buffers and procedure buffers Configurable Minimum memory required per stored procedure 2K Maximum number of parameters per stored procedure 2048 Limited by amount of RAM and maximum size of shared m
Adaptive Server specifications Databases 2K page 4K page 8K page 16K page model database tempdb database 3MB 4MB 6MB 6MB 12MB 12MB 24MB 24MB sybsystemdb database 3MB 6MB 12MB 24MB Larger logical page sizes can contain more data. Table 1-5 lists the maximum data for each logical page size.
CH A PTE R 2 Starting and Stopping Servers This chapter describes how to start and stop Adaptive Server, Backup Server, Monitor Server, and XP Server.
Starting servers • The system environment variables discussed in Chapter 1, “Introduction” • Access to SySAM licenses. For more information, see the Sybase Software Asset Management User’s Guide. The installation program creates the interfaces file and system environment variables when you install servers on your computer. Starting servers You can start Adaptive Server, Backup Server, or Monitor Server from the command line by using RUN_server_name files and startserver commands.
CHAPTER 2 Starting and Stopping Servers Changing start-up parameters You cannot change any of these default start-up parameters unless you directly edit the $SYBASE/$SYBASE_ASE/install/RUN_ server_name file. You can also specify additional start-up parameters within the $SYBASE/$SYBASE_ASE/install/RUN_ server_name file. Additional start-up parameters include any valid server command line options listed for the databaserver and backupserver descriptions in the Utility Guide.
Starting servers when the operating system restarts Using the startserver command To start a server from the command line, enter: $SYBASE/$SYBASE_ASE/install/startserver [ -f RUN_server_name file ] where $SYBASE/$SYBASE_ASE/install/startserver is the full path name of the startserver utility, and RUN_server_name file is the full path name of the RUN_server_name file (usually $SYBASE/$SYBASE_ASE/install/RUN_server_name).
CHAPTER 2 Starting and Stopping Servers For HP-UX In HP-UX versions 10.0 and later, you cannot edit commands in the /etc/rc file, so the System Administrator must create a script that executes when the operating system starts or shuts down. For more information about rc (1M), see the HP-UX manual page. You can model your script after the HP-UX template file /sbin/init.d/template. After creating the start-up and shutdown script, place it in the directory /sbin/init.d.
Starting servers when the operating system restarts sleep seconds_of_rest Note To enable restart of a Backup Server when the operating system starts, add a Backup Server start-up command to /etc/inittab. Use the path of the Backup Server RUN_server_name file in this command. For Sun Solaris and Linux Before you set Adaptive Server or Backup Server to start automatically, make sure that all network resources are available. Your server does not start if the network is not running.
CHAPTER 2 ln /etc/init.d/script_name Starting and Stopping Servers /etc/rc#.d/S##script_name For Linux: Use ln -s to create symbolic links from the script name to the appropriate run control (rc) directory, rc# where # is the run level. Use syntax like the following: ln -s /etc/init.d/script_name /etc/rc#.d/S##script_name When you type the command to create this link, add an uppercase “S” and a two-digit sequence number preceding the name of the script file. “S” indicates a start-up file.
Starting XP Server after initial installation Starting XP Server after initial installation If you install Adaptive Server and XP Server in the same build session, srvbuild automatically adds information about the XP Server to the sysservers table of Adaptive Server.
CHAPTER 2 2 Starting and Stopping Servers Enter: 1> shutdown 2> go The default for shutdown uses the with wait option, which allows Adaptive Server to finish executing SQL statements or procedures, perform a checkpoint in each database, disable new logins, and perform other shutdown tasks. Issuing the shutdown command prints a message like this to the sterr file: Server SHUTDOWN by request.The SQL Server is terminating this process. CT-LIBRARY error: This is normal behavior.
Stopping servers This is normal behavior. If a message indicates that Adaptive Server or Backup Server is waiting for processes to complete, and you must stop Adaptive Server or Backup Server immediately, use shutdown with nowait, which neither waits for currently executing statements to finish, nor performs checkpoints in every database. Using shutdown with nowait for Backup Server can cause inconsistent or incomplete dumps and loads. Use this command only when necessary.
CHAPTER 2 Starting and Stopping Servers kill pid where pid is the process identification of any dataserver or backupserver process, as determined by the showserver command. Killing one engine for a particular Adaptive Server kills all engines for that server. If more than one Adaptive Server is running on the same system, be careful that the engine you kill is associated with the correct Adaptive Server.
Stopping servers If Adaptive Server is configured with a memory size that is greater than the MAXSHMSEGSIZE parameter in the operating system then Adaptive Server may create additional shared memory segments and for every additional shared memory segment that it creates, an additional file with SERVER_NAME.srg[N] (where N ranges from 0 – N), is created under $SYBASE/$SYBASE_ASE. When Adaptive Server is shut down in a normal manner, the shared memory files are automatically removed.
CH A PTE R 3 Configuring the Operating System This chapter discusses the operating system configuration settings that you can adjust after installing or upgrading Adaptive Server. Unless stated otherwise, the information pertains to all supported UNIX platforms.
Configuring new servers with srvbuild You may want to verify that the Adaptive Server environment variables in Table 3-1 are set correctly. To check the current value of environment variables, enter the following command at the operating system prompt: env Table 3-1 describes the system environment variables for Adaptive Server.
CHAPTER 3 5 Configuring the Operating System In the Adaptive Server type screen, select the: • Server page size • Master device path • Master device size • Master database size • Sybsystemprocs device path • Sybsystemprocs device size • Sybsystemprocs database size • Error log • Transport type • Host name • Port number In the Edit Advance Adaptive Server Attributes tab, enter: 6 Configuration Guide • Adaptive Server configuration file • Sybsystemdb device path • Sybsystemdb
Configuring new servers with srvbuild • 7 8 9 Port number To configure Monitor Server, select the following information in the Monitor Server screen: • Maximum number of connections • Error log • Configuration file • Shared memory directory • Transport type • Host name • Port number In the XP Server type screen, select: • Transport type • Host name • Port number In the Full-Text Search SDS type screen, select: • Error log • Collection directory • Default database • Language
CHAPTER 3 • Sybmgmtdb database size • Transport type • Host name • Port number Configuring the Operating System 11 In the “Configure Self Management...
Restoring correct permissions Restoring correct permissions Sybase software files and directories are installed with the correct access permissions. If you notice that the permissions are no longer correct, you can restore the correct permissions with the script setperm_all, located in the $SYBASE/$SYBASE_ASE/install directory.
CHAPTER 3 Configuring the Operating System For Linux The number of file descriptors per process is limited to 10,000. You can set the number of file descriptors using ulimit. For Sun Solaris For Sun Solaris, you can set both soft and hard limits for file descriptors. The soft limit can be increased up to the hard limit by the user, but the hard limit can be increased only by someone with “root” permissions.
File descriptors and user connections ulimit -Sn new_value where n is the current value for the soft limit, and new_value is the value to which you want to increase the soft limit. Note You can use the preceding commands in your RUN_server_name file to increase the hard and soft limits. The RUN_server_name file is a Bourne shell script, be sure to use the Bourne shell versions of these commands in the RUN_server_name file.
CHAPTER 3 Configuring the Operating System where program_name is the name of the compiled program, and master_device_name is the full path of Adaptive Server’s master device. Instead of typing the command at the operating system prompt, you can add program_name preceding the dataserver command line in the Adaptive Server RUN_server_name file. Sample program Note This is an sample script; modify it as necessary.
Enabling asynchronous disk I/O setuid(uid); /* run the program indicated as arguments to this program */ execv(*++argv, argv); } For additional information on user connections, see the System Administration Guide. Enabling asynchronous disk I/O For HP-UX This step is mandatory for HP users. To improve I/O performance on character or raw and block devices, enable asynchronous I/O by installing the HP asynchronous I/O driver from SAM.
CHAPTER 3 4 HP-UX 11.23 Configuring the Operating System At the UNIX prompt, execute the following statements as “root”. The user ID of the user who is starting Adaptive Server and Backup Server must be the owner of the /dev/async directory. This step is mandatory for HP users. To improve I/O performance on character or raw block devices, enable asynchronous I/O by installing the HP asynchronous I/O driver from SAM.
Enabling asynchronous disk I/O # ls /dev/asyn* idev/async /dev/asyncdsk For IBM AIX Enable asynchronous disk I/O. This step is mandatory for IBM users. Enable asynchronous I/O by adjusting the kernel parameters, using the System Management Interface Tool (SMIT): 1 Enter “smit” at the UNIX prompt. 2 From the Devices menu, select Asynchronous I/O. 3 Select Change/Show Characteristics of Asynchronous I/O.
CHAPTER 3 Configuring the Operating System Adjusting the client connection timeout period Adaptive Server uses the KEEPALIVE option of the TCP/IP protocol to detect clients that are no longer active. When a connection to a client is inactive for a period of time (the timeout period), the operating system sends KEEPALIVE packets at regular intervals.
Checking for hardware errors For Sun Solaris To display the timeout value, enter: /usr/sbin/ndd -get /dev/tcp tcp_keepalive_interval To reduce the timeout period to 15 minutes (900,000 ms.), enter: /usr/sbin/ndd -set /dev/tcp tcp_keepalive_interval 900000 For Linux To display the timeout value, enter: /sbin/sysctl -e net.ipv4.tcp_keepalive_time To reduce the timeout period to 15 minutes (900 seconds,) enter: /sbin/sysctl -w net.
CHAPTER 3 Configuring the Operating System For IBM RS/6000 The errpt command includes several options for limiting the report to events that match certain criteria. Use the errpt command on a regular basis. If errors appear, use the diagnostic tool diag to check your memory and disks. Or use the System Management Interface Tool (SMIT) to run the errpt command. This command may produce a lot of output. For Sun Solaris Check the /var/adm/messages file on a regular basis.
Monitoring the use of operating system resources • The ps command provides a snapshot of accumulated CPU time and usage for individual processes. • The time command can be useful in determining the various user, system, and real-time resources used over a complete run. For details about these tools, see your operating system documentation.
CHAPTER 3 Configuring the Operating System • The ps command gives you an accurate snapshot of accumulated CPU time and usage for individual processes. This can be very helpful in determining the dataserver-, engine-, and process-specific loading. • The time command can be useful in determining the various user, system, and real-time resources used over a complete run. For details about these tools, see your operating system documentation.
A sample C shell maintenance script Next, the script invokes an isql backup script for each database for which no 2500-level errors occurred and adds the “Backing up database_name” line to dbcc_mail.out. For example, the script master.backup backs up the master database: use master go dump database master to master_dump go You may want to add appropriate dump transaction commands to your scripts. If there are 2500-level error messages, the script does not back up the database.
CH A PTE R Adaptive Server Default Configuration 4 When you install or upgrade Adaptive Server, it includes some default parameter settings and a few of its auxiliary programs. After installing and testing this “default” Adaptive Server, you can configure it to your system’s needs and install other optional features. For information about configuring Adaptive Server, Backup Server, and Monitor Server see the System Administration Guide.
Default settings Item Default value • Character set HP – Roman8 IBM – ISO 8859-1 Sun – ISO 8859-1 • Sort order Linux – iso_1 Linux – Binary ordering Login security mode Standard Table 4-2 lists the default settings for the Backup Server, Monitor Server, and XP Server. For more information about these servers, see “Introduction” on page 1.
CH A PTE R 5 Setting Up Communications Across the Network Adaptive Server can communicate with other Adaptive Servers, Open Server applications, and client software across a network. Clients can communicate with one or more servers, and servers can communicate with other servers via remote procedure calls.
How Adaptive Server determines which directory service entry to use Servers also need network information. When a server starts up, it looks in its interfaces file to determine where to listen for client connection requests. In addition, Adaptive Server can take on a client role when it makes remote procedure calls to other Adaptive Servers. Table 5-1 shows where to find more information on server and client interfaces file tasks and topics.
CHAPTER 5 Setting Up Communications Across the Network 3 Looks in directory services for an entry whose name matches the name found in the steps above. 4 It uses the network information provided by the directory services entry it has found to listen for client connections. How a client uses directory services When a client connects to a server it: • Determines the name of the server either programmatically or by referring to the DSQUERY environment variable.
Supported directory drivers Supported directory drivers There are three supported drivers: • interfaces driver • Lightweight Directory Services driver. • Cell Directory Service (CDS) provided by Distributed Computing Environment (DCE) This remainder of this chapter describes the interfaces file and provides specific configuration information for each supported UNIX platform.
CHAPTER 5 Setting Up Communications Across the Network A client’s interfaces file does not need a master line. It functions correctly with only a query line. If your site has multiple installations If you have more than one Adaptive Server installation, each server’s interfaces file should contain information about all servers on the network. If all of your server products are running on the same platform, you can create one master interfaces file and copy that file to each machine.
Heterogeneous and homogeneous environments Figure 5-1: Establishing network connections in a heterogeneous environment PC clients Get Harpo’s address and connect. PC clients Get Chico’s address and connect. sql.ini Harpo SQL server Make a remote procedure call to Chico. [Harpo] xxxxx [Chico] interfaces Chico SQL server Harpo xxxxx Chico xxxxx xxxxx If both a client and a server are running under UNIX, the same interfaces file is valid for both.
CHAPTER 5 Setting Up Communications Across the Network Figure 5-2: Establishing network connections in a homogeneous environment Harpo SQL server Homogeneous clients Get Harpo’s address and connect. Get Chico’s address and make an RPC. Harpo xxxxx Chico xxxxx Get Chico’s address and connect.
Understanding the format of the interfaces file servername retry_attempts delay_interval service_type api protocol device address filter ha_failover servername A TCP style entry looks like: servername retry_attempts delay_interval service_type protocol network machine port filter ha_failover servername Components of an interfaces file entry Table 5-2 describes the components of an interfaces file entry.
CHAPTER 5 Setting Up Communications Across the Network Component Value machine Network name or address of server’s host machine. You can use either the host name or Internet address. Maximum size of entry is 32 bytes. To determine the host name of a machine, log in to that machine and enter: /bin/hostname device The network device endpoint. For TCP networks, the device varies according to the vendor supplying the networking software. Check the vendor-specific documentation for the name of the device.
Creating a master interfaces file Creating a master interfaces file A master interfaces file contains entries for all Sybase servers on the network. It can be used with every server and client connected to the network. By distributing copies of a master interfaces file, you can ensure that all Sybase products on the network interact with one another.
CHAPTER 5 Setting Up Communications Across the Network 1 Concatenate the individual interfaces files. 2 Make a copy of the file. 3 Use an ASCII text editor to modify the copy of the concatenated file. Note When you manually edit an interfaces file, be sure that, for each entry, each line following the first line begins with a character. The following elements must be correct and unique in the resulting file: • servername – each server entry in the interfaces file must be unique.
Configuring interfaces files for multiple networks 2 In your interfaces file, use a text editor to add copies of the “master” line for your Adaptive Server; one for each additional interface you want the server to listen on. 3 Include a unique host name on each line to configure a network handler for each network interface. 4 Port numbers within the interface need not be the same, but they can be. They fall under the same rules for naming and numeric range as the primary network interface.
CHAPTER 5 Setting Up Communications Across the Network Using one network-independent DSQUERY name If uniform client DSQUERY naming is important, you can make the necessary changes in the network addressing of the clients in the interfaces file. You can install separate Sybase installation directories and distinct interfaces files on client file servers on each network to allow users to connect to the correct network address.
Configuring interfaces files for multiple networks You can concatenate the original server name and the network name. For example, if your server is named PRODUCTION, you could choose the names PRODUCTION_network1 and PRODUCTION_network2. 2 Do one of the following: • For PC clients, use sqledit to create multiple sql.ini file entries for the server, one for each network. In the following example, you create one entry for PRODUCTION_network 1 and one for PRODUCTION_network2.
CHAPTER 5 Setting Up Communications Across the Network The following example shows how to configure a backup network that will be used only if the normal connection fails. The primary network is “corporate network” and backup is “engineering network.
IPv6 support • IPv6-enabled – an application that, in addition to being IPv6-aware, takes advantage of some IPv6 features. • IPv6-required – an application that requires some IPv6 features and cannot operate over IPv4. IPv6 Infrastructure: IPv6 infrastructure Dual Stack infrastructure implements both IPv4 and IPv6. This is the recommended infrastructure implementation for using Adaptive Server Enterprise as an IPv6-aware server. Sybase applications are IPv6-aware.
CHAPTER 5 Setting Up Communications Across the Network • RPC mechanisms • Job Scheduler Task / Agent session connection • Network Host API • UDP Message support for sybsendmsg • Component Integration Services connectivity • Host / name resolving • XML URL connection handler • Auditing for client address data The following functional mechanisms in Adaptive Server Enterprise do not support IPv6. These mechanisms in Adaptive Server Enterprise are IPv6unaware.
Troubleshooting Before starting Adaptive Server for IPv6-aware operations, make sure that your infrastructure is correctly set up. Once your operating system is correctly configured, an IPv6 connection handler can be configured and enabled. Configuring and enabling the IPv6 connection handler requires adding an additional DCL entry. A single Adaptive Server configuration can typically carry up to 32 connection handler assignments within the DCL.
CHAPTER 5 Setting Up Communications Across the Network 2 00:00000:00002:2003/09/22 12:37:23.68 server 00:00000:00002:2003/09/22 12:37:23.68 kernel listeners have failed. Shutting down. 00:00000:00002:2003/09/22 12:37:23.68 kernel 00:00000:00016:2003/09/22 16:11:35.46 server v Unable to initialize network 0 ninit: All master network ueshutdown: exiting SQL Server shutdown by request. Investigating the port assignment 1 Look in the interfaces file to identify the port number assigned to the server.
Troubleshooting information on how to bring XP Server up. XP Server cannot start because the port number may be in use by another process. Use the netstat command described in the previous section to determine if the port number specified for XP Server is in use. If you find no processes using the same port number: 1 Restart Adaptive Server. 2 Execute the ESP that you attempted earlier. XP Server should start automatically.
CH A PTE R 6 Using the Lightweight Directory Access Protocol as a Directory Service Adaptive Server uses directory services to establish client and RPC connections over the Internet. This chapter provides information about using LDAP directory services to establish connections. Topic Overview LDAP directory services versus the Sybase interfaces file Page 69 70 The libtcl*.
LDAP directory services versus the Sybase interfaces file The LDAP server stores and retrieves information about: • Adaptive Server, such as IP address, port number, and network protocol • Security mechanisms and filters • High availability companion server name The LDAP server can be configured with these access restrictions: • Anonymous authentication – all data is visible to any user.
CHAPTER 6 Using the Lightweight Directory Access Protocol as a Directory Service • A network-based alternative to the traditional Sybase interfaces file • A single, hierarchical view of information, including users, software, resources, networks, files, and so on Table 6-1 highlights the differences between the Sybase interfaces file and an LDAP server.
LDAP directory services versus the Sybase interfaces file Attribute name Value type Description sybaseAddress String Each server address includes: • Protocol: TCP, NAMEPIPE, SPX DECNET (entry is case sensitive). • Address: any valid address for the protocol type. Note dscp splits this attribute into Transport type and Transport address. sybaseSecurity (optional) String Security OID (object ID).
CHAPTER 6 Using the Lightweight Directory Access Protocol as a Directory Service In the example above, the entry describes an Adaptive Server named “foobar” listening on a TCP connection with a port number of 5000. This entity also specifies a retry count of 12 (times) and a retry delay of 30 (seconds). Once a client has found an address where a server responds, the login dialog between the client and the server begins.
Enabling LDAP directory services You should edit both the libtcl.cfg and the libtcl64.cfg files to ensure compatibility between 32- and 64-bit applications. The default libtcl.cfg file is located in $SYBASE/$SYBASE_OCS/config. If LDAP is specified in the libtcl.cfg file, the interfaces file is not used. Note Open Client/Open Server applications that use the -I option at start-up override the libtcl.cfg file and use the interfaces file. In its simplest form, the libtcl.
CHAPTER 6 Using the Lightweight Directory Access Protocol as a Directory Service • Add the LDAP URL under the [DIRECTORY] entry. See Table 6-3 for supported LDAP URL values. Warning! The LDAP URL must be on a single line. libtcl.cfg ldap+libsydblad.so ldap://host:port/ditbase??scope??bindname=username password libtcl64.cfg ldap=libsydbldap64.so ldap://host:port/ditbase??scope??bindname=username password For example: [DIRECTORY] ldap=libsydbldap.
Adding a server to the directory services Adding a server to the directory services Warning! Most LDAP servers have an ldapadd utility for adding directory entries. Sybase recommends you use dsedit instead since it has built-in semantic checks that generic tools do not provide. Each server entry is made up of a set of attributes. When you add or modify a server entry, you are prompted for information about server attributes. Some attributes are provided by default, others require user input.
CHAPTER 6 Using the Lightweight Directory Access Protocol as a Directory Service For example: ldap://huey:11389/dc=sybase,dc=com??one Note Microsoft Internet Explorer does not recognize LDAP URLs. For more information about dscp, see the Open Client/Server Configuration Guide, in the 11.1.x Generic Collection at http://www.sybase.com/support/manuals. Multiple directory services Any type of LDAP service, whether it is an actual server or a gateway to other LDAP services, is called an LDAP server.
Encrypting the password Encrypting the password Entries in the libtcl.cfg file are in human-readable format. Sybase provides a pwdcrypt utility for basic password encryption. pwdcrypt is a simple algorithm that, when applied to keyboard input, generates an encrypted value that can be substituted for the password. pwdcrypt is located in $SYBASE/$SYBASE_OCS/bin. From the $SYBASE/$SYBASE_OCS directory, enter: bin/pwdcrypt Enter your password twice when prompted. pwdcrypt generates an encrypted password.
CHAPTER 6 Using the Lightweight Directory Access Protocol as a Directory Service Migrating from the interfaces file to LDAP There is no direct method to upgrade an existing server using the interfaces file to one that uses lightweight directory services. To upgrade a previous release of Adaptive Server to Adaptive Server version 15.0, see the Installation Guide for Windows. Once you have upgraded the server, you can configure your server to use LDAP service. Configuration Guide 1 Shut down the server.
Migrating from the interfaces file to LDAP 80 Adaptive Server Enterprise
CH A PTE R 7 Customizing Localization for Adaptive Server This chapter provides information about Sybase localization support for international installations, including configuring languages, character sets, and sort order. For more information, see the System Administration Guide.
Overview of localization support • • • Latin America • Asia Translated system messages – Adaptive Server includes language modules for: • Brazilian Portuguese • Chinese (Simplified) • French • German • Japanese • Korean • Polish • Spanish • Thai Translated documentation – translated documentation is available in: • Chinese (Simplified) • French • German • Japanese • Korean Language modules Adaptive Server stores its localized software messages in separate language modules.
CHAPTER 7 Customizing Localization for Adaptive Server Default character sets for servers The default character set is the character set in which data is encoded and stored on the Adaptive Server databases. Changing the default language and character set Warning! Make all changes to the character set and sort order for a new Adaptive Server before creating any user databases or making any changes to the Sybase-supplied databases.
Overview of localization support By default, when Adaptive Server and Backup Server are installed on HP systems, the installation installs the character set files for ROMAN8, which supports the Western European languages. Changing the default character set for servers You can select any character set as the default on Adaptive Server, including character sets that are not the platform default character sets.
CHAPTER 7 Customizing Localization for Adaptive Server • Hebrew – see Table 7-8 on page 87. • Japanese – see Table 7-9 on page 87. • Korean – see Table 7-10 on page 87. • Thai – see Table 7-11 on page 87. • Turkish – see Table 7-12 on page 88. • Unicode (which supports over 650 languages) – see Table 7-13 on page 88. • Vietnamese – see Table 7-14 on page 88. • Western European – see Table 7-15 on page 88.
Overview of localization support Table 7-3: Simplified Chinese character sets Character set eucgb Unilib required X cp936 X Description EUC GB encoding = Simplified Chinese character sets Microsoft Simplified Chinese character sets gb18030 X PRC 18030 standard Table 7-4 lists the traditional Chinese character set: Table 7-4: Traditional Chinese character set Character set Unilib required Description cp950 euccns X X big5 X PC (Microsoft) Traditional Chinese EUC CNS encoding = Traditional Chi
CHAPTER 7 Customizing Localization for Adaptive Server Table 7-7: Greek character sets Character set cp869 Unilib required Description IBM PC Greek cp1253 greek8 MS Windows Greek HP GREEK8 iso88597 ISO 8859-7 Latin/Greek Table 7-8 lists the Hebrew character set: Table 7-8: Hebrew character sets Character set cp1255 Unilib required X Description Microsoft Windows Hebrew iso88598 X ISO 8859-8 Hebrew Table 7-9 lists the Japanese character set: Table 7-9: Japanese character sets Character set Un
Overview of localization support Table 7-12: Turkish character sets Character set cp857 Unilib required Description IBM PC Turkish cp1254 iso88599 Microsoft Windows Turkish ISO 8859-9 Latin-5 Turkish turkish8 HP TURKISH8 Table 7-13 lists the Unicode character set: Table 7-13: Unicode character set Character set utf8 Unilib required X Description Unicode UTF-8 encoding Table 7-14 lists the Vietnamese character set: Table 7-14: Vietnamese character set Character set cp1258 Unilib required X Descr
CHAPTER 7 Customizing Localization for Adaptive Server Character set conversion Backup Server passes messages to Adaptive Server in the client’s language and in the Adaptive Server character set. Adaptive Server then converts the messages and issues them in the client’s language and character set.
Sort orders When a localized client application connects to Adaptive Server, the server checks to see if it supports the client’s language and character set. • If Adaptive Server supports the language, it automatically performs all character set conversions and displays its messages in the client’s language and character set. • If Adaptive Server does not support the language, it uses the user’s default language or Adaptive Server’s default language.
CHAPTER 7 Customizing Localization for Adaptive Server Sort orders are located in sort order definition files (.srt files) that accompany your character set definition files. Note Available sort orders vary according to the character set installed on Adaptive Server. You can see the available sort orders for your character set by looking in the .srt file for your language. Sort orders are stored in: $SYBASE/charsets//*.
Sort orders Sort order name Description Dictionary order, case insensitive with preference Case-insensitive dictionary sort order, with case preference for collating purposes. A word written with uppercase letters is equivalent to the same word written with lowercase letters. Uppercase and lowercase letters are distinguished only when you use an order by clause. The order by clause sorts uppercase letters before it sorts lowercase.
CHAPTER 7 Customizing Localization for Adaptive Server Language modules If you want Adaptive Server error messages to be displayed in a language other than U.S. English (us_english), you must install the appropriate language module. When you install a new language module, installation automatically loads the language into the Sybase installation directory to support the new language. For information about directories, see “Localization directories” on page 94.
Localization For example, if your client’s language is Latin, the Spanish language module is installed, and Spanish is specified as the Adaptive Server default language, the client receives messages in Spanish. Localization By default, the Adaptive Server and Backup Server configurations use the English locale settings, which include: • Character set definition files for Western European character sets • Sort-order definition files for Western European character sets • U.S.
CHAPTER 7 Customizing Localization for Adaptive Server About the directory The $SYBASE/locales directory contains a subdirectory for each available language. Each language subdirectory contains a subdirectory for each character set available with that language. • The .loc files in these subdirectories enable Adaptive Server or Backup Server to report errors in a specific language, encoded in a specific character set. There are a variety of .loc files in each subdirectory.
Localization • platform_locale is the platform-specific keyword for a locale. For acceptable values, see your operating system documentation. When the locale being defined as the default for the site, platform_locale is “default.” • syb_language is the name of the language directory to be used from within $SYBASE/locales/language_name.
CHAPTER 7 Customizing Localization for Adaptive Server Editing the locales.dat file Before beginning the edit, make a copy of the original file, in case you have problems with the resulting edited version. To edit the locales.dat file: 1 Open the locales.dat file copy in a text editor.
Changing the localization configuration During the installation process and through reconfiguration, you can specify a different language, character set, and sort order. Adaptive Server localization Each language uses about 2MB of database space per module. If necessary, use the alter database command to increase the size of the master database before adding another language.
CHAPTER 7 Customizing Localization for Adaptive Server Backup Server localization You can change the Backup server language and character set by modifying the RUN_ file. See the Utility Guide for more information on the backupserver command arguments. Configuring Adaptive Server for other character sets To configure Adaptive Server with the character set and sort order for your language, complete the following steps. Your system messages appear in the default language, English.
Changing the localization configuration 6 Use your normal process on your UNIX system to reboot the server, usually by invoking one of the RUN_xxx scripts from $SYBASE/$SYBASE_ASE/install. 7 The server starts, rebuilds all the system indexes, then shuts down. Restart a second time to bring the server up in a stable state. Sort orders Table 7-17 describes the available sort orders. If your language does not appear, then there is no language-specific sort order for your language—use a binary sort order.
CHAPTER 7 Customizing Localization for Adaptive Server Language or script Sort orders File name ID Scandinavian Dictionary order, case sensitive, accent sensitive Dictionary order, case insensitive, with preference scandict.srt scannocp.srt 47 48 Dictionary order, case sensitive, accent sensitive espdict.srt 55 Dictionary order, case insensitive, accent sensitive Dictionary order, case insensitive, accent insensitive espnocs.srt espnoac.
Changing the localization configuration Character sets Sybase name CP 1253 CP 1254 cp1253 cp1254 CP 1255 CP 1256 cp1255 cp1256 CP 1257 CP 1258 cp1257 cp1258 DEC Kanji EUC-CNS deckanji euccns EUC-GB EUC-JIS eucgb eucjis EUC-KSC GB 18030 eucksc gb18030 GREEK8 ISO 8859-1 greek8 iso_1 ISO 8859-2 ISO 8859-5 iso88592 iso88595 ISO 8859-6 ISO 8859-7 iso88596 iso88597 ISO 8859-8 ISO 8859-9 iso88598 iso88599 ISO 8859-15 Koi8 iso15 koi8 ROMAN8 ROMAN9 roman8 roman9 Shift-JIS TIS 620 sjis tis
CHAPTER 7 Syntax Customizing Localization for Adaptive Server charset [ -U username ] [ -P password ] [ -S server ] [ -I interfaces ] [ -v version ] sort_order [ charset ] Table 7-19: Keywords and options for charsets Keywords and options -U Description If you are not already logged in to your operating system as “sa”, you must specify “-Usa” or “/username = sa” in the command line. -P Specifies the “sa” password on the command line. If not specified, the user is prompted for the “sa” password.
Changing the localization configuration 104 Adaptive Server Enterprise
CH A PTE R 8 Logging Error Messages and Events This chapter describes how to use the error logging features of Adaptive Server. Topic Adaptive Server error logging Setting error log paths Page 105 106 Managing messages 107 Adaptive Server error logging Each time Adaptive Server starts, it writes information to a local error log file, called the Adaptive Server error log: $SYBASE/$SYBASE_ASE/install/server_name.log This file: • Stores information about the success or failure of each start-up attempt.
Setting error log paths Enabling and disabling error logging Logging to the Adaptive Server error log is always enabled. However, when you create or modify a specific user-defined message, you can set it to be omitted from the log. See “Logging user-defined messages” on page 107. Setting error log paths The installation program sets the error log location in the Sybase installation directory when you configure a new Adaptive Server. Backup Server and Monitor Server each have their own error logs.
CHAPTER 8 Logging Error Messages and Events Managing messages When event logging is enabled, you can manage its functions in the following ways: • Use sp_addmessage or sp_altermessage to control whether a specific user-defined message is logged in the Adaptive Server error log. For the complete syntax for sp_addmessage and sp_altermessage, see the Reference Manual. • Use configuration parameters to specify whether auditing events are logged.
Managing messages Logging auditing events By default, Adaptive Server does not log auditing events. However, you can use sp_configure parameters to specify whether Adaptive Server is to log auditing events, such as logins, to the Adaptive Server error log.
CH A PTE R 9 Managing Adaptive Server Databases The administration of Adaptive Server databases includes both routine tasks and performance and tuning considerations. • The System Administration Guide discusses most of the administrative tasks in detail. • The Performance and Tuning Guide provides in-depth explanations of performance issues.
Managing database devices • The minimum device size for a 16K page server is 4MB • The maximum number of database devices is 2,147,483,647. However, Adaptive Server must retain a description of each device in memory, so in practice this number is limited by your system’s memory. Your operating system also limits how many devices one program can open simultaneously.
CHAPTER 9 Managing Adaptive Server Databases In this example, "size = 2048" tells the command to allocate 2048 “virtual” pages to the device. A virtual page is 2048 bytes, so this command creates a 4MB device. The example command does not specify a device number, instead letting the server choose one. Unless you need to assign a specific number to a given device, Sybase recommends you use this method.
Managing database devices 112 Adaptive Server Enterprise
CH A PTE R 1 0 Adding Optional Functionality to Adaptive Server This chapter provides instructions for adding optional functionality to Adaptive Server: Topic Adding auditing Installing online help for Transact-SQL syntax Page 113 121 After you have installed the Sybase products on your system, see the product documentation for configuration and administration issues. Adding auditing Auditing is an important part of security in a database management system.
Adding auditing • The audit trail, which consists of several audit devices and tables that you determine at configuration time • The syslogs transaction log device, which stores transaction logs The sybsecurity device and database The sybsecurity device stores the sybsecurity database. The sybsecurity database is created as part of the auditing configuration process.
CHAPTER 10 Adding Optional Functionality to Adaptive Server Pre-installation tasks for auditing devices Determine the location of the raw devices for the sybsecurity, syslogs, and sysaudits table devices. You will need to provide this information later. Sybase recommends that you: • Configure your system with the minimum number of auditing devices you require—you must configure at least three devices. You can add more auditing devices later with sp_addaudittable.
Adding auditing 1. Release directory: /usr/u/sybase 2. Configure a Server product 3 Select Configure a Server Product. 4 Select Adaptive Server. 5 Select Configure an Existing Sybase Server. 6 Select the server to configure. 7 Provide the SA password for the server you selected. 8 From the Sybase Server Configuration screen, select Configure Auditing. As you proceed through the menus in auditinit, you can change any default values that appear.
CHAPTER 10 2 Adding Optional Functionality to Adaptive Server Select Sybsecurity Physical Device Name. To create a device for an audit table: 1 Enter the full path of the physical device (raw partition) that you located in “Pre-installation tasks for auditing devices” on page 115. Enter the physical name of the device to use for the audit database (default is " "): /dev/path_to_partition where path_to_partition is the path to the raw partition for the device.
Adding auditing List of devices for the audit tables: Logical name Physical name Segment name Table name Size 6.Audit_01' secret1/sybase_dr/install/aud1.dat’ sysaudits_01 5 5 To add multiple audit devices, repeat steps 1– 6. You can add as many as eight devices. Sybase recommends adding three or more audit table devices. After adding a device, auditinit returns to the Configure Auditing menu and displays all the devices you have created. CONFIGURE AUDITING 1. Configure auditing: yes 2.
CHAPTER 10 Adding Optional Functionality to Adaptive Server where path_to_partition is the path to the raw partition for the device. 3 Enter the full path name of a physical device. If you enter an operating system file name, the following warning appears: WARNING: '/secret1/sybase_dr/install/audlog' is a regular file, which is not recommended for a Server device. 4 Press Return to acknowledge this warning.
Adding auditing Logical name name Size Physical name 6. Audit_01' 7. Audit_02' 8. auditlog Segment name Table /secret1/sybase_ dr/install/aud1.dat’ sysaudits_01 /secret1/sybase_ dr/install/aud2.dat' sysaudits_02 /secret1/.../auditlog.dat logsegment syslogs 7 When you are ready to execute the audit configuration, press Ctrl+A. auditinit returns you to the Sybase Server Configuration screen. 8 Press Ctrl+A again.
CHAPTER 10 Adding Optional Functionality to Adaptive Server 3. size of the new device (Meg): 5 4. Device size for auditing:5 3 Select each remaining entry you want to change. 4 Press Ctrl+A to save the new entries. Installing online help for Transact-SQL syntax This section provides instructions for installing online help for Transact-SQL syntax. Online syntax help: sp_syntax The $SYBASE/$SYBASE_ASE/scripts directory contains scripts for installing the syntax help database, sybsyntax.
Installing online help for Transact-SQL syntax You can install any of these scripts, depending on the need for Sybase information on your server. The first script you execute creates the sybsyntax database and the needed tables and indexes. Any scripts that you execute after the first one add to the existing information in the database. If you execute a script that was executed previously, the previously installed rows of information are deleted from the table in the database and then reinstalled.
CHAPTER 10 3 Adding Optional Functionality to Adaptive Server Use a text editor to edit the script, if necessary, to change the default device from the master device to the device created in step 1. For information on the default device, see “Default device for the sybsyntax database” on page 122.
Installing online help for Transact-SQL syntax If you have set the DSQUERY environment variable to the servername, you can replace the server name with $DSQUERY. 5 To ensure that you have installed the sybsyntax database and that it is working correctly, use isql to log in to the server on which you installed the database, and execute sp_syntax.
Index Symbols ::= (BNF notation) in SQL statements , (comma) in SQL statements {} (curly braces) in SQL statements () (parentheses) in SQL statements [ ] (square brackets) in SQL statements xiv xiv xiv xiv xiv A accented letters 13, 91 Adaptive Server character set, changing 83 character sets 89 client communications with 49 conversions between, and clients 89 customizing features 47 database device requirements 9 default character set 83 default configuration 47, 48 default sort order 83 error log path
Index C C shell 29 case sensitivity in SQL xv changing character sets 83, 97 languages 97 sort order 97 character devices improving I/O performance on 38, 39 character sets 89 accented letters in 13 changing 83, 84, 97 client selection of 84 code conversions and 89 configuring 99 converting between 89 databases and 90 default 83 in a heterogeneous environment 89 sort orders and 90 U.S.
Index sybsystemdb 5 sysprocsdev 5, 6 databases 90 dbccdb 7 devices 109 master 5, 6 model 5 sample 6, 7 sizes of 13 specifications 13 sybsecurity 7 sybsystemprocs 6, 13 tempdb 5 dataserver utility 27 dbcc checkstorage, database for 7 dbcc error messages 45 dbccdb database 7 debug service type 56 Dec-Kanji character set 89 default character set for Adaptive Server 83 character set, changing 83 character sets installed by 83 language for Adaptive Server 83 language, changing 83 sort order 83 delay_interval com
Index device files 109 locales.dat 95 localization 82 localized error messages (.loc) 95 runserver 19 shared memory 27 sort order definition (.
Index query port backup configuration query service type 56 retry_attempt component 56 servername component 56 service_type component 56 spaces in 55 tab characters in 55 unique elements in entries 59 used by clients 51 international systems support for 81 Sybase support for 81 interpubs sample database 7 iostat command IBM RS/6000 44 Sun Solaris 44 iso-Latin1 character set 83 J Japanese sample database 7 jpubs sample database 7 K KEEPALIVE option, TCP/IP kill command 26, 28 Korean character sets 87 41
Index M machine component in interfaces files 57 master interfaces file 51, 58 service type 56 master database 5 master device 5, 9 maxfiles kernel parameters 34 maxfiles_lim kernel parameters 34 mbuf pools 44 messages hardware errors 42 messages, selecting language for 93 model database 5 Monitor Server default configuration for 48 monserver command 20 starting from UNIX command line 18 starting with operating system 20 monitoring I/O 43 network status 43, 44 operating system resources 43 virtual memory u
Index paths, error log 106 permissions 34 required in environment variables 29 restoring of 34 PID. See process identification platforms, supported vii platform-specific locale names 95 port component in interfaces files 57 port numbers and interfaces files 59 PPID. See parent process identification privileges 10 procedure specifications 15 procedures, Sybase extended stored process identification (PID) 27 .
Index sort orders 90 binary 91 changing 97 character sets and 90 databases and 90 definition files 90 dictionary 91 spaces in interfaces files 55 Spanish dictionary sort orders 92 SPX network protocol 11, 56 square brackets [ ] in SQL statements xiv srt files 90 srvbuild utility 12 starting servers from UNIX command line 18 with operating system 20 startserver utility 20 start-up script 21 stty settings 33 Sun Solaris iostat command 44 netstat command 44 network protocol 56 ps command 45 time command 45 ti
Index user-defined message utilities slloc 91 107 V vmstat command HP-UX 43 IBM RS/6000 44 Sun Solaris 44 W Windows Sockets default socket 47, 48 X XP Server default configuration 48 XP Server, starting 17 xp_cmdshell command 17 Configuration Guide 133
Index 134 Adaptive Server Enterprise
