IBM Content Manager Version 8.6 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.6.

Readme file for:
IBM Content Manager
Product or component release:
Version 8.6
Update name:
Fix Pack 1
Fix ID:
  • 8.6.00.100-ECM-CM-WIN-fixpack1
  • 8.6.00.100-ECM-CM-AIX-fixpack1
  • 8.6.00.100-ECM-CM-LNX-fixpack1
  • 8.6.00.100-ECM-CM-zLNX-fixpack1
Publication date:
15 December 2018
Last modified date:
15 December 2018
Online version of readme file: CM_8.6.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.6 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.6.00.100_installer_win.zip
AIX FP8.6.00.100_installer_aix.tar.gz
Linux FP8.6.00.100_installer_lnx.tar.gz
Linux zSeries FP8.6.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.6 fix packs, use the following link to query the product support knowledge base: IBM Content Manager Enterprise Edition Version 8.6.0 or IBM Content Manager for z/OS Version 8.6.0. For IBM Content Manager for z/OS, also read the cover letter that is shipped with the PTF.

ORA-00600 [25027] might occur when you perform a text search on Oracle 12c R2 CDB/PDB

If you create a item type with text search without update frequency argument for content on Oracle12c R2 CDB/PDB and import some documents in the itemtype, an ORA-00600 [25027] error might occur if you perform a text search before you run text index update manually. This is due to Oracle internal bug26894361. The error for text search query is like this:

ORA-00600: internal error code, arguments: [25027], [4], [4], [4], [1], [], [], [], [], [], [], []

Workaround

  1. Use the following SQL statement to get the text index name:
    SELECT c.COLUMNNAME, c.COMPONENTTYPEID, c.INDEXNAME
    FROM ICMSTNLSKEYWORDS k, ICMSTCOMPDEFS d, ICMSTTEXTINDEXES c
    WHERE k.KEYWORDCLASS = 2 AND
    k.KEYWORDCODE = d.ITEMTYPEID AND
    d.COMPONENTTYPEID = c.COMPONENTTYPEID AND
    k.LANGUAGECODE = 'ENU' AND
    c.COLUMNNAME = 'TIEREF' AND
    k.KEYWORDNAME = '<ITEM TYPE NAME>';
  2. Login to SQLPlus as the IBM Content Manager admin user. (The default username is icmadmin.)
  3. Run the following SQL statement to update the text index:
    execute ctx_ddl.sync_index ('text_index_name', '2M');
    Or run the following SQL statement to rebuild the index: 
    alter index text_index_name rebuild
  4. Perform the text search again.

Prerequisites for Version 8.6 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.6.

Mandatory prerequisites

None.

Optional prerequisites

None.

More information

For more information about the hardware and software requirements for IBM Content Manager, see:

Installing IBM Content Manager Fix Pack 1

To install an IBM Content Manager Version 8.6 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.6 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.6 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.6 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 V8.6 using SMP/E first before the fix pack.
For information about supported component and product compatibility combinations, see IBM Content Manager V8.6 Component and Product Compatibility.

Before you install the fix pack on z/OS

The fix packs on z/OS are installed by using SMP/E. During the SMP/E RECEIVE process, installation instructions are in the ++HOLD sections, which can be found in the SMPRPT DD name in the RECEIVE job. The ++HOLD sections must be reviewed before the start of the SMP/E APPLY process.

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:
    If the following statement is true Perform this step
    The library server monitor is running on Oracle Stop the monitor. Enter the following SQL statement:
    set serveroutput on
    execute icmlsmon.stopmonitor
    The library server monitor is running on DB2® Stop the monitor.

    Stop the service ICM LS Monitor DBNAME.
    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
    You are using DB2 and DB2 Net Search Extender Enter the following command:
    db2text stop
    You are using DB2 and DB2 Text Search Enter the following command:
    db2ts "STOP FOR TEXT"
    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.
  2. Optional: Recommendation: Create an index on the RMREPLICATION table to improve the fix pack installation and replication performance:
    Database Action
    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:
    Database Action
    DB2 Enter the command:

    CREATE INDEX IDX_OBJ_STATUS ON RMOBJECTS (OBJ_STATUS ASC, OBJ_REFERENCEDDATE ASC, OBJ_STAGEDVOLUMEID ASC);

    RUNSTATS ON TABLE schema name.RMOBJECTS WITH DISTRIBUTION AND DETAILED INDEXES ALL;
    Oracle Enter the command:

    CREATE INDEX IDX_OBJ_STATUS ON RMOBJECTS (OBJ_STATUS ASC, OBJ_REFERENCEDDATE ASC, OBJ_STAGEDVOLUMEID ASC);

    COMPUTE STATISTICS TABLESPACE OBJECTS;
    If your content management system contains many items and parts (that is, there are many rows in these tables), creating 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: 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 then 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.

    Follow the instructions in Enabling debug installation logging on Windows.

  8. If you are using Oracle 12c R1: the EXTPROC_CONNECTION_CM8 entry must be added in tnsnames.ora before installing the fix pack. The EXTPROC_CONNECTION_CM8 entry should look like this: 
    LISTENER_ECM =
    (ADDRESS = (PROTOCOL = TCP)(HOST = myhost.mydomain.com)(PORT = 1522))

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

    Recommendation: For Oracle 12cR1, you can copy the entire EXTPROC_CONNECTION_DATA entry that works in CM 8.6 GA and change the name to EXTPROC_CONNECTION_CM8. After this, the EXTPROC_CONNECTION_DATA entry may be removed if it is no longer needed.

  9. If you are using Oracle: Login as a user with SYSDBA authority to grant the required Content Manager Enterprise Edition database privileges to library server database users, and then run the Content Manager Enterprise Edition schema creation SQL script, icmlsschemas.sql.

    For example:

    sqlplus sys/change_on_install as sysdba
    icmlsschemas.sql icmadmin password icmconct password ICMLFQ32 TEMP

    where:

    icmadmin password
    The name and password for the library server administration database user.
    icmconct password
    The name and password for the library server connection database user.
    ICMLFQ32 TEMP
    The default table spaces for library server database users. You must include these values as shown, even though they are not actually used by the command.

    Alternatively, you can run the script as any database user with the privilege to grant all of the privileges that are in this script.

    The script detects the existence of your library server database users, and does not drop them or recreate them. It does not revoke any privileges, but it does revoke any Oracle default roles.

    Important

    • For Oracle 12c R1, the library server administrative user must have the create database link privilege. Running the icmlsschemas.sql script is a required step for Oracle 12c R1.
    • Do not change icmlsschemas.sql. The script grants only the minimum database privileges required for library server functionality. If you change this script, the library server will fail during configuration and administration.
    • Use the script only on Content Manager Enterprise Edition users.

Before you install the fix pack on AIX or Linux

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

Restriction: After you install IBM Content Manager on AIX or Linux, 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 the target machine:
/opt/IBM/db2cmv8/bin/cmlevel -l
  1. Perform these steps to prepare your AIX or Linux environment for fix pack installation:
    If the following statement is true Perform this step
    The library server monitor is running on Oracle Stop the monitor. Enter the following SQL statement:
    set serveroutput on execute icmlsmon.stopmonitor
    The library server monitor is running on DB2 Stop the monitor.

    For AIX, enter the following command:

    /etc/rc.cmlsproc - shutdown

    For RHEL 7+ and SuSE 12+, enter the following command:

    systemctl stop cmlsmonitor

    For other systems, enter the following command:

    /etc/rc.cmlsproc -shutdown
    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.
    You are using DB2 and DB2 Net Search Extender Enter the following command: 
    db2text stop
    You are using DB2 and DB2 Text Search Enter the following command: 
    db2ts "STOP FOR TEXT"
    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:
    Database Action
    DB2 Enter the command:

    CREATE INDEX IDX_OBJ_STATUS ON RMOBJECTS (OBJ_STATUS ASC, OBJ_REFERENCEDDATE ASC, OBJ_STAGEDVOLUMEID ASC);

    RUNSTATS ON TABLE schema name.RMOBJECTS WITH DISTRIBUTION AND DETAILED INDEXES ALL;
    Oracle Enter the command:

    CREATE INDEX IDX_OBJ_STATUS ON RMOBJECTS (OBJ_STATUS ASC, OBJ_REFERENCEDDATE ASC, OBJ_STAGEDVOLUMEID ASC);

    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.
  3. Recommendation: Create an index on the RMOBJECTS table to improve the background performance:
    Database Action
    DB2 Enter the command:

    CREATE INDEX IDX_OBJ_STATUS ON RMOBJECTS (OBJ_STATUS ASC, OBJ_REFERENCEDDATE ASC, OBJ_STAGEDVOLUMEID ASC);

    RUNSTATS ON TABLE schema name.RMOBJECTS WITH DISTRIBUTION AND DETAILED INDEXES ALL;
    Oracle Enter the command:

    CREATE INDEX IDX_OBJ_STATUS ON RMOBJECTS (OBJ_STATUS ASC, OBJ_REFERENCEDDATE ASC, OBJ_STAGEDVOLUMEID ASC);

    COMPUTE STATISTICS TABLESPACE OBJECTS;
    If your content management system contains many items and parts (that is, there are many rows in these tables), creating 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: 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 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).
  7. Set up for debug logging.

    Follow the instructions in Enabling debug installation logging on AIX or Linux.

  8. If you are using Oracle 12c R1: the EXTPROC_CONNECTION_CM8 entry must be added in tnsnames.ora before installing the fix pack. The EXTPROC_CONNECTION_CM8 entry should look like this: 
    LISTENER_ECM =
    (ADDRESS = (PROTOCOL = TCP)(HOST = myhost.mydomain.com)(PORT = 1522))

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

    Recommendation: For Oracle 12cR1, you can copy the entire EXTPROC_CONNECTION_DATA entry that works in CM 8.6 GA and change the name to EXTPROC_CONNECTION_CM8. After this, the EXTPROC_CONNECTION_DATA entry may be removed if it is no longer needed.

  9. If you are using Oracle: Login as a user with SYSDBA authority to grant the required Content Manager Enterprise Edition database privileges to library server database users, and then run the Content Manager Enterprise Edition schema creation SQL script, icmlsschemas.sql.

    For example:

    sqlplus sys/change_on_install as sysdba
    icmlsschemas.sql icmadmin password icmconct password ICMLFQ32 TEMP

    where:

    icmadmin password
    The name and password for the library server administration database user.
    icmconct password
    The name and password for the library server connection database user.
    ICMLFQ32 TEMP
    The default table spaces for library server database users. You must include these values as shown, even though they are not actually used by the command.

    Alternatively, you can run the script as any database user with the privilege to grant all of the privileges that are in this script.

    The script detects the existence of your library server database users, and does not drop them or recreate them. It does not revoke any privileges, but it does revoke any Oracle default roles.

    Important

    • For Oracle 12c R1, the library server administrative user must have the create database link privilege. Running the icmlsschemas.sql script is a required step for Oracle 12c R1.
    • Do not change icmlsschemas.sql. The script grants only the minimum database privileges required for library server functionality. If you change this script, the library server will fail during configuration and administration.
    • Use the script only on Content Manager Enterprise Edition users.

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. For the component or components that you are updating, gather the information listed in the following table. When the installation wizard runs, it 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:
Product component to update Data required Your values
Library server Library server database name  
Library server schema name (DB2 only)  
Library server JDBC connection string (Oracle only)  
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 (DB2 only)  
Resource manager JDBC connection string (Oracle only)  
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

(Needed only needed if application server security is enabled.)

  
Application server administration password

(Needed only needed if application server security is enabled.)

  
Application server node name

(Needed only if the deployment target is an application server.)

  
Resource manager Web server name

(Needed only if the deployment target is an application server.)

  
Application server cluster name

(Needed only if the deployment target is a cluster.)

  

Installing the fix pack for IBM Content Manager Enterprise Edition

To install the fix pack for IBM Content Manager Enterprise Edition, 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.
    Operating system Command
    AIX and Linux 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.
    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.
    Enter the data that you gathered in Completing the installation worksheet for IBM Content Manager.
  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.

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 V8.6, 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.

After you install the fix pack

Restart the resource manager application server. If the resource manager is deployed in a cluster, restart the cluster.

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, right-click the host from which you will be removing the fix pack, and then 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 V8.6 Fix Pack 1 includes the following additional updates.

  • Data modeling item type improvements:
    • Definition tab options to start item on process and enable records management.
    • the following SQL statement to update the text index
    • New retention tab (does not include custom settings).
    • New logging tab.
    • LDAP configuration is part of registering the plugin to ICN.
  • Support for Oracle container databases (CDB). Learn more
  • Support for Amazon Simple Storage Service (Amazon S3) cloud storage. Cloud storage is useful for long-term storage of objects on devices other than the fixed disks that are attached to the resource manager. Learn more...
  • Performance improvement for IBM Content Navigator multiple item retrieve operation.

Included software updates

IBM Content Manager Version 8.6 Fix Pack 1 includes the following updated software:

  • Snowbound RasterMaster version 14.11.2
  • Apache Axis2 1.7.7

Behavior changes

IBM Content Manager Version 8.6 Fix Pack 1 includes no behavior changes.

Fix list (APARs)

The fix list contains all APARs that are fixed in Version 8.6 Fix Pack 1 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.
Table 2. Fix list for IBM Content Manager Version 8.6 Fix Pack 1
APAR Description
Connectors
IO26006 Get Wrong engine type causes Text Searches (DB2TS) to produce inconsistent results.
Library Server Enterprise Edition
IO26173 ICM5006E error while doing DB2TS text indexing.
IO25035 OIT text extraction is not working for AIX PDF files created by using "Save As" from Microsoft Word 2013.
Resource Manager Enterprise Edition
IO26649 If ENCRYPT_DATA_AT_REST feature is enabled in Content Manager Enterprise Edition, content retrieval will not get the original content if local migration happened to the content.
Resource Manager for z/OS
PH03368 ABEND S0C4 (or U4091) in Content Manager resource manager HTTP module when storing objects greater than 256 MB.
System Administration client
IO26026 Content Manager-supplied cmdatamodel.xsd incorrectly defines ICM$AUTODELETE as XS:DATE instead of XS:DATETIME.
IO24551 Display name of child component name not updated in Item type.
Viewer
IO26193 Cursor does not change to the select text cursor by using the Java Viewer.
IO26314 Find panel is not displayed when thumbnails are docked in the top position.
Web Administration client
IO26464 Cannot display more than 500 group names.
z/OS Install ISPF Panels
PH00990 Content Manager V8.6 ISPF job config has no option to upgrade from 8.4.3 to 8.6.0.

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.