Tru64 UNIX Transition Strategies for Informix Dynamic Server
Introduction......................................................................................................................................... 2 Tru64 UNIX IDS transition plan ............................................................................................................. 4 Review your business situation ........................................................................................................... 4 Assess infrastructure stack and availability .......................................................................................... 5 Identify transition components............................................................................................................ 7 Define technical requirements ............................................................................................................ 8 Define transition strategy................................................................................................................... 8 IDS upgrade ..................................................................................................................................... 10 IDS transition implementation steps ...................................................................................................... 10 Tru64 UNIX server: Gather information & customizations.................................................................... 10 Select the database moving method ................................................................................................. 13 HP-UX 11i server: Install HP-UX 11i, patches, IDS, third-party products ................................................. 14 HP-UX 11i server: Apply gathered information and customizations....................................................... 15 Move database from Tru64 UNIX .................................................................................................... 17 Post-transition steps......................................................................................................................... 17 Test and tune ................................................................................................................................. 18 Move to production ........................................................................................................................ 18 Laboratory transition test setup ............................................................................................................ 18 Appendix A: dbexport/dbimport migration example ............................................................................. 20 Appendix B: HPL migration example .................................................................................................... 26 Appendix C: Example device array files............................................................................................... 31 Further information............................................................................................................................. 32
Introduction In the coming years, HP will be phasing out Tru64 UNIX® and the AlphaServer enterprise system line in favor of the new HP Integrity server line based on the Intel® Itanium® 2 processor architecture. For Tru64 UNIX-based Informix Dynamic Server (IDS) environments, Information Technology (IT) organizations should start considering when and how they should transition to the new platforms. HP is investing significant resources to help you transition easily and reliably to the new HP Integrity servers. Because transitions are easier when the same version is available on both the original and target platforms, HP has partnered with IBM to make sure that the latest version of IDS for Tru64 UNIX is also available for the HP Integrity server family. HP will continue Tru64 UNIX operating system support through 2011. However, as more robust market-leading solutions become available, it will become increasingly compelling for you to consider higher performing, lower cost options, such as HP Integrity servers. This technical document can assist you in planning and implementing your transition. Its purpose is to present the transition strategy and details involved with moving the IDS to the HP Integrity server platform. It draws upon IDS migration methodology combined with a focus on the Tru64 to HP-UX Integrity server environment and testing done in HP laboratories. An IDS transition involves many implementation steps, including gathering data, setting up the target HP Integrity database server, moving the original database, testing, tuning, and turning the target environment over to production. This document discusses these steps and illustrates them for two different methods of moving IDS from one operating system to another. This document assumes: Working knowledge of IDS installation and database administration Working knowledge of Tru64 UNIX and HP-UX system and network administration Working knowledge of Tru64 UNIX, HP-UX, and IDS performance tuning Familiarity with project management methodologies
Note: The information in this document pertaining to the next release of IDS may change since that release was not final when this document was published. The steps that are necessary to perform an IDS transition to HP Integrity servers are summarized as follows: 1. Developing a transition plan 2. Performing an IDS upgrade (if necessary) 3. Implementing IDS transition steps
In Figure 1, the above steps are represented by shaded boxes. The implementation steps and other activities are represented by bulleted text items and are discussed in detail through this document.
Rev. 1.1
2
Figure 1. Overall IDS transition steps example
Develop transition plan
Perform IDS upgrade (if necessary)
Check if current IDS version is supported on Itanium
Review business situations Assess infrastructure stack & availability Identify transition components Define technical requirements Define transition strategy
IDS transition implementation
Gather information & customizations
Select database moving method
Install HP-UX, patches, IDS, other products Apply information gathered and customizations Move database from Tru64
Post transition steps Test and tune Move to production
Tru64 UNIX production environment
HPL (unload)
or
dbexport
compress
UNIX pipes
uncompress
HPL (load) Disk storage
Disk storage tar/ gzip/ rmesh
dbimport Disk storage
HP-UX Itanium environment
Rev. 1.1
3
Tru64 UNIX IDS transition plan Developing and documenting a plan is critical to a successful transition. Planning can help identify crucial decisions that are needed before beginning the transition process. Some of the steps that are essential in developing a Tru64 UNIX IDS transition plan are: • Review your business situation • Assess infrastructure stack and application availability • Identify transition components • Define technical requirements • Define transition strategy: – – –
Transition process Test plan and acceptance criteria Allowable production downtime
In addition, include general project plan activities such as: • Identify and schedule staff and equipment resources • Identify and schedule other resources that you may use for the transition • Prepare a contingency plan for unanticipated problems You should make the transition to HP Integrity servers as soon as it makes business sense to do so. This transition may involve an IDS upgrade to the latest release of the OLTP database. If you are happy with a version of IDS that does not support HP Integrity servers, and have no plans to perform an IDS upgrade in the immediate future, HP recommends that you continue using Tru64 UNIX. If more capacity is required, consider purchasing or leasing new AlphaServer systems. See your HP account representative or Solution Architect for information and visit the Alpha RetainTrust website for general information: http://www.hp.com/go/alpha-retaintrust/ You may find the HP Transition Benefits Calculator useful in analyzing and evaluating your transition. Visit the following website to use the calculator and get additional information: http://www.hp.com/go/artvalue
Review your business situation A transition to HP-UX 11i on HP Integrity servers should be conducted with due consideration for factors that drive your business, and for resulting demands on your IT environment. Among the elements to be considered: • Business needs may require you to implement additional IDS modules, some of which may be offered only with IDS V9.4 or above. • Business demands on your IT environment may currently or potentially exceed its capacity, driving a need for additional computer resources. • Server consolidation, to reduce cost while implementing the latest Adaptive Enterprise technology, may be combined with your transition. • End-of-service dates on older versions of IDS, the operating system or other infrastructure components may force the transition.
Rev. 1.1
4
Assess infrastructure stack and availability Availability of Tru64 UNIX, HP-UX 11i, and IDS versions will play a major role in deciding when to start the transition. End-of-support dates and general availability dates create time windows during which transition opportunities present themselves. The following information about product roadmaps can help you with transition planning. However, since roadmaps can change, you should also check the links in the Further information section and contact your HP account representative or Solution Architect for up-to-date information. Tru64 UNIX HP plans to deliver updates to its Tru64 UNIX operating system until at least 2006 with standard support at least until 2011. Information about the Tru64 UNIX roadmap can be found at: http://h30097.www3.hp.com/unix/downloads/tru64_unix_roadmap.ppt
End-of-life dates for current Tru64 UNIX versions are listed in the following table. Only versions that have not already reached their end-of-life date are shown. Table 1. End-of-life dates for Tru64 UNIX versions Tru64 UNIX version
End-of-life date
4.0F
9/30/05
4.0G
9/30/05
5.1A
2/28/05
5.1B
End-of-life date has not been determined yet
Since Tru64 UNIX end-of-life dates might change, you should check the following HP website for the latest information: http://www.hp.com/hps/os/os_pvs_amap.html/
HP-UX 11i on the Intel Itanium architecture HP-UX 11i v2 is now supported on HP 9000 and HP Integrity server architectures. Transition information can be found at: http://h30097.www3.hp.com/transition/
IDS The current version of IDS, Version 9.40, is supported on Tru64 UNIX and HP-UX 11i (PA-RISC and Itanium) operating systems. As of this writing, the next version of IDS is also expected to have Tru64 UNIX and HP-UX 11i (PA-RISC and Itanium) operating system support. The following table summarizes the support matrix for IDS on Tru64 UNIX and HP-UX 11i UNIX operating systems. Note that only IDS versions that have not reached their end-of-service dates are listed.
Rev. 1.1
5
Table 2. IDS support matrix for Tru64 UNIX and HP-UX operating systems Tru64 UNIX IDS* version
End-ofservice date
7.31U
4/30/06
7.31F
4/30/06
9.21U
6/30/04
9.21H
6/30/04
9.21F
6/30/04
9.30H
4/30/05
9.30F
4/30/05
9.40H
4/30/06
9.40F
4/30/06
4.X
X
5
X
HP-UX 11i 5.0A
X
5.1
X
5.1A
X
5.1B
10.2
11.0
11.11
11i v2
(PARISC)
(PARISC)
(PARISC)
(Itanium)
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X X
X
X
X
X
X
X
X
X
X
* F = 64 bit, H = 32 bit build on HP-UX 11.x, U = 32 bit
See the Further information section for sources of additional information. HP recommends that you check them for the latest information about availability and support. DB2 information management software If you are considering updating IDS to DB2 in the near future, DB2 UDB V8.1 is also available on HP Integrity servers. Other Informix products Other Informix products that are supported on HP Integrity servers are listed in the following table. Table 3. Other Informix products support matrix for HP Integrity servers
Rev. 1.1
Informix product
HP-UX 11i v2 (Itanium)
CSDK 2.81.U
Supported (32-bit)
CSDK 2.81.F
Supported (64-bit)
4GL 7.32.U 4GL 7.32.F
Supported (32-bit) Supported (64-bit)
C-ISAM 7.26.U C-ISAM 7.26.F
Supported (32-bit) Supported (64-bit)
6
Identify transition components Components in your current environment that need transitioning and/or upgrading must be determined, along with new components that must be introduced. Current transition components The current Tru64 UNIX components that you need to transition to HP Integrity servers are: • IDS IDS database, user profiles, database configuration files, schema, and so on (see the Tru64 UNIX server: Gather information & customizations section) • Operating system information Memory and disk utilization, system parameters, performance data, and so on (see the IDS transition implementation steps section) • Client applications (refer to any application that is associated with IDS) • Additional products Other Informix or third-party products executing on the Tru64 UNIX server that need to be transitioned (for example, 4GL, CSDK, compiler, and so on) • Technical skills Refer to Transitioning Technical Skills from Tru64 UNIX to HP-UX. This HP white paper is an evaluation for system administrators and value added resellers and is available at: http://h21007.www2.hp.com/dspp/files/unprotected/hpux/transition_techskilles_tru64_hpux.pdf New transition components The new hardware, software, and environmental components introduced with the transition are: • Itanium hardware and peripherals • Computer (amount of memory, disks, and CPUs) • External storage (SAN, RAID) • Network (routers, adapters, switches) • Environment • Power requirements • Air conditioning • Computer room • Software • Operating system (HP-UX 11i v2 or above) • Operating system patches • IDS 9.4 and above OTLP database • Other HP Integrity servers supported products (Informix, HP, third-party) Many of the above topics are addressed in the Transition Modules (TMs) available at: http://www.hp.com/go/transition-modules/ The TMs discuss such issues as platform, custom code, and application migration.
Rev. 1.1
7
Define technical requirements The technical requirements for both hardware and software must be reviewed. Hardware requirements Environmental requirements for HP Integrity servers are available at: http://www.hp.com » Servers Moving data between Tru64 UNIX and HP Integrity servers often calls for an extremely fast network. The network between these computers must have sufficient bandwidth to accomplish the task as promptly as possible. External storage with equal or greater capacity than your current Tru64 UNIX external storage is required for the new system. Intermediate storage may also be needed for use during database migration. Additional storage or tape may be needed for backups. Software requirements IDS operating system and hardware requirements can be found in the IDS machine notes. The machine and release notes for IDS v9.4 are located in the following directory of the installed IDS product: $INFORMIXDIR/release/en_us/0333 The machine notes contain system requirements and configurations that you need to implement IDS on a particular operating system. Other documentation notes in this directory contain release information that was not included in the IDS user manuals. IDS user manuals can be found on the following IBM website: http://www-3.ibm.com/software/data/informix
Review this website to acquire the latest information regarding technical requirements.
Define transition strategy Your Tru64 UNIX transition plan should include a step-by-step transition process description, along with plans for in-process testing and acceptance testing the new environment. Moving your database itself will probably require the most time, possibly imposing some planned production downtime. How much downtime you will need and how much is allowable will influence your selection of a database moving method. Defining the transition process Defining the overall transition process, deciding whether to implement an IDS upgrade, and selecting the method for moving the database are very important technical requirements. Currently, IDS V9.40FC3 (or above) is required for HP Integrity server support; previous versions of IDS must first be upgraded to at least IDS V9.40FC3 on Tru64 UNIX. The Informix IDS Migration Guide lists different database moving methods. The two principal methods HP has focused on are the dbexport/dbimport and High-Performance Loader (HPL) methods. Test plan and acceptance criteria The objective of a test plan is to prescribe tests that ensure that your production environment performs properly following the transition. You may want to check the performance of your target system and conduct scalability tests to ensure that it can grow along with your business. Make sure that the functionality of all your critical business processes is tested and do not forget to test any customizations that may have been implemented. It should also include a schedule for the staff that will implement the tests.
Rev. 1.1
8
The test plan should also cover the following important points: • Types of tests needed (for example, system, performance, data types, acceptance, and so on) • Methods of testing (manual or with scripts) • Amount of workload and number of simulated users • Response times for certain transactions or queries Allowable production downtime and selecting a database moving method Downtime usually begins when you start your data transfer from your current production system to your target production system. In most cases, the database cannot be used during that time. You can manage when the downtime ends by using one or more tactics. With good planning and testing, you can reduce the amount of production downtime. To begin, you and your database administrator can prototype system measurements to decide which bulk data copying method to use. In general, the dbexport/dbimport utility works fine with a relatively small database, but can be time consuming with a large database. Alternative methods like HPL may take less time. HP ran database transfer tests (see the Laboratory transition test setup section); the data transfer rates that were achieved for both the dbexport/dbimport and HPL methods are in Appendix A and Appendix B respectively. Be cautioned that these transfer rates depend heavily on database tuning, database table structure, processor, network, and I/O speed. Your experience may vary significantly. However, these transfer rates should give an indication of the relative differences between each method. Prototype: testing and tuning Before turning your target system over to production, you will want to test and tune it. Testing and tuning the target database server can take some time. HP recommends that you set up a prototype target production system to conduct tests of your transition procedure and additional target system performance and scalability tests. This will give you an opportunity to select, correct, and refine your procedures while allowing your users to continue useful production work on the original system. Then, when you are ready, you can run through a well-exercised transition process quickly, verify it, and then cut it over to production use. You may want to consider some of the following prototype test operations: • Experiment with moving the database between the Tru64 UNIX and HP-UX 11i database servers, measuring the time required. • Move a partial database containing different types of storage spaces (dbspaces, blobspaces, or sbspaces) and test whether applications that use them function properly on the target system. • Test questionable data types (endian aware, for example) or storage arrangements (see the Endianism considerations section). • Test the newly created database (conduct validation and integrity checks). • Tune the newly created database and target operating system. Test runs can help you estimate the amount of downtime the above tasks require along with exposing testing and tuning problems you may have.
Rev. 1.1
9
IDS upgrade An IDS upgrade is necessary only if your current IDS version is not supported on HP Integrity servers. The IDS upgrade must be performed on an operating system that supports both the source and target IDS version. Therefore, HP recommends that you perform upgrades on your Tru64 UNIX IDS server until you reach a version of IDS that is supported on HP Integrity servers. Backing up the database, installing a new version of IDS, converting the database, backing up the database on the new IDS version, and testing the database instance are the basic steps for upgrading IDS. These steps are all discussed in detail in the IBM Informix Migration Guide available at: http://www-306.ibm.com/software/data/informix/pubs/library/ids_94.html
Differences between IDS versions environmental variables, database parameters, system catalog, system masters, and storage manager are also discussed in this document.
IDS transition implementation steps The “Migrating between Database Servers and Operating Systems” chapter in the IBM Informix Migration Guide for V9.40 describes the steps needed to migrate from Tru64 UNIX to HP Integrity servers. HP recommends that you read this chapter before implementing any transition steps. Informix and HP manuals that can assist you throughout the transition for both IDS V9.4 and HP-UX can be found on the following websites: • IDS V9.4: http://www-3.ibm.com/software/data/informix/pubs/library/ids_94.html • HP-UX: http://www.docs.hp.com/ The steps that are necessary to perform an IDS transition to HP Integrity servers are summarized as follows: 1. 2. 3. 4. 5. 6.
Gathering information and customizations about your current Tru64 UNIX configuration Selecting the database moving method Installing HP-UX, patches, RDBMS, and third-party products on new HP-UX servers Applying gathered information and customizations to new HP-UX servers Moving the database from Tru64 UNIX Implementing post-transition steps: • Testing and tuning the newly created environment • Moving the newly created environment to production
Tru64 UNIX server: Gather information & customizations It is advisable to have in hand certain information from your current Tru64 UNIX IDS database server. This can assist in the transition process. Examples of the information you should collect are the following: • Informix user profiles • Database configuration files • Database integrity checks • Database backup • Database census • Database schema • Endianism considerations • Performance metrics
Rev. 1.1
10
Check the IDS version executing on Tru64 UNIX to make sure that it is supported on HP Integrity servers. To determine the version of IDS currently installed on your Tru64 UNIX database server, go to $INFORMIXDIR and read one of the release notes documents in the release subdirectory. The version of IBM Informix database should be IBM IDS 9.40.FC3 (64-bit) or later. If an earlier version of IDS is running, see the IDS upgrade section.
Informix user profiles Print Informix user profile information from the current IDS database server. This can help in establishing user profiles on the new database server. Notice which shell you are currently using, to eliminate shell related script problems. IDS environmental variables are used to specify the location of the current IDS database configuration files. Save a list of these environmental variables and implement them with appropriate modifications (for example, shared library path, binary path, and so on) on the HP-UX IDS as a transition step. The command env can display all IDS environmental variables that are in use. For example, to display and save environmental variables: $env > env.out Database configuration files Transfer current IDS database configuration files which are referenced by IDS environmental variables to the new HP-UX Itanium server and then modify them for the new HP-UX environment. The different varieties of IDS configuration files are located in the following directories by default: • Current ONCONFIG file located in etc subdirectory of your installation directory: $INFORMIXDIR/etc/$ONCONFIG $INFORMIXDIR/etc/onconfig.std $INFORMIXDIR/etc/oncfg* • sqlhost information: $INFORMIXDIR/etc/sqlhosts • adtcfg located in the aaodir subdirectory: $INFORMIXDIR/aaodir/adtcfg • adtmasks.* located in the dbssodir subdirectory: $INFORMIXDIR/dbssodir/adtmasks • Other configuration files located in the etc subdirectory $INFORMIXDIR/etc/sm_versions $INFORMIXDIR/etc/tctermcap $INFORMIXDIR/etc/termcap $INFORMIXDIR/etc/plconfig Database integrity checks Verify the integrity of the IDS data with the oncheck utility. Instructions on how to do this can be found in the “Migrating to Dynamic Server 9.40 or 9.30 from 9.x, 7.3x, or 7.24” chapter (the “Verify the Integrity of the data” section) in the IBM Informix Migration Guide. Moving a database without integrity can cause problems. Examples of commands you can use to check the integrity the database are listed in the following table.
Rev. 1.1
11
Table 4. Database integrity check commands Oncheck command
Verification
-cI db_name
Index
-cD db_name
Data
-cc db_name
System catalog
-ce
Extents
-cr
Reserve pages
Database backup A level-0 backup is recommended. Use either the ON-Bar or the ontape utilities. Refer to the IBM Informix Backup and Restore Guide and IBM Informix Migration Guide for information on how to use these utilities. This step should be done just before bringing the database offline. Database census Take a census of your Tru64 UNIX source database. Make sure that you have a database layout and row counts for all your database tables. • To get all information of the database: $onstat –a > onstat_a.txt • To get the space and chunk of the database: $onstat –d > onstat_d.txt Database schema You can save the database schema using the dbschema or dbexport utilities. Use either of the following commands to save your current schema information: $dbschema –ss –d database_name > schema.sql $dbexport –ss –o The dbexport command will export together both the complete database and the schema file to the directory specified by the –o option. For both the dbschema and dbexport commands, the –ss option will generate database serverspecific information for all tables in the database. Use this option if you plan to restore your current Tru64 UNIX space and chunk storage information. You can get this information from output of the onstat –d command. Endianism considerations Endianism refers to the way in which data is stored and defines how bytes are addressed in multi-byte data types. Tru64 UNIX is least significant first (little-endian) while HP-UX 11i is most significant first (big-endian). A database that tries to interpret multibyte binary data on a machine that is of a different endianism will have different results. Therefore, moving binary data from Tru64 UNIX to HP-UX 11i is not allowed unless the move is endian neutral. The dbexport/dbimport utilities read and write to a file using only one endian type, therefore allowing the moving of data between machines of different endian types. The HPL utility allows you to choose whether to use a machine type table. Machine types for both Tru64 UNIX (unloading of data) and HP-UX (loading of data) are necessary to perform an endian neutral move unless all data in the table are stored in single byte format. The machine types you should create are listed in the following table.
Rev. 1.1
12
Table 5. Machine types Machine type
Tru64 UNIX
HP-UX 11i
Byte Order
LSB
MSB
Short Size
2
2
Integer Size
4
4
Long Size
8
8
Float Size
4
4
Double Size
8
8
The Tru64 UNIX to HP-UX 11i Porting Guide discusses endianism considerations between Tru64 UNIX and HP-UX and is available at: http://www.hp.com/go/tru64appmigration » Porting guide User-defined and complex data types can have problems with endianism depending on their internal formats. This also applies to data stored as BLOB. Standard data types (for example, char, int, and date) within complex or user-defined data types are endian neutral. Non-standard data types (for example, BLOB and other large objects) usually will have problems with endianism. You should check and thoroughly test any table containing these types of internal storage for endianism problems. You can use the dbschema utility to locate user-defined data types ($dbschema –u all). Performance metrics Consider collecting performance data on both of your databases so that you can compare them. Commands to get performance statistics are described in the IBM Informix Dynamic Server Performance Guide. The onstat utility can be used to gather these statistics. You may want to obtain transaction or query response times also. You can monitor Tru64 UNIX performance metrics such as CPU, I/O, and memory with the Tru64 UNIX utility collect (for example, collect –scdm) and you can use the syscheck utility to take a census of the operating system.
Select the database moving method There are several methods for moving an IDS database across different operating systems; you need to decide which method is best for your environment. These methods are described in the IBM Informix Data Migration Guide. IBM also offers a class called IBM Informix Data Migration and Reorganization which can help you gain experience using Informix data movement utilities such as dbexport/dbimport and HPL.
Rev. 1.1
13
HP used the following methods for in the laboratory tests: dbexport/dbimport The dbexport/dbimport utilities are designed to move the complete IDS database but may be slow with large amounts of data. The HP implementation example used intermediate disk storage to store the database export on both Tru64 UNIX and HP-UX 11i. High-Performance Loader (HPL) HPL is designed to load and unload large quantities of data to or from a database. It is faster than the dbexport/dbimport utilities but harder to use. The HP implementation example transferred data from individual database tables through a UNIX pipe into compressed files on the remote database server. The data was then loaded from the compressed files using UNIX pipes on the remote database server.
HP-UX 11i server: Install HP-UX 11i, patches, IDS, third-party products You can begin installing the software once the new HP Integrity server hardware has been set up in its proper environment. Review the IBM Informix Dynamic Server machine note before starting any software installations. To read the machine note, go to: http://www.ibm.com/software/data/informix/pubs/
Required version and patches of the HP-UX 11i operating system are specified in this note, along with platform-specific information for the IDS database server. Also included in this note is a list of features that may not be supported for a specific platform. Operating system and patches You must install the HP-UX 11i version that is certified with your target IDS version (including patches). The minimum version levels for the operating system and IDS are HP-UX 11i v2 and IBM IDS 9.40FC3. The machine note for IBM Informix Dynamic Server 9.40FC3 specifies that HP-UX 11i v2 is required along with patches PHSS_29656 and PHSS_29655. To find the HP-UX11i installation guides, go to: http://www.docs.hp.com
To find the HP-UX 11i patches, go to: http://www.itrc.hp.com
The IDS V9.40FC3 machine note also specifies the following: • UNIX graphical tools provided with IDS will use X and Motif shared libraries. If these graphical tools do not work properly, try exporting the environment variable LD_LIBRARY_PATH to the proper shared libraries. For example: export LD_LIBRARY_PATH=/usr/shlib:/usr/dt/lib:$LD_LIBRARY_PATH • Minimum physical memory for HPL is 35MB and minimum swap space is 70MB. You can use utilities like swapinfo and vmstat to determine the amount of available physical and swap memory. • IDS kernel parameter adjustments. The initial values in the machine note are listed in the following table.
Rev. 1.1
14
Table 6. Kernel parameter values Kernel parameter
Value
shmseg
512
shmmni
512
shmmax
4294967296
semmnu
1400
semmns
4096
semmni
4096
nfile
5000
You can use the kcweb utility to adjust system parameters. These values may need tuning depending on the application and system resource availability. IDS and other products Install IDS 9.40 as described in the IBM Informix Dynamic Server Installation Guide for UNIX and Linux. You can use the HP operating system sam utility to create an Informix user and group. Install other products that are currently residing on the Tru64 UNIX server and are supported on HP Integrity servers (for example, 4GL, CSDK, C compiler, and so on). File systems and raw devices If you plan to use files greater than 2GB, you need to enable Large File support. You can check /etc/fstab or use a utility like sam to see if you are currently using this option. The fsadm and fsadm_hfs man pages can show you how to enable large file support. Since the Tru64 UNIX file system does not have this limitation, HP recommends that you enable large file support. If you plan to use raw devices, kernel asynchronous I/O must be ENABLED. Refer to the machine notes for information on how to enable this feature. If the asynchronous driver is loaded properly, the command fuser –u /dev/async will show Informix processes. Audit support Follow the instructions stated in the machine notes if you want to configure the operating system audit subsystem to record IBM Informix Dynamic Server audit records in the operating system audit log.
HP-UX 11i server: Apply gathered information and customizations You can now apply the information that was collected from the Tru64 UNIX IDS database server to the newly created IDS database server. Environmental variables Use the applicable contents of your Tru64 UNIX user profile and output from the env command with appropriate modifications (for example, different paths) and with modifications as required if you have chosen a different user shell. Customize configuration files Modify the Tru64 UNIX IDS configuration files which were saved (as described in the Tru64 UNIX server: Gather information & customizations section) and restore them to the appropriate directories. You must edit these files to reflect the changes for the target environment. This includes some PATH variables, hostname, shared memory location, large memory addressability, and so on. Refer to the IBM Informix Migration Guide and the IDS machine notes for further information.
Rev. 1.1
15
One of the differences between Tru64 UNIX and HP-UX is that the SHMBASE parameter in onconfig has changed from 0x200000000L to 0x0L. Refer to the machine notes of IDS on both platforms and the IBM Informix Migration Guide for more information.
Communication support modules The onconfig and sqlhost files are used to establish communication with application processes. Make sure that the communication support modules that you used on Tru64 UNIX are supported on HP-UX Itanium. Modify these files for HP-UX implementations. Currently, all communication support modules supported on Tru64 UNIX are supported on HP-UX 11i Integrity servers. Initializing the IDS Once you have setup all IDS environmental variables and configuration files, you can initialize the IDS by using the $oninit –iv command. This command will initialize all disk space and shared memory for IDS. CAUTION: Do not use this command if there is data in the database. All data will be destroyed.
Note: Before you can initialize the IDS server, a file must be created and the proper privileges given if you specify rootdbs in onconfig as a cooked file. These steps are not needed if rootdbs is created on a raw device. $cd /data/informix $touch rootdbs $chmod 660 rootdbs If the IDS instance is properly initialized, the message Verbose output complete: mode=5 will be displayed and there will be no errors in the IDS log file. The location of the IDS log file is specified in onconfig. Create storage space and chunks If you plan to use the same storage space and chunk of your Tru64 UNIX IDS server, review the output from onstat –d. Use the –ss option when you create the schema. See the Database schema section for information about creating schemas. Create the storage space by using the onspaces utility. Remember to create a file and assign the proper privileges if you are using cooked files. Install and configure any DataBlade modules You must recompile all UDRs and DataBlades that were built on Tru64 UNIX in 64bit-mode on HP-UX. Please check which DataBlades are ported to HP-UX Integrity servers and are available for this platform. Currently, the LOB Locator DataBlade is supported on HP Integrity servers.
Rev. 1.1
16
Other customizations As described in the machine notes, the shared library ipldd09a.so supplies the user-defined conversion routines for HPL. The HPL_DYNAMIC_LIB_PATH configuration parameter contained in a file which the PLCONFIG environment variables specifies must specify the $INFORMIXDIR/lib directory. $PLCONFIG=plconfig.tpcc;export PLCONFIG $vi plconfig.tpcc
Move database from Tru64 UNIX Once you have chosen a database moving method, you can begin moving the database from Tru64 UNIX to your HP Integrity server. See the Select the database moving method section for further information. Steps for the two database moving methods HP tested (using a laboratory test setup described later in this document) are documented in Appendix A and Appendix B. You can create the IDS HP Integrity server database by modifying schema files that were created by the Tru64 UNIX IDS database. Both the dbexport and dbschema utilities can create schema files (see the Tru64 UNIX server: Gather information & customizations section for further information).
Post-transition steps You should perform the following recommended steps on the target IDS database server after you have completed moving the Tru64 UNIX IDS database: 1. Update indexes, evaluate triggers, and set constraints.
Depending on your data moving method, you may have to do one or more of these tasks manually. Table 7. Moving methods Moving method
Manually performed
dbexport/dbimport
triggers
HPL Deluxe Mode
(none)
HPL Express Mode
Indexes, triggers, constraint
2. Update statistics.
The “Improving Individual Query Performance” chapter in the IBM Informix Dynamic Server Performance Guide shows different commands for updating the database statistics. You should update your transition database statistics with the UPDATE STATISTICS command. 3. Verify the integrity of the IDS data using the oncheck utility (see the Database integrity checks
section for more information.) 4. Check any of the database logs for errors. 5. Check the database contents.
– – – –
Check the output of onstat –d to see if it looks like the similar output for the Tru64 UNIX IDS. Compare row counts and size, and column numbers of all database tables. Manually check all data types with endianism problems (see the Endianism considerations section). HP recommends that you perform some database table content comparisons between the Tru64 UNIX and HP-UX databases.
Rev. 1.1
17
6. Perform a level-0 backup.
HP recommends you use ON-Bar, or ontape utilities to perform the level-0 backup. Refer to the IBM Informix Backup and Restore Guide for information on how to use these utilities. The use of HPL Express Mode requires a level-0 backup.
Test and tune Test and tune your newly created IDS database server before moving it to production. It is important to determine that your critical business processes are working properly and that your IDS database server is delivering optimal performance. Test plan and acceptance criteria Test your new database server by executing the test plan you prepared (see the Test plan and acceptance criteria section under “Defining transition strategy”). Tune After testing, tune your new HP Integrity server IDS database server. The IBM Informix Dynamic Server Performance Guide provides guidelines. Machine notes, release notes, and performance notes can also assist the tuning effort. They can be found under $INFORMIXDIR/release/en_us//0333 for IDS V9.40. HP-UX tuning documentation can be found on the HP-UX documentation website: http://www.docs.hp.com
Both HP and IBM Informix offer training classes that can assist you in tuning both HP-UX and IBM IDS. Performance monitoring is necessary for tuning. Monitor memory, CPU, and I/O performance of your new configuration. Tune the system, application, and database as necessary. Use the statistics and transaction and query response times obtained earlier from the Tru64 UNIX IDS database server to judge whether there is a performance problem with the new server. (see the Tru64 UNIX server: Gather information & customizations section). The amount of memory and CPU and I/O resources can create performance bottlenecks and degradation. Monitor resources with utilities like GPM, glance, sar, vmstat, and iostat. Differences in disk layouts, memory, and kernel design between Tru64 UNIX and HP-UX can also affect performance. Both operating system configuration and database configuration parameters may need tuning.
Move to production When you have completed all tests and are satisfied with the performance you can move your new IDS HP Integrity database server to production.
Laboratory transition test setup To simulate the transition, HP set up the environment illustrated in Figure 2. Several test databases composed of 1.6 and 7GB of raw data executing IDS V9.40FC3 on Tru64 UNIX V5.1B were transitioned using the steps shown in Appendix A and Appendix B. The network topology between the database servers consisted of a dedicated 1000 Base T link for transferring the database data and a shared 100 Base T link for general or corporate access The dbexport/dbimport and the HPL utilities were used to unload and load data between database servers. The methods used to validate the database transfer were row counts, column count, row size for each table, and database integrity checks (see the Database integrity checks section). HP did not test all combinations of IDS data types or storage, but included information about the things you should be aware of that may need special attention. Rev. 1.1
18
Figure 2. Tru64 UNIX to HP-UX 11i transition test environment
Tru64 UNIX IDS Database Server Environment
Itanium HP-UX IDS Database Server Environment
External Storage ESA 12000 400 GB
GS 1280 4 X 1.2 GHz CPU 8 GB Memory Tru64 V5.1B
External Storage VA7410 400 GB
RX5670 4 X 1.0 GHz CPU 8 GB Memory HP-UX 11i v2
1000 Base T Dedicated Network 100 Base T Shared Access Network
Rev. 1.1
19
Appendix A: dbexport/dbimport migration example In this example, HP executed the dbexport utility on Tru64 UNIX to unload the database and schema information into files. The files were then transferred to the new HP Integrity database server using tar, gzip, and rsh. The dbimport utility was executed to create and populate a new database (for information on using the dbexport/dbimport utilities, refer to the IBM Informix Migration Guide). The steps and commands used are shown in the following figure. Figure 3. dbexport/dbimport process
Tru64 IDS Database
1. dbexport –unload database schema and data Tru64 Storage
2. tar/gzip/rsh – transfer by compressing/decompressing schema and data to HP-UX HP-UX Storage
3. dbimport – load schema and data
HP-UX IDS Database
Rev. 1.1
20
Tru64 UNIX IDS: Copying and analyzing files On the Tru64 UNIX IDS database server, HP copied and analyzed certain IDS environmental and configuration files. 1. Check current environmental variables which IDS uses.
$env DBSPACETEMP=temp_space_1:temp_space_2 PATH=/usr1/informix/bin:/usr1/informix/product/bin:/usr/bin:. INFORMIXSQLHOSTS=/usr1/informix/product/etc/sqlhosts LOGNAME=informix USER=informix SHELL=/bin/ksh HOME=/usr1/informix INFORMIXDIR=/usr1/informix/product TERM=vt100 LD_LIBRARY_PATH=/usr/shlib:/usr/dt/lib ONCONFIG=onconfig.tpc INFORMIXSTACKSIZE=128 PWD=/data3/informix/backup INFORMIXSERVER=online_tpcc 2. Copy certain IDS configuration files that are specified in IDS environmental variables.
The IDS environmental variables for this example show user configurations for files onconfig.tpc and sqlhosts. Transfer these files to your new HP-UX 11i server. Note the tcp/ip port address in file /etc/services if IDS is communicating using tcp. $ vi /etc/services tpc_migrate 9900/tcp 3. Check and save a copy of the current IDS space management. $onstat –d IBM Informix Dynamic Server Version 9.40.FC3 Kbytes Dbspaces address number 2f3176e58 1 2f458d418 2 2f458dc20 3 2f45bacf8 4 2f45bb500 5 2f45bbda8 6 2f45bc650 7 2f4525368 8 2f4525c10 9 2f45264b8 10 2f4526d60 11 11 active, 2047 maximum
Rev. 1.1
flags 0x20001 0x20001 0x20001 0x20001 0x20001 0x20001 0x20001 0x20001 0x20001 0x20001 0x20001
fchunk 1 2 3 4 5 6 7 8 9 10 11
-- On-Line -- Up 01:47:15 – 40
nchunks 1 1 1 1 1 1 1 1 1 1 1
flags N N N N N N N N N N N
owner informix informix informix informix informix informix informix informix informix informix informix
79616
name rootdbs plog loglog1 loglog2 loglog3 wdinhdbs orderlinedbs stockdbs custdbspace_1 temp_space_1 temp_space_2
21
Chunks address chunk/dbs offset 2f3177028 1 1 0 /data3/informix/tpcc/rootdbs 2f458d598 2 2 0 /data3/informix/tpcc/plog 2f458dda0 3 3 0 /data3/informix/tpcc/llog1 2f45bae78 4 4 0 /data3/informix/tpcc/llog2 2f45bb680 5 5 0 /data3/informix/tpcc/llog3 2f45bbf28 6 6 0 /data3/informix/tpcc/wdinhdbs 2f45bc7d0 7 7 0 /data3/informix/tpcc/orderlinedbs 2f45254e8 8 8 0 /data3/informix/tpcc/stockdbs 2f4525d90 9 9 0 /data3/informix/tpcc/custdbs 2f4526638 10 10 0 /data3/informix/tpcc/tempdbs1 2f4526ee0 11 11 0 /data3/informix/tpcc/tempdbs2 11 active, 2047 maximum Expanded chunk capacity mode: disabled
size 400000
free 78802
bpages
flags pathname PO--
300000
299947
PO--
540000
539947
PO--
540000
539947
PO--
540000
539947
PO--
200000
143993
PO--
1000000
312819
PO--
800000
74947
PO--
500000
38179
PO--
360000
359747
PO--
360000
359747
PO--
4. Use the utility dbexport to create a schema and export the data.
$mkdir –p /data3/informix/dbexport $dbexport –ss –o /data3/informix/dbexport tpcc@online_tpcc Sample execution times for this step: Size of raw data (GB)
Execution time
1.6
6 min 38 sec
7
27 min 04 sec
Note: Simple Large Objects are created in files located in /tmp or a path defined by the environmental variable DBTEMP. If your data contains these objects, you must copy these files to your HP-UX Itanium server while setting up the proper path.
Transferring data to HP-UX 11i Integrity server HP transferred schema and data by using a combination the tar, gzip, and rsh utilities. 5. Create rsh authentication file on the HP-UX Itanium server (this utility is called remsh in HP-UX).
$vi /etc/hosts.equiv rx5670 informix
Rev. 1.1
22
6. Issue the tar with gzip and rsh commands assuming that you have proper directory created
on the HP-UX Itanium server. $cd /data3/informix $tar cf – dbexport | gzip -9 | ( rsh rx5670 ‘( cd /data3/Informix ; gunzip | tar xf – )’ ) Sample execution time for this step using dedicated 1000 base T network: Size of raw data (GB)
Execution time
1.6
6 min 24 sec
7
24 min 39 sec
HP-UX 11i Integrity server IDS Once you have installed the operating system and patches, adjusted the system parameters for IDS, created the Informix user and group, and installed IDS on the HP-UX 11i IDS Server, perform the following steps: 7. Set up IDS environmental variables (create the environmental variables which IDS used on the
Tru64 UNIX IDS server).
$vi .profile INFORMIXDIR=/usr1/informix/product;export INFORMIXDIR LD_LIBRARY_PATH=/usr/shlib:/usr/dt/lib;export LD_LIBRARY_PATH INFORMIXSTACKSIZE=128;export INFORMIXSTACKSIZE INFORMIXSERVER=tpcc;export INFORMIXSERVER ONCONFIG=onconfig.tpc;export ONCONFIG INFORMIXSQLHOSTS=$INFORMIXDIR/etc/sqlhosts;export INFORMIXSQLHOSTS DBSPACETEMP=temp_space_1;temp_space_2;export DBSPACETEMP PATH=$PATH:$INFORMIXDIR/bin;export PATH Note: The name for the INFORMIXSERVER has changed. 8. Set up the IDS configuration files.
Modify all IDS configuration files (for example, onconfig, sqlhosts, and so on) that were transferred from the Tru64 UNIX IDS server to reflect the changes in the HP-UX environment. The SHMBASE parameter in onconfig has changed from 0x200000000L to 0x0L In this example, physical log configuration was set to its own dbspace. HP had trouble initializing the IDS when this was set to its own dbspace since the storage space was not created yet. HP changed the physical log location to rootdbs, initialized the IDS server, created the physical log, shut down the server, modified this parameter in onconfig, and started the IDS again. The rootdbs file was created by using: $cd /data3/informix/tpcc $touch rootdbs $chmod 660 rootdbs
Rev. 1.1
23
9. Initialize the IDS using $oninit –iv
CAUTION: The initialize flag (-i) in oninit will initialize disk space and shared memory. Do not use it if there is data in the database. All data will be destroyed.
Note: If the initialization was successful, the message Verbose output complete: 5 will be displayed. Check the online logs if there is a problem.
mode =
10. Create storage spaces (dbspaces, blobspaces, or sbspaces) and chunks (review the output of
onstat –d on your Tru64 UNIX server and create these storage spaces). For creating raw partitions refer to the IDS machine notes. a. Make the storage space if not using raw partitions. $cd /data3/informix/tpcc $touch plog $touch llog1 $touch llog2 $touch llog3 $touch wdinhdbs $touch orderlinedbs $touch stockdbs $touch custdbs $touch tempdbs1 $touch tempdbs2 $chmod 660 * b. Check the buffer size with $onstat –b. IBM Informix Dynamic Server Version 9.40.FC3 -- On-Line -- Up 03:12:53 -- 40 79616 Kbytes Buffers address userthread flgs pagenum memaddr nslo ts pgflgs xflgs owner waitlist 2 modified, 1800000 total, 2097152 hash buckets, 2048 buffer size Since a page size is 2048 bytes, the initial chunk size must be two times the size of a chunk in the onstat –d output. Therefore, the –s parameter must be multiplied by two from the output of onstat –d. c.
Use onspaces to create the dbsapces, blobspaces, or sbspaces that are displayed in the output of Tru64 UNIX onstat –d. $onspaces $onspaces $onspaces $onspaces $onspaces $onspaces $onspaces $onspaces $onspaces $onspaces
-c -d plog -p /data3/informix/tpcc/plog -o 0 -s 600000 -c -d loglog1 -p /data3/informix/tpcc/llog1 -o 0 -s 1080000 -c -d loglog2 -p /data3/informix/tpcc/llog2 -o 0 -s 1080000 -c -d loglog3 -p /data3/informix/tpcc/llog3 -o 0 -s 1080000 -c -d wdinhdbs -p /data3/informix/tpcc/wdinhdbs -o 0 -s 400000 -c -d orderlinedbs -p /data3/informix/tpcc/orderlinedbs -o 0 -s 2000000 -c -d stockdbs -p /data3/informix/tpcc/stockdbs -o 0 -s 1600000 -c -d custdbspace_1 -p /data3/informix/tpcc/custdbs -o 0 -s 1000000 -c -d temp_space_1 -p /data3/informix/tpcc/tempdbs1 -o 0 -s 720000 -c -d temp_space_2 -p /data3/informix/tpcc/tempdbs2 -o 0 -s 720000
Note: HP used the onmode –BC 1 command to enable large chunkmode for files greater than 2GB. 11. Check the onstat –d output to see if it is the same as the Tru64 UNIX IDS.
Rev. 1.1
24
12. Restore the IDS Tru64 UNIX schema and database.
$dbimport –c –i /data1/informix/dbexport tpcc Note: The name of the export directory and schema file may need to be changed. $cd $mv $cd $mv
/data1/informix/dbexport tpcc@online_tpcc.exp tpcc.exp tpc.exp tpcc@online_tpcc.sql tpcc.sql
Sample execution time for this step:
Rev. 1.1
Size of raw data (GB)
Execution time
1.6
21 min 54 sec
7
1 hr 13 min 53 sec
25
Appendix B: HPL migration example In this example, HP executed HPL using pipe commands on both the Tru64 UNIX and HP Integrity database servers. Unloading a table data into a compressed format over the network is accomplished by executing an HPL unload job on the Tru64 UNIX database server using multiple pipe commands that compress the data and store the table data in a compressed file on the HP Integrity server. Loading table data from compressed files on the HP-UX server is accomplished by executing an HPL load job on the HP-UX 11i database server using pipe commands. The unloading jobs used a machine type that was made for Tru64 UNIX and the loading jobs used another machine type that was made for HP-UX 11i. These machines types are listed in Table 5 and are used to make the transfer endian neutral. Consider enrolling in the IBM Informix Data Migration and Reorganization class which will teach you on how to use and troubleshoot HPL. Figure 4. HPL data load/unload process
Ipload (Tru64) 4. Create unload and load device array 5. Generate Job
Tru64 IDS Database
6. Execute unload Job creating compress files
UNIX pipes Ipload (HP-UX) 1. Create onpload database 2. Define Project 7. Execute load Job reading compress files
Repeat 4-7 for all tables in the database
Rev. 1.1
HP-UX Compress files
HP-UX IDS Database + onpload database
3. Create DB schema
26
Refer to the IBM Informix Migration Guide and IBM Informix High-Performance Loader User’s Guide for information on using the dbschema and HPL utilities. Refer to the white paper Using the Onpladm Tool for Informix High-Performance Loader for help in developing different pipe commands and for instructions on how to perform these steps using the command line interface for HPL. The white paper is available at: http://www106.ibm.com/developerworks/db2/zones/informix/library/techarticle/0307carlson/0307carlson.html
The steps HP used in the HPL migration example are described below.
Tru64 UNIX IDS On the Tru64 UNIX IDS database server, HP copied and analyzed certain IDS environmental and configuration files, saved the current schema, and transferred this file to the HP-UX server. 1. Perform steps 1, 2, and 3 in Appendix A of this document. 2. Use the dbschema utility to create the Tru64 UNIX IDS schema.
$dbschema –ss –d tpcc@online_tpcc > schema.sql 3. Add a create database statement to the schema.sql file that you just created.
$vi schema.sql create database tpcc; 4. Copy this file to the HP-UX Itanium server.
HP-UX 11i Integrity IDS Once you have installed the operating system and patches, adjusted the system parameters for IDS, created the Informix user and group, and installed IDS on the HP-UX Itanium IDS Server, perform the following steps which create the IDS instance and schema: 5. Perform steps 5, 7 8, 9, 10, and 11 in Appendix A. 6. Execute the schema.sql file which you copied from the Tru64 UNIX IDS server.
$dbaccess – schema.sql HPL needs to be set up using one onpload database for both the Tru64 UNIX and HP-UX 11i IDS servers. HP used the HP-UX 11i IDS as the onpload database in this example. HP also used the ipload utility in GUI mode to set up and execute the data transfer. Executing HPL from the command line may be faster if your database has many tables. The equivalent HPL command line interface is documented in the Using the Onpladm Tool for Informix High-Performance Loader white paper mentioned above. 7. Execute ipload to create an onpload database on the HP-UX 11i IDS. 8. Select Configure->Project to create a new project (for example, migration). 9. Select Configure->Machine to create a Tru64 UNIX and a HP-UX 11i machine types. See Table 5
for the contents of these machine types.
Rev. 1.1
27
10. Set up the onpload database connectivity to the Tru64 UNIX IDS.
a. Modify INFORMIXSQLHOSTS file on both servers. $ vi sqlhosts onpload onsoctcp rx5670 onpload b. Modify /etc/services on both servers. $ vi services onpload 9400/tcp c.
Add onpload as the dbaliasname in onconfig on the HP-UX 11i server.
Note: The instance was shut down and restarted in order to start the tcp listener process on the HPUX 11i server.
Transferring data from the Tru64 UNIX IDS to the HP-UX IDS In this example, HP selected a database table and moved it using ipload with a UNIX pipe to the HP Integrity server. This process was repeated until all tables of the database were moved. 11. Set up the environmental variable PLOAD_LO_PATH if your database contains CLOB or BLOB
data. This path points to the location of files where these data may be stored. 12. Execute ipload and select the HP-UX onpload database server.
Select Configure->Server and select the onpload database server located on the HP Integrity server for the onpload server. 13. Select the new project you created e.g. migration 14. Select Configure->Default and modify machine type to Tru64 UNIX. Make sure you chose the
proper database and data code set.
15. Create unload and load device arrays for each table you migrate.
a. Create unload device array.
Select Components->Devices->create Create a device with a device array name similar to the table. Use a name that indicates this device array will be used for unloading of data (for example, stock_u). Create pipe command using the following example format gzip –9 | rsh rx5670 “cat > /data1/informix/test/stock1.gz” Repeat by adding an additional pipe command for each compressed data file that you used for storing the table data. For this example, HP used three pipe commands and therefore established three UNIX pipes for unloading the data from the stock table. The array items display for the device array look like the following: PIPE PIPE PIPE
gzip -9 | rsh rx5670 “cat > /data1/informix/test/stock1.gz” gzip -9 | rsh rx5670 “cat > /data2/informix/test/stock2.gz” gzip -9 | rsh rx5670 “cat > /data3/informix/test/stock3.gz”
Note: These pipe commands will create three compressed files on the HP Integrity server located in /data1/informix/test, /data2/informix/test, and /data3/informx/test directories.
Rev. 1.1
28
b.
Create load device array. Repeat Step 15a above except use a device array name that will indicate the loading of data (for example, stock_l) and create a pipe command using the following example format gunzip < /data1/informix/test/stock1.gz Note: Repeat pipe commands if multiple files were created in step 15a. You can also create device arrays for each table using the command line. Command line examples follow: onpladm create object –F stock_u.devarr –S onpload onpladm create object –F stock_l.devarr –S onpload Appendix C lists the content of stock_u.devarr and stock_l.devarr. Refer to the white paper Using the Onpladm Tool for Informix High-Performance Loader for information on how to generate and execute HPL jobs using the command line.
16. Generate a job for load and unload jobs by performing the following
a. Select Components->Generate Job. b. Select Load/Unload Job. Note: Do not select non-conversion job. It does not use the conversion for machine type needed for the endian neutral move Format Type – refer to note for information Generate Name – Use a name that is similar to the table. Each table will have a unique job (for example, stock). Database – select the database Table – select the table to move Device – select the device you just created in the previous step for unloading (for example, stock_u) 17. Select the unload job and execute Jobs->Unload.
Select the job you just created and execute. Sample execution times for this step using three pipe commands (time may vary depending on CPU, I/O, database tuning, database table structure, and network) Size of raw data in table (MB)
Execution time
Row size (bytes)
Column count
Row count
628 (stock)
55 sec
308
17
2000000
590 (orderline)
2 min 7 sec
56
10
8768261
3000 (stock)
8 min 58 sec
308
17
10000000
1945 (orderline)
10 min 42 sec
56
10
29996848
Note: The first two entries in the above table are taken from the 1.6GB raw data database; the last two entries are from the 7GB raw data database.
Rev. 1.1
29
HP-UX Itanium IDS 18. If PLOAD_LO_PATH was set up on Tru64 UNIX server (step 11), define this environmental
variable and FTP the files contained in this directory from the Tru64 UNIX server. 19. Run ipload on HP-UX. 20. Select the project and load job that you are using.
Highlight the project and select Jobs -> Load. 21. Select the HP-UX machine type, Data Code Set, and database.
Configure-> Default 22. Change the device for the load job to the load device (for example, stock_l). 23. Select the table format icon if you want to check if the table contains any blob, complex, or user-
defined data types causing endianism problems.
24. Select the option icon and change from Express to Deluxe Mode w/o replication. 25. Save and execute the load job.
Sample execution time for this step using three pipe commands (time may vary depending on CPU, I/O, index build, and so on, and using deluxe mode w/o replication) Size of raw data in table (MB)
Execution time
Row size (bytes)
Column count
Row count
628 (stock)
2 min 45 sec
308
17
2000000
590 (orderline)
56 sec
56
10
8768261
.002 (warehouse)
1 min 25 sec
93
9
20
3000 (stock)
5 min 35 sec
308
17
10000000
1945 (orderline)
14 min 39 sec
56
10
29996848
.002 (warehouse)
7 min 25 sec
93
9
100
Note: The first three entries in the above table are taken from the 1.6GB raw data database; the last three entries are from the 7GB raw data database.
Repeat loading and unloading all tables Repeat this process (steps 12-25) until all tables of the database have been moved. Note: The steps that were developed in this example are designed only to show the concepts of performing the transition. Efficient HPL command line interface scripts can be developed by your DBA.
Rev. 1.1
30
Appendix C: Example device array files The following are the two example device array files used in Appendix B, step 15. $ vi stock_u.devarr BEGIN OBJECT DEVICEARRAY stock_u BEGIN SEQUENCE TYPE PIPE FILE TAPEBLOCKSIZE 0 TAPEDEVICESIZE 0 PIPECOMMAND "gzip -9 | rsh rx5670 'cat > /data1/informix/test/stock1.gz'" END SEQUENCE BEGIN SEQUENCE TYPE PIPE FILE TAPEBLOCKSIZE 0 TAPEDEVICESIZE 0 PIPECOMMAND "gzip -9 | rsh rx5670 'cat > /data2/informix/test/stock2.gz’" END SEQUENCE BEGIN SEQUENCE TYPE PIPE FILE TAPEBLOCKSIZE 0 TAPEDEVICESIZE 0 PIPECOMMAND "gzip -9 | rsh rx5670 'cat > /data3/informix/test/stock3.gz'" END SEQUENCE END OBJECT
$vi stock_l.devarr BEGIN OBJECT DEVICEARRAY stock_l BEGIN SEQUENCE TYPE PIPE FILE TAPEBLOCKSIZE 0 TAPEDEVICESIZE 0 PIPECOMMAND "gunzip < /data1/informix/test/stock1.gz" END SEQUENCE BEGIN SEQUENCE TYPE PIPE FILE TAPEBLOCKSIZE 0 TAPEDEVICESIZE 0 PIPECOMMAND "gunzip < /data2/informix/test/stock2.gz" END SEQUENCE BEGIN SEQUENCE TYPE PIPE FILE TAPEBLOCKSIZE 0 TAPEDEVICESIZE 0 PIPECOMMAND "gunzip < /data3/informix/test/stock3.gz" END SEQUENCE END OBJECT
Rev. 1.1
31
Further information For additional information and assistance, contact:
[email protected]
For more information about the Alpha RetainTrust program and other sources of support, go to: http://www.hp.com/go/alpha-retaintrust/
For technical and planning information about transition subjects, go to: http://www.hp.com/go/tru64transition/ http://www.hp.com/go/transition-modules/
For information regarding the Tru64 UNIX roadmap, go to: http://h30097.www3.hp.com/unix/downloads/tru64_unix_roadmap.ppt
For IDS system information, go to: http://www-3.ibm.com/software/data/informix/ids/requirements.html
For IDS end-of-service date, go to: http://www-3.ibm.com/software/data/informix/support/plc/eos.html
For IDS general availability date, go to: http://www-3.ibm.com/software/data/informix/support/plc/ga.html
For IDS roadmap, white paper, IBM Informix portfolio, and future directions, go to: http://www-3.ibm.com/software/data/informix/pubs/
For Informix product availability (a spreadsheet which lists the current Informix product that is available and the version of the operating system it supports), go to: http://www-306.ibm.com/software/data/informix/pubs/roadmaps.html
For IDS user manuals, go to: http://www-3.ibm.com/software/data/informix
For the IBM Informix Migration Guide, go to: http://www-306.ibm.com/software/data/informix/pubs/library/ids_94.html
For the Informix and HP manuals that can assist you throughout the transition for both IDS V9.4 and HP-UX, go the following websites: •
IDS V9.4: http://www-3.ibm.com/software/data/informix/pubs/library/ids_94.html
•
HP-UX: http://www.docs.hp.com
Rev. 1.1
32
© 2005 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Itanium and Intel are registered trademarks of Intel Corporation in the U.S. and other countries and is used under license. UNIX is a trademark of The Open Group in the U.S. and/or other countries. 5982-5387EN, 01/2005
