Customers using DB2 Content Manager Enterprise Edition V8.4.0 on a platform other than z/OS for indexing of content that had been migrated to Tivoli Storage Manager under certain conditions might not have a complete and accurate index

Flash (Alert)


Abstract

When an application running on DB2 Content Manager Enterprise Edition Version 8.4.0 on a platform other than z/OS is attempting to retrieve content (for example, emails, documents, jpegs, etc.) that has been migrated to Tivoli Storage Manager (TSM), only an empty file will be retrieved if the TSM media is not available at the time retrieval is attempted. No error message is presented.

When this problem has occurred, DB2 Content Manager will:
- Retrieve 0 byte content (a zero length file), rather than getting an error message.
- Display a blank page when attempting to view the content, symptomatic of an error.
- Complete the content retrieval for text indexing or re-indexing without any indication of content retrieving error, but only empty content will be indexed. As a result, queries of the index using text search functions will not find such content.

To avoid this problem in the future, we recommend that you upgrade to DB2 Content Manager Enterprise Edition Version 8.4.1 as soon as possible.

Notes:
- There is no issue with the TSM software.
- There is no data loss because the content remains on TSM.
- This issue does not exist with DB2 Content Manager versions 8.3, 8.4 on z/OS or version, or 8.4.1.

Content

When an application running on DB2 Content Manager Enterprise Edition Version 8.4.0 on a platform other than z/OS is attempting to retrieve content that are stored on media devices managed by Tivoli Storage Manager (TSM) and the TSM media is not available during the retrieval attempt, the content is not retrievable and no error message is returned to the client application. Instead, a zero length file might be returned to the client and will be written to the disk cache. No error is returned to the client application. Until such content is purged from the cache, subsequent content retrievals will continue to use the disk cache copy (zero length file) and no error is returned to the client application.


When the content is retrieved for text indexing, the operation completes without any indication of content retrieving error, but only empty content will be indexed.

To avoid experiencing this problem in the future, we recommend that you upgrade to DB2 Content Manager Enterprise Edition Version 8.4.1 as soon as possible.

Implications:

  • When attempting to view the content, a blank page will be displayed, symptomatic of an error.
  • The text index operation will complete without any indication of content error, but only empty content will be indexed. As a result, subsequent queries of the index using text search functions will not find the content.

Determining if you are impacted:
To find out if you are currently using DB2 Content Manager Enterprise Edition Version 8.4.0, go to the DB2 Content Manager installation "bin" directory and run the cmlevel command. If DB2 Content Manager Enterprise Edition Version 8.4.0 is installed, the response to the cmlevel command will include reference to 8.4.00.000 or higher (for example: .000 to .999).

For you to have experienced this problem, ALL of the following conditions must have occurred:
  • You used DB2 Content Manager Enterprise Edition V8.4.0; AND
  • Using DB2 Content Manager Enterprise Edition V8.4.0, you had migrated content to Tivoli Storage Manager and then attempted to retrieve/index the content; AND
  • The TSM media was not available at the time the retrieval or indexing was attempted.

You will also experience this problem if:
  • You subsequently used DB2 Content Manager Enterprise Edition V8.4.0 to retrieve or index a cached copy of content that had previously been stored on media managed by the Tivoli Storage Manager product (TSM); AND
  • The TSM media was not available when the content was retrieved from TSM.

You will not experience this problem if
  • You use or have used both (i) DB2 Content Manager Enterprise Edition V8.4.0 on a platform other than z/OS and (ii) Tivoli Storage Manager; AND
  • You have never retrieved, indexed or re-indexed any content after it has been migrated from disk to Tivoli Storage Manager.

Solution:
All impacted customers should upgrade to DB2 Content Manager Enterprise Edition V8.4.1 as soon as possible, and then re-index content that was previously indexed using DB2 Content Manager Enterprise Edition V8.4.0.

If you have already upgraded to DB2 Content Manager Enterprise Edition V8.4.1, you will still need to re-index content that was indexed using DB2 Content Manager Enterprise Edition V8.4.0.

If you might have been impacted and need additional detailed information to determine if you are affected, or you have questions or concerns about how to proceed, contact IBM Content Management Support for further assistance.

Additional information for impacted CommonStore or Content Collector customers who use fast indexer to index documents:

After the upgrade to DB2 Content Manager Enterprise EditionV8.4.1 and before indexing any new content, you should re-index the content of all item types archived after you installed or upgraded to DB2 Content Manager V8.4.0 and before your upgrade to Version 8.4.1.
  1. You need to collect the following information:
    • Your DB2 Content Manager V8.4.0 installation or upgrade date
    • The DB2 Content Manager index log table names of your item types
    • The DB2 Content Manager index backup table names of your item types
  2. Mark documents of one item type archived after the date you upgraded or installed DB2 Content Manager Enterprise Edition V8.4.0 to be re-indexed using the following query:

    db2 "insert into <CM_index_log_table> (select * from <CM_index_backup_table> where time > timestamp ('<YYYY-MM-DD>-00.00.00.000000'))"

    in which:
    • <CM_index_log_table> is your DB2 Content Manager index log table name of the chosen item type
    • <CM_index_backup_table> is your DB2 Content Manager index backup table name of the chosen item type
    • <YYYY-MM-DD> is the date you upgraded or installed DB2 Content Manager Version 8.4.0

  3. Run indexing for the documents of the item type mentioned in step 2 by running the fast indexer’s indexdocuments command (indexdocuments.bat or indexdocuments.sh).

  4. Repeat step 2 and 3 until all of the item types are processed.

If you continue to index content before you upgrade to DB2 Content Manager Enterprise Edition V8.4.1, make sure that you index only before the content is migrated to TSM.

Cross reference information
Segment Product Component Platform Version Edition
Enterprise Content Management Content Collector Windows 2003 server, Windows 2008 2.1
Enterprise Content Management CommonStore for Exchange Server TextSearch Windows 2000 Server, Windows Server 2003 8.3, 8.4
Enterprise Content Management CommonStore for Lotus Domino TextSearch AIX, Windows 2000 Server, Windows Server 2003 8.3, 8.4
Enterprise Content Management eDiscovery Manager AIX, Windows 2003 server, Windows 2008 2.1, 2.1.0.1, 2.1.1.0

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Content Manager

Software version:

8.4, 8.4.0.1

Operating system(s):

AIX, Solaris, Windows 2003, Windows 2008

Reference #:

1390831

Modified date:

2013-01-15

Translate my page

Machine Translation

Content navigation