Adaptive Server® Enterprise Document Version: 16.
Table of Contents 1 Installation Guide for Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2 Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3 Installation Task Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 3.1 Installation Workflows. . . . . . . . . . . . . . . .
7.5 Uninstalling SAP ASE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 7.5.1 Removing an Existing SAP ASE Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49 8 Starting and Stopping SAP Control Center. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 9 Postinstallation Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.7.4 10.8 10.9 Reenabling Replication Server After the Dataserver Upgrade. . . . . . . . . . . . . . . . . . . . . . . . .86 Migrate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89 10.8.1 Migrating Data Using a Dump-and-Load Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 10.8.2 Using bcp to Migrate Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Installation Guide for Linux ® ® SAP Adaptive Server Enterprise is a high-performance relational database management system for missioncritical, data-intensive environments. It ensures highest operational efficiency and throughput on a broad range of platforms. ® This installation guide includes information on system requirements, planning the installation, installing SAP ASE, post-installation tasks, upgrades, and downgrades.
2 Conventions ® ® ® These style and syntax conventions are used in SAP Adaptive Server Enterprise (SAP ASE) documentation. ● In a sample window display, commands to be entered exactly as shown appear in: this font ● In a sample window display, words that you should replace with the appropriate value for your installation are shown in: ● In the regular text of this document, the names of files and directories appear in this font: /usr/u/home_dir.
3 Installation Task Overview To successfully install and configure SAP ASE, use the configuration guide along with this installation guide. The SAP ASE installation guide explains how to unload the SAP ASE software from the distribution media to your hard disk, and perform the minimal set of additional tasks so that you can start SAP ASE on your machine.
Uninstalling SAP ASE See Uninstalling SAP ASE. 8 © 2014 SAP SE or an SAP affiliate company. All rights reserved.
4 SAP ASE Components SAP ASE is based on a client/server model, communicating with its clients over the network via the Tabular Data Stream™ (TDS) protocol. Each client process may execute on one machine and communicate with a database server on the same or a different machine. SAP ASE runs as an application on top of an operating system. The hardware that the operating system runs on is completely transparent to SAP ASE, which sees only the operating system's user interfaces.
SAP ASE returns a value of EE, SE, or DE based on the edition that is currently running. See the Reference Manual for more information about sp_lmconfig. 4.2 SAP ASE Options SAP offers various optional features for SAP ASE, such as data compression, partitions, and encrypted columns.
In addition, you must also install the SCC Management User Interface for SAP ASE in the custom installation option by selecting the SAP Control Center Management User Interface for SAP ASE feature. This feature provides the GUI that allows you to manage and monitor activities in SAP ASE using a Web browser. In some cases, you may want to use a central SCC server to manage multiple SAP ASE servers and other products rather than using the SCC server that is installed with each SAP ASE server.
4.4 Client Components and Utilities There are several components that you can install onto a PC client to support the SAP ASE server, which are downloaded from the SAP Service Marketplace (SMP). The previous PC-Client installer is replaced in ASE 16.0 by separately downloadable installers that provide many of the same components. SDK for SAP ASE ® The SAP Service Marketplace provides both 32-bit and 64-bit SDK for SAP ASE images.
Product Description jutils-3_0 A collection of SAP ASE utility programs that includes ribo, a tool to trace TDS traffic utilities between a client program and SAP ASE. See the SDK Installation Guide at the SAP Service Marketplace for installation instructions. PowerDesigner Physical Modeler The modeler is available in the ASE SAP 16.0 section of the SAP Service Marketplace, and is installed from its own image. To install the modeler, download and extract the file, then run setup.
5 System Requirements Before installing SAP ASE version 16.0, ensure that your system is updated with the latest patches and system requirements. Do not use a patch that is earlier than the version suggested for your operating system. Use the patch recommended by the operating system vendor, even if it supersedes the patch listed. To list all currently installed patches and display the operating system version level, enter: rpm -q -a SAP ASE supports Pentium and higher chip sets.
Required Files Description ● libXp-devel ● libX11-devel ● libSM-devel ● libICE-devel These files should be compatible with RHEL5.3 or later. There is a known OS kernel bug in scheduling threads in RHEL 6.0 that has been fixed in RHEL 6.1; for this reason, you use 6.1.
5.1 Memory Requirements Each operating system has a default maximum shared-memory segment. Configure your operating system to allow the allocation of a shared-memory segment at least as large as the maximum memory value. The amount of memory SAP ASE can use on a Linux system is chip-dependent. The amount of memory SAP ASE can use is: ● On Sun Solaris 10 (SPARC) – 16EB ● On Sun Solaris 10 on AMD (x86) – chip-dependent 5.
6 Planning Your SAP ASE Installation Before you install or upgrade, prepare your environment. Procedure ● Identify the components and options to install or upgrade. ● Obtain a license. Note If you are using a served license, you must install the SySAM license server version 2.1 or later. ● Make sure your system meets all requirements for your installation scenario and planned use. 6.
Procedure 1. Choose a SySAM license model. License Model Description Unserved license model Licenses are obtained directly from the license file. If you are using an unserved license, save the license file to the machine on which you install the product. Served license model A license server manages the allocation of licenses among multiple machines.
6.2.1 Comparing License Deployment Models Learn about license deployment models. Unserved Licenses Served Licenses Licenses can be used only on the machine for which the license was generated. Licenses can be distributed from a network license server to products running on any network machine. Generate licenses at SMP or SPDC for each machine that will run the product: Generate licenses at SMP or SPDC for products run ning on multiple machines: 1. 2.
6.2.2 SySAM License Server If you choose to use the served licensed model, make sure you have installed the required SySAM license server version. The license server is a lightweight application that serves licenses to products running on any operating system. A license server can run on a low-end machine or a machine with spare cycles.
To determine the host ID of the machine, run the lmutil utility from a terminal window or the Windows command prompt. For example: lmutil lmhostid Note You can download the lmutil utility from either: ● The SAP ASE installer image, under the sysam_utilities directory; or, ● The Flexera Software Web site at http://www.globes.com/support/fnp_utilities_download.htm . You can also determine the host ID using native operating system commands.
6.2.3.2 Using Alternate Host IDs on Windows If your Windows machine does not have a network adapter, SySAM allows you to use an alternate host ID based on the hard disk serial number. Procedure 1. At a Windows command prompt on the machine where you will deploy your license, enter: lmutil lmhostid -vsn This returns output similar to: The FLEXlm host ID of this machine is "DISK_SERIAL_NUM=70ba7a9d" 2.
Required Information or Action License Model Served License server TCP/IP port numbers 6.2.4.1 Description Unserved X Determine the two port numbers on which the license server will listen for license requests. Generating License Keys at SMP Use SMP to generate license keys. Procedure 1. Go to the SAP Marketplace main page at http://service.sap.com/licensekeys 2. Log in using your SMP credentials. 3. Select SAP Support Portal. 4. Select 5.
6.2.5.1 Optional Feature Licenses Some SAP ASE applications are offered as base products with optional features that require a separate license. Customers can mix license types. For example, customers can order SAP ASE under the Server License (SR) license type and order an optional feature (for example, High Availability or Enhanced Full Text Search) under the CPU License (CP) type. Optional features are licensed only with the base product of the same product edition.
Vendor Product Platform Support Secure Resource Partitions IBM LPAR OS containers AIX 6.1, AIX 7 dLPAR Sun Dynamic System Domains Intel, AMD Virtualization Type Virtual partition Virtual partition Solaris 10 Physical partition Solaris Containers/Zones with Solaris Resource Manager Virtual partition Sun Logical Domain (LDOM) Virtual partition VMWare ESX Server Guest O/S: Windows VMWare ESX 3.5, ESX 4.0 and ESX 4.1, ESXi4.1, ESXi 5.
Although the installation media includes a copy of the most recent SySAM license server, we recommend that you periodically check for updates at http://service.sap.com/patches . When using SySAM sub-capacity licensing, set the SYBASE_SAM_CAPACITY environment variable before installing, or copy in the license key after installation. 6.3 Installation Directory Contents and Layout SAP ASE includes server components that are installed into specific directories.
Product Description Note The SAP ASE typical installation option installs only the SCC Remote Command and Control (RCC) agent. To use a GUI-based connection to the SCC server using a Web browser, you must use the custom installation option to install the SCC Management User Interface for SAP ASE. Language Modules Installed into the locales directory. Provides system messages and date/time formats. Character Sets Installed into the charsets directory.
6.4 Creating the Sybase User Account To ensure that SAP ASE product files and directories are created with consistent ownership and privileges, create a system administrator account. Context One user—typically the system administrator, who has read, write, and execute privileges—should perform all installation, configuration, and upgrade tasks. Procedure 1. To create a system administrator account, choose an existing account, or create a new account and assign a user ID, group ID, and password for it.
3. Verify that you can uncompress files on your UNIX machine. To uncompress: Option Description .zip files Use the unzip command .tgz files Use gzip or GNU Tar 4. Ensure that the account used to start the server has read and write permissions for the directory in which you are installing the server. You may need to create nonadministrative logins to install the server into personal directories. 5. Unset the LD_ASSUME_KERNEL variable. 6.
SAP ASE and client applications use network software even when they 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. Adjust the shared memory for your operating system. 6.5.1 Adjusting the Operating System Shared Memory Parameters Adjust shared memory segments if SAP ASE cannot obtain large memory as a single segment, or if Backup Server stripes fail due to insufficient segments.
Note The default operating system shared memory for some older Linux releases is 32MB. The minimum required by SAP ASE is 64MB for a default server with 2K pages. A higher value is required if you plan to increase the SAP ASE max setting. 3. To guarantee that the minimum operating shared value is applied every time the system is started, edit the /etc/sysctl.conf file. 4. For larger configurations, it may also be necessary to adjust the shmall parameter. The default on RHEL5 is 8GB (2097152 4K pages).
3> 4> 5> 1> 2> physname = "${SYBASE}/data/sybpcidb_dev.dat", size = "48M" go create database sybpcidb on sybpcidb_dev = 48 go The device and database sizes depend on the SAP ASE server page size. The minimum and default size requirements for sybpcidb are: 2. ○ 2KB page size server – 48MB ○ (Default) 4KB page size server – 96MB ○ 8KB page size server – 192MB ○ 16KB page size server – 384MB Disable Java in the database: 1> sp_configure 'enable java', 0 2> go 3.
● Solaris – Multiplexed I/O (MPxIO) ● AntemetA Multipathing Software for HP EVA Disk Arrays ● Bull StoreWay Multipath ● NEC PathManager ● EMC PowerPath ● FalconStor IPStor DynaPath ● Fujitsu Siemens MultiPath ● Fujitsu ETERNUS Multipath Driver ● Hitachi HiCommand Dynamic Link Manager (HDLM) ● HP StorageWorks Secure Path ● NCR UNIX MP-RAS EMPATH for EMC Disk Arrays ● NCR UNIX MP-RAS RDAC for Engenio Disk Arrays ● ONStor SDM multipath ● IBM System Storage Multipath Subsystem Device
Enterprise Linux 4 in Update 2 and into Novell SUSE Linux Enterprise Server 9 in Service Pack 2. To setup multipathing on Linux: Procedure 1. Edit the /etc/multipath.conf file: ○ Comment out the following lines at the top of the file. This section of the configuration file, in its initial state, blacklists all devices. You must comment it out to enable multipathing: blacklist { devnode "*" } ○ Add configuration information.
7 Installing SAP ASE Install SAP ASE using your chosen method. Prerequisites Complete installation planning tasks. Procedure 1. Choose an installation method: ○ GUI wizard (recommended) ○ Console mode ○ Response file 2. Follow the instructions for your chosen method. 3. Perform postinstallation steps. 7.1 Installing SAP ASE in GUI Mode Use GUI mode to install SAP ASE and related products. Prerequisites Shut down all programs before running the installer.
SAP ASE version 15.5 and later uses InstallAnywhere for its installation, while versions earlier than 15.5 and other products use InstallShield Multiplatform. Do not use both installers to install products into the same directory, as this creates files to be installed incorrectly and overwritten without warning. At the end of the installation, verify that the product has installed correctly. You may also need to perform additional configuration procedures. Procedure 1.
If you see Choose Update Installation, this means that there is an older version of SAP ASE in the directory you specified for the installation, and you need to perform an upgrade rather than a new installation. 8. Select the type of installation: Option Description Typical (Default) Recommended for most users, this option installs a default set of components, including the SAP Control Center Remote Command and Control Agent plug-in.
○ Message severity that triggers e-mail messages 12. In the preinstallation summary, verify the installation type and that you have enough disk space for the installation. Click Next. The installation status window displays the result of the installation process. 13. In the Configure New Servers window, configure: ○ SAP ASE ○ Backup Server ○ XP Server ○ Job Scheduler ○ SAP Control Center 14.
Related Information SAP ASE Upgrades [page 65] Managing SAP ASE with SAP Control Center [page 10] 7.2 Installing SAP ASE in Console Mode Choose command line installation if you prefer a nonwindowing interface, or if you are developing custom installation scripts. Prerequisites Launch the installer in console mode. If the installer launches automatically, click Cancel to cancel the GUI installation, then launch the setup program from a terminal or console.
7.3 Minimally Configuring an SAP ASE Server Use GUI mode to minimally configure an SAP ASE server and related products for use. Prerequisites The Configure screen shows a list of everything you can minimally configure. By default, all products are selected. Unselect any products you do not want to configure now. If you are configuring in console mode, enter the corresponding number: ● 1. Configure New SAP ASE ● 2. Configure New Backup Server – see the System Administration Guide ● 3.
Option Description ○ (Default) 4KB ○ 8KB ○ 16KB The default page size selection changed from 2KB to 4KB in SAP ASE version 15.5. If you plan to load database dumps from an SAP ASE with a page size that is not 4KB, enter the page size that matches the database dump. Language Default: us-english. In typical installations, only us-english is available. Default Character Set Default is iso_1. Default Sort Order Default is bin_iso_1.
Configuration Value master Database Size (MB) The minimum and default sizes are: ○ 2KB page size – 18MB ○ 4KB page size – 26MB ○ 8KB page size – 52MB ○ 16KB page size – 104MB System Procedure Device The complete file path name. System Procedure Device Size (MB) and System Procedure Database Size (MB) The default for both is 196MB. System Device The complete file path name.
4. 5. Configuration Value Allow Hosts Comma-separated lists of hosts that are allowed to connect to this Backup Server. When null, only the dataserver running on the same host as the Backup Server can access this Backup Server. The default value is null. Set the Configure New XP Server option: Configuration Value XP Server Name The XP Server name is set automatically, in the form of _XP. Port Number The port number of the Backup Server. The default is 5002.
9. Set the SAP Control Center – Configure RMI Port option with a port number (1025 to 65535) that is not used by another application or service on the system. The default is 9999. 10. Set the user names and passwords in Configure Administration Passwords.
7.4 Installing SAP ASE Using a Response File Unattended or silent installations are typically used to update multiple systems across the enterprise. Procedure To perform a silent, or "unattended" installation, run the installer and provide a response file that contains your preferred installation configuration. 7.4.
Note The directory path you specify must already exist. 2. Verify that the response file includes the passwords for the SAP ASE sa login, SAP Control Center admin, and SCC agent admin by including these lines in the file: SY_CFG_ASE_PASSWORD=<> CONFIG_SCC_CSI_SCCADMIN_PWD=<> CONFIG_SCC_CSI_UAFADMIN_PWD=<> CONFIG_SCC_REPOSITORY_PWD=<> Each password must be at least six characters long.
Note Make sure that the user you specify in this property setting has read/write/modify permissions to access the data directory. 7.4.2 Installing in Silent Mode To perform a silent, or unattended installation, run the installer and provide a response file that contains your preferred installation configuration. Prerequisites Use setup.bin -r to generate a installation response file during a console or GUI installation. Procedure 1.
○ SY_CFG_ASE_PASSWORD ○ CONFIG_SCC_CSI_SCCADMIN_PWD ○ CONFIG_SCC_CSI_UAFADMIN_PWD ○ CONFIG_SCC_REPOSITORY_PWD Note For security purposes, treat response files with care if they contain passwords. 7.4.3 Command Line Options Options for installing or uninstalling SAP ASE in console mode. Option Purpose -i console Uses the console interface mode, where messages appear on the Java console and the wiz ard runs in console mode.
Procedure 1. Execute: $SYBASE/sybuninstall/ASESuite/uninstall 2. Click Next in the Uninstall Welcome window. 3. Choose one of the following, then click Next: Option Description Complete Uninstall Uninstalls everything originally installed by the installer. Uninstall Specific Features Displays a list of features. If any unselected products/components are dependent on features selected for uninstallation, you can still proceed with the uninstallation but dependent features are not uninstalled.
8 Starting and Stopping SAP Control Center SAP Control Center (SCC) for SAP ASE is a Web-based tool for monitoring the status and availability of SAP ASE servers. Set the $SYBASE environment variables and start an SCC agent on your SAP ASE server. Prerequisites Before starting SAP Control Center, make sure you have installed both: ● SCC agent for SAP ASE – a remote command and control agent that runs on a managed server, and which is required to manage SAP ASE tasks within SCC.
You should see a status message similar to: Agent Home: /remote/perf_archive/mymachine/Install_Testing/157CE_C3/SCC-3_3/instances/ solstrs3 Connection URL: service:jmx:rmi:///jndi/rmi://solstrs3:9999/agent Status: RUNNING ● To shut SCC down from the console: scc-console> shutdown Related Information Managing SAP ASE with SAP Control Center [page 10] Installation Guide for Linux Starting and Stopping SAP Control Center © 2014 SAP SE or an SAP affiliate company. All rights reserved.
9 Postinstallation Tasks After you install the server, set it up. The SAP ASE installation includes directories that contain sample client library applications. These sample programs are included for training purposes only and are not intended to be installed in a production environment.
Procedure 1. From a UNIX command line, set the environment variables. ○ In the C shell: source /SYBASE.csh ○ In the Bourne shell: /SYBASE.sh 2. Show all SAP ASE-related processes that are on the system: $SYBASE/$SYBASE_ASE/install/showserver 9.2 Verifying Your Connection to the Servers Use isql to verify your connection to the servers. Context 1.
(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 using remote procedure calls. For SAP Control Center to work, install both the SCC agent for SAP ASE as well as the SCC Management User Inserface for SAP ASE. A "typical" installation includes the agent, while the SCC Management User Interface for SAP ASE is available only if you select the "custom" installation option.
Caution Ensure that the LDAP URL is on a single line. ldap=libsybdldap.dll ldap://:/ditbase??scope?? bindname=username?password For example (entry shown on multiple lines only for readability): [DIRECTORY] ldap=libsybdldap.dll ldap://huey:11389/dc=sybase,dc=com??one?? bindname=cn=Manager,dc=sybase,dc=com?secret Note On Windows x64, the .dll file is called libsybdldap64.dll. 2. Verify that the appropriate environment variable points to the required third-party libraries.
9.4 The System Administrator Password When you install SAP software, the software creates a system administrator account called "sa," which can use any database on an SAP ASE server, including master, with full privileges. When you log in to the SAP ASE server, you are prompted to set a password for "sa." See the Security Administration Guide for more information about passwords. 9.
9.5.1 Default Devices for Sample Databases The SAP ASE installation includes scripts for installing the us_english sample database, foreign language sample databases, and the image data associated with the US English pubs2 sample database on a default device. These scripts are located in $SYBASE/$SYBASE_ASE/scripts. By default, these scripts install the sample databases on the master device.
The pubs3 database does not use image data. For more information about running these scripts, see the Configuration Guide for UNIX. 9.5.3 Installing the interpubs Database The interpubs database is similar to pubs2, and contains French and German data. Prerequisites Back up the original installintpubs script, in case you experience problems with the edited script. Procedure 1. Set your terminal to display 8-bit characters. 2.
Procedure 1. Set your terminal to display 8-bit characters. 2. Verify that the EUC-JIS, Shift-JIS, or the UTF-8 character set is installed either as the SAP ASE default character set or as an additional character set. 3. Determine the type (raw partition, logical volume, operating system file, and so on) and location of the device where you will be storing the jpubs database. You will need to provide this information later. 4.
● After users have finished updating one of the sample databases, instruct them to issue the rollback transaction command to undo the changes. 9.6 Raw Partitions on Linux You can create and mount database devices on raw bound devices for raw disk I/O. Raw disk I/O enables direct memory access from your address space to the physical sectors on the disk, while omitting needless memory copy operations from the user address space to the kernel buffers.
9.6.2 Examples for Creating Raw Partitions Specific system administration is required before you can enable and use raw devices. The available tools to configure devices depend on the distribution configuration. You must allocate physical disk space in partitions on the disks where you want to set up raw devices. The physical I/O subsystem can be on either SCSI or EIDE devices. Note You can create partitions with the Linux default fdisk(8) utility. You must have root privileges to use the command fdisk.
4. Use the t command, enter 5 at this prompt: Partition number (1-8): 5 5. Enter 60 at this prompt: Hex code (type L to list codes): 60 The output is: Changed system type of partition 5 to 60 (Unknown) 6. Repeat steps 1–5 to create four partitions for raw device I/O. 7. Verify the setup using p to print the full partition table before writing it out. Make sure that there are no overlapping partitions and the type for the unassigned partitions is Unknown type 60.
d) To make sure the raw device binding runs whenever you restart the system, enter: # /sbin/chkconfig rawdevices on ● If you are using Red Hat Enterprise Linux system running release 5 or later, modify the /etc/udev/ rules.d/60-raw.rules file: # Enter raw device bindings here.
9.6.4 Accessing Raw Devices from the Server After you create partitions and bind the devices for raw disk I/O, Adaptive Server can use them.
10 SAP ASE Upgrades You can upgrade to SAP ASE version 16.0 from versions 12.5.4 or later. Upgrades are supported only between nonclustered editions of SAP ASE. You cannot upgrade from SAP ® Adaptive Server Enterprise Cluster Edition to a nonclustered edition. ® You can upgrade to SAP ASE version 16.0 from versions 12.5.4, 15.0 through 15.7 by executing the upgrade sequence from the same node on which the database resides. This is a major upgrade, and requires that you perform preupgrade tasks.
An upgrade is done by: ● Upgrading your entire installation by switching binaries. ● Upgrading a single database using online database, having first loaded it with a database dump and transaction logs taken on a server with an earlier version. Table 6: Upgrading Your Entire Installation Current Ver sion Upgrading to Special Upgrade Information SAP ASE 15.0.x or ear lier SAP ASE 16.
10.2 Considerations for Component Integration Services If you have both a local and a remote server running on SAP ASE version 15.x and are upgrading both of them to version 16.0, upgrade the local server first. If you plan to upgrade one server but not the other, upgrade the local server. SAP does not certify that Component Integration Services running on earlier versions of SAP ASE can connect to later versions.
Manually drop objects before you execute procedures for the first time. The first time you run the server after an upgrade, the server internally rebuilds procedures from the text in syscomments. The procedure may not execute properly if it contains code that drops, then re-creates, an existing object. Procedure 1. Go to the directory where your current version of SAP ASE is installed. 2. Enter cd in to go to the directory ASE-, where is your current version of SAP ASE. 3.
Component Location Language settings (locales) ● 12.5.4 and 15.0.2 locations – $SYBASE/locales ● 15.0.3, 15.5, 15.7 GA, and 15.7 ESD #1, ESD #2, ESD #3, and SP100 locations – $SYBASE/ locales and $SYBASE/ASE-15_0/locales ● Connectivity Web Service SySAM Job Scheduler Unified Agent 16.0 location – $SYBASE/locales and $SYBASE/ASE-16_0/locales ● 12.5.4 location – $SYBASE/OCS-12_5 ● 15.0.2, 15.0.3, 15.5, 15.7 GA, and 15.7 ESD #1, ESD #2, ESD #3, and SP100 locations – $SYBASE/OCS-15_0 ● 16.
Context Note Follow these steps only if you are performing a major upgrade from an SAP ASE version earlier than 16.0. Skip these preparatory tasks if you plan to use sqlupgrade, which performs these tasks automatically. Procedure 1. Install SAP ASE 16.0 into the old ASE directory. 2. Check system and upgrade requirements. 3. Ensure that the directory to which your TEMP environment variable points exists. 4.
f) Disable disk mirroring. g) Verify that your SYBASE environment variable points to the location of the new server software files you just installed. Fix any problems that preupgrade utility reports. You can safely ignore any warnings SAP ASE issues about configuration parameters not being set to the default, as these are only for your information. 13. If you are upgrading from a nonclustered 12.5.4, 15.0.2, 15.5, or 15.
If you change an object name, also change applications and stored procedures that refer to that object. Conflicts between object names do not prevent the upgrade process from completing. However, applications that refer to conflicting object names may not work after the upgrade. Rename all objects that use reserved words. As part of the preupgrade process, you can have sqlupgrade, sqlupgraderes, or preupgrade perform a reserved-word check for you.
10.5.2.2 Addressing Reserved Words Conflicts Change any database names that are reserved words. Procedure 1. Use sp_dboption to set the database to single-user mode, then run sp_renamedb, specifying the new name. 2. If other identifiers are reserved words, you can use: ○ sp_rename to change the name of the object, before or after the upgrade. ○ Quoted identifiers. ○ Brackets around the identifier. For example: create table [table] ( [int] int, [another int] int ) 3.
stored procedures or compiled objects in any database, the syscomments and sysprocedures system tables require additional space. The preupgrade utility scans the system catalogs and performs this calculation automatically. 2. If you are: ○ Not using two-phase commit or distributed transaction management (DTM) applications, create a sybsystemdb with a minimum of 4MB if it does not already exist.
10.5.4 The sybprocsdev device Sybase system procedures are stored in the sybsystemprocs database, which is stored in the sysprocsdev device. You may need to increase the size of sysprocsdev before upgrading SAP ASE. Regardless of page size, when configuring a new server, the size of sybsystemprocs is: ● Minimum – 184 MB ● Default – 196 MB For upgrades, you need an additional 10 percent of this. You may need more space if you are adding user-defined stored procedures.
Procedure 1. In isql, use alter database to increase the size of the sybsystemprocs database. For example: 1> 2> 1> 2> use master go alter database sybsystemprocs on sysprocsdev=40 go In this example, "sysprocsdev" is the logical name of the existing system procedures device, and 40 is the number of megabytes of space to add. If the system procedures device is too small, you may receive a message when you try to increase the size of the sybsystemprocs database.
Procedure 1. Determine which device you must remove: select , from sysdevices d, sysusages u where u.vstart between d.low and d.high and u.dbid = db_id("sybsystemprocs") and d.status & 2 = 2 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.
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 that were returned in the list. Note File names cannot be complete path names. If you use relative paths, they are relative to the directory from which your server was started. 5.
10.6 Upgrade to SAP ASE 16.0 If you are performing a major upgrade from a version earlier than 16.x, you are ready to upgrade SAP ASE after you successfully run the preupgrade utility. 10.6.1 Upgrading Interactively Using sqlupgrade Use the interactive sqlupgrade tool to upgrade SAP ASE using an X-Windows or Motif GUI. Prerequisites Set the OLDSYBASE_ASE variable to the SYBASE_ASE that is appropriate to your older server. If you are upgrading from 15.7 for example, OLDSYBASE_ASE should be ASE-15_0.
○ The full path of the data directory for the new SAP ASE release directory. This field allows you to specify a working directory that differs from the default $SYBASE directory, which allows users other than the sa to configure and use SAP ASE without the need to have access permission to the $SYBASE directory. ○ The name of the component directory that contains the new SAP ASE version. ○ The full path of the old release directory.
● select @@version – SAP ASE should return 16.0. ● sp_configure "upgrade version" – SAP ASE should return 16000000 (16 million). 10.6.2 Upgrading Noninteractively Using sqlupgraderes You can upgrade SAP ASE without the graphical user interface (GUI), in noninteractive mode by using values from a resource file that defines the attributes for the server to be upgraded. Prerequisites Set the OLDSYBASE_ASE variable to the SYBASE_ASE that is appropriate to your older server. If you are upgrading from 15.
○ – is the server you are upgrading. ○ – is the month. ○ - – is the date. ○ – is a three-digit number identifying the sqlupgrade session. If the resource file you are modifying was created by sqlupgrade, the prefix of the attribute name may vary. sqlupgraderes ignores this prefix when processing the resource file. The attributes and their default values are: ○ sybinit.release_directory – $SYBASE [] ○ sybinit.product – sqlsrv ○ sqlsrv.
3. Copy the .cfg file from old directory to the new $SYBASE directory. 4. Start the 16.0 server with the old master device from the old server. 5. Restart all the additional servers you shut down after shutting down the pre-16.0 SAP ASE. 6. Run upgrade. If problems occur, fix them, and re-run the upgrade process. 7. Reinstall the SAP ASE-supplied stored procedures to prevent any errors caused from changes to the system catalogs. 10.
10.7.1 Restoring Functionality in SAP ASE After Upgrading Restore functionality in the server after an upgrade. Procedure 1. If you changed any configuration parameters before upgrading, use sp_configure to set them back to their earlier values. 2. Use sp_dboption to reset any database options you disabled before upgrading. 3. Before you use the upgraded server, verify that all custom scripts point to SAP ASE 16.0. 4. Verify procedure cache allocation.
10.7.2 Reenabling Auditing If the server you upgraded from was configured for auditing, reenable auditing in the upgraded server. Procedure 1. Enter: sp_configure 'auditing', 1 2. Reenable auditing for all system stored procedures for which auditing was enabled before the upgrade. a) Use the output of sp_displayaudit recorded during the preupgrade process to identify the system stored procedures for which auditing was enabled. b) Reenter the audit options using sp_audit.
10.7.3 Restoring Permissions If the server you upgraded from had site-specific permissions on system stored procedures, restore those permissions in the upgraded server. Context 10.7.4 Reenabling Replication Server After the Dataserver Upgrade If you disabled replication before the upgrade, you must reenable replication. Procedure 1. Remove older formatted log records from your database. 2.
10.7.4.1 Restoring Replication on Replicate Databases Restore replication if you have upgraded a destination-only dataserver in a replication system. Context Perform these steps for each replicate database and Replication Server System Database (RSSD). Procedure 1. Start the SAP ASE server if it is not already running. 2. Log in to the SAP ASE server. 3. If you have zeroed out the locator for the database, go to step 4.
10.7.4.2 Restoring Replication on Primary Databases Restore replication if you have upgraded a source database, or primary database, in a Replication Server system, or if the destination database is also a source for other Replication Servers. Procedure 1. If you have zeroed out the locator for the database, go to the next step. Otherwise, stop Replication Server, then run: 1> 2> 1> 2> 2.
10.8 Migrate You can migrate from 32-bit to 64-bit versions on different computers or partitions. To migrate SAP ASE from the 32-bit to the 64-bit version, first install and configure the 64-bit operating system. To migrate, you can: ● Use dump and load. ● Use the bcp utility. ● Replace the binary. 10.8.1 Migrating Data Using a Dump-and-Load Method To perform migrations, back up and restore databases using the dump and load commands. Procedure 1.
10.8.2 Using bcp to Migrate Data If you use DDL scripts to create devices, databases, tables, rules, stored procedures, triggers, and views, you can use bcp to migrate data from a 32-bit SAP ASE to a 64-bit SAP ASE. Context If you: ● Do not have DDL scripts, use the ddlgen utility to re-create the schema for the SAP ASE you are about to migrate. See the Utility Guide.
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 SYBASE.csh script (C shell). 9.
2. Make sure the new server is running. 3. Ensure that at least 9000 locks are configured. If the number of locks on the server is fewer than 9000, increase it: 1> sp_configure "number of locks", 9000 2> go 4. Before you restart the SAP ASE server and run Job Scheduler, run the installjsdb script to update Job Scheduler tables and stored procedures: a) Disable Job Scheduler: 1> 2> 1> 2> sp_configure "enable job scheduler", 0 go sybmgmtdb..
10.9.1.1 Upgrading Job Scheduler Templates After upgrading to the new server, upgrade the templates and jobs created by Job Scheduler. Context Note Several changes impact the Job Scheduler templates. These changes make some templates incompatible with earlier versions of the server. The current templates are version 3.0 in the XML files. Procedure 1. Disable Job Scheduler. 2. Update any environment variables, scripts, or applications that refer to the Job Scheduler directory path.
6. Template Modified Files Datatype for Changed from varchar(5) to int rebuild table jst_reorg_rebuild_tables @dump_flag reclaim indexes jst_reclaim_index_spac @dump_flag reclaim tables jst_reclaim_table_space @resume_flag Some Job Scheduler templates have been modified to support new server functionality. These changes are related to new parameters for specifying a partition name, or a data change value for the new server commands that added these options.
7. Install the template stored procedures and and move them to the Job Scheduler template stored procedure directory. For example: cd $SYBASE/$SYBASE_ASE/jobscheduler/Templates/sprocs Run the stored procedure installation script for each server being upgraded: installTemplateProcs <> <> <> Note Upgrade template stored procedures on all Job Scheduler servers and target servers that are upgraded to SAP ASE version 16.0. Do not install them on pre-15.5 servers. 8.
There are two ways to upgrade a cluster subsystem: Procedure ● Perform a major upgrade, which involves cluster downtime, then shut down and restart all servers. You must: a) Run sp_companion suspend, as described in Using Sybase Failover in a High Availability System. b) Take offline the resource groups of primary and secondary companions on both nodes. Ensure that the companion server and corresponding resource groups are not automatically brought online until the cluster system upgrade is complete.
10.9.3 Upgrading Java in the Database If Java in the database functionality is currently enabled, you must run the installpcidb script, which creates tables and stored procedures in the sybpcidb database. Procedure 1. Use isql to run the installpcidb script, saving the output to an operating system file. isql -Usa -P<> -S<> -i$SYBASE/$SYBASE_ASE/scripts/installpcidb -o<> 2.
10.9.4 Upgrading Backup Server You can upgrade Backup Server at any point after you upgrade SAP ASE using similar steps. XP Server does not have a formal upgrade process. Procedure 1. If you are: Option Description Upgrading during the initial server installation Select: ○ Upgrade Existing Servers when the installer prompts ○ Upgrade SAP ASE Server and Backup Servers This launches the sqlupgrade utility. Click OK.
10.9.6 How Compiled Objects Are Handled When Upgrading SAP ASE SAP ASE upgrades compiled objects based on their source text. Compiled objects include: ● Check constraints ● Defaults ● Rules ● Stored procedures (including extended stored procedures) ● Triggers ● Views The source text for each compiled object is stored in the syscomments table, unless it has been manually deleted. The upgrade process verifies the existence of the source text in syscomments.
Related Information Postupgrade Tasks [page 83] Restoring Functionality in SAP ASE After Upgrading [page 84] 10.9.6.1 Finding Compiled Object Errors Before Production Use dbcc upgrade_object to identify potential problem areas that may require manual changes to achieve the correct behavior.
10.9.6.1.1 Quoted Identifier Errors 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. Context dbcc upgrade_object returns a quoted identifier error if: ● The compiled object was created in a pre-11.9.2 version with quoted identifiers active (set quoted identifiers on). ● Quoted identifiers are not active (set quoted identifiers off) in the current session.
In this example, you have the following statement: create view all_emps as select * from employees Caution Do not execute a select * statement from the view. Doing so upgrades the view and overwrites the information about the original column information in syscolumns. 2.
11 Downgrading SAP ASE You cannot downgrade SAP ASE version 16.0 to an earlier version of SAP ASE. Note Do not run the sp_downgrade system procedure. The downgrade may appear to work but does not actually occur, and you can neither start the previous version of SAP ASE or load databases you dumped from version 16.0 Installation Guide for Linux Downgrading SAP ASE © 2014 SAP SE or an SAP affiliate company. All rights reserved.
12 Troubleshoot the Server Determine the cause of problems and apply the recommended solution. To determine the cause of an error, first look in the log file of the utility being used, to identify the task the utility was performing when it failed. Then check the server error log. This table lists possible causes and solutions for common problems that you might encounter during a first-time installation, or an upgrade. If you continue to have problems, retry the installation or upgrade.
12.2 Error Logs for SAP ASE Servers The information in the error logs may help to determine the reason and possible solution for an error message. Server Default Location and File Name SAP ASE $SYBASE/$SYBASE_ASE/install/.log Backup Server $SYBASE/$SYBASE_ASE/install/.log XP Server $SYBASE/$SYBASE_ASE/install/.log 12.3 Troubleshooting Common Installation Problems Identify the cause of installation problems and apply the recommended solutions.
Problem Resolution Client not authorized to connect to server. This error message means a remote machine does not have permission to display the user interface on the local machine where you start working: Xlib: connection to "host_name" refused by server Xlib: Client is not authorized to connect to Server xhost: unable to open display "host_name" To correct the problem: 1.
12.3.1 If the Installation Quits While You Are Configuring an SAP ASE Server Perform specific steps if the installation suddenly quits. Procedure 1. View the contents of the log file generated by the SAP ASE server. 2. Take any suggested actions to correct the problem. If the installation fails after the installation program: 3. ○ Created any operating system files, such as the master device or system procedures device files, delete those files.
12.5 If SAP ASE Fails the Preupgrade Eligibility Test Examine the log file to determine why SAP ASE is ineligible for an upgrade. Context If SAP ASE fails the preupgrade test, Server Config displays: Server failed preupgrade eligibility test. See log for more information. Procedure 1. From the Upgrade window, select Exit. 2. Examine the log file in $SYBASE/$SYBASE_ASE/init/logs.
Procedure 1. Exit the sqlupgrade program. 2. 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. If needed, shut down the SAP ASE server. Shutting down the server enables the installation program to start the server and re-run the upgrade session. 4. Start sqlupgrade again. 5.
Procedure ● If the upgrade failed because the process ran out of some resource, such as data or log space, locks, or auxiliary scan descriptors, add space to the database using the alter database command. You may also correct other resource failures by changing the server’s configuration using the sp_configure stored procedure.
Note When a server fails during an upgrade process, it attempts to upgrade the databases when it restarts. When the installation is fully recovered, re-run the upgrade utility to ensure that all postupgrade configuration work is done. Then reinstall the system stored procedures. ● During the upgrade process, the log may become too full due to recorded catalog changes.
13 ® [conref] ASE Installation Guide ® SAP Adaptive Server Enterprise is a high-performance relational database management system for missioncritical, data-intensive environments. It ensures highest operational efficiency and throughput on a broad range of platforms. This installation guide includes information on system requirements, planning the installation, installing ASE, post-installation tasks, upgrades, and downgrades. 112 © 2014 SAP SE or an SAP affiliate company. All rights reserved.
Important Disclaimers and Legal Information Coding Samples Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding.
www.sap.com/contactsap © 2014 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.
