Installation Guide Adaptive Server® Enterprise 15.0.
DOCUMENT ID: 35889-01-1502-01 LAST REVISED: April 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 Overview .......................................................................................... 1 Product licensing with SySAM 2.0.................................................... 2 Product components ........................................................................ 3 Adaptive Server Enterprise .....................................
Contents Installing the Adaptive Server version 15.0.2 binary overlay... 36 Backward compatibility with previous Adaptive Server 15.x versions ............................................................................ 37 XML Services in Adaptive Server version 15.0.2 .................... 38 CHAPTER 3 Post-Installation Tasks.................................................................. 39 Verifying that servers are running ..................................................
Contents CHAPTER 6 Reenabling auditing................................................................. Shutting down SySAM servers................................................ Upgrading Backup Server, Monitor Server, and XP Server ........... Upgrading Job Scheduler............................................................... Upgrading Job Scheduler templates ....................................... Upgrading high availability .............................................................
Contents Uninstalling Adaptive Server 15.0.2 ............................................. 119 Removing an existing Adaptive Server ........................................ 120 AP PE ND IX A AP PE ND IX B AP PE ND IX C Alternative Installation Methods ................................................ Installation on consoles (non-GUI mode)..................................... Silent installation ..........................................................................
About This Book The Installation Guide for Sybase Adaptive Server Enterprise for 15.0.
Related documents • Chapter 5, “Upgrading Adaptive Server,” describes how to upgrade an existing Adaptive Server to the current version. • Chapter 6, “Troubleshooting SySAM Issues,” provides information about and solutions to SySAM related errors. • Chapter 7, “Troubleshooting,” provides installation error messages and possible solutions to installation problems. • Chapter 8, “Removing Adaptive Server,” describes how to uninstall Adaptive Server.
About This Book Installation Guide • Component Integration Services User’s Guide – explains how to use the Adaptive Server Component Integration Services feature to connect remote Sybase and non-Sybase databases. • The Configuration Guide for your platform – provides instructions for performing specific configuration tasks for Adaptive Server. • Full-Text Search Specialty Data Store User’s Guide – describes how to use the Full-Text Search feature with Verity to search Adaptive Server Enterprise data.
• x Monitoring and Analyzing – explains how statistics are obtained and used for monitoring and optimizing performance. • Quick Reference Guide – provides a comprehensive listing of the names and syntax for commands, functions, system procedures, extended system procedures, datatypes, and utilities in a pocket-sized book.
About This Book Other sources of information • Web Services User’s Guide – explains how to configure, use, and troubleshoot Web Services for Adaptive Server. • XA Interface Integration Guide for CICS, Encina, and TUXEDO – provides instructions for using the Sybase DTM XA interface with X/Open XA transaction managers.
• 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.
• Commands for both the C shell and the Bourne shell are provided in this document, when they differ. The initialization file for the C shell is called .cshrc. The initialization file for the Bourne shell is called .profile. If you are using a different shell, such as the Korn shell, refer to your shellspecific documentation for the correct command syntax. Table 1 shows the conventions for syntax statements in this manual.
About This Book 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 Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support.
xvi Adaptive Server Enterprise
CH A PTE R 1 Overview This chapter introduces important concepts about the product and installation of Adaptive Server and Adaptive Server products. Topic Product licensing with SySAM 2.0 Page 2 Product components Adaptive Server editions 3 5 Adaptive Server specifications Product descriptions and directory layout 7 7 PC-Client product descriptions and directory layout 9 This installation guide contains information about how to install and configure Adaptive Server version 15.0.2.
Product licensing with SySAM 2.0 Product licensing with SySAM 2.0 Starting with Adaptive Server Enterprise version 15.0, the Sybase Software Asset Management System (SySAM) implementation has changed. With these changes, SySAM configuration is no longer optional, and requires some changes in the Adaptive Server installation and configuration process. Review the updated SySAM implementation and plan your SySAM deployment before you install Adaptive Server Enterprise.
CHAPTER 1 Overview Product components Adaptive Server Enterprise is based on the client/server model. Each Adaptive Server user is associated with a client process that communicates with a server process via a network interface called the Tabular Data Stream™ (TDS) protocol. The client process may execute on one machine and communicate with a database server on the same or a different machine.
Product components The heart of Adaptive Server is the SQL/DBMS engine. The SQL/DBMS engine processes data manipulation statements (DML), utility commands, which are generally data definition statements (DDL) and administrative functions, and performs stored procedure executions. The DBMS engine uses the services provided by the resource manager routines and the access methods routines.
CHAPTER 1 Overview Application code Open Client Request Response Network interface Figure 1-1: Adaptive Server system model sql compiler RPC Shared memory SQL executive Access Manager Data cache Procedure cache Data tables Indexes Transaction log System procedures Adaptive Server editions Adaptive Server is available in the following editions: • Enterprise Edition – has no limit on scalability and can run all available options that can be purchased separately.
Adaptive Server editions Use the sp_lmconfig command to determine which edition of Adaptive Server your are running. Enter: sp_lmconfig 'edition' go Adaptive Server returns value of EE, SE, DE or XE based on the edition it is running. See the Reference Manual for more information about the sp_lmconfig command. Enterprise Edition The Enterprise Edition (EE) includes a full-featured Adaptive Server. In addition to the base server, you can purchase options, including High Availability.
CHAPTER 1 Overview Adaptive Server specifications Table 1-1 provides Adaptive Server specifications for Sun Solaris. Table 1-1: Adaptive Server specifications for Sun Solaris Hardware and memory Sun Solaris 32-bit Processor Minimum RAM for Adaptive Server Default user stack size Memory per user connection Sun Solaris 64-bit Processor Minimum RAM for Adaptive Server Default user stack size Memory per user connection 32-bit 66MB 45K Approx. 145K 64-bit 92MB 84K Approx.
Product descriptions and directory layout Table 1-2: Product description Product Adaptive Server and Historical Server Description Installed into the ASE-15_0 directory. • Adaptive Server – the database server. • Backup Server – an Open Server-based application that manages all database backup (dump) and restore (load) operations.
CHAPTER 1 Overview Product Description Collation Sequences Installed into the collate directory. Provides the collation sequences available for use with Adaptive Server. ASE Replicator Installed into the RPL-15_0 directory. Provides lightweight replication for those companies who do not need a full-featured replication product such as Sybase Replication Server. Sybase Software Asset Management (SySAM) Installed into the SYSAM-2_0 directory.
PC-Client product descriptions and directory layout Table 1-3: Products and platforms Product Software Developer Kit (SDK) Description Installed into the OCS-15_0 directory. • Open Client ( Ctlib, dblib) • ESQL/C • Monitor Client Library • ESQL/COBOL • XA Installed into the DataAccess directory: • ODBC (Windows and Linux only ) – a driver used to connect to Adaptive Server from ODBC based applications. • OLEDB (Windows only) – a provider used to connect to Adaptive Server from OLE DB-based applications.
CHAPTER 1 Overview Product Description Unified Agent Unified Agent is a management framework that provides runtime services to manage, monitor, and control distributed Sybase resources. Agents plug into the framework and provide the ability to manage specific components. It is installed into the new UA directory %SYBASE%\UAF-2_0. A collection of Adaptive Server utility programs including: jutils-2_0 • jisql – a JDBC-based GUI isql tool.
PC-Client product descriptions and directory layout 12 Adaptive Server Enterprise
CH A PTE R 2 Installing Adaptive Server This chapter provides instructions for installing a new Adaptive Server, Backup Server, and Monitor Server. Topic Overview Page 13 System requirements Pre-installation tasks for SySAM 14 14 Pre-installation tasks for Adaptive Server Installing server components 22 26 Installing version 15.0.2 over an existing 15.
System requirements 3 Perform the installation using any of the methods described in “Installation methods” on page 27. 4 Perform the post-installation tasks as described in Chapter 3, “PostInstallation Tasks.” System requirements Check to make sure your system has the required version-level, RAM, and network-protocol requirements for Adaptive Server. See the release bulletin for your platform the latest information about required system patches.
CHAPTER 2 Installing Adaptive Server For information about served and unserved licenses, and which model is best suited for your environment, see Chapter 2, “Choosing a License Model” in the Sybase Software Asset Management User’s Guide. 2 If you plan to use a served license, you need a license server. Decide whether it will be an existing license server or a new license server. The license server need not be on the same machine or running on the same operating system and architecture.
Pre-installation tasks for SySAM To access SPDC when you have purchased Sybase products from Sybase: 1 Once you have ordered a Sybase product you receive a welcome e-mail that contains a URL to the SPDC site, as well as a user name and password. Note If you have purchased your Sybase software from a Sybase reseller, you will receive a web key rather than an e-mail. 2 Click on the URL, and when prompted, enter the designated user name and password. Your login is typically your e-mail address.
CHAPTER 2 4 Installing Adaptive Server Save the host ID so you can use it later at SPDC. Your host ID is platform-specific, but may be similar to: 170a3472 on Solaris platforms. Generating licenses at SPDC This section provides information about how to generate a license for a served and an unserved license model. To generate your license, regardless of license model: 1 At the Welcome screen at SPDC, you can view all of the product families to which you have access.
Pre-installation tasks for SySAM 7 Step one of the SySAM license generation wizard asks you to choose between a served license and an unserved license. If you choose a served license, continue with the steps in “Generating a served license” on page 18, and if you choose an unserved license, continue with the steps in “Generating an unserved license” on page 19. Note Some Sybase Products or specific license types do not give you a choice of license model to use, and therefore do not display this page.
CHAPTER 2 6 Installing Adaptive Server a Download the license file by clicking the Download License File button. b Print a paper copy of the license by clicking the Print Friendly button. c Return to the license information page to generate additional licenses. Once you have generated all the licenses you need, save them to the licenses directory in your license server installation. Note You must save your license files with a .lic extension, or SySAM 2.0 will not recognize them.
Pre-installation tasks for SySAM 6 Once you have generated all the licenses you need, save them to the specific location required by your product. Note You must save your license files with a .lic extension, or SySAM 2.0 does not recognize them. Installing a new license server Note If you have selected a served license model, you must install a license server. Perform the following steps to install a new license server. 1 2 Install the license server.
CHAPTER 2 Installing Adaptive Server 4 Go to the Sybase Product Download Center (SPDC) at https://sybase.subscribenet.com. 5 Generate the licenses for the products you want to install. For instructions on generating your licenses, see “Generating licenses at SPDC” on page 17. 6 From command prompt navigate to installed directory Source/Execute to setup the environment variables. • ASE150.[csh.
Pre-installation tasks for Adaptive Server Pre-installation tasks for Adaptive Server Before installing Adaptive Server: 1 Read the release bulletins for the latest information on the products (Adaptive Server, Monitor Server, and so on) that you are installing. See “Special Installation Instructions” in the release bulletin. 2 Install operating system patches, if required.
CHAPTER 2 Installing Adaptive Server 7 Decide where the Adaptive Server software will be installed. Make sure there is sufficient available disk space. There cannot be any spaces in the path name of the directory. 8 Know what product edition you are installing.
Pre-installation tasks for Adaptive Server 12 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. If you are having connection problems, or to verify your network configuration, ping the host. 13 14 15 Adjust the operating system shared memory parameter. Because Solaris 10 is shifting to a new method of controlling system resources.
CHAPTER 2 Installing Adaptive Server project-sybase:200:For use by Sybase:sybase:sybase: project.max-shm-memory=\(privileged,17179869184,deny) project.max-shm-memory=(privileged,17179869184,deny) – this is the name for the project parameter that replaces the old shminfo-shmmax parameter. “privilege” is a threshold value on a resource control that constitutes a point at which local actions can be triggered or global actions such as logging in to machine can occur.
Installing server components To adjust shared memory segments of the operating system, add the following line to the configuration file /etc/system: set shmsys:shminfo_shmseg=x where x is the number of shared memory segments. 19 20 If after adjusting the SHMMAX parameter the server fails to reboot you may also need to increase the value of another Kernel parameter, SHMALL, which is the maximum amount of shared memory that can be allocated. Its value is in the file /proc/sys/kernel/shmall.
CHAPTER 2 Installing Adaptive Server Installation methods The following instructions are for using the Installer in GUI mode. You can also perform the installation in a non-GUI (text-based) mode or a completely silent installation with no interaction. Or, you can perform the installation, then configure Adaptive Server separately using either the GUI-based configuration tools or silently with the use of a resource file.
Installing server components Not every country is listed in the drop-down list. If the country you are located in is not listed, select the most appropriate area. 5 The Install directory window allows you to select a directory for the installation by clicking Browse. Click Next to accept the default of: /opt/sybase You can also enter a directory for installation.
CHAPTER 2 8 Installing Adaptive Server If you select Custom, the Products and Features Selection window displays. Select the products you want to install by checking the box next to each product name. Note Some features are dependent on other features; therefore, you cannot unselect some items without first unselecting others. After you have made your selection, click Next. Before proceeding to the next window, the Installer verifies the selections, and checks for dependencies and available disk space.
Installing server components If you answer No, you will be using unserved licenses. You will be reminded to download and install the license file after you have finished the installation. Note When you download the license file, copy it to $SYBASE/$SYBASE_SYSAM/licenses. 13 The Sybase Software Asset Management Notification screen asks you to configure your server for e-mail notification.
CHAPTER 2 • Configure new Backup Server • Configure new Monitor Server • Configure new XP Server • Configure new Job Scheduler • Enable Self Management • Configure Web Services • Configure Unified Agent Installing Adaptive Server Select the servers you want to configure. If you do not want to configure the new servers at this point, unselect the item and click Next. The Custom Configure New Server Options window appears.
Installing server components • Custom configure new Job Schedule • Custom configure Self Management • Custom configure Web Services • Custom configure new Unified Agent The Custom Configure Input window displays next. 18 The Custom Configure Input window prompts you for the custom Adaptive Server configuration information. • Server name • Port number • Page size • Error log – name of error log file and the path where it should be located.
CHAPTER 2 • • 4K page size server – 6MB • 8K page size server – 12MB • 16K page size server – 24MB Installing Adaptive Server System database size (in MB) The minimum sizes are: • 2K page size server – 3MB • 4K page size server – 6MB • 8K page size server – 12MB • 16K page size server – 24MB Once you have customized the Adaptive Server configuration, select Next to record the input fields. 19 The Custom Configure Backup Server Input window prompts you for the Backup Server information.
Installing server components 23 Custom configure Self Management by entering the following information: • Self Management user name • Self Management password Note If you choose the default user name “sa,” you cannot enter the password. The “sa” default password is null. 24 25 The Unified Agent – Discovery Services screen prompts you to choose either a “Jini” adaptor or a UDP adaptor. The UDP adaptor is the default.
CHAPTER 2 Installing Adaptive Server 30 The Installation Complete window is the last window. If you encounter any errors, see the Troubleshooting Guide. Adaptive Server and related products have been successfully installed, and minimally configured for use. See “Installing sample databases” on page 42, to begin experimenting with your servers, or see the System Administration Guide at Sybase Product Manuals at http://www.sybase.com/support/manuals for more advanced topics.
Installing version 15.0.2 over an existing 15.x Adaptive Server Installing version 15.0.2 over an existing 15.x Adaptive Server Determining Adaptive Server version Verify that your current Adaptive Server installation is at version 15.x by running the following query from isql: 1> select @@version 2> go If your server is not running, you can get a version string by running: %SYBASE%\%SYBASE_ASE\bin\sqlsrvr.exe-v If this shows that the Adaptive Server is not at version 15.
CHAPTER 2 Installing Adaptive Server This document may also contain last minute installation information for the 15.0.2 installation. 2 After backing up your databases, shut down Adaptive Server and back up your SYBASE directory. 3 Installing Adaptive Server 15.0.2 overwrites current Adaptive Server software. Prior to installing 15.0.2, make sure that your databases are error-free as described in “Backing up Adaptive Server” on page 36 and that your SYBASE directory is backed up.
Installing version 15.0.2 over an existing 15.x Adaptive Server You can downgrade to earlier 15.x versions of Adaptive Server, but to do so you must take the precautions described in the technical note before using any of the new 15.0.2 features. XML Services in Adaptive Server version 15.0.2 If you are planning on using XML in Adaptive Server version 15.0.2, there are installation issues you must take into consideration.
CH A PTE R 3 Post-Installation Tasks After the installation process, you have a minimally configured Adaptive Server. This chapter describes post-installation tasks to administer Adaptive Server and install stored procedures and sample databases. For more information, see the configuration guide for your platform.
Connecting to Adaptive Server via Sybase Central isql -Usa -P -Sserver_name where server_name is the Adaptive Server name. Warning! The first time you log in to Adaptive Server, use the default “sa” user name and leave the password blank. After you log in for the first time, change the System Administrator’s password. See “Setting the System Administrator password” on page 41. The command prompt is displayed if the login is successful.
CHAPTER 3 5 Post-Installation Tasks Click OK. The Adaptive Server plug-in to Sybase Central does not display all servers listed in the interfaces file. Instead, Sybase Central lists only those servers that you connected to earlier, or those servers that are started as Windows services. To access a new server for the first time, select Tools | Connect to select a server listed in the interfaces file.
Installing sample databases The reports provided by SAMreport belong to three report families: • Summary reports – summarize usage information about each feature used from the license server. • Raw reports – show individual usage detail in textual format. • Server reports – provide details about a given license server. For more information on SAMreport, see Chapter 5, “Using SySAM for Asset Management” in the Sybase Software Asset Management User’s Guide.
CHAPTER 3 Script Description installpix2 Installs the image data that is used with the pubs2 database. Post-Installation Tasks Note The master device size should be at least 30MB to install the full pubs2 database, including the image data. Run the installpix2 script after you run installpubs2.
Installing sample databases From the Adaptive Server scripts directory ($SYBASE/$SYBASE_ASE/scripts), use isql to log in to Adaptive Server and run the script: isql -Usa -P***** -Sserver_name -iscript_name Where: • server_name – represents the destination server for the database • script_name – is the full path to and file name of the script to run For example, to install pubs2 on a server named VIOLIN, enter: isql -Usa -P***** -SVIOLIN \ -i $SYBASE/$SYBASE_ASE/scripts/installpubs2 5 To install the
CHAPTER 3 Post-Installation Tasks 2 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. 3 Make a copy of the original installintpubs script. Be sure you can access this copy, in case you experience problems with the edited script.
Installing sample databases isql -Usa -Ppassword -Sservername -Jeucjis \ -i $SYBASE/$SYBASE_ASE/scripts/eucjis/installjpubs or: isql -Usa -Ppassword -Sservername -Jsjis \ -i $SYBASE/$SYBASE_ASE/scripts/sjis/installjpubs For more information on the -J option in isql, see the Utility Guide. Maintaining the sample databases The sample databases contain a guest user that allows access to the database by any authorized Adaptive Server user.
CH A PTE R 4 Installing Sybase PC-Client Products Adaptive Server also includes PC-Client products, and this chapter describes how to install client products. Topic Overview Before you install the PC-Client products Page 47 48 Installing PC-Client products Installing PowerDesigner, PowerTransfer, and InfoMaker 48 51 Configuring network connections for client products 51 Overview Clients, such as Sybase Central and Open Client, are used to access Adaptive Server.
Before you install the PC-Client products • Extended Architecture (XA) • jConnect for JDBC • ASE ODBC driver by Sybase • ASE OLE DB provider by Sybase • ASE ADO.NET Data provider by Sybase • Language modules • PowerDesigner • PowerTransfer • Infomaker Monitor Client Library requires Open Client/C with the SDK option.
CHAPTER 4 • Install PowerDesigner 12.0 • Install PowerTransfer 15.0 • Install InfoMaker 10.5 • View our (Sybase) Web site • Exit Installing Sybase PC-Client Products Before installing any products, review the readme.txt file, which contains a brief description of each of the products, lists dependencies, and contains any last-minute instructions or changes.
Installing PC-Client products 7 When the Sybase license agreement displays, select a country, click Agreement, then click Next. 8 Enter the directory path and click Next. • If user has Sybase Central previously installed to a directory other than the one specified in step 5 the following pop-up dialogue will be shown: The install program detected a previously installed copy of Sybase Central 4.3 in the following directory '{0}'.
CHAPTER 4 Installing Sybase PC-Client Products If the target directory does not have enough free space, the available space appears in red. You must either click Previous to return to the previous window and change your selections, or Cancel to quit the installer. 12 Click Next. 13 The Installer displays a progress indicator as it installs components. To configure client network connections to Adaptive Server, see the Configuration Guide for your platform.
Configuring network connections for client products For a 64-bit LDAP driver, the format is: [DIRECTORY] ldap=libsybdldap64.dll You can use either a 32-bit or a 64-bit LDAP driver on Windows x64. When an LDAP server is specified in the libtcl.cfg file and the libtcl64.cfg file (when applicable to your platform), the server information is accessible only from the LDAP server. Adaptive Server ignores the interfaces file.
CHAPTER 4 f Installing Sybase PC-Client Products • Select the transport type from the drop-down list. • Enter the host name. • Enter the port number. Click OK twice to exit the dsedit utility. For more information, see the Configuration Guide for your platform. Adding a server to the interfaces file To access a Sybase server through the interfaces file, each server must be included in the interfaces file on the client computer.
Configuring network connections for client products If prompted to start Adaptive Server, click OK. When the traffic light icon representing the server is green, the server is running. Warning! Do not start XP Server from Sybase Central. Adaptive Server starts XP Server automatically when Adaptive Server receives the first request for an extended stored procedure. 5 To disconnect from a server, select Tools | Disconnect. 6 Exit Sybase Central.
CH A PTE R 5 Upgrading Adaptive Server This chapter describes the various steps for upgrading Adaptive Server to version 15.0.2. If you are installing Adaptive Server 15.0.2 on top of an earlier version refer to section Installing version 15.0.2 over an existing 15.x Adaptive Server in Chapter 2, “Installing Adaptive Server”. If you need information on recovering from a failed upgrade refer to the section “Recovering from a failed upgrade” on page 106 in Chapter 7, “Troubleshooting.
Overview of the upgrade process • 12.5.x Note Adaptive Server version 15.0.2 does not support upgrade from Adaptive Server version 12.5.3a. For a server installation 11.5.x and older, Sybase recommends that you upgrade to version 12.5.4, then upgrade to version 15.0.2. You can upgrade Adaptive Server from a 32-bit version to a 64-bit version, but you cannot move from a 64-bit version to a 32-bit version. Likewise, you can upgrade only from an earlier version of Adaptive Server to a more recent version.
CHAPTER 5 c Upgrading Adaptive Server Run the upgrade process. Note Adaptive Server issues advisory warnings when configuration parameters are not set to the default. These do not require any action. The preupgrade and upgrade utilities are internally called by sqlupgrade or sqlupgraderes. Each new version of Adaptive Server contains features that introduce new parameters, commands, reserved words, and so on. For this reason, preupgrade is for preparing the old server for upgrade.
Pre-upgrade tasks Pre-upgrade tasks Note Before you begin the upgrade process, install Adaptive Server 15.0.2 onto your system. To ensure a successful upgrade, review the following pre-upgrade tasks and perform them as necessary. Depending on the old server configuration, you may not need to perform all pre-upgrade tasks. 1 Check system and upgrade requirements. 2 Check RUN_server file location. 3 If you are upgrading Adaptive Server, the previously installed version of the server must be running.
CHAPTER 5 Upgrading Adaptive Server You also can set the OLDSYBASE, OLDSYBASE_ASE, and OLDSYBASE_OCS environment variables to the location of the server you are upgrading, to avoid having to type this path when you run sqlupgrade. • Disable Job Scheduler. For UNIX platforms: • $SYBASE/$SYBASE_OCS/config/libtcl.cfg • $SYBASE/$SYBASE_OCS/config/libtcl64.cfg • $SYBASE/$SYBASE_SYSAM/licenses/license.
Pre-upgrade tasks 4 Verify that you unloaded Adaptive Server 15.0.2 in a different directory than your previous Adaptive Server installation. If you overwrote your previous server installation: 5 a Restore it from your most recent backup. b Reinstall the product files for Adaptive Server in a different directory. c Continue with the upgrade. Verify that your operating system is at the proper version level and has all operating system patches needed for Adaptive Server.
CHAPTER 5 Upgrading Adaptive Server Reserved words Reserved words are pieces of SQL syntax that have special meaning when used as part of a command. Transact-SQL does not allow words that are part of command syntax to be used as identifiers, unless they are enclosed in quotation marks. If you are upgrading Adaptive Server, and the identifiers in your user databases match new reserved words, errors result when you run queries, stored procedures, or applications that use these identifiers.
Pre-upgrade tasks If you use either sqlupgrade or sqlupgraderes, they automatically install new reserved words and sp_checkreswords, which is a stored procedure used to detect and display any identifiers in your existing databases that conflict with reserved words in the new database. You can then run the new version of sp_checkreswords at any time while preforming pre-upgrade tasks.
CHAPTER 5 Upgrading Adaptive Server 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. Preparing the database and devices for the upgrade If you ran the pre-upgrade option in preupgrade, the utility scanned the system catalogs and calculated how much additional space you need to perform the upgrade.
Pre-upgrade tasks 2> go Note The model database cannot be larger than the tempdb. If your changes cause the model database to be larger than the tempdb, then you must first increase the size of tempdb, before increasing the size of the model database. 3 Verify the size of each database. Enter the following, where database_name is the name of the system database you are checking: 1> sp_helpdb database_name 2> go Create a sybsystemdb database In version 11.9.
CHAPTER 5 Upgrading Adaptive Server sybsystemprocs sybprocsdev is the default name for the device-holding database sybsystemprocs. It is frequently referred to as the sybsystemprocs device in Adaptive Server. Verify that the sybsystemprocs database is large enough. For an upgrade, the default size for sybsystemprocs is 124MB, or enough free space to accommodate the existing sybsystemprocs database, and the largest catalog that is to be upgraded, plus an additional 10 percent for logging upgrade changes.
Pre-upgrade tasks To upgrade using sqlupgrade: 1 Make sure your current server is running. 2 Verify that you have performed the tasks mentioned on the window, before beginning the upgrade. 3 Source ASE150.csh before running sqlupgrade. 4 Execute sqlupgrade, by entering at the UNIX prompt: $SYBASE/$SYBASE_ASE/bin/sqlupgrade A sqlupgrade window now displays. 5 The first screen warns you to back up the databases, devices, and so on. Click Next to proceed to the next screen. 6 Click OK.
CHAPTER 5 Upgrading Adaptive Server sqlupgrade displays the Status Output window.View the Status Output window for the completion status and informational messages about the upgrade process. Warning! Do not interrupt the upgrade, and do not try to connect to Adaptive Server or run any stored procedures while the upgrade is in progress. You can also check the progress of the upgrade by viewing the sqlupgrade log in $SYBASE/$SYBASE_ASE/init/logs/sqlupgradeMMDD.NNN.
Pre-upgrade tasks Using sqlupgraderes You can upgrade Adaptive Server in noninteractive mode by using values from a resource file that defines the attributes for the server to be upgraded. To upgrade an Adaptive Server using a resource file, either: 1 Edit the sample resource file included in your Adaptive Server distribution in $SYBASE/$SYBASE_ASE/init/sample_resource_files directory. Use an ASCII text editor to edit the resource file as described in Appendix A, “Alternative Installation Methods.
CHAPTER 5 Upgrading Adaptive Server Table 5-1: Resource file attributes for upgrading Adaptive Server Attribute sybinit.release_directory Default value [other options] $SYBASE [path = _name_of_old_release] sybinit.product sqlsrv.server_name sqlsrv server_name sqlsrv.new_config sqlsrv.sa_login No current_login sqlsrv.sa_password sqlsrv.do_upgrade current_password Yes sqlsrv.
Post-upgrade tasks Run the instmsgs.ebf script You must run the instmsgs.ebf script after you upgrade from a 15.0 Adaptive Server to a 15.0.2 Adaptive Server. Run the instmsgs.ebf script immediately after runnning the installmaster script. If you are a localized customer: • First run the instmsgs.ebf script, and then install any localized language using langinstall, sqlloc, or syconfig. • If you run instmsgs.ebf after installing the 15.0.2 localized message, this script may delete some new messages.
CHAPTER 5 Upgrading Adaptive Server For example, if procedure cache percent is configured as 20 percent of 200MB of memory, then the absolute value of procedure cache percent is 40MB. During the upgrade process, Adaptive Server converts procedure cache percent at 20 percent to procedure cache size at 40MB. If the value for procedure cache size is less than the default value, Adaptive Server sets procedure cache size to the default value.
Post-upgrade tasks In pre-12.5 versions of Adaptive Server, the default data cache available depended on the amount of memory available to Adaptive Server. If the default data cache was set to 2MB, Adaptive Server allocated 2MB to the default data cache. If, after memory was allocated to all user-defined data caches and to the procedure cache, there was more memory available, that memory was allocated to the default data cache.
CHAPTER 5 Upgrading Adaptive Server Reenabling Replication Server If you disabled replication before the upgrade, you must reenable replication. To do so, first remove any older format log records from your database, and then reenable replication. Removing old log records Use the dump tran command to dump the database and transaction logs to remove the older format log records from your database. This prevents Replication Server from accessing the pre-upgrade portion of the transaction logs.
Post-upgrade tasks 6 Resume the DSI connections that were suspended before the upgrade by executing the following Replication Server command for each suspended database: 1> resume connection to dataserver.database 2> go The replication system is now ready for Adaptive Server 12.5.x, and applications can resume. If you installed any Sybase client products, such as Open Client, use the dsedit utility to edit your interfaces file and to specify the servers to which you want to connect.
CHAPTER 5 5 Upgrading Adaptive Server Log in to the Replication Server, and resume the Log Transfer connection for each replicated primary and each replicated RSSD: 1> resume log transfer from server.database 2> go If this is a replicated RSSD, you must log in to the replicate Replication Server. 6 If you are using Rep Agent, log in to the Adaptive Server and restart the Rep Agent: 1> 2> 1> 2> 7 use database go sp_start_rep_agent database go If you are using LTM, restart the LTM.
Upgrading Backup Server, Monitor Server, and XP Server 1> 2> 1> 2> sp_audit "security", "all", "all", "on" go sp_audit "dbcc", "all", "all", "on" go For more information, see the Reference Manual.
CHAPTER 5 Upgrading Adaptive Server XP Server does not have a formal upgrade process. Note Back up all databases, including master, after successfully upgrading Adaptive Server and Backup Server. v Upgrading Backup and Monitor Servers The procedures for upgrading Backup Server and Monitor Server are similar. • If you are upgrading during the initial installation of Adaptive Server 15.0.
Upgrading Job Scheduler Upgrading Job Scheduler After upgrading to the new Adaptive Server, perform the following steps to upgrade Job Scheduler. Note You must have $SYBASE/$SYBASE_OCS/bin directory in $PATH so the isql executable is accessible. v Upgrading Job Scheduler 1 Copy the directory services entry for JSAGENT (or jsagent) from the old server to the new server. 2 Make sure your new server is running. 3 Stop the Job Scheduler. From isql, issue: sybmgmtdb..
CHAPTER 5 Upgrading Adaptive Server go alter database sybmgmtdb LOG on sybmgmtdev=20 go 9 Upgrade the sybmgmtdb. Using isql, run the installjsdb script that is included with this release and save the output to a file: isql -Usa -Psa_password -Sservername -n -i$SYBASE/$SYBASE_ASE/scripts/installjsdb -ooutput_file 10 Enable Job Scheduler to start when Adaptive Server starts. From isql enter the command: sp_configure "enable job scheduler", 1 11 Start Job Scheduler.
Upgrading Job Scheduler 4 If you have modified any of the Sybase-supplied templates stored procedures or XML documents, do not overlay the new templates with your versions. If you do, you will 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 Sybase recommends that if you modify Sybase-supplied templates that you save the changes under new names and in new files.
CHAPTER 5 6 Upgrading Adaptive Server Some Job Scheduler templates were modified to support new 15.0.2 Adaptive Server functionality. The changes are related to new parameters for specifying a partition name or a datachange value for the Adaptive Server command that have added these options. If you have jobs created from any of the enhanced templates, modify the SQL of the jobs for 15.0.2 servers. Note If you have a job scheduled to run on a pre-15.0.2 server and you need it to run on 15.0.
Upgrading Job Scheduler Template multiple Modified file jst_get_freespace,jst_get_usedspace Change description Replace reserved_pgs and data_pgs with reserved_pages and Modify jobs created from this template No impact on job SQL. data_pages 7 Install the Template stored procedures. • Move to the JS template stored procedure directory.
CHAPTER 5 Upgrading Adaptive Server Upgrading high availability Using the following steps to upgrade high availability-enabled Adaptive Server in active-active configuration: 1 Drop the high availability companionship. On the secondary server, use isql: sp_companion , "drop" go 2 Use the cluster system command to stop monitoring resources associated with Adaptive Server on each cluster node.
Upgrading high availability 10 Use the cluster system command to restart monitoring resources associated with Adaptive Server on each cluster node. 11 Re-establish companionship by using isql to issue: sp_companion , configure go If user databases exist on the secondary server, warning message may display on the console. There is no need to take any action. You can safely ignore them.
CHAPTER 5 Upgrading Adaptive Server 3 Follow the upgrade steps provided in “To assist with the upgrade process, Sybase recommends you set the OLDSYBASE, OLDSYBASE_ASE, and OLDSYBASE_OCS environment variables to point to the old installation of Adaptive Server. If you set these environment variable to the old installation of the Adaptive Server, the upgrade utility automatically populates input fields with the correct information as you upgrade.
Migrating from 32-bit to 64-bit versions 3 Create devices and databases to match those in the 32-bit server. Make sure that the sysusages mapping is correct. See document ID #1324 at http://my.sybase.com/detail?id=1324. Note Allow 10 percent additional space for the sybsystemprocs database. Method #2: BCP data out and in 4 Dump the databases on the 32-bit server. 5 Load the databases to the 64-bit server. 6 If you have partitioned tables, update partition statistics.
CHAPTER 5 Upgrading Adaptive Server 5 Copy the 32-bit $SYBASE/$SYBASE_ASE/install/RUN_ 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 Change to the 64-bit $SYBASE directory and source the ASE150.[csh, sh] script (Bourne shell).
Recovering from a failed upgrade isql> dump tran dbname with no_log This frees the log space, and allow the upgrade process to continue. • In some cases, the pre-upgrade space estimations might be insufficient for the data copy phase of upgrade. In this case, you may get an error that there is insufficient space in the system segment for the upgrade. The upgrade process hangs, waiting for space to be provided.
CH A PTE R 6 Troubleshooting SySAM Issues Note If SySAM 2.0 related errors are not addressed in a timely fashion, Adaptive Server may cease to function. For the most up to date information about troubleshooting SySAM, see the SySAM FAQ at http://www.sybase.com/sysam. For the most up-to-date troubleshooting information in this installation guide, go to Product Manuals at http://www.sybase.com/support/manuals/. This section includes information about troubleshooting the most common SySAM 2.
Where to look for SySAM-related errors • If Adaptive Server has started in grace mode – the output from the sp_lmconfig command. • If Adaptive Server does not start – the server’s properties file On UNIX: $SYBASE/ASE-15_0/sysam/.properties On Windows: %SYBASE%\ASE-15_0\sysam\.properties servername must correspond to the name of the Adaptive Server that does not start. • The license files saved in the SYSAM-2_0 licenses directory on the machine running Adaptive Server.
CHAPTER 6 Troubleshooting SySAM Issues If you are using a served license model, the license server’s debug log located in the log directory provides information about any license check-out issues. Troubleshooting SySAM Table 6-1 lists methods for troubleshooting SySAM. Table 6-1: Troubleshooting SySAM Description What to do Cannot find license type during the Adaptive Server installation The Adaptive Server installation program displays only the most commonly used license types.
Troubleshooting SySAM Description What to do The installation program produces a warning about not finding a suitable license If you select a served license model, the install program checks for a license with the selected edition and license type. A warning message is displayed if no suitable license is available. If you are performing a new Adaptive Server installation or upgrading an existing Adaptive Server version 12.5.x or earlier, proceed with the installation.
CHAPTER 6 Troubleshooting SySAM Issues Description What to do The license server does not start The most common cause for the license server failing to start is that there are no served licenses in the server. In order for license server to start, there needs to be at least one served license in the licenses directory.
Troubleshooting SySAM Description What to do Adaptive Server cannot check out a license and starts with graced license instead Execute the sysam diag feature_name command from the SYSAM-2_0 bin directory, where feature_name is the SySAM feature name for Adaptive Server or the optional feature that is in grace mode. The feature name is printed in the Adaptive Server errorlog and in the optional e-mail notifications.
CHAPTER 6 Troubleshooting SySAM Issues Description What to do Adaptive Server cannot checkout a license and starts with graced license instead (continued) If the diag command shows the license for the given feature is available for check-out, the reason that Adaptive Server cannot check-out the license could be: • The product edition or license type does not match the requirement.
SySAM grace mode Description What to do Adaptive Server does not start with the expected edition or license type If the edition and license type configuration parameters are not set, Adaptive Server uses the first available ASE_CORE license. If you have multiple ASE_CORE licenses with different editions and license types, which license is the first available depends on many factors such as license file directory sort order, available licenses on the license server, and so on.
CHAPTER 6 Troubleshooting SySAM Issues SySAM grace period Typically, you get a 30-day grace period to resolve any SySAM-related issues. When a license is awarded under grace, the Adaptive Server errorlog entry and optional e-mail message includes the date and time when the grace period expires. In addition, you can execute sp_lmconfig to determine the expiration date. The Expiry Date column next to any row that shows graced status indicates the date and time the grace period expires.
Enabling and changing e-mail notifications 98 Adaptive Server Enterprise
CH A PTE R 7 Troubleshooting This chapter provides instructions for troubleshooting installation error messages. If this chapter does not describe the error message you are encountering, see the Error Messages and Troubleshooting Guide.
Error log locations Table 7-1: Troubleshooting guidelines for UNIX platforms Problem The installation program cannot start Adaptive Server. Possible cause and solution Failure to start Adaptive Server is generally caused by a lack of available RAM or disk space. Make sure you meet RAM requirements. If you have the required RAM, remove, then reinstall all applications to the hard drive and restart the installation process.
CHAPTER 7 Utility Error log location srvbuild $SYBASE/$SYBASE_ASE/init/logs/srvbuildMMDD.NNN srvbuildres where: Troubleshooting • MM is the month • DD is the date • NNN is a three-digit number identifying the srvbuild session $SYBASE/$SYBASE_ASE/init/logs/sqllocMMDD.NNN sqlloc sqllocres sqlupgrade • $SYBASE/$SYBASE_ASE/init/logs/sqlupgradeMMDD.NNN sqlupgraderes • $SYBASE/$SYBASE_ASE/upgrade/upgrade.
Solutions to common installation problems % ? ? ? % foreach i(*) cat $i | sed -e "s/140/100/g" | sed -e "s/^#D/D/g" | sed -e "s/^#S/S/g" > p mv p $i end The installation utilities will now use approximately 25 percent less window space. Cannot eject the CD from the drive If you cannot eject the CD from the drive: • Check to see whether the CD drive path is the current directory (pwd) in a UNIX terminal window. If it is, change (cd) to another directory.
CHAPTER 7 Troubleshooting xhost: unable to open display "host_name" To correct the problem: 1 Enter the following command at the UNIX prompt of your local machine, where remote_machine is the machine on which you are running the Installer: xhost +remote_machine 2 Restart the Installer.
Solutions to common installation problems Msg 11018, Level 16, State 1: Procedure "xp_cmdshell", Line 2: XP Server must be up for ESP to execute. (return status = -6) Verify that there is an XP Server entry in the Adaptive Server sysservers table. If you created XP Server in a different srvbuild session than Adaptive Server and you did not specify a related Adaptive Server, srvbuild cannot update the sysservers table.
CHAPTER 7 Troubleshooting Recovering from a failed installation If the installation does not succeed, the installation program displays error messages. Review the error messages and your Adaptive Server error log to determine the cause of the installation failure. For default error log locations, see Table 7-3 on page 101.
Solutions to common installation problems 1 From the Upgrade window, select Exit. 2 Examine the log file created in the $SYBASE/$SYBASE_ASE/init/logs directory to find out why Adaptive Server failed the pre-upgrade eligibility test. After you resolve any problems, shut down Adaptive Server and use sqlupgrade to complete the upgrade session. Recovering from a failed upgrade If the upgrade process fails, the installation program displays error messages.
CHAPTER 7 1 Troubleshooting If an individual database fails to upgrade, you can retry that upgrade manually. Begin by correcting the problem that caused the failure. Output from the upgrade utility should identify the problem. The most common cause of failure is running out of some resource: space (either data or log), locks, auxiliary scan descriptors. You can add space to the database using the alter database command.
Solutions to common installation problems while @dbname is not null begin online database @dbname select @dbname = min(name) from master..sysdatabases where name > @dbname end Note There are certain upgrade failures from which the server cannot recover. For example, attempts to upgrade system tables to version 15.0 format are quite sensitive to failures at certain points during the required changes. If you encounter such a failure, restore the failed database from backup.
CHAPTER 7 Troubleshooting If the cause of the failure is unknown If the upgrade process fails again, and you cannot determine the cause of failure, check the error log file to find out when and where the upgrade failed, and contact Sybase Technical Support. By default, the log file is located in $SYBASE/$SYBASE_ASE/install/.log. Upgrading compiled objects with dbcc upgrade_object Adaptive Server version 11.9.3 introduced the process of upgrading compiled objects based on their source text.
Upgrading compiled objects with dbcc upgrade_object 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_hidetext, see the Reference Manual:Procedures.
CHAPTER 7 Troubleshooting Reserved word errors If dbcc upgrade_object finds a reserved word used as an object name in a compiled object, it returns an error, and that object is not upgraded. To fix the error, either manually change the object name or use quotes around the object name, and issue the command set quoted identifiers on. Then drop and re-create the compiled object. For example, suppose you load a database dump from Adaptive Server 11.5 into Adaptive Server 15.
Upgrading compiled objects with dbcc upgrade_object For compiled objects created in version 11.9.2 or later, the upgrade process automatically activates or deactivates quoted identifiers as appropriate. Note Quoted identifiers are not the same as literals enclosed in double quotes. The latter do not require you to perform any special action before the upgrade.
CHAPTER 7 Determining whether select * should be changed in views Troubleshooting If dbcc upgrade_object reports the existence of select * in a view, compare the output of syscolumns for the original view to the output of the table, to determine whether columns have been added to or deleted from the table since the view was created.
Upgrading compiled objects with dbcc upgrade_object • dbid – specifies the database ID. If you do not specify dbid, all compiled objects in the current database are upgraded. • dbname – specifies the database name. If you do not specify dbname, all compiled objects in the current database are upgraded. • compiled_object_name – is the name of a specific compiled object you want to upgrade.
CHAPTER 7 Troubleshooting Example 2 Upgrades all stored procedures in the listdb database. Single quotes are used around procedure because set quoted identifiers is on: dbcc upgrade_object(listdb, 'procedure') Example 3 Upgrades all rules and check constraints in the listdb database. Double quotes are used around rule because set quoted identifiers is off. dbcc upgrade_object(listdb, "rule") Example 4 Upgrades all stored procedures named list_proc in the listdb database.
Upgrading compiled objects with dbcc upgrade_object Error reporting To send all the output from dbcc upgrade_object to the window, a System Administrator can execute dbcc traceon(3604). Sybase recommends that you use this command if you think the output of error messages might overflow the error log. Using database dumps in upgrades Upgrading using dump and load You can load pre-12.5 database dumps and transaction logs and upgrade the databases.
CHAPTER 7 Troubleshooting Determining whether a compiled object has been upgraded To determine whether a compiled object has been upgraded, do one of the following: Installation Guide • Look at the sysprocedures.version column. If the object was upgraded, this column will contain the number 12500. • If you are upgrading to a 64-bit pointer size in the same version, look at the sysprocedures.status column.
Upgrading compiled objects with dbcc upgrade_object 118 Adaptive Server Enterprise
CH A PTE R 8 Removing Adaptive Server Only actions performed by the Installer are removed during an uninstallation process. This means that files or registry entries created after installation are not removed by the uninstaller and must be removed by the customer after the uninstall is completed. Where possible these actions are identified in this chapter. Heading Uninstalling Adaptive Server 15.0.2 Page 119 Removing an existing Adaptive Server 120 Uninstalling Adaptive Server 15.0.
Removing an existing Adaptive Server 4 The component selection window displays with everything selected. Deselect components by clicking the check box and erasing the check mark. Click Next to continue. Note If there is SySAM Network License Server installed on this machine, it may be used by other Sybase products. Uncheck this component unless you know no one is using this License Server. 5 A summary window displays what is about to be uninstalled. Click Next to continue.
A P PE N DI X A Alternative Installation Methods Topic Installation on consoles (non-GUI mode) Silent installation Page 121 122 Configuration using resource files 124 Installation on consoles (non-GUI mode) In cases where there is no graphics display device available, or for some other reason you wish to run the installer without the graphical user interface (GUI), the Installer can be launched in console or non-GUI mode.
Silent installation Silent installation A silent installation (sometimes referred to as an unattended install) is done by running the Installer and providing a response file that contains answers to all of the Installer’s questions. There are two methods of generating a response file for the Installer. The first method is to run the Installer in GUI mode and record all of the responses into a response file. This response file then be edited with an editor to customize the responses if needed.
APPENDIX A Alternative Installation Methods Except for the absence of the GUI screens all actions of the Installer are the same and the result of an installation in silent mode is exactly the same as one done in GUI mode with the same responses. Note The value for -options, -options-template, and -options-record must specify an absolute path. Installation in silent mode can fail when a response is required from the user.
Configuration using resource files Configuration using resource files You can create an Adaptive Server or Backup Server, using values specified in a resource file that defines the attributes for the server. Resource files are ASCII format template files that contain configuration variables. To use the template files, edit the resource file, replace variables with desired values, and execute the srvbuildres utility. The srvbuildres utility uses the variables to create servers.
APPENDIX A Alternative Installation Methods • To create a server with a different name, change the Adaptive Server name and use the new name with the “_BK” extensions for Backup Server. For example, the Backup Server for PIANO should be PIANO_BK. • The minimum master device size must be: • 2K page size – 24MB • 4K page size – 45MB • 8K page size – 89MB • 16K page size – 177MB • The system procedure device and sybsystemprocs database sizes must be at least 120MB.
Configuration using resource files Table A-1: Resource file attributes for Adaptive Server Attribute sybinit.release_directory sybinit.product sqlsrv.server_name sqlsrv.new_config sqlsrv.do_add_server (to interfaces file) sqlsrv.network_protocol_list sqlsrv.network_hostname_list sqlsrv.network_port_list sqlsrv.master_device_physical_name sqlsrv.master_device_size sqlsrv.master_database_size sqlsrv.errorlog sqlsrv.do_upgrade sqlsrv.sybsystemprocs_device_physical_name sqlsrv.
APPENDIX A Alternative Installation Methods Table A-2: Resource file attributes for Backup Server Attribute sybinit.release_directory Default value [other options] $SYBASE bsrv server_name_back sybinit.product bsrv.server_name bsrv.do_add_backup_server (to interfaces file) bsrv.network_protocol_list bserv.network_hostname_list bsrv.
Configuration using resource files Using srvbuildres Note When building a new sever with srvbuild or srvbuildres, configuration parameters can be set in the configuration file in $SYBASE.This configuration file is used to start the new server. Source SYBASE.csh before running srvbuildres.
A P PE N DI X B Upgrading Servers with Replicated Databases Topic Introduction Suspending transaction processing and replication activities Page 129 130 Draining the transaction logs for primary databases Draining the RSSD transaction log 131 133 Disabling the secondary truncation point 134 Introduction After you have upgraded, you will no longer be able to scan any part of the transaction log that existed before the upgrade, so you must follow the following process if your server contains replicat
Suspending transaction processing and replication activities • Disabling the log truncation point. After upgrading to version 15.0, complete the post-upgrade tasks to re-enable database replications functions. For more information, see the Replication Server Reference Manual and the Replication Server System Administration Guide. Warning! As a safeguard, perform a dump database and a dump transaction before executing the procedures in the following sections.
APPENDIX B Upgrading Servers with Replicated Databases The status of all existing routes should be “Active.” If any routes are not active, resolve them before continuing. See the Replication Server documentation for help in diagnosing and fixing the problem with the route, and then go to step 3. 3 Shut down all applications that use the databases you are upgrading.
Draining the transaction logs for primary databases 5 Use isql to update one row in a single replicated table in the primary database: 1> update table set column = column 2> where key = unique_value 3> go The update command helps track whether all modifications to the replicated database have been sent to the Replication Server. Note In Replication Server 10.1 or later, choose a table that does not use the replicate minimal columns clause, or use the alter replication definition command...
APPENDIX B Upgrading Servers with Replicated Databases 2> go 12 If you are using LTM, shut down the LTM. After draining the transaction logs, do not allow any other activity in the databases. If activity does occur, you will need to redrain the logs. Draining the RSSD transaction log If the Replication Server has routes to other Replication Servers, you must ensure that Replication Server processes all transactions in the RSSD transaction log before you upgrade the databases.
Disabling the secondary truncation point 3 Log in to the replicate Replication Server and suspend the Log Transfer connection from the primary RSSD: 1> suspend log transfer from server.database 2> go 4 If you are using Rep Agent, log in to the Adaptive Server, and stop the Rep Agent: 1> use database 2> go 1> sp_stop_rep_agent database 2> go 5 If you are using LTM, shut down the LTM.
A P PE N DI X C Using sybsystemprocs Topic Introduction Increasing the size of the sybsystemprocs database Page 135 136 Increasing device and database capacity for system procedures 137 Introduction Note sysprocsdev is the default system name for this device. However, it is frequently referred to as the sybsystemprocs device, as in the Adaptive Server attribute window, since it stores the sybsystemprocs database. Verify that the sybsystemprocs database is large enough.
Increasing the size of the sybsystemprocs database 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, you must increase the size of sysprocdev.
APPENDIX C Using sybsystemprocs If there is space available on another device, you can expand sybsystemprocs to a second device, or initialize another device that is large enough. For instructions on creating a larger sybsystemprocs device, see “Increasing device and database capacity for system procedures” on page 137.
Increasing device and database capacity for system procedures and not exists (select vstart from sysusages u2 where u2.dbid != u.dbid and u2.vstart between d.low and d.high) where: • d.name – is the list of devices to remove from sysdevices • d.phyname – is the list of files to remove from your computer The “not exists” clause in this query excludes any devices that are used both by sybsystemprocs and other databases. Note the names of the devices; you will need them in the steps.
APPENDIX C Using sybsystemprocs If any of the named devices are OS files rather than raw partitions, use the appropriate OS commands to remove those files. 4 Remove all files for the list of d.phyname returned in step 1. Note File names cannot be complete path names. If they are relative paths, they are relative to the directory from which your server was started.
Increasing device and database capacity for system procedures 140 Adaptive Server Enterprise
Index A Adaptive Server described 8 installing multiple 124 installing via resource file 124 language, changing 35 more information about 35 RAM required by 14 stopping 104 System Administrator 41 verifying environment for upgrade 59 Administrator Sybase System 22 alter database command 135 applications changing after renaming objects 61 testing current 60 auditing feature 75 B Backup Server installing via resource file 124 more information about 35 batch installation of servers 124 current applications
Index H hardware requirements M 7 Monitor Server more information about I identifiers conflicting with reserved words 61 installation directory for unloading products 22 installing Open Client/C 11.9.
Index renaming objects 61 replicated databases checking for 130 restoring 74 Replication Server 73 draining logs for Adaptive Server reserved words checking for conflicts 62 using quoted identifiers 62 resource files 68, 124 installation using 124 74, 131 S xd2 saxd3 user 41 sample databases 42, 46 scripts installintpubs 45 installjpubs 45 installpix 44 installpubs2 43 installpubs3 43 servers including in sql.
Index 144 Adaptive Server Enterprise
