Calyx RIM Viewing 5.5 CHF 7 Upgrade Guidelines

Calyx RIM Viewing Prerequisite: Oracle Configuration Update

Oracle configuration modifications must be performed on your database server before data migration and before installing Calyx RIM Viewing 5.5. You can increase the maximum size of VARCHAR2, NVARCHAR2, and RAW columns in a non-CDB.

Please note the following descriptions and settings when performing the Oracle configuration update:
  • MAX_STRING_SIZE controls the maximum size of VARCHAR2, NVARCHAR2, and RAW data types in SQL.
  • STANDARD means that the length limits for Oracle Database releases prior to Oracle Database 12c apply (for example, 4000 bytes for VARCHAR2 and NVARCHAR2, and 2000 bytes for RAW).
  • EXTENDED means that the 32767 byte limit introduced in Oracle Database 19c applies.
  • The COMPATIBLE initialization parameter must be set to 12.0.0.0 or higher to set MAX_STRING_SIZE = EXTENDED.
  • You can change the value of MAX_STRING_SIZE from STANDARD to EXTENDED. However, you cannot change the value of MAX_STRING_SIZE from EXTENDED to STANDARD.
A non-CDB is any database before Oracle 12c, or a 12c database created without the enable_pluggable_database clause.

To increase the maximum size of VARCHAR2, NVARCHAR2, and RAW columns in a non-CDB:

  1. Shut down the database. 
  2. Restart the database in UPGRADE mode.
  3. Change the setting of MAX_STRING_SIZE to EXTENDED.
  4. Run the rdbms/admin/utl32k.sql script.
    You must be connected as SYSDBA to run the script.
  5. Restart the database in NORMAL mode. 
    Note: The utl32k.sql script increases the maximum size of the VARCHAR2, NVARCHAR2, and RAW columns for the views where this is required. The script does not increase the maximum size of the VARCHAR2, NVARCHAR2, and RAW columns in some views because of the way the SQL for those views is written.
  6. Run the rdbms/admin/utlrp.sql script to recompile invalid objects. You must be connected as SYSDBA to run the script.