We are planning to migrate our Oracle DB to oracle ExaData DB, Will Pega support ExaData DB ? on Pega V7.2.1 & V7.3.1, If so can you please help us with below questions/Clarifications:
1)Pega7 7.2.1 and 7.3.1 - Current Oracle database uses UTF8 Charset in the database. Is AL32UTF8 a supported character set for operating with an Oracle DB?
2)Pega 7 7.2.1 and 7.3.1 - Is “oracle advance compression” compatible with Pega – should this feature be disabled?
3)Pega7 7.2.1 Installation instructions contains a note about “Java enablement” when installing/configuring the oracle database. Please find/provide the excerpt with the Oracle settings that are discussed in the install documentation.
So (1) depends on the length semantics. For AL32UTF8 I would be sure character length semantics are in place for the database prior to installation. In some circumstance I believe we do generate column level CHAR for the length semantics. This will prevent issues of data storage problems (varying character data is measured in characters - not bytes)
(2) I do not know - if it is transparent to the application then it should work - it is unclear regarding performance impact. Other folks may know
(3) Consult the ORACLE documentation for enabling JAVA. This is in order for User Defined Functions we have that extract data from the BLOB data for reporting purposes. Using this feature is not recommended for production environments. Reporting data should be exposed at that point and not require extracting from the BLOB.