IBM Content Manager Version 8.5 Fix Pack 1 Readme

This readme document contains information about installation and removal of the fix pack and about known problems, restrictions, and solutions in support of IBM® Content Manager Version 8.5.

Readme file for:
IBM Content Manager
Product or component release:
Version 8.5
Update name:
Fix Pack 1
Fix ID:
  • 8.5.0.100-ECM-CM-WIN-fixpack1
  • 8.5.0.100-ECM-CM-AIX-fixpack1
  • 8.5.0.100-ECM-CM-SOL-fixpack1
  • 8.5.0.100-ECM-CM-LNX-fixpack1
  • 8.5.0.100-ECM-CM-zLNX-fixpack1
Publication date:
25 April 2014
Last modified date:
12 June 2015
Online version of readme file: CM_8.5.0.1_fix_pack_readme.html
Important: The most current version of the readme file can always be found online.

Download location

Download IBM Content Manager Version 8.5 Fix Pack 1 from the following location: Fix Central Download Support site or access the fix pack from the table below.

Table 1. Files associated with readme file
Platform File Name
Windows FP8.5.00.100_installer_win.zip
AIX FP8.5.00.100_installer_aix.tar.Z
Solaris SPARC FP8.5.00.100_installer_sun.tar.Z
Linux FP8.5.00.100_installer_lnx.tar.gz
Linux zSeries FP8.5.00.100_installer_zlnx.tar.gz

Known problems, restrictions, and solutions

Known problems, restrictions, and solutions that affect administration and usage of fix packs are documented as techdocs in the product support knowledge base.

To review all known problems, restrictions, and solutions that affect Version 8.5 fix packs, use the following link to query the product support knowledge base: IBM Content Manager Enterprise Edition Version 8.5.0 or IBM Content Manager for z/OS Version 8.5.0

In addition, the fix pack includes the following known problems:
  • Known issues while upgrading to Version 8.5 Fix Pack 1:

    If you are upgrading to IBM Content Manager Version 8.5 Fix Pack 1 on Linux, you might experience DB2® instance down. In this case, you need to apply DB2 APAR IC98362 (for DB2 Version 10.1) or IC98880 (for DB2 Version 10.5) and try the upgrade again.

  • Known issues after Version 8.5 Fix Pack 1 is removed:

    Before the Version 8.5 Fix Pack 1 release, the resource manager and Net Search Extender passwords in the library server were supported with lengths up to 24 bytes long. After the upgrade, you can modify the passwords lengths up to 32 bytes long. Note that the previous releases do not support these passwords lengths. If you remove Version 8.5 Fix Pack 1, you might need to modify the passwords back to the supported length in order for the system to operate properly. If passwords lengths are less than 24 bytes long, no action is needed after you remove Version 8.5 Fix Pack 1.

Prerequisites for Version 8.5 Fix Pack 1

The official statements for hardware and software support for IBM Content Manager are provided as part of the hardware and software requirements for IBM Content Manager Version 8.5.

The fix pack includes the following new prerequisite:

  • IBM Content Manager for z/OS Library Server and Resource Manager have a new requirement: Integrated Cryptographic Service Facility

    As this fix pack contains stronger encryption for passwords, you need to install Integrated Cryptographic Service Facility, ICSF, on the z/OS platform. ICSF is a component of z/OS and it is included in the base product. ICSF provides cryptographic support either in its own software routines or through access to the cryptographic hardware available on System z. Refer to http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/TD103782 for the supported hardware and operating system releases.

Installing IBM Content Manager Fix Pack 1

To install an IBM Content Manager Version 8.5 fix pack, you determine where the fix pack should be installed, prepare the environment for the fix pack installation, complete the installation worksheet for the fix pack programs, install the fix pack, and verify the fix pack installation.

A single installation program installs the fix pack. All of the components installed by the original installation program are updated by this fix pack installation program. You install the fix pack to the repository installation directory (IBMCMREPO) first, and then use the repository installation's updated version of Configuration Manager to update the target installation (IBMCMROOT) with the fix pack.
Restriction: If you install the fix pack on a reference machine without IBM Content Manager Version 8.5 installed to the repository directory, the updated Configuration Manager from the fix pack can only apply the fix pack on a target machine with previously installed and configured IBM Content Manager Version 8.5 components. It cannot install and configure new components. To install and configure new components at this fix pack level, both the fix pack and IBM Content Manager Version 8.5 must be installed to the repository installation directory on the reference machine. For IBM Content Manager for z/OS components, you must install IBM Content Manager for z/OS Version 8.5 using SMP/E first before the fix pack.

Before you install the fix pack on Windows

Before you run the fix pack installation program on Windows®, you must prepare the environment.

  1. Perform these steps to prepare your Windows environment for fix pack installation:
    Table 2. Steps to prepare the Windows environment
    If the following statement is true Perform this step
    If you have the library server monitor running: Stop the monitor.

    Stop the service ICM LS Monitor DBNAME.

    If you are using DB2: Stop the DB2 instance where the IBM Content Manager databases are installed.

    Enter the following command to exit all DB2 applications: db2stop

    If you are using DB2 and DB2 Net Search Extender: Enter the following command: db2text stop
    If you are using DB2 and DB2 Text Search: Enter the following command: db2ts "STOP FOR TEXT"
    If you are using DB2: Start the DB2 instance:
    1. Enter db2start at a command prompt.
    2. If you use DB2 Net Search Extender, enter db2text start at a command prompt.
    If you installed IBM Content Manager Services for Lotus® Quickr® Version 1.0: Delete win32serv.dll and WinFileService.dll from your WINDIR\system32 directory if these two files exist.
  2. Optional: Recommendation: Create an index on the RMREPLICATION table to improve the fix pack installation and replication performance:
    Option Description
    DB2 Enter the command: CREATE INDEX IDX_REP1 ON RMREPLICATION (PROCESSTIMEOUT ASC, REP_REPLICATETYPE ASC)

    RUNSTATS ON TABLE schema_name.RMREPLICATION WITH DISTRIBUTION AND DETAILED INDEXES ALL

    Oracle Enter the command: CREATE INDEX IDX_REP1 ON RMREPLICATION(PROCESSTIMEOUT ASC, REP_REPLICATETYPE ASC);

    COMPUTE STATISTICS TABLESPACE REPLICAS;

    If there are many items and parts in your content management system (that is, many rows in these tables), then the creation of the index might take a long time.
  3. Optional: Recommendation: Create an index on the RMOBJECTS table to improve the background performance:
    Option Description
    DB2 Enter the command: CREATE INDEX IDX_OBJ_REFDATE ON RMOBJECTS (OBJ_REFERENCEDDATE, OBJ_STATUS, OBJ_STAGEDVOLUMEID)

    RUNSTATS ON TABLE schema name.RMOBJECTS WITH DISTRIBUTION AND DETAILED INDEXES ALL

    Oracle Enter the command: CREATE INDEX IDX_OBJ_REFDATE ON RMOBJECTS (OBJ_REFERENCEDDATE, OBJ_STATUS, OBJ_STAGEDVOLUMEID);

    COMPUTE STATISTICS TABLESPACE OBJECTS;

    If there are many items and parts in your content management system (that is, many rows in these tables), then the creation of the index might take a long time.
  4. Important: Stop all resource manager services Purger/Migrator/Stager/Replicator by using the System Administration Client or the resource manager administration console.
  5. If you are using Oracle and have it installed: Ensure that all of the connections to the IBM Content Manager servers are stopped but the listener and your Oracle instance are started. You or your Oracle DBA should quiesce all user activity or terminate all user sessions on the IBM Content Manager library server database (whether or not Oracle indicates that they are active). Additionally, extproc processes might still be alive even after user sessions are terminated. Make sure to stop them before installing the Fix Pack by completing the following steps:
    1. Open the Windows Task Manager.
    2. Click Processes.
    3. Click each process with the name extproc.exe and click End Process.
  6. If you have multiple active Oracle homes installed on the same Oracle server, then make sure that the IBM Content Manager runtime environments can correctly access the IBM Content Manager databases. Verify that the DB2 Content Manager processes are started with correct values for the intended Oracle Home in such environment variables as ORACLE_HOME, PATH, and CLASSPATH.
  7. Configure debug logging.

Before you install the fix pack on AIX, Linux, and Solaris

Before you run the fix pack installation program on AIX®, Linux®, or Solaris, you must prepare the environment.

Restriction: After you install IBM Content Manager on AIX, Linux, or Solaris, the IBM Content Manager file sets do not reflect the current version of the product. To retrieve the correct product level and determine whether the target installation should be updated with the fix pack, enter this command on target machine:
/opt/IBM/db2cmv8/bin/cmlevel -l
  1. Perform these steps to prepare your AIX, Linux, or Solaris environment for fix pack installation:
    Table 3. Steps to prepare the AIX, Linux, or Solaris environment
    If the following statement is true Perform this step
    If you have the library server monitor running: Stop the monitor.

    Enter the following command: /etc/rc.cmlsproc -shutdown

    If you are using DB2: Stop the DB2 instance where the IBM Content Manager databases are installed.
    Enter the following command, where the user ID of the DB2 instance is db2inst1 by default:
    su - userID of the DB2 instance
    db2stop
    
    For AIX only: As root, enter the /usr/sbin/slibclean command to unload unused shared libraries from memory.
    If you are using DB2 and DB2 Net Search Extender: Enter the following command: db2text stop
    If you are using DB2 and DB2 Text Search: Enter the following command: db2ts "STOP FOR TEXT"
    If you are using DB2: Start the DB2 instance.
    1. As the root user, enter the following command:
      su - userID of the DB2 instance
    2. Enter the following command:
      db2start
    3. If you have DB2 Net Search Extender installed, enter the following command:
      db2text start
    4. Enter the following command:
      exit
  2. Recommendation: Create an index on the RMREPLICATION table to improve the fix pack installation and replication performance:
    Option Description
    DB2 Enter the command: CREATE INDEX IDX_REP1 ON RMREPLICATION (PROCESSTIMEOUT ASC, REP_REPLICATETYPE ASC)

    RUNSTATS ON TABLE schema_name.RMREPLICATION WITH DISTRIBUTION AND DETAILED INDEXES ALL

    Oracle Enter the command: CREATE INDEX IDX_REP1 ON RMREPLICATION(PROCESSTIMEOUT ASC, REP_REPLICATETYPE ASC);

    COMPUTE STATISTICS TABLESPACE REPLICAS;

    If there are many items and parts in your content management system (that is, many rows in these tables), then the creation of the index might take a long time.
  3. Recommendation: Create an index on the RMOBJECTS table to improve the background performance:
    Option Description
    DB2 Enter the command: CREATE INDEX IDX_OBJ_REFDATE ON RMOBJECTS (OBJ_REFERENCEDDATE, OBJ_STATUS, OBJ_STAGEDVOLUMEID)

    RUNSTATS ON TABLE schema name.RMOBJECTS WITH DISTRIBUTION AND DETAILED INDEXES ALL

    Oracle Enter the command: CREATE INDEX IDX_OBJ_REFDATE ON RMOBJECTS (OBJ_REFERENCEDDATE, OBJ_STATUS, OBJ_STAGEDVOLUMEID);

    COMPUTE STATISTICS TABLESPACE OBJECTS;

    If there are many items and parts in your content management system (that is, many rows in these tables), then the creation of the index might take a long time.
  4. Important: Stop all resource manager services Purger/Migrator/Stager/Replicator by using the System Administration Client or the resource manager administration console.
  5. If you are using Oracle and have it installed: Ensure that all of the connections to the IBM Content Manager servers are stopped but the listener and your Oracle instance are started. Terminate all outstanding extproc processes unless other applications other than IBM Content Manager require them. Oracle occasionally continues to run extproc processes to save time when reloading them. If Oracle reuses an old extproc process that did not pick up the changes to your tnsnames and listener configuration, then a TNS error can result.
    On AIX:
    1. From a command prompt, enter the following command:
      /usr/bin/ps -ef | grep -i oracleSID
      where SID is associated with your IBM Content Manager library server database. The process ID number is displayed in the second column.
    2. For each process ID number, enter the following command:
      /usr/bin/kill -9 processID
      where processID is the process ID number. Ensure that you already stopped active database sessions against the library server (in the previous step) before you run the kill -9 command.
    3. Log in as root and enter the /usr/sbin/slibclean command to unload unused shared libraries from memory.
    On Solaris and Linux:
    1. From a command prompt, enter the following command:
      /usr/ucb/ps -auxww | grep -i oracleSID
      where SID is associated with your IBM Content Manager library server database. The process ID number is displayed in the second column.
    2. For each process ID number, enter the following command:
      /usr/bin/kill -9 processID
      where processID is the process ID number. Ensure that you already stopped active database sessions against the library server (in the previous step) before you run the kill -9 command.
  6. If you have multiple active Oracle homes installed on the same Oracle server, then make sure that the IBM Content Manager runtime environments can correctly access the IBM Content Manager databases. Verify that the IBM Content Manager processes are started with correct values for the intended Oracle Home in such environment variables as ORACLE_HOME, PATH, CLASSPATH, and LIBPATH (AIX) or LD_LIBRARY_PATH (Solaris).
  7. Set up for debug logging.

Completing the installation worksheet for IBM Content Manager

You can use an installation worksheet to gather the information needed to install the fix pack for IBM Content Manager.

This worksheet is valid only when configuring a library server and resource manager database with DB2. For the component or components that you are updating, gather the information listed in the following table. When the installation wizard runs, it automatically prompts you to enter data for any setting that it cannot detect. The table is provided with blank spaces so that you can print it and enter your information.
Supply values for the following table:
Table 4. Installation worksheet for IBM Content Manager
Product component to update Data required Your values
Library server Library server database name  
Library server schema name  
Library server database administration ID  
Library server database administration password  
Library server database connection port  
Resource manager database Resource manager database name  
Resource manager schema name  
Resource manager database administration ID  
Resource manager database administration password  
Resource manager database connection port  
Resource manager application (for each application) Application server home directory  
Application server profile home directory  
Resource manager Web application name  
Application server administration ID *  
Application server administration password *  
Application server node name **  
Resource manager Web server name **  
Application server cluster name ***  

* Only needed if application server security is enabled.

** Only needed if the deployment target is an application server.

*** Only needed if the deployment target is a cluster.

Installing the fix pack for IBM Content Manager

To install the fix pack for IBM Content Manager, run the installUpdate fix pack installation wizard.

You must first install the fix pack to the IBM Content Manager repository on the reference machine, and then use the updated Configuration Manager on this reference machine to update each target machine with the fix pack. The target machines are any computer where one of these system components is installed. Note that a target machine can also be the same as the reference machine. The Configuration Manager will launch the fix pack configuration wizard for a target machine after you select a target machine and click Configuration > Update configuration on the menu bar. The fix pack configuration wizard updates only those system components and components that are local to the computer on which it runs. For example, if your IBM Content Manager library server and resource manager components are installed on different computers, then you need to run the fix pack configuration wizard for both computers.
Complete the following steps to install IBM Content Manager.
Important: The more component views that exist in the library server, the longer that the fix pack installation can take to run because of the need to regenerate the access statements for those component views. Although the generation of an individual access statement for a component view can take only subseconds, the actual time that the installation takes can vary according to your environment, your content management setup, and the number of component views that you have configured.

If you have a large number of component views, such as thousands of views, and if the fix pack upgrade is slow, then you might want to inspect the installation log file during the installation. By inspecting this log file, you can find out if the delay is due to the generation of these access statements. The update configuration log including the generation of the access statements is IBMCMREPO/version/cmcfgmgr/log/hostname/version/cmfpconfig.log, where IBMCMREPO is the installation location on the reference machine as defined by the IBMCMREPO environment variable and version is the fix pack version.

  1. Run the installUpdate program to start the installation.
    Option Description
    AIX, Linux, and Solaris installUpdate
    Windows installUpdate.bat
    The installation wizard detects which IBM Content Manager system components and components are installed on the computer on which it is running and displays the components that will be updated with this fix pack installation.
    Attention: If you close the Configuration Manager before installing the fix pack, you can reopen it by launching the Configuration Manager shortcut or by running the cmcfgmgr_CM script at IBMCMREPO\VERSION\bin\. Then click Configuration > Update configuration on the menu bar.
  2. Continue with the wizard as instructed by the interface panels.
  3. After you enter all configuration information, click Next to begin the fix pack installation.

The fix pack installation and configuration data is retained in log files that are created by the fix pack installation wizard during installation. You can find log files for the installation and configuration in the following locations. In the path for the log file location, IBMCMREPO is the installation directory, version is the fix pack version, and hostname is the name of the host for which the fix pack is being installed.

Table 5. Locations of log files
Log file type Log file location
Installation IBMCMREPO/version/cmcfgmgr/log/hostname/version/fpinstall.log
Removal IBMCMREPO/version/cmcfgmgr/log/hostname/version/fpuninstall.log
Configuration IBMCMREPO/version/cmcfgmgr/log/hostname/version/cmfpconfig.log
Removal of configuration IBMCMREPO/version/cmcfgmgr/log/hostname/version/cmfpunconfig.log
Validation log IBMCMREPO/version/cmcfgmgr/log/hostname/cfgactions.log
Tip: For more information about the log file locations for Version 8.5, see Log file locations.

Installing the fix pack in silent mode

To run a silent installation, enter the following command:
install -i silent -f path/install.rsp
where path/install.rsp represents the complete path and file name for the installation response file. If no path is specified, the default location is the local directory.
To run a silent configuration, enter the following command:
IBMCMREPO/VERSION/bin/cmcfgmgr_CM -f path/config.rsp
where path/config.rsp represents the complete path and file name for the configuration response file. If no path is specified, the default location is the local directory.
For remote configuration, you must specify the login user's password for the target machines too:
IBMCMREPO/VERSION/bin/cmcfgmgr_CM -f path/config.rsp -p password

When the configuration manager runs in silent mode, no windows display and the configuration progresses as if you had entered the response file values into each window.

If you run a silent installation or configuration that stops immediately, you might not see any error messages. Some error messages are hidden when there are no installation windows.

Removing the fix pack

To remove IBM Content Manager Fix Pack 1:

  1. Open the Configuration Manager on the reference machine by running the cmcfgmgr_CM script at IBMCMREPO\VERSION\bin\, or by double-clicking the Configuration Manager shortcut.
  2. Expand the profile and right-click the host from which you will be removing the fix pack, and select Connect and Validate. Enter your user id and password to start the validation process.
    When the validation process completes, click Finish.
  3. In the Configuration Manager menu bar, click Configuration > Remove Operations. The fix pack update wizard opens.
  4. Select Remove the fix pack configuration and click Next. Follow the instructions in the wizard to complete the removal of the fix pack.

Additional updates

IBM Content Manager, Version 8.5 Fix Pack 1 includes the following additional updates.

  • Oracle 11gR2 support for Linux on zSeries®

    Content Manager now supports Oracle 11gR2 (11.2.0.3 or later), for Linux on zSeries.

    Follow these steps to install and configure IBM Content Manager with Oracle for Linux on zSeries:

    1. Install IBM Content Manager Version 8.5 but do not run the Configuration Manager.
    2. Install IBM Content Manager Version 8.5 Fix Pack 1.
    3. Start the Configuration Manager from the Fix Pack 1 repository by running the cmcfgmgr_CM script at IBMCMREPO\VERSION\bin\.

    If you are integrating IBM Content Manager with an LDAP server in this environment, the IBM Tivoli Directory Server client package must be Version 6.3 Fix Pack 28 or later. To download the IBM Tivoli Directory Server interim fix, see: 6.3.0.28-ISS-ITDS-LinuxX64-IF0028. The readme file for this package is at: 6.3.0.28-ISS-ITDS-IF0028.README.

    Attention: To uninstall IBM Content Manager Version 8.5 Fix Pack 1 with Oracle for Linux on zSeries, you must first unconfigure the Library Server component.

  • Enhanced password security

    User passwords in library server now use SHA256 hashing with dynamic hashing capability to increase security. This new feature takes effect when you modify IBM Content Manager passwords or when a new user is created. When you uninstall the fix pack, user passwords are restored to a format supported by previous versions.

    The resource manager and Net Search Extender passwords in library server now use dynamic encryption to increase security. The new encryption process takes place during the Version 8.5 Fix Pack 1 upgrade process and when you create or update the passwords. No user action is required. When you uninstall the fix pack, the resource manager and Net Search Extender passwords are restored back to a format supported by previous releases.

  • Library Server updated tables

    The following library server tables are updated in Version 8.5 Fix Pack 1.

    Table 6. ICMSTSysControl (System Control Table)
    Column Name Data Type Attribute
    TIEPassword2 [DB2] VARCHAR(256) FOR BIT DATA, [ORACLE] RAW (256) nullable
    TIEPassword2
    The password of the TIEUserID.
    Table 7. ICMSTResourceMgr (Resource Manager Table)
    Column Name Data Type Attribute
    RMPassword2 [DB2] VARCHAR(256) FOR BIT DATA, [ORACLE] RAW (256) nullable
    RMPassword2
    The password of the user who will log on to the resource manager.
    Table 8. ICMSTUsers (User Table)
    Column Name Data Type Attribute
    Password2 [DB2] CHAR(256) FOR BIT DATA, [ORACLE] RAW (256) nullable
    Password2
    A hashed form of the password.
  • Windows Service support for Event Monitor and BPM Event Handler

    You can start Event Monitor or BPM Event Handler as a service on Microsoft Windows platforms. For more information about event monitor and BPM event handler enhancements, see http://www.ibm.com/support/docview.wss?uid=swg21666540.

  • Windows domain administration user support for client components

    A Windows domain administration user is now supported to run Version 8.5 Fix Pack 1 installation and configuration with the following considerations:

    • The primary domain group of the Windows domain administration user must be added to the local Windows administrator group.
    • You must choose the ‘Run as administrator’ option when you run the IBM Content Manager installation program or the updated Configuration Manager.
    • A Windows domain administration user can be used to add IBM Content Manager client components only. The client components include connectors, the system administration client, toolkits, and samples.
    • A Windows domain administration user cannot upgrade or update any components from a previous IBM Content Manager version. Only a new installation of IBM Content Manager at Version 8.5 Fix Pack 1 is supported. To achieve this capability, a Windows domain administration user needs to first install the IBM Content Manager Version 8.5 (do not run configuration wizard) and then install the Version 8.5 Fix Pack 1 installation followed by configuration.
    • The IBM Content Manager server components, which include the library server, resource manager database, resource manager application, and the web services application cannot be installed by using a Windows domain administration user.
  • Resource Manager support for Data ONTAP® Snaplock® volumes

    Resource Manager in IBM Content Manager Enterprise Edition Version 8.5 Fix Pack 1 introduces support for Data ONTAP® Snaplock® volumes. Previously Snaplock® volumes were tolerated and files were locked by using the default minimum retention as soon as they were written. For more information, see http://www.ibm.com/support/docview.wss?uid=swg27041658.

  • New maximum number of item types, components, itemtype views, and itemtype subsets

    This fix pack increases the limit for the number of user-defined itemtypes, components, itemtype views that include the base itemtype views, and views of itemtype subsets. Previously, the default (base) itemtype views and itemtype subset views had the maximum ID of 32767. In this fix pack:

    • For itemtype, base item type view, component type, and base component type view, the maximum allowable ID value is 99999.
    • For itemtype subset view and component type subset view, the maximum allowable ID value is 2147483647.

    Library server generates database view names as follows:

    • If the length of user-provided view name is less than or equal to 15 characters, the generated database view name is User-provided view name001.
    • If the user-provided view name is longer than 15 characters:
      • If view ID < 100000, the generated database view name is ICMCaaaaaVbbbbb01. Where aaaaa is five-digit component type ID and bbbbb is five-digit view ID.
      • Before IBM Content Manager Version 8.5 Fix Pack 1, view ID is always < 100000. Now in Content Manager Version 8.5 Fix Pack 1, when view ID >= 100000, the generated database view name is ICMVbbbbbbbbbb001. Where bbbbbbbbbb is six to 10-digit view ID.
  • The Library Server for IBM Content Manager for z/OS can drop empty non-partition table space

    Starting with Version 8.5 Fix Pack 1 of the IBM Content Manager for z/OS library server, you can automatically drop a non-partition table space when it becomes empty. You can select this option by doing the following tasks:

    1. Add a row in ICMST390Control table with OPTIONKEY = 'DROPT' by entering the following command:
      INSERT INTO ?CREATOR?.ICMST390Control VALUES ('DROPT', NULL)
    2. If you use defer DDL to create, update, or delete an item type, you must customize one of the new templates ICMMLSQ1, ICMMLSQ2, or ICMMLSQ3. Each template contains a new step to check whether the non-partition table space is empty. If the non-partition table space is empty, it gets dropped automatically. The new step is included in the generated job only if the previous step in the generated job contains SQL to drop a table in non-partition table space.

Cumulative fix list (APARs)

The cumulative fix list contains all APARs that are fixed in Version 8.5 of IBM Content Manager.

Important: For some APARs, such as security-related APARs, information about that APAR is not made available to customers to avoid compromising customer and product security. If an APAR is listed in the fix list but no information is available, the APAR might be a security APAR.
Table 9. Fix list for IBM Content Manager Version 8.5 Fix Pack 1
APAR Description
Beans
IO20032 When the item.addAttr BEANS API is used to set the attribute value to "empty String", NULL is stored instead.
IO20036 CMBItem.getAttrValue returns a NullPointerException. When a CMBConnection object is disconnected and then reconnected, the cached data is not cleared and reset correctly. This results in the NullPointerException error when the CMBItem.getAttrValue method is called after reconnect.
IO20436 DK Beans API UpdateItemRequest yields unexpected results when the multivalue child attribute is handled. The API incorrectly deletes the first request operation in the request list which causes an unexpected result after the request is executed.
Connector
IO20540 Production client search for documents against an item type that has an attribute of type decimal for an Oracle library server returns an error. This error states the system cannot complete the search.
IO20900 Content Manager API calls are logged at trace level when library server trace user is specified and API ERROR level logging is enabled.
Viewer
IO19513 Watermark on a page of a PDF document is not rendered by the application using the Java Viewer Toolkit.
IO19541 Vertical lines rendered on the PDF page are misplaced by the application using the Java Viewer Toolkit.
IO19709 The extracted text from a PDF document may contain additional spaces by the application using the Java Viewer Toolkit.
IO19828 Text on a page of a MO:DCA document is rendered incorrectly by the application using the Java Viewer Toolkit.
IO20131 Highlight annotations may be incorrectly modified and saved by using JRE 1.7 to a non-transparent value by the application using the Java Viewer Toolkit.
IO20173 Saving a modified TIFF document may be incorrectly sized by the application using the Java Viewer Toolkit.
Library Server
IO19720 In an Oracle RAC high availability environment, the Library Server monitor can sometimes incorrectly mark the Resource Manager as offline.
PI10605 The Resource Manager asynchronous process cannot find the object in the Object Access Method while deleting a part item. The z/OS batch utility did not add the EXTOBJECTNAME value to the URLADDRESS column of the ICMSTITEMSTODELETE table for items with a non-blank EXTOBJECTNAME value (for example: items migrated from Content Manager Version 7).
PI12217 The library server shows S0C4 (protection exception) during retrieve operation as an example. The library server does not verify that the function to allocate storage completed without errors. If the allocation failed, then instead of returning an error, the library server continues to execute routines as if the allocation was successful.
System Administration
IO19020 The LDAP User import utility fails to create a new LDAP user in the Content Manager Library Server if the first and default Resource Manager created during installation has been deleted. An error message can be seen in LDAP import related log files.
IO19493 The LDAP import utility removes empty groups (groups that have no users) during synchronization with the original design. You may want to keep this empty LDAP group because there are some ACLs associated with it, and those groups may be needed later. LDAP users may be imported to that group in the future.
IO19528 If an LDAP group's DN is longer than 128 characters, then the DN is truncated before saving it to the LDAP group's description field. This may cause a mismatch if the truncated group DN in the group description field is compared to the one in the LDAP server, which causes the user/group synchronization to fail.
IO19623 The description field is configurable by design. However, when the nested group support function is enabled for Active Directory, this field is always filled with the LDAP user's DN, not the attribute that is defined in the LDAP configuration.
Knowledge Center
IO17502 When configuring web services for IBM Content Manager, if you want to use the HTTPS for axis2 engine, you must manually add "https" transportReceiver to axis2.xml in the WAS_HOME/profiles/profileName/installedApps/cellName/appName/CMBSpecificWebService.war/WEB-INF/conf directory. See Configuring HTTPS for the IBM Content Manager web services axis2 engine for more information.
IO17540 The IBM Content Manager documentation incorrectly states that the UDFTRACELEVELvariable is an environment variable. See the comments section in the following Knowledge Center topics for the corrections to the documentation:
IO18392 The IBM Content Manager documentation on migration aggregation is incomplete. See the comments section in the following Knowledge Center topics for the addition to the documentation:
IO20282 The IBM Content Manager documentation on the allowed value of the TSM_MAX_WAIT_FOR_FREE_CONNECTION parameter in the RMCONFIGURATION table is incorrect. The documentation has been corrected.
Resource Manager for z/OS
PI07491 After the IBM Content Manager for z/OS resource manager received certain errors from Tivoli Storage Manager, it could no longer perform any other operations. The only solution to this problem was to restart the resource manager.
Table 10. Fix list for IBM Content Manager Version 8.5
APAR Description
Web Services
IO16826 The WSDL file that is generated from the System Administration Client on AIX has a syntax error which causes a parsing error when the web service is used.
IO18389 Web Services logging for Axis2 does not work properly: Nothing is logged after logging is enabled.
IO18507 Web Services returns a "Did not understand 'MustUnderstand'" error when the soap header is set with the 'MustUnderstand' property of 1.
Beans
IO17348 Under certain circumstances document routing operation may fail with error code 4470 and SQLSTATE 0880003. If for any reason library server is restarted in middle of doc routing operations, the doc routing operation that is performed after re-establishing connection with library server will fail.
IO17567 There might be a performance issue when an item is added into a large folder using the DK Beans API. When a new item is added into a folder using the DK Beans API, the API calls the _ddo.update() method to update the folder in the server. This call might be slow if the folder already contains many items (over 200000).
IO18814 The writeObject function returns java.io.NotSerializableException error. When the application calls writeObject(item) (where item is an element of a CMBSearchResults list), the java.io.NotSerializableException error is returned.
Connector
IO17143 The changed name of a system managed storage collection is ignored during an update operation.
IO17333 An add failure due to an undefined collection in the IBM Content Manager for z/OS library server can cause an incomplete transaction in the resource manager.
IO17340 If an item type has two subset item type views, then when the active view is not specified, the base item type view is not picked up as the default active view during a query.
IO17494 A MIME type is set to null with a zero length part content document update.
IO18054 A null pointer exception occurs while item types or views are listed.
IO18076 A timestamp value that is stored in GMT is not returned in GMT.
IO18078 Two undefined semantic types DKConstantICM.DK_ICM_SEMANTIC_TYPE_BASETEXT and DKConstantICM.DK_ICM_SEMANTIC_TYPE_BASESTREAM are deprecated.
IO18772 A synchronization issue in logging with Java API might cause slow performance in a multi-thread environment.
IO19434 When adding a child to an existing resource item when the primary resource manager is down during an update operation, the update operation is sending library server TIEREF, which contains the primary resource manager instead of a replica resource manager that is available. The update text index operation fails for this TIEREF.
IO19521 An error occurs during the update of an Oracle 11g date of an item because there is a data type mismatch. This error occurs when the retrieved Oracle date is returned as a timestamp value.
IO20626 A resource manager explicit transaction is not rolled back when a duplicate unique attribute value error occurs during creation of a resource item.
Business Process Manager Integration
IO18150 If an attribute value contains an ampersand ('&'), the event monitor does not convert it properly to the escaped XML value "&amp;". This causes a parsing error for a custom event handler, which assumes characters are escaped and that '&' is a special character.
IO18279 Both event monitor and BPM event handler stop when the user is logged off from a terminal session on a UNIX platform or if the user exits from a command console on a Windows platform.
IO18448 Content Manager Content Operations logon error ICM7172 occurs when connecting to a new datastore after the connection to the library server was terminated.
IO18707 BPM content operations users receive a DB2 for z/OS timeout error with a Return code: -4499. Reason code: 08001 when they use the getURLFromAttachment function.
Viewer
IO17697 A PDF document with a JPEG2000 image is not rendered correctly by the application using the Java Viewer Toolkit.
IO17807 Stamp annotations with large font sizes and using the italic font style will be rendered incorrectly by applications using the Java Viewer Toolkit. The text will appear truncated.
IO17991 Rendering the first page of a TIFF document with JPEG compressed pages is delayed by applications using the Java Viewer Toolkit.
IO18104 In applications using the Java Viewer Toolkit, related information set on a cut operation is lost in the PAGES_DELETED event.
IO18778 Text annotations with a font size not listed in the properties window resizes the annotation when there are any property updates in applications using the Java Viewer Toolkit.
IO18955 Pages are rendered with missing content when viewing a PDF document by applications using the Java Viewer Toolkit. There will be an ArrayIndexOutOfBoundsException error logged.
IO19404 A red background is incorrectly rendered with a TIFF document by the application using the Java Viewer Toolkit.
Library Server
IO14002 After upgrading to IBM DB2 Content Manager 8.4.3, on power7+ hardware, IBM Content Manager logon time increases to 2-4 seconds.
IO15515 If any transaction failure occurs after the first phase of creating a document, and before the second phase is committed, the INPROGRESS=1 row is kept in the ICMSTITEMS001001 table. This row might use a library server object such as an ACL ID. As a result, that ACL cannot be deleted. In addition, when many of these failures happen, there will be many orphan rows that must be removed from the table for optimal table performance.
IO16923 Content Manager importing and creating text index operations hang when processing some .xls files.
IO16926 Content Manager importing and creating text index operations encounter access violations when processing some .xls files.
IO18661 After upgrading to IBM Content Manager 8.4.3, query searches may fail to find documents if the default CCSID for the database is different from the one for the documents' code page.
IO18837 The use of an uninitialized variable in library server code can cause the data in the EventData1 field of the item audit record to be incorrect. 
IO19351 During logon, you may notice messages that are logged in the library server log even though the logging mode is for ERROR logging only. If the return code from the LDAP user exit is 8020(logon user is not LDAP user) or 8021(no input PASSWORD), the library server logon continues instead of returning an error. Since these are not real errors, they should not be logged if the logging level is at ERROR.
PM78762 Duplicate case statements were generated by the batch load module icmpbl02 for item types with self linking rule.
PM79657 Unable to properly retrieve objects migrated from VisualInfo for a non-English code page database when stored procedures use PARAMETER CCSID UNICODE.
PM80311 XML import of item type with indexes and foreign keys failed with sqlcode -204.
PM85214 Create hierarchical item failed with sqlcode -330 for certain ICM$NAME values.
Resource Manager
IO17703 Security enhancements for IBM Content Manager 8.4.3 since Fix Pack 2 restrict the use of special characters like $ or @ for item ID. Content Manager installations, which were upgraded previously from Visual Info 2.3, Content Manager 7.1, Content Manager 8.3, or Content Manager 8.4.03.301 might have item IDs, that contain restricted special characters “@#$”.
IO17854 When you store an object in a resource manager, that is configured to use TSMPOOLED class device manager, the resource manager log shows a return code of -68 on the first attempt to create a Tivoli Storage Manager handle. However the second attempt succeeds and the Tivoli Storage Manager connection handle is put into the connection pool.
IO17886 When using replicated resource managers, when the database instance for the primary resource manager is shut down and the primary resource manager application is still operational, the Library Server monitor believes that the resource manager remains available. All operations continue to be directed to the primary resource manager and those operations eventually fail because the database is not available. The expected behavior of the library server monitor is to use the secondary replicated resource manager.
IO18132 IBM Content Manager 8.4.03 FP2 strips special characters $ and @ when these characters exist in the transaction ID. This action causes the end-trans operation to fail with an error reported during the update of an object or during the use of the store or update functions of a notelog or annotation. 
IO18298 When a resource manager tablespace other than the default name "OBJINDX" is created, the resource manager validation utility fails to create an index and it reports that the tablespace is not found.
IO18985 When there is no corresponding information in the RMOBJECTS table for a migration task, a retrieval of the object metadata returns a null value. This null object results in a NullPointerException when the resource manager processes object aggregation.
System Administration
IO17873 The System Administration client does not permit leading blank spaces in a user or user group name, and assumes that none will be there. During an update or delete operation, the blank spaces were removed, and as a result the server was unable to locate the definition.
IO18211 If an administrator creates a resource manager definition with a name that includes trailing blanks, then it is not possible to modify a user definition that assigns this resource manager as the default. This problem occurs because the client incorrectly searches for the resource manager with the trailing blanks removed from the name. The client is then unable to load the collections for this resource manager. Since the default collection field is empty and this field is required, it is not possible to save the user definition. 
IO18796 In IBM Content Manager Version 8.4.3, the Content Manager LDAP user import function moved the LDAPUser flag from the description field to the "additional information" field. Most LDAP-related functions can now support the LDAP flag in both places, but the LDAP information in user properties was not fully supported.
Knowledge Center
IO18501 The VWAttachment object definition is not clear for the DKContentOperationsICM searchForOne and searchForMany methods. The documentation has been corrected.

Copyright and trademark information

IBM, the IBM logo, and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at http://www.ibm.com/legal/copytrade.shtml

Notices

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Other company, product, or service names may be trademarks or service marks of others.

THIRD-PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION

The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version.

Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions:
  • the Excluded Components are provided on an "AS IS" basis
  • IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
  • IBM will not be liable to you or indemnify you for any claims related to the Excluded Components
  • IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components.