Professional Documents
Culture Documents
Agenda
Introduction
Upgrade Process Overview Some Key Concepts New Data Type Conversion Performance Tuning Q&A
Focus on Customizations
Improved Performance
What is an Upgrade?
The process of getting a customers existing production database up on the new release Application Upgrade
Migrate object definitions
from new application release to your production database
1. Analyze and Preserve Customizations New Release
3. Convert Data
Upgrade Delivery
GA of new release CD is prior to Upgrade GA
Customer installs Demo database and code line Demo to Demo compare reports
New in PT8.48 Copy of Current Demo orientation More robust and flexible than Upgrade Assistant
Completed
Auto Run
Agenda
Introduction
Upgrade Process Overview Some Key Concepts Data Type Conversion Performance Tuning Q&A
Compare/Preserve Customizations Copy New Release Objects Data Conversion Alter Tables and Migrate System Data Complete Manual Setup
Copy of Production
New Demo
Run application reports to ensure consistency of data Functional analysis and pre-upgrade transaction processing Data mappings and default values
Copy of Production
Identify Customizations
Rename Records and Fields
Full database compare between Copy of Production and old release Demo database Resultant project contains customized objects Project has to be named UPGCUST
3. Rename Records/Fields 5. Remove non-custom patches from UPGCUST project
Old Demo
UPGCUST project
Copy of Production
Tools Upgrade
Upgrade Copy of Production database to new Tools release Upgrades to 9.0 require PT8.48 or above
ELS 9.0 upgrade is the only exception
Data type conversion on Oracle and MSS for 9.0 Integration Broker Conversion
Copy of Production
Node Message
Node Message Queue Services, Service Operations, Service Operation Versions/Routings Application Classes and Service Operation Handlers
Compare/Copy Customizations
Rename database tables in COP database Compare custom projects in COP to new release Demo database
UPGCUST project definition is re-used UPGCUSTIB project is created by comparing IB objects
Analyze upgrade status for custom objects Apply customizations to new Demo database
Copy custom objects to preserve them
Copy of Production
New Demo
Migrate object definitions plus customizations from the new Demo to the COP Data mover scripts have replaced time consuming full database compare/copy Copy trees and roles using UPGNONCOMP Copy Integration Broker objects using UPGIBCOPY Create tables Alter tables without deletes
New Demo
9. Copy object definitions 10. Creates/Alters without Deletes
Copy of Production
Copy of Production
New Demo
Copy of Production
Data Conversion Alter Tables and Migrate System Data Complete Manual Setup Test your Upgrade
Agenda
Introduction
Upgrade Process Overview Some Key Concepts New Data Type Conversion Performance Tuning Q&A
Old Demo
Copy of Production
Prepare DB Identify Customizations Upgrade Tools Export objects Save Customizations Create/Alter Data Conversion Complete Migration Manual Setup
New Demo
Copy Objects
*Prepare DB Upgrade Tools Import objects Create/Alter Data Conversion Complete Migration *Manual Setup
*possible shortcut
*Unchanged Object was modified by customer before the comparison release date
Target Status
Same Absent (*)Changed or (*)Unchanged (*)Changed or (*)Unchanged (*)Changed or (*)Unchanged (*)Changed or (*)Unchanged (*)Changed or (*)Unchanged
Action
None Copy? Delete? Copy? Copy? Copy? Copy?
System Data
Data that is necessary for any transaction processing
DLXXSYS_N DLXXSYS_R New Release Demo
Deletes rows in
COP based on WHERE conditions Imports data using Import * option
Overwrites the
data on COP for the specified tables Imports data using REPLACE_DATA option DLXXSYS_U
DLXXSYS_I
Updates rows in
COP with same keys as new release Imports data using UPDATE_DUPS option
Tablespaces
REL SQL scripts are delivered with new tablespace information DBTSFIX aligns tablespaces in the delivered release scripts
with those on the Copy of Production (target) database
Record DDL is set to the new tablespace information TABLESPACEALTERTABLES.sql is a generated script to alter
tables in PT84TBLSPC project
Edit the script for tablespace names and sizing and then run it
Application Tablespaces
PeopleSoft based tablespaces and Custom tablespaces
XXDDL.sql script (XX is product line identifier)
Tablespaces
Contains DDL commands to create all PeopleSoft tablespaces Edit the script to create just the new tablespaces
Custom Tablespaces (use either of these methods)
1. 2.
Update Tools for each record that will go into a custom tablespace (App Designer or update PSRECTBLSPC) Change the SQL in the Create/Alter scripts to create tables in the correct tablespaces
SETSPACE.sqr
Identifies missing tablespaces from the system catalog Identifies tables mapped to invalid tablespaces Reset the combinations to correspond to COP for all existing tables Synch App Designer with System Catalog for Custom tablespaces Run multiple times at various stages to ensure DDL integrity
Agenda
Introduction
Upgrade Process Overview Some Key Concepts New Data Type Conversion Performance Tuning Q&A
MS SQL Server
Variable length Data types padding blanks overhead is eliminated Avoid deprecated data types
Oracle 9i/10g or later MS SqlServer 2005 or later Both Unicode and Non-Unicode databases
Unicode
LOBs for Long Varchar and Long Raw Character Length Semantics for CHAR
Unicode
NVARCHAR(n) for NCHAR and Long Character NVARCHAR(max) for Long Character VARBINARY(max) for Image
NonUnicode
CLOB
Image
BLOB
VARCHAR2 (n*3) VARCHAR2 (n*3) when 1 <= n < = 4000 LONG VARCHAR when n = 0 or n > 4000
Unicode
Image
LONG RAW
BLOB
NonUnicode
Long Character(n)
TEXT
VARCHAR(n) When n>0 and n <= 8000 VARCHAR(max) When n=0 and n>8000 VARBINARY(max)
Image
IMAGE
Character(n)
NVARCHAR(n) NVARCHAR(n) When n>0 and m<= 4000 NVARCHAR(max) When n=0 and n>4000 VARBINARY(max)
Unicode
Long Character(n)
Image
IMAGE
Database settings and ALTER TABLE PSBUSPRIMGLANG MODIFY (IMGSEG BLOB); Instance level parameters Generate Alter table scripts (delivered Java Utility) Run the Alter scripts Bit flag update on PSSTATUS
MS SQL Server
CREATE TABLE PSYEMPL_PHOTO (EMPLID VARCHAR(11) NOT NULL, EMPLOYEE_PHOTO VARBINARY(MAX) NULL)
Copy of Production on MSS2005 and PT8.48 or higher Verify Database Settings Create/Build Alter project Run the Alter scripts Bit flag update on PSSTATUS
MS SQL Server
Non-Unicode
Agenda
Introduction
Upgrade Process Overview Some Key Concepts Data Type Conversion Performance Tuning Q&A
Performance Tuning
Tuning for Move to Production Process Improvement, Automation, Concurrency, Best Practices Customer Database Upgrade program
Performance Tuning
Tuning for Move to Production
Preparing Your Environment
Network Server Database and File Server Workstations Database sizing Database level parameters Split the alter table script into small units, especially for large tables, and then run them all concurrently Run Data Conversion concurrently (unless otherwise instructed in the upgrade documentation) Run Data Conversion AE program via Change Assistant on the server
Performance Tuning
Process Improvement, Automation & Concurrency
Process Improvements Database compare between old release DEMO and the COP Streamlined compare report analysis Simplified process to preserve customizations New release metadata imported to COP via Data Mover Replaces long-running, memory-intensive copy process ReCreate only modified indexes Change Assistant templates provide automated steps Concurrency available in Change Assistant Create tables and Alter w/o Delete script steps Data Conversion groups, unless otherwise documented Data Type Conversion Alter scripts
Performance Tuning
Best Practices
Data Conversion Code Mutually exclusive code allows conversion concurrency Set based processing for high volume tables Recommended performance indexes for data conversion Use of temp tables reduces I/O & avoids locking contention ReUse flag eliminates SQL recompile in DoSelect %UpdateStatistics after high volume row inserts %TruncateTable, faster than Delete from table Avoid Log Messages in Row-based processing
Performance Tuning
Best Practices
Leverage RDBMS-specific Features
Oracle PARALLEL & NOLOGGING clauses in CREATE INDEX syntax Faster index creation for tables that have large # of rows EXTENT MANAGEMNT LOCAL AUTOALLOCATE in Create Tablespace DDL Extent information tracking is done using bitmaps DB2 z/OS VOLATILE clause on Create table eliminates incorrect statistics on temp tables and their instances DB2 LUW VOLATILE and LOCKSIZE TABLE clause on Alter table eliminates incorrect statistics & database locking on temp tables and their instances
Program Objective
To identify and resolve upgrade performance issues related to customer data volume and composition. Extends Superior Ownership Experience commitment