Known Issues with ISA 1.50


  1. General Issues
  2. Windows Issues
  3. Java-Enabled Features Issues
  4. Migration Issues


The Problem Tracking System (PTS) number appears in parentheses at the end of each issue description.

1. General Issues

High-Availability Data Replication (HDR):
The following are known issues with HDR (Configuration->Replication):

Index by Utility->onstat->-B:
Selecting -B (All buffers) can create a very large file which uses all the available memory and can cause the browser (both Internet Explorer and Netscape) to crash. (148475)

Linux:
The ps system command output does not conform to the usual format on all other platforms. Therefore, when using ISA to drill down to a user's process ID, the values shown might not be correct. (116862)

Nework Connection Error:
During ISA installation, the ISA installer prompts you for up to two port numbers (for the ISA HTTP server and the ISA servlet engine). If the port numbers you select are not listed in the /etc/services file, the ISA installer tests each port to determine if it is in use.

If the port number is currently in use by a program, such as the database server or a client, when the ISA installer performs this test, the program might report a network connection error. For example, the database server reports an error like the following in the online message log (or in the ISA Summary page):

16:16:21  listener-thread: err = -25582: oserr = 9: errstr = : Network
connection is broken.
 System error = 9.
You can safely ignore this error. (150688)

SQL->Schema:
If a database table name contains an "&" character, the SQL->Schema page does not correctly display the schema of the table. (120830)

Storage->FAQ:
The following are known issues with Storage->FAQ:

Storage->Spaces:
Creating a large space might take a long time and cause the browser to time out. (121005)

XPS 8.30:
The onmode -z command does not kill a dbaccess session against an XPS 8.30 database server.
This is a known XPS dbaccess bug. (116733)


2. Windows Issues

CSDK Installation:
If you install IBM Informix Client Software Development Kit (CSDK) after installing IBM Informix Dynamic Server with J/Foundation, you might experience problems, such as the following, with ISA that did not occur before installing CSDK:

If you experience problems such as these, verify that the Apache service runs as user informix. To do this, follow step 5 in the section "4. Installing ISA for the First Time". Verify that the user is informix and reenter the password. If the Apache service is already started, click Stop before clicking Start in step 5i.

HDR:
Setting up HDR on Windows NT using the hosts.equiv file results in the following error:
-956 Host or user name is not trusted
HDR on Windows NT requires trusted host access between systems. One method for setting up trusted host access is to place a hosts.equiv file in the %WINNT%\system32\drivers\etc directory.

If your Windows NT system is set up to hide familiar extensions, make sure that the filename is hosts.equiv and not hosts.equiv.txt.

Internet Information Server:
If you use Internet Information Server as the HTTP server, running ON-Bar, dbimport, and dbexport might take a long time and cause the browser to time out. (127043)

Migration:
The default value for the LOGFILE on the Job Details page and Log File Path on the Run Job page is in UNIX format (/<path>/<jobname>.log). To fix this problem before you run the job, from the Job Details page, either: (132996)

Netscape 4.7x:
If you use Netscape 4.7x on the same Windows system on which the ISA Apache HTTP server is installed, you might experience a problem with long waits. To avoid this problem, set the focus by clicking some part of the browser window. (149951)

Port Number Detection:
The ISA installer cannot detect if the port number you select (for the ISA HTTP server or the ISA servlet engine) is already in use by another application. ISA will not function correctly if the port you choose is in use by another application. (120873).

Server Setup:
Before running Server Setup on a Windows system, you must use the Instance Manager to create the new instance. If you do not use the Instance Manager, onstat reports a subsystem security error.

Spaces in Pathnames:
If you edit either the isacfg or httpd.conf files by hand, and use pathnames that contain spaces, ISA malfunctions. To avoid this problem, use the "short name" (which never contains spaces) when editing these files by hand. (120842)

SQL->Schema:
Using the SQL->Schema-> Generate an Update Statistics Script feature fails with the following error when saving the script to a directory that contains a space:
Cannot access path: "pathname\My Directory\upd_databasename.sql"
This error occurs whether you specify the full name or DOS name. (147086)


3. Java-Enabled Features Issues

Browser Back Button in Server Setup:
In general, when using Server Setup, you should only use your browser Back button to return from viewing Help or from reviewing the changes that Server Setup will make to your ONCONFIG file, storage configuration, or chunk aliases.

If you use the browser Back button in other situations, such as in the middle of allocating chunks to dbspaces in the Disk Space Allocation page, unpredictible behavior might result. (150683)

Browser Timeout:
If you use ISA to monitor remote database servers, you might experience a problem with browser timeout.

If a remote ISA node does not exist or the remote ISA web server is offline, the browser experiences a delay while ISA tries to connect. This might cause your browser to timeout and you will be unable to configure local servers or change remote ISA servers.

Java Runtime Environment:
The Java-enabled features of ISA require the JRE version 1.2.2 or higher. A bug exists with using the Java-enabled features with the JRE version 1.2.1. (150468)

Server Setup Disk Allocation:
If you allocate two chunks to the physdbs dbspace (physical logs) and the size of the first chunk that you allocate is less than or equal to the value of the ONCONFIG parameter, PHYSFILE, the database server might not come online.

For example, if PHYSFILE is 2000 and you allocate two chunks to physdbs (2000 KB and 2048 KB), when Server Setup brings the server online after adding the spaces, oninit reports a fatal error during shared memory creation and the online message log contains the following error:

Cannot allocate Physical Log File, 1000 wanted, 997 available.
(151067)


4. Migration Issues

Migration->Dbimport:
If importing a database from a tape device and the tape is not mounted, ISA displays the following message:
        Please mount tape 1 and press return.... However, nothing happens when you press return. To correct this, mount the tape device before performing the import. (126727)

Migration ->HPL->Jobs:
The following are known issues with the High-Performance Loader:

Windows:
See Windows Issues for known issues with Migration on Windows platforms.
 
© Copyright International Business Machines Corporation 2002, 2003. All Rights Reserved.

US Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.