NoCOUGPersistanceofMemoryIssues：nocoug永恒的记忆问题.pptVIP

Shutdown app Shutdown various app servers Shutdown source db Cold backup Upgrade source db to Migrate to Upgrade Oracle client Upgrade Oracle client software to For all machines that have SQL*Plus Upgrade to Install Client install only Tar up client ORACLE_HOME ftp, untar on machines that need SQL*Plus Source db character set Fix any user tablespace issues Import won’t fix them for you Change source db character set WE8MSWIN1252 Siebel requirement Contains euro symbol Is a strict superset of WE8ISO8859P1 Run migrate.sh script Siebel supplied script Generates various scripts Expand.ksh Widen columns for Unicode Impexp06.ksh Import individual tables for large dbs We use full export/import instead Run sun_expand.sql Widen columns in tables outside Siebel schemas Export Source, Import Target Full export of source db Source db is now NLS_LANG AMERICAN_AMERICA.AL32UTF8 Import into target db Target db created as NLS_LANG AMERICAN_AMERICA.AL32UTF8 The conversion setup Source Db Target Db export import Source Db WE8ISO8859P1 WE8MSWIN1252 WE8MSWIN1252 WE8MSWIN1252 AL32UTF8 Modify target db Run impexp06.ksh Handles sequences etc. Run check_schema.sql Find columns that didn’t get widened Various changes on Siebel App side Verify db links to Custdb databases Conversion Complete? Siebel process is done Fix any data issues Multi-byte character data in source db Convert properly to AL32UTF8 Testing Unicode changes GUI changes Performance Unicode processing Users accessing different data Multi-byte Data In Source Db? Source db is WE8ISO8859P1 Single-byte character set Doesn’t support multi-byte characters That’s the official story The reality is somewhat different What, if any multi-byte data is in source db? How to determine correct character set? How to find, how to fix? Japanese, Russian, others? CRM Unicode Conversion Three separate presentations 1) The overall conversion process What we had, what we wanted, how to get there Issues that come up during conversion 2) Mu