Support for Oracle 12cR2 in Content Manager Enterprise Edition V8.6

Important information

Required patches

For Oracle 12.2.0.1:

• Windows: Oracle Windows bundle patch WINDBBP 12.2.0.1.190416(29394003)
• Linux: Patch 25785676 and 29757449
• AIX: Patch 25785676 and 30138470
• zLinux: Patch 25785676

Library server: tnsnames.ora file

EXTPROC_CONNECTION_CM8 =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = IPC)(KEY = ICMLSEXTPROC))
    )
    (CONNECT_DATA =
      (SID = ICMLSExtProc)
      (PRESENTATION = RO)
    )
  )

This entry is required because the "extproc" agent no longer resolves the EXTPROC_CONNECTION_DATA entry in tnsnames.ora. Oracle changed this for security reasons: for more information, see Doc ID 2326592.1.

For information about adding this entry, see the following steps.

New installation of Content Manager Enterprise Edition V8.6 or later with Oracle 12cR2

1. See Preparing Oracle for a Content Manager Enterprise Edition installation.

   Note that:

   • Content Manager Enterprise Edition provides DBCA template files that contain the minimum recommended database instance settings. Your database administrator must closely monitor the Content Manager Enterprise Edition server database environment, and optimize the database workload by changing the settings (for example, the value of sga_target) as necessary.
   • If you create the Content Manager Enterprise Edition database by using the DBCA template: In the Database Identification window, clear Create as Container database.
   • See also Important information above.
2. Install and configure Content Manager Enterprise Edition: Run the Content Manager Enterprise Edition V8.6 or later configuration manager.

Upgrading to Content Manager Enterprise Edition V8.6 or later with Oracle 12cR2

If you are using Oracle 12cR1 and you upgraded to Content Manager Enterprise Edition V8.6 or later, you can upgrade to Oracle 12cR2, and then configure Content Manager Enterprise Edition to use the new version of Oracle.

To configure Content Manager Enterprise Edition to work with Oracle 12cR2, complete the following steps:

1. Make sure that Content Manager Enterprise Edition still works on Oracle 12cR1, and then back up this configuration.
2. Stop all library server and resource manager processes.
3. Make sure that the listener and all of the connections to the Content Manager Enterprise Edition servers are stopped but that the Oracle instance is started. For more information, see Upgrading to Content Manager Enterprise Edition V8.6 for Oracle.
4. Upgrade your Oracle database from 12cR1 to 12cR2:
   1. Back up the current Oracle 12cR1 databases.
   2. Back up the working directory. The default directory is:

      UNIX: /home/ibmcmadm

      Windows: %IBMCMROOT%\cmgmt

   3. Back up the Content Management environment (at IBMCMROOT).
   4. Install Oracle 12cR2.
   5. Run the Oracle Database Upgrade Assistant (DBUA) tool on the Oracle database instance or instances containing a Content Manager Enterprise Edition database, for example, a library server or resource manager. For more information, see the Oracle Database Server documentation.
   6. Recommendation: Set the resource manager database's sga_target to at least 330 MB.
   7. Back up the Oracle 12cR2 databases.
5. Configure the Oracle listener for Oracle 12cR2:
   1. If you defined a dedicated listener for the Content Manager Enterprise Edition database in your old Oracle database, make sure that the same configuration is in the 12cR1 extproc.ora or listener.ora and tnsnames.ora files.

      If the configuration is different, see Creating a dedicated Oracle listener for Content Manager Enterprise Edition (recommended) for a sample configuration. Edit the tnsnames.ora file, and then add the EXTPROC_CONNECTION_CM8 entry (see Important information above). Content Manager Enterprise Edition provides only sample templates; follow the Oracle documentation to configure the Oracle listener. For more information, see the Oracle 12c Net Administrator's Guide.

   2. Make sure that the 12cR2 database connections are working. To do this, start the listener, and then start SQL*Plus with a valid SQL*Plus connection string for a Content Manager Enterprise Edition repository, such as a library server or resource manager, by using the new listener.

      For example, to get the database service name, enter this command:

      lsnrctl status CM_LISTENER_NAME

      To test the library server, enter this command:

      sqlplus icmadmin/password@//myhost.mydomain.com:1522/icmnlsdb.mydomain.com

      To test the resource manager, enter this command:

      sqlplus rmadmin/password@//myhost.mydomain.com:1522/rmdb.mydomain.com

      If the new listener does not start, check the listener's log file. Check the listener template for any discrepancies between the tnsnames.ora, listener.ora, and sqlnet.ora files. Make sure that the three files are synchronized.

   3. If the profile of the user that starts the Oracle listener sets Oracle environment variables, such as ORACLE_HOME, you might need to update the variables to point to Oracle 12cR2 instead, unless you already defined these variables explicitly as part of a dedicated Content Manager Enterprise Edition listener definition:

      Operating system	Variables
      AIX	IBMCMROOT, LIBPATH, PATH
      Linux x86_64	IBMCMROOT, LD_LIBRARY_PATH, PATH
      Windows	IBMCMROOT, PATH

6. Grant the required privileges to library server database users.

   For more information, see Upgrading to Content Manager Enterprise Edition V8.6 for Oracle.

7. Run the configuration manager. To do this, use the cmcfgmgr_CM command that is in the IBMCMREPO/CM8.6 version/bin directory (for example, /opt/IBM/cmrepository/8.6.00.000/bin).

   Select the Oracle 12cR2 product directory to reconfigure Content Manager Enterprise Edition for use with Oracle 12cR2.