Migrating to Adaptive Server Enterprise 12.5 Adaptive Server Enterprise 12.
DOCUMENT ID: 34982-01-1250-01 LAST REVISED: Oct 2001 Copyright © 1989-2001 by Sybase, Inc. All rights reserved. This publication pertains to Sybase database management software and to any subsequent release until otherwise indicated in new editions or technical notes. Information in this document is subject to change without notice. The software described herein is furnished under a license agreement, and it may be used or copied only in accordance with the terms of that agreement.
Contents Introduction and Guide to Resources 1 In This Chapter 1 Chapters in the Migration Guide 1 Relating Documentation to Migration Phase 2 Other Sources of Information 3 Sybase Certifications on the Web 4 Migration Web Page 5 Classes 5 Consulting Services 5 If You Need Help 6 Analyze: Documenting Business Requirements 1 In This Chapter 1 Diagramming the System 1 Operational Business Requirements 3 Availability Requirements 3 Database Change Metrics 4 Database Dump Details 4 Maintenance Procedures 4 Ser
Database Devices 7 Databases and Segments 8 Dump Devices 8 Adaptive Server Objects 9 Gather Scripts to Create Objects 9 If You Don’t Have Scripts 9 Plan: Writing a Plan and Getting Ready to Migrate 1 In this Chapter 1 Review Documentation 1 Review the Upgrade Process 2 Special Cases: Migrating to 64-bit Operating System or Larger Page Size 3 Determine Migration Approach 4 Parallel With Replication 5 Cutover Without Replication 7 Phased Cutover 9 Write a Migration Plan 11 Build the Adaptive Server Environmen
Chapter Wide Columns and Data Truncation 19 Implement: Making Database Administration Changes 1 In This Chapter 1 If Your Version is 11.5 2 New Rollback Records 2 Optimizer Changes 3 Trace Flag 326 4 If Your Version is 11.5 or 11.9.x 4 Documentation Changes 5 Backup Server 5 Suspending Updates to Databases for Copying 7 New Unix File System Device Support 8 Changes to dbids 8 CIS Proxy Databases 9 ASE Plug-in for Sybase Central 9 The sybsyntax Utility 9 If Your Version is 11.5, 11.9.x, or 12.
Developing Fallback Procedures 5 Summary of Testing Techniques 5 Writing Performance Scripts 7 Write Benchmark Scripts 7 Drivers 8 Test Cycle: Summary of Tests 10 Test Cycle: Testing for Performance 11 Pre-Upgrade Single-User Tests 11 Pre-Upgrade Multi-User Tests 12 Test System Upgrade 13 Post-Upgrade Single-User Tests 13 Post-Upgrade Multi-User Tests 13 Worksheets for Your Current Environment 1 Adaptive Server Operational Worksheets 1 Operational Business Requirements 1 Backup and Restore Procedures 2 Data
Contents Parallel Migration Task List Example 9 Define Test/Acceptance Criteria—Regression Test Suites 10 Set Up Target Production Environment 11 Set Up Replication Server 11 Run Regression Test Suites 11 Upgrade Server B (Shadow) 12 Run Post-upgrade Regression Test Suites on ASE 12.5 (Server B) 13 Run User Acceptance Tests on ASE 12.5 (Server B) 13 Shift Production Users to Adaptive Server 12.5 (Server B) 14 Perform Final Steps 14 Cutover Migration Task List Example 14 Set Up ASE 12.
viii
CH A PTE R 1 Introduction and Guide to Resources In This Chapter This chapter gives an overview of the topics covered in this manual. In addition, it points you to a list of Sybase resources that can help you plan and execute a trouble-free migration to Sybase Adaptive Server EnterpriseTM 12.5.
Relating Documentation to Migration Phase The chapters in this manual are described in the following table: Chapter Contents Chapter 1, “Introduction and Guide to Resources” Chapter 2, “Analyze: Documenting Business Requirements” Chapter 3, “Analyze: Documenting Your Environment” Chapter 4, “Plan: Writing a Plan and Getting Ready to Migrate” A survey of resources available from Sybase and third-party vendors.
CHAPTER 1 Introduction and Guide to Resources Document Time period covered Range of tasks covered • What’s New in Adaptive Server Enterprise at http://manuals.sybase.com:80/o nlinebooks/groupas/asg1250e/whatsnew/@Gener ic__BookView Planning/preparation prior to upgrade Assessing current system • Migrating to Adaptive Server Enterprise 12.5 • Release Bulletins • TechNotes (ASE Migration Resources Web page at http://sybase.com/support/techd ocs/migration) • installation guide at http://manuals.sybase.
Sybase Certifications on the Web • Technical Library CD contains product manuals and is included with your software. The DynaText browser (downloadable from Product Manuals at http://www.sybase.com/detail/1,3693,1010661,00.html) allows you to access technical information about your product in an easy-to-use format. Refer to the Technical Library Installation Guide in your documentation package for instructions on installing and starting the Technical Library.
CHAPTER 1 5 ❖ Introduction and Guide to Resources Click an EBF/Update title to display the report. To create a personalized view of the Sybase Web site (including support pages) Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages. 1 Point your Web browser to Technical Documents at http://www.sybase.com/support/techdocs/ 2 Click MySybase and create a MySybase profile.
If You Need Help If You Need Help Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you cannot resolve a problem using the manuals or online help, please have the designated person contact Sybase Technical Support or the Sybase subsidiary in your area.
CH A PTE R 2 Analyze: Documenting Business Requirements In This Chapter In this chapter you begin the first phase of migration planning, documenting your environment. This chapter helps you organize business information required for an effective migration plan.
Diagramming the System • Protocols • Gateways • Routers, brouters, bridges For example, you can create a diagram like the this high-level view of the Acme Brokerage, a firm with business in several cities and two main computing centers: 8
CHAPTER 2 Analyze: Documenting Business Requirements You can write a high-level business description in addition to or instead of a diagram. Operational Business Requirements This section suggests ways to document your operational business requirements. You will use these baseline requirements to help you plan the migration and develop success criteria.
Operational Business Requirements Database Change Metrics For all databases, record: • Database size • Transaction log growth • Table rowcounts and daily change rate (number of inserts, deletes, and updates Database Dump Details Document your dump procedures, including times and devices, as in the following example: Database name master Frequency of database dumps every night TRD every night CIS ACT every night every night Frequency of transaction log dumps Dump device used TRD_tape1 TRD_tap
CHAPTER 2 Database name Frequency of dbcc checkdb and dbcc checktable CIS every weekend ACT every weekend Analyze: Documenting Business Requirements Frequency of dbcc checkalloc and dbcc tablealloc Frequency of update statistics different tables “Round-robin” every night different tables “Round-robin” every night different tables “Round-robin” every night different tables “Round-robin” every night Frequency of monitoring utilization every hour every hour Service Level Requirements Document app
Current Performance Metrics Xact priority Freq per user (per hour) Heavy OLTP P1 90 Stored Proc <2 sec <5 sec 1 sec avg 3 sec max bustTrade Heavy OLTP P1 10 Stored Proc <5sec <10 sec 2 sec avg 8 sec Max Trades reconcileTrades Batch P1 1 per day Embedd ed SQL/CO BOL <30 min <60 min 25 min avg 45 min max Trades listAccounts Light OLTP P1 180 <2 sec <5 sec 1 sec avg 2 sec max App name process (xact) name Trades addTrade Trades Type of proces sing Source code Stored Proc
CHAPTER 2 • • Disk I/O: • Use operating system monitors to measure I/Os per second per disk and controller, and I/O queue lengths per “time window” per server. • Use Sybase monitors to measure total I/Os, reads, and writes per second per Sybase device per “time window” per server. Concurrency: • • • Analyze: Documenting Business Requirements Use Sybase monitors to determine the average lock contention.
Additional Business Requirements • • 14 • Should the upgrade take place over the weekend • What staff is available: DBAs, system administrators? • What resources are available: Replication Servers, machines, tools, funding? Application and data server dependencies • Is more than one application using the same ASE? • Can all applications on a server be migrated? Are there any vendor issues? Are your third-party applications certified to run against ASE 12.
CH A PTE R 3 Analyze: Documenting Your Environment In This Chapter This chapter provides guidelines for documenting system hardware and software in the Adaptive Server production environment. This information is used to identify resource issues during the planning phase of the migration. See Appendix A, “Worksheets for Your Current Environment” for worksheets like the ones used in the examples in this chapter.
Hardware Configuration General Server Hardware List the following hardware information for every server machine: • Make and model • Your customer ID with the vendor • Technical support information • Telephone number • Support hours • Name of your account manager and his or her telephone or pager number • Vendor’s Web page CPU Resources per Machine List the following CPU information for each server machine: • Total number of processors and their speed • Number of processors available to ASE
CHAPTER 3 Controller Number 1 Physical Device name Make and Model Sun Sparc 20 Firmware Revision 1.00 Analyze: Documenting Your Environment Months in Service 6 Transfer Rate (Kb/sec) 10000 Transfe r Rate (Kb/sec ) Make and Model Firmware Revision Months in Service Controlle r Number Capacity (Mb) Throughput (I/Os per sec) c0t0d0 Seagate ST43401N 2.15 9 0 2900 80 1500 c0t0d1 Seagate ST43401N 2.15 12 0 2900 80 1000 c0t0d2 Seagate ST43401N Seagate ST43401N 2.
Physical Memory Utilization Physical Device Name Partition Number Used by (Sybase, UFS) c0t0d2 s0 s2 s3 disk label backup swap OS Mirror Device Name Device Name swap Capacity (mb) Cylinder Range 2 0–1 2900 2 – 2733 Network Configuration Use a worksheet like the one in the following example to show network interface card information for server and client machines: Physical Device Name c0t0d0 Make and Model Sun Sparc 5 Firmware Revision 1.5 Months in Service 9 c0t0d1 Sun Sparc 20 1.
CHAPTER 3 Analyze: Documenting Your Environment Name Runtime Memory Usage Calculation Operating System Adaptive Server OS-specific Add together these ASE parameters: total memory + additional netmem + extent i/o buffers Backup Server Add: size of the binary + (110Kb * number of stripes) sybmultbuf Replication Server Size of the binary only (attaches to BS shared memory) See “memory limit” parameter Monitor Server Gateways {List:} Size of the binary only Specific to the product - see product docum
Sybase Configuration • High availability software installed You may need to contact your operating system vendor to get system upgrades, recent patches, or help with problems, so make a note of the following operating system technical support information: • Telephone number • Support hours • Name of your technical account manager and his or her telephone or pager number • Vendor’s Web page Applications Make a list of applications to be migrated to ASE 12.5.
CHAPTER 3 Analyze: Documenting Your Environment General Information Record the following Sybase information: • Adaptive Servers and their SYBASE home directories • Components and release levels (including EBFs) • Names and location of scripts to rebuild database environment • All server configuration values; these can be listed by sp_configure. or found in the .cfg file. • Server runtime memory map: Run dbcc memusage during non-peak time or in single user mode.
Sybase Configuration Database Device Name Physical Device name CIS_log /dev/rdsk/c0t1d1s4 Mirrored Device Name Virtual Device Number Size (Mb) 6 420 Databases and Segments List of all segments and the objects on them. Use a worksheet like that in the following example: Database Name master DB Options Set none Size (Mb) 700 Segments Names default.system.log Device Name master Size (Mb) 3 master master none none 500 300 default.system.log default.system.
CHAPTER 3 Analyze: Documenting Your Environment Adaptive Server Objects Document the objects in your current Adaptive Server as described in the following sections: • Gather Scripts to Create Objects • If You Don’t Have Scripts Gather Scripts to Create Objects Locate or create the scripts necessary to recreate: • • Server level objects • Database devices • Configurations • Logins and security Database level objects, including: • Defaults, rules, and user datatypes • User databases • Users
Adaptive Server Objects Query Sybase System Tables The following system tables contain object information that you can use to create installation scripts: • sysdatabases • sysdevices • sysusages • sysobjects • sysusers • sysservers • syslogins • sysremotelogins See the System Administration Guide at http://manuals.sybase.com:80/onlinebooks/groupas/asg1250e/sag/@Generic__BookView for more details on system tables and objects.
CH A PTE R 4 Plan: Writing a Plan and Getting Ready to Migrate In this Chapter Now that you have collected data about your current system, you can write a migration plan. This chapter discusses migration methods and planning. In addition to choosing a migration method, you may need to bring your system resources to the level required by ASE 12.5 and make changes needed in applications and system administration procedures.
Review the Upgrade Process • The Release Bulletin at http://manuals.sybase.com:80/onlinebooks/groupas/asp1250e/@Generic__CollectionView;pt=asp1250e for your platform • The installation guide at http://manuals.sybase.com:80/onlinebooks/groupas/asp1250e/@Generic__CollectionView;pt=asp1250e for your platform For other documentation and resources, see Chapter 1, “Introduction and Guide to Resources.” Review the Upgrade Process Changes in the upgrade process were introduced in Releases 11.9.2 and 12.0.
CHAPTER 4 Plan: Writing a Plan and Getting Ready to Migrate Special Cases: Migrating to 64-bit Operating System or Larger Page Size As of release 11.9.3, Adaptive Server runs on 64-bit operating systems. As of 12.5, ASE allows you to create a server that uses a logical page size larger than 2K in order to store more data per page. These changes are described in What’s New in Adaptive Server Enterprise at http://manuals.sybase.
Determine Migration Approach Determine Migration Approach The best migration strategy for you depends on such factors as the cost of the effort, the type of business you do, the size of your databases, and available resources. The following table highlights the advantages and disadvantages of each migration approach: Approach Advantages Disadvantages When used Parallel With Replication Easy fallback to earlier release. You do not need to rebuild previous release databases.
CHAPTER 4 • Plan: Writing a Plan and Getting Ready to Migrate Phased Cutover Note This migration guide does not cover other parallel migration approaches; such as running two systems in parallel where you have to maintain both the systems simultaneously, or transaction duplication where you use one front-end to drive two parallel back-ends. These system operational approaches include factors too site-specific to detail effectively in this guide.
Determine Migration Approach • The earlier server cannot read release 12.5 backup files. You need to create bcp or other scripts to move tables back to pre-release 12.x. • Do not apply schema enhancements. For information about scheduling backups of user databases, see the System Administration Guide at http://manuals.sybase.com:80/onlinebooks/groupas/asg1250e/sag/@Generic__BookView. Additional tips: Application test suite • Upgrade Replication Server first.
CHAPTER 4 Plan: Writing a Plan and Getting Ready to Migrate Be sure to account for any increased release 12.5 memory requirements that apply to your configuration. For more information, see: • The installation guide at http://manuals.sybase.com:80/onlinebooks/groupas/asp1250e/@Generic__CollectionView;pt=asp1250e for your platform. It gives basic RAM requirements. • Chapter 6, “Implement: Making Database Administration Changes”.
Determine Migration Approach You can use dump database or bcp out before an upgrade to prepare for fallback. Plan a way to capture transactions after cutover to be used in case of fallback. If you go into production and then need to back off, you will have to restore all the transactions that occurred after the last dump/load. Application test suite For a development system, simple validation may be adequate.
CHAPTER 4 • Plan: Writing a Plan and Getting Ready to Migrate Information on how to configure memory for performance in the Performance and Tuning Guide at http://manuals.sybase.com:80/onlinebooks/groupas/asg1250e/perf/@Generic__BookView. Note For a production system, execute the performance suite during off hours. Scheduling For a development system, you may want to add a short period to the development schedule for release 12.5 issues.
Determine Migration Approach See Chapter 7, “Test: Ensuring Stability and Performance” for more information on testing. Bridging There should not be any user impact during migration. The more stringent the validation test is, the less likely you will have bridging issues. The earlier server cannot read release 12.5 backup files. You need to create bcp or other scripts to move tables back to pre-release 12.5. Note Do not use release 12.5 schema enhancements until the conversion succeeds.
CHAPTER 4 Plan: Writing a Plan and Getting Ready to Migrate Write a Migration Plan Produce a project plan which documents: • Migration strategy—Which method is most appropriate for your site. • Fallback—What to do in case the migration fails. The plan you evolve will be site-specific, but some general issues are discussed in Chapter 7, “Test: Ensuring Stability and Performance”. • Application test suite—What validation and performance testing to perform for acceptance.
Build the Adaptive Server Environment • Update Applications and System Administration Procedures • Create Migration Scripts • Create a test environment. See Chapter 7, “Test: Ensuring Stability and Performance” for more information on the test environment Update Hardware Resources Evaluate hardware resource needs according to your migration approach. For example, if you plan to use the parallel-with-replication method.
CHAPTER 4 Plan: Writing a Plan and Getting Ready to Migrate Note If you need to perform an operating system upgrade, do so before migrating. Test the new system to be sure it’s working properly to avoid introducing unrelated errors into the migration process. Review Adaptive Server Interoperability with Other Sybase Products To ensure that the versions of other Sybase products in use at your site are compatible with Adaptive Server 12.5, see Technical Documents at http://sybase.
Build the Adaptive Server Environment Create Migration Scripts Using the scripts you located, wrote, or reverse engineered in Chapter 2, “Analyze: Documenting Business Requirements”, write or edit the scripts that will create your 12.5 Adaptive Server installation.
CH A PTE R 5 Implement: Making Required Application Changes In This Chapter This chapter and Chapter 6, “Implement: Making Database Administration Changes” divide technical issues into those relevant to application developers and those relevant to database administrators. However, many issues are not exclusive to either of these roles and you should check both chapters whatever your role. This chapter covers those issues that may affect the execution of applications or that might require coding changes.
If Your Version is 11.5 If Your Version is 11.5 This sections covers the following topics: • Changes to Locking • Changes to Error Checking • 11.9.2 Query Processing Changes Changes to Locking Release 11.9.2 introduced several changes to locking, including support for row-level and page-level locking. Some of these changes require you to make application or configuration changes to avoid performance issues. Data-only Locking Sybase now supports new locking methods called “data-only” locking.
CHAPTER 5 Implement: Making Required Application Changes • Bulk copy into data-only-locked tables requires the version of bcp and the bulk copy libraries shipped with Adaptive Server version 11.9.2. Older versions of bcp and the bulk-copy libraries can still be used to copy into allpages-locked tables. See the Release Bulletin for the required version number.
If Your Version is 11.5 Workarounds If deadlocks are creating problems, consider converting the table to use datarows locking. If deadlocks or excessive numbers of locks are creating problems, consider using the lock table command to acquire an exclusive table lock before you begin the transaction. Changes to Error Checking As of version 11.5.1, ASE performs more rigorous checking of permissionsrelated access to database objects. This change was not documented in 11.5 documentation.
CHAPTER 5 Implement: Making Required Application Changes as select * from mary.sales_prospects However, this user cannot execute the procedure; the attempt to execute returns a permissions error. Stored Procedure Existence Checks in Command Batches In pre-11.5 versions, an entire batch fails during compilation if a stored procedure named in the batch does not exist. In 11.5.x and later versions, the existence of stored procedures included in batches is not checked until execution time.
If Your Version is 11.5 • Those permissions set with the grant command • Permissions that depend on roles (such as sa_role or SSO_role) or on status as the DBO (database owner) Pre-11.5.
CHAPTER 5 Implement: Making Required Application Changes Pre-11.5.
If Your Version is 11.5 Pre-11.5.1 error number 7730 Changed to: 10319 Type of message Failure for set role commands; new message indicates that the role is not granted to the user 7731 10320 Failure for set role commands; new message indicates that the role is not granted to the user in current database 7964 10302 7983 10354 Permission failure for dbcc commands Permission failure for 9503 10353 Role required message.
CHAPTER 5 Column Level Statistics Implement: Making Required Application Changes • Table/Index Level Statistics • Changes to the update statistics Command The sysstatistics table contains statistics related to the data in a column. Column level statistics describe the distribution of values in the column (and in the case of multicolumn density values, a set of columns).
If Your Version is 11.5 Aggregate Optimization Aggregate optimization was introduced in ASE 11.9.x. This allows the optimizer to factor in an index on the column referenced in an aggregate function. Sometimes the optimizer can be overly optimistic in costing this index and may choose it when it is not the best choice.
CHAPTER 5 Implement: Making Required Application Changes This trace flag is well-documented in New Functionality in 11.9.2 at http://manuals.sybase.com:80/onlinebooks/groupas/asg1192e/asefun92/@Generic__BookView and the sections on query tuning in the Performance and Tuning Guide at http://manuals.sybase.com:80/onlinebooks/groupas/asg1200e/aseperf/@Generic__BookView. Syntax for Trace Flag 302 When using trace flag (302) to see optimizer information, use trace flag 3604 to send output to the client.
If Your Version is 11.5 or 11.9.x indid 2 scan selectivity 0.983249, filter selectivity 0.983249 590512 rows, 45991 pages, index height 2, Data Row Cluster Ratio 1.000000, Index Page Cluster Ratio 0.998609, Data Page Cluster Ratio 1.
CHAPTER 5 • Implement: Making Required Application Changes Inner joins, in which the joined table includes only the rows of the inner and outer tables that meet the conditions of the on clause. The result set of a query that includes an inner join does not include any null supplied rows for the rows of the outer table that do not meet the conditions of the on clause.
If Your Version is 11.5 or 11.9.x See the section New Unix File System Device Support in Chapter 6 of this manual. See also the sections on disk init and sp_deviceattr in the Reference Manual at http://manuals.sybase.com:80/onlinebooks/groupas/asg1250e/refman/@Generic__BookView for more information. 12.0 Query Processing Changes The query processing and optimizer changes introduced in ASE 12.0 are less extensive than those in 11.9.2, and should provide improved performance for most sites.
CHAPTER 5 Implement: Making Required Application Changes select * from lineitem, part where ((p_partkey = l_partkey and l_quantity >= 10) or (p_partkey = l_partkey and l_quantity <= 20) ) becomes select * from lineitem, part where ((p_partkey = l_partkey and l_quantity >= 10) or (p_partkey = l_partkey and l_quantity <= 20) ) and (p_partkey = l_partkey) and (l_quantity >= 10 or l_quantity <= 20) The addition of the conjuncts adds usable SARGs for the optimizer.
If Your Version is 11.5 or 11.9.x Adaptive Server can capture query text and save an abstract plan for a query in a new system table called sysqueryplans. Using a rapid hashing method, incoming SQL queries can be compared to stored query text, and if a match is found, the saved abstract plan is used to execute the query. For more information on abstract query plans, see the Performance and Tuning Guide at http://manuals.sybase.com:80/onlinebooks/groupas/asg1250e/perf/@Generic__BookView.
CHAPTER 5 Implement: Making Required Application Changes If a pattern match is found in the cell boundaries then the selectivity is estimated to be the sum of the weights of all cells with a pattern match. In either case the resulting selectivity estimate will be more accurate than in previous versions. This also applies to queries with like clauses of the type like “_abc”, or like “[ ]abc”. If Your Version is 11.5, 11.9.x, or 12.
If Your Version is 11.5, 11.9.x, or 12.0 New Reserved Words Reserved words can only be used by ASE. New ASE objects and commands result in new reserved words being added with every release. To see the new reserved words for ASE 12.0, see the Adaptive Server Reference Manual at http://manuals.sybase.com:80/onlinebooks/groupas/asg1200e/aserefmn/@Generic_BookView. You must change all object names that contain reserved words before you upgrade.
CHAPTER 5 Release Implement: Making Required Application Changes New reserved words 11.9.2 exp_row_size reservepagegap lock readpast reorg 12.0 proxy proxy_table key jar join install remove identity_gap quiesce modify 12.5 deterministic func function inout new out output stringsize Note The Sybase procedures for detecting reserved words in object names cannot be used to find them in scripts and applications. You need to check scripts and applications separately.
If Your Version is 11.5, 11.9.x, or 12.0 • Using New Wide Data Sizes with Open Client • Wide Columns and Optimizer Statistics • Wide Columns with col_length() and datalength() Change in Truncation Behavior Previous releases of Adaptive Server had a column-length limit of 255 bytes. The 12.5 release of Adaptive Server allows you to create columns using char, varchar, binary, and varbinary data up to 16294 bytes long, depending on the logical page size your server uses.
CHAPTER 5 Implement: Making Required Application Changes To see whether you can enable wide data sizes for your client software, go to the section below that describes your system: Both ASE and Open Client are Version 12.5 Open Client Is an Older Version • Both ASE and Open Client are Version 12.5 • Open Client Is an Older Version • ASE 12.5 Connects to a Remote Pre-12.5 Server You should not have any problems if both Adaptive Server and Open Client are at version 12.5.
If Your Version is 11.5, 11.9.x, or 12.0 Wide Columns with col_length() and datalength() The commands col_length() and datalength() are “built-in” Transact-SQL functions that return database information. These functions can now return values greater than 225. If you use one of these functions in a query and assign the result to a variable, be sure to make the variable large enough to hold the value.
CH A PTE R 6 Implement: Making Database Administration Changes In This Chapter This chapter discusses changes to Adaptive Server system administration that can cause problems if you are not prepared for them. It does not attempt to cover new features or changes that are not likely to cause surprises. For a comprehensive listing of changes and new features, see What’s New in Adaptive Server Enterprise at http://manuals.sybase.com:80/onlinebooks/groupas/asg1250e/whatsnew/@Generic__BookView.
If Your Version is 11.5 If Your Version is 11.5 This section covers the following topics: • New Rollback Records • Optimizer Changes • Trace Flag 326 New Rollback Records New rollback records added to the transaction log in 11.9.2 may require you to add more space to the syslogs system table. Rollback records are logged whenever a transaction is rolled back. For every update record that is rolled back, a rollback record is logged.
CHAPTER 6 Implement: Making Database Administration Changes Optimizer Changes ASE 11.9.2 introduced major changes in the way the server keeps statistics and optimizes queries. These changes were aimed at increasing granularity in the statistics kept by the server, improving query plans, and producing better performance. Changes introduced in 11.9.
If Your Version is 11.5 or 11.9.x However, be cautious about adding new statistics to the production environment until you have determined your needs and tested any changes. Not all new statistics are needed or helpful in every environment. Warning! Making unneeded changes to statistics may adversely affect performance. In addition, running the update statistics command with incorrect parameters may change the number of steps in a histogram and impact performance. Apply changes first in a test environment.
CHAPTER 6 Implement: Making Database Administration Changes Documentation Changes ASE 12.0 includes several new manuals that describe separately-licensed Adaptive Server features such as Java, High Availability, and Distributed Transaction Management.
If Your Version is 11.5 or 11.9.x Stripes In earlier versions, Backup Server could dump to a maximum of 32 stripes, either disk or tape. In 12.0, more stripes are available. The maximum number of stripes it can use is equal to the maximum number of Open Server threads it can create. Note The documentation for ASE 12.0 still refers to 32 stripes, but this is an error. Network Connections The maximum number of network connections a local Backup Server can originate is limited by Open Server to 9118.
CHAPTER 6 Implement: Making Database Administration Changes You must configure the local and remote Backup Servers at startup by providing the appropriate values to the command line options. A remote dump to greater than 25 stripes with the local and remote Backup Servers started with default configuration will fail because the maximum number of network connections that Backup Server can originate (specified by the -N option) is by default 25.
If Your Version is 11.5 or 11.9.x New Unix File System Device Support In release 12.0, Sybase introduced the dsync option of the disk init command. This option guarantees that writes to database devices placed on Unix file systems are performed by the operating system as soon as the server flushes the data. In the past, the server might log a write, but the operating system buffered the data. If the system went down, the server had no way to recover the buffered data that was lost.
CHAPTER 6 Implement: Making Database Administration Changes CIS Proxy Databases In 12.0, HA creates databases with names like “__pxy”. As a result, you cannot drop proxy databases with similar names ending in “pxy” from Adaptive Servers configured with Sybase Failover in a high availability system. If you attempt to drop these proxy databases, Adaptive Server issues an error message. This is expected behavior.
If Your Version is 11.5, 11.9.x, or 12.0 • New Reserved Words • Configuration Parameters • Increased Memory • New Storage for text and image Data Changes to Documentation The following changes were made to the Adaptive Server documentation set: • Managing and Monitoring Adaptive Server Enterprise has been discontinued. • The Utility Guide is now a generic book that includes all utilities, regardless of platform.
CHAPTER 6 Implement: Making Database Administration Changes sybsystemdb The sybsystemdb database is used for the spt_values table and two-phase commits. Before ASE 12.5, this database was not required. The database is automatically created on the master device by the configuration utility. Because this database may have a lot of activity and use a lot of log space, we strongly recommended that you create sybsystemdb on another device prior to upgrade or move it to another device after upgrade.
If Your Version is 11.5, 11.9.x, or 12.0 New Database and Table Limits This section covers changes in table and database limits: • Maximum Number of Users and Logins • New Table Limits Maximum Number of Users and Logins The maximum number of logins to the server and users to the database has been increased. ASE 12.
CHAPTER 6 User-visible object (sizes in bytes) Row length Fixed-length column Variable-length column Size of index key Implement: Making Database Administration Changes 2K logical page APL=1960 4K logical page APL=4008 8K logical page APL=8104 16K logical page APL=16296 DOL=1958 DOL=4006 DOL=8102 DOL=16294 APL=1960 APL=4008 APL=8104 APL=16296 DOL=1958 DOL=4006 DOL=8102 DOL=16294 APL=1947 APL=3987 APL=8067 APL=16227 DOL=1952 DOL=4000 DOL=8096 DOL=16288 APL=600 APL=1250 APL=260
If Your Version is 11.5, 11.9.x, or 12.0 Release 12.5 New reserved words deterministic func function inout new out output stringsize You must change all object names that contain reserved words before you upgrade. You must also change those names in your procedures, SQL scripts, and applications before you can run them against the upgraded server. Use the reserved word check in sqlupgrade, which you can run without starting the upgrade, to check object names.
CHAPTER 6 Implement: Making Database Administration Changes stack size The default value of the stack size parameter has increased over the last several releases. While stack size varies from platform to platform, the changes on Solaris (shown in the table below) illustrate the increase in stack size requirements with successive versions: Server Version Minimum Stack Size 11.0.x 24576 (24K) 11.5 34816 (32k) 11.9.2 34816 (32k) 12.0 46090 (45K) - 32-bit 86016 (84K) - 64-bit 12.
If Your Version is 11.5, 11.9.x, or 12.0 Increased Memory ASE 12.5 uses more memory than previous releases. ASE now allocates more memory for the dataserver, procedure cache, and named caches. If you do not increase physical and/or shared memory, the additional needed memory will be taken from the default data cache, possibly affecting performance. Check the installation guide at http://manuals.sybase.com:80/onlinebooks/groupas/asp1250e/@Generic__CollectionView;pt=asp1250e for minimum memory requirements.
CHAPTER 6 Implement: Making Database Administration Changes buildmaster Command Obsolete ASE 12.5 no longer uses the buildmaster command. Instead, the dataserver command or sqlsrvr.exe for NT (the ASE product binary) has a new flag, -b, to run in build mode. Use the dataserver -b command where you used buildmaster in the past.
If Your Version is 11.5, 11.9.x, or 12.
CH A PTE R 7 Test: Ensuring Stability and Performance In This Chapter This chapter will help you evaluate testing methods and develop a testing plan.
Setting Up the Test Environment • The test and production systems are stable and the data is safe. • The upgrade is successful and does not adversely impact the production system. Setting Up the Test Environment Ideally, you should set up a dedicated hardware configuration (including subnets) and Adaptive Server exactly like your production system.
CHAPTER 7 Test: Ensuring Stability and Performance Use backups or the bcp scripts to populate your test databases. Note When you create a new database and then load bcp files, you reduce the fragmentation that may be present in the production system and change the performance characteristics of the database.
Prioritizing Applications to be Tested You need to make adjustments when you have less disk space or memory in the test system. Scale down databases proportionally, while retaining the same data distributions so optimizer decisions remain constant. Scale down memory to ensure consistent I/O rates. Reproduce data layout across available devices as closely as possible. If you use fewer CPUs, adjust transaction arrival rates (that is, load) and concurrent users proportionally.
CHAPTER 7 • Test: Ensuring Stability and Performance A phased cutover is subject to the highest performance expectations. Some performance tuning of the production workload after cutover of the production server may be best. You can time the production server cutover to occur as soon as performance gains are acceptable and testing is successful. See Chapter 4, “Plan: Writing a Plan and Getting Ready to Migrate” for information on migration methods.
Summary of Testing Techniques Technique Description Advantages Disadvantages Ad hoc testing Manually walk through important application processes, screens, and reports • Easy to implement • For complex applications, code coverage is too small • Tests front-end applications and back-end servers • Difficult to distinguish front-end and back-end bottlenecks if response time is a determining factor • Impossible to obtain production multiuser load, which misses concurrency and capacity issues altogethe
CHAPTER 7 Test: Ensuring Stability and Performance Technique Description Advantages Disadvantages Transaction generation Thin client to simulate user execution of transactions • Strong multiuser load testing • May increase development time for creating multiuser test simulations, though learning and development curve generally less than keystroke capture tools • Focus on back-end server issues • Adds time for debugging test harness to prevent skewed results Production load capture Using tools t
Writing Performance Scripts • Write code to process result set(s) • Name each transaction explicitly (for example, “begin tran cust_update”) to make it easier to identify in system procedures and tables • For a stored procedure-based system, verify the parameters that make the stored procedures work. If the parameters need to vary for a meaningful test, add the necessary logic. Volume is critical in performance simulation.
CHAPTER 7 Test: Ensuring Stability and Performance Result Handling You can capture query results by fetching the entire result set back to the client and binding it to local variables. Outputting results to a file may increase your time by requiring additional file I/O and operating system buffering. Time Measurement Time measurement is especially important in multi-tiered applications where a bottleneck could occur at any level. Generally, you should time database transactions, not business functions.
Test Cycle: Summary of Tests Test Cycle: Summary of Tests This section summarizes a complete test cycle, with tests that target specific issues, including old and new functionality, performance under multi-user loads, integration, and user acceptance.
CHAPTER 7 Test: Ensuring Stability and Performance Stage Purpose Best Technique Final migration plan testing • Ensure that you are fully prepared by walking through the upgrade/migration plan. Walk through every upgrade step, including fallback strategies • Verify that fallback procedures work. • Identify and test the contingencies. Test Cycle: Testing for Performance This section expands on performance benchmarking before and after upgrade.
Test Cycle: Testing for Performance • Data and data distribution problems. Check data layout and be sure that these match the productions system. • Index definitions. Verify that your reindexing scripts worked. Using sp_helpindex, compare the index definitions of the production and test systems. Resolve any problems before going on. I/O Verify that the test server is performing the same amount of I/O. Physical and logical I/O should be in the same proportion as in the production system.
CHAPTER 7 Test: Ensuring Stability and Performance Test System Upgrade Perform the upgrade on the test system following the instructions in the installation guide. Be sure to perform all steps so that the test upgrade is a walkthrough of the real upgrade. Make the memory and disk space changes you determined that you needed in Chapter 6, “Implement: Making Database Administration Changes”. However, do not change your Adaptive Server configuration to use new features at this time.
Test Cycle: Testing for Performance Untimed Benchmarks In multi-user mode, run untimed benchmarks as often as necessary, capturing response time and throughput metrics. Resolve: • Differences, such as cache hit rate, to the pre-upgrade state • Bottlenecks • Other problems or mistakes Be sure that you have enough default data cache after the upgrade. Tune as needed to fix problems. Between runs, restore your databases from backup or perform a quick reset.
A P PE N DI X A Worksheets for Your Current Environment This appendix provides guidelines and sample worksheets for gathering information that will help you in planning for migration. The topics are: • Adaptive Server Operational Worksheets • Data Architecture Worksheet • Adaptive Server Infrastructure Worksheets As part of migration planning, see the ASE Migration Resources Web page at http://sybase.com/support/techdocs/migration for current documents.
Adaptive Server Operational Worksheets Database Name Operational Hours Maximum Downtime Comments Backup and Restore Procedures This worksheet is helpful for a general survey of your backup and restore procedures: 94
APPENDIX A Task Yes/No Worksheets for Your Current Environment Comments Are backup and recovery procedures documented? Are automated dump procedures in place? What is the number of generations of dumps? Are dumps kept offsite? Are maintenance activities documented? What is the frequency of ASE error log scanning? Is database space utilization monitored? Has database capacity planning been performed recently? Database Dump Details Detailed backup and restore information is helpful for defining success
Adaptive Server Operational Worksheets Database Name Frequenc y of Database Dumps Dump Device Used Frequency of Transaction Log Dumps Dump Device Used Comments Maintenance Procedure Details Use the following worksheet to record detailed maintenance information: Database/O bject Name 96 Frequency of dbcc checkdb/checkta ble Frequency of dbcc checkalloc/tableal loc Frequency of update statistics Frequency of Monitoring Space Utilization
APPENDIX A Database/O bject Name Frequency of dbcc checkdb/checkta ble Frequency of dbcc checkalloc/tableal loc Worksheets for Your Current Environment Frequency of update statistics Frequency of Monitoring Space Utilization Data Architecture Worksheet Documenting the flow of information is discussed in Chapter 2, “Analyze: Documenting Business Requirements”.
Data Architecture Worksheet Applicatio n Name Type of Applicatio n Tool Used to Write Applicatio n Where Client Runs Number of Concurre nt Users DBs Accessed Maximum Downtime (per day) Average Response for Priority 1 Production Performance Metrics Measure current production performance metrics, using operating system monitors, for the following: • CPU Measure the average and maximum CPU utilization (aggregate and per CPU on SMP servers) per “time window” (online, batch, and so on) per server.
APPENDIX A • Worksheets for Your Current Environment • Measure I/Os per second per disk and controller, and I/O queue lengths per “time window” per server. • Also measure total I/Os, reads, and writes per second per Sybase device per “time window” per server. Concurrency Determine the average lock contention. You can use sp_who to determine the processes currently running, and sp_lock to find out which current processes hold locks.
Adaptive Server Infrastructure Worksheets Process (Xact) Name Process Type (OLTP, batch) Xact Priority Freque ncy per User (per hour) Source Code Type (stored procedure, ESQL, etc.) Average Respons e Time Required Maximu m Respons e Time Required Current Average and Maximu m Respons e Time Note To quickly identify response time problems, save showplan output for all critical transactions.
APPENDIX A Worksheets for Your Current Environment Record this information for both the production and development environments. Host Configuration This section provides worksheets for host configuration.
Adaptive Server Infrastructure Worksheets CPU Other CPU-intensive processes/threads: Processes/threads bound to specific CPUs: Processes/threads run at high priority: Physical Memory Usage List all the major processes and memory requirements running on each server.
APPENDIX A Application Worksheets for Your Current Environment Runtime Memory Usage Open Servers Include: • Backup Server • sybmultbuf • Replication Server • Monitor Server • Gateways (list) Other applications Total memory required Total memory installed Disk I/O Configuration General disk information can help with firmware incompatibilities and capacity planning.
Adaptive Server Infrastructure Worksheets Physical Device Name Make and Model Firmwar e Revision Months in Service Controll er Number Capacity (MB) Through -put (I/Os per second) Transfer Rate (KB per second) The following disk layout information can help in case redistribution is required, for load balancing, and for capacity planning. Physical Device Name Partition Number Used by (Sybase, UNIX File System, etc.
APPENDIX A Logical Volume Device Member Disk Partitions Used by (Sybase, UNIX File System, etc.) Sybase Device Worksheets for Your Current Environment Mirror Logical Device Capacity (MB) Stripe Width (MB) Network Configuration Network layout information can help with firmware incompatibilities, MTBF, and capacity planning.
Adaptive Server Infrastructure Worksheets Tape Configuration Tape layout information can help with firmware incompatibilities, MTBF, and capacity planning. Physical Device Name Make and Model Firmware Revision Months in Service Capacit y (MB) Operating System Configuration Detail the operating system.
APPENDIX A Worksheets for Your Current Environment Server Hardware Technical account manager: • Name • Phone number(s) • Pager number Adaptive Server Configuration Document general information about the ASE configuration.
Adaptive Server Infrastructure Worksheets Run dbcc memusage on ASE during an off-peak time or in single-user mode. Usage MB 2K Pages Bytes Configured memory Code size Kernel structures Server structures Page cache Proc buffers Proc headers Number of page buffers Number of proc buffers Database Devices Database device information can help in case redistribution is required, load balancing, and capacity planning.
APPENDIX A Database Device Name Physical Device Name Worksheets for Your Current Environment Virtual Device Number Capacity (2K Pages) Mirrored Device Name Databases and Segments Database and segment information can help with load balancing and capacity planning.
Adaptive Server Infrastructure Worksheets Dump Devices Dump device information can help with load balancing and capacity planning.
A P PE N DI X B Sample Migration Task Lists This appendix provides the following samples: • Sample Task List Template • General Migration Task List Example • Parallel Migration Task List Example • Cutover Migration Task List Example • Staged Cutover Task Overview Note These examples are illustrations. They are not step-by-step procedures that must be followed by everyone. Every migration is unique and you need to write a plan appropriate for your site.
General Migration Task List Example General Migration Task List Example The following general task list shows typical migration tasks, with differing details for the install/load approach (install an new server, then load compatible dumps from earlier server) and one using the upgrade approach (run the upgrade program on the current databases). Your own migration task lists may differ in detail and order.
APPENDIX B Sample Migration Task Lists 13 Update configuration document. Gather Business Requirements 1 Define business requirements. 2 Define constraints. 3 Define application dependencies. 4 Define dataserver dependencies. 5 Prioritize applications. 6 Identify vendor issues. 7 Review requirements document. 8 Update requirements document. Conduct Compatibility Analysis 1 Analyze hardware compatibility. 2 Analyze operating system compatibility.
General Migration Task List Example 5 Define migration downtime impact. 6 Notify affected departments. 7 Revise implementation plan. 8 Obtain user signoff for migration and implementation. Migration Preparation Write Test Plans and Test Scripts 1 Write system functional tests. 2 Write integration tests. 3 Write stress tests. 4 Write user acceptance tests. 5 Review test plans. 6 Update test plans. 7 Create test scripts for each phase of testing.
APPENDIX B Sample Migration Task Lists 2 Design and develop file system configuration for devices. 3 Create database device scripts. 4 Prepare security, login, and password corrections. 5 Create security scripts. Design and Develop Database Migration Scripts 1 Create database scripts. 2 Create database object creation scripts. 3 Create database security scripts. 4 Modify/create system administration scripts.
General Migration Task List Example 3 Configure file system. 4 Complete installation/upgrade preparation from installation guide. 5 Install Adaptive Server, Backup Server, and Open Client. Perform Server Migration 1 Restrict access to systems and servers. 2 Create database devices. 3 Execute server security and other scripts. Perform Database Migration 1 Execute database creation scripts 2 Create database partitions and segments.
APPENDIX B Sample Migration Task Lists 3 Analyze and correct application changes. 4 Configure applications to access new server. 5 Perform preliminary tuning. 6 Allow user access to system and server. 7 Insure no access to obsolete files. 8 Notify users of availability. Implement Migration (Using Upgrade Technique) Upgrade Adaptive Server 1 Verify target system readiness. 2 Configure file system. 3 Install software. 4 Use sqlupgrade to perform upgrade. 1 Run dbcc commands.
General Migration Task List Example Migration Quality Assurance Perform System Tests 1 Perform functional tests. 2 Compare functional test results to baseline. 3 Analyze functional test results. 4 Perform corrective actions. 5 Retest as necessary. 6 Document functional test results. 7 Obtain user signoff on functional test results. Perform Integration Tests 1 Perform integration tests. 2 Compare integration test results to baseline. 3 Analyze integration test results.
APPENDIX B Sample Migration Task Lists Perform User Acceptance Tests 1 Perform acceptance tests. 2 Compare acceptance test results to baseline. 3 Analyze acceptance test results. 4 Perform corrective actions. 5 Retest as necessary. 6 Document acceptance test results. 7 Obtain user signoff on acceptance test results. Perform Production Data Refresh 1 Schedule production data cutover. 2 Extract production data. 3 Move data to target.
Parallel Migration Task List Example • Define Test/Acceptance Criteria—Regression Test Suites • Set Up Target Production Environment • Set Up Replication Server • Run Regression Test Suites • Upgrade Server B (Shadow) • Run Post-upgrade Regression Test Suites on ASE 12.5 (Server B) • Run User Acceptance Tests on ASE 12.5 (Server B) • Shift Production Users to Adaptive Server 12.
APPENDIX B Sample Migration Task Lists Set Up Target Production Environment 1 Identify physical drive configuration for Server A (production) and Server B (shadow). 2 Configure physical drives. 3 Perform a dump of the production environment. 4 Install older system on Server B. 5 Configure older system on Server B, to duplicate Server A. 6 Update the interfaces. 7 Create the databases. 8 Load the Server A dump on Server B. 9 Run dbcc commands (checktable, checkalloc, checkcatalog).
Parallel Migration Task List Example 2 Iteratively perform back-end regression testing. 3 Monitor and capture system dynamics (sp_who, sp_lock, statistics io...). 4 Verify and document older system regression test. Front-end simulation regression test suite 1 Iteratively do front-end simulation regression tests. 2 Monitor and capture system dynamics (sp_who, sp_lock...). 3 Verify and document older system regression test.
APPENDIX B Sample Migration Task Lists 10 Recycle ASE. Run Post-upgrade Regression Test Suites on ASE 12.5 (Server B) Back-end regression test suite—production loads 1 Perform back-end regression testing. 2 Monitor and capture system dynamics (sp_who, sp_lock, statistics io...). 3 Verify and document regression test. Front-end simulation regression test suite 1 Perform front-end simulation regression testing. 2 Monitor and capture system dynamics (sp_who, sp_lock...).
Cutover Migration Task List Example Shift Production Users to Adaptive Server 12.5 (Server B) 1 Ensure that there is no production activity. 2 Perform a dump from Server A (production). 3 Load the dump onto Server B (shadow). 4 Run dbcc commands (checktable, checkalloc, checkcatalog) on the older release databases just loaded to Server B. Be sure to verify the dbcc log and error log 5 Switch the IP address, and rename the machines and servers. 6 Run user testing and verification.
APPENDIX B Sample Migration Task Lists • Run Regression Test Suites on Older Release Test System • Upgrade Test System to Release 12.5 • Run Regression Test Suites on Release 12.5 Test System • Run User/Acceptance Tests on Release 12.5 Test System • Execute Fallback Procedures on Test System • Upgrade Production Server to ASE 12.5 • Perform Final Steps Set Up ASE 12.
Cutover Migration Task List Example 2 Capture and map SQL for target user functions. 3 Encapsulate SQL for user functions. 4 Create front-end simulated test suite (showplan, stat io, and stat time wrappers). Front-end regression test suite 1 Identify front-end test scenarios. 2 Understand front-end application and acceptance/test procedures. 3 Document functional test approach. 4 Compose front-end test mix matrix.
APPENDIX B Sample Migration Task Lists 3 Make the “go/no go” call for the test system. 4 Verify and document the regression test. 5 Verify performance and functions on the older release test server. Upgrade Test System to Release 12.5 1 Perform a dump of the current system’s databases. 2 Before the upgrade, run dbcc commands (checktable, checkalloc, checkcatalog). 3 Alter the sybsystemprocs database. 4 Perform a pre-upgrade verification. 5 Upgrade the test system to Release 12.5.
Cutover Migration Task List Example Front-End Regression Test Suite 1 Perform user regression testing. 2 Monitor and capture system dynamics (sp_who, sp_lock...). 3 Verify and document this regression test. Other Testing Verify 12.5 performance and functions on the test system. Run User/Acceptance Tests on Release 12.5 Test System 1 Testers perform user regression testing of Release 12.5. 2 Monitor and capture system dynamics (sp_who, sp_lock...). 3 Verify and document the regression test.
APPENDIX B Sample Migration Task Lists 3 Alter the sybsystemprocs database. 4 Perform a pre-upgrade verification. 5 Upgrade the production system to Release 12.5. 6 Run dbcc commands (checktable, checkalloc, checkcatalog) on the Release 12.5 databases. Be sure to verify the dbcc log and error log. 7 “Baseline” the Release 12.5 configuration on the production system. 8 Perform user testing and verification. 1 Start production users on the Release 12.5 production system.
Staged Cutover Task Overview 1 Configure ASE 12.5 on the development system, duplicating the earlier release development configuration. 2 Migrate the development objects to the 12.5 development system. 3 Construct regression test suites. 4 Construct bcp scripts to move object deltas. 5 “Baseline” the older test environment. 6 Configure a duplicate 12.5 server on the test platform. 7 Migrate the test/acceptance objects to the 12.5 test system.
A P PE N DI X C Migration Issue Checklists The following checklists were produced by Sybase Consulting to use in writing migration plans for customers. They list issues that you may wish to address in your migration planning. Not all issues shown here will apply to your site, nor are these lists exhaustive. For more information on writing a migration plan, see Chapter 4, “Plan: Writing a Plan and Getting Ready to Migrate”.
Logical Application Architecture Logical Application Architecture Does the logical application architecture include: • A list and brief description of the required RPCs and stored procedures needed to support the new IT architecture • List of any potentially sharable functions • List of shared services such as initialization, termination, global edits, error handling, logging, and monitoring • An approach and a graphical representation of how application functionality will be split between servers, clients
APPENDIX C Migration Issue Checklists • Vendor-independent description (functions and features) and graphical representation of hardware and software components in the new systems infrastructure • Information about expected network loads at normal and peak processing periods • Information about any upgrades necessary to the existing network infrastructure, including information on specific carrier types • Information on all connected nodes (workstations, database servers, gateways, etc.
Migration Strategy Design • • • • • Disaster recovery • Production approval and access control New support organization, including roles and responsibilities Staffing and training plans Strategy for meeting needs for support coverage (location and number of shifts) Strategy for meeting needs for required response time for problem resolution Migration Strategy Design Does the migration strategy include: • An implementation sequence or a transition plan for candidate applications, that shows the evolution
A P PE N DI X D Pre-Upgrade Checklist This checklist can be used in addition to that found in the installation guide. It lists steps to prepare for upgrade. It is in order of earliest tasks to tasks done just before upgrading. Pre-Upgrade Checklist 1 Install the most recent version of the operating system, or at least the certified release for ASE. 2 Check that you have enough disk space. See your installation guide for requirements. 3 Check that each database has at least 10% free space.
Pre-Upgrade Checklist 7 Record size and device fragment information for all databases. You can query the sysdevices and sysusages tables for this information. 8 Make a note of the default character set and sort order. See the System Administration Guide at http://manuals.sybase.com:80/onlinebooks/groupas/asg1200e/asesag/@Generic__BookView? for information about character sets and sort order.
APPENDIX D Pre-Upgrade Checklist 5 On NT, if server is an automatic service, change the service type for ASE to manual. 6 Stop mirroring. 7 Disable auditing: sp_auditoption “enable auditing”, “off” 8 Set trunc log on chkpt off in all databases. 9 Save the server configuration (.cfg) file.
Pre-Upgrade Checklist 138