CACI Proprietary Information | Date 1 Pre-Upgrade Tasks Name: Semarria Rosemond Title: Systems Analyst, Lead Date: December 8, 2011

CACI Proprietary Information | Date 2 2 Pre-Upgrade Tasks  The pre-upgrade tasks include configuring the Sybase ASE ESD#2 database server for the upgrade and retrieving the Sybase ASE ESD#4 install files. Warning: When multiple Sybase instances (e.g., PD² and MWS) use the same Sybase binary installation, all instances are affected by one single Sybase binary upgrade. Therefore, all affected instances must complete each pre-upgrade task at the same time before continuing to the next task.  Sybase databases must be online and accessible.  Users should be able to access databases without receiving connection errors.  Start both Sybase Adaptive Server and Backup Server of each Sybase instance if they are currently down.

CACI Proprietary Information | Date 3 3 Pre-Upgrade Tasks  2.1 Record Information about ASE ESD#2 To record ASE ESD#2 information: −Ensure that the database server meets the PD² Database Server Configurations requirement specified in the PD² v4.2 Increment 2 SR13 Hardware Software Specifications document. −Record following information into the Worksheet: −Fully qualified Sybase ASE ESD#2 database server host name (Worksheet Item #1). −Windows database server only: Existing operating system user name and password that manages Sybase ASE ESD#2 services (Worksheet Item #2). This user must have the Administrators privileges.

CACI Proprietary Information | Date 4 4 Pre-Upgrade Tasks  2.1 Record Information about ASE ESD#2 To record ASE ESD#2 information: −Record following information into the Worksheet: −UNIX database server only: Existing operating system user name and password that manages Sybase ASE ESD#2 servers (Worksheet Item #2). −Existing Sybase ASE ESD#2 installation directory on the database server (Worksheet Item #3). −If the PD² instance exists: PD² Sybase Adaptive Server name (Worksheet Item #4) on the database server (Worksheet Item #1). −This is typically named SPS_ or SPS_ _ASE15, where is the DoDAAC of the site.

CACI Proprietary Information | Date 5 5 Pre-Upgrade Tasks  2.1 Record Information about ASE ESD#2 To record ASE ESD#2 information: −Record following information into the Worksheet: −If the PD² instance exists: PD² Sybase Adaptive Server port number (Worksheet Item #5). −If the PD² instance exists: PD² Sybase Backup Server name (Worksheet Item #6) on the database server (Worksheet Item #1). This is typically named SPS_ _BS or SPS_ _ASE15_BS, where is the DoDAAC of the site. −If the PD² instance exists: PD² Sybase Adaptive Server super user account (e.g., sa) and password (Worksheet Item #7).

CACI Proprietary Information | Date 6 6 Pre-Upgrade Tasks  2.1 Record Information about ASE ESD#2 To record ASE ESD#2 information: −Record following information into the Worksheet: −If the MWS instance exists: MWS Sybase Adaptive Server name (Worksheet Item #8) on the database server (Worksheet Item #1). This is typically named SPS_ _MWS, where is the DoDAAC of the site. −If the MWS instance exists: MWS Sybase Adaptive Server port number (Worksheet Item #9).

CACI Proprietary Information | Date 7 7 Pre-Upgrade Tasks  2.1 Record Information about ASE ESD#2 To record ASE ESD#2 information: −Record following information into the Worksheet: −If the MWS instance exists: MWS Sybase Backup Server name (Worksheet Item #10) on the database server (Worksheet Item #1). This is typically named SPS_ _MWS_BS, where is the DoDAAC of the site. −If the MWS instance exists: MWS Sybase Adaptive Server super user account (e.g., sa) and password (Worksheet Item #11).

CACI Proprietary Information | Date 8 8 Pre-Upgrade Tasks  2.1 Record Information about ASE ESD#2 The SSH Tectia software secures the network communication between the client and database server and is not required to complete the Sybase upgrade. However, if the site decides to implement the SSH Tectia solution, ensure that the physical database server (Worksheet Item #1) has the SSH Tectia Server software installed and configured.

CACI Proprietary Information | Date 9 9 Pre-Upgrade Tasks  2.2 Locate a Windows Workstation with Sybase Open Client 15 The pre-upgrade tasks should be performed from a Windows workstation with Sybase Open Client 15 ESD#16 unless specified otherwise. This Windows workstation must have Sybase Open Client 15 ESD#16 configured to connect to the Sybase ASE ESD#2 Adaptive Server. Record the name of the Windows workstation in Worksheet Item #12. Ensure that the Windows workstation meets the SPS Database Installer Configurations requirement in the PD² v4.2 Increment 2 SR13 Hardware Software Specifications document.

CACI Proprietary Information | Date 10 Pre-Upgrade Tasks  2.2 Locate a Windows Workstation with Sybase Open Client 15 Sybase Interactive SQL tool must be configured as follows: −On the Windows workstation (Worksheet Item #12), launch Interactive SQL. −Connect to the Sybase Adaptive Server by entering the user name and password, selecting the database server from the drop-down list box, and clicking [OK]. −From the menu select Tools → Options then following step listed this section (2.2) of the Sybase ASE ESD4 Upgrade Guide for PD² v4.2 Increment 2 SR13.

CACI Proprietary Information | Date 11 Pre-Upgrade Tasks  2.3 Check the Current Sybase Version select go The result should contain the following text: −Adaptive Server Enterprise/15.0.3/EBF xxxxx ESD#2/ −where “xxxxxx” is the EBF number for the database server platform. −STOP immediately if the version number is incorrect and contact the SPS Help Desk or the JPMO for further assistance.

CACI Proprietary Information | Date 12 Pre-Upgrade Tasks  2.4 Verify Sybase Super User Account The upgrade process requires the use of Sybase super user account “sa.” Ensure that the “sa” account is unlocked, sa_role, sso_role, oper_role, and sybase_ts_role are granted, and its default database is master.

CACI Proprietary Information | Date 13 Pre-Upgrade Tasks  2.4 Verify Sybase Super User Account To verify these conditions, log in to the: −Sybase ESD#2 Adaptive Server (PD²: Worksheet Item #4) as a Sybase super user (PD²: Worksheet Item #7); −MWS: (Worksheet Item #8) as a Sybase super user (Worksheet Item #11) through Interactive SQL or ISQL from the Windows workstation and enter the following command(s): −sp_displaylogin sa go −The output message should contain the following output: −Loginame: sa −Default Database: master −Configured Authorization: sa_role (default ON), sso_role (default ON), oper_role (default ON), sybase_ts_role (default ON) −Locked: NO

CACI Proprietary Information | Date 14 Pre-Upgrade Tasks  2.5 Verify That Users Are Logged Off and Processes Are Stopped To verify that users are logged off and processes are stopped: −If the PD² instance exists, verify that all users are logged off the PD² Sybase instance. Log in to the Adaptive Server (Worksheet Item #4) through Interactive SQL or ISQL from the Windows workstation (Worksheet Item #12) as “sa” (Worksheet Item #7) and enter the following commands to display the users currently logged on to the server: sp_who go Note: It is normal to see multiple system processes logged into the Sybase server (e.g., Network Handler, Deadlock tune, Housekeeper, etc.).

CACI Proprietary Information | Date 15 Pre-Upgrade Tasks  2.5 Verify That Users Are Logged Off and Processes Are Stopped To verify that users are logged off and processes are stopped: −If the MWS instance exists, log in to Sybase Central as “sa” (Worksheet Item #11) and lock out all MWS user logins for the duration of the upgrade. DO NOT lockout the following logins: −sa −probe −mon_user −If the MWS instance exists, shutdown and restart the MWS Sybase Backup Server and Adaptive Server. Refer to Appendix E: Start and Stop Sybase ASE Services.

CACI Proprietary Information | Date 16 Pre-Upgrade Tasks  2.5 Verify That Users Are Logged Off and Processes Are Stopped −If the MWS instance exists, verify that all users are logged off the MWS Sybase instance. Log in to the Adaptive Server (Worksheet Item #8) through Interactive SQL or ISQL from the Windows workstation (Worksheet Item #12) as “sa” (Worksheet Item #11) and enter the following commands to display the users currently logged on to the server: sp_who go Note: It is normal to see multiple system processes logged into the Sybase server (e.g., Network Handler, Deadlock tune, Housekeeper, etc.).

CACI Proprietary Information | Date 17 Pre-Upgrade Tasks  2.5 Verify That Users Are Logged Off and Processes Are Stopped To verify that users are logged off and processes are stopped: −Shutdown all external servers that access the Sybase ASE ESD#2 database server (e.g., Application Server, AcquiLine Web Server, webMethods Integration Servers, etc.) −Disable all scheduled tasks that access the Sybase ASE ESD#2 database server. These tasks include database backups and server restart scripts.

CACI Proprietary Information | Date 18 Pre-Upgrade Tasks  2.5 Verify That Users Are Logged Off and Processes Are Stopped To verify that users are logged off and processes are stopped: −If the PD² instance exists, log in to Sybase Central as “sa” (Worksheet Item #7) and lock out all PD2 user logins for the duration of the upgrade. DO NOT lockout the following logins: −sa −sysadmin −probe −mon_user −If the PD² instance exists, shutdown and restart the PD² Sybase Backup Server and Adaptive Server. Refer to Appendix E: Start and Stop Sybase ASE Services.

CACI Proprietary Information | Date 19 Pre-Upgrade Tasks  2.6 Disable Auditing and Monitoring Note: Repeat this section for each affected Sybase instance. Sybase Auditing and Monitoring must be disabled for the Sybase Server and MWS instances prior to the upgrade. −Execute the following commands and record the values on the worksheet in the appropriate section: −sp_configure 'auditing' −sp_configure 'enable monitoring' −Execute the following commands to disable: −sp_configure 'auditing', 0 −sp_configure 'enable monitoring', 0 −Shutdown and restart the Sybase Adaptive Server and MWS.

CACI Proprietary Information | Date 20 Pre-Upgrade Tasks  2.7 Update DBCC Parameters (MWS Instance Only) Note: This section is only applicable when the MWS instance exists. It does not apply to PD² instance. From the Windows Workstation (Worksheet Item #12), log in to the MWS Sybase Adaptive Server (Worksheet Item #8) through Interactive SQL or ISQL as “sa” (Worksheet Item #11), and execute following commands: sp_poolconfig 'default data cache' go

CACI Proprietary Information | Date 21 Pre-Upgrade Tasks  2.7 Update DBCC Parameters (MWS Instance Only) At the end of the output, the cache pool size is specified. If only the 16 Kb pool is specified and the 128 Kb pool is missing, execute following commands: sp_poolconfig 'default data cache', '6M', '128K' go sp_dbcc_updateconfig null, 'max worker processes', '1' go

CACI Proprietary Information | Date 22 Pre-Upgrade Tasks  2.8 Check Database Integrity Note: Repeat this section for each affected Sybase instance. Run dbcc checkstorage on all databases except tempdb by executing the following commands (replace with actual database name): −use go dbcc checkstorage −sp_dbcc_summaryreport

CACI Proprietary Information | Date 23 Pre-Upgrade Tasks  2.8 Check Database Integrity If the dbcc summary report returns any hard fault (i.e., the value under the Hard Faults column is greater than 0) on the database, execute the following dbcc commands on the databases to get additional information about the errors: −use go −dbcc checkdb go −dbcc checkalloc go −dbcc checkcatalog go Any errors from the above dbcc commands should be resolved before continuing with the upgrade. Contact the SPS Help Desk for assistance.

CACI Proprietary Information | Date 24 Pre-Upgrade Tasks  2.9 Calculate Space Requirement Note: Calculate the total space by summing spaces used of all affected instances. The upgrade process requires sufficient free disk space to hold database dump files. From the Windows workstation (Worksheet Item #12), log in to Sybase ASE ESD#2 Adaptive Server (PD²: Worksheet Item #4; MWS: Worksheet Item #8) through Interactive SQL or ISQL as “sa” (PD²: Worksheet Item #7; MWS: Worksheet Item #11) and execute the following command: select sum((high-low+1)*2/1024) from master.dbo.sysdevices where cntrltype = 0 go The result is the total disk space used by Sybase ESD#2 Adaptive Server devices in Megabytes (MB). Repeat the query for each affected Sybase instance and record the sum of all instances in Worksheet Item #17.

CACI Proprietary Information | Date 25 Pre-Upgrade Tasks  2.10 Create Database Backups Locate a backup directory on the Sybase ASE ESD#2 database server and record its path in Worksheet Item #18. Verify that the directory resides in a file system with sufficient free space to hold the backup files. The free space should exceed or be equal to Worksheet Item #17. Verify the Sybase ESD#2 operating system user (Worksheet Item #2) has the read, write, and execute privileges on the directory.

CACI Proprietary Information | Date 26 Pre-Upgrade Tasks  2.10 Create Database Backups Note: If there are multiple Sybase instances affected by the upgrade, create a subdirectory inside the main backup directory (Worksheet Item #18) for each instance. The subdirectory name must be unique for each instance, preferably using the instance name as the directory name. Repeat the backup instructions for each affected Sybase instance.

CACI Proprietary Information | Date 27 Pre-Upgrade Tasks  2.10 Create Database Backups From the Windows workstation (Worksheet Item #12), log in to Sybase ASE ESD#2 Adaptive Server through Interactive SQL or ISQL as “sa” and execute the following commands. All databases (including master) should be backed up except tempdb or any other temporary databases. dump database to '.ncp‘ with compression=5 go −Replace with the name of the database and with the designated backup location (Worksheet Item #18 and instance-specific subdirectory, if applicable). −Remember to include the trailing \ (Windows) or / (UNIX) as part of the. −Use “.ncp” as the file extension of the backup file to indicate this is a compressed dump with the new compression algorithm. −For a large database, you may need to stripe the backup into multiple dump files (up to 32) to speed up the process.

CACI Proprietary Information | Date 28 Pre-Upgrade Tasks  2.10 Create Database Backups Dump command examples: −Windows database server (assuming C:\sybase\backups is the backup directory): −dump database SPS_DODAAC to 'C:\sybase\backups\SPS_DODAAC.ncp' with compression=5 go −UNIX database server (assuming /sybase/backups is the backup directory): −dump database SPS_DODAAC to '/sybase/backups/SPS_DODAAC.ncp' with compression=5 go

CACI Proprietary Information | Date 29 Pre-Upgrade Tasks  2.10 Create Database Backups Save a copy of the “dump database” command (not the output) that was used to generate the dump files to an operating system file called “syb1503esd2backup.txt” on the Windows workstation. Record the location of this file in Worksheet Item #19. Note: If there are multiple Sybase instances affected by the upgrade, create a unique "syb1503esd2backup.txt" file for each instance. The file name can contain the instance name to distinguish each instance. Check the timestamps of the backup files and the backup server error log to ensure that each backup has run properly, has no errors, and is current.

CACI Proprietary Information | Date 30 Pre-Upgrade Tasks  2.11 Preserve Current Sybase JVM Module Path Parameter Note: Repeat this section for each affected Sybase instance. After the upgrade, the Sybase ASE ESD#4 system script will modify the Sybase JVM module path parameter back to the default value. The current JVM module path parameter value should be preserved in order to restore it after the upgrade. From the Windows Workstation (Worksheet Item #12), log in to the Sybase Adaptive Server (PD²: Worksheet Item #4; MWS: Worksheet Item #8) through Interactive SQL or ISQL as “sa” (PD²: Worksheet Item #7; MWS: Worksheet Item #11), and execute following commands:

CACI Proprietary Information | Date 31 Pre-Upgrade Tasks  2.11 Preserve Current Sybase JVM Module Path Parameter use master go if exists (select 1 from sysobjects where name='pd2_ase1503esd4_upg') begin drop table pd2_ase1503esd4_upg end go create table pd2_ase1503esd4_upg ( param_name varchar(255) not null, param_value varchar(255) not null) go insert into pd2_ase1503esd4_upg (param_name,param_value) select 'pca_jvm_module_path',jre_args_string_value from sybpcidb.dbo.pca_jre_arguments where jre_args_directive_index=5 and jre_args_name='pca_jvm_module_path' go

CACI Proprietary Information | Date 32 Pre-Upgrade Tasks  2.12 Dump Transaction Logs Note: Repeat this section for each affected Sybase instance. The transaction log of each database should be cleared to provide sufficient transaction space during the upgrade. −From the Windows Workstation (Worksheet Item #12), log in to the Sybase Adaptive Server (PD²: Worksheet Item #4; MWS: Worksheet Item #8) through Interactive SQL or ISQL as “sa” (PD²: Worksheet Item #7; MWS: Worksheet Item #11), and execute following commands (replace with actual database name): dump tran with no_log go This command must be executed for each database, including master and tempdb.

CACI Proprietary Information | Date 33 Pre-Upgrade Tasks  2.13 Checkpoint Databases Note: Repeat this section for each affected Sybase instance. From the Windows Workstation (Worksheet Item #12), log in to the Sybase Adaptive Server (PD²: Worksheet Item #4; MWS: Worksheet Item #8) through Interactive SQL or ISQL as “sa” (PD²: Worksheet Item #7; MWS: Worksheet Item #11), and execute following commands (replace with actual database name): use go checkpoint go This command must be executed for each database, including master and tempdb.

CACI Proprietary Information | Date 34 Pre-Upgrade Tasks  2.14 Stop Sybase Services Note: Repeat this section for each affected Sybase instance. All Sybase ASE ESD#2 services must be stopped. Refer to Appendix E: Start and Stop Sybase ASE Services for instructions. SPS Increment 2 does not use Sybase Monitor Server and by default does not install one. If Sybase Monitor Server is installed, shutdown the Monitor Server.

CACI Proprietary Information | Date 35 Pre-Upgrade Tasks  2.15 Prepare Database Server Windows −Verify the file system where the existing Sybase ASE ESD#2 is installed has sufficient space. −Sybase ASE ESD#4 will require at minimum 2GB for the install UNIX −Verify that the file system where Sybase ASE ESD#2 is currently installed has sufficient space. −The ASE ESD#4 installation needs 2 GB of free disk space.

CACI Proprietary Information | Date 36 Pre-Upgrade Tasks  2.16 Modify Sybase Java Directory Windows Server (32-bit and 64-bit) −To identify the current Sybase Java directory and delete the default Sybase Java directory on Windows server: −Log in to the Windows database server (Worksheet Item #1) as the Sybase ASE OS user (Worksheet Item #2). −Open a command prompt. −Execute set SYBASE_JRE6 −If the returned value ends with JRE-6_0_6_32BIT (32-bit) or JRE-6_0_6_64BIT (64-bit), leave Worksheet Item #20 empty. Otherwise, record the value of the SYBASE_JRE6 environment variable to Worksheet Item #20. This is the path of Sybase Java directory after applying the SPS Java update.

CACI Proprietary Information | Date 37 Pre-Upgrade Tasks  2.16 Modify Sybase Java Directory Windows Server (32-bit and 64-bit) −To identify the current Sybase Java directory and delete the default Sybase Java directory on Windows server: −Open Windows Explorer and locate the Sybase ASE installation directory (Worksheet Item #3). −Change directory to the Shared directory. −If the following directory exists, delete it: −Windows 32-bit: JRE-6_0_6_32BIT −Windows 64-bit: JRE-6_0_6_64BIT

CACI Proprietary Information | Date 38 Pre-Upgrade Tasks  2.16 Modify Sybase Java Directory UNIX Platforms −To identify the current Sybase Java directory and delete the default Sybase Java directory on the non-HP-UX PA-RISC UNIX platform: −Log in to the UNIX database server (Worksheet Item #1) as the Sybase ASE OS user (Worksheet Item #2). −Initialize Sybase ASE environment variables as described in Appendix D: Initialize Sybase Environment Variables in UNIX. −Execute the following command to identify the current Sybase Java directory: echo $SYBASE_JRE6 If the returned value ends with the following name, leave Worksheet Item #20 empty. −HP-UX Itanium: JRE-6_0_1 −Sun Solaris SPARC 64-bit: JRE-6_0_6 −Sun Solaris Intel 64-bit: JRE-6_0_6

CACI Proprietary Information | Date 39 Pre-Upgrade Tasks  2.16 Modify Sybase Java Directory UNIX Platforms −To identify the current Sybase Java directory and delete the default Sybase Java directory on the non-HP-UX PA-RISC UNIX platform: −Otherwise, record the returned value to Worksheet Item #20. This is the path of Sybase Java directory after applying the SPS Java update. −Execute the following command to change directory: cd $SYBASE/shared −Execute the following command to list the content of current directory: ls −Execute the following command to delete the default Sybase JRE directory: −HP-UX Itanium - rm -rf JRE-6_0_1 −Sun Solaris SPARC 64-bit, Sun Solaris Intel 64-bit - rm -rf JRE-6_0_6

CACI Proprietary Information | Date 40 Pre-Upgrade Tasks  2.17 Retrieve Sybase ASE ESD#4 Installers The Sybase ASE installer set includes Sybase ASE ESD#4 installer and Sybase ASE Post Configuration Installer. Sites have two options on retrieving the Sybase ASE ESD#4 installers. −Option 1: Request CDs −Option 2: Download from SPS Web Site

CACI Proprietary Information | Date 41 Pre-Upgrade Tasks  2.17 Retrieve Sybase ASE ESD#4 Installers Note: CACI and the JPMO only provide ASE ESD#4 software for Windows (32-bit and 64-bit), Sun Solaris SPARC (64-bit), Sun Solaris Intel (64-bit), and HP-UX Itanium (64-bit). For other platforms, please consult your Sybase license agreement. The Sybase ASE Post Configuration Installer is applicable to all Sybase ASE ESD#4 platforms and should be retrieved regardless of the Sybase ASE ESD#4 platform.

CACI Proprietary Information | Date 42 Pre-Upgrade Tasks  2.18 Unpack Sybase ESD#4 Installer Locate a temporary directory on the database server machine (Worksheet Item #1) that is accessible (read, write, execute) by the Sybase ASE operating system user (Worksheet Item #2) and record the full path in Worksheet Item #21. Create the ase1503esd4 directory inside the Worksheet Item #21 directory. Transfer the Sybase ESD#4 Installer file (excluding the Sybase ASE Post Configuration Installer file) on the Windows workstation (Worksheet Item #12) to the ase1503esd4 directory inside the temporary directory (Worksheet Item #21) on the Sybase ASE server machine (Worksheet Item #1). Verify the file is accessible by the Sybase ASE OS user (Worksheet Item #2). Note: When transferring files using FTP, binary transfer mode must be used.

CACI Proprietary Information | Date 43 Pre-Upgrade Tasks  2.19 Unpack Sybase ESD#4 Installer Confirm Worksheet Items #1 through #21 are completed.

CACI Proprietary Information | Date 44 Questions?