Readme file for: IBM® FileNet® Image Services
Update name: 4.2.0.13
Fix ID: 4.2.0.13-IS-FP013
Publication date: 29 April 2016
Last modified date: 29 April 2016
The IBM FileNet Image Services (IS) 4.2.0.13-IS-FP013 fix pack updates an existing Image Services 4.2.0 system. Image Services fix packs are cumulative and include content from all previously released fix packs since the base release. Image Services fix packs are released periodically and include the binary executable installation program, the manifest file, and the readme.
Important As of April 2012, IBM AIX 5L Version 5.3 entered end of service (EOS). Going forward, Image Services fix packs will no longer be tested with AIX 5.3. However, the Image Services support team continues to accept problem reports for AIX 5.3 based configurations. If a problem is suspected to be AIX-dependent, you might be required to recreate the problem on a supported version of AIX.
Important As of 31 December 2011, FileNet-controlled Oracle is no longer supported. See the announcement regarding this change here: Software withdrawal: IBM FileNet Image Services with Oracle Runtime Authorized User Value Unit Renewal.
To determine the current fix pack version installed on your server, enter the following command:
fn_util whichfn
Click the following link to access the files for this fix pack update: Fix Central for Fix Pack 4.2.0.13-IS-FP013.
Or from the main Fix Central website, make the following menu selections:
| From this menu... | Make this selection... |
|---|---|
| Product Group: | Enterprise Content management |
| Enterprise Content Management: | FileNet Product Family |
| FileNet Product Family: | FileNet Image Services |
| Installed Version: | 4.2.0 |
You need an IBM login and password to access this download location.
For details about the resolved defects in this fix pack, see the section Fix list (APARs).
For more information about Image Services new features and known issues, see the IBM FileNet Image Services Release Notes.
For more Image Services 4.2.0 compatibility information, see the IBM FileNet Image Services, Image Services Resource Adapter, and Print Hardware and Software Requirements document.
In the past, when SCavenge found an overlap condition in cache it would report the error and immediately stop processing. An overlap condition occurs when the csm_used_space and cms_free_space tables contain the same cache address. The FileNet Image Services software could not be restarted until the overlap issue was resolved by initializing the transient database. In this release, the SCavenge option in CSM_tool has been enhanced to continue processing and report the all of cache addresses with an overlap condition. The bad cache addresses are displayed on the screen and written in the FileNet Image Services error log.
For details on both CSM_tool options, see technote 1633859, Image Services: Improvements to the SCavenge option in CSM_tool on the IBM support site.
UNIX
Process record PID %d does not match the real PID %d\n
This is most likely due to a fork without exec.\n
Windows
Process record PID %d does not match the real PID %d\n
The thread may not have initialized properly.
The message can identify an Image Services process that is not working properly.
Currently only SDS Unit IDs from 2 through 99 can be used with the clip_ids option in DOC_tool to create a file list containing the document ID and clip ID. The file list can be used by sds_import to recover Integral SDS documents.
When a System Administrator runs the sds_convert_nls command, by default it moves the Near Line Storage (NLS) user-defined indexes, FNP_ARCHIVE and FNP_CLIPID from the doctaba table in the index database to the docs table in the MKF permanent database. It also assigns the SDS Unit number 1 to the documents. The System Administrator is no longer able to access the doctaba table to collect the NLS data.
This enhancement gives the System Administrator the capability of creating file list of the document ID and clip ID of NLS documents that can be used by the SDS_tool command to recover documents in the case of a disaster recovery situation.
UNIX
/fnsw/local/trigger/kill_delay
/fnsw/local/sd/ims_stop
Windows
drive:\fnsw_loc\sd\ims_stop.bat
These trigger files are useful when you run the Integral SDS sds_copy or the sds_migr command with the -writelist option, which creates a list of document IDs that are processed. If Image Services stops too quickly while the background job is running, the list might not be complete.
For complete information on creating and using these trigger files, see the technote titled "Image Services: Integral SDS writelist is not correct if the Image Services software is recycled while the background job is running" # 1609954 on the IBM support site for details.
This section contains the following topics:
Tip Installation of this fix pack is not affected by any virus protection software that might be running in the background.
Before installing this fix pack, verify that you have a copy of the latest IBM FileNet Image Services documentation. The Image Services documentation packages contain additional information that you might need to perform the procedures mentioned in this readme, such as stopping services and applications.
This fix pack has the following minimum requirements:
Important: Windows 2008 R2 Service Pack 1 (SP1) or later is required for Windows 2008 R2 systems that use Integral Single Document Storage (SDS) with Centera SDS devices. On Windows 2008 R2 systems, EMC Centera requires SDK 3.3, which is included in Image Services 4.2.0 FP5 and later.
|
Operating system
|
Recommended minimum disk space
|
Temporary directory used by the installation program
|
|---|---|---|
|
AIX
|
300 MB
|
/tmp
|
|
HP-UX
(HP Integrity) |
500 MB
|
/var/tmp
|
|
Solaris
|
300 MB
|
/var/tmp
|
|
Windows
|
340 MB
|
temp (determined by installer)
On Windows servers, the installation program determines the temporary file path as follows:
Tip The installation program does not run any checks to verify that a specified directory exists. |
If you plan to run the installation program in another mode (silent, console, or graphical), and you have determined earlier that the /var/tmp directory does not have enough free space, set the IATEMPDIR environment variable to an alternate directory. The alternate temporary directory must be outside the /fnsw directory structure. For example, you might enter:
IATEMPDIR=/othertemp
export IATEMPDIR
export IATEMPDIR=/othertemp
setenv IATEMPDIR=/othertemp
The Image Services fix pack installation program automatically copies the existing modules affected by this fix pack to a backup directory before overwriting them with the updated modules. You can find out which modules were backed up and their new location in the configFiles.log file at:
/fnsw/local/logs/hfp/4.2.0/HFP11/misc/configFiles.log
Following is an example of what you might see in the configFiles.log:
The following configuration modules have been
replaced by the fix pack installation.
The original files were backed up to:
/fnsw/hfp/backup/fnsw/lib/perf/reports
Restriction If the fix pack updates any configuration files, they will have only the default settings. Therefore, a system administrator will have to transfer customized settings from the backed up configuration files to the newly installed files at the end of the installation procedure. For instructions, see steps 11 and 12 in the installation procedure.
Several log files are created during the fix pack installation. You can check these log files to determine the status of a fix pack installation. If the installation failed, these log files can help you determine the cause of the problem.
UNIX
Use the more or less commands to view the log files on UNIX servers, which are stored in the following directories:
/fnsw/local/logs/hfp/4.2.0/HFP12/
/fnsw/local/logs/hfp/4.2.0/HFP12/misc/
Windows
Use WordPad in landscape mode to view the log files on Windows servers, which are stored in the following directories:
IS_local_directory \logs\hfp\4.2.0\HFP12
IS_local_directory \logs\hfp\4.2.0\HFP12\misc
The .../4.2.0/HFP13/ directory contains the IS_420-HFP13.log file. This log file lists all the Image Services modules that were replaced. Each time you run the installer, new information is appended to the end of the file.
This log file also records all the processing steps taken during the fix pack installation, and indicates if they were successful or unsuccessful. The last line indicates the status of the installation:
SUCCESS - All files were copied successfully, and no errors were detected
WARNING - All files were copied successfully, but some errors were detected
ERROR - One or more files were not copied, and some errors were detected
You can determine the number of files that were copied by the following line located near the end of the log file. The actual number of files copied varies from one fix pack to another. However, the total number of files copied must equal the total number of files provided with this fix pack. For example:
200 files of 200 have been copied to the target
If the number of files do not match, verify that all Image Services-related applications are stopped, and run the fix pack again.
The .../4.2.0/HFP13/ directory contains log files generated by the Install Anywhere (IA) program.
These files contain error messages and warnings that can help you troubleshoot an unsuccessful installation. However, when you run the installation program again, these files will be overwritten if any further messages are generated. If you want to save the current files, rename them before you rerun the installation program.
Harmless messages: If the logs contain any warnings about Swing or AWT initialization, you can ignore them. You can also ignore these messages:
Unable to compare stamp versions...
Unable to read Host name: Null pointer exception
The .../4.2.0/HFP13/misc/ directory has several logs that can be used for troubleshooting and debugging:
This directory also contains a record of the file "stamp" information before and after the installation.
Silent installation does not display any messages to the user whereas graphical installation does. To determine if silent installation is running, refer to the primary error log found in the /fnsw/local/logs/hfp/4.2.0/HFP13/ directory (the \fnsw_loc\logs\hfp\4.2.0\HFP13\ directory on Windows servers). On UNIX servers, enter the following command to dynamically display the installation log as it is created:
tail -f IS_4.2.0-HFP13.log
Before using silent installation mode, verify the amount of free space in the default temporary directory as described in the Temporary Disk Space Requirements table. The amount of free disk space must be verified either manually or through an automated script. Lack of sufficient disk space prevents the installer from starting successfully.
As a user with root privileges, change to the directory where the FileNet Image Services installation program is located and start the installation program.
Tip: If you are installing from CD-ROM, do not change to the /cdrom directory to run the program. Run the installation program from the / (root) file system.
./is_4.2.0-FP13_ operating system.bin &
Tip: The trailing "&" character detaches the installation program from the console window so that it can run in a separate window. Use the console window to correct any configuration errors reported by the installation program.
./is_4.2.0-FP3_ operating system.bin -i console
./is_4.2.0-FP3_ operating system.bin -i silent -f /tmp/opt.txt
Important: /tmp/opt.txt is the location of the text file you modified in an earlier step. Specify its full path on the command line. For example, ... -i silent -f /fnsw/local/tmp/opt.txt.
If you run the system checks in silent mode, check the log file in /fnsw/local/logs/hfp/4.2.0/HFP12/ to determine the results. The name of the log file is IS_4.2.0-HFP13.log.
As a user with administrative privileges, change to the directory where the FileNet Image Services installation program is located and start the installation program.
\is_4.2.0-FP13_win.exe
\is_4.2.0-FP13_win.exe -i silent -f c:\tmp\opt.txt
Important: c:\tmp\opt.txt is the location of the text file you modified earlier.
Specify its full path on the command line. For example, ... -i silent -f c:\fnsw_loc\tmp\opt.txt
The DISPLAY environment variable controls whether or not the "Welcome" screen displays on UNIX systems in graphical mode. If you use the su command to log on as the root user, the DISPLAY environment variable might not be correct. Check the DISPLAY environment variable by entering:
echo $DISPLAY
The environment variable should be set to 0:0 to display on a local monitor. If you are installing the fix pack remotely to another server, the variable on that server must be set to direct the display to the server you are working on.
To install this fix pack on Windows servers in a cluster environment, you must perform the installation task with other required tasks as outlined below:
Some Image Services systems include Tivoli Monitoring. Tivoli Monitoring is a software tool that collects availability and performance data of enterprise systems from one or more central workstations.
It is necessary to stop Tivoli Monitoring before you install Image Services or the Image Services Toolkit. Image Services and Image Services Toolkit installation software uses commands that stop Tivoli Monitoring. In some cases, Tivoli Monitoring might not stop and an error message is displayed. If Tivoli Monitoring does not stop, you need to manually stop it before the Image Services or the Image Services Toolkit installation can be completed.
To manually stop the Tivoli Monitoring User Interface:
Important Windows installations: There is a potential problem with WinZip version 8.0. Use WinZip version 9.0 or higher to avoid this problem.
In dual-server and multi-server configurations, install the fix pack on the root server first, and then on the other servers.
UNIX
Log on as a user with root privileges.
Windows
Log on with Administrator privileges.
UNIX
On all UNIX servers:
initfnsw -y stop
killfnsw -DAy
ps -elf | grep fnsw
kill -9 processID
ps -elf | grep vl
kill -9 processID
ps -elf | grep MasterSnmpd
kill -9 processID
wal_purge
Restriction Do not run any other Image Services commands before you install the fix pack.
Windows
On all Windows servers:
initfnsw -y stop
killfnsw -Dy
Important
net stop "SNMP"
Tip: Windows automatically clears the ISTK shared memory.
Important
UNIX - If any files are in the /fnsw/procs directory, delete them and rerun the installation program.
Windows - If any files are in the \fnsw\procs directory, delete them and rerun the installation program. Use the Windows Task Manager to check for and terminate any processes that were stopped abnormally.
UNIX
chmod +x is_4.2.0-FP13_operating_system.bin
Graphical mode
./is_4.2.0-FP13_operating_system.bin
Console mode
./is_4.2.0-FP13_operating_system.bin -i console
Silent mode
./is_4.2.0-FP13_operating_system.bin -i silent -f /tmp/opt.txt
Windows
Graphical mode
Silent mode
drive :\is_4.2.0-FP13_win.exe -i silent -f drive:\tmp\opt.txt
UNIX
cd /fnsw/etc
stamp serverConfig
Windows
Use Windows Explorer to check the date stamp on the serverConfig file.
cd /fnsw/local/sd/1
rm perflog
Important If any FAIL status is encountered in the install log file, review the log file, correct the reported problem and retry the operation.
If you plan on upgrading to a later version of RDBMS during this fix pack installation, complete the upgrade, and then run the following command at a command prompt:
fn_setup_rdb -u
After running the fn_setup_rdb command, close the command window and open a new command window to ensure that the new RDBMS home is in the PATH environment variable. You must also verify that, if the RDBMS is Oracle, the ORACLE_HOME is set to the new ORACLE_HOME.
After the fix pack is successfully installed on all Image Services servers in the Image Services domain, you can resume normal processing.
If Image Services has MSAR surfaces that were converted from a 14x magneto-optical 9.1 GB drives, use the following procedure to ensure the integrity of your MSAR data. In rare instances, the 9.1 GB drive returns incorrect data from large block read commands. The st_msar_convert tool requests large blocks of data, and so st_msar_convert might have written incomplete data onto the MSAR surface during the conversion. After you install the latest firmware on the optical drive, use the Image Services MSAR_surf_fixup_14x tool to scan and fix your MSAR surfaces. If Image Services does not have MSAR surfaces that were converted from a 14x magneto-optical 9.1 GB drives, you can skip this section.
The MSAR_surf_fixup_14x tool provides all the information necessary to find and fix any MSAR problems caused by the 14x firmware. The MSAR_surf_fixup_14x tool searches the entire server for MSAR surfaces that were converted from 9.1 GB optical drives, and if the original optical disk is inserted in the storage library, it will verify whether the converted MSAR surface is correct or not. If you specify the fix flag (-f), the tool can fix an incomplete MSAR surface by copying the correct data from the original optical media. The command uses the following syntax:
MSAR_surf_fixup_14x [-f] [-s surface_id]
-f - causes the fix to run if the original optical surfaces are available.
-s surface_id - runs the scan, report, and fixup, if indicated (-f), on the single MSAR converted surface indicated.
Notes
Contact the hardware vendor to obtain the HP 14x Magneto-Optical drive firmware version 1.19 or higher. Install the new firmware according to the manufacturer's instructions.
Contact the hardware vendor to obtain the Sony 14x Magneto-Optical drive firmware version 1.13 or higher. Install the new firmware according to the manufacturer's instructions.
After the firmware on the optical drives is updated, locate all the original 9.1 GB optical disks that were converted to MSAR.
UNIX /fnsw/local/logs/msar_check/
Windows \fnsw_loc\logs\msar_check\
A typical log file might look like this: MSAR_SURF_FIXUP_14X Report for 9.1G converted surfaces
MSAR_SURF_FIXUP_14X Report for 9.1G converted surfaces Host Server Name: cassini Creation Date & Time: 04/29/2013 15:43:06 MSAR MSAR MSAR Optical Optical Orig Orig Surface Problem Surface Surface Surface Surface Optical Optical ID Exists Avail Type ID Avail SSN surface id ========== =========== ======= ======= ========= ======= ======= ========== 3002 Y Y Conv 3001 Y 20119 20827 Document id: 100040, ssn 20119 loc_id 1528574237 surf_ids 1002 and 0. Bad sector range 1087730 to 1093255. Bad sector count: 5526. Fixed: No 3004 Not scanned N Non 9.1 XXXX X XXXX XXXX 3006 Not scanned Y Non 9.1 XXXX X XXXX XXXX 3008 N Y Conv 3001 Y 20119 20827 1 bad converted surfaces found out of 2 9.1G converted surfaces. 2 non-9.1G converted surfaces found. End of Job Date & Time: 04/29/2013 15:45:41 Report name: C:\FNSW_LOC\logs\msar_check\sc_20130429_154121.log |
Windows only The allocation of shared memory used by Image Services can conflict with other software that is integrated into Image Services (such as Windows .dll files). Image Services is designed to automatically reorganize its memory usage to handle these conflicts, but in order to accomplish this adjustment, you might need to restart Image Services more than once. Conversely, after you install or upgrade another product that is installed on the same server as Image Services, the address spaces allocated by those other products might conflict with the address space that is allocated to the SysV shared memory for Image Services processes.
For more information on shared memory configuration, see technote 1506926, Image Services Shared Memory Configuration, on the IBM support site.
Only the most recently installed fix pack can be uninstalled. If you need to return an even earlier version, you will have to restore Image Services from your backups.
Important The files in the /fnsw/hfp/backup directory are the modules that will be restored. If these files have been modified or deleted, the uninstall operation will not succeed.
UNIX
Important Use only this command to uninstall the fix pack. Using the operating system tools might delete vital data that is needed for future fix pack installations.
/fnsw/hfp/_uninst/uninstall_hfp.bin
Windows
The following tables list the product fixes in this fix pack.
APAR Name |
Type |
Description |
|---|---|---|
PJ43751 |
Fix |
SDS_worker reports fatal error. 74,23,102 – Invalid class number passed to QMA. |
PJ43874 |
Fix |
Page 0 of a document contains invalid security data. |
PJ43876 |
Fix |
The current write surface is ejected when a 94,0,10 error is logged. |
PJ43900 |
Fix |
Improve TM_daemon logging when recv() returns a zero status. |
PJ43967 |
Fix |
IS Connector: The Image Services Connector for ICN reports 92,0,99 errors when there are idle sessions. |
PJ43992 |
Fix |
The SDS_CSAR reader reports a <0,0,1> error with UNKNOWN SEVERITY. |
PJ44033 |
Fix |
The SDS_CSAR_reader process can abort when receiving a long error message from Centera due to a buffer overrun. |
PJ43710 |
Enh |
ER: Provide Integral SDS performance statistics based on configurable threshold settings. |
PJ43726 |
Enh |
ER: Replace OpenProcess() in the ISTK SysV routine fnl_is_dead() with OpenEvent() to check whether an ISTK process is still alive. |
PJ43723 |
Enh |
ER: Create a new circular buffertrace log that avoids the current circular buffer log limitations. |
PJ43725 |
Enh |
ER: Expand existing TM_daemon debug logging to include detailed information on network initialization calls. |
PJ43821 |
Enh |
ER: Change doccopy to take advantage of the MSAR synchronization read feature. |
PJ43991 |
Enh |
ER: Write a message to the error log when the Image Services is started if the NO_MIGRATE_FB environmental variable is set./td> |
PJ43990 |
Enh |
ER: Change Image Services to detect and prevent duplicate BiDi documents coming from Content Engine. |
PJ44148 |
Enh |
ER: Image Services Connector 1.4.0.1 for IBM Content Navigator. |
APAR Name |
Type |
Description |
|---|---|---|
PJ43708 |
Fix |
Windows 2012: Help option returns “You're not connected to online Help", when the latest help content is available. |
PJ43498 |
Fix |
Add Oracle 12.1.0 to fn_edit for Oracle 12c support. |
PJ43501 |
Fix |
80,0,12 error when Capture commits batch specifying Alternative Page Cache point to page_cache1. |
PJ43512 |
Fix |
Checking for size mismatch. Fast Batch Committal was interfering with Integral SDS retry. |
PJ43513 |
Fix |
Performance counter close_write has a problem when running with FBC. The close_write elapse times are off. |
PJ43564 |
Fix |
The 911 output file does not contain the DOC_tool SDS report on the Windows hardware platform. |
PJ43589 |
Fix |
BESs logs an 88,0,52 error – BESl: 'batch_open_id' wrap around in 'batch_ctl' record – not recoverable. |
PJ43607 |
Fix |
The SDS_worker process does not update the checksum (csum) field in the csm_used_space table when a document is retrieved. |
PJ43659 |
Fix |
80,2,2 – Orphaned “Write Request” records get created in FileNet Image Services. |
PJ43692 |
Fix |
A process can abort when an attempt is made to send a message to a message queue and the process has a high waitcount. |
PJ43714 |
Fix |
Integral SDS – Add retry logic to enable an SDS device again when it becomes disabled for writes. |
PJ43652 |
Fix |
The ce_os_id is set on the remote system for documents remotely committed when using BiDi. |
PJ43803 |
Fix |
The stdoccpy program reports a bogus error - Can't specify -ignore (unavailable surfaces) option without -docidfile. |
PJ43601 |
Enh |
ER: Add option to INX_tool to replicate index data to a remote peer system. |
PJ43709 |
Enh |
ER: Image Services Connector 1.4.0 for IBM Content Navigator. |
APAR Name |
Type |
Description |
|---|---|---|
PJ42555 |
Fix |
Running multiple killfnsw commands during shutdown can hang the software on a semaphore. |
PJ42601 |
Fix |
CSM_tool aborts holds an SEC interlock after a 156,0,25 error - nch_GetCourierService: cannot find service cor / protocol tcp combination. |
PJ42726 |
Fix |
Change misleading error message – 121,0,3 – Missing table 'doctaba'. |
PJ42795 |
Fix |
FNPoll does not build the /dev/fnsod entries correctly on the AIX hardware platform, causing the optical library not to be available. |
PJ42819 |
Fix |
The docimp program fails, reporting a 30,0,35 error – Can't write checkpoint file. |
PJ42822 |
Fix |
Add the folder C:\fnsw_loc\logs\CFSIS to fn_perm and /fnsw/local/logsl/CFSIS to permission table. |
PJ42962 |
Fix |
DOC_tool SDS statistics report provides incorrect information on ISDS reads when sds_read_after_write is enabled. |
PJ42968 |
Fix |
Enabling MSAR synchronous to cache feature results in DOCs process consuming too many file handles. |
PJ43009 |
Fix |
Integral SDS retry/connection does not recover, causing the SDS device to be disabled. |
PJ43083 |
Fix |
When the MSAR_SYNC_THRESHOLD trigger file is set and an MSAR surface is moved,.nfs files are created until the Image Services software is restarted. |
PJ43216 |
Fix |
The stdoccpy process may hang in phase one when the doc_id_list contains more than 50 surfaces. |
PJ43409 |
Fix |
INXD timeout not working correctly - 90,0,112 - INXD_lock: timeout could not get dictionary lock for update. |
PJ43409 |
Fix |
When a writer times out attempting to claim a lock, SysV claimt() fails to wake up any readers in the claim share queue for the lock. |
PJ43247 |
Enh |
ER: Perform additional retries within Integral SDS when SnapLock repository operations fail. |
PJ43130 |
Enh |
ER: Improve CFS annot_log SEC map error handling. |
PJ42766 |
Enh |
ER: Modify document allocation id to check the range of ids returned is free of existing documents in the MKF docs table. |
PJ43131 |
Enh |
ER: Add additional logging when courier disconnects under certain error conditions. |
PJ42936 |
Enh |
ER: Improve error log messages to point to the server when the dtp process reports MKF database full errors (161,1,1075). |
PJ43502 |
Enh |
ER: Image Services to support SQL 2014 database. |
PJ43156 |
Enh |
ER: Add operating system error number and string when getaddrinfo errors occur. |
PJ43222 |
Enh |
ER: Alter the signal handler to create only one stack trace file per process. |
PJ43245 |
Enh |
ER: Add the capability to configure SDS_worker processes to be dedicated readers. |
PJ43246 |
Enh |
ER: Allow the ECM SDK FP_OPTION_BUFFERSIZE and FP_OPTION_TIMEOUT environmental variables to be set by the System Administrator. |
PJ43248 |
Enh |
ER: Enable doccopy to skip documents that return 132,0,12 - No compatible storage library. |
PJ43294 |
Enh |
ER: Add a new option to the DOC_tool SDS command to list the status of Integral SDS devices. |
PJ43295 |
Enh |
ER: Separate the wait queue statistics in the DOC_tool SDS report based on worker type. |
PJ43408 |
Enh |
ER: Image Services Connector 1.3.0 for IBM Content Navigator. |
APAR Name |
Type |
Description |
|---|---|---|
PJ42493 |
Fix |
The fnlogon program logs the following error – fnfork nchl_CheckString: Null argument. |
PJ42649 |
Fix |
Cannot exit SEC_tool when the tool is called by a script or the input is a redirect from a text file. |
PJ42356 |
Enh |
ER: 911 enhancements. |
PJ42554 |
Enh |
ER: Unable to view user logons in Security Administration when more than 4,000 users are logged in. |
PJ42710 |
Enh |
ER: Release the traceit.sh tool that gathers stack traces on UNIX servers. |
PJ42703 |
Enh |
ER: Image Services Connector & Plugin for IBM Content Navigator (Add Annotation Support + Multi-content elements). |
| APAR Name | Type | Description |
|---|---|---|
PJ42223 |
Enh |
ER: Support for Oracle 12c. |
PJ42492 |
Fix |
Fast batch breakup can free more CSM used space than it should when breakup is interrupted by a system recycle, as the batch is reprocessed after start up or when the fast batch breakup document already resides in cache. |
PJ41656 |
Fix |
Windows: DOC_tool is not able to obtain retention settings for documents migrated to HCAP. |
PJ42507 |
Fix |
The SQIs process crashes if FIPS is configured causing the software to hang. |
PJ41938 |
Fix |
The docfetch utility takes a long time to complete when using the -s option. |
PJ42067 |
Fix |
Shared memory leak in INX logon when retrieving NLS documents that were only archived to an SDS device. |
PJ42127 |
Fix |
Image Services processes may abort in the COR library if ELA tracing is enabled. |
PJ42141 |
Fix |
Detect if fast batch object page 0 size does not match size in the FB table of contents when written to SDS. |
PJ42103 |
Fix |
Windows: gethostname failed messages reported in the error log. |
PJ42111 |
Fix |
fnc_create_handle: Error 2 opening file mapping. Map file name is: Global\FNSHM_464a0001. |
PJ42250 |
Fix |
Long MKF transaction times can occur when running sds_copy or sds_migr resulting in performance issues. |
PJ42254 |
Fix |
SDS_worker processes do not release UDP ephemeral ports, resulting in TPI_OpenPEPStr2 bind failed errors. |
PJ42258 |
Fix |
INXs process aborts – 90,5,1 – Activity Log count should never be greater than 1 per process. |
PJ42290 |
Fix |
SEC_init -o aborts when Image Services is started – 161,0,1076 error – MKF_end_transcation: process not in transaction. |
PJ42363 |
Fix |
Online EBR backup fails with 202,100,10 BRTs FATAL MKF ERROR ready the rl partition.. |
PJ42441 |
Fix |
CSM_exim -e -c page_cache1 -o aborts with Bad page number 3237224, should be in 1 to 1000 on Windows platform. |
PJ42484 |
Fix |
Database queries can return duplicate folders. |
PJ42148 |
Enh |
ER: Change the courier recv time out error log entry. |
PJ42126 |
Enh |
ER: Add Windows dump file creation to SysV. |
PJ42259 |
Enh |
ER: Add optional trigger file to log the document id sent back to the client when a request is made. |
PJ42370 |
Enh |
ER: Add optional trigger to prevent creation of Index record unless the document is committed. |
PJ42362 |
Enh |
ER: Enhancement to validate cache consistency – csm_free_space with csm_used_space. |
PJ42512 |
Enh |
ER: Release Image Services connector for IBM Content Navigator (Query, Retrieval & Committal). |
PJ42510 |
Enh |
ER: Enhance 4.2.0 Image Services installer for the Image Services connector for IBM Content Navigator WAR file. |
| APAR Name | Type | Description |
|---|---|---|
PJ42227 |
Fix |
MKF FATAL ERROR (161,0,1076) occurs when adding an annotation causing a DOCs process to abort. |
PJ41186 |
Fix |
Windows: IPC_daemon process not able to connect to all shared memory segments when starting Image Services. |
PJ41295 |
Fix |
Windows: Error 5 is reported when opening a process that is owned by another user. |
PJ41305 |
Fix |
Windows: Image Services Toolkit (ISTK) logs a "Global/ADC0ADC0 CreateFileMapping FAILED err=5" message. |
PJ41354 |
Fix |
SysV: The highest shared memory segment (#128) is now in use. |
PJ41399 |
Fix |
A "155,2,3 COR_Listen – getinterlock(rpclock) failed" is reported in the Image Services error log. |
PJ41416 |
Fix |
The timeoutmonitor causes EBR performance issues. |
PJ41417 |
Fix |
After applying Image Services 4.2.0 FP5 (or higher), the LOGIC field in the AIX Performance reports is always set to zero. |
PJ41437 |
Fix |
Windows: Checksum errors 77, 1, and 58 are reported when retrieving Integral SDS documents in an SDS only environment. |
PJ41449 |
Fix |
The sds_copy logs a 202,100,10 error when the MSAR optical surfaces are not available and copying NLS documents. |
PJ41575 |
Fix |
Error message missing document id – sds fbc: write_sds_object: internal error. |
PJ41585 |
Fix |
Windows: 202,0,2005 check_seg_addrs: CreateFileMapping 'Global\CHK_SHM_2436_7700' err=5. |
N/A |
Fix |
Solaris 11: sds_migr fails and sds_copy only works with sds-only source documents. |
N/A |
Fix |
Getstamps outputs two unnecessary WARNING messages. These messages are recorded in the Fix Pack install logs. |
N/A |
Fix |
Solaris 11: Unable to locate enough shared memory addresses on startup. |
N/A |
Fix |
Solaris 11: fnsod.install needs to handle Solaris 11. |
N/A |
Enh |
ER: Request to add isinfo to the beginning of 911. |
N/A |
Enh |
ER: Image Services 4.2.0 needs to support FIPS SHA-256. |
N/A |
Enh |
ER: Add warning message when the software starts if the shared segment size is not 256 MB on the AIX hardware platform. |
N/A |
Enh |
ER: The Image Services GA and Image Services Fix Pack installers must use InstallAnywhere 2012 to support newer Windows platforms. |
N/A |
Enh |
ER: Release the isinfo and wal_info modules to assist in troubleshooting SysV issues. |
N/A |
Enh |
Update the error message file to include the message text for the <92,0,175> errors. |
N/A |
Enh |
Rebuild the message catalog files released in the following SCR: 44038. |
N/A |
Enh |
Clarify the Fix Pack installer log message by stating the Fix Pack number at the end of the pre-installation change. |
| APAR Name | Type | Description |
|---|---|---|
PJ40933 |
Fix |
Add additional safeguards and sys_log messages to the CSM_tool SCavenge option. |
PJ40953 |
Fix |
Invalid tiff images are created when a 61,0,10 error is reported. Incorrect document information written to Single Document Storate (SDS) device. |
PJ40982 |
Fix |
Provide conditional support for EMC Centera SDK 3.3 for Windows 2008 R2. Note: EMC Centera SDK 3.2 is fully supported. For details, see technote 1633676, Image Services: Windows 2008 R2: SDS workers abort after applying latest Fix Pack on the IBM support site. |
PJ41046 |
Fix |
SECs deadlocks occur when SEC interlocks are not released. |
PJ41113 |
Fix |
TM_daemon reports a 202,4,17 error - FNL_lock: Process record PID (0) does not match the real PID. |
PJ41179 |
Fix |
Saving an annotation fails after upgrading to Image Services 4.2. |
PJ41180 |
Fix |
A random crash occurs in the SEC subsystem when Image Services starts. This condition is often associated with error tuple 202,0,9. |
PJ41241 |
Fix |
No object stores are listed in INX_tool ce_info due to a missing ce_os_id 1000 in the INX_get_ce_id_map_info cell. |
PJ41286 |
Fix |
The dumpqs command in WQS_tool shows erroneous results after the first queue. |
NA |
Fix |
Add display of the NLS_LANG and NLS_Characterset variables and extended security to sys_log. |
NA |
Fix |
Need deadlock retries for the dbupgrade tool for populating extended security fields. |
NA |
Fix |
Resolve buffer overflow conditions in the INX, INXI, ARM, TM_daemon, and PRI_tool modules. |
NA |
Enh |
ER: Add CSM_tool FINdused option to check used space for specified blocks of cache. |
NA |
Enh |
ER: Qualify Windows and VMWare 5.1 ESXi. |
| APAR Name | Type |
Description
|
|---|---|---|
|
PJ40621
|
Fix
|
On Windows servers, terminating INX_export can cause Content Federation Services for Image Services (CFS-IS) to stop responding. |
|
PJ40648
|
Fix
|
A zero-sized PED file is created after the error: "216,0,1029 PEDs_gen_keypair - pedl_write_new_kpkf short write." |
|
PJ40755
|
Fix
|
Unable to abort Integral SDS jobs launched against Centera in background job control. |
|
PJ40765
|
Fix
|
Add a retry option to prevent the cold_3770 from terminating when a network error occurs. |
|
PJ40773
|
Fix
|
SEC_daemon terminates when more than two IP addresses are configured in fn_edit for the Root/Index server. |
|
PJ40780
|
Fix
|
A document retrieval error occurs on an NLS document when the MKF docs fields are set to surface_id=1002 and status_1=NULL. |
|
PJ40785
|
Fix
|
CFS-IS: When a user index is updated, the new index value is not federated to Content Engine. |
|
PJ40860
|
Fix
|
Running Xtaskman > Monitor RPC Activity causes TM_daemon to terminate and report a process record generation mismatch error. |
|
PJ40861
|
Fix
|
The timeoutmonitor process reports a 202,0,1049 error: "Failed to send a notification." |
|
PJ40870
|
Fix
|
CSM_tool DELETE cannot be run in a script on Windows servers. |
|
PJ40873
|
Fix
|
Enterprise Backup and Restore (EBR) errors are logged as SERIOUS, but they should be logged as INFORMATIONAL. |
|
NA
|
Fix
|
When the SDS option is used in DOC_tool, the sub-options f, delete and clipids display the message Invalid SDS=1 Not configured displayed. |
|
NA
|
Fix
|
Usage statement for the INX_export tool does not display the new -t option. |
|
NA
|
Fix
|
INX_cfs_recovery does not support new -t option. |
|
NA
|
Fix
|
The eladisp process terminates when the chfilter option is used. |
|
NA
|
Enh
|
ER: Allow SDS Unit 1 to be used with the CLIP_IDS option in DOC_tool to create a file list. |
|
NA
|
Enh
|
ER: Add a check to verify that the process ID (PID) value stored in a process record matches the actual PID for the process. |
| APAR Name | Type |
Description
|
|---|---|---|
|
PJ40004
|
Fix
|
For Windows servers, enhanced killfnsw to add more time before terminating integral SDS processes after stopping the Image Services software. |
|
PJ40295
|
Fix
|
92,2,11 DOCs - DOCl_CFS_get_annot_log_entries (line=624): INX_ce_get_object_store_id() failed during federation. |
|
PJ40351
|
Fix
|
Create a trigger file to allow the Microsoft SQL isolation level to be changed from read uncommit to read commit. |
|
PJ40386
|
Fix
|
An interlock leak occurs when committing fast batch documents to SDS device may cause 202,0,1017. |
|
PJ40467
|
Fix
|
Integral SDS background jobs do not create the writelist correctly if the Image Services software is recycled. |
|
PJ40504
|
Fix
|
Migrating Near Line Storage (NLS) documents causes 77,1,35 errors because the age duration specified is unknown to the Cache Manager (CSM). |
|
PJ40509
|
Fix
|
Migrating NLS docs causes 80,1,59 errors because SDS reader creates a checksum in page0, but not in the csm_used_space table. |
|
PJ40601
|
Fix
|
The bkg_sds process aborts when sds_migr -surface is used and the surface contains more than 5000 documents. |
|
PJ40621
|
Fix
|
On UNIX servers, terminating INX_export can cause Content Federation Services for Image Services (CFS-IS) to stop responding. |
|
NA
|
Fix
|
A GDB error that is handled by Process Engine is being logged in the elog as SERIOUS. |
|
NA
|
Fix
|
The SEC_tool decode option reports false results if the input string is invalid. |
|
NA
|
Fix
|
The performance reports do not display the correct CPU statistics on an AIX Logically Partitioned (LPAR) server. |
|
NA
|
Fix
|
On the Single Document Storage tab of the FileNet Image Services System Configuration Editor (fn_edit), the Default Retention Date field is not automatically filled in. |
|
NA
|
Fix
|
CFS-IS: With both lockdown and inbound reflect request in outbound replication, the inbound reflect is skipped. |
|
NA
|
Enh
|
ER: Enhance 911 tool to output an XML file with IBM product info (for EcuRep). |
|
NA
|
Enh
|
ER: Support for EMC Centera SDK 3.3 for Windows 2008 R2. |
|
NA
|
Enh
|
ER: Support IBM DB2 10.1 for Linux, UNIX, and Windows (LUW). |
|
NA
|
Enh
|
ER: Add a warning not to use Database Maintenance to Define or Update Document Classes or to Define User Indexes during production hours. |
|
NA
|
Enh
|
ER: Add a new clip_ids option to the DOC_tool command. The new option allows a document ID list consisting of document IDs and Centera Clip IDs to be used with the sds_import utility to import documents into the Image Services databases. |
| APAR Name | Type |
Description
|
|---|---|---|
|
PJ40003
|
Fix
|
The Multi-Keyed File MKF_tool average option returns incorrect results when the sum of the numeric field is greater than four billion. |
|
PJ40004
|
Fix
|
Creates a trigger file that adds more time before "killfnsw" terminates processes during a shutdown. (UNIX systems only) |
|
PJ40035
|
Fix
|
Mismatching properties occur between Image Services documents and their federated documents on Content Engine. |
|
PJ40112
|
Fix
|
The Image Services software does not start if the priority of an Integral SDS device is set to medium. |
|
PJ40135
|
Fix
|
SDS_CSAR_reader cores in csm_dequeue_object. |
|
PJ40187
|
Fix
|
Error tuple '121,12,65534 invalid cursor' is returned when the database is shutting down. This fix provides a new tuple. |
|
PJ40227
|
Fix
|
NCHRetrieveItem() calls generated by IMS_reserve_svc_handle() from IDM Desktop generates too many Remote Procedure Calls to the server. |
|
PJ40232
|
Fix
|
fn_snmpd crashes and stops responding Image Services software. |
|
PJ40244
|
Fix
|
INXs processes hang when waiting on a lock for INXD as shown in ipc_tool. |
|
PJ40260
|
Fix
|
DOC_tool – Inserting an MSAR surface without a fully qualitifed path name causes dtp process to core. |
|
PJ40265
|
Fix
|
The enlarge_ncol aborts with a 202,0,9 error tuple. |
|
PJ40273
|
Fix
|
121,1,12505 <fnsw> INXu – GDB_prepare failed=. Cannot determine the number of f_new_dir* & f_old_dir*. |
|
PJ40281
|
Fix
|
A fatal MKF Perm error occurs in an Images Services/Content Federated Services system while processing Records Manager records, which causes the Image Services Server to stop responding. |
| APAR Name | Type |
Description
|
|---|---|---|
|
PJ39510
|
Fix
|
The CSM update duration routine is slow when the same document id is requested more than once within a short period of time. |
|
PJ39574
|
Fix
|
Windows: SDS_CSAR_reader is unable to retrieve NLS documents because the document id and SSN numbers are byte swapped. |
|
PJ39644
|
Fix
|
Image Services processes can core when MSAR libraries are configured. |
|
PJ39694
|
Fix
|
Enterprise Backup and Recovery (EBR) restore fails due to a missing BRORxxxxx.log output file. |
|
PJ39713
|
Fix
|
Windows only: Image Services logs a 202,0,7 error during shutdown (No Shared Memory Available). |
|
PJ39714
|
Fix
|
MKF_setLongTransThreshold aborts on Windows |
|
PJ39720
|
Fix
|
sds_update_retention reports performance statistics incorrectly. |
|
PJ39728
|
Fix
|
Windows 2008 64-bit: fn_snmpd does not function properly due to change in the registry. |
|
PJ39755
|
Fix
|
dbverify displays inconsistent results regarding missing documents. |
|
PJ39791
|
Fix
|
SysV does not parse “ps -ef” properly due to internal buffer size, which causes processes to core. |
|
PJ39798
|
Fix
|
Xapex Database Admin DocClass reports are not formatted correctly. |
|
PJ39851
|
Fix
|
fn_util init incorrectly checks for free space when MKF is configured to use the filesystem format. |
|
PJ39877
|
Fix
|
The ds_init process aborts with the error message: 76,0,261 – ds_init attempted to start too many background jobs. |
|
PJ39893
|
Fix
|
On-line help is not available from the Security Administration menu for the AIX hardware platform. |
| APAR Name | Type |
Description
|
|---|---|---|
|
PJ39132
|
Fix
|
No error is returned from CSMl when no document ID is passed. Remote Procedure Calls are slow when no data is passed. |
|
PJ39224
|
Fix
|
Running Enterprise Backup and Recovery (EBR) restore with the combination of thread count > 1 and database count > 1 causes EBR process to crash. |
|
PJ39447
|
Fix
|
SDS_CSAR_reader attempts to retrieve document when FNP_CLIPID is set to Report Manager Record. |
|
PJ39448
|
Fix
|
<15,16,17> HGKMG0015E [WARNING] COR_Open: connect to addr [port#] failed with WSAGetLastError 10048. |
|
PJ39482
|
Fix
|
CSM should return 92,2,11 error when it is encountered rather than letting commit return a 77,0,7. |
|
PJ39489
|
Fix
|
Error 121,0,75 during a GDBD_logoff should be changed to INFORMATIONAL severity level. |
|
PJ39650
|
Fix
|
Remote Procedure Call (RPC) definitions are missing from the eladisp command. |
| APAR Name | Type |
Description
|
|---|---|---|
|
PJ38868
|
Fix
|
MKF_ddl reports a 161,0,11017 error adding a 17th permanent db dataset. |
|
PJ38933
|
Fix
|
SDS_worker process cores inside MKF_update reporting a 161,0,1076 error. |
|
PJ39073
|
Fix
|
When SDS_read_after_write is set, Image Services retries but does not perform a reconnect. |
|
NA
|
Fix
|
<92,2,11> SECs, SEC_verify_logon2 errors seen on cmaix16a. Content Engine repeatedly loses its log on session to Image Services. |
|
NA
|
Fix
|
An INXs memory leak occurs in the 'getarea' made in the inxl_get_doc(): |
|
NA
|
Fix
|
ISTK 4.2 clients cannot login to Image Services 4.1.2 servers. Long passwords implemented in Image Services 4.2 are not compatible with Image Services 4.1.2. |
|
NA
|
Fix
|
The spacerpt utility aborts on the Windows hardware platform. |
|
NA
|
Fix
|
Windows documents are not written correctly when using Adaptec 2932LPE and an UDO drive. |
The manifest files for each platform list checksum information for each file included in the fix pack.
To access documentation and compatibility matrixes for FileNet Image Services:
For information about contacting IBM customer support:
The Support home page contains a wide variety of options:
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
IBM Corporation J74/G4 555 Bailey Avenue San Jose, CA 95141 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd. 19-21, Nihonbashi-Hakozakicho, Chuo-ku Tokyo 103-8510, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: 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 states 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.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation J46A/G4 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.
IBM, the IBM logo, and ibm.com are trademarks or registered 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 www.ibm.com/legal/copytrade.shtml.
Microsoft, Windows, Windows NT, SQL Server, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Other product and service names might be trademarks of IBM or other companies.
|
Date
|
Description
|
|---|---|
| 29 April 2015 | Initial release of this fix pack. |