E-DB2 How to configure DB2 Connect for Non-Unicode to Unicode?
(Doc ID 658530.1)
Last updated on NOVEMBER 25, 2019
Applies to:PeopleSoft Enterprise PT PeopleTools - Version 8.2 and later
Information in this document applies to any platform.
This document was previously published as Customer Connection Solution 201056086
Reviewed for currency March 2010
Reviewed for currency Aug 2013
implemented comment Dec 2011
Reviewed for currency April 2016
Reviewed for currency Dec 2017
I have some questions regarding installing/converting to a Unicode database in a DB2 z/OS environment.
1. Can there be a mix of Unicode and non-Unicode PeopleSoft Instances in the same DB2 subsystem? If so, how should DB2 Connect be installed and bound? With Unicode settings (no DISABLEUNICODE=1, CODEPAGE=1208 in DB2CLI.INI and ENCODING UNICODE bind parm)?
2. Do I need separate app servers to accommodate Unicode/non-Unicode DB2 Connect installs?
3. We have HCM, EPM, CRM(HRHD), Portal - will all need to be converted to Unicode at the same time since the data flows between the products?
I am confused by the DB2 Connect binds - based on my query of SYSIBM.SYSPACKAGE, there is only one package per DB2 subsystem for each of the DB2 Connect packages. For instance, one of the packages is NULLID.SYSSH402. There is only one row in SYSIBM.SYSPACKAGE for this package and when I do the bind, the row is replaced with the latest bind. It is not like there are different collections for each database alias.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document