IBM FileNet
Image Services 4.1.2.26-IS-FP026 Fix Pack Readme
© Copyright IBM Corporation 2008, 2020.
Readme file for: IBM® FileNet® Image Services
Update name: 4.1.2.26
Fix ID: 4.1.2.26-IS-FP026
Publication date: 30 March 2019
Last modified date: 18 February 2020
Installation, migration, upgrade,
and configuration
Accessing IBM FileNet documentation
Contacting IBM customer support
The IBM FileNet Image Services (IS) 4.1.2.26-IS-FP026 fix pack updates
an existing Image Services 4.1.2 system. FileNet Image Services fix packs are
cumulative and include content from all previously released fix packs since the
base release. FileNet Image Services fix packs are released periodically, and include
the binary executable installation program, the manifest file, and the readme.
Important After upgrading to IBM FileNet Image Services 4.1.2 FP18 (or
higher), clients might randomly be disconnected due to an improperly configured
/fnsw/etc/serverConfig or /fnsw/etc/serverConfig.custom file. For details,
refer to this technote: Clients randomly disconnect after an
Image Services upgrade to version 4.1.2 FP18 (or higher).
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. For details, refer to this announcement: 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:
Download location
Click this link to access the files for this fix pack update: Fix Central for Fix Pack
4.1.2.26-IS-FP026.
Or from the main Fix Central website, make the following menu
selections:
|
Fix Central 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.1.2 |
Note: IBM login credentials are required to access this
download location.
For more information on compatibility
of Image Services 4.1.2, refer to IBM
FileNet Image Services, Image Services Resource Adapter, and Print Hardware and
Software Requirements.
New in this fix
pack
Removed dependency on Fix Pack 25 and resolved the stamp issue.
For details about all the resolved defects in this fix pack, see
section Fix list (APARs).
For more information about Image Services new features and known issues,
refer to IBM FileNet Image Services
Release Notes.
Introduced in Image Services 4.1.2.26-IS-FP026
·
IBM Image Services introduces support for Data ONTAP version 9.x. for snaplock NetApps. For
details, refer to this announcement: Data ONTAP version 9.x for snaplock NetApps Support Announcement.
Previous fix packs
Introduced in Image Services 4.1.2.25-IS-FP025
·
Completed
qualifications for EMC Elastic Cloud Storage (ECS) versions 2.2.1 and 3.0. For
details, see these Technotes:
o ECS
2.2.1 Support Announcement
o ECS
3.0 Support Announcement
Introduced in Image Services
4.1.2.24-IS-FP024
·
Image Services online help was added for Windows 2012 servers. For
details, refer to this technote: The Xapex help option does not display on Windows
2012.
·
Released FileNet Image Services Connector 1.4.0 & Plugin for IBM
Content Navigator. For details, refer to this announcement: Announcing the release of the FileNet Image
Services Connector 1.4.0 & Plugin for IBM Content Navigator.
Introduced in Image Services
4.1.2.23-IS-FP023
·
IMPORTANT: The dbupgrade program must be run after applying IS 4.1.2
FP14 (or higher) and restarting the software. For details, refer to this technote: 121,99,1 occurs during federation.
·
Support for Multiple COR_Listen processes to work around the TCP-accept
limit of 2,200 TCP-accepts per second per address. For details, refer to this technote: FileNet Image Services Multiple COR_Listen process
configuration.
·
Release of the FileNet Image Services Connector 1.3.0 and Plugin for IBM
Content Navigator. For details, refer to this announcement: Announcing the release of the FileNet Image
Services Connector 1.3.0 & Plugin for IBM Content Navigator.
Introduced in Image Services
4.1.2.22-IS-FP022
·
Support for MSSQL 2014.
·
Release of the FileNet Image Services Connector 1.2.0 for IBM Content
Navigator. For details, refer to this technote: Announcing the release of the FileNet Image
Services Connector 1.2.0 for IBM Content Navigator.
Introduced in Image Services
4.1.2.21-IS-FP021
·
The 911 support tool has been enhanced to gather additional information
when a problem occurs.
·
The traceit.sh support tool is now installed in the /fnsw/support
directory on all UNIX hardware platforms.
·
Release of the FileNet Image Services Connector 1.1.0 & Plugin for
IBM Content Navigator. For details, refer to this document: Announcing the release of the FileNet Image Services
Connector 1.1.0 & Plugin for IBM Content Navigator.
Introduced in Image Services
4.1.2.20-IS-FP020
·
Add optional trigger file to log the document ID sent back to the client
when a request is made. For details, refer to this document: New trigger file to track document ID allocation.
·
Add optional trigger file to troubleshoot customer applications when
adding rows to the MKF and Index databases. For details, refer to this document: New trigger file to prevent creation of Index
doctaba record.
·
Released FileNet Image Services connector for IBM Content Navigator. For
details, refer to this document: Announcing the release of the FileNet Image
Services connector for IBM Content Navigator.
Introduced in Image Services
4.1.2.19-IS-FP019
·
Support for Oracle 12c. For details, refer to this document: Support for Oracle Database Server 12c with IBM
FileNet Image Services.
·
A new support tool has been released for the Windows hardware platform.
The tool is named fn_dump and is used to create a Windows mini-dump of a hung
process. The dump file that is created can then be analyzed to determine the
cause of the problem. For details, refer to this technote: Announcing the release of the fn_dump support tool.
Introduced in Image Services
4.1.2.18-IS-FP018
·
A new stand-alone utility named isinfo is now available. The isinfo
utility is designed to help diagnose hangs on an Image Services server. For
details, refer to this technote: Announcing the release of the isinfo and wal_info
support tools.
·
Enhanced Document Security: Many FileNet Image Services 4.1.2 customers
have hundreds of millions of doctaba records in their Index Database and need
the performance improvement provided by this enhancement. The enhancement
allows up to 8 processes to perform dbupgrade for Enhanced Document Security.
Refer to the manual titled Image Services Implementing Enhanced Document
Security for instructions on implementing Enhanced Document Security.
·
When the FileNet Image Services software is started, the NLS_LANG
environmental variable setting and the Oracle database
character set will log if they do not match. A warning message is written to
the error log that character translation could cause the need for Enhanced
Document Security to be enabled. If the server has a situation where the
document security is not having permission or retrieval issues and the NLS_LANG
character set and Oracle character set do not match, the message can be
ignored.
·
A new Courier timeout enhancement has been added to Filenet Image
Services software. This new courier enhancement provides a timeout feature that
enables the user to gracefully break down any courier connection, for any given
stub type, such as CSMs, DOCs, INXs, etc., based on a user configured value.
The enhancement makes the Osar server more resilient to connectivity and
application issues by not allowing CSMs server stub connections to remain in a
RECEIVE state waiting for data over the network for an extended period of time. For details, refer to this document: Courier Timeout Enhancement.
·
A warning message has been added when the software starts if the shared
memory segment size is not 256 MB on the AIX hardware platform.
Introduced in Image Services
4.1.2.17-IS-FP017
·
Improvements to CSM_tool:
o The SCavenge
option
In the previous version of CSM_tool, the System Administrator could run
SCavenge while users were logged on to the FileNet Image Services system, which
resulted in lower system performance. Now, when SCavenge is run with the
FileNet Image Services software fully operational, the message "IS software
should be stopped before running scavenge." is displayed on the screen.
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.
o The FINdused
option
A new FINdused option has been added to CSM_tool that allows the System
Administrator to locate all of the documents that
could be impacted when an overlap condition is reported. The new option can be
accessed after entering the allowupdates password in CSM_tool.
For details on both CSM_tool options, refer
to this technote: Improvements to the SCavenge option in CSM_tool.
·
Allows Single Document Storage (SDS) Unit ID 1 to be used with the
clip_ids option in the DOC_tool command to create a file list with doc_id and
clip_id that can be used to recover or import NLS Centera documents.
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.
·
Add a fork() API and an exec() API check to the
SysV library.
On UNIX systems, a process can create a
copy of itself by calling the fork() API, which
creates a child process that is a duplicate of the parent and includes the
values of global and static variables. Normally this is not a problem; the
purpose of the fork() command is to create an
identical copy. However, care must be taken to guarantee that all inherited
variables can be used and do not need to be unique to each process.
To avoid using inherited variables in
the child, the child process immediately performs an exec()
API call to overlay itself as a totally new process with uninitialized
variables.
·
Support for ECM SDK 3.3 for
Windows 2008 R2 has been withdrawn. For details, refer to this technote: Windows 2008
R2: SDS workers abort after applying latest Fix Pack.
Introduced in Image Services
4.1.2.16-IS-FP016
·
Support for ECM SDK 3.3 for Windows 2008 R2.
·
Support for IBM DB2 10.1 for Linux, UNIX and Windows (LUW).
·
Support for HP-UX 11i v3 (11.31) Standard Patch Bundles March 2012
·
Add warning to not use Database Maintenance to Define or Update Document
Classes or to Define User Indexes during production hours.
·
Add a 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. For details, refer to this technote: DOC_tool - New option added to create file lists
for the sds_imprt command and Centera devices.
·
Add a -r (retry) option to the cold_3770 process. In earlier releases,
if the cold_3770 daemon process encountered an error while opening the
directory where the COLD data files reside, an error would be logged and the process would terminate. The new option
causes the cold_3770 process to automatically retry opening the data file in
case of an error. For details, refer to this technote: COLD - A new option has been added to the cold_3770
process to automatically retry opening the data file directory in case of an
error.
·
Add a -t (terminate) option to the INX_export command. The new option
allows users to terminate a long INX_export query gracefully without having to
restart FileNet Image Services. For details, refer to this technote: INX_export - How can I terminate the INX_export
process.
·
Resolves a problem with the Image Services performance reports not
displaying the correct CPU statistics on an AIX LPAR server. The problem is
resolved by taking advantage of current AIX API calls that are available for
LPAR CPU statistics. For details, refer to this technote: The performance reports do not display the correct
CPU statistics on an AIX LPAR server.
·
Support for new trigger files that can allow additional time for
Integral SDS background processes to finish when you stop or restart Image
Services:
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, refer to this technote: Integral SDS writelist is not
correct if the Image Services software is recycled while the background job is
running.
Introduced in Image Services
4.1.2.15-IS-FP015
·
Support Solaris 10 8/11 (Update 10) patchset release
·
Support for Refederation logging in Content Federation Services for
Image Services (CFS-IS)
·
Support for Microsoft™ SQL Server 2012
·
Support for Red Hat Enterprise Linux (RHEL) 6.0 as a remote Oracle database
server
·
Enhance the 911 tool to output an XML file with IBM product information
·
Provides a new trigger file that adds time before killfnsw terminates
processes during a shutdown. For details, refer to this technote: Software hangs on a semaphore
during shutdown.
·
Provides a new trigger file that eliminates retry messages for
"open object for read" on Integral SDS devices. For details, refer to
this technote: Hitachi HCP devices report UNIX
stale mount point errors.
Introduced in Image Services
4.1.2.14-IS-FP014
·
Support for AIX® 7.1 TL1
·
Support for Microsoft SQLserver 2008 R2 SP1
·
CFS-IS: Document federation support for a larger DIR size in the Export
log table
·
Provides support for displaying the client IP address in the error log
entry when PEDs errors are reported
·
Improves massive federation document error processing; when the export
of a document fails the corresponding annotations will not be stuck in the
annotation log
Introduced in Image Services
4.1.2.13-IS-FP013
·
No new features were introduced in this fix pack.
Introduced in Image Services
4.1.2.12-IS-FP012
·
No new features were introduced in this fix pack.
Introduced in Image Services
4.1.2.11-IS-FP011
·
Support for AIX 6.1 TL6
·
Support for HP-UX 11i v2 December 2010 Support Pack (RISC and Itanium)
·
Support for HP-UX 11i v3 (11.31) Standard Patch Bundles September 2010
·
Support for Microsoft SQL Server 2008 SP2
·
Support for Windows 2008 R2 SP1
·
Support for Windows 7 SP1 for Image Services Toolkit (ISTK) and IS
Remote Admin Console (RAC)
·
The minimum COR_set_prefetch_timeout value has been changed from 90 to
1. Specifically, the minimum prefetch timeout value has been lowered from 90
seconds to 1 second.
·
A new Multi-Keyed File (MKF) feature (MKF instrumentation introduced to
sys_log long Input/Output [I/O]) is available that helps to isolate time spent
in a long MKF_probe.
This feature helps determine if a long
MKF_probe is spent in I/O or transaction mode. The two shared libraries (FCL,
MKF) add entries to the elog when an IO or MKF transaction is greater than the
threshold values set by the user.
o The FCL module
reports where the IO is spent and how long it took by logging the action of the
I/O (read/write), the number of bytes processed, the database file and the IO
time.
o The MKF module
reports what the process performing the MKF transaction is doing by logging the
threshold value, the duration of the transaction, creating a stack trace of the
process that started the transaction, and logging the name of the file
containing the trace.
The two tools
(MKF_setLongTransThreshold and FCL_setLongIOThreshold) are used to dynamically
set the threshold values for IOs and MKF transactions without requiring a
recycle of the IS software.
Tip The file names
and commands are shown for UNIX systems. Make appropriate alterations when
performing these steps on Windows systems.
Introduced in Image Services
4.1.2.10-IS-FP010
·
Support for AIX 7.1. Oracle is supported on AIX 7.1 but with the Oracle
11gR2 (11.2.0) version only. The following IBM APARs (IBM OS Patches) are also
required: IZ87216 and IZ87564. For details, refer to this announcement: FileNet Image Services, version
4.1.2 FP10 and later, supports AIX 7.1.
·
Support for VMWare 4.1 ESX
Introduced in Image Services
4.1.2.9-IS-FP009
·
Support for DB2 pureScale cluster in a remote
database
For more information on DB2 pureScale configuration requirements, refer to this
technote: Image Services supports DB2
pureScale.
Introduced in Image Services 4.1.2.8-IS-FP008
·
911 script enhancements
The 911 script has been enhanced to
clean up temporary files. The 911 script creates temporary files in
/fnsw/local/logs/911 and by default leaves these files on the system. Two new
options were added to cleanup the files:
-r This option removes the temporary
files after they have been collected in the tar file.
-m <directory> This option moves
the temporary files to the designated directory after they have been collected
in the tar file. The directory path must be absolute (It must start with the
root directory "/").
The name of the tar file created by 911
was modified slightly. The old format updated a "version" number each
time 911 was executed on the same date (1, 2, 3, etc). This was replaced by a
time stamp for the hour and minute when the tar file was created (in 24 hr
format). This has the advantage of preserving both the date and time when 911
was run in the tar file name.
Old tar file name examples:
911.20100628.01.tar.Z
911.20100628.02.tar.Z
911.20100628.03.tar.Z
New tar file name examples:
911.20100628.0824.tar.Z (8:24 AM)
911.20100628.1216.tar.Z (12:16 PM)
911.20100628.2153.tar.Z (9:53 PM)
or
911.20100628.0824.zip (8:24 AM)
911.20100628.1216.zip (12:16 PM)
911.20100628.2153.zip (9:53 PM)
911 was also modified to run the
command "ipc_tool -P" to dump the SysV process log and save this to
the tar file. This process log provides information on Image Services activity
up to the time 911 is executed.
·
Shared memory configuration
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 details, refer to this document: Image Services Shared Memory Configuration.
·
SAS_open timeout is now configurable
In an unstable network environment, existing ISTK connections may become
unusable. This can cause Image Services software to abandon the existing
connection, then start a new connection. Error 71,0,2 is also logged at the same
time. The current SAS design waits 30 seconds before re-establishing a new
connection with the client. This defect is intended to reduce the client wait
time by making the SAS time-out value configurable. For details, refer to this
technote: Technical background and steps to
configure SAS timeout value.
After installing 4.1.2 FP8 the following informational message is written to
the event log:
2010/07/28
23:04:04.077 71,0,7 <fnsw> ds_init (1269906.1.28 0x136092.1) ... [INFO]
SAS init X_sasopentimeout: 30 initialized from
"/fnsw/local/trigger/sasopentimeout"
You can ignore the message if the default 30 second timeout is set.
·
Support for Oracle 11gR2 - Refer to this technote: Support Oracle Database Server 11g Release 2
(11.2.0)
·
Support for Microsoft SQL Server 2008 R2
·
Support for AIX 6.1 TL5
·
Support for EMC 3.2 Patch 5
·
Support for Tivoli 6.2. Refer to this announcement: Image Services introduces support for Tivoli TSM
Client API v.6.2.0.0 for DR550
Introduced in Image Services
4.1.2.7-IS-FP007
·
Software Inventory Tags made available as a common
solution for identifying the product name, product version and fix pack level
installed.
This information is now standardized, making collecting system information more
efficient for support teams, automated problem determination and compatibility
advisors. Software Tags are released for 4.1.2 FP7 and all future 4.1.2 fix
packs.
·
For FileNet-controlled Oracle 10g or later, fn_util
updaterdb fixed to automatically execute the Oracle ALTER TABLESPACE command
for all SYSAUX datasets that used fn_edit to add IS configuration.
Important As of 31 December 2011, FileNet Owned Oracle is no longer
supported. For details, refer to this announcement: Software withdrawal: IBM FileNet
Image Services with Oracle Runtime Authorized User Value Unit Renewal.
The following (legacy) information is
being maintained for historical reference:
Oracle 10g introduced a new SYSAUX
tablespace that provides storage of non-sys-related tables and indexes that
were formerly stored in the SYSTEM tablespace.
Prior to the 4.1.2.7-FP007 Image
Services fix pack, you could add additional SYSAUX datasets in Image Services
configuration, but running fn_util updaterdb did not execute the Oracle command
to actually add them to the SYSAUX tablespace. To work
around this missing functionality, it was necessary to execute the ALTER
TABLESPACE command directly in Oracle.
Since fn_util updaterdb has been fixed
to recognize SYSAUX datasets in Image Services configuration, it now
automatically runs the ALTER TABLESPACE command for all SYSAUX datasets that
were added to Image Services configuration using fn_edit
("Procedures" tab -> "Create an optional relational DB
dataset").
·
For FileNet-controlled Oracle customers that have
added additional SYSAUX data files directly in Oracle outside of Image Services
tools as a workaround prior to this fix
Before using fn_edit to add or modify any SYSAUX datasets-related configuration
and running fn_util updaterdb, there are important instructions to follow to
ensure that any of the SYSAUX datafiles that were manually added as a
workaround are not erased and reused after the command is executed.
Immediately after applying this fix
pack level, refer to this technote: New requirement for
FileNet-controlled Oracle environments that have added additional SYSAUX
datafiles for mandatory instructions. Do not use fn_edit to change any
SYSAUX-related configuration, and do not run fn_util updaterdb for any reason
until you have followed the instructions in the technote.
Introduced in Image Services
4.1.2.6-IS-FP006
·
Support for IBM Information Archive (IIA) through the existing Tivoli
Storage Manager (TSM) interface, as of 4.1.2 FP5. For details, refer to this
document: Image Services support of IBM
Information Archive (IIA).
·
New tools have been created that use getaddrinfo() to
resolve host names and determine whether they are considered local addresses.
There are two tools, one for Image Services, HAnetcheck, and one for Image
Services Toolkit, wal_getnetaddr. For details, refer to this document: Use HAnetcheck and wal_getnetaddr for nch network
configuration.
·
Simplifies Image Services High Availability clustering configuration by
dropping the requirement to re-configure the host file or DNS server. For
details, refer to this technote: Upgrading / Installing Image Services 4.1.2 in HA
cluster environment which documents the minimal Image Services
4.1.2 software level and the configuration checklist for running Image Services
in a cluster environment.
·
Enhanced Document Security - The following DRs are resolved: 849560,
849591, 849599 and 849603 (see the Fix list (APARs) table for
details). Refer to the Implementing Enhanced Document Security
section in IBM
FileNet Image Services documentation.
·
Support for Windows Server 2008 R2. This is a 64-bit only release. Refer
to this technote: Image Services Supports
Windows 2008 R2.
·
Support for SQL Server 2008 SP1
·
Support for EMC 3.2 Patch 4
·
Support for AIX 6.1 Technology Level (TL) 4
·
Support for AIX 5.3 Technology Level (TL) 11
·
Support for Solaris 10, 10/09 Update Release
·
Support for HP-UX 11i v3 (11.31) Standard Patch Bundles Sept. 2009 on
PA-RISC
·
Support for HP-UX 11i v3 (11.31) Standard Patch Bundles Sept. 2009 on
Itanium
·
Images Services now supports Windows 7 for its client applications,
Image Services Toolkit (ISTK) and Image Services Remote Administration Console
(ISRAC). For details, refer to this document: Image Services Supports Windows 7
for ISTK and ISRAC.
Introduced in Image Services
4.1.2.5-IS-FP005
·
Support for Windows 2008 SP2
·
A new -s option was added to the sgs tool to list SDS device information
for Solaris (Other platforms were previously supported.)
·
Two new options were added to the FNL_disp tool that output more
information about interlocks
o The -l option detects
and prints out interlocks that are owned by abstracts that have leaked.
The -l option is specifically for interlocks that have been allocated, used,
and encapsulated by abstracts. The option is not for per process interlocks.
Per process interlocks cannot really leak because they can be reclaimed once
the process dies.
o The -o option outputs
to stdout the number of interlocks owned by each abstract.
The information is listed in descending order of number of interlocks. The -o
option also lists the number of interlocks that are in use but have never been
de-allocated, and the number of interlocks that have been de-allocated at least
once.
·
The 911 script was modified to:
o Handle compressed
core files
o Specify an additional
core file output directory
911 searches for core files under /fnsw
and the home directory of the fnsw user. However, on some systems, you can set
the location of core files. For example, on AIX you can use the chcore command
to set the location of the core files. This feature provides you with the
advantage of creating core files in a file system that is not the file system
that Image Services uses. Thus, preventing the Image Services file system from
filling up.
If you use an additional core file directory, you can configure 911 to also
search that directory. You accomplish this by placing the new directory name in
a trigger file that is called: /fnsw/support/extra_core_directory.
For example, if the new core file directory is /tmp/corefiles, then run the
following command to create the new trigger file:
echo /tmp/corefiles > /fnsw/support/extra_core_directory
The full path to the new directory must be entered. Make sure that the
permissions for the new directory allow access by the fnsw user. The
/fnsw/support/extra_core_directory trigger file can be modified or removed at
any time other than when running the 911 script. The core files can also be
compressed to save space (911 will uncompress the core files for analysis then
compress them again).
Introduced in Image Services
4.1.2.4-IS-FP004
·
Provides the capability to configure SDS writes to occur either before
fast batch cataloging and breakup or after fast batch cataloging and breakup.
In the latter case, newly committed documents would be available to users even
if the SDS device was hard- or soft-down.
·
Support of Tivoli TSM Client API 6.1.0.0 on AIX, Solaris and Windows.
·
Support for Multiple COR_Listen processes to work around the TCP-accept
limit of 2,200 TCP-accepts per second per address. For details, refer to this
document: FileNet Image Services Multiple
COR_Listen process configuration.
·
In Image Services 4.1.2, the NCHl_RetrieveAddresses call was deprecated.
Image Services logs an error without the IP address of the client that makes
this call. It might be difficult to track down the source machine for this
call.
·
Replaced the sys_log semaphore with a spinlock timeout that prevents any
process from hanging while trying to write to the elog file.
Introduced in Image Services
4.1.2.3-IS-FP003
·
Support for DB2 9.7
·
Ability to view network activity in P8 System Manager through perfmon,
for HP-UX, Solaris, and Windows (AIX was already supported).
·
Moved COLD message strings from header file to url file so that they can
be localized when running on a non-English server.
·
Support for Integral SDS - Centera on HP Integrity servers
·
Eliminated Centera ARM requirement for advanced retention in Integral SDS
·
Implemented Read after Write feature for Integral SDS
·
Changed the perflog format. The format of the perflog file was changed
between the Image Services 4.1.2 FP002 and Image Services 4.1.2 FP003 releases.
During the upgrade procedure the
perflog file needs to be renamed so a new format perflog can be created. When
the Image Services software is started, perf_mon will automatically create a
new perflog with the new internal format.
Procedure:
1. Stop the Image
Services software.
2. As the fnsw user,
save the old perflog file:
UNIX mv /fnsw/local/sd/1/perflog /fnsw/local/sd/1/perflog.old
Windows rename \fnsw_loc\sd\1\perflog \fnsw_loc\sd\1\perflog.old
3. As the root user,
install 4.1.2 FP003
4. As the fnsw user,
start the Image Services software.
5. Verify that the
perf_mon utility is running, and that a new perflog file has been created.
Introduced in Image Services
4.1.2.2-IS-FP002
·
EMC SDK 3.2 Patch 3
·
Microsoft SQL Server, 64-bit, locally on Windows® 64-bit OS
·
Microsoft SQL Server 2005, 32-bit, on Windows 64-bit OS
o fn_setup_rdb.cmd was
modified to support Windows 64-bit
·
Image Services on Windows 64-bit
For more information about Image Services support for SNMP v3 on AIX 5.2
and later, refer to IBM FileNet Image
Services Release Notes.
Introduced in Image Services
4.1.2.1-IS-FP001
·
Support for IPv6 network addresses.
For Image Services 4.1.2 compatibility information, refer to IBM FileNet Image
Services, Image Services Resource Adapter, and Print Hardware and Software
Requirements.
Installation, migration, upgrade, and configuration
This section contains the following topics:
Graphical installation and silent installation modes
DISPLAY environment variable on UNIX servers
Windows cluster server guidelines
Special procedure for IBM Tivoli Monitoring
Tip: Installation of this fix pack is not affected by any virus protection
software that might be running in the background.
Note: Removed dependency on Fix Pack 25.
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.
Requirements
This fix pack has the following minimum requirements:
·
IBM FileNet Image Services 4.1.2 base version
Disk space requirements
·
Directory for Image Services software (typically, /fnsw), two times the
size of the fix pack.
·
Temporary disk space (by operating system)
|
Temporary disk space requirements by operating system |
||
|
Operating system |
Recommended minimum disk space |
Temporary directory used by the
installation program |
|
AIX |
250 MB |
/tmp |
|
HP-UX |
450 MB |
/var/tmp |
|
HP-UX |
450 MB |
/var/tmp |
|
Solaris |
250 MB |
/var/tmp |
|
Windows |
250 MB |
temp On
Windows servers, the installation program determines the temporary file path
in the following sequence: o The path specified by the TMP
environment variable o If TMP is not defined, the path
specified by the TEMP environment variable o If both TMP and TEMP are not
defined, the Windows directory Tip The
installation program does not run any checks to verify that a specified
directory exists. |
·
You can override the temporary directory on both UNIX and Windows
servers by adding -is:tempdir directory to
the command line as shown here. However, the directory must
already exist, and it must be located outside of the /fnsw directory (UNIX) or
the \fnsw and \fnsw_loc directories (Windows). For example, on an AIX server
you might enter:
·
is_4.1.2-FP26_aix.bin -is:tempdir directory
Backups
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.1.2-HFP26/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 must 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.
Installation log
files
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.1.2/HFP26/
·
/fnsw/local/logs/hfp/4.1.2/HFP26/ismp/
·
/fnsw/local/logs/hfp/4.1.2/HFP26/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.1.2\HFP26\
·
IS_local_directory\logs\hfp\4.1.2\HFP26\ismp\
·
IS_local_directory\logs\hfp\4.1.2\HFP26\misc\
Fix pack installation logs
The .../4.1.2/HFP26/ directory contains the is_412-HFP26.log file. This
log file lists all the Image Services modules that were replaced. Each time you
run the installation program, 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 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. If the number
of files do not match, verify that all Image
Services-related applications are stopped, and run the fix pack again.
Example: 300 files of 300 have been
copied to the target (your installation might have a different number of files)
Tip: Due to an InstallShield known issue about clearing out temporary
directories, you might have to manually clear the temporary directory of
extraneous files, especially after a failed installation.
InstallShield
Multi-Platform (ISMP) logs
The .../ base_release
/HFP # /ismp/ directory contains log files generated by the InstallShield
Multi-Platform (ISMP) program if the fix pack installation was not successful.
·
ismp_product_log.txt
·
ismp_wizard_install_log.txt
·
ismp_wizard_uninstall_log.txt
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
Miscellaneous logs
The .../ base_release
/HFP # /misc/ directory has several logs that can be used for troubleshooting
and debugging:
·
configFiles.log - Lists the
configuration files replaced by this fix pack
·
devModules.log - Lists development
modules replaced by this fix pack
·
newerFiles.log - Lists files that
were newer than the ones provided by this fix pack
This directory also
contains a record of the file "stamp" information before
and after the installation.
Graphical installation and silent installation modes
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/
base_release /HFP # / directory (the \fnsw_loc\logs\hfp\ base_release \HFP # \
directory on Windows servers). On UNIX servers, the command tail -f is_
base_release -HFP # .log dynamically displays the installation log as it is
created.
Before using silent
installation mode, verify that the default temporary directory contains the
amount of free space described in the previous section. The amount of free disk
space must be verified either manually or through an automated script. Lack of
sufficient disk space will prevent the installation program from starting
successfully. Note that if no prior fix packs have been installed on the
current Image Services release, the main fix pack log will not exist. The
absence of this log file also indicates a failed installation.
DISPLAY environment variable on UNIX servers
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 root, 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.
Windows cluster server guidelines
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:
1.
Stop node 2.
2.
On node 1:
a.
Stop the Image Services
ControlService service.
b.
Install the fix pack on
node 1.
c.
Restart node 1.
d.
Start the Image
Services ControlService service, and verify that it
started successfully on node 1.
3.
On node 2:
a.
Start node 2.
b.
Move Image Services
resources to node 2.
c.
Stop the IS
ControlService service.
d.
Install the fix pack on
node 2.
e.
Restart node 2.
f.
Move Image Services
resources to node 2.
g.
Bring the Image
Services ControlService online and verify that it started successfully on Node
2.
4.
Move Image Services resources
to node 1.
Special procedure for systems that use IBM Tivoli® Monitoring
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:
1. From the Action tab, click the pull-down menu and click Stop.
2. Complete the Image Services and Image Services Toolkit installation.
3. From the Action tab, click the pull-down menu and click Start.
Installing this fix
pack
Important: Windows installations: There is a known compatibility
issue where an Image Services fix pack that has been zipped using WinZip
version 9.0 cannot be unzipped using WinZip version 8.0. We recommend that
users upgrade to 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.
1. Download and extract
the 4.1.2.26-IS-FP026 fix pack for your operating system.
2. Log on to the Image
Services server as a user that has the appropriate permissions to start and
stop Image Services.
UNIX
Log on as a user with root privileges.
Windows
Log on with Administrator privileges.
3. Stop all instances of
Image Services.
UNIX
On all UNIX servers:
a. Stop Image Services:
initfnsw -y stop
killfnsw -DAy
b. Determine if any fnsw
processes are running:
ps -elf | grep fnsw
c. Stop any fnsw
processes that are still running:
kill -9 processID
d. Determine if any view
log (vl) processes are running:
ps -elf | grep vl
e. Stop any vl processes
that are still running:
kill -9 processID
f. (HP-UX and Solaris
only) Determine if any MasterSnmpd process are running:
ps -elf | grep
MasterSnmpd
g. Stop any MasterSnmpd
processes that are still running:
kill -9 processID
h. If Image Services
Toolkit (ISTK) is installed on this server, stop all ISTK applications that
interface with Image Services, and then enter the following command to clear
out the ISTK shared memory:
wal_purge
Restriction: Do not run any other Image Services commands
prior to installing the fix pack.
Windows
On all Windows servers:
a. Stop Image Services:
initfnsw -y stop
killfnsw -Dy
Important:
·
The killfnsw command also stops the Image Services Control Service.
·
Do not run any other Image Services commands before
you install the fix pack.
b. Stop the Simple
Network Management Protocol (SNMP) process:
net stop "SNMP"
Tip: Windows automatically
clears the ISTK shared memory.
2. The
/fnsw/etc/serverConfig could be overwritten by a Fix pack installation. If the
server contains a file named /fnsw/serverConfig.custom this is not an issue and
no action is necessary.
If the serverConfig.custom file does
not exist, copy the serverConfig file to serverConfig.custom before applying
the Fix Pack to preserve the current settings.
3. Start the fix pack
installation program.
Important:
·
If the installation program does not appear to be running, compare the
size of the downloaded fix pack to the size of the fix pack posted on the IBM
support site. If they differ in size, download and run the fix pack again.
However, installation of this fix pack can take several minutes, depending on
the server processor speed.
·
If a message indicates that Image Services was not stopped correctly,
determine if any processes previously stopped abnormally, and then stop them
correctly.
UNIX - If any files are in the
/fnsw/procs directory, delete them and the installation program will work
correctly. If the files were recently created (during shutdown), look at the
files through an editor to determine what went wrong.
Windows - Use the
Windows Task Manager to check for and terminate any processes that were stopped
abnormally.
UNIX
k. Verify the DISPLAY
environment variable is set correctly. For more information, see DISPLAY
environment variable on UNIX servers earlier in this readme.
l. Verify the file is
executable. If it is not, add execute permission with the following command:
chmod +x is_4.1.2-FP26_ operating_system .bin
m. Change to the
directory where you installed the fix pack file, and enter the file name:
Graphical mode
./is_4.1.2-FP26_ operating_system .bin
Silent mode
./is_4.1.2-FP26_ operating_system .bin
-silent
Windows
Graphical mode
·
Locate and double-click the is_4.1.2-FP26_win.exe file.
Silent mode
·
Open a command prompt and enter the name of the fix pack:
drive :\is_4.1.2-FP26_win.exe
-silent
4. (Graphical mode users
only) Follow the instructions in the InstallShield wizard.
5. (Windows only) When the fix
pack installation completes, you do not need to restart Windows, unless you are
prompted to do so.
6. (HP-UX and Solaris
only) If you were not prompted to restart the server, restart the
MasterSnmpd daemon.
MasterSnmpd_start &
7. Check the log files
to ensure the installation was successful. Checking the log files is especially
important if the installation ran in silent mode. For more information, see Fix pack
installation logs earlier in this readme.
8. (AIX and Solaris
only with optical storage libraries attached) Determine if a new fnsod
(FileNet SCSI Optical Device) driver or or cfgfnsod module is included with
this fix pack. For more information, see Files changed in this fix pack later in this
readme. If a new driver is included with this readme, you must install it
manually by entering the following command. The update will go into effect the
next time the server is restarted.
fnsod.install /fnsw/bin/fnsod
9. Compare the fix pack
content on your server with the latest modules available.
a. Navigate to the
untarred/unzipped fix pack files and locate the scrs.platform .412.db
file. Place it into the /fnsw/local/tmp directory.
b. Change directory to
the /fnsw/local/tmp directory, and enter the following command to compare the
files on the system with the latest modules:
getstamps.sh -all
c. If a module is marked
with PASS on the report, it is the current released version. If a module is
marked with FAIL, contact customer support. For more information, see Contacting IBM customer support later in this
readme.
Upgrade to SQL
Server 2005 (Optional)
If you plan on
upgrading to SQL Server 2005 during this fix pack installation, complete the
upgrade, and then run the following command at a DOS command prompt:
fn_setup_rdb -u
After running the
fn_setup command, close the command window and open a new command window to
ensure that SQL Server 2005 is using the correct path.
After the fix pack is
successfully installed on all Image Services servers in the Image Services
domain, you can resume normal processing.
Tip: If the Oracle,
Microsoft® SQL Server, or DB2® database is site-controlled, restart the
database software before starting Image Services.
1.
Restart Image Services
by using the Task Manager (Xtaskman) or by entering the initfnsw -y start
command.
2.
Use the Protocol
Process Manager Operator Interface (PPMOI) tool to ensure that the serverConfig
stub settings are correct.
a.
At a command prompt,
enter:
PPMOI
b.
Display the current
settings by entering:
PPMOI show
c.
Verify that the
settings displayed by PPMOI are correct.
3.
When Image Services
returns to normal operations, you can delete or back up the fix pack
installation program.
MSAR surface check
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
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 syntax is as follows:
MSAR_surf_fixup_14x
[-f] [-s surface_id ]
-f
causes the fix to run if the original optical surfaces are
available.
-s
surface_id causes the fix to run if the Original
optical surfaces are available.
Restrictions
·
The original optical
surface must be present to find or fix a problem.
·
This tool must be run
on every storage library server.
·
Only one copy of
MSAR_surf_fixup_14x can be run at a time on a server.
HP drives: Obtain the
HP 14x Magneto-Optical v1.19 or higher firmware
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.
Sony® drives: Obtain
the Sony 14x Magneto-Optical v1.13 or higher firmware
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.
Compare the optical
and MSAR surfaces
After the firmware on
the optical drives is updated, locate all the original 9.1 GB optical disks
that were converted to MSAR.
1.
Insert the 9.1 GB
optical disks into the storage library.
2.
Insert the
corresponding MSAR surfaces using Storage Library Control. (See Chapter 3 of
the MSAR Procedures and
Guidelines, if necessary. To find this document on the IBM support
page, see Accessing IBM FileNet documentation, compatibility
matrices, and fix packs)
3.
As the FileNet software
user, such as fnsw, run the MSAR_surf_fixup_14x tool.
MSAR_surf_fixup_14x -f
Important If you have many 9.1
GB optical disks, you can compare them in groups. All the MSAR converted
surfaces and optical surfaces do not have to be present at once. For example,
you can insert a group of optical disks and the corresponding MSAR converted surfaces, and run the tool with no parameters to produce a
list of the MSAR surfaces that need to be fixed. Rerun the tool as often as
necessary on different groups of media to determine if any other MSAR surfaces
need to be fixed.
As the tool scans the MSAR surfaces, it adds a new field to the MSAR header.
The tool marks surfaces that were not converted from 9.1 GB optical media as
"Not Scanned." If an MSAR converted surface has been fixed (with the
-f option) or if no problem exists, the tool marks the surface "N"
(no problem exists). But if an MSAR converted surface does not match the
optical surface, and you did not use the -f option, the tool marks the MSAR
surface "Y" (yes, a problem exists).
4.
The MSAR_surf_fixup_14x
tool creates a log file named sc_YYYYMMDD_HHMMSS.log
in the following location:
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 surfacesHost Server Name: cassiniCreation Date & Time: 01/05/2013 15:43:06MSAR MSAR MSAR Optical Optical Orig OrigSurface Problem Surface Surface Surface Surface Optical OpticalID Exists Avail Type ID Avail SSN surface id========== =========== ======= ======= ========= ======= ======= ==========3002 Y Y Conv 3001 Y 20119 20827Document id: 100040, ssn 20119 loc_id 1528574237 surf_ids 1002 and 0.Bad sector range 1087730 to 1093255. Bad sector count: 5526. Fixed: No3004 Not scanned N Non 9.1 XXXX X XXXX XXXX3006 Not scanned Y Non 9.1 XXXX X XXXX XXXX3008 N Y Conv 3001 Y 20119 208271 bad converted surfaces found out of 2 9.1G converted surfaces.2 non-9.1G converted surfaces found.End of Job Date & Time: 01/05/2013 15:45:41Report name: C:\FNSW_LOC\logs\msar_check\sc_20130105_154121.log |
5.
If you have not updated
the HP 14x firmware, the following message displays:
Optical disk drive for surface 3001 does not have current revision
firmware. Currently installed FW Rev: 1.18. Required FW Rev: 1.19.
Disable this drive, ensure that only updated drives are enabled,
and re-run tool.
6.
If you have not updated
the Sony 14x firmware, the following message displays:
Optical disk drive for surface 3001 does not have current revision
firmware. Currently installed FW Rev: 1.12. Required FW Rev: 1.13.
Disable this drive, ensure that only updated drives are enabled,
and re-run tool.You must exit the tool and either
update the firmware or disable the optical drive before you can continue.
7.
Repeat the
MSAR_surf_fixup_14x tool as often as necessary on each storage library server
until all MSAR converted surfaces have been scanned and fixed.
Shared memory configuration
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 details, refer to this technote: Image Services Shared Memory Configuration.
Uninstalling this
fix pack
Only the most recently installed fix pack can be uninstalled. If you
need to return an even earlier version, you must 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 be successful.
UNIX
Important Use only this
command to uninstall the fix pack. Using the operating system tools can delete
vital data that is needed for future fix pack installations.
1. Log on to the UNIX
system as a user with root privileges.
2. Stop Image Services.
3. Start the
uninstallation program:
/fnsw/hfp/_uninst/uninstall_hfp.bin
Windows
1. Log on to the Windows
system as a user with Administrator privileges.
2. Stop Image Services.
3. Open the Control
Panel window.
4. Select Add/Remove Programs.
5. Select the Image
Services fix pack entry, and click Add/Remove...
Fix list (APARs)
The following tables list the product fixes in this fix pack.
|
4.1.2.26-IS-FP026 |
||
|
APAR |
Type |
Description |
|
PJ45553 |
Fix |
DOCs
server stubs back up
when Oracle TNS listner is RDBMS is slow |
|
PJ45550 |
Fix |
TM_daemon
reports getservbyname failure |
|
PJ45457 |
Fix |
dtp_tran
reports 121,1,12545 Error encountered during committal with SDS Fast Batch Committal |
|
PJ45374 |
Fix |
SEC_tool
reports 202,0,43 Signal 13 received and ignored error |
|
PJ45321 |
Fix |
IS
Connector: logonImageServices(): sec login failed
but error tuple was blank in the log |
|
PJ45313 |
Fix |
Fast
Batch committal fails with error 80,1,61 if FBC cache object is deleted and
write request remains |
|
PJ45269 |
Fix |
IS
Connector: ClassNotFoundException: com.filenet.is.ra.util.FN_IS_MessageImpl |
|
PJ45236 |
Fix |
dtp_tran
reports 161,1,1004 CSMl Error inserting a record into the free space table |
|
PJ45224 |
Fix |
Comittal
not written to SDS on system configured for SDS storage only due to doc class
set to the default of no migrate |
|
PJ45117 |
Fix |
wqs_table_gen
terminates prematurely with 121,0,37 when public synonym is missing |
|
PJ45087 |
Fix |
docfetch
creates INX shared memory leak when retrieving NLS document |
|
PJ45061 |
Fix |
INX_export
went into infinite loop after encountering <90,0,1030> error. |
|
PJ45060 |
Fix |
DOCl_CFS_get_annot_log_entries
SEVERITY UNKNOWN syslog while federation |
|
PJ44692 |
Fix |
getssn
reports 90,0,1030 error: 1450 |
|
PJ44612 |
Fix |
CSM_tool
- delage command is unable to skip busy object to delete other agable objects |
|
PJ44551 |
Fix |
Retrieve
unmigrated error: 47,0,14 because SDS_doc_is_available().
Failed with error tuple 92,2,11 as the user is not logged in. |
|
PJ44541 |
Fix |
Oracle
connection error 121,0,78 - Query retry error was not handled correctly by
internal client calls. |
|
PJ44445 |
Fix |
SDS FBC
fails with 238,5,2 error tuple |
|
PJ45586 |
Fix |
DOCl_CFS_get_annot_log_entries_2
reports 121,1,12547 INX_logon failed |
|
PJ44839 |
Fix |
Using IS
Connector 1.2. When retrieval of documents is not found in Centera archived
storage, the elog keeps looping the log information.Error
tuple 238,1,3. It is found in elog. |
|
PJ44691 |
Fix |
To
change the Password Never Expires flag to TRUE or FALSE incorrectly requires
a new password to be entered |
|
PJ45458 |
Enh |
ER:
Qualify Image Services for ONTAP 9.0 |
|
PJ45422 |
Enh |
ER:
CSM_tool listing and delete filters lock objects, temporary, none temporary
cache objects, display page0 |
|
PJ45312 |
Enh |
ER: Qualify
Image Services on AIX 7.2 LPAR |
|
PJ45311 |
Enh |
ER: Qualify
Image Services with Oracle 12.2.0 |
|
PJ45256 |
Enh |
ER: Qualify
Image Services with Hitachi Content Platform 7.3 |
|
PJ45183 |
Enh |
ER:
/fnsw/etc/serverConfig 7th column comment is misleading. |
|
PJ45058 |
Enh |
ER:
Qualify Image Services for EMC Elastic Cloud Storage (ECS) 3.1 via the
Centera APIs. |
|
PJ45008 |
Enh |
ER:
Qualify Image Services Connector 1.4.0.x with IBM Content Navigator 3.0. |
|
PJ44999 |
Enh |
ER:
Qualify Image Services / Image Services Toolkit / Remote Admin Console (RAC)
for both 4.2.0 and 4.1.2 releases on Windows 2016. |
|
PJ44998 |
Enh |
ER:
Qualify Image Services with DB2 v11.1 |
|
PJ44997 |
Enh |
ER:
Enhance deldocs to include surface location in expanded verbose option -V. |
|
PJ44996 |
Enh |
ER: Qualify
Image Services with SQL 2016 SP1 database |
|
PJ44743 |
Enh |
ER:
Allow creation of Oracle libraries symbolic link manually by using a trigger
file on UNIX platforms. |
|
PJ44416 |
Enh |
ER: Add
capability to elog when commonly used command line tools are initiated. |
|
4.1.2.25-IS-FP025 |
||
|
APAR |
Type |
Description |
|
PJ43992 |
Fix |
The SDS_CSAR_reader reports a <0,0,1> error with UNKNOWN
SEVERITY - Remote server: page_cache7 Check elog on remote server for more
information. |
|
PJ44033 |
Fix |
The SDS_CSAR_reader process can abort when receiving a long error
message from Centera due to a buffer overrun. |
|
PJ44116 |
Fix |
MSAR surface becomes disabled when the dtp process reports a 61,0,10
error. |
|
PJ44158 |
Fix |
When migrating a document 121,1,25408 errors are reported - Oracle
lost connection error. |
|
PJ44163 |
Fix |
GDB_logon - Incorrect function testing |
|
PJ44090 |
Fix |
AIX: If the file /etc/slibclean exists, after shutting down the Image
Services software, a file is left behind in the /fnsw/procs directory. |
|
PJ44354 |
Fix |
The dtp is using CSM Null handle causing CSM/dtp to abort |
|
PJ44360 |
Fix |
SDS_worker on Solaris has segmentation violation when deleting
document |
|
PJ44379 |
Fix |
IS Connector: Content Navigator Desktop hangs intermittently with IS
users without primary group assigned |
|
PJ44547 |
Fix |
Qualify Image Services for EMC Elastic Cloud Storage (ECS) 2.2.1 and
3.0 via the Centera APIs |
|
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 |
|
4.1.2.24-IS-FP024 |
||
|
APAR |
Type |
Description |
|
PJ43589 |
Fix |
BESs logs an 88,0,52 error – BESl: 'batch_open_id' wrap around in
'batch_ctl record – not recoverable. |
|
PJ43644 |
Fix |
IS 4.1.2 FP12 installer must create the /fnsw/local/tmp/fnsw_update
file to force dbupgrade to be run when the software is started. |
|
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,0,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 login to enable an SDS device again when it
becomes disabled for writes. |
|
PJ43836 |
Fix |
Windows: Image Services GUI help option returns “You are not connected
to online Help, where the latest help content is available. |
|
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. |
|
PJ43900 |
Fix |
Improve TM_daemon logging when recv() returns
a zero status. |
|
PJ43726 |
Enh |
ER: Replace OpenProcess(0 in the ISTK SysV
routine fnl_is_dead(0 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. |
|
PJ43709 |
Enh |
ER: Image Services Connector 1.4.0 for IBM Content Navigator. |
|
4.1.2.23-IS-FP023 |
||
|
APAR |
Type |
Description |
|
PJ42962 |
Fix |
DOC_tool SDS statistics report provides incorrect information on ISDS
reads when sds_read_after_write is enabled. |
|
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. |
|
PJ43498 |
Fix |
Add Oracle 12.1.0 to fn_edit for Oracle 12c support. |
|
PJ43501 |
Fix |
An 80,0,12 error is logged when Capture commits batch specifying
Alternative Page Cache pointing to page_cache1. |
|
PJ43564 |
Fix |
The 911 output file does not contain the DOC_tool SDS report on the
Windows hardware platform. |
|
PJ42936 |
Enh |
ER: Improve error logs message to point to the server when the dtp
process reports MKF database full errors (161,1,1075). |
|
PJ43247 |
Enh |
ER: Perform additional retries within Integral SDS when SnapLock
repository operations fail. |
|
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. |
|
PJ43408 |
Enh |
ER: Image Services Connector 1.3.0 for IBM Content Navigator. |
|
4.1.2.22-IS-FP022 |
||
|
APAR |
Type |
Description |
|
PJ43130 |
Enh |
ER: Provide additional logging when a SEC_map error is encountered
processing records in the annot_log table to the end user understands how to
resolve the problem. |
|
PJ42438 |
Fix |
When a Fix Pack is uninstalled the reference in the vdp.properties
file is not removed. |
|
PJ42555 |
Enh |
Running killfnsw commands during shutdown can hang the software on a
semaphore. |
|
PJ42726 |
Fix |
Change a misleading error message - 121,0,2 - 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. |
|
PJ43189 |
Enh |
ER: Image Services Connector 1.2.0 for IBM Content Navigator. |
|
PJ42819 |
Fix |
The docimp program fails and reports a 30,0,35 error. Cannot write
checkpoint file. |
|
PJ42924 |
Fix |
Add the folder C:\fnsw_loc\logs\CFSIS to fn_perm and
/fnsw/local/logs/CFSIS to permission_table. |
|
PJ42822 |
Fix |
Security Administration hangs when attempting to view User Detail
report on the AIX hardware platform running IS 4.1.2. |
|
PJ43009 |
Fix |
Integral SDS retry/connection does not recover, causing the SDS device
to be disabled. |
|
PJ43131 |
Fix |
ER: Add additional logging when courier disconnects under certain error
conditions. |
|
N/A |
Enh |
Support for MSSQL 2014. |
|
4.1.2.21-IS-FP021 |
||
|
APAR |
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). |
|
4.1.2.20-IS-FP020 |
||
|
APAR |
Type |
Description |
|
PJ42507 |
Fix |
The SQIs process crashes if FIPS is configured. |
|
PJ42250 |
Fix |
Long MKF transaction times can occur when running sds_copy or sds_migr
resulting in performance issues. |
|
PJ42290 |
Fix |
SEC_init -o aborts when Image Services is started – 161,0,1076 error –
MKF_end_transaction: process not in transaction state. |
|
PJ42363 |
Fix |
Online EBR backup fails with 202,100,10 BRTs Fatal MKF Error reading
the rl partition. |
|
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
startup. |
|
PJ42484 |
Fix |
Database queries can return duplicate folders. |
|
PJ41953 |
Fix |
Interlock usage increases when committing fast batch documents to an
Integral SDS device. |
|
PJ42441 |
Enh |
CSM_exim -e -c page_cache1 -o aborts with Bad page number 3237224,
should be in 1 to 1000 on Windows platform. |
|
PJ42363 |
Enh |
ER: Enhancement to validate cache consistency – csm_free_space with
csm_used_space. |
|
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. |
|
PJ42511 |
Enh |
ER: Enhance 4.1.2 Image Services installer for the Image Services
connector for IBM Content Navigator WAR file. |
|
PJ42512 |
Enh |
ER: Release Image Services connector for IBM Content Navigator (Query,
Retrieval & Committal). |
|
4.1.2.19-IS-FP019 |
||
|
APAR |
Type |
Description |
|
PJ42223 |
Enh |
ER: Support for Oracle 12c. |
|
PJ41399 |
Fix |
A <155,2,3> COR_Listen - getinterlock(rpclock) failed is
reported in the Image Services error log. |
|
PJ41437 |
Fix |
Windows: Checksum errors 77,1,58 are reported when retrieving Integral
SDS documents in an SDS Only environment.. |
|
PJ41449 |
Fix |
sds_copy logs a 202,100,10 error when MSAR/optical surfaces are not
available and copying NLS documents.. |
|
PJ42152 |
Enh |
ER: Image Services GA Installer now supports Windows 2012. |
|
PJ41454 |
Enh |
ER: Request to add isinfo to the beginning of 911. |
|
PJ41585 |
Fix |
Windows: 202,0,2005 check_seg_addrs: CreateFileMapping
'Global\CHK_SHM_2436_7700' err=5. |
|
PJ41656 |
Fix |
Windows: DOC_tool is not able to obtain retention settings for
documents migrated to Hitachi HCAP. |
|
PJ42149 |
Enh |
Add general signal handlers to SysV library. |
|
PJ41938 |
Fix |
The docfetch utility takes a long time to complete when using the -s
option. |
|
PJ41953 |
Fix |
Interlock usage increases when committing fast batch documents to an
Integral SDS device. |
|
PJ42148 |
Enh |
ER: Change the courier recv time out error log entry. |
|
PJ42126 |
Enh |
ER: Add Windows dump file creation to SysV to aid in trouble shooting
problems when processes hang or abort. |
|
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. |
|
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. |
|
4.1.2.18-IS-FP018 |
||
|
APAR |
Type |
Description |
|
N/A |
Fix |
Allow up to 8 processes to perform dbupgrade for extended security. |
|
N/A |
Fix |
Add display of NLS_LANG, NLS_Characterset, and extended security to
sys_log. |
|
N/A |
Fix |
Resolve buffer overflow conditions in the INX, INXl, ARM, TM_daemon
and PRI_tool modules. |
|
N/A |
Fix |
Unable to locate enough shared memory addresses on startup. |
|
N/A |
ER |
Add warning message when the software starts if the shared segment
size is not 256 MB on the AIX hardware platform. |
|
N/A |
ER |
Release the isinfo and wal_info modules to assist in troubleshooting
SysV issues. |
|
PJ41046 |
Fix |
SECs deadlock – SEC interlock not released. |
|
PJ41180 |
Fix |
Random crash in SEC subsystem during IS startup. The condition is
often associated with error tuple 202,0,9. |
|
PJ41186 |
Fix |
Windows: ipc_daemon process not able to connect to all shared memory
segments when starting Image Services. |
|
PJ41187 |
Fix |
Windows: The addr_list file is not updated correctly when the last
address in the file is reported as a conflict. |
|
PJ41232 |
Fix |
Add the Courier timeouts: recv() timeout and
prefetch timeout. |
|
PJ41241 |
Fix |
No object stores listed in INX_tool ce_info due to missing ce_os_id
1000 on INX_get_ce_id_map_info cell. |
|
PJ41295 |
Fix |
Windows: Error 5 reported when opening a process owned by another
user. |
|
PJ41305 |
Fix |
Windows: ISTK logs a Global/ADC0ADC0 CreateFileMapping FAILED err=5
message. |
|
PJ41354 |
Fix |
Solaris: SysV: The highest shared memory segment (#128) is now in use. |
|
PJ41416 |
Fix |
The timeoutmonitor causes EBR performance issues. |
|
4.1.2.17-IS-FP017 |
||
|
APAR |
Type |
Description |
|
PJ40621 |
Fix |
Windows: Terminating the INX_export process can cause Content
Federation Services for Image Services (CFS_IS) to stop responding. |
|
PJ40860 |
Fix |
Running Xtaskman > Monitor RPC Activity causes TM_daemon to
terminate and report a process record generation mismatch error. |
|
PJ40861 |
Fix |
The timeout monitor process reports a 202,0,1049 error: Failed to send
a notification. |
|
PJ40870 |
Fix |
The CSM_tool DELETE option cannot be run in a script on Windows
servers. |
|
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 is written to the Single Document Storage
(SDS) device. |
|
PJ40982 |
Fix |
Withdraw support for EMC Centera SDK 3.3 for Windows 2008 R2. |
|
PJ41113 |
Fix |
TM_daemon reports a 202,4,17 error - FNL_lock: Process record PID (0)
does not match the real PID. |
|
NA |
Enh |
ER: Add CSM_tool FINdused option to check used space for specified
blocks of cache. |
|
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 fork() API and an exec() API check
to the SysV library. |
|
4.1.2.16-IS-FP016 |
||
|
APAR |
Type |
Description |
|
PJ30648 |
Fix |
A zero sized PED file is created after 216,0,1029 PEDs_gen_keypair -
pedl_write_new_kpkf short write error. |
|
PJ40004 |
Fix |
For Windows servers, enhanced killfnsw to add more time before
terminating Integral SDS processes after stopping the Image Services
software. |
|
PJ40467 |
Fix |
Integral Single Document Storage (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). |
|
PJ40506 |
Fix |
The performance reports do not display the correct CPU statistics on
an AIX Logically Partitioned (LPAR) server. |
|
PJ40509 |
Fix |
Migrating Near Line Storage (NLS) documents causes 80,1,59 errors
because SDS reader creates a checksum in page0, but not in the csm_used_space
table. |
|
PJ40584 |
Fix |
The Uninstallation wizard for a fix pack does not restore the sysv.dll
file on Windows servers if sysv.dll is loaded after this initial check. |
|
PJ40621 |
Fix |
Terminating the INX_export process can cause Content Federation
Services for Image Services (CFS-IS) to stop responding. |
|
PJ40755 |
Fix |
SDS_find_object should not be retried if the background (BKG) job has
been aborted and PG_cancelled is set to TRUE. |
|
PJ40765 |
Fix |
Add a retry option to prevent the cold_3770 from terminating when a
network error occurs. |
|
PJ40773 |
Fix |
SEC_daemon terminates when there are more than two IP addresses
configured in fn_edit for the Root/Index server. |
|
PJ40775 |
Fix |
After applying Image Services 4.1.2 FP15, document retrieval is very
slow when using docfetch with the -f or -s option. |
|
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. |
|
NA |
Fix |
A Generic Database (GDB) error that is handled by Process Engine is
being logged in the elog as SERIOUS. |
|
NA |
Fix |
The fn_setup_rdb tool does not work after Image Services 4.1.2 FP15 is
installed. |
|
NA |
Fix |
The CSM_daemon does not keep up with deleting ageable items from page
cache. The cache becomes 100% full and creates <77,0,8> errors. |
|
NA |
Fix |
The DOC_tool utility cannot display a document that is stored on an
SDS foreign device. |
|
NA |
Fix |
When Image Services is started, the SEC_daemon process terminates if
the repository string is too long. |
|
NA |
Fix |
The sds_import tool does not check the original SDS device name and
System Serial Number (SSN) when importing documents. |
|
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 to not 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. |
|
4.1.2.15-IS-FP015 |
||
|
APAR |
Type |
Description |
|
PJ40004 |
Fix |
Create a trigger file on UNIX servers to add more time before killfnsw
terminates processes during a shutdown. |
|
PJ40187 |
Fix |
Error tuple 121,12,65534, invalid cursor, is returned when the
database is being shutdown. Need new tuple. |
|
PJ40227 |
Fix |
NCHRetrieveItem() calls that are generated by
IMS_reserve_svc_handle() from IDM desktop generate too many RPCs to the
server. |
|
PJ40232 |
Fix |
The fn_snmpd tool fails and causes Image Services to stop responding. |
|
PJ40243 |
Fix |
The SDS_worker process aborts, reporting a 202,0,1014 error.
"FNL: release: caller error: release limit exceeded." |
|
PJ40244 |
Fix |
INXs processes hang while waiting on a lock for INXD as shown in
ipc_tool. |
|
PJ40260 |
Fix |
DOC_tool: Inserting an MSAR surface without a fully qualified path
name causes the dtp process to core. |
|
PJ40265 |
Fix |
The enlarge_ncol process aborts, reporting a 202,0,9 error. |
|
PJ40273 |
Fix |
Error tuple 121,1,12505 <fnsw> INXu - GDB_prepare failed=.
Cannot determine the number of f_new_dir* and f_old_dir*. |
|
PJ40281 |
Fix |
While processing Records Manager records on a CFS-IS system, a fatal
MKF Perm error occurs, which causes the Image Services server to stop
responding. |
|
PJ40295 |
Fix |
Error tuple 92,2,11 <fnsw> DOCs -
DOCl_CFS_get_annot_log_entries(line=624): INX_ce_get_object_store_id() failed during federation. |
|
PJ40351 |
Fix |
A trigger file must be created to allow the MS SQL isolation level to
be changed from read uncommit to read commit. |
|
NA |
Fix |
Windows: The ipc_tool -D command creates the memory dump file in ASCII
mode but not in binary mode. |
|
NA |
Enh |
Support for Refederation logging in content Federation Services for
Image Service (CFS-IS).. |
|
NA |
Enh |
Support for Microsoft SQL Server 2012. |
|
NA |
Enh |
Support for Red Hat Enterprise Linux (RHEL) 6.0 as a remote Oracle
database server. |
|
NA |
Enh |
Enhance the 911 tool to output an XML file with IBM product
information. |
|
4.1.2.14-IS-FP014 |
||
|
APAR |
Type |
Description |
|
PJ34003 |
Fix |
The MKF_tool avg option returns incorrect results when the number of
results is excessive. |
|
PJ39755 |
Fix |
The dbverify command displays inconsistent results for missing
documents. |
|
PJ39791 |
Fix |
SysV does not parse “ps -ef” properly due to an erroneous internal
buffer size. This causes processes to core. |
|
PJ39877 |
Fix |
The ds_init process aborts with the error message: 76,0,261 – ds_init
attempted to start too many background jobs. |
|
PJ40035 |
Fix |
Mismatching properties found between Image Servies documents and their
federated documents on Content Engine. |
|
NA |
Fix |
DOCs crash when federating annotations to Content Engine. |
|
NA |
Enh |
The “change getstamps -compare” option to verify the Image Services
binaries is now based on the cycle number, instead of the SCR number. |
|
4.1.2.13-IS-FP013 |
||
|
APAR |
Type |
Description |
|
PJ39447 |
Fix |
SDS_CSAR_reader attempts to retrieve documents when FNP_CLIPID is set
to Report Manager Record. |
|
PJ39482 |
Fix |
CSM should return a 92,2,11 error when it is encountered, rather than letting
commit return a 77,0,7. |
|
PJ39489 |
Fix |
The error '121,0,75', that occurs during a GDBD_logoff is changed to
INFORMATIONAL severity level. |
|
PJ39510 |
Fix |
The csml_update_durations process is slow when the same document id is
requested within seconds of each other. |
|
PJ39574 |
Fix |
Windows: SDS_CSAR_reader unable to retrieve NLS documents because the
doc id and SSN numbers are byte swapped. |
|
PJ39644 |
Fix |
Image Services processes core in lsi_find_by_surf_id on servers
configured with MSAR libraries. |
|
PJ39650 |
Fix |
Remote Procedure Call (RPC) definitions are missing from the eladisp
command. |
|
PJ39694 |
Fix |
Performing an EBR Restore process fails due to a missing BRORxxxxx.log
output file. |
|
PJ39713 |
Fix |
Windows: Image Services logs a 202,0,7 error during shutdown (No
Shared Memory Available). |
|
PJ39714 |
Fix |
Windows: MKF_setLongTransThreshold aborts. |
|
PJ39720 |
Fix |
The sds_update_retention process reports incorrect performance
statistics. |
|
PJ39728 |
Fix |
Windows 2008 64-bit: fn_snmpd does not function properly due to a
change in the registry. |
|
4.1.2.12-IS-FP012 |
|||
|
APAR |
Defect # |
Type |
Description |
|
PJ39073 |
894922 |
Fix |
When SDS_read_after_write is set, the software retries, but does not
perform a reconnect to Centera. |
|
PJ39080 |
962359 |
Fix |
Windows documents are not written correctly when using Adaptec
29320LPE and an UDO drive. |
|
PJ39110 |
962416 |
Fix |
CEMP: Annotations with security set to NONE cannot propagate to CFS.
NONE cannot be resolved in the SEC_MAP. |
|
PJ39132 |
960193 |
Fix |
No error is returned from CSMl when no document id is passed. Remote
Procedure call (RPC) is slow when no data is passed. |
|
PJ39224 |
966335 |
Fix |
Running EBR restore with the combination of thread count > 1 and
database count >1 causes the EBR process to crash. |
|
4.1.2.11-IS-FP011 |
|||
|
APAR |
Defect # |
Type |
Description |
|
PJ38570 |
943862 |
Fix |
The 911 tool fails to run on a Windows 2008 server that is running in
64-bit mode. |
|
PJ38585 |
944474 |
Fix |
The output from the stamp program displays incorrect information. |
|
PJ38589 |
944608 |
Fix |
The eladisp command does not display the client IP address correctly. |
|
PJ38610 |
945081 |
Fix |
MKF_tool cores when using the HARDCOPY option and the select statement
is longer than 239 characters. |
|
PJ38719 |
948319 |
Fix |
The “sgs -o” command does not show link information for the optical
drives or library. |
|
PJ38751 |
949341 |
Fix |
The doctaba_retent_update process reports an INX_update_DIR
error=0x5a00002e. |
|
PJ38758 |
949522 |
Fix |
When the destination surface is full, a '77,0,10' error is reported
during the doccopy process. |
|
PJ38801 |
950806 |
Fix |
Running sds_migr and sds only committal causes the system to lock up. |
|
PJ38868 |
952864 |
Fix |
MKF_ddl reports a 161,0,11017 error when adding a 17th permanent
database dataset. |
|
PJ38927 |
958271 |
Fix |
Enables the deletion of virtual EBR documents for iSDS committed docs. |
|
PJ38933 |
956641 |
Fix |
SDS_worker process cores inside MKF_update when reporting a 161,0,1076
error. |
|
PJ38941 |
956952 |
Fix |
Running the CEINFO command in DOC_tool causes DOC_tool to crash and
hangs the Image Services server. |
|
PJ39024 |
960192 |
Fix |
Windows shared memory addr_list file is incorrectly truncated. |
|
PJ39059 |
864763 |
Fix |
PEDl does not generate a new key pair after 30 days. |
|
4.1.2.10-IS-FP010 |
|||
|
APAR |
Defect # |
Type |
Description |
|
PJ38243 |
934251 |
Fix |
Error 77,0,11 dtp_tran does not handle cache objects when attempting
to update duration. |
|
PJ38314 |
937203 |
Fix |
Checksum errors are reported when retrieving a COLD document with
multiple table of contents pages. |
|
PJ38328 |
937640 |
Fix |
The dbverify -o command reports Integral SDS Only documents as missing
from the media. |
|
PJ38329 |
937719 |
Fix |
Image Services hangs on SEC interlock with “Not logged on to IMS
server” error. |
|
PJ38396 |
939057 |
Fix |
Security Services SEC entry points miss checks for input string
length, which can lead to stack corruption. |
|
PJ38403 |
938301 |
Fix |
If cache object is deleted or aged out during doccopy job, elog
message 77,0,10 incorrectly states that the job will resume after a system
restart. |
|
PJ38421 |
939665 |
Fix |
Image Services hangs when the current busy prefetch courier handles
reach at 75 shown in PPMOI. |
|
PJ38456 |
940626 |
Fix |
SDS_worker and SDS_CSAR_reader processes do not use the EMC SDK
environmental variables if they are set. |
|
PJ38534 |
942848 |
Fix |
Error 90,6,31 is reported in the Image Services elog when federating a large number of documents. |
|
PJ38561 |
943681 |
Fix |
Error 121,0,3 is reported on Image Services. PullWorker is causing
duplicate completed log entries to be returned to Image Services. |
|
4.1.2.9-IS-FP009 |
|||
|
APAR |
Defect # |
Type |
Description |
|
PJ37643 |
894922 |
Fix |
DOCs or SDS_worker process aborts due to CSM nil handle. |
|
PJ37984 |
914783 |
Fix |
HP Integrity hardware platform does not contain the SDS_CSAR_reader
program. |
|
PJ38006 |
916689 |
Fix |
The COR_Listen is aborted while performing an shm_search. |
|
PJ38042 |
920178 |
Fix |
The Image Services Centera library libSDSw_centera truncates the
repository string after 255 characters. |
|
PJ38112 |
925153 |
Fix |
Change COR to correctly report errno after an error is returned in the
Ocor_snd call. |
|
PJ38114 |
925203 |
Fix |
After Image Services is started, the SDS_FS_reader process reads all
sub-directories. Initial retrievals are very slow. |
|
PJ38226 |
932940 |
Fix |
Fastbatch break-up stores wrong checksum value for page-0 objects in
cache |
|
NA |
916013 |
Fix |
The 911 -m tool (move temp files to a specific directory) does not work
on Solaris. Cannot execute “grep -q” command on Solaris OS. |
|
NA |
922838 |
Enh |
Qualify Image Services 4.1.2.n with a remote DB2 9.8 pureScale
environment. |
|
4.1.2.8-IS-FP008 |
|||
|
APAR |
Defect # |
Type |
Description |
|
PJ37757 |
890360 |
Fix |
Improves SysV shared memory segment allocation on Windows. |
|
PJ37655 |
894914 |
Fix |
OSAR server returns numerous SAS [71,0,2] errors. |
|
PJ37773 |
901888 |
Fix |
The oddump tool does not output all of the
document headers once the size of the file size is 2 GB. Not all of the Doc Headers are output. |
|
PJ37785 |
903036 |
Fix |
The docfetch -s ?doc_id command
no longer waits for a response to RSVP message to insert a surface. |
|
PJ37807 |
903210 |
Fix |
SDS_worker process terminates when SnapLock device is set to read-only
mode. |
|
PJ37855 |
906748 |
Fix |
The sds_convert_nls command reports 90,0,46 errors on documents if the
document class indexes are modified after being archived by NLS. |
|
PJ37862 |
907250 |
Fix |
Using MKF_tool with a file does not return correct results for joined
tables. |
|
PJ37890 |
909794 |
Fix |
The fn_build utility truncates the SDS repository string in the as_conf.g file to 129 characters. |
|
PJ37951 |
907579 |
Fix |
The sds_copy command reports a checksum error 77,1,58 when processing
older NLS documents. |
|
PJ37956 |
912722 |
Fix |
Performance reports secdb_io, transdb_io and secdb_io show dashes
instead of data. |
|
PJ37971 |
913808 |
Fix |
When an existing network connrection is broken due to a network error,
SAS waits 30 seconds before starting a new connection. |
|
PJ NA |
912469 |
Fix |
Windows Centera SDS_workers and SDS_CSAR_readers die with EMC Centera
SDK 3.2 patch 5 libraries. |
|
NA |
862995 |
Enh |
Qualifies support for Oracle 11g R2. |
|
NA |
899020 |
Enh |
Enhances the 911 script to cleanup temporary files (*.wri). |
|
NA |
904966 |
Enh |
Provides currency support for ECM 3.2 Patch 5. |
|
4.1.2.7-IS-FP007 |
|||
|
APAR |
Defect # |
Type |
Description |
|
PJ37307 |
861133 |
Fix |
EBR offline backup does not remove Oracle Archive Logs after upgrading
to IS 4.1.2. |
|
PJ37329 |
861942 |
Fix |
DOCs reports unknown type (57) followed by a
corrupt shared memory. |
|
PJ37337 |
862318 |
Fix |
CFS-IS property updates are failing with 90,6,31 errors with Multiple
Object Stores. |
|
PJ37396 |
864262 |
Fix |
Numerous 92,2,11 errors written to Image Services error log - INX_get_single_DIR
- user is not logged on. |
|
PJ37398 |
861448 |
Fix |
For FN-controlled Oracle, fn_util updaterdb does not execute the
necessary Oracle commands to extend SYSAUX after the changes are made in
fn_edit. |
|
PJ37435 |
864750 |
Fix |
Shared memory pre-allocation does not work if IS Services is
configured to start. |
|
PJ37436 |
865233 |
Fix |
Xupretent changes the F_ENTRYDATE of documents to a random date when
no date is entered. |
|
PJ37470 |
866204 |
Fix |
IDMWS communicating with Solaris 10 IS 4.1.2 FP4 gets 155,210,219 with
heavier load. |
|
PJ37578 |
891818 |
Fix |
In dbupgrade - fn_util mlb_mig_sec_cols does
not populate the new f_accessrights_rw, _wr and _ax fields. |
|
PJ37680 |
895623 |
Fix |
Cormon displays invalid data when 3rd party port scan software
monitors Image Services ports. |
|
PJ37556 |
891163 |
Fix |
Error 21,1,1455 occurs on dbupgrade -m -Q when the document id is
greater than (>) 2,147,483,647. |
|
NA |
794474 |
Enh |
GDB_exim: Adds support for SEQUENCES for DB2 and Oracle databases. |
|
NA |
895404 |
Enh |
Includes Software Group (SWG) Inventory Tags. |
|
4.1.2.6-IS-FP006 |
|||
|
APAR |
Defect # |
Type |
Description |
|
PJ36605 |
835958 |
Fix |
Extended Membership reports cannot be viewed. |
|
PJ36750 |
820449 |
Fix |
When setting the Date/Time field, Daylight Savings Time (DST) pre-2007
rules are not respected on Windows platforms after DST starts one hour
earlier. |
|
PJ36823 |
843681 |
Fix |
The "Xdbconnect" utility does not function in a clustered
environment. |
|
PJ36876 |
845759 |
Fix |
The csm_breakup_object process found a duplicate object in cache: data
mismatch for page 0 when fast batch breakup is on running NLS Archive. |
|
PJ36923 |
847314 |
Fix |
ISDS reports an incorrect file system space available on the SSAR file
system. |
|
PJ36984 |
849436 |
Fix |
CSM_tool: The "largest_fs_blks" in cache is always displayed
as 4204079050. |
|
PJ37043 |
851245 |
Fix |
Optical Libraries are still reserved after a cluster failover. |
|
PJ37044 |
851461 |
Fix |
You cannot perform a TSM trace on the SDS_worker process. |
|
PJ37052 |
850352 |
Fix |
Errors 156,0,0 and 156,0,29 occur when running the ddtsimp tool on AIX
5.3 IS 4.1.2 Fix Pack IS-4.1.2-FP003. |
|
PJ37127 |
854636 |
Fix |
Image Services 4.1.1 requires page 0 to be migrated to cache. |
|
PJ37141 |
852423 |
Fix |
Inaccurate warning messages occur in the courier. |
|
PJ37185 |
856665 |
Fix |
An upgrade from Image Services 4.0 to Image Services 4.1.1 FP9 EBR
offline backup of FileNet Controlled Oracle fails with a 222,0,13002 error. |
|
PJ37242 |
858102 |
Fix |
The ixdb_stat program fails to load on the HP Itanium platform –
Unsatisfied code symbol SEC_init_V in load. |
|
PJ37279 |
859709 |
Fix |
Xdbconnect does not accept special characters for the password. |
|
NA |
794447 |
Fix |
The sds_update_retention process can be run on a secondary storage
server: the Object is updated, but the docs table is
not. |
|
NA |
845720 |
Fix |
An Enterprise Backup and Restore (EBR) backup generates a 222,0,1005
error. |
|
NA |
847057 |
Fix |
A fastbatch breakup error can be transferred to the next fastbatch. |
|
NA |
847622 |
Fix |
A fastbatch breakup can error with too many documents at half the
batch maximum. |
|
NA |
847918 |
Fix |
The sds_convert_nls process does not check if a document has already
been written using sds_migr or sds_copy. |
|
NA |
848367 |
Fix |
INX: Fails to compare 40 bytes of guid because of uninitialized data. |
|
NA |
848402 |
Fix |
The 911 utility has been modified; the command looks for core files
starting in the /fnsw directory. |
|
NA |
849591 |
Fix |
Trigger files for dbupgrade are not being detected on Windows
platforms. |
|
NA |
849599 |
Fix |
The fn_util tool has been modified to support Enhanced Document
Security. |
|
NA |
849603 |
Fix |
Interrupting the migration process generates errors in the elogs. |
|
NA |
851740 |
Fix |
The \fnsw\etc\broadcast.exe program does not have stamp information. |
|
NA |
852977 |
Fix |
HPII and IM Utility programs are hanging on an IMS_get_version call on
a Solaris 10 server. |
|
NA |
853250 |
Fix |
Multiple Storage Server cache only systems status_1 was not being set
to unmigrated when used with non-SDS family. |
|
NA |
853627 |
Fix |
An Enterprise Backup and Restore (EBR) backup of a large (200 GB)
site-owned Oracle database fails with a <222,0,13043> error. |
|
NA |
854106 |
Fix |
You cannot perform a TSM trace on the SDS_worker process on Windows. |
|
NA |
855821 |
Fix |
The docfetch -s command returns an invalid checksum error for FBC/FBB
documents written to a second storage server. |
|
NA |
856944 |
Fix |
Interrupting the migration process generates errors in the elogs.
Continuation of DR 849603. |
|
NA |
857806 |
Fix |
SDS_fbc_breakup: Deleting documents from Image Services before they
write to ISDS device leaves documents locked in cache and errors on ISDS
commit. |
|
NA |
857928 |
Fix |
The PPMOI program terminates with a segmentation violation error. |
|
NA |
860550 |
Fix |
DOC_find_documents_w_sds entry point returns incorrect values for the
“sds_id” field. |
|
NA |
861093 |
Fix |
ISDS Centera retry does not working properly when opening a
repository. The retry passes a handle not set to '0'. Error 238,3,19 should
not be returned. |
|
NA |
813379 |
Enh |
The sds_migr utility does not update the SDSMigrDocs.nnn log correctly
when Image Services is recycled. |
|
NA |
826528 |
Enh |
Provides support for IIA (IBM Information Archive) through the
existing TSM interface. |
|
NA |
844761 |
Enh |
Updates docfetch with signal handling per coding standards. |
|
NA |
846271 |
Enh |
Currency support for EMC 3.2 Patch 4. |
|
NA |
851499 |
Enh |
Provides a tool called netcheck that uses getaddrinfo()
to resolve host names and determines whether it is considered a local
address. |
|
NA |
851969 |
Enh |
Updates the DOC_tool with signal handling per coding standards. |
|
NA |
855329 |
Enh |
Provides simplified Image Services HA clustering configuration by
dropping the existing requirement to re-configure hosts files or a DNS
server. |
|
4.1.2.5-IS-FP005 |
|||
|
APAR |
Defect # |
Type |
Description |
|
PJ36146 |
800645 |
Fix |
ISDS needs additional retries when Repository operations (SDSw) fail.
This will be based on error code return values from the SDSw layer. |
|
PJ36515 |
830905 |
Fix |
Core dump running docfetch -s -f filelist - when
the filelist contains over 20,000 document ids. |
|
PJ36566 |
835925 |
Fix |
Image Services and Process Engine installing on AIX with a host name
greater than 31 characters causes a mismatch of uname and gethostname ( ), causing initfnsw start to fail. |
|
PJ36609 |
837206 |
Fix |
The filenet.podf file is created as a folder instead of a file. |
|
PJ36621 |
838340 |
Fix |
DOCs and INXs abort/segmentation violation with 71 ,0,2 SAS_open:area_type mismatch errors. |
|
PJ36632 |
838957 |
Fix |
Only documents with doc_ID > 100096 are imported with sds_import
from an SDSw_snaplock device. |
|
PJ36714 |
838470 |
Fix |
Fast Batch committal to ISDS errors on cache-only server without
SDS_fbc_breakup trigger file and without the sds_only configured. |
|
PJ36715 |
839692 |
Fix |
The sds_update_retention of snaplock docs created in past with f_deletedate
of today or past does not work. |
|
PJ36398 |
814925 |
Fix |
The 911 program should not perform a UNIX list command (ls) on the cdb
files when they do not exist on an OSAR or application server. |
|
PJ36781 |
842796 |
Fix |
OSAR server receiving error nch_check -q 15 ,16 ,
17 after restarting both the Root/Index and OSAR server. |
|
PJ36886 |
846374 |
Fix |
Unable to delete document from SnapLock device on a Windows server. |
|
PJ36952 |
848178 |
Fix |
PPM does not clean up properly on terminating server stubs. |
|
NA |
828819 |
Fix |
Unable to start Image Services on the first installed node in a two
node Process Engine Veritas Cluster. |
|
NA |
843085 |
Fix |
Xapex Storage Library Control window creates segmentation violation
when clicking on Info button for ISDS retry error 238 ,3,1. |
|
NA |
843115 |
Fix |
ISDS Retry: Objects remain locked in cache after 16 retries. Multiple
attempts to create more documents result in a CSM error. |
|
NA |
843128 |
Fix |
After Image Services 4.1.2 FP2 or higher is applied to a Windows
server with MSSQL remote database, the software will not start. |
|
NA |
843626 |
Fix |
ISDS Retry: SFBB objects do not write successfully to ISDS device when
ISDS device is in retry error state. |
|
NA |
844068 |
Fix |
ISDS retry on Sun with fast batch continually issues Xslc RSVPs, but doesn't write docs after at least 30 RSVP
responses. |
|
NA |
844948 |
Fix |
ISDS retry code causes endless disabling of SDS unit on Windows FBC
with SDS_read_after_write. |
|
NA |
845467 |
Fix |
SDS_worker cores using ISDS retry when committing FBC on Windows only
with retry environment variables set. |
|
NA |
845472 |
Fix |
SDS_worker gets into endless ISDS retry Xslc RSVP loop on Windows only
when FBC commit to HCAP and ISDS retry environment variables are set. |
|
NA |
845917 |
Fix |
ISDS writing to HCAP with ISDS retry variables writes random oddball
docs to device. |
|
NA |
847054 |
Fix |
FNPoll won't run and gives errors on HP Integrity with 11iV3. |
|
NA |
848400 |
Fix |
Thousands of 88 byte COR shared memory segments are
created when IS is started. |
|
NA |
838159 |
Enh |
Update MKF_tool with signal handling per coding standards. |
|
NA |
846446 |
Enh |
QMA uses an increasing number of interlocks. |
|
NA |
846622 |
Enh |
Need more information about interlocks from tools. |
|
NA |
846731 |
Enh |
Modify 911 script to handle compressed core files and additional core
file directory. |
|
NA |
847175 |
Enh |
Allows Courier II worker thread stack size to be configurable (AIX
only). |
|
4.1.2.4-IS-FP004 |
|||
|
APAR |
Defect # |
Type |
Description |
|
PJ35988 |
791993 |
Fix |
Error 43 ,0,2005 locks up Storage Library Control. |
|
PJ36145 |
799263 |
Fix |
System hangs after running getreports. |
|
PJ36159 |
798054 |
Fix |
fn_db2 shared memory errors occur during shutdown after installing
Image Services 4.0 SP5 FP13. |
|
PJ36188 |
760759 |
Fix |
SDS_worker logs checksum errors when retrieving COLD docs with TOC
pages from Centera |
|
PJ36191 |
797192 |
Fix |
Performance issue after migrating IS 3.6 Oracle to Image Services 4.0
SP5 DB2. |
|
PJ36236 |
816586 |
Fix |
Error 156,0,25 - NCHl_RetrieveAddresses NCHl_RetrieveAddresses should
never be called. |
|
PJ36288 |
786981 |
Fix |
Annotation Only export from IS RAC always performs full re-export,
even when “re-export” is not selected by user. |
|
PJ36384 |
822500 |
Fix |
The ipc_tool -I command shows "no process name" for last
claimer process. |
|
PJ36416 |
825040 |
Fix |
ERROR; stats field changed (0x44056 ! =
0x144056) (comparison errors) occur with perf_report -a and -rful with IS
4.1.2. |
|
PJ36433 |
826011 |
Fix |
The DOC_tool utility failed to get document information from an ECM
Centera device using a large document id (2147483647). |
|
PJ36435 |
826170 |
Fix |
SDS_update_retention is taking too long to update docs in large pool
of Centera device. |
|
PJ36483 |
831070 |
Fix |
SDS_migr: SDS_worker processes hang waiting on RSVP msg if MSAR
surface has been deleted. |
|
PJ36516 |
832823 |
Fix |
SDS_worker cores when receiving an error message from the ECM SDK
library over 1K. |
|
PJ36571 |
790738 |
Fix |
Process Engine and Image Services: Cannot finish the installation of
Process Engine 4.5 on AIX 6.1: inst_templates fails
with sed error. |
|
NA |
791582 |
Fix |
PE/Image Services: cfg_verify checked the swap space incorrectly
against HP-UX B.11.23 system. |
|
NA |
813221 |
Fix |
Process Engine processes crash after stopping the Process Engine
service on Process Task Manager due to killfnsw guard-file error. |
|
NA |
817713 |
Fix |
Process Engine installation program does not start IMS ControlService
and returns false positive of service initialization (Windows only). |
|
NA |
818940 |
Fix |
Process Engine and Image Services: AIX server on a pure IPv6 network
has syslog messages that are unclear and too frequent. |
|
NA |
825677 |
Fix |
Shared memory errors when running killfnsw -SDAy after running
initfnsw -y stop on Solaris 10 server. |
|
NA |
826191 |
Fix |
Process Engine and Image Services: Process Engine 51.029 fresh
installation on Windows 2008 64 bit: Running "initfnsw -y restart"
after fresh installation failed. |
|
NA |
828819 |
Fix |
Process Engine and Image Services: Unable to start Image Services on
first installed node in a two node PE Veritas Cluster. |
|
NA |
834122 |
Fix |
Multiple dtp_tran processes errors with DT_doc_loc_select with fast
batch five batches of 100 small images, many indexes and 64K DIR buffer. |
|
NA |
785127 |
Enh |
Provide Integral SDS Migration tool to synchronize DoctabA and DCL
retention settings. |
|
NA |
788965 |
Enh |
ISDS breakup before SDS write option. |
|
NA |
799273 |
Enh |
Currency support for Tivoli 6.1. |
|
NA |
800980 |
Enh |
Provide BPM with Image Services 4.1.2 FP3 mini-installer. |
|
NA |
825797 |
Enh |
Image Services does not log the source IP address when the deprecated
NCHl_RetrieveAddresses API is called. |
|
NA |
832470 |
Enh |
Replaced the sys_log semaphore with a spinlock timeout that prevents
any process from hanging while trying to write to the elog file. |
|
4.1.2.3-IS-FP003 |
|||
|
APAR |
Defect # |
Type |
Description |
|
PJ35029 |
783671 |
Fix |
PE/IS: mini-installer fn_IS_has_rdb_password errors are hard to
diagnose. |
|
PJ35458 |
771018 |
Fix |
The perf_report –a command generates a segmentation violation after
installing SCR 325091. |
|
PJ35578 |
786206 |
Fix |
ISDS: fn-edit default retention date >= 2038-01-06 for
enabled_with_default_offset cores on IS. |
|
PJ35611 |
792816 |
Fix |
SDS_worker process logs 80 ,0,8 , 80,0,57 and
192,2,108 errors when migrating documents to an SDS device. |
|
PJ35656 |
792952 |
Fix |
Incorrect data is placed in the export_log when updating a DIR record. |
|
PJ35668 |
793837 |
Fix |
Closing a telnet session while running CSM_tool generates a 202
,0,1045 error and holds on to an interlock. |
|
PJ35705 |
785301 |
Fix |
SDS_FS_reader fails when SDS_tool recover rewrites to a new
surface_id_1, causing the SDS_FS_reader to look in the wrong File System
Directory path. |
|
PJ35804 |
796341 |
Fix |
Documents committed to ISDS or updated with an f_deletedate > 2038
are not updated in DOCS or on the ISDS device. |
|
PJ35811 |
663796 |
Fix |
Server Attributes tab in fn_edit: the platform dialog box should be
widened to accommodate entire "Windows Server" text. |
|
PJ35819 |
795625 |
Fix |
SDS_worker reports an error - sds fbc : Bad
read length when trying to read page info. |
|
PJ36004 |
801249 |
Fix |
After installing IS 4.1.1.5-FP005, you cannot run perf_report. |
|
PJ36019 |
800866 |
Fix |
The bkg_sds process is not updating objects on EBR supported ISDS
devices that are EBR and then triggered with an f_deletedate value set to one
or two days from the creation date or with a past value. |
|
PJ36055 |
801456 |
Fix |
Running the osschk tool returns an error - if: Badly formed
number, while running the application. |
|
PJ36071 |
801845 |
Fix |
ISTK: The fn_rel tool does not run on HP-UX. No error message is
returned for tuple <212,3,11>. |
|
PJ36103 |
803481 |
Fix |
ISDS read after write with regular committal is updating docs table
with sds info when compare fails. |
|
PJ36122 |
803398 |
Fix |
When perf_report –a –csv is run, the total column for All RPCs in the
Cumulative Service Activity Report contains garbage. |
|
PJ36144 |
794352 |
Fix |
<MKF_import init> throwing exception during the MKF_fixup phase. |
|
PJ36150 |
785167 |
Fix |
Plasmon UDO sense data in misinterpreted as a dirty drive. |
|
PJ36158 |
801367 |
Fix |
Multiple entries are returned in the elogs of 138,0,38 for some
optical surfaces. |
|
PJ36177 |
811236 |
Fix |
IPv4 server is receiving an error return from TPI_SendPEPreq2 from an
IPv6 client and returns an IPv6 address to an IPv4 server. |
|
PJ36184 |
379308 |
Fix |
Generic: MKF_fixup does not fix corrupted data in an index page block. |
|
PJ36193 |
814002 |
Fix |
In fn_edit, the Maximum document buffer count is 128 and maximum
directory buffer count is 64. |
|
PJ36198 |
813906 |
Fix |
The sds_copy usage statement now informs users that it can use NLS/SDS
unit as a source only if those documents have had sds_convert_nls run on
them. |
|
PJ36203 |
794095 |
Fix |
On HP-UX systems, the Process Engine mini-installer overwrites the
system default PATH variable. CE 4.5 client installation program requires
gzip to be in the path and the system default path includes /usr/contrib./bin
that contains gzip. |
|
PJ36205 |
798472 |
Fix |
The UNIX mini-installer log file will log “fn_pso_convert: not found”
if /fnsw/bin is not specified in the PATH before installing Process Engine. |
|
PJ36251 |
815226 |
Fix |
Spelling error during fn_setup_rdb -f. |
|
PJ36252 |
815951 |
Fix |
COSM: Applications Executive: An incorrect format appears when
selecting Cache Export/Import. |
|
PJ36256 |
800168 |
Fix |
P8 System Manager Listener fails on Image Services. |
|
PJ36272 |
816290 |
Fix |
Configuration Editor: A string is truncated in the MSAR Storage
Library dialog. |
|
NA |
789676 |
Fix |
With UNIX, the Process Engine installation program hangs when an IS
mini-installer upgrade fails with an fn_IS_has_rdb_password error. |
|
NA |
803481 |
Fix |
ISDS read after write with regular committal is updating docs table
with SDS information when compare fails. |
|
NA |
761105 |
Enh |
Network activity is now available in P8 System Manager through
Microsoft Windows Performance Monitor (perfmon). |
|
NA |
772757 |
Enh |
Modifies fn_setup_rdb to support SQL 2005 32-bit on Windows 2008
64-bit O/S. |
|
NA |
780789 |
Enh |
Moves COLD message strings from the header file to the URL file. |
|
NA |
784188 |
Enh |
Support Integral SDS – Centera on Itanium. |
|
NA |
784193 |
Enh |
Implements a Read after Write feature for Integral SDS. |
|
NA |
784309 |
Enh |
Adds support for SQL Server 2008. |
|
NA |
793656 |
Enh |
PE/IS: Provides IPv6 support for a mini-installer. |
|
NA |
794160 |
Enh |
Provides Image Service code changes to improve the consumability of
the Process Engine product. Changes allow the IS mini-installer to reduce its
payload, thus occupying less disk space, and also
reduces installation time for BPM. |
|
NA |
797164 |
Enh |
Creates a tool named sds_copy_to_surf to copy documents from an SDS
device to an MSAR/OSAR surface. |
|
NA |
799272 |
Enh |
Provides currency support for EMC 3.2 Patch 3. |
|
NA |
800980 |
Enh |
Provides BPM with an IS 4.1.2 FP4 mini-installer. |
|
NA |
811306 |
Enh |
PE/IS NCH optimization for local service. |
|
NA |
811495 |
Enh |
Provides support for BPM consumability requirements with internal
security changes. |
|
NA |
811560 |
Enh |
Provides BPM consumability requirements support with changes to the
background daemon startup. |
|
NA |
811818 |
Enh |
Modifies the perf_mon to link SEC only when necessary (for Image
Services). |
|
NA |
812379 |
Enh |
Provides changes in the perflog format. When the Image Services
software is started, perf_mon will automatically create a new perflog with
the new internal format. |
|
4.1.2.2-IS-FP002 |
|||
|
APAR |
Defect # |
Type |
Description |
|
|
792449 |
Fix |
CSM_tool: New option delage docid MB <count> or delage MB
<count> accepts negative and/or garbage numbers. |
|
|
787257 |
Fix |
The wal_dbcheck_cemp test program is reporting [INFO] for each thread. |
|
PJ34865 |
782613 |
Fix |
VW stub processes failed to invoke sysv exception handler. |
|
PJ34873 |
755331 |
Fix |
Image Services does not stop sometimes for backup mode. |
|
PJ35093 |
783546 |
Fix |
ISDS: sds_update_retention does not handle docs closed in IDM Desktop
with months >= 351. |
|
PJ35115 |
782865 |
Fix |
Process Engine 450 – Database does not throw error when the actual
blob tablespace name does not match the one in the VWRDBObject table/CDB
file. |
|
PJ35178 |
782063 |
Fix |
TRUNC: Xapex: There is truncated text within COLD app on Windows 2003
server. |
|
PJ35196 |
785642 |
Fix |
Selecting List button immediately after Define/Update Doc Class screen
launched results in 90,0,2 errors. |
|
PJ35328 |
785519 |
Fix |
Problem using Centera Embedded BLOB option when migrating documents
from MSAR to Centera |
|
PJ35338 |
787375 |
Fix |
The sds_convert_nls background tool excludes CLOSED (DOCTABA)
documents when using a document range. |
|
PJ35376 |
788960 |
Fix |
Resizing a window with cormon running causes corruption of the
displayed data. Cormon data display does not dynamically adjust to window
size. |
|
PJ35377 |
374824 |
Fix |
DOC_tool – SDSinfo info message needs to be improved when SDS readers
are not configured. |
|
PJ35390 |
780027 |
Fix |
GLOB: CHAR: Xapex/fn_edit/etc: There are some characters which can’t
display well on JP Windows 2003 server. |
|
PJ35456 |
790500 |
Fix |
The docfetch tool gives errors when running on a non-storage server. |
|
PJ35458 |
771018 |
Fix |
The perf_report –a command generates a segmentation violation after
installing SCR 325091. |
|
PJ35459 |
786390 |
Fix |
TRANS: Security Administration: Unlocalize in Add User Message DE
& FR. |
|
PJ35507 |
788509 |
Fix |
SDS migration hangs on specific documents with <61,0,10>. |
|
PJ35508 |
790456 |
Fix |
ER: New options added to CSM_tool > delage command to resolve cache
full (77,0,8) issue when processing Fast Batch objects. |
|
PJ35518 |
788995 |
Fix |
ISDS is not correctly protecting DR550 EBR documents. |
|
PJ35520 |
790455 |
Fix |
DOC stub crashes intermittently while locking SEC DB, system halts. |
|
PJ35553 |
786397 |
Fix |
TRANS: COLD: Preview Documents: Unlocalize in the message box DE &
FR. |
|
PJ35554 |
786395 |
Fix |
TRANS: Storage Library: Statistics: Unlocalize in the Message Box. |
|
PJ35556 |
791704 |
Fix |
The sds_update_retention process on centera chrono doc creates a new
clip with a shortened retention when f_deletedate has not changed. |
|
PJ35578 |
786206 |
Fix |
ISDS: fn_edit default retention date >= 2038-01-06 for
enabled_with_default_offset cores on IS. |
|
PJ35612 |
379614 |
Fix |
Generic: Groups outside of the administration domain will be listed
when logging in with administrator with ADMIN GROUP=none. |
|
PJ35712 |
792955 |
Fix |
PSI : PSI test for OC 4.0.2 patch3 on IS 4.1.2 is failing. |
|
PJ35768 |
784276 |
Fix |
Surface Activity tracking logs too many writes. |
|
PJ35811 |
663796 |
Fix |
Server Attributes tab in fn_edit: The platform dialog box should be
widened to accommodate the entire “Windows Server” text. |
|
PJ35812 |
381643 |
Fix |
SEC: Limitation on logon time (Minute) is invalid for time ahead. |
|
NA |
757961 |
Enh |
ER: The Archive options should be removed from the Background Job
Control menu. |
|
NA |
758600 |
Enh |
ER: After setting “Maximum Concurrent Logons Per User” to 1, there
will be problems logging on after restarting the client computer. |
|
NA |
767062 |
Enh |
ER: Integral SDS: Attempt to embed documents into Centera blobs when
possible. |
|
NA |
782835 |
Enh |
ER: New option –v for docfetch tool. |
|
NA |
784309 |
Enh |
ER: Add support for SQL Server 2008. |
|
NA |
787925 |
Enh |
ER: Mini-installer support for BPM with IS 4.1.2 FP1. |
|
NA |
790912 |
Enh |
ER: New options added to CSM_tool > stat command to monitor number
of free space by size. |
|
NA |
791057 |
Enh |
ER: The Archive options should be removed from the Background Job
Control menu online help and System Administration Handbook. |
|
NA |
791270 |
Enh |
ER: 911 enhancements – Add the sgs-s and CSM_tool > stat free
commands to the 911 output. |
|
NA |
792178 |
Enh |
ER: Additional improvements on Courier II. |
|
NA |
793212 |
Enh |
ER: Support for SNMP v3 |
|
4.1.2.1-IS-FP001 |
|||
|
APAR |
Defect # |
Type |
Description |
|
PJ34437 |
771753 |
Fix |
NCH_daemon reports a “Critical” error for a TPI_GetPEPReq. |
|
PJ34581 |
775914 |
Fix |
The stdoccpy tool causes <77,1,36> errors on some documents due
to zero (0) page length. |
|
PJ34836 |
783744 |
Fix |
PE/IS: Upgrade to IS 4.1.1 fails with fn_is_has_rdb_password error
when MSSQL client software is not installed. |
|
PJ34888 |
784009 |
Fix |
TRUNC: Xtaskman: There is an area truncated in the Status window. |
|
PJ34889 |
780024 |
Fix |
TRUNC: Xapex: There are some areas truncated on JP Windows 2003
server. |
|
PJ34899 |
783523 |
Fix |
Error 161,1,1004 - SAT_update failed. |
|
PJ34902 |
782580 |
Fix |
TRANS: Security Administration: Unlocalize and truncation in database
logons. |
|
PJ34920 |
784574 |
Fix |
Unable to print SDS documents when all pages are not in cache –
58,0,1006. |
|
PJ34976 |
785088 |
Fix |
Cross System Committal pus errors in elog, will fail to migrate to an
SDS device. |
|
PJ35009 |
785383 |
Fix |
A syslog can appear for a retryable MKF error. This shouldn’t occur. |
|
PJ35029 |
783761 |
Fix |
PE/IS: mini-installer fn_IS_has_rdb_password errors are hard to
diagnose. |
|
PJ35080 |
779785 |
Fix |
92,2,8 error is generated when attempting to view security user
details via Xapex Security Administration. |
|
PJ35086 |
776680 |
Fix |
The fn_snmpd tool returns wrong date errors and smux_init: systemError
on AIX. |
|
PJ35091 |
663322 |
Fix |
Extensible Authentication – error message truncated when validation
fails customer authentication. |
|
PJ35093 |
783546 |
Fix |
ISDS: sds_update_retention does not handle docs closed in IDM Desktop
with months >= 351. |
|
PJ35112 |
784884 |
Fix |
QMA abstract logs excessive QMA_wait info syslog entries during
initfnsw startup time. |
|
PJ35115 |
782865 |
Fix |
Process Engine 450 – Database does not throw error when the actual
blob tablespace name does not match the one in the VWRDBObject table/CDB
file. |
|
PJ35149 |
770361 |
Fix |
Running CPT_test with a –c parameter higher than 23813 causes CPT_test
to hang. |
|
PJ35169 |
786376 |
Fix |
Windows XP client PCs cannot log onto Unix Image Services servers when
IPv6 is enabled. |
|
PJ35200 |
768283 |
Fix |
The serverConfig file has an invalid “queue connection size”
parameter. |
|
PJ35267 |
788079 |
Fix |
Client PCs hang while waiting for PED stubs from IS server. |
|
PJ35333 |
784098 |
Fix |
The fn_build –a command cannot update verify.txt file because it is
being used by other process. |
|
PJ35371 |
785729 |
Fix |
The fn_edit configuration editor crashed from the OSAR server (new
installation) and generated a Dr. Watson report when an invalid
(non-existent) domain name was entered. |
|
PJ35383 |
768994 |
Fix |
Investigate and correct SEC_get_message holding of SEC interlock
across ERM calls. |
|
PJ35385 |
783103 |
Fix |
Segmentation violation when sys_log *** with asterix ** can occur. |
|
PJ35387 |
781000 |
Fix |
The SysV.dll file cannot be overwritten on Windows. The module appears
to be mapped/locked. Cannot perform Image Services upgrade to 4.1 SP1 FP4. |
|
PJ35388 |
783739 |
Fix |
The nch_tool listprop of Bes objects shows improperly structured
address list. |
|
NA |
749868 |
Enh |
ER: Image Services to support IPv6 network addresses. |
|
NA |
750268 |
Enh |
The sgs tool needs the capability to list Integral SDS units
configured. |
|
NA |
783178 |
Enh |
PE/IS: During an upgrade of P8PE-4.3.0 to P8PE-4.5.0 with DB2 9.5 on
HP-UX 11.23: The libdb2.sl link points to /fnsw/lib/shobj/db2lib/libdb2.so
instead of libdb2.sl. |
|
NA |
783373 |
Enh |
ER: Post-qual support of DB2 v9.5 client with Image Services 4.1.1. |
|
NA |
784346 |
Enh |
ER: Provide installation support for Image Services 4.1.2 FP. |
|
NA |
785322 |
Enh |
ER: fn_setup_rdb.cmd terminated abnormally with File not found -
FN_SETUP_RDB.REG on 64-bit Windows. |
|
NA |
787925 |
Enh |
ER: Mini-installer support for BPM with Image Services 4.1.2 FP1. |
Files changed in
this fix pack
The manifest files for each platform list checksum information for each
file included in the fix pack.
·
is_4.1.2-FP26_aix_manifest.wri
·
is_4.1.2-FP26_hp_manifest.wri
·
is_4.1.2-FP26_hpintegrity_manifest.wri
·
is_4.1.2-FP26_sun_manifest.wri
·
is_4.1.2-FP26_win_manifest.wri
Accessing IBM
FileNet Image Services documentation
To access documentation and compatibility matrixes for FileNet Image
Services:
1. Go to the Product Documentation for FileNet Image Services support page.
2. Select a PDF or a Doc
Link, whichever is appropriate.
Contacting IBM
customer support
For information about contacting IBM customer support:
1. Go to the IBM Support home page.
2. On the Support home
page, click Sign in to access your
authorized content and to customize your pages.
The Support home page contains a wide
variety of options:
·
Check the "Featured links" and "Flashes and alerts"
for possible solutions.
·
Expand the "Support resources" menu for links to many tools
and references.
·
Expand the "Contact support" menu and select Directory of worldwide
contacts. Click the link for your country to view the contact information.
Notices
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, FileNet, 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.
Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.
Microsoft, Windows, Windows NT, 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 |
|
18 February 2020 |
Updated the following sections: ·
New in this fix ·
Software
requirements in Installation, migration, upgrade, and
configuration |
|
30 March 2019 |
Initial release of this fix pack |