Installation Guide Adaptive Server® Enterprise 15.
DOCUMENT ID: DC30119-01-1572-01 LAST REVISED: July 2012 Copyright © 2012 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.
Contents CHAPTER 1: Conventions ..............................................1 CHAPTER 2: Installation Task Overview .......................3 Installation Workflows ...........................................................3 CHAPTER 3: Adaptive Server Components .................5 Adaptive Server Editions ......................................................5 Determining the Edition You Have ..................................6 Adaptive Server Options .....................................................
Contents Determining Host IDs ...................................................17 Determining Host IDs for Machines with Multiple Network Adapters ............................................18 Using Alternate Host IDs on Windows .................18 Knowing the Product License Type ...............................18 Optional Feature Licenses ...................................19 Generating Licenses at SPDC ......................................19 Logging in to SPDC and Beginning License Generation .......
Contents Uninstalling Adaptive Server ..............................................48 Removing an Existing Adaptive Server ........................ 49 CHAPTER 7: Installing Components from the PCClient ...........................................................................51 Creating a Response File for the Client .............................52 Installing the Client in Unattended, Silent Mode ..............52 Uninstalling PC-Client .........................................................
Contents CHAPTER 10: Adaptive Server Upgrades ...................69 Upgrading Adaptive Server ................................................69 Considerations for Component Integration Services ......72 Preparing to Upgrade ..........................................................72 Changes in Adaptive Server Directories ...........................73 Performing Preupgrade Tasks ............................................74 Upgrade System Tables and Stored Procedures ..........76 Reserved Words .........
Contents Updating Threshold Procedures for Audit Segments ........................................................90 Reenabling Replication Server After the Dataserver Upgrade ....................................................................90 Restoring Replication on Replicate Databases .........................................................................91 Restoring Replication on Primary Databases ......91 Migrate ..................................................................................
Contents Downgrading an Adaptive Server That Uses Encryption .........................................................................................113 Downgrade Considerations for Adaptive Server with Replicated Databases ...................................................114 Post-Downgrade Tasks for Adaptive Server ...................114 CHAPTER 12: Troubleshooting SySAM Errors .........117 Where to Find License Error Information ........................117 Problems and Solutions .....................
Contents CHAPTER 14: Obtaining Help and Additional Information ...............................................................139 Technical Support ..............................................................139 Downloading Sybase EBFs and Maintenance Reports ..139 Sybase Product and Component Certifications .............140 Creating a MySybase Profile ............................................140 Accessibility Features .......................................................140 Index .................
Contents x Adaptive Server Enterprise
CHAPTER 1 Conventions ® These style and syntax conventions are used in Sybase documentation.
CHAPTER 1: Conventions 2 Adaptive Server Enterprise
CHAPTER 2 Installation Task Overview To successfully install and configure Adaptive Server® Enterprise, use the configuration guide along with this installation guide. The Adaptive Server installation guide explains how to unload the Adaptive Server software from the distribution media to your hard disk, and perform the minimal set of additional tasks so that you can start Adaptive Server on your machine.
CHAPTER 2: Installation Task Overview Upgrading to a New Version 1. Determine your upgrade eligibility, plan your installation, and review system requirements. 2. Run the preupgrade utility to prepare Adaptive Server for upgrading. 3. Upgrade Adaptive Server. 4. Perform postinstallation tasks. Uninstalling Adaptive Server Uninstall Adaptive Server. See Uninstalling Adaptive Server on page 48.
CHAPTER 3 Adaptive Server Components Adaptive Server® Enterprise is based on a client/server model, communicating with its clients over the network via the Tabular Data Stream™ (TDS) protocol. Each client process may execute on one machine and communicate with a database server on the same or a different machine. Adaptive Server runs as an application on top of an operating system.
CHAPTER 3: Adaptive Server Components Determining the Edition You Have If you already use Adaptive Server, use the sp_lmconfig system procedure to identify the version. Enter: sp_lmconfig 'edition' Adaptive Server returns a value of EE, SE, or DE based on the edition that is currently running. See the Reference Manual for more information about sp_lmconfig. Adaptive Server Options Sybase offers various optional features for Adaptive Server, such as data compression, partitions, and encrypted columns.
CHAPTER 3: Adaptive Server Components console, agents, common services, and tools for managing and controlling Sybase products. It includes historical monitoring, threshold-based alerts and notifications, alert-based script execution, and intelligent tools for identifying performance and usage trends.
CHAPTER 3: Adaptive Server Components • • • • QPTune jConnect™ for JDBC™ 7.0 SySAM License Utilities SDC Administration Utility In addition to the SDK, the PC-Client CD includes PowerDesigner Physical Architect, a tool for data modeling, including database design, generation, maintenance, reverse engineering, and documentation for database architects.
CHAPTER 4 System Requirements Before installing Adaptive Server, ensure that your system is updated with the latest patches and system requirements. Do not use a patch that is earlier than the version suggested for your operating system. Use the patch recommended by the operating system vendor, even if it supersedes the patch listed. To list all currently installed patches and display the operating system version level, enter: rpm -q -a Linux Requirements Adaptive Server 15.
CHAPTER 4: System Requirements Required files Description Required libraries for Linux • • • • • • • • • • Required X/Motif-related RPM pack- • age manager files • • • • • • • • • openmotif-2.3.1-2.el5 libXp-1.0.0-8.1.el5 libXt-1.0.2-3.1.fc6 libXtst-1.0.1-3.1 libXi-1.6.1-1 libXmu-1.0.2-5 libXext-1.0.1-2.1 libSM-1.0.1-3.1 libICE-1.0.1-2.1 libX11-1.0.3-9.
CHAPTER 4: System Requirements Product Linux X64 Requirements Linux X64 PSeries Requirements Default databases created during installation 306MB 164MB Total 1071MB 1256MB Before you can install a 64-bit Adaptive Server version 15.7 ESD #2 to a Red Hat Enterprise Linux 6.x x86_64, install the 32-bit GNU C Libraries package (glibc-2.xxx.xx.el6.i686.rpm). Ensure that you have the required operating system patches for the Java Runtime Environment (JRE) version 6.
CHAPTER 4: System Requirements 12 Adaptive Server Enterprise
CHAPTER 5 Planning Your Adaptive Server Installation Before you install or upgrade, prepare your environment. • • • Identify the components and options to install or upgrade. Obtain a license. Note: If you are using a served license, you must install the SySAM license server version 2.1 or later. Make sure your system meets all requirements for your installation scenario and planned use. Adaptive Server Release Bulletin Obtain updated information from the release bulletin.
CHAPTER 5: Planning Your Adaptive Server Installation • If you ordered your product under an SAP® contract and were directed to download from SAP Service Marketplace (SMP), you can use SMP at http://service.sap.com/licensekeys to generate license keys for Sybase products that use SySAM 2-based licenses.
CHAPTER 5: Planning Your Adaptive Server Installation Sybase recommends that you use a license server if you run products on more than several machines, as this simplifies and centralizes license administration providing more control over software assets. After you download the unserved licenses, you can install your Sybase products. Comparing License Deployment Models Learn about license deployment models.
CHAPTER 5: Planning Your Adaptive Server Installation Unserved Licenses Served Licenses Unserved Standalone Seat (SS) licenses do not allow Products can be used via Remote Desktop Connecproduct use via Remote Desktop Connection or other tion or other Terminal Services clients, irrespective terminal services clients. of the type of license in use.
CHAPTER 5: Planning Your Adaptive Server Installation License Servers The license server is a lightweight application that serves licenses to products running on any operating system. A license server can run on a low-end machine or a machine with spare cycles. For example, a license server running on a Solaris UltraSparc-60 serving 100 different licenses to 200 product instances, used 50MB of memory, 5 minutes of CPU time per week, and 100MB of disk space per year.
CHAPTER 5: Planning Your Adaptive Server Installation Determining Host IDs for Machines with Multiple Network Adapters On some platforms, the host ID is derived from the network adapter address.
CHAPTER 5: Planning Your Adaptive Server Installation Your account can have the same product licensed under multiple license types. Make sure you select the correct license type when you generate your SySAM license file. When you generate licenses, each license type is presented on the License Information screen in bold font. For example: License Type: CPU License (CP) Note: The End User License Agreement for your region, available from the Sybase Software Licenses Web page at http://www.sybase.
CHAPTER 5: Planning Your Adaptive Server Installation Required Information or Action License Model Served Product machine host ID Description Unserved X Determine the host ID of the machine, or machine partition where the product will run. License server – download and install X Download and install the SySAM license server before you generate the product’s licenses, and before you install the product.
CHAPTER 5: Planning Your Adaptive Server Installation • At the Web Key Registration page, enter your account information, then click one of these options: • Submit My Registration Information – to register your product using your direct account information. • Anonymous Activation – to activate your product anonymously. 3. Select the product family that includes the product for which you want to generate a license; for example, Adaptive Server Enterprise. 4.
CHAPTER 5: Planning Your Adaptive Server Installation Generating Unserved Licenses Generate and download an unserved license for your product. 1. Enter the number of machines (up to 10) for which to generate unserved licenses, and click Next. 2. Enter: • • Node Host ID – enter the host ID of the machine where the product will be run. If you do not know the host ID, select What Is My Host ID? or see Determining Host IDs in the Sybase Software Asset Management (SySAM) 2 Users Guide.
CHAPTER 5: Planning Your Adaptive Server Installation If you are unsure of the license quantity, select How Many Licenses Should I Generate?. 2. Select an existing license server host, or enter the host ID, and an optional host name and port number, of a new license server host. When completing this step, use these recommendations: • • • • If you do not know the license server host ID, select What Is My host ID? or see Determining Host IDs in the Sybase Software Asset Management (SySAM) 2 Users Guide.
CHAPTER 5: Planning Your Adaptive Server Installation Warning! If you do not save the license files with a .lic extension, SySAM does not recognize the licenses. 7. After you save the license files to the license server, enter on the machine where your license server is running: sysam reread Your new licenses are registered with the license server. Regenerating, Renewing, and Rehosting Licenses Learn when licenses must be regenerated, renewed, and rehosted.
CHAPTER 5: Planning Your Adaptive Server Installation Modifying Individual Licenses Learn about modifying individual licenses. 1. Follow instructions in Logging in to SPDC and Beginning License Generation in the Sybase Software Asset Management (SySAM) 2 Users Guide through the step for selecting options that identify the license you want to change. 2. On the License Information page, select the desired license order. 3. Select one of: • Check in – returns the license to the available license pool.
CHAPTER 5: Planning Your Adaptive Server Installation Required Information or Action License Model Served Description Unserved License server host ID X Determine the host ID of the machine where the license server will run. License server host name X Determine the host name of the machine where the license server will run. License server TCP/IP port numbers X Determine the two port numbers on which the license server will listen for license requests.
CHAPTER 5: Planning Your Adaptive Server Installation Product Description Software Developer Kit (SDK) Installed into the OCS-15_0 directory. • Open Client (Client Library, dblib) • • • • ESQL/C ESQL/COBOL XA ODBC (Windows, Solaris SPARC, Solaris x64, Linux Power, HP-UX Itanium, IBM AIX) – a driver used to connect to Adaptive Server from ODBCbased applications. OLEDB (Windows only) – a provider used to connect to Adaptive Server from OLEDB-based applications. ADO.
CHAPTER 5: Planning Your Adaptive Server Installation Product Description Character sets Installed into the charsets directory. Provides character sets available for use with Adaptive Server. Collation sequences Installed into the collate directory. Provides the collation sequences available for use with Adaptive Server. Sybase Software Asset Management (SySAM) Installed into the SYSAM-2_0 directory. Provides asset management of Adaptive Servers and optional features.
CHAPTER 5: Planning Your Adaptive Server Installation PC-Client Product Descriptions and Layout An Adaptive Server installation includes additional products that are installed into specific directories.
CHAPTER 5: Planning Your Adaptive Server Installation Product Description Uninstaller Installed into the sybuninstall/PCClient directory. Interactive SQL Interactive SQL is a GUI tool that allows you to execute SQL statements, build scripts, and display data from Adaptive Server. It is installed into the DBISQL directory. jutils-3_0 utilities A collection of Adaptive Server utility programs including ribo, a tool to trace TDS traffic between client program and Adaptive Server.
CHAPTER 5: Planning Your Adaptive Server Installation Preparing to Install Adaptive Server Prepare your system before starting the installation. 1. Ensure that the account used to start the server has read and write permissions over the directory in which you are installing the server. You may need to create nonadministrative logins to install the server into personal directories. 2. Unset the LD_ASSUME_KERNEL variable. 3.
CHAPTER 5: Planning Your Adaptive Server Installation • • • E-mail return address Recipients of the notifications Severity level of an event that triggers mail. Your choices are: • None • Informational • Warning • Error 9. Verify that your network software is configured. Sybase software uses network software even if Adaptive Server and Sybase client applications are installed on a machine that is not connected to a network.
CHAPTER 5: Planning Your Adaptive Server Installation # /sbin/sysctl -w kernel.shmmax=nnn Note: The default operating system shared memory for some older Linux releases is 32MB. The minimum required by Adaptive Server is 64MB for a default server with 2K pages. A higher value is required if you plan to increase the Adaptive Server max. 3. To guarantee that the minimum operating shared value is applied every time the system is started, edit the /etc/sysctl.conf file. 4.
CHAPTER 5: Planning Your Adaptive Server Installation 1> sp_configure 'enable java', 1 2> go Multipathing Multipathing is the ability of a server to communicate with the same physical or logical block storage device across multiple physical paths between the host bus adapters (HBA) in the server and the storage controllers for the device, typically in Fibre Channel (FC) or iSCSI SAN environments. You can also achieve multiple connections with direct attached storage when multiple channels are available.
CHAPTER 5: Planning Your Adaptive Server Installation • • • • • • • • • • • • • • • • • NCR UNIX MP-RAS EMPATH for EMC Disk Arrays NCR UNIX MP-RAS RDAC for Engenio Disk Arrays ONStor SDM multipath IBM System Storage Multipath Subsystem Device Driver (SDD) Accusys PathGuard Infortrend EonPath OpenVMS FreeBSD - GEOM_MULTIPATH and GEOM_FOX modules Novell NetWare Sun StorEdge Traffic Manager Software ATTO Technology multipath driver Fibreutils package for QLogic HBAs RDAC package for LSI disk controllers lpfcd
CHAPTER 5: Planning Your Adaptive Server Installation For example: • /usr2/sybase/ASE1503/dev/wdb_data – is a symbolic link pointing to / dev/raw/raw73 • /dev/raw/raw73 – is a raw character device mapped to /dev/mapper/ mp_wdb_data • /dev/mapper/mp_wdb_data – is a multipath device which contains two paths /dev/sdbf & /dev/sds.
CHAPTER 6 Installing Adaptive Server Install Adaptive Server using your chosen method. Prerequisites Complete installation planning tasks. Task 1. Choose an installation method: • GUI wizard (recommended) • Console mode • Response file 2. Follow the instructions for your chosen method. 3. Perform postinstallation steps. Mounting the CD If you are installing using the CD, mount the CD. The location of the mount command is site-specific and may differ from the instructions shown here.
CHAPTER 6: Installing Adaptive Server the same directory with existing products should not impact the existing products. However, installing other products on top of Adaptive Server version 15.7 ESD #2 may result in one or more products not working correctly. Sybase strongly recommends that you install Adaptive Server version 15.7 ESD #2 into its own directory if possible. If you must install other products into the same directory, install Adaptive Server version 15.7 ESD #2 last.
CHAPTER 6: Installing Adaptive Server 8. Select the type of installation: Option Description Typical (Default) Installs the default components. This is recommended for most users. Full Installs every Adaptive Server component, including all the supported language modules. Customize Lets you select the components to install. Some components are automatically installed if they are required to run your selected components. 9.
CHAPTER 6: Installing Adaptive Server • • Recipient e-mail addresses Message severity that triggers e-mail messages In the summary window, click Next. 12. In the preinstallation summary, verify the installation type and that you have enough disk space for the installation. Click Next. The installation status window displays the result of the installation process. 13.
CHAPTER 6: Installing Adaptive Server Installing Adaptive Server in Console Mode Choose command line installation if you prefer a nonwindowing interface, or for developing custom installation scripts. Prerequisites Launch the installer in console mode. If the installer launches automatically, click Cancel to cancel the GUI installation, then launch the setup program from a terminal or console.
CHAPTER 6: Installing Adaptive Server Task 1. Set the Configure new Adaptive Server option: Option Description Adaptive Server name Default is the machine name. Port number Default is 5000. Error log Name and location of the error log file. Defaults to servername.log. Application type The options are numbered only in console mode: • 1. (Default) MIXED – both OLTP and DSS. • 2. OLTP – online transaction processing generally consists of smaller, less complex transactions. • 3.
CHAPTER 6: Installing Adaptive Server Option Description Create sample databases Create or install sample databases. Make sure you calculate the additional space for your master device. After customizing your Adaptive Server configuration, click Next to record the input fields.
CHAPTER 6: Installing Adaptive Server Configuration Value Temporary database device size Default is 100MB for all page sizes. Temporary database size Default is 100MB for all page sizes. Enable PCI in Adaptive Serv- If you select this option, provide this additional information: er • PCI device – default is sybpcidbdev_data.dat in $SYBASE/data. • • PCI device size – default is 48.
CHAPTER 6: Installing Adaptive Server 5. Set the Configure self management option: • Self management user name – default is "sa". • Self management password – prompted only if you change the default user name. 6.
CHAPTER 6: Installing Adaptive Server Adaptive Server and related products have been successfully installed, and minimally configured for use. See Installing Sample Databases on page 60, to begin experimenting with your servers, or see the System Administration Guide for more advanced topics. If you encounter any errors, see the Troubleshooting Guide. Installing Adaptive Server Using a Response File Unattended or silent installations are typically used to update multiple systems across the enterprise.
CHAPTER 6: Installing Adaptive Server Each password must be at least six characters long. The sccadmin and uafadmin logins need not be the same as the sa password. Installing in Silent Mode To perform a silent, or unattended installation, run the installer and provide a response file that contains your preferred installation configuration. Prerequisites Use setup.bin -r responseFileName to generate a installation response file during a console or GUI installation. Task 1.
CHAPTER 6: Installing Adaptive Server Option Purpose -i console Uses the console interface mode, where messages appear on the Java console and the wizard runs in console mode. -i silent Installs or uninstalls the product in silent mode, where the installation or uninstallation is performed without user interaction. -D Passes custom variables and properties.
CHAPTER 6: Installing Adaptive Server Note: You may need to confirm the deletion of some files that have been modified since installation. 4. When you see the final window, click Done to exit the uninstallation program. Removing an Existing Adaptive Server Remove an existing Adaptive Server. 1. From $SYBASE, enter: rm servername.* 2. Change to $SYBASE/$SYBASE_ASE/install and run: rm RUN_servername.* rm servername.* 3. Edit $SYBASE/interfaces, to remove all references to the Adaptive Server. 4.
CHAPTER 6: Installing Adaptive Server 50 Adaptive Server Enterprise
CHAPTER 7 Installing Components from the PC-Client The PC-Client CD contains several components that are each packaged with their own installer. When you insert the PC-Client CD, a menu program launches automatically. The menu program lists the components that can be installed from the CD and allows you to install them one at a time. Before installing any products, review the readme.
CHAPTER 7: Installing Components from the PC-Client Creating a Response File for the Client By saving installation configuration information into a response file during the initial GUI installation, you can perform subsequent installations of Adaptive Server using a silent—or unattended—method. Note: Adaptive Server version 15.7 ESD #2 uses a rearchitected installation program that is incompatible with response files generated for versions 15.0.3 and earlier.
CHAPTER 7: Installing Components from the PC-Client The only difference when you install the client in silent mode is the absence of the GUI screens. All actions and responses are the same as using InstallAnywhere. Warning! Sybase recommends that, when you run a silent installation, you use the setupConsole.exe executable, which runs in the foreground. The normal setup.
CHAPTER 7: Installing Components from the PC-Client 54 Adaptive Server Enterprise
CHAPTER 8 Starting and Stopping Sybase Control Center Agent Sybase Control Center (SCC) for Adaptive Server is a Web-based tool for monitoring the status and availability of Adaptive Servers. Set the $SYBASE environment variables and start an SCC agent on your Adaptive Server.
CHAPTER 8: Starting and Stopping Sybase Control Center Agent 56 Adaptive Server Enterprise
CHAPTER 9 Postinstallation Tasks After you install the server, set it up. The Adaptive Server installation includes directories containing sample client library applications. These sample programs are included for training purposes only and are not intended to be installed in a production environment.
CHAPTER 9: Postinstallation Tasks Verifying Your Connection to the Servers Verify your connection to the servers. Use isql to perform a quick test: • At the command prompt, enter the following, where server_name is the Adaptive Server name: isql -Usa -P -Sserver_name • You see the isql prompt if the login is successful. At the isql prompt, enter: 1> select @@version 2> go The output should show Adaptive Server at version 15.7 ESD #2.
CHAPTER 9: Postinstallation Tasks Configuring libtcl.cfg for LDAP Use the libtcl.cfg file to specify an LDAP server name, port number, DIT base, user name, and password to connect to an LDAP server. When you specify an LDAP server in the libtcl.cfg file, the server information becomes accessible only from the LDAP server; the interfaces file is ignored. Open Client and Open Server applications that use the -I option at start-up override the libtcl.cfg file and use the interfaces file.
CHAPTER 9: Postinstallation Tasks 3. Click Add New Server Entry, and enter: • Server name • Security mechanism – (Optional) there is a list of security mechanism OIDs in %SYBASE%\ini\objectid.dat. 4. Click Add New Network Transport, and: • Select the transport type. • Enter the host name. • Enter the port number. 5. Click OK twice to exit the dsedit utility.
CHAPTER 9: Postinstallation Tasks Database Description installpubs2 Installs the pubs2 sample database. This database contains data that represents a publishing operation. Use this database to test your server connections and to learn Transact-SQL. Most of the examples in the Adaptive Server documentation query the pubs2 database. Note: The master device size should be at least 30MB to install the full pubs2 database, including the image data. installpubs3 Installs the pubs3 sample database.
CHAPTER 9: Postinstallation Tasks Running the Database Scripts After you determine your default device, run the scripts to install the sample databases. Prerequisites Back up the original installpubs2 and installpubs3 scripts, in case you have problems with the edited scripts. Task 1. Start Adaptive Server. 2. Go to the Adaptive Server scripts directory at $SYBASE/$SYBASE_ASE/scripts. 3.
CHAPTER 9: Postinstallation Tasks The interpubs database contains 8-bit characters and is available for use at Adaptive Server installations using the ISO 8859-1 (iso_1), ISO 8859-15 (iso_15), Roman 8, or Roman9 (for HP-UX) character set. 3. Determine the type (raw partition, logical volume, operating system file, and so on) and location of the device where you will be storing the interpubs database. You will need to provide this information later. 4.
CHAPTER 9: Postinstallation Tasks Maintaining Sample Databases The sample databases contain a guest user option that allows authorized users to access the database. Guest users have a wide range of privileges, including permissions to select, insert, update, and delete user tables. Sybase recommends that you remove the guest user option from user databases in production systems. For more information about the guest user and a list of guest permissions, see the System Administration Guide. 1.
CHAPTER 9: Postinstallation Tasks Choosing a Raw Partition Select a raw partition on which to create and mount database devices. 1. 2. 3. 4. Determine which raw partitions are available. Determine the sizes of the raw partitions. From the list of available raw partitions, select a raw partition for each device. Verify with the operating system administrator that the partition you have chosen is available. 5. Make sure the "sybase" user has read and write privileges to the raw partition.
CHAPTER 9: Postinstallation Tasks 1. Use the n command to create a new partition, and enter l at this prompt for "logical": Command (m for help): n Command action l logical (5 or over) p primary partition (1-4) 2. Accept the default by pressing Enter when you see: First cylinder (8013-8683, default 8013): 3. Accept the default by pressing Enter again, when you see: Last cylinder or +size or +sizeM or +sizeK (8013-8683, default 8683): 8269 4.
CHAPTER 9: Postinstallation Tasks /dev/raw/raw2: /dev/raw/raw3 --> /dev/raw/raw3: /dev/raw/raw4 --> /dev/raw/raw4: done bound to major 3, minor 6 /dev/sdd7 bound to major 3, minor 7 /dev/sdd8 bound to major 3, minor 8 To guarantee that the raw device binding occurs during any restart, use: # /sbin/chkconfig rawdevices on SuSE Raw Device Administration Administer raw disk partitions in the /etc/raw file, which is a plain text file containing comments and examples for possible configurations: # /etc/raw #
CHAPTER 9: Postinstallation Tasks Accessing Raw Devices from the Server After you create partitions and bind the devices for raw disk I/O, Adaptive Server can use them.
CHAPTER 10 Adaptive Server Upgrades You can upgrade to Adaptive Server 15.7 from Adaptive Server versions 15.0 through 15.0.3, with the exception of versions 15.0.1 and 15.0.3 of the Cluster Edition. You can upgrade to this version of Adaptive Server from: • • Adaptive Server 15.0 through 15.0.3 (but not the 15.0.1 or 15.0.3 of the Cluster Edition) – to install version 15.7 on top of an earlier 15.x version, see Installing Adaptive Server Using Binary Overlay on page 86. Adaptive Server 12.5.
CHAPTER 10: Adaptive Server Upgrades and later (nonclustered editions). See the following table for all possible combinations of upgrades. An upgrade is done by: • • Upgrading your entire installation by switching binaries. Upgrading a single database using online database, having first loaded it with a database dump and transaction logs taken on a server with an earlier version. Table 6. Upgrading Your Entire Installation 70 Current Version Upgrading to Special Upgrade Information Adaptive Server 15.
CHAPTER 10: Adaptive Server Upgrades Current Version Upgrading to Special Upgrade Information Adaptive Server Cluster Edition 15.5.x or later Adaptive Server Cluster Edition 15.7.x In the installer destination directory pane, enter the 15.5.X directory, then choose Update. After your installation, install the new system procedures (from $SYBASE/ASE-15_0/scripts/installmaster). See "Installation of Version 15.7 ESD #2 over Existing 15.x Adaptive Server" on page 85 for details. Table 7.
CHAPTER 10: Adaptive Server Upgrades Considerations for Component Integration Services If you have both a local and a remote server running on Adaptive Server version 15.x and are upgrading both of them to version 15.7 ESD #2, upgrade the local server first. If you plan to upgrade one server but not the other, upgrade the local server. Sybase does not certify that Component Integration Services running on earlier versions of Adaptive Server can connect to later versions.
CHAPTER 10: Adaptive Server Upgrades 4. Enter preupgrade to run the preupgrade utility. Changes in Adaptive Server Directories The directory structures for Adaptive Server installations differ depending on version. Table 8. Directory Changes for UNIX Platforms Component 12.5.4 Location 15.0.2 Location 15.0.3 Location 15.5, 15.7, and 15.
CHAPTER 10: Adaptive Server Upgrades Component 12.5.4 Location 15.0.2 Location 15.0.3 Location 15.5, 15.7, and 15.7 ESD #1 and ESD #2 Locations Job Scheduler $SYBASE/ JS-12_5 $SYBASE/ ASE-15_0/ jobscheduler $SYBASE/ ASE-15_0/ jobscheduler $SYBASE/ ASE-15_0/ jobscheduler $SYBASE/ UAF-2_0 $SYBASE/ UAF-2_0 $SYBASE/ UAF-2_5 Unified Agent In Adaptive Server 15.7 ESD #1 and later, UAF-2_5 is placed with SCC-3_2 for the Sybase Control Center.
CHAPTER 10: Adaptive Server Upgrades The default RUN_servername file for a server SYBASE is called RUN_SYBASE. If the RUN_servername file for your current server is named differently, use the actual name of your server during the upgrade process. 5. Verify that the text of all stored procedures you upgrade is available in syscomments by either: • • Reinstalling the procedures with text, or, Removing and reinstalling the procedures after the upgrade.
CHAPTER 10: Adaptive Server Upgrades • • $SYBASE/interfaces $SYBASE/$SYBASE_ASE/servername.cfg – where servername is your server name. $SYBASE/$SYBASE_OCS/config/libtcl.cfg $SYBASE/SYSAM-2_0/licenses/license.lic • • 16. If you have enabled the Java in the database feature, create the sybpcidb database and disable the feature during the installation. 17. Set the environment variables by sourcing the SYBASE.[csh, sh, env] file. Warning! Do not run the environment variable script more than once. 18.
CHAPTER 10: Adaptive Server Upgrades Note: Before upgrading, use sp_renamedb to change the name of any user database that is a reserved word. If you change an object name, also change applications and stored procedures that refer to that object. Conflicts between object names do not prevent the upgrade process from completing. However, applications that refer to conflicting object names may not work after the upgrade. Rename all objects that use reserved words.
CHAPTER 10: Adaptive Server Upgrades create table [table] ( [int] int, [another int] int ) 3. Run sp_checkreswords in master and in each user database to display the names and locations of conflicting identifiers. See Reference Manual: Procedures for information about sp_dboption, sp_rename, and sp_checkreswords. Quoted Identifiers To avoid reserved word conflicts, all users on the server must invoke the quoted_identifier option in all stored procedures and queries that include the reserved words.
CHAPTER 10: Adaptive Server Upgrades 1> sp_create_syscoordinations 2> go Adaptive Server uses this database for tracking transactions and during recovery. It is also used by applications using two-phase commit and DTM. 4. Verify that the sybsystemdb database is large enough. For an upgrade, the default size for sybsystemdb is 124MB, or enough free space to accommodate the existing sybsystemdb database, and the largest catalog that is to be upgraded, plus 10 percent for logging upgrade changes.
CHAPTER 10: Adaptive Server Upgrades 1> sp_helpdb sybsystemprocs 2> go Use sp_helpdevice to determine the size of the sysprocsdev device: 1> sp_helpdevice sysprocdev 2> go If the db_size setting is less than the required minimum, increase the size of sysprocdev. Increasing the Size of the sybsystemprocs Database Create a new database with sufficient space if your current sybsystemprocs database does not have the minimum space required for an upgrade.
CHAPTER 10: Adaptive Server Upgrades Increasing Device and Database Capacity for System Procedures If you cannot fit the enlarged sybsystemprocs database on the system procedures device, increase the size of the device and create a new database. Prerequisites This procedure removes all stored procedures you have created at your site. Before you begin, save your local stored procedures using the defncopy utility. See the Utility Guide. Task This procedure involves dropping the database.
CHAPTER 10: Adaptive Server Upgrades 3. Remove the device: 1> sp_configure "allow updates", 1 2> go 1> delete sysdevices where name in ("devname1", "devname2", ...) 2> go 1> sp_configure "allow updates", 0 2> go The where clause contains the list of device names returned by the query in step 1. Note: Each device name must have quotes. For example, "devname1", "devname2", and so on. If any of the named devices are OS files rather than raw partitions, use the appropriate OS commands to remove those files. 4.
CHAPTER 10: Adaptive Server Upgrades Upgrade to Adaptive Server 15.7 ESD #2 After you successfully run the preupgrade utility, you are ready to upgrade Adaptive Server. Upgrading Interactively Using sqlupgrade Use the interactive sqlupgrade tool to upgrade Adaptive Server using an X-Windows or Motif GUI. Prerequisites Set the OLDSYBASE_ASE variable to the SYBASE_ASE appropriate to your older server. If you are upgrading from 12.5 for example, OLDSYBASE_ASE should be ASE-12_5.
CHAPTER 10: Adaptive Server Upgrades Warning! Do not interrupt the upgrade, connect to Adaptive Server, or run any stored procedures while the upgrade is in progress. You can also check progress by viewing the sqlupgrade log in $SYBASE/ $SYBASE_ASE/init/logs/sqlupgradeMMDD.NNN, where: • MM – is the month. • DD – is the date. • NNN – is a three-digit number identifying the srvbuild server upgrade session.
CHAPTER 10: Adaptive Server Upgrades If the resource file you are modifying was created by sqlupgrade, the prefix of the attribute name may vary. sqlupgraderes ignores this prefix when processing the resource file. Attribute Default Value [other options] sybinit.release_directory $SYBASE [path = _name_of_old_release] sybinit.product sqlsrv sqlsrv.server_name server_name sqlsrv.new_config No sqlsrv.sa_login current_login sqlsrv.sa_password current_password sqlsrv.do_upgrade Yes sqlsrv.
CHAPTER 10: Adaptive Server Upgrades See also • Managing Java in the Database During Installations and Upgrades on page 33 Determining the Adaptive Server Version Before using the binary overlay, verify that your current version of Adaptive Server is at least 15.x. If your server is at a 15.7 version level, you can begin installing Adaptive Server 15.7 ESD #2. 1. Verify that you have version 15.
CHAPTER 10: Adaptive Server Upgrades the initial and final steps. Doing so flushes free space accounting figures, object statistics, and runs checkpoint on the database to minimize recovery work during the upgrade process. 2. Use the installer to load the new software from the CD or DVD. Navigate to the CD or DVD drive and enter ./setup.bin. 3. Install Adaptive Server 15.7 ESD #2 into the existing $SYBASE installation path.
CHAPTER 10: Adaptive Server Upgrades upgrade_object to upgrade compiled objects such as check constraints, rules, triggers, and views. 4. Run the scripts for different options or licensed features: • installcommit – if you use two-phase commit or distributed transactions, re-run installcommit to restore: • sp_start_xact • sp_abort_xact • sp_remove_xact • sp_stat_xact • sp_scan_xact • sp_probe_xact • installsecurity – if you used auditing in your earlier installation.
CHAPTER 10: Adaptive Server Upgrades If you run instmsgs.ebf after installing the 15.7 ESD #2 localized message, this script may delete some new messages. Restoring Functionality in Adaptive Server After Upgrading Restore functionality in the server after an upgrade. 1. If you changed any configuration parameters before upgrading, use sp_configure to set them back to their earlier values. 2. Use sp_dboption to reset any database options you disabled before upgrading. 3.
CHAPTER 10: Adaptive Server Upgrades Reenabling Auditing If the server you upgraded from was configured for auditing, reenable auditing in the upgraded server. 1. Enter: sp_configure 'auditing', 1 2. Reenable auditing for all system stored procedures for which auditing was enabled before the upgrade. a) Use the output of sp_displayaudit recorded during preupgrade to help determine the system stored procedures for which auditing was enabled. b) Reenter the audit options using sp_audit.
CHAPTER 10: Adaptive Server Upgrades 1> dump transaction sales with truncate_only 2> go 3. Reenable replication. Restoring Replication on Replicate Databases Restore replication if you have upgraded a destination-only dataserver in a replication system. Perform these steps for each replicate database and Replication Server System Database (RSSD). 1. Start Adaptive Server if it is not already running. 2. Log in to the Adaptive Server. 3. If you have zeroed out the locator for the database, go to step 4.
CHAPTER 10: Adaptive Server Upgrades 1> rs_zeroltm dataserver, database 2> go 2. Log in to each replicated primary, and replicated RSSD and issue: 1> use database 2> go 1> dbcc settrunc ('ltm', 'valid') 2> go 3. Restart the Replication Server. 4.
CHAPTER 10: Adaptive Server Upgrades 2. Create a 64-bit server in a new directory. 3. Create devices and databases to match those in the 32-bit server. Make sure the sysusages mapping is correct. Note: Allow 10 percent additional space for the sybsystemprocs database. 4. 5. 6. 7. Dump the databases from the 32-bit server. Load the databases to the 64-bit server. If you have partitioned tables, update partition statistics. Run dbcc checks on the 64-bit server and make sure they run cleanly.
CHAPTER 10: Adaptive Server Upgrades 4. Copy the interfaces file and the configuration file from the 32-bit $SYBASE directory to the 64-bit $SYBASE directory. 5. Copy the 32-bit $SYBASE/$SYBASE_ASE/install/RUN_server file to the equivalent 64-bit $SYBASE/$SYBASE_ASE/install directory. 6. Edit the RUN_server file to reflect the new location of the interfaces, configuration, and log files. 7. Remove all references to the 32-bit $SYBASE directories from your $PATH definition. 8.
CHAPTER 10: Adaptive Server Upgrades 1> sp_configure "number of locks", 9000 2> go 5. Upgrade the internal Job Scheduler SQL code using: 1> 2> 1> 2> use sybmgmtdb go dbcc upgrade_object go 6. Restart Adaptive Server. 7. (Optional) Add more log space. Some 64-bit platforms require additional space for the sybmgmtdb log: 1> 2> 1> 2> use master go alter database sybmgmtdb LOG on sybmgmtdev=20 go 8.
CHAPTER 10: Adaptive Server Upgrades 4. If you modified Sybase-supplied templates, stored procedures, or XML documents, do not overlay the new templates with your modified versions. If you do, you lose the enhancements provided by the revised templates. Carefully merge your template changes into the Sybase template files, or better yet, rename your modified templates. Note: If you modify Sybase-supplied templates, save the changes under new names and in new files. 5.
CHAPTER 10: Adaptive Server Upgrades Template Modified Files Datatype for Changed from varchar(5) to int reclaim tables SybReclaimTableTemplate.xml @resume_flag jst_reclaim_table_space 6. Some Job Scheduler templates have been modified to support new server functionality. These changes are related to new parameters for specifying a partition name, or a data change value for the new server commands that added these options.
CHAPTER 10: Adaptive Server Upgrades Template Modified File Change Descrip- Job Modifications tion reclaim indexes SybReclaimIndexTemplate.xml Added @ptn_name as Required. Include valthird parameter. ue (or NULL) for new parameter. jst_reclaim_index_space reclaim tables SybReclaimTableTemplate.xml jst_reclaim_table_space multiple jst_get_freespace,jst_get_use dspace Added @ptn_name as Required. Include valsecond parameter. ue (or NULL) for new parameter. Replace re- No impact on job SQL.
CHAPTER 10: Adaptive Server Upgrades • • • • • • HP-UX – MCSG 11.17 HPIA – MCSG 11.18 IBM AIX – HACMP 5.4 Sun Solaris – VCS4.0, SunCluster 3.2 Linux-AMD – VCS4.1 Win2003 – Cluster Manager 5.2 There are two ways to upgrade a cluster subsystem: • • Perform a major upgrade, which involves cluster downtime, then shut down and restart all servers. You must: a) Run sp_companion suspend, as described in Using Sybase Failover in a High Availability System.
CHAPTER 10: Adaptive Server Upgrades 2. Upgrade the cluster subsystem on N2 following the upgrade instructions from the vendor. 3. Start ASE2 by bringing the secondary resource group online to N2. Upgrading Java in the Database If Java in the database functionality is currently enabled, you must run the installpcidb script, which creates tables and stored procedures in the sybpcidb database. 1. Using isql, run the installpcidb script that is included with the release.
CHAPTER 10: Adaptive Server Upgrades 3. Perform the upgrade steps as prompted. See also • Upgrade to Adaptive Server 15.7 ESD #2 on page 83 Upgrading Databases Using Dump and Load When you upgrade Adaptive Server, you can also upgrade databases and transaction logs from versions of Adaptive Server as early as 12.5 using the dump and load commands. Some issues of which you should be aware: • • The upgrade process requires space for copying data and logging changes to the system tables.
CHAPTER 10: Adaptive Server Upgrades Compiled objects for which the source text was hidden using sp_hidetext are upgraded in the same manner as objects for which the source text is not hidden. For information on sp_checksource and sp_hidetext, see Reference Manual: Procedures. Note: If you are upgrading from a 32-bit to a 64-bit Adaptive Server, the size of each 64-bit compiled object in the sysprocedures table in each database increases by approximately 55 percent when the object is upgraded.
CHAPTER 10: Adaptive Server Upgrades Problem Description Solution Reserved word errors If you load a database dump from an earlier version of Adaptive Server into Adaptive Server 15.7 or later and the dump contains a stored procedure that uses a word that is now reserved, when you run dbcc upgrade_object on that stored procedure, the command returns an error. Either manually change the object name or use quotes around the object name, and issue the command set quoted identifiers on.
CHAPTER 10: Adaptive Server Upgrades select name from syscolumns where id = object_id("employees") 3. Compare the output of the two queries by running sp_help on both the view and the tables that comprise the view. This comparison works only for views, not for other compiled objects. To determine whether select * statements in other compiled objects need to be revised, review the source text of each compiled object.
CHAPTER 11 Adaptive Server Downgrades An Adaptive Server that has been upgraded to 15.7 or later requires specifics tasks before it can be downgraded. Even if you have not used any of the new features in Adaptive Server 15.7 or later, the upgrade process added columns to system tables. This means you must use sp_downgrade to perform the downgrade. The sp_downgrade procedure requires sybase_ts_ role, and you must have sa_role or sso_role permissions. See sp_downgrade in Reference Manual: Procedures.
CHAPTER 11: Adaptive Server Downgrades alter table @tablename set compression = none reorg rebuild @tablename • • If any table uses LOB compression or in-row LOBs: a) Copy the data from that table to a new table. b) Drop the original table.
CHAPTER 11: Adaptive Server Downgrades 2. Make sure Adaptive Server 15.7 ESD #2 is prepared for downgrade by executing this command from the master database: sp_downgrade 'prepare', @toversion='version' The format for the value of version does not need periods, so these are all valid:"15.5", "155", "15.0", "150", "15.0.1", "1501", "15.0.2", "1502", "15.0.3," "1503". The version you enter should be the Adaptive Server version to which you want to downgrade. Note: If you have used the 15.0.
CHAPTER 11: Adaptive Server Downgrades and print on the console. Save the output of sp_downgrade 'downgrade', into a file, so the passwords are not lost. To regenerate the sa password, restart the downgraded server with -psa. See sp_passwordpolicy in Reference Manual: Procedures. 6. To restore the original messages for the earlier version of Adaptive Server, run this script after downgrading the server: isql -Usa -Psa_password -irestoremsgs.ebf 7.
CHAPTER 11: Adaptive Server Downgrades where: • @db_name – is the name of the database you are downgrading • @esd – is the ESD number you are downgrading to. The valid options are: • "ESD1" – for Adaptive Server version 15.7 ESD #1. • "GA" – for Adaptive Server version 15.7. • @verbose – when used, displays the output in the verbose mode. For example: 1> sp_downgrade_esd tempdb, esd1 2> go Reverting database 'tempdb' to 'ESD1'. Database 'tempdb' is now suitable for use by ESD1.
CHAPTER 11: Adaptive Server Downgrades Dumping a 15.7 ESD #2 Database to Load into a 15.7 or 15.7 ESD #1 Adaptive Server Using sp_downgrade_esd on an Adaptive Server 15.7 ESD #2 database allows you to load it into Adaptive Server 15.7 or 15.7 ESD #1. Prerequisites To use sp_downgrade_esd, you must have sa_role, and be in the master database. Task If you have a database in Adaptive Server version 15.7 ESD #2 that you want to open in Adaptive Server 15.7 or 15.
CHAPTER 11: Adaptive Server Downgrades Additional Considerations for New Features Used Additional downgrade steps may be necessary due to Adaptive Server 15.7 or later features that are unavailable in the Adaptive Server version to which you are downgrading. In general, no additional steps are required when you are returning to an Adaptive Server version in which the feature was already available. Returning to 15.0.
CHAPTER 11: Adaptive Server Downgrades Feature Considerations Unicode noncharacters If you used sp_configure to enable functionality group or permissive Unicode in Adaptive Server 15.7 ESD #2, and also stored Unicode noncharacters (that is, u +FFFF or u+FFFE) in a database, you may see a conversion error after you downgrade to a version earlier 15.7 when Adaptive Server retrieves the data and triggers a character set conversion.
CHAPTER 11: Adaptive Server Downgrades See also • Downgrading from Adaptive Server 15.7 ESD #2 on page 106 Downgrading an Adaptive Server That Uses Encryption Downgrade an Adaptive Server versions 15.7 and later if you enabled 256-bit key encryption keys. 1. Set the downgrade_kek_size configuration option to true. This means you must change the key encryption key size to 128 bits. 2.
CHAPTER 11: Adaptive Server Downgrades Downgrade Considerations for Adaptive Server with Replicated Databases Special considerations exist for downgrading Adaptive Server version 15.7 that uses replicated databases, If the server you are downgrading from has replicated databases and SQL replication has been enabled, you must follow different procedures depending upon the version of Adaptive Server you are downgrading to. If your replication system is using RepAgent and you are downgrading to a 15.0.
CHAPTER 11: Adaptive Server Downgrades stored procedures introduced in releases subsequent to the downgraded server are not removed. Warning! Executing new stored procedures against an older binary may cause unpredictable results. 2. During the upgrade to Adaptive Server 15.7 ESD #2, you should have created a restore_msgs.ebf file. Run this script now to restore your messages back to the version from which you upgraded: isql -Usa -P
CHAPTER 11: Adaptive Server Downgrades 116 Adaptive Server Enterprise
CHAPTER 12 Troubleshooting SySAM Errors Troubleshoot the most common SySAM errors. See your Sybase product documentation for product-specific information. See the SySAM FAQ at http://www.sybase.com/sysam for the most recent troubleshooting information. If a license problem occurs, solve the problem as quickly as possible. Products that cannot acquire a valid license during installation may still install or run under grace.
CHAPTER 12: Troubleshooting SySAM Errors Error Possible Causes Solution Updating an Existing Installation If you are updating an existing installation, make sure your license authorizes you to install the update. See Installing If you are installing an update that is authorized by the license, see the solution for Product Updates, EBFs, and Support Renewal in the SySAM Users Guide. If your license does not allow you to perform the update, the product may not be usable.
CHAPTER 12: Troubleshooting SySAM Errors Error Possible Causes License Server Does • not Recognize the License Files • • Linux virtual machine does not appear to be part of the Microsoft Hyper-V host. Installation Guide Solution The license was generated • for a different machine or generated using an incorrect host ID. The license has been altered. You cannot change any information in a generated license.
CHAPTER 12: Troubleshooting SySAM Errors Error Possible Causes Solution Product Does not Start, License Checkout Error • At a command prompt or in a terminal window, execute the following commands, where feature_name is the name of the feature for which SySAM failed to check out a license: • • • • • • • 120 You have not generated and deployed the valid licenses for the product requesting licenses. The required license does not exist and the product does not award a license on grace.
CHAPTER 12: Troubleshooting SySAM Errors Error Possible Causes Solution Product Cannot Check Out a License and Starts in Grace Period To help you determine the pos- See Served License Deployment Models or sible causes when your product Unserved License Deployment Models, cannot check out a license, ex- both in the SySAM Users Guide.
CHAPTER 12: Troubleshooting SySAM Errors Error Possible Causes Product Obtains the Wrong License These locations are searched, • in the order specified, until a suitable license is found. When a license directory is specified, • license files in that directory are loaded in the directory sort order. When a product looks for a license, it looks in: • • Solution Configure your product to choose a license for a specific edition and license type.
CHAPTER 12: Troubleshooting SySAM Errors Installing for the First Time The installer or product cannot find a valid license and issues a warning. 1. If the installation fails, go to SPDC or SMP to generate and install the required valid licenses, then restart the installation. 2. Verify that you have generated and deployed the correct license.
CHAPTER 12: Troubleshooting SySAM Errors • The licenses on one machine were generated for a different machine – examine the host ID recorded next to the value in the license file host name in the SERVER header. It must match the host ID for the machine on which the license server will run.
CHAPTER 12: Troubleshooting SySAM Errors Possible Causes Solutions The available licenses are for a different operating Obtain a license for the correct platform from system or architecture than the machine on which SPDC. you are running your product feature. 1. Check the license back in to SPDC. 2. Generate a license for the correct platform, or install the product on the correct platform. 3. Deploy a license to the local machine where you are running your instance of the Sybase product.
CHAPTER 12: Troubleshooting SySAM Errors Served License Deployment Models Learn about license checkout problems for served licenses. Possible Cause Solution The license server may not be running. Verify that the license server is running by entering this command from the bin directory on the license server host: sysam status If the license server is not running, restart it. The license server is running, but does not contain Enter the following command to determine if the the desired license.
CHAPTER 12: Troubleshooting SySAM Errors Possible Cause Solution Cannot connect to the license server Ensure that the client can connect to both TCP/IP ports used by the license server. If there is a firewall, fix the ports used by both lmgrd and the SYBASE vendor daemon (the license server's constituent processes), and set up the firewall or VPN policies to allow access to both ports. The license server's SYBASE.log file shows the port numbers to be fixed:.
CHAPTER 12: Troubleshooting SySAM Errors • The output from: sysam diag feature_name • • • 128 The license server software version The license server debug log file The licenses that are saved in the licenses subdirectory of the SYSAM-2_0 directory on the license server host machine Adaptive Server Enterprise
CHAPTER 13 Troubleshoot the Server Determine the cause of problems and apply the recommended solution. To determine the cause of an error, first look in the log file of the utility being used, to identify the task the utility was performing when it failed. Then check the server error log. This table lists possible causes and solutions for common problems that you might encounter during a first-time installation or upgrade. If you continue to have problems, retry the installation or upgrade.
CHAPTER 13: Troubleshoot the Server Error Logs for Installation Utilities The information in the error logs may help determine the reason and possible solutions for problems with installation-related utility programs. Locations of Error Logs for Installation-Related Utilities Utility Default Location and File Name InstallAnywhere $SYBASE/log/ASE_Suite.log srvbuildres $SYBASE/$SYBASE_ASE/init/logs/srvbuildMMDD.NNN where: • • • sqlupgraderes • • MM – is the month. DD – is the date.
CHAPTER 13: Troubleshoot the Server Troubleshooting Common Installation Problems Identify the cause of installation problems and apply the recommended solutions. Problem Resolution Cannot use XWindows. If the setup and configuration utilities do not show correctly, you may need to adjust the resolution on your monitor.
CHAPTER 13: Troubleshoot the Server Problem Resolution Client not authorized to connect to server. This error message means the remote machine does not have permission to display the user interface on the local machine where you start working: Xlib: connection to "host_name" refused by server Xlib: Client is not authorized to connect to Server xhost: unable to open display "host_name" To correct the problem: 1.
CHAPTER 13: Troubleshoot the Server Stopping Adaptive Server After a Failure If the installation or upgrade session fails after you start Adaptive Server for any reason, use the shutdown command. 1. Log on as "sa". 2. Shut down Adaptive Server using the shutdown with nowait command. This stops the Adaptive Server immediately, without waiting for currently executing SQL statements to finish: 1> shutdown with nowait 2> go 3.
CHAPTER 13: Troubleshoot the Server 2. Examine the log file in $SYBASE/$SYBASE_ASE/init/logs. After you resolve any problems, shut down Adaptive Server and use sqlupgrade to complete the upgrade session. When an Upgrade Fails If the upgrade process fails, the installation program displays error messages. Once you start Adaptive Server on the new version, you cannot start Adaptive Server on the earlier version. Attempts to do so result in having to restore from backups.
CHAPTER 13: Troubleshoot the Server • If you are concerned about the possible corruption of your databases, exit Server Config, but do not attempt to restart the upgrade session until you have restored the databases from backup. After restoration is complete, retry the upgrade. Recovering from a Failed Upgrade Upgrade issues may be due to a failure to upgrade an individual database, or a failure to complete configuration changes after all databases have been upgraded.
CHAPTER 13: Troubleshoot the Server online database @dbname select @dbname = min(name) from master..sysdatabases where name > @dbname end • Reinstall system stored procedures using the scripts from the new version: isql -Usa -Ppassword -i $SYBASE/$SYBASE_ASE/scripts/installmaster • Note: When a server fails during an upgrade process, it attempts to upgrade the databases when it restarts.
CHAPTER 13: Troubleshoot the Server 2. Contact Sybase Technical Support with the information.
CHAPTER 13: Troubleshoot the Server 138 Adaptive Server Enterprise
CHAPTER 14 Obtaining Help and Additional Information Use the Sybase Getting Started CD, Product Documentation site, and online help to learn more about this product release. • • • The Getting Started CD (or download) – contains release bulletins and installation guides in PDF format, and may contain other documents or updated information. Product Documentation at http://sybooks.sybase.com/ – is an online version of Sybase documentation that you can access using a standard Web browser.
CHAPTER 14: Obtaining Help and Additional Information c) If prompted, enter your MySybase user name and password. d) (Optional) Select a filter, a time frame, or both, and click Go. e) Select a product. • Padlock icons indicate that you do not have download authorization for certain EBF/ Maintenance releases because you are not registered as an authorized support contact.
CHAPTER 14: Obtaining Help and Additional Information generally also meet non-U.S. accessibility guidelines, such as the World Wide Web Consortium (W3C) guidelines for Web sites. Note: You may need to configure your accessibility tool for optimal use. Some screen readers pronounce text based on its case; for example, they pronounce ALL UPPERCASE TEXT as initials, and MixedCase Text as words. You might find it helpful to configure your tool to announce syntax conventions.
CHAPTER 14: Obtaining Help and Additional Information 142 Adaptive Server Enterprise
Index Index A accounts, creating sybase user 30 Adaptive Server installing in command line mode 47 installing in silent mode, unattended 47 Adaptive Server components 94 Adaptive Server Configuration Guide for UNIX 3 Adaptive Server editions 5 determining which edition you have 6 Adaptive Server plug-in for Sybase Central 6 additional steps for downgrading new features 111 adjusting shared memory parameters in operating system 32 administration tasks 30 applications changing after renaming objects 76 B Ba
Index error information, finding 117 license checkout 117 error log files troubleshooting and 133 F fails preupgrade eligibility 133 features, separately licensed optional 19 file descriptors 31 finding license error information 117 finding compiled object errors before production 102 G generating served licenses 22 unserved licenses 22 grace period 16, 117 cannot check out 117 license continues to run after fixing 117 GUI installation 37 H heartbeat 16 host IDs determining 17 lmutil utility 17 on Window
Index M memory requirements 11 methods of installation Adaptive Server 37 migrating dump and load method 92 methods 92 minimal configuration Adaptive Server 41 minimum size for database devices 65 modifying individual licenses 25 mount commands by platform 37 mounting the Replication Server installation media 37 multipathing described 34 setting up before installation 35 N new features reverting to earlier version 111 O objects conflicting names of 77 renaming 77 optional databases 60 optional features d
Index SCC starting 55 scripts installpix 62 installpubs2 62 installpubs3 62 location 61 security services described 6 separately licensed optional features 19 served licenses 22 license servers 16 server component descriptions 26 directory layout 26 overview 5 servers, license 16 shared memory parameters adjusting 32 shared-memory segments allocating 11 showserver command 57 silent installation 52 source environment variables 37 sp_checkreswords system procedure 77 sp_downgrade system procedure 106 sp_downg
Index upgrading Adaptive Server 69 entire installations 69 failure 134 Java in the database 100 single databases 69 tasks after you upgrade 87 using bcp 93 upgrading compatibility versions 69 upgrading compiled objects dbcc upgrade_object 101 upgrading high availability and cluster support 98 upgrading Job Scheduler templates 95 Installation Guide utilities 7 dsedit 91 sqlupgrade 83 sqlupgraderes 84 V verifying connection to the server 58 virtual network adaptor license problems 117 W warning, installat
Index 148 Adaptive Server Enterprise
