Customers planned a unicode migration just change the database character set itself from WE8ISO8859P15 to AL32UTF8 Unicode migration and have two databases on different database character sets for the time of migration to Unicode.
1. Two Databases (db1 and db2) with WE8ISO8859P15 character Set and Shareplex replication in place. All applications are hitting db1 as the main database. Db2 is a hot standby.
2. stop export on db1, let the post queue empty on db2, then Stop post on db2
3. shutdown Shareplex on db2
4. migrate db2 to Unicode using the way described in Metalink Note:260192.1 @@?\rdbms\admin\csalter.plb
5. Start db2 as AL32UTF8 database
6a. . sp_ctrl (db2)>set param SP_OPO_CHARACTERSET WE8ISO8859P15 Note: Setting the parameter SP_OPO_CHARACTERSET WE8ISO8859P15 for db2. This has to be done before poster starts so as data can be properly converted from source character set to target character set 6. start shareplex on db2
7. start export on db1 and post on db2
8. after some time do a maintenance window and make db2 the main database 8a. sp_ctrl (db2)>unset SP_OPO_CHARACTERSET
Note: You can unset SP_OPO_CHARACTERSET on db2 once db2 becomes source at step 8.
9. rebuild db1 from hot backup of db2 and redo Shareplex replication.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center