Release notes - IBM InfoSphere Optim 11.3

• With the archiving or data growth features of Optim, you can segregate historic data from current activity and safely remove it to secure offline storage, access the archived data easily, and restore archived data to its business context when necessary.
• The Optim test data management capacity lets you create and populate appropriately sized development and test environments, automatically or manually edit the data in these environments to match your test cases, and compare test results with your original data.
• Data masking features help you to prevent misuse of information by masking, obfuscating, and privatizing personal information that is propagated outside your production environment.

• Oracle 18c – at the supported support level.
• Oracle 19c – at the supported support level.
• PostgreSQL 9.4 – at the supported support level.
• PostgreSQL 9.5 – at the supported support level.
• PostgreSQL 9.6 – at the supported support level.
• PostgreSQL 10.7 – at the supported support level.
• PostgreSQL 11.2 – at the supported support level.
• Silent install fix.
• PR0CNFG DB alias functionality for UNIX.
• Audit record Purge enhancements.
• Work order REST APIs.
• ODPP Age Provider enhancements.
• Java.
  • The version of Java that Optim ships and uses is upgraded to the Oracle July 2019 CPU. This is Java 8.0 SR5 FP37.

• Platform support added:
  • Windows Server 2016.
  • SUSE 12.
• Database support added:
  • Db2 11.1 – supported. Includes support for Db2 BLU (column-organized tables). Temporal Tables are not yet supported.
  • Oracle 12c on SUSE 12.
  • SQL Server 2017 – supported. Temporal Tables are not yet supported.
  • Microsoft Azure.
  • Hive: Support on Windows and Linux has been upgraded to version 2.3.1.

    The following Optim functions are supported:

    • Archive.
    • Compare.
    • Convert.
    • Create.
    • Extract.
    • Load.
    • Report.
    • Restore.

    The following Optim functions are not supported:

    • Delete.
    • Edit.
    • Insert.

    The following capabilities are also supported:

    • Optim relationships.
    • Primary keys.

    The following new capabilities have been added to Hive support in this release:

    • Archive.
    • Security – Kerberos can be used for authentication in Hadoop secure mode.

      For detailed configuration instructions, see http://www.ibm.com/support/docview.wss?uid=ibm10739541.

    The following Hive products are supported:

    • Apache Hadoop Hive 2.0.
    • Cloudera CDH Hive 5.4.
    • Hortonworks Hive 2.3.
• Other enhancements:
  • Cloud WORM.

    EMC Elastic Cloud Storage (ECS).

  • Java.

    The version of Java that Optim uses has been upgraded to the Oracle July 2018 CPU. This is Java 8.0 SR5 FP20.

• Red Hat Enterprise Linux 7.

  Optim can now be installed and run on RHEL 7.

  The document OptimConnectServer_533_inst_UNIX.pdf gives instructions on how to have the Optim Connect Server start at system boot time. For RHEL 7, this process is different and the document will be updated in a future release. See Configure the Optim Connect Server to start at boot time on RHEL 7 for instructions on how to have the Optim Connect Server start at system boot time for RHEL 7.

• Support for Oracle 12c is added for Optim running on the following platforms:
  • AIX.
  • RHEL.
  • Windows (32-bit and 64-bit).
• The JRE used by Optim has been upgraded for the Oracle October 2017 Java CPU.
• TLS 1.2.

  Optim now uses and requires TLS version 1.2 as it is more secure than previous versions.

• DB2 for iSeries.

  DB2 for iSeries is supported through Federation Server, that is included in DB2 11.1.

• Update Enhancements.
  • When updating Optim Runtime services from a previous 11.3.0 release, the installer will back up the rt/bin directory (all platforms), and copy the license files (all platforms) from the backup directory to the new installation (rt/bin) directory. The installer will then preselect the licenses that you have so you do not need to select them.
  • When updating Optim Runtime services from a previous 11.3.0 release, the installer will copy any Optim shell scripts from the backup directory to rt/bin and append '.orig' to the file name.
  • When updating the Optim Web Applications component from a previous 11.3.0 release, the installer will back up the shared/web/app directory and copy any LDAP definitions from the backup directory to the new installation directory. If you use the WAS-CE component, you must then reapply the LDAP definitions.

1. Oracle 12c on Solaris is currently not supported. Look for this in a future Fix Pack or Release of Optim.
2. Oracle 12c on SUSE is currently not supported as it requires SUSE 12, which Optim does not yet support. Look for this support in a future Fix Pack or Release of Optim.
3. Oracle 12c supports object names (tables, columns, and so on) that have more than 63 characters. Optim currently does not support this. Look for this support in a future Fix Pack or Release of Optim.
4. Oracle 12c provides a COMMON USER that can perform administrative tasks that are specific to the CDB or PDB, such as plugging and unplugging a PDB. Support of COMMON USER to create the Optim Directory, or access DB Aliases, is not currently supported by Optim. Look for this support in a future Fix Pack or Release of Optim.
5. Microsoft SQL Server 2016 Always Encrypted for VARCHAR(MAX) and VARBINARY(MAX) has been turned off. This support was initially shipped with Optim 11.3.0.5, and a subsequent iFix (iFix 30) has been provided for 11.3.0.5 to not accept Always Encrypted on VARCHAR(MAX) and VARBINARY(MAX). With the current limitations from Microsoft, and the current imlementation of Optim, data corruption will occur. It is therefore strongly recommended that customers running Optim 11.3.0.5 and using Always Encrypted apply iFix 30. (For more information, contact Optim support.) Look for support of Always Encrypted for VARCHAR(MAX) and VARBINARY(MAX) in a future Fix Pack or Release of Optim.

1. Optim Connection Manager receives an ORA-12505 error when connecting to an Oracle 12c Pluggable Database (PDB).

   For information on how to resolve this, see Technote 2014816.

2. Optim Connection Manager is unable to test properly the connection to SQL 2008 database while adding Optim Directory.

   For information on how to resolve this, see Technote 2015748.

3. IBM Installation Manager will not warn you if WAS-CE or OCM is running while you try to update or uninstall the WAS-CE component. To avoid any issues, ensure that all Optim components are completely shutdown before updating or uninstalling any Optim component.
4. When installing Optim Runtime Services on Windows, IBM Installation Manager may fail to create one or more start menu or desktop shortcuts (icons). You can easily create any missing shortcuts, which could be for the Optim configuration program (PR0CNFG.EXE), Optim tool (PR0TOOL.EXE), or Optim Scheduler (PR0SMON.EXE).

• Create a file in /etc/systemd/system named irpcd.service with the following contents, replacing <navroot> with the full pathname of the navroot directory where Optim Connect Server has been installed.

  #
  # Optim Connect Server startup
  #
  [Unit]
  Description=Optim Connect Server
  
  [Service]
  ExecStart=<navroot>/bin/irpcd 
  Type=forking
  KillMode=process
  Restart=on-failure
  
  [Install]
  WantedBy=multi-user.target
  

• To enable startup of the service permanently when the system is booted, enter:

  systemctl enable irpcd.service

• Now you can start the service:

  systemctl start irpcd.service

• To verify that the service is running, use the systemctl status command:

  systemctl status irpcd.service

irpcd.service - Optim Connect Server
   Loaded: loaded (/etc/systemd/system/irpcd.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2018-04-17 13:19:55 PDT; 2s ago
  Process: 9642 ExecStart=/home/optim/navroot/bin/irpcd start (code=exited, status=0/SUCCESS)
Main PID: 9647 (irpcd)
   CGroup: /system.slice/irpcd.service
           └─9647 /home/optim/rt/navroot/bin/irpcd start

Apr 17 13:19:55 OPTIM-RHEL7 systemd[1]: Starting Optim Connect Server...
Apr 17 13:19:55 OPTIM-RHEL7 irpcd[9642]: Starting a daemon process...
Apr 17 13:19:55 OPTIM-RHEL7 irpcd[9642]: Starting a daemon process...
Apr 17 13:19:55 OPTIM-RHEL7 irpcd[9642]: A daemon process was started
Apr 17 13:19:55 OPTIM-RHEL7 systemd[1]: Started Optim Connect Server.

• The following databases are now supported in Toleration mode:

  DB2 11.1

  DB2 for z/OS 12

  Teradata 15.0

  Netezza 7.1, 7.2

  Sybase 16 SP2

  SQL Server 2016

• The JRE used by Optim is upgraded from version 1.6 to version 1.8.
  Note: As Oracle does not ship a 32-bit JRE at the 1.8 level for Solaris, Optim for Solaris continues to ship and use JRE at the 1.6 level.
• SQL Server 2016 Always Encrypted is supported.

  Please ensure a version of the Microsoft SQL Server ODBC driver is used that supports this functionality. The minimum version is 13.00.4413. Also required is iFix 004 – please contact support to obtain it.

• SQL Server Uncommitted Read is now supported.
• Oracle 11.2 and higher.

  The Optim stored procedures have been updated so that access to sys.user$ and sys.enc$ tables are no longer required.

• Remove Clear Text Passwords for ODPP lookup functions in Lua.

  Lua Column Map procedures no longer need to code the password as clear text in the Lua Column Map procedure source text. The following new Optim functions are provided to extract the values from a named DBAlias defined in the Optim Environment:

  optim.dbalias.getconnect(dbalias_name) – Retrieve the connect string associated with the named DBAlias.

  optim.dbalias.getuser(dbalias_name) – Retrieve the RDBMS User name associated with the named DBAlias.

  optim.dbalias.getpassword(dbalias_name) – Retrieve the password for the User name associated with the named DBAlias.

  The values retrieved from the invocation of these new functions are then used during the construction of the ODPP Lookup command. Normally the command string is constructed by concatenating a series of String Literals and values to form the complete command.

  Note: These new functions are optional in nature. If a customer has another mechanism for acquiring these values it is not required that these functions be used. Customers are free to update their LUA Column Map procedures over time to use these new functions to remediate procedure instances that contain sensitive data.
• Netezza Multi Schema is now supported.
• Optim Security Exit enabled.

  Due to a change in the licensing architecture in 11.3.0.4, the Security Exit was disabled. It has been enabled in release 11.3.0.5.

• Metering Enhancements.
  • The accuracy of the byte count of what is extracted from the database has been improved.
  • Table-wise byte count now included in the report. To enable this, in Trace Settings select:

    Trace Components: NEC Extract File Builder (EFB).

    Trace Options: Option 13.

  • The correlation between Optim and Optim for z/OS has been improved.
  • A Personal Options has been added to Format Numeric Values (to have comma (,) separators to aid in readability).

• Detailed product description, including a description of new functions
• Product-positioning statement
• Packaging and ordering details
• International compatibility information

• AIX® 5.2
• Solaris 8
• Windows 2000
• HP-IA®

• DB2 LUW v9.7 FixPack 5 or higher is required on the Optim client/server.
• Optim Load into a DB2 z/OS system does not support object names (for example, table names, column names, and so on) that contain MBCS-type characters.
• CLOB and DBCLOB data is not supported in an ASCII or Unicode tablespace.