Installation Guide Adaptive Server® Enterprise 15.0.
DOCUMENT ID: 35890-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 Backing up Adaptive Server .................................................... Installing the Adaptive Server version 15.0.2 binary overlay... Backward compatibility with previous Adaptive Server 15.x versions ............................................................................ XML Services in Adaptive Server version 15.0.2 .................... 36 37 38 38 CHAPTER 3 Post-Installation Tasks..................................................................
Contents CHAPTER 6 Run the instmsgs.ebf script ..................................................... Restoring functionality in Adaptive Server............................... Reenabling Replication Server................................................ Reenabling auditing................................................................. Shutting down SySAM servers................................................ Upgrading Backup Server, Monitor Server, and XP Server ........... Upgrading Job Scheduler......
Contents AP PE ND IX B AP PE ND IX C Silent installation .......................................................................... Configuration using resource files ................................................ Configuring from a resource file ............................................ Resource file variables .......................................................... Running the sybatch utility ....................................................
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.
Table 1: SQL syntax conventions Key command variable { } [ ] ( ) | , Accessibility features Definition Command names, command option names, utility names, utility flags, and other keywords are in san-serif font. Variables, or words that stand for values that you fill in, are in italic. Curly braces indicate that you choose at least one of the enclosed options. Do not include braces in your option. Brackets mean choosing one or more of the enclosed options is optional.
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 8 PC-Client product descriptions and directory layout 11 This installation guide contains information about how to install and configure Adaptive Server version 15.0.2.
Product licensing with SySAM 2.0 • For information about uninstalling Adaptive Server, see Chapter 8, “Removing Adaptive Server.” Warning! Before you run Adaptive Server version 15.0 on 32-bit Windows platforms, you must either: • Install Microsoft Visual C++ 6.0, or • Download a patch called vcredist.exe referred to in Microsoft Knowledge Base article # 259403. Find the patch at the Microsoft Web site at http://support.microsoft.com/default.aspx?scid=http://support.microsoft.
CHAPTER 1 Overview The Adaptive Server Installation Guide (this document) has the following information about SySAM-related tasks: • Installation instructions are described in “Installing components with the Installer in GUI mode” on page 27. • If you have problems, see Chapter 6, “Troubleshooting SySAM Issues.” • For information about using SySAM for asset management, see “The SAMreport” on page 43. Product components Adaptive Server Enterprise is based on the client/server model.
Product components All server processes share two distinct areas of shared memory: a kernel area and a DBMS area. The kernel area contains data structures that relate to task management and operating system services, while the DBMS component contains caches of database buffers, object descriptors, and other resources used by the DBMS component of the server process.
CHAPTER 1 Overview Stored procedures Stored procedures encapsulate a series of SQL commands that the server can execute as a single command. System stored procedures (SSPs) are created when the server is installed. The client A client uses functions provided by the CT-Library (CT-Lib) and Common Library (CS-Lib) APIs to establish a connection to the server, submit requests to the server, and receive results back from the server.
Adaptive Server editions • Small Business Edition – has some limit on scalability, and can run a limited set of options that can be purchased separately. • Developer Edition – has a limit on scalability and includes many of the options. Sybase also offers a series of options that you must purchase separately. Some of these options are intended for an enterprise-level site, and are not available in the Small Business Edition.
CHAPTER 1 Overview Developer Edition The Developer Edition (DE) is a competitively-priced version of Adaptive Server that developers can use to create applications in their development environment. The Developer Edition includes a full set of Adaptive Server Enterprise features and options (that is, DTM, High Availability, and so on), and allows for the following configuration: • Number of engines – 1. • Number of connections – 25.
Product descriptions and directory layout Note For more information about Adaptive Server specifications see Chapter 1, “Introduction” in the Configuration Guide for your platform. Product descriptions and directory layout The Adaptive Server installation installs a wide array of software products into the SYBASE directory. Table 1-3 provides a brief description of the server products installed, and the top-level directory structure. Note Starting with ASE 15.0.
CHAPTER 1 Product Description Software Developer Kit (SDK) Installed into the OCS-15_0 directory. Overview • 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. shared – on UNIX platforms • ADO.
Product descriptions and directory layout Product Description Interactive SQL Unified Agent 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. 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.
CHAPTER 1 Overview Installing ODBC driver from ASE 15.x or SDK 15.x on top of an IQ 12.6 installation might produce a warning. You can ignore this warning. The ODBC driver will be functional at the end of the install. PC-Client product descriptions and directory layout The following products are installed as Adaptive Server PC-Client products. In addition to these products, there are several separately installed products listed in the following sections.
PC-Client product descriptions and directory layout Product Description Language Modules Character Sets Installed into the locales directory. Provides system messages and date/time formats. Installed into the charsets directory. Provides character sets available for use with Adaptive Server. Installed into the jConnect-6_0 directory. Provides a Java Database Connectivity (JDBC) driver for Adaptive Server. This is a Sybase Central plug-in that manages the Unified Agent.
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 15 Pre-installation tasks for Adaptive Server Installing server components 23 27 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 Operating system Hardware Supported protocols Windows XP Professional SP1 or higher • Intel Pentium III 600 MHz or higher • TCP • AMD Athlon 1 GHz or higher • IPX/SPX • Intel Xeon EM64T • Named pipes (not supported for LDAP server connections • TCP • AMD Opteron • IPX/SPX Windows 2003 Standard, Enterprise, and Datacenter Editions, SP1 • Named pipes (not supported for LDAP server connections Windows x64 Table 2-5: Disk space requirements for Windows platf
Pre-installation tasks for SySAM • For information about creating a new license server before installing Adaptive Server, see “Installing a new license server” on page 21. Note There can be only one instance of a SySAM license server running on a given machine. If you want to setup a SySAM 2.0 license server on a machine that is already running a SySAM 1.0 license server, the old license server must be migrated to 2.0. A migrated license server can serve licenses for both SySAM 1.0 and SySAM 2.
CHAPTER 2 1 Installing Adaptive Server 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.
Pre-installation tasks for SySAM 778DA450 or #2005771344 on HP-UX PA-RISC platforms, or ID_STRING=9c766319-db72-d411-af62-0060b05e4c05 on HP-UX Itanium 64-bit. 00B0A9DF9A32 on Windows 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.
CHAPTER 2 Installing Adaptive Server 6 Once you’ve determined the license you wish to generate, select it via the Generate radio button on the left side of the screen. Scroll to the bottom of the page, and click Select to Generate. 7 Step one of the SySAM license generation wizard asks you to choose between a served license and an unserved license.
Pre-installation tasks for SySAM d You should have gotten your server host ID before you began the process of generating your licenses. For information about how to get the host ID, see “Getting your host ID” on page 17. You have the option to specify redundant server information if you choose to configure your servers for three-server redundancy. 4 Click Generate. 5 Once you have generated the license, you can: 6 a Download the license file by clicking the Download License File button.
CHAPTER 2 6 Installing Adaptive Server • Download the license file by clicking the Download License File button. • Print a paper copy of the license by clicking the Print Friendly button. • Return to the license information page to generate additional licenses. 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.
Pre-installation tasks for SySAM e Enter or select the destination directory. f Select the Custom installation. g Select only “SySAM License Server” for installation. h Deselect other components, to install the license server only. i Click OK for the installer to install the license server. Note The license server cannot be started until there is at least one valid served license installed in the licenses directory.
CHAPTER 2 Installing Adaptive Server > sysam start Starting the SYSAM service The SYSAM service is starting. The SYSAM service was started successfully. lmutil - Copyright (c) 1989-2006 Macrovision Europe Ltd. and/or Macrovision Corporation. All Rights Reserved. Flexible License Manager status on Wed 5/24/2006 15:04 License server status: 27000@mysysamserver License file(s) on keyserver: /opt/sybase/SYSAM_0/licenses/mysysamserver_60302031 5.
Pre-installation tasks for Adaptive Server 4 Review the SySAM procedures and plan your client/server configuration using the configuration guide for your platform. 5 Create a “sybase” account on your system to perform all installation tasks. The “sybase” user must have permission privileges from the top (or root) of the disk partition or operating system directory down to the specific physical device or operating system file. 6 Log in to the machine as the “sybase” user.
CHAPTER 2 • Installing Adaptive Server Severity level of an event that will trigger mail. Your choices are: • None • Informational • Warning • Error 10 Verify that the operating system meets the version-level, RAM, and network protocol requirements for your platform. 11 Adjust the operating system shared memory parameter.
Pre-installation tasks for Adaptive Server Adaptive Server may allocate shared memory segments after start-up if any reconfiguration through sp_configure requires additional memory. You may need to account for these additional segments. Allocate the maximum memory you will make available to Adaptive Server, by using the allocate max shared memory configuration parameter. See the System Administration Guide for more information.
CHAPTER 2 Installing Adaptive Server Installing server components Follow the instructions in this section to install Adaptive Server, Backup Server, and Monitor Server. Note Adaptive Server Enterprise 15.0.2 includes new major versions of Adaptive Server and many of the supporting components. Installing Adaptive Server version 15.0.2 into the same directory with existing products should not impact the existing products. However, installing other products on top of Adaptive Server version 15.0.
Installing server components At the end of the installation, you can verify the product installation. You may need to perform additional configuration procedures before you can use some products. Note As part of the installation, the Installer sets most of the environment variables in %SYBASE%\ASE150.bat. If you need to run any Sybase Application from command prompt you must execute this file first. To install server components: 1 Stop and shut down all programs before running the installer.
CHAPTER 2 Installing Adaptive Server installing Sybase Central and Adaptive Server plugin in? If you choose “no” to above question, the following pop-up dialogue will be shown. You have chosen to install Sybase Central in a new location. Once the installation is complete you will no longer be able to access plug-ins previously registered. In order to access these plug-ins you will need to manually re-register the previously installed plug-ins.
Installing server components 12 The Sybase Software Asset Management License Server screen allows you to designate where Adaptive Server will find its licenses. Where you choose to store your license depends upon whether you have selected a served or unserved license model. Note For information about served and unserved licenses, and about choosing the best license server for your environment, seec Chapter 2, “Choosing a License Model” of the Sybase Software Asset Management User’s Guide.
CHAPTER 2 • Small Business Edition • Developers Edition • Express Edition Installing Adaptive Server Note You must select only the Adaptive Server edition for which you have a license. For more information about troubleshooting license type and edition problems, see Chapter 6, “Troubleshooting SySAM Issues.” 15 If you are installing Enterprise Edition or Small Business Edition, you must also enter the License Type under which Adaptive Server is licensed.
Installing server components • Monitor Server – _MS • XP Server – _XP • Job Scheduler Agent – _JSAGENT If you configure the servers with default values, the Configure Server Attributes Summary window displays next.
CHAPTER 2 • Installing Adaptive Server Master database size (MB). The minimum master database sizes are: • 2K page size – 13MB • 4K page size – 26MB • 8K page size – 52MB • 16K page size – 104MB • System procedure device • System procedure device and database minimum size are 124MB.
Installing server components Once you have entered the appropriate information, click Next to record the information. 22 The Custom Configure New Job Scheduler Input window prompts you to enter Job Scheduler information: • Agent name • Port number • Management device • Management device size • Management database size Once you have entered the appropriate information, click Next to record the information.
CHAPTER 2 Installing Adaptive Server Select the Enable box to enable a login module. To order the modules according to priority, select the module, and click Move up or Move down. 26 The Configure New Servers Summary window displays a summary of the values that are used to configure the servers. These values are either the default or custom values. After verifying the information, click Next, and the Installer proceeds with the server configuration.
Installing version 15.0.2 over an existing 15.x Adaptive Server Unified Agent Unified Agent and Agent Management Console – Describes the Unified Agent, which provides runtime services to manage, monitor and control distributed Sybase resources. 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.
CHAPTER 2 Installing Adaptive Server Installing the Adaptive Server version 15.0.2 binary overlay 1 Read “Special Installation Instructions” in the release bulletin for the latest information that may affect specific 15.0.2 configurations. 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.
Installing version 15.0.2 over an existing 15.x Adaptive Server Backward compatibility with previous Adaptive Server 15.x versions Before using the new Adaptive Server 15.0.2 features, read “Adaptive Server 15.0.2 Backward Compatibility,” the Sybase Web site at http://www.sybase.com/support/techdocs. 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.
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.
Verifying that servers are running 2 Identify the drives and folders where the Adaptive Server software is installed, and identify Adaptive Server’s disk devices. Use the Windows command line tool cacls or Windows Explorer to set access permissions on the identified drives and folders. For detailed instructions on the use of cacls or Windows Explorer, see your Windows documentation or your Windows Operating System administrator.
CHAPTER 3 Post-Installation Tasks The Status column indicates if it is started. If it is not, select the server, then click Start. Verifying that you can connect to servers Use isql to perform a quick test. Source ASE150.[csh, sh]. Then, use isql to connect to servers: 1 At the command prompt, enter: isql -Usa -P -Sserver_name where server_name is the Adaptive Server name.
Connecting to Adaptive Server via Sybase Central Connecting to Adaptive Server via Sybase Central Sybase Central provides a graphical user interface where you can perform Adaptive Server administrative tasks. The Sybase Central interface provides a hierarchical list of servers in the left pane and a list of details for the selected server in the right pane. To select a server, click on it in the left pane. 1 From the Windows task-bar, select Start | Programs | Sybase | Sybase Central v4.3.
CHAPTER 3 Post-Installation Tasks The System Administrator should log in to the new Adaptive Server as “sa” and set a password using sp_password: %SYBASE%\%SYBASE_OCS%\bin\isql -Usa -P -Sserver-name 1> sp_password null, new_password 2> go where “null” is the default password and new_password is the password that you are assigning to the “sa” account. If Job Scheduler was configured to use the sa account an additional step is necessary whenever the sa password is changed.
Installing sample databases Installing sample databases This section describes how to install the U.S. English and international language sample databases. For installation instructions specific to each sample database, see the following sections: • “Running the database scripts” on page 45 • “Installing the interpubs database” on page 46 • “Installing the jpubs database” on page 47 The sample databases contain information about a fictitious business.
CHAPTER 3 Post-Installation Tasks If you have not used sp_diskdefault to change the status of the master device or to specify another default device, the scripts install the sample databases on the master device. Sybase does not recommend this configuration because it uses valuable space that is best used for system tables. Each sample database requires 3MB on a 2K server, and multiples of 3MB on a 4K, 6K, 8K, and 16K server on your database device.
Installing sample databases -Sservername -i %SYBASE%\%SYBASE_ASE%\scripts\instpix2 Note The image data requires a fair amount of space—there are six pictures, two each in the PICT, TIFF, and Sun raster file formats. Run instpix2 script only to use or test the image datatype. Sybase does not supply any tools for displaying image data. You must use appropriate window graphics tools to display the images after you have extracted them from the database.
CHAPTER 3 Post-Installation Tasks For more information on the -J option in isql, see the Utility Guide. jpubs database If you installed the Japanese Language Module with your Adaptive Server, the scripts file contains the installjpubs script for installing the jpubs database. jpubs is a database similar to pubs2 that contains Japanese data. installjpubs uses the EUC-JIS (eucjis), UTF-8 (utf8), or the Shift-JIS (sjis) character sets.
Installing sample databases Maintaining the sample databases The sample databases contain a guest user that allows access to the database by any authorized Adaptive Server user. The guest user has a wide range of privileges, including permissions to select, insert, update, and delete user tables. For more information about the guest user and a list of guest permissions, see the System Administration Guide. Note Sybase recommends that you remove the guest user from user databases in production systems.
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 49 50 Installing PC-Client products Installing PowerDesigner, PowerTransfer, and InfoMaker 50 53 Configuring network connections for client products 54 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 PC-Client Components are provided so they can be installed on client computers. You may install PowerDesigner, PowerTransfer, and Infomaker on the same computer as Adaptive Server. 1 Verify that your computer has sufficient disk space for each product. 2 If you are unloading components, log in using an account with administrator privileges. 3 Close any open applications or utilities to free memory and system resources. 4 Insert the PC-Client CD in the CD drive.
CHAPTER 4 9 Installing Sybase PC-Client Products Select the type of installation to be performed. • Typical Install – installs the default components that most users need. • Full Install – installs every component on the CD. • Customized Install – allows you to select the components to install. Certain components are automatically installed if they are required to run other selected components.
Configuring network connections for client products Configuring network connections for client products Adaptive Server communicates with other Adaptive Servers, Open Server applications (such as Backup Server), and client software on your network. Clients can talk to one or more servers, and servers can communicate with other servers by remote procedure calls. For Sybase products to interact with one another, each product must know where the others reside on the network.
CHAPTER 4 Installing Sybase PC-Client Products • Remove the semicolon (;) comment markers from the beginning of the LDAP URL lines in the libtcl.cfg file under the [DIRECTORY] entry. • Add the LDAP URL under the [DIRECTORY] entry. See the Configuration Guide for supported LDAP URL values. Warning! You must enter the LDAP URL on a single line. ldap=libsybdldap.dll ldap://host:port/ditbase??scope?? bindname=username password For example: [DIRECTORY] ldap=libsybdldap.
Configuring network connections for client products • e f HA server name – optional. This is the name of the highavailability failover server, if you have one. Click Add New Network Transport. • 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.
CHAPTER 4 8 Installing Sybase PC-Client Products In the Network Address box, you can enter either the server name or the IP address, along with the server port number. For example: machine_name, 4100 where machine_name is the name of the computer, and 4100 is the port number the server is using to “listen” for clients.
Configuring network connections for client products • Historical Server User’s Guide Testing the Sybase Central installation After you install Adaptive Server, Sybase Central, and the Java Runtime Environment, test the installation and network connections: 1 Select Start | Programs | Sybase | Sybase Central v4.3 from the Windows task-bar to start Sybase Central. 2 Select Tools | Connect from the Sybase Central menu bar to activate a Sybase Adaptive Server login window.
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 Overview of the upgrade process You can upgrade to Adaptive Server 15.0.2 from any of these versions: • 11.9.2.6 and later • 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.
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 syconfig.exe or sybatch.exe. 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. syconfig.
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 variable to the location of the server you are upgrading, to avoid having to type this path when you run syconfig.exe. • Disable Job Scheduler. For Windows platforms you must specify the location in detail: a Copy %OLDSYBASE%\%OLDSYBASE_OCS\ini\libtcl.cfg to %SYBASE%\%SYBASE_OCS\ini\libtcl.cfg.
Pre-upgrade tasks Noting server and device names and locations By default, the master (master.dat) and system procedures device (sybsytemprocs.dat) files are installed in the %SYBASE%\data directory. The device file names can be different from their device names. Be sure that the directory to which your TEMP environment variable points exists. The installation program uses the directory to write files temporarily during the installation, which it locates via the TEMP environment variable.
CHAPTER 5 Upgrading Adaptive Server As part of the pre-upgrade process, syconfig.exe or sybatch.exe can perform the reserved word check for you. See the Reference Manual for a complete list of reserved words. Note If you change an object name, change applications and stored procedures that refer to that object. Running a reserved word check The sp_checkreswords system procedure detects and displays any identifiers in your existing databases that conflict with reserved words.
Pre-upgrade tasks Run sp_checkreswords in master and in each user database to display the names and locations of conflicting identifiers. For more information about sp_rename and sp_checkreswords and methods for avoiding reserved word conflicts, see the Reference Manual. Using quoted identifiers You can enclose the identifiers that are reserved words in double quotation marks and invoke the quoted_identifier option of the set command in procedures and queries that include the reserved words.
CHAPTER 5 1 Upgrading Adaptive Server In isql, use alter database to increase the size of the master database. For example: 1> 2> 1> 2> use master go alter database master on master=x go This example increases the size of the master database; x is the number of megabytes of space added to the existing database size. 2 Repeat this step to increase the size of each of the tempdb and the model databases.
Upgrading to Adaptive Server 15.0.2 If you do not have a sybsystemdb database If you do not have a sybsystemdb, and will not be using two-phase commit or DTM applications, create a sybsystemdb with a minimum of 4MB. If you will be using two-phase commit or DTM, you can either: • Create a minimum-sized sybsystemdb for upgrade and expand it later, or • Create a sybsystemdb of 5 to 20MB, depending on your expected usage.
CHAPTER 5 Upgrading Adaptive Server Set the OLDSYBASE_ASE variable to the SYBASE_ASE appropriate to your older server. If you are upgrading from 12.0 for example, it should be ASE-12_0. If your preupgrade version is earlier than 12.0, specify it as null: set OLDSYBASE_ASE="" This is required if you are using sybatch.exe to perform your upgrade. Install the new Adaptive Server into the same directory as the Adaptive Server you are upgrading.
Upgrading to Adaptive Server 15.0.2 6 In the Password window, enter the administrator login name and password. 7 Choose Continue. 8 If Adaptive Server is not running, the upgrade program starts it for you automatically. Before making any changes to the existing Adaptive Server databases, the Installer states: You are advised to back up your databases before upgrading.
CHAPTER 5 Upgrading Adaptive Server After Adaptive Server starts, a green light appears next to the server name. 3 When prompted, log in as a System Administrator. Your user ID appears in parentheses next to the server name. 4 Connect to each server listed to verify the installation. 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.
Post-upgrade tasks Restoring functionality in Adaptive Server To reset or enable options or functionality you had to change before the upgrade: 1 Reset the configuration parameters. If you changed any configuration parameters before upgrading, use sp_configure to set them back to their previous values. 2 Use sp_dboption to reset any database options you disabled before upgrading.
CHAPTER 5 5 Upgrading Adaptive Server Check the procedure cache requirements. Stored procedures, triggers, and other compiled objects require more memory to run than older versions. The memory required to run a stored procedure increased by 20 percent between versions 10.x and 11.5. Adaptive Server 12.5.x needs approximately 4 percent more procedure cache than version 11.5 for the server to maintain the same performance. You may increase the procedure cache size during runtime, using sp_configure.
Post-upgrade tasks In pre-12.5 Adaptive Server, it meant all the memory left after allocating memory for other configurations, procedures, and user-defined named caches. In Adaptive Server 12.5.x and later, it means a default value of 8MB. During the upgrade process, Adaptive Server ensures that the default data cache size remains the same. Therefore, during the pre-upgrade process, the size of the default data cache is obtained and written to the configuration file as an absolute value, not as “DEFAULT”.
CHAPTER 5 Upgrading Adaptive Server 2> go Reenabling replication Follow the steps in this section to reenable replication after upgrading the primary databases and primary RSSDs. For each primary database and RSSD: 1 Start Adaptive Server if it is not already running. 2 Log in to the server.
Post-upgrade tasks Restoring replication after upgrade Restore the replication functionality: 1 Log in to the RSSD for each replicated primary, and for each replicated RSSD, and issue: 1> use RSSD_name 2> go 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.
CHAPTER 5 Upgrading Adaptive Server Reenabling auditing Reenable all auditing options for stored procedures using the audit options you recorded during pre-upgrade. Reenter the audit options using sp_audit. For example, if you had enabled stored procedure auditing for sp_addlogin stored procedure in your server before upgrade, run the following sp_audit command to reenable auditing on sp_addlogin: sp_audit "exec_procedure", "all", "sp_addlogin", "on" Adaptive Server 12.5.
Upgrading Backup Server, Monitor Server, and XP Server alter table MyPre15SysAuditHistoryTable add nodeid tinyint NULL See the Reference Manual for system tables sysaudits01 through sysaudits08 for further details about the sysaudits tables. Shutting down SySAM servers Shut down the old SySAM servers if they are no longer used by earlier versions of Adaptive Servers. Upgrading Backup Server, Monitor Server, and XP Server Before you can upgrade Backup or Monitor Server, you must upgrade Adaptive Server.
CHAPTER 5 Upgrading Adaptive Server 7 Back up all existing databases before upgrading. Once you have done so, select Yes. 8 When the upgrade is complete, the syconfig utility displays the message, “Upgrade completed successfully.” Select OK. Repeat this procedure to upgrade Monitor Server.
Upgrading Job Scheduler There is no need to specify any parameters. 6 Restart Adaptive Server. 7 If the sybmgmtdev device is less than 100MB, change the device to be a minimum of 100MB. From isql enter the following, where nn.nM is the number of megabytes needed to get to 100 MB: use master go disk resize name = 'sybmgmtdev' , size = 'nn.nM' go 8 Optionally, add more log space. On some 64-bit platforms more space is need for the sybmgmtdb log.
CHAPTER 5 v Upgrading Adaptive Server Upgrading Job Scheduler templates 1 Disable Job Scheduler before ugrading Job Scheduler templates. 2 Update any environment variables, scripts, or applications that refer to the Job Scheduler directory path. The Job Scheduler directory has been renamed and moved beneath the ASE-15_0 directory. New location is $SYBASE/$SYBASE_ASE/jobscheduler. Directories below jobscheduler remain the same.
Upgrading Job Scheduler Template rebuild indexes Change description Changed the datatype for the @dump_flag parameter from varchar(5) to int Changed the datatype for the @dump_flag parameter from varchar(5) to int Modify jobs created from this template Required, modify job SQL to change @dump_flag to int datatype. Required, modify job SQL to change @dump_flag to int datatype. Required, modify job SQL to change @dump_flag to int datatype. Required, modify job SQL to change @resume_flag to int datatype.
CHAPTER 5 Template Modified file SybUpdateStatsTemplate.xml update statistics jst_update_statistics rebuild indexes SybRebuildIndexTemplate.xml jst_reorg_rebuild_indexes reclaim indexes SybReclaimIndexTemplate.xml jst_reclaim_index_space SybReclaimTableTemplate.
Upgrading high availability Use “en” for the language_code or you may omit the parameter completely as “en” is the default. Note Template XML should be upgraded on all Job Scheduler servers upgraded to Adaptive Server version 15.0.1. Do not install them on pre-15.0.1 servers or servers where Job Scheduler is not installed. Upgrading high availability Using the following steps to upgrade high availability-enabled Adaptive Server in active-active configuration: 1 Drop the high availability companionship.
CHAPTER 5 9 Upgrading Adaptive Server Manually restart Adaptive Server on each cluster node with trace flag 2209. Use the Adaptive Server command-line option -T2209. Warning! Do not use trace flag 2209 after the Adaptive Server companionship is re-established. 10 Use the cluster system command to restart monitoring resources associated with Adaptive Server on each cluster node.
Migrating from 32-bit to 64-bit versions 2 Use the cluster system command to stop monitoring resources associated with Adaptive Server. 3 Follow the upgrade steps provided in “Upgrading to Adaptive Server 15.0.2” on page 68 to upgrade the Adaptive Server to the new version. 4 Run the new Adaptive Server installmaster script against the newly upgraded Adaptive Server. 5 In new Adaptive Server installation area, modify the high availability-related files such as the RUN_server_file, and the SYBASE.
CHAPTER 5 3 Upgrading Adaptive Server 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.
Recovering from a failed upgrade 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).
CHAPTER 5 Upgrading Adaptive Server isql> alter database dbname on device_name = "2m" Note In 15.0.2 Adaptive Server, alter database allows you to specify the size to alter the database with the unit-specifier ‘m’, or ‘M’.
Recovering from a failed upgrade 90 Adaptive Server Enterprise
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 100 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.
Overview Table 7-1: Troubleshooting guidelines for Windows 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. After Adaptive Server is installed, you should have 25MB of free disk space left in the disk drive.
CHAPTER 7 Troubleshooting Problem Possible cause and solution Attempts to create a server at the network level. Use the Open Client and Open Server configuration utility to edit %SYBASE%\ini\libtcl.cfg. The file should contain one of the following entries, depending on the protocol you have chosen to use: • NLWNSCK = Windows Socket driver • NLMSNMP = Named Pipes driver • NLNWLINK = spx/ipx driver If the entry is missing or incorrect, enter the correct value.
Solutions to common installation problems Table 7-3: Default locations for error log files Product Adaptive Server Error log location %SYBASE%\%SYBASE_ASE%\install\.log Backup Server Monitor Server %SYBASE%\%SYBASE_ASE%\install\.log %SYBASE%\%SYBASE_ASE%\install\.log Historical Server %SYBASE%\%SYBASE_ASE%\install\.
CHAPTER 7 Troubleshooting 1 From Windows, go to the MS-DOS command prompt window. 2 Start isql and connect to Adaptive Server: %SYBASE%\%SYBASE_OCS%\bin\isql -Usa -P -Sserver_name Where: 3 • %SYBASE% – is the Sybase installation directory • server_name – is the name of your Adaptive Server Shut down Adaptive Server using the shutdown with nowait command.
Solutions to common installation problems 4 If the installation fails after the installation program starts the Adaptive Server that you are attempting to install, shut down that server. 5 Use Server Config to restart the configuration. If Adaptive Server fails the pre-upgrade eligibility test If Adaptive Server fails the pre-upgrade test, Server Config displays: Server SERVER_NAME failed preupgrade eligibility test. See log for more information. 1 Click Exit.
CHAPTER 7 Troubleshooting If you think the upgrade failure or its cause may have damaged your databases, restore the databases from backups. For information on restoring databases, see the System Administration Guide. 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.
Solutions to common installation problems 2 If the failure occurs after all databases have been upgraded, or if a failure somehow causes the upgrade utility to crash, you can re-run the utility manually. First diagnose and correct the failure, then run the upgrade utility: %SYBASE%/%SYBASE_ASE%/upgrade/upgrade.exe When restarted in this way, the upgrade process says it is “verifying” the upgrade rather than “starting” it, but it makes all the same checks as for the original upgrade.
CHAPTER 7 2 Troubleshooting Perform the necessary actions to fix the problem. For example, if the error log indicates that the upgrade failed because your existing databases do not contain enough space, use the alter database command to increase the available space. 3 You may need to shut down Adaptive Server. Shutting down the server enables the installation program to start the server and re-run the upgrade session. 4 Start Server Config from the Sybase program folder.
Upgrading compiled objects with dbcc upgrade_object For example, if you have a user-defined stored procedure named list_proc, the presence of source text for list_proc is verified when you upgrade to Adaptive Server 15.0. The first time list_proc is invoked after the upgrade, Adaptive Server detects that the list_proc compiled object has not been upgraded. Adaptive Server recompiles list_proc, based on the source text in syscomments. The newly compiled object is then executed.
CHAPTER 7 Troubleshooting After reviewing the errors and potential problem areas, and fixing those that need to be changed, you can use dbcc upgrade_object to upgrade compiled objects manually instead of waiting for the server to upgrade the objects automatically. For details, see “Using dbcc upgrade_object” on page 113. 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.
Upgrading compiled objects with dbcc upgrade_object If quoted identifier errors occur, use the set command to activate quoted identifiers, and then run dbcc upgrade_object to upgrade the 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. If Adaptive Server version 15.0.2 is installed on top of an existing Adaptive Server 15.0.1, Adaptive Server version 15.0.
Removing an old server 5 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. 6 A summary window displays what is about to be uninstalled. Click Next to continue.
CHAPTER 8 Installation Guide Removing Adaptive Server 5 Click Remove Adaptive Server. This displays an Existing Servers window. 6 Select the server you remove, and click OK. 7 Restart the computer to reset registry entries.
Removing an old server 122 Adaptive Server Enterprise
A P PE N DI X A Alternative Installation Methods Topic Installation on consoles (non-GUI mode) Silent installation Page 123 124 Configuration using resource files 126 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 In either case it is possible to custom configure the servers as well as being able to select a typical install and use the default configuration values. 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.
Configuration using resource files .\setupConsole -silent -options -W SybaseLicense.agreeToLicense=true -G replaceNewerResponse="yesToAll" 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.
APPENDIX A Alternative Installation Methods Edit the resource file using a text editor such as Windows Notepad. You might want to edit a copy of the file. The sample resource files provided in the %SYBASE%\%SYBASE_ASE%\sample\server directory are: • sybatch_ase.res – Configure a new Adaptive Server • sybatch_bs.res – Configure a new Backup server • sybatch_ms.res – Configure a new Monitor server • sybatch_js.
Configuration using resource files Resource file variables Table A-1 lists the resource file variables. Before running the resource file, change all variables that start with “PUT-THE-*” with the corresponding value of the variable in Table A-1, or delete the value entirely. Table A-1: Resource file variable values Variable, “PUT-THE-” Description BOOT-DIRECTORY (sybinit) The directory in which to install Adaptive Server, %SYBASE%.
APPENDIX A Alternative Installation Methods Variable, “PUT-THE-” Description PATH-AND-NAME-OF-THE-BACKUP-ERRORLOG (Backup Server) The path in which Backup Server error logs are placed, such as c:\sybase\ASE-15_0\install\backup.log. The port number by which to identify Backup Server on the network, such as 5001. PORT-NUMBER (Backup Server) CHARACTERSET (Backup Server) The character set used by Backup Server, such as CP 850.
Configuration using resource files 130 Adaptive Server Enterprise
A P PE N DI X B Upgrading Servers with Replicated Databases Topic Introduction Suspending transaction processing and replication activities Page 131 132 Draining the transaction logs for primary databases Draining the RSSD transaction log 133 135 Disabling the secondary truncation point 136 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 137 138 Increasing device and database capacity for system procedures 139 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 139.
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 1> create database sybsystemprocs on sysprocsdev = 112 2> go 5 Run the instmstr command in the old release directory. For version 12.0: isql -Usa -Ppassword -i%SYBASE%\%SYBASE_ASE% \scripts\instmstr -oinstmster.out For versions earlier than 12.0: isql -Usa -Ppassword -i%SYBASE%\scripts\instmstr -oinstmster.
Increasing device and database capacity for system procedures 142 Adaptive Server Enterprise
Index A D Adaptive Server described 8 entries in sql.
Index I identifiers conflicting with reserved words 65 installation directory for unloading products 24 installing Open Client/C 11.9.
Index draining logs for Adaptive Server reserved words checking for conflicts 66 using quoted identifiers 66 resource files 126, 129 installation using 126 75, 133 S sample databases 44, 47 scripts installintpubs 46 installjpubs 47 installpix 45 servers including in sql.ini files 56 shared memory parameters setting 25 size recommended for database devices 137 Small Business Edition package 6 sp_checkreswords system procedure 65 SPX network protocol 14 sql.
Index 146 Adaptive Server Enterprise
