Chapter 3 Sybase Software
Asset Management (SySAM)

Installation Guide Adaptive Server Enterprise for Linux/Intel

Chapter 2 Installation Requirements

Chapter 2

Installation Requirements

This chapter covers important information regarding system requirements for installing Adaptive Server databases and devices:

For easier installation, make a copy of this chapter, so you have the requirements information available as you perform the pre-installation, installation, or upgrade procedures.

System requirements

Table 2-1 shows the required release-level, RAM, and network-protocol requirements for Adaptive Server. See the release bulletin for the latest information on required system patches.

System requirements

This section contains the hardware and software requirements for the server and client software included with Adaptive Server 12.5.

Adaptive Server 12.5.0.1 has been released on two versions of the Linux kernel. The release levels of the operating system components for both releases are indicated in the tables below.

System requirements on kernel version 2.2.14
Hardware	Operating system	Network protocols
Server
Linux with Intel architecture, Pentium II, 230 MHz	Kernel - version 2.2.14-5.0 Run-time environment - glibc-2.1.3-15 RPM - rpm-3.0.4-0.48 X11R6.4 - XFree86-3.3.6-20 If you plan to use raw disk I/O, you need kernel 2.2.18 or higher.	TCP/IP sockets
PC-client
Windows NT	Windows NT 4.0, (Service Pack #6a, or later)	TCP IPX/SPX Named Pipes
Windows 98	Windows 98	TCP IPX/SPX Named Pipes

System requirements on kernel version 2.4.x
Hardware	Operating system	Network protocols
Server
Linux with Intel architecture, Pentium II, 230 MHz	Kernel - version 2.4.7-10 Run-time environment - glibc-2.2.4-13 Pthreads - libpthread-0.9 RT- librt-2.4.4 RPM - rpm-4.0.3-1.03 X11R6.4 - XFree86-4.1.0-3	TCP/IP sockets
PC-client
Windows NT	Windows NT 4.0, (Service Pack #6a, or later)	TCP IPX/SPX Named Pipes
Windows 98	Windows 98	TCP IPX/SPX Named Pipes

Table 2-3 shows the system requirements for installing jConnect for JDBC.

System requirements for jConnect on UNIX
Hardware	Any UNIX platform that supports Java VM 1.2.x
Operating system	Linux/Intel, Sun Solaris, HP UX, IBM AIX, DEC Digital Unix, SGI IRIX, and so on.
Java Developer's Kit	Sun's JDK 1.2.x or later
Database	Adaptive Server Enterprise, from SQL Server 11.x through Adaptive Server Enterprise 12.x; or Sybase SQL Anywhere 5.5.23 or later, running Open Server Gateway(TM) dbos50; or Sybase SQL Anywhere Studio 6.0* Some features in jConnect version 4.5 and 5.5 require Adaptive Server Enterprise 12.x or later: Support of wide tables Support for outer join syntax Support for Sybase Failover in high availability systems ("HA Failover") Implementation of a DynamicClassLoader (or Adaptive Server Anywhere 6.x and later) Support for distributed transaction management --Java Transaction API (JTA), and Java Transaction Service (JTS) For more information on these features, see the Sybase jConnect for JDBC Programmer's Reference.
Web browser	Any browser that supports JDK 1.1.x or later, such as Netscape 4.0.x, Internet Explorer 4.0.x, or HotJava 1.x
Other Sybase products (optional)	Adaptive Server IQ, OmniConnect, DirectConnect
Web server (optional)	For jConnect's TDS-tunnelling servlet, any Web server that supports the HTTPS protocol and javax.servlet interfaces
A free evaluation version of SQL Anywhere Studio 6.0 (includes Adaptive Server Anywhere 6.0) is available from Sybase . The Open Server Gateway and the required DLLs are no longer needed with Sybase SQL Anywhere Studio version 6.0 and later.

Client products are supported on Windows NT, and Windows 98. Table 2-4 lists the RAM required for client products.

RAM requirements for PC-client products
Product	Memory requirements
Adaptive Server plug-in for Sybase Central, Java Edition	16MB
Adaptive Server plug-in for Sybase Central, C++	16MB
Open Client/C Developer's kit	16MB, 32MB recommended
Monitor Client Library	16MB, 32MB recommended
Embedded SQL/COBOL and Embedded SQL/C
jConnect 4.5 and 5.5	16MB each
SQL Remote 7.0.2	37MB
PowerDynamo 3.5.2
InfoMaker 7.0.3	32MB
Physical Architect 8.0	16MB

Table 2-5 shows the installation requirements for the Adaptive Server plug-in for Sybase Central.

Installation requirements
Operating system	Product	Disk space
Windows NT 4.0 Service Pack 6 or later, or Windows 98	Sybase Central ASE plug-in C++ *Warning!* The C++ version of the plug-in is included only to provide the DDLGEN functionality required by the database migration utility. Do not use the C++ plug-in for general administrative purposes.	12MB
Windows NT 4.0 Service Pack 6 or later, or Windows 98	Sybase Central ASE plug-in Java edition	16MB

Product disk space requirements

Table 2-6 lists the disk space requirements for each product.

Product disk space requirements
Product and version level	Package size	Disk space required
Adaptive Server 12.5, includes Monitor Server 12.5 Historical Server 12.5 Monitor Client Library 12.5	37MB	115MB
Sybase Common package	95MB	100MB
Open Client/C 12.5	38MB	120MB
Language Modules (Server 12.5) Sybase-french Sybase-german		2-7MB per language
Language Modules (Open Client 12.5)		3-6MB per language
Enhanced full-text search	33MB	65MB
Sybase-esql	1.2MB	4MB
Sybase Openserver	13MB	45MB
SQL Remote	1.7MB

Language module sizes

Table 2-7 lists the sizes for the Adaptive Server and Open Client Language modules.

Language module sizes
Language	Size language module
Brazilian Portuguese	6.5MB
Chinese (simplified)	2MB
Chinese (traditional)	2MB
French	6.5MB
German	6.5MB
Japanese	4.5MB
Korean	2MB
Spanish	6.5MB

Adaptive Server specifications

Adaptive Server specifications on Linux (approximate)
Hardware
Processor	32-bit Intel Pentium II
Minimum RAM required for Adaptive Server	50MB
Minimum RAM per additional user	116KB
Default user stack size	64KB

Database specifications
Memory per user connection	155K	With default stack size, packet size, and user log cache size
Databases per Adaptive Server	32,767	Practical limit is approximately 100
Maximum database size	243(8TB)	Minus overhead for system databases
Minimum allowable sybsystemprocs database	100MB	Required for an upgrade
Maximum size of a database device (disk partition)	224(32GB)	2GB maximum device size if using operating system files 32GB device size for raw partitions.
Maximum number of database devices per server	256
Maximum number of devices or device pieces per database	Unlimited
Maximum number of segments per database	31
Maximum number of login IDs per server	2147516416
Maximum number of users per database	2146484223
Maximum number of groups per database	1032193
pubs2 database	2MB 3MB	Minimum required for a new installation Minimum required for an upgrade
pubs3 database	2MB 3MB	Minimum required for a new installation Minimum required for an upgrade
interpubs database	2MB 3MB	Minimum required for a new installation Minimum required for an upgrade
jpubs database	2MB 3MB	Minimum required for a new installation Minimum required for an upgrade

Table specifications
User objects per database	231 - 100
Indexes per table	250 (one clustered index)
Rows per table	Limited by available storage	Maximum 232
Columns per composite index	31
Creation of clustered index	1.2*(x + y) x = total data space in table, y = sum of space of all nonclustered indexes on table, and 20% overhead for logging	For sorted data, approximately 20% of the table size needed
Characters per database object name	30

Query specifications
Maximum number of tables in a "union" query	256
Maximum number of databases participating in one transaction	16	Includes database where transaction began, all databases changed during transaction, and tempdb, if it is used for results or worktables
Practical number of databases participating in one query	16	Includes each occurrence of each database queried and tempdb, if it is used for results or worktables
Maximum number of tables participating in a query	64	Maximum of 50 user tables, including result tables, tables referenced by views (the view itself is not counted) correlations and self-joins; maximum of 14 worktables.
Maximum number of tables with referential integrity constraints for a query	192

Procedure specifications
Number of buffers and procedure buffers	Configurable	Limited by amount of RAM and maximum size of shared memory segment
Minimum memory required per stored procedure	2K
Maximum number of parameters per stored procedure	2048

Adaptive Server 12.5 extended-limit capabilities vary by type of table and the database logical page size. Table 2-9 lists the column and row limits for allpages-locked (APL) tables.

Allpages-locked (APL) tables
Maximum APL table limits	Number of columns	Column size 2K page	Column size 4K page	Column size 8K page	Column size 16K page
Fixed-length column	1024	1960 bytes	4008 bytes	8104 bytes	16296 bytes
Variable-length column	254	1948 bytes	3988 bytes	8068 bytes	16228 bytes

Table 2-10 lists the column and row limits for data-only-locked (DOL) tables.

Data-only-locked (DOL) tables
Maximum DOL table limits	Number of columns	Column size 2K page	Column size 4K page	Column size 8K page	Column size 16K page
Fixed-length column	1024	1958 bytes	4006 bytes	8102 bytes	16294 bytes
Variable-length column	1024	1954 bytes	4002 bytes	8098 bytes	16290 bytes

Database space requirements depend upon the logical page size of the server. Table 2-11 lists the minimum size for each database.

Database requirements for varying page sizes
Databases	2K page	4K page	8K page	16K page
Default database size	2MB	4MB	8MB	16MB
master database	6MB	12MB	24MB	48MB
model database	3MB	4MB	8MB	16MB
tempdb database	3MB	4MB	8MB	16MB

Larger logical page sizes can contain more data. Table 2-12 lists the maximum data for each logical page size.

Data limits for tables according to page size
Tables	2K page	4K page	8K page	16K page
Maximum number of data bytes per text or image file	1800	3600	7650	16200
Bytes per index key	600	1250	2600	5300
User-visible row length DOL table	1958	4006	8102	16294
User-visible row length APL table	1960	4008	8104	16296

Adaptive Server devices and system databases

Devices are operating system files that are used to store databases and database objects. Adaptive Server uses the O_SYNC option with operating system files to ensure data is reliably written to the disk.

Adaptive Server requires the following devices:

master device - to store system databases.
sysprocsdev device - to store system procedures.

The master and sysprocsdev devices are created when you create a new Adaptive Server.

master device

The master device contains the following databases:

master - controls the operation of Adaptive Server as a whole and stores information about all users, user databases, devices, objects, and system table entries. The master database is contained entirely on the master device and cannot be expanded onto any other device.
model - provides a template for new user databases. The model database contains required system tables, which are copied into a new user database with the create database command.
tempdb - the work area for Adaptive Server. Each time Adaptive Server is started the tempdb database is cleared and rebuilt from the model database.
The sample databases are stored on the master device at installation, but should be moved to a user-defined device after installation. For more information, see "Sample databases".
For recovery purposes, Sybase recommends that you do not create other system or user databases or user objects on the master device.

sybsystemdb device and database

For new installations the master device also contains the sybsystemdb database. The sybsystemdb device stores the sybsystemdb database, which stores information about transactions in progress, and which is also used during recovery.

See Chapter 8, "Upgrading Sybase Servers " for instructions on how to create the sybsystemdb device and database for two-phase commit and Data Transfer Management.

For recovery purposes, it is recommended that you do not create other system or user databases or user objects on the master device.

The sample databases are stored on the master device at installation, but should be moved to a user-defined device after installation. For information on the sample databases, see "Optional devices and databases".

sysprocsdev device

The sysprocsdev device stores the sybsystemprocs database, which contains most of the Sybase-supplied system procedures. System procedures are a collection of SQL statements and flow-of-control statements that perform system tasks; for example, sp_configure.

The system procedures that are needed during recovery situations are stored in the master database.

sysprocsdev is the default system name for this device. However, it is frequently referred to as the sybsystemprocs device, since it stores the sybsystemprocs database.

Optional devices and databases

The following devices and databases are needed only if you configure Adaptive Server for optional functionality, like auditing or two-phase commit transactions.

sybsecurity device and database

The sybsecurity device stores the sybsecurity database and the auditing system procedures with which you can configure auditing for your system.

The auditing system records system security information in an Adaptive Server audit trail. You can use this audit trail to monitor the use of Adaptive Server or system resources.

Install auditing using the auditinit utility. The sybsecurity device is created as part of the auditing installation process.

See the Adaptive Server Configuration Guide for instructions on how to configure Adaptive Server for auditing.

The auditing system is discussed in more detail in the System Administration Guide.

Sample databases

The pubs2 and pubs3 databases are sample databases provided as a learning tool for Adaptive Server. The pubs2 sample database 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.

The interpubs database contain French and German data. jpubs contains Japanese data.

For information about installing the sample databases, see "Installing sample databases ".

For information on the contents of these sample databases, see the Transact-SQL User's Guide.

sybsyntax database

The syntax database, sybsyntax, contains syntax help for Transact-SQL commands, Sybase system procedures, Adaptive Server utilities, and Open Client routines. You can retrieve this information using the system procedure sp_syntax.

For example, to see the syntax of the Transact-SQL select command, enter:

sp_syntax "select"

Adaptive Server includes a script for creating the sybsyntax database.

For instructions on how to install sybsyntax, see "Installing online help for Transact-SQL syntax ".

For more information about sp_syntax, see the Reference Manual.

bccdb database

The database consistency checker (dbcc) provides commands for checking the logical and physical consistency of a database. The dbccdb database stores the results of dbcc when dbcc checkstorage or dbcc check verifying are used.

dbcc checkstorage records configuration information for the target database, operation activity, and the results of the operation in the dbccdb database. Stored in the database are dbcc stored procedures for creating and maintaining dbccdb and for generating reports on the results of dbcc checkstorage operations.

Information on installing dbccdb is located in the chapter "Checking Database Consistency," in the System Administration Guide.

Determining the location, type, and size of a database device

Adaptive Server requires several database devices. Table 2-13 below shows baseline values for each of the devices. See the release bulletin for any last-minute changes to these values.

Adaptive Server database devices
Device	Purpose	Minimum size	Minimum recommended size
master	Stores system databases	14MB for 2K pages 27MB for 4K pages 50MB for 8K pages 105MB for 16K pages	30MB 60MB 120MB 240MB
sysprocsdev (also called the sybsystemprocs device)	Stores the sybsystemprocs database	100MB	100MB (plus any space for holding stored procedures that you have created)
sybsystemdb	Transaction processing	4MB	5 - 20MB
sybsecurity (optional)	Required for auditing	0-5MB	7MB; more for specialized auditing

By default, Adaptive Server 12.5 opens database devices with the O_SYNC flag to ensure recoverability in the event of power failure, operating system crash or Adaptive Server crash. This significantly affects performance. You can turn off the O_SYNC flag by starting the server with -T1623 trace flag.

Sybase Adaptive Server supports the database devices on NFS- and CIFS-mounted devices with Network Appliance Filers for storing data. Network appliance filers provide the same performance and data integrity as raw devices. There are no changes needed to the operating system or to Sybase Adaptive Server to use network appliance filers.

NFS mounted devices have been tested on Solaris, HP/UX, IBM AIX, Windows NT, and Linux.

You may need to repartition the disk you choose. Contact your operating system administrator for assistance.

Sybase recommends that to configure raw devices, you use Adaptive Server version 12.5.0.1 released on kernel 2.4.7 and deploy it on a system with at least the same operating system release level.

For a description of how to configure Adaptive Server for raw devices, see Appendix B, "Creating Raw Partitions. "


	Expand Search