=================================
RELEASE NOTES
FOR
INFORMIX 7.31.UC2 PRODUCT RELEASE
DATE: 26 Feb 1999
=================================
TABLE OF CONTENTS
I. OVERVIEW OF RELEASE NOTES
II. PRODUCTS, FEATURES, AND ENHANCEMENTS IN THE 7.3 RELEASE
Informix Products
New Features for 7.30
New Features for 7.31
Features not Available in This Version
Documentation Information
Year 2000 Information
Restrictions and Workarounds in 7.31
Using Target Tables in the INSERT INTO SELECT FROM Statement
Changes to the stdev() Function
III. INFORMIX DATABASE SERVER PRODUCTS
Limits in Informix Dynamic Server
System-Level Parameters
Access Capabilities
System Defaults
On-Monitor Statistics
IV. MIGRATION AND INSTALLATION ISSUES
Installing the 7.31 Product
New Features in the Installation Wizard (7.31)
Conversion and Reversion
New ONCONFIG Parameters
Using Older Clients
New Reserved Words
New Environment Variables
Reversion from 7.3 to 7.24 or Earlier (ALTER TABLE)
Reverting 7.3 GLS System to Version 7.1 NLS of IDS on Windows NT
Reverting From 7.31 to an Older Version When Using RAW Tables
Migrating and Reverting with Enterprise Replication
Coexistence of Multiple Release Versions
Improving Dbload Performance
Verifying that the Storage Manager is Certified
V. INFORMIX STORAGE MANAGER INSTALLATION AND CONFIGURATION
ISM 2.0 Information
ISM Setup Procedure on UNIX Database Servers
Script
ISM Setup Procedure on NT Database Servers
Script for Minimum SETUP and STARTUP
Setup with ISM GUI
ISM Configurations Not Using ISMData Pool
ISM Installation and Uninstallation Problems on Solaris
Installing and Certifying the Storage Manager During Migration
Hosts File Required When Using ISM With DNS Disabled
Using HDR with ISM and ON-Bar
VI. ENTERPRISE REPLICATION INFORMATION
Restrictions
Configuration with Informix Enterprise Command Center
Configuration without Informix Enterprise Command Center
Using regedt32 to Configure Sqlhosts
Configuration with the SQLHOSTS Editor
Troubleshooting the Replication Manager
Notes for the Replication Manager
Notes for the Monitor
Known Defects in Enterprise Replication
VII. ON-BAR INFORMATION FOR RESTARTABLE RESTORE
VIII. MACHINE-SPECIFIC INFORMATION FOR UNIX
IX. WINDOWS-SPECIFIC INFORMATION FOR NT
Installation Requirements
User Names
Changing the Machine Name
Logon Locally Permissions (UPDATED)
Multibyte Characters
GLS Settings
Environment Variables
SHMBase for Large Memory Configurations
NET VPs
Problem with More than Twelve Informix Server Services
Stores7 Demonstration Database Batch File
DB-Access Default Editor
Informix Dynamic Server Running With Clearcase Software
System Commands in Stored Procedures (UPDATED)
Special Conditions when Primary Domain Controller Not Available
Information Related to the High-Performance Loader
REGCDRCL.EXE Utility in Enterprise Replication
Specifying LTAPEDEV and TAPEDEV When Using Ontape
Ontape Backups to Compressed Files on NTFS Drives
Clash of Optical Library DLL with Engine's Shared Memory
Informix Storage Manager and Microsoft Clusters
Viewing Error Messages from Cluster Service
Use of Named Pipe Protocol on Informix Dynamic Server on a Cluster
Interrupting Long Queries (NEW)
X. KNOWN DEFECTS IN 7.30 WITH WORKAROUNDS
Defects in 7.30.UC1 (UNIX) With Workarounds
Defects in 7.30.TC1 (NT) With Workarounds
XI. KNOWN PROBLEMS WITH THE 7.31 BUILDS
XII. FIXED CUSTOMER-REPORTED BUGS in 7.31 (UNIX)
XIII. OPEN CUSTOMER-REPORTED BUGS in 7.31 (UNIX)
XIV. FIXED CUSTOMER-REPORTED BUGS in 7.31 (WINDOWS NT)
XV. OPEN CUSTOMER-REPORTED BUGS in 7.31 (WINDOWS NT)
I. OVERVIEW OF RELEASE NOTES
The purpose of these release notes is to make the user aware of
changes in products that might affect existing applications.
The release notes contain information on changes from previous
versions, known bugs, and workarounds. Bug numbers are assigned
to known defects to assist you in identifying the defects to
Customer Services personnel.
The release notes document is not intended to be all-inclusive;
it is a tool to assist you in the update process. Please consult
Informix product manuals for additional information on product
features and for clarification of product behavior.
Note: These release notes apply to both NT and UNIX platforms
unless specifically stated otherwise for a particular section.
This SERVERS_7.3 file applies only to the 7.3 release.
It contains information you will need to know when upgrading from
the 7.2 release. If you are upgrading from a release prior to 7.2,
then you should also examine the SERVERS_7.1 and SERVERS_7.2 files.
Purpose of the Addendum File
----------------------------
The addendum file, SERVERS-ADDENDUM_7.3, contains bug fixes for
interim releases (7.31.UC2/TC2 and later).
II. PRODUCTS, FEATURES, AND ENHANCEMENTS IN THE 7.3 RELEASE
Informix Products
=================
The following products are contained in the 7.3 servers
products release:
Product Name
------------
Informix Dynamic Server (database server)
Informix Dynamic Server, Workgroup Edition
Informix Dynamic Server, Developer Edition
New Features for 7.30
=====================
Most of the new features for this release fall into five major areas:
o Reliability, Availability, and Serviceability (RAS)
o Performance
o Windows NT-Specific Features
o Application Migration Enhancements
o Manageability
In addition, several features that are implemented in this release
fall into the areas of connectivity, Enterprise Replication, and
the Optical Subsystem.
Reliability Availability and Serviceability
-------------------------------------------
Alter Fragment Attach/Detach enhancements
In-place Alter Table Modify/Drop
Oncheck enhancements
Restartable restore (see "Backup and Restore Guide")
External backup/restore (see "Backup and Restore Guide")
Performance Improvements
------------------------
Optimizer directives
Select first 'n' rows
Ordered merge
Memory resident tables
Correlated subquery enhancements
Keyfirst index scan
Other selected performance enhancements
NT Specific Features
--------------------
Multiple residency
Raw device support
High Performance Loader
ON-Bar XBSA certification
ON-Bar parallelism
Optical Subsystem
Non-domain Administrator install
Microsoft Cluster Support
Local connection support using named pipes
Application Migration Enhancements (Changes to SQL)
---------------------------------------------------
Three new functions for case insensitive search:
UPPER, LOWER, INITCAP
Four new functions for string manipulations:
REPLACE, SUBSTR, LPAD, and RPAD
The CREATE VIEW statement now includes UNION
New CASE expression
New NVL and DECODE functions
Two new date conversion functions:
TO_CHAR and TO_DATE
New environment variable: IFX_UPDDESC
You can now describe an UPDATE statement if you turn on the
IFX_UPDDESC environment variable.
You can now update triggering columns with EXECUTE PROCEDURE.
Enhancements to the dbinfo function that allow you to obtain
the hostname and version of the database server.
Manageability Enhancements
--------------------------
Informix Enterprise Command Center provides the ability
to manage your entire database environment (UNIX & NT) from a
single console.
The Informix Storage Manager (ISM), shipped with this database
server, is an application that manages the storage devices and
media that contain backups. During a backup, ON-Bar sends the data
to ISM and during a restore, it retrieves the data from ISM.
Some customers might find ISM functionality adequate; other customers
might require the more extensive functions in third-party
storage managers.
Additional information for onsnmp Management Information Bases
is available.
Connectivity Enhancements
-------------------------
Greater network security is available through support of
third-party security services.
Enterprise Replication Enhancements in 7.30
-------------------------------------------
Enhanced GLS support: ability to replicate within a locale.
In other words, you can replicate in any language locale that
Informix supports.
Command-line utility.
Scripting view in the Replication Manager GUI.
New CONNECT and DISCONNECT functions in the Enterprise Replication API
Optical Subsystem Enhancements
------------------------------
Shared library support for Informix Optical Subsystem; you no
longer need to order the Optical Subsystem as a separate product.
Oncheck Enhancements
--------------------
The new oncheck options -ciw, -cIw, -pkw, -pKw, -plw, -plW, -cpR
are documented in the 7.3 Administrator's Guide and 7.3
Performance Guide.
The new oncheck -w option allows you to check and print
an index without placing a shared lock on
the table. Use this option only for tables with row locking.
Example: -c{i|I}w
The new oncheck -R option checks the reserved pages,
physical-log pages, and logical-log pages. The existing -r option
checks the reserved pages only. Example: [c|p]R
Features Not Available in 7.31
==================================
The following features are currently not supported in this
release of Informix Dynamic Server 7.31:
Please refer to machine notes for HP & Sequent specific issues
(in release/en_us/0333/IDS_7.3).
The archecker tool for ontape and ON-Bar is not documented or
supported for customers because use of this tool might corrupt
data and indexes if not used properly. Only Informix technical support
or consultants can use it.
Documentation Information
=========================
Please read the documentation notes for the product manuals. They
contain further information about modified features.
Year 2000 Information
=====================
The present default for the DBCentury environment variable is
"current." If you want the closest century (such as 2000),
set DBCentury to "closest."
For information Year 2000 bugs and fixes, the external website is at:
.
Please contact Sun Microsystems for their Year 2000 patches.
New Features in the 7.31 Release
================================
The following features have been introduced in 7.31 release:
1> Retain Update Locks
For information, see the PERFDOC_7.3, SQLSDOC_7.3 and SQLTDOC_7.3
documentation notes. SQLSDOC_7.3 describes the SQL syntax and
PERFDOC_7.3 describes the locking behavior.
2> ANSI Join
For information, see the SQLTDOC_7.3, SQLSDOC_7.3, and PERFDOC_7.3
documentation notes. SQLTDOC_7.3 describes the ANSI join.
SQLSDOC_7.3 describes the SQL syntax and differences between the
ANSI outer join and Informix outer join. PERFDOC_7.3
describes the performance advantages of push-down filters
in the ON clause and changes in the SET EXPLAIN output.
3> Nonlogging Tables
For information, see the ADMINDOC_7.3, SQLSDOC_7.3, SQLTDOC_7.3,
and PERFDOC_7.3 documentation notes.
Usage of the TYPE Reserved Word
-------------------------------
With the addition of the new "nonlogged table" type,
TYPE is now a reserved word. If you are using TYPE as an
identifier in an SQL query, it might return syntax errors.
For example, the following query returns an error:
SELECT * FROM tab type;
In the above situation, use either of the following workarounds:
o Rename the table alias to a nonreserved word.
o Rewrite the query as:
SELECT * FROM tab AS type;
4> Rename Index
For information, see the PERFDOC_7.3 and SQLSDOC_7.3 documentation
notes.
5> Up to 3 GB Shared Memory Support on NT (NT specific)
For information, see the ADMINDOC_7.3 documentation notes.
6> Password Encryption
For information, see the ADMINDOC_7.3 documentation notes.
7> Enterprise Replication Enhancements in 7.31
Data compression on network messages.
Option to apply replicated transactions as table owner.
The Enterprise Replication Monitor is no longer supported.
Section IV, "Migrating and Reverting with Enterprise Replication,"
Section VI, "Enterprise Replication Information," also have been
updated with 7.31 information.
The EREPDOC_7.3 documentation notes and the ER on-line help
also have been updated.
8> IFX_NETBUF_PVTPOOL_SIZE and IFX_NETBUF_SIZE Environment Variables
For information on these environment variables, database
server settings that affect the client environment variables,
and the new systables flag for raw tables, see the SQLRDOC_7.3
documentation notes.
For information on how these environment variables affect the
network buffer pools, monitoring, and tuning these environment
variables, see the PERFDOC_7.3 documentation notes.
9> IDS 7.31 uses ISM 2.0 which is Year 2000 compliant. For more
information, see the section "INFORMIX STORAGE MANAGER
INSTALLATION AND CONFIGURATION."
Restrictions and Workarounds in 7.31
------------------------------------
Using Target Tables in the INSERT INTO SELECT FROM Statement
============================================================
The following information is the fix for PTS 102347.
Let us consider the following INSERT statement:
INSERT INTO <target-table>
(SELECT * FROM <source-table> WHERE ...);
The earlier implementation did not allow the source table to be the same
as the target table. Any table occurrence in the SELECT clause
of the INSERT clause cannot have the target table. The server returns
error -360 if it detects such a case.
This feature relaxes the above restriction by allowing the use of target
tables in the SELECT clause of the INSERT statement.
Semantics:
---------
If one of the tables in the SELECT clause is the target table, then
newly inserted rows into the target table by the INSERT statement
are NOT used for evaluation of the select or any of the nested
subquery of the INSERT statement.
The effect of the above statement is the same as the following
statements executed in a transaction.
SELECT * FROM <source-table> WHERE ... INTO TEMP <temp-tab>
INSERT INTO <target-table> SELECT * FROM <temp-tab>
DROP TABLE <temp-tab>
Restrictions:
-------------
INSERT INTO <target-table> EXECUTE PROCEDURE <someproc>();
If procedure <someproc> scans or updates <target-table>,
then the database server returns error -360.
The behavior of the UPDATE and DELETE statements
has not changed where the target table is used in their select
subqueries. In this case, the database server
returns error -360.
Changes to the stdev() Function (PTS 101236)
============================================
This fix to PTS 101236 applies to the stdev() function in a SELECT
statement that has a group by clause for a single row group.
The stdev() function has changed from calculating 'sample
deviation' to calculating 'population deviation.' The difference
between the two is in the final divide by the value '/N' in
the expression. For sample deviation, we would divide by 'N-1' and for
population deviation, which we are now calculating, we use 'N'.
Users will find that our calculation of the standard deviation is
different from earlier server versions, the difference being (N-1)/N
and, of course, the special case when N is 1.
Use the following formula to calculate the population deviation:
(sum((X[k])^2) - (sum(X[k]))^2/N) / N
By definition, the population deviation for a population of 1 is 0.
If you wish, you can omit such cases through the appropriate query
construction; for example, "having count(*) > 1."
III. INFORMIX DATABASE SERVER PRODUCTS
LIMITS IN Informix Dynamic Server
=================================
Maximum Capacity
System-Level Parameters Per Computer System
-----------------------------------------------------------------
Informix Dynamic Server systems per computer...........255
(Dependent on available system resources)
Maximum number of accessible remote sites ...... machine specific
Maximum Capacity
Table-Level Parameters (based on 2K page size) per Table
-----------------------------------------------------------------
Data rows per fragment............................. 4,277,659,295
Data pages per fragment............................... 16,775,134
Data bytes per fragment........................... 33,818,671,136
(excludes Binary Large Objects, BLOBs; roughly double this
number for 4k page size)
Binary Large Object bytes.................................. 2**31
Row length................................................ 32,767
Number of columns............................................ 32K
Indexes....................................................... 77
(roughly double this number for 4k page size)
Columns per index............................................. 16
Bytes per index.............................................. 255
Maximum Capacity
Access Capabilities per Dynamic Server System
-----------------------------------------------------------------
Maximum databases per Dynamic Server.................. 21 million
Maximum tables per Dynamic Server..................... 477,102,080
Maximum active users per Dynamic Server........... 32K userthreads
(minus the minimum number of system threads)
Maximum active users per database and table...... 32K userthreads
(Also limited by the number of available locks, a tunable parameter)
Maximum number of open tables per Dynamic Server.......... 32,000
Maximum number of open tables per user and join........... 32,000
Maximum locks per Dynamic Server and database........... 8 million
Maximum number of page cleaners.............................. 128
Maximum number of recursive synonym mappings.................. 16
Maximum number of tables locked by user....................... 32
Maximum number of cursors per user.............. machine specific
Maximum number of pages per chunk............................. 1m
Maximum number of open BLOBs.................................. 20
Maximum number of B-tree levels............................... 20
Maximum amount of Decision Support memory ...... machine specific
Informix Dynamic Server System Defaults
-----------------------------------------------------------------
Table lock mode............................................. Page
Initial extent size...................................... 8 Pages
Next extent size......................................... 8 Pages
Read-only isolation level......................... Committed Read
(w/ database transactions)
Read-only isolation level........................ Repeatable Read
(MODE ANSI database)
ON-Monitor
-----------------------------------------------------------------
Number of displayed user threads.............................1000
Number of displayed chunks...................................1000
Number of displayed dbspaces.................................1000
Number of displayed databases................................1000
Number of displayed logical logs.............................1000
IV. MIGRATION ISSUES
Installing the 7.31 Product
---------------------------
Follow the recommended order when installing the IDS 7.31 media
and when upgrading from an existing 7.30 installation.
1. Stop all Informix services.
2. Uninstall old client products - IECC, CLIENTSDK, I-CONNECT -
using the Uninstall option in the program group.
3. Uninstall the 7.30 database server. Choose the option
"remove only database server executables and support files."
4. Install the 7.31 database server N267 or higher versions.
5. Install IECC 3.01.
6. Install the server agent for IECC 3.01.
7. Install ClientSDK 2.20.
8. Reboot the computer.
9. Set the environment variables through setnet32.
The new IDS 7.31 database server should now be accessible.
New Features in the Installation Wizard (7.31)
----------------------------------------------
* An enhanced dialog box shows the progress of file copying.
While the files are being copied from the media to the disk,
the progress dialog shows three additional pieces of
information:
- the product number
- the total number of products copied
- a progress bar
* The first time you install the 7.31 product on a PC, the installation
program sets the default target directory for the computer.
The default installation target directory is
C:\Informix if the PC is brand new, or if the
INFORMIXDIR registry key is null and the INFORMIXDIR
environment variable is not set.
* The "Select Installation Alternative" (Typical, Custom)
dialog box is not displayed in a Meta install.
* The display of the "Configure the Products" dialog box
depends on the product selection. It displays only when
you select one or more products that require configuration.
Conversion and Reversion
------------------------
The 7.31.UC1 and 7.31.TC1 releases support automatic data
conversion from previous versions to 7.31 INFORMIX versions, as well as
automatic data reversion from 7.31 to older versions.
To convert or revert existing data, use the following guidelines:
CONVERSION
----------------------
Source
----------------------
*Single user mode
onmode -sy
onmode -l
onmode -c
*Data integrity check
oncheck
*Level-0 backup
*Server shutdown
onmode -yuk
---------------------
Target
---------------------
Server startup
oninit
*Update statistics
highly recommended
*Data integrity check
oncheck options
*Level-0 backup
REVERSION
------------------------------
Source
------------------------------
*Drop all unsupported features
*Single User Mode
onmode -sy
onmode -l
onmode -c
*Data integrity check
oncheck
*Level-0 backup
*Activate reversion and shut down server
* onmode -b version
------------------------------
Target
-----------------------------
Server startup
oninit
*Update statistics recommended
*Data integrity check
oncheck
*Level-0 backup
During the conversion or reversion process, monitor the server
online.log activity.
* To find what version to use when you revert from 7.3 to a
previous version, use onmode -b --.
New ONCONFIG Parameters
-----------------------
New ONCONFIG parameters are available in this release.
For a complete list of ONCONFIG parameters used in setting up
and configuring Informix Dynamic Server, Version 7.3, see your
"Informix Dynamic Server Administrator's Guide."
Using Older Clients
-------------------
If you use a 7.x or 9.x client-side product with the 7.3 server,
you will not be able to use new SQL syntax unless you use the
syntax in a PREPARE statement. You can use new syntax with the
2.01 version of the client SDK.
New Reserved Words
------------------
With the addition of new functionality, new reserved words have
been added for this release. For the complete list of reserved
words, see the "Informix Guide to SQL: Syntax."
New Environment Variables
-------------------------
For a complete list of environment variables used in setting up
and configuring Informix Dynamic Server, Version 7.3, see the
"Informix Guide to SQL: Reference."
Reversion from 7.3x or 7.24 to an Earlier Database Server (ALTER TABLE)
---------------------------------------------------
If your 7.3x or 7.24 database contains tables with in-place ALTER TABLE
statements, you must run a test UPDATE statement on these tables
before you revert to an earlier version. For more information, see
the Migration Guide and the SERVERS_7.2 file. For more information
on in-place ALTER TABLE statements, see your Performance Guide.
Reverting 7.3 GLS System to Version 7.1 NLS of IDS on Windows NT
-----------------------------------------------------------------
This problem applies only if you need to revert from the 7.3 version
of Informix Dynamic Server on Windows NT to the older 7.1 version.
After you run the reversion utility (onmode -b 7.1), back up the
reverted dbspaces using ontape. This step is necessary
because of some incompatibilities arising from the GLS<->NLS catalog
conversion between the 7.3 and 7.1 versions of Informix
Dynamic Server on Windows NT.
Install and initialize the 7.1 database server.
Restore the ontape backup onto the 7.1 installation. Continue with
steps 9, 10, 11, and 12 on pages 3-12 and 3-13, as described in the
Migration Guide for Version 7.1.
This problem does not affect the ability to revert to Version 7.2 of
the Dynamic Server. Follow the steps described in the
Migration Guide for Version 7.3.
Reverting From 7.31 to an Older Version When Using RAW Tables
-------------------------------------------------------------
The reversion process automatically alters RAW (nonlogging) tables
to STANDARD (logging) tables. If you do not alter RAW tables to
STANDARD when reverting, later when you convert from the older version
to 7.31, these tables become RAW again. (This situation occurs because
the systable flag used to identify RAW tables is not known in 7.30.)
Before shutting down the old database server, alter all RAW tables to
STANDARD. Later, if you convert from the older version to 7.31,
these tables remain STANDARD.
If RAW tables were updated since the last backup, you must
perform a level-0 backup.
Migrating and Reverting with Enterprise Replication
---------------------------------------------------
For important migration information about the following topics,
see the Migration Guide documentation notes in the MIGRATEDOC_7.3
file:
o Migrating the syscdr database
o Modifying SQL statements larger than 255 bytes
o Retaining Enterprise Replication state during migration
o Reverting to 7.20 which does not support Enterprise Replication
All the conversion and reversion operations must be performed by
user 'informix'.
I. Converting CDR to 7.31
You can convert from either 7.2x or 7.30 to 7.31.
1. Before shutting down the old database server
a) Stop applications doing replicatable transactions.
b) Make sure that control and TRG send queues are empty.
Run 'onstat -g grp' to ensure grouper doesn't have any pending
transactions.
Sample Output:
Informix Dynamic Server Version 7.31.UC1--On-Line--Up 00:28:15--18752 Kbytes
Grouper:
Last Idle Time: 98/11/09 15:12:01
Log update buffers: 1024
Log update buffers in use: 0
Log update buffers in use should be zero.
Run 'onstat -g rqm' to check for queued messages.
Sample Output:
RQM Statistics for Queue #3
Database name: syscdr
Table name: control_sendq
Index name: control_sendq_key
Flags: 0x00000301
Elements in memory: 0
Elements on disk only: 0
Memory used for data: 0 Bytes
Total memory used: 0 Bytes
Element high water mark: 2000
Data high water mark: 140000 Bytes
Elements stored on disk: 0
'Elements in memory' and 'Elements stored on disk' should be zero.
c) Make sure that CDR is in stopped state or use the stop_cdr
program in the demo directory.
In 7.30 and 7.31, you can execute 'cdr stop' command to stop CDR. In
7.2x servers, you have to use Enterprise Replication Manager for this.
2. Shut down the old server and bring up 7.31 server on the same root
dbspace.
3. Take a full backup of syscdr and databases.
4. Make sure that no replicatable transactions occur in the system before
CDR is started.
5. If you are converting from release 7.30,
rebuild sysmaster database using the "buildsmi" command.
6. Run the concdr script that is in the $INFORMIXDIR/etc directory.
% concdr <from vers> 7.31
Valid values for <<from vers> are "7.2" or "7.3." Wait for the message:
'syscdr' conversion completed successfully.
or
'syscdr' conversion failed.
For details, look in $INFORMIXDIR/etc/concdr.out.
7. If conversion failed, then resolve the problem reported in
$INFORMIXDIR/etc/concdr.out. Restore the 'syscdr' database from backup
and then attempt conversion again.
8. Bring up CDR after successful conversion.
% cdr start
II. Reversion from 7.31
Before shutting down the 7.31 database server:
1. Stop applications doing replicatable transactions.
2. Make sure that the control and TRG send queues are empty.
Run 'onstat -g grp' to check for pending transaction in
the grouper.
Sample Output:
Informix Dynamic Server Version 7.31--On-Line--Up 00:44:30--18968 Kbytes
Grouper:
Last Idle Time: 98/11/09 15:01:15
Log update buffers: 1024
Log update buffers in use: 0
Log update buffers in use should be zero.
Run 'onstat -g rqm' to find out the elements in the queue.
In the output look for 'Txns in queue: 0' for both
'control_send' and 'trg_send' queues.
Sample output:
RQM Statistics for Queue (0xa6c4018) trg_send
Transaction Spool Name: trg_send_stxn
Insert Stamp: 0/0
Flags: SEND_Q, SPOOLED, PROGRESS_TABLE, NEED_ACK
Txns in queue: 0
3. Shut down cdr using 'cdr stop' command.
4. Take a full backup of the 'syscdr' database.
5. Run the reversion test script to make sure that none of the new
features are being used.
% revtestcdr 7.31 <to version>
Valid values for <<to versions> are "7.3" and "7.2"
6. If the reversion test succeeds, then run the actual reversion.
% revcdr 7.31 <to version>
7. If the reversion fails then check the file $INFORMIXDIR/etc/revcdr.out.
Attempt reversion after resolving problems reported in revcdr.out and
restoring syscdr from backup.
8. If you are reverting to 7.2x, then to revert the rest of the server,
run the following command:
% onmode -b 7.2
Note: This will automatically bring down the database server.
If the reversion is to 7.30, then you need to shut down the
database server manually.
9. Bring up old database server.
10. If you are reverting to release 7.30, rebuild sysmaster
database using the "buildsmi" command.
11. To bring up Enterprise Replication after a successful reversion,
use the "cdr start" command for 7.30 or use the
or use the Enterprise Replication Manager for 7.2x.
Co-existence of Multiple Release Versions
---------------------------------------------------
Informix Dynamic Server, Version 7.31 for NT cannot co-exist with
Informix Universal Server, Version 9.1 or OnLine Dynamic Server,
Versions 7.2x and 7.1x, due to differences in registry structure.
Informix Dynamic Server does not work when running on the same
SMP system. However, you can have different versions of the
database server on different SMP boxes but on the same network.
Improving Dbload Performance
----------------------------
Use a small commit level to improve dbload performance. Also,
the Performance Guide describes how to improve dbload and LOAD
performance on page 4-24.
Verifying that the Storage Manager is Certified
-----------------------------------------------
For information on verifying that the storage manager is
certified on the database server that you are migrating to,
see the last item in the "Informix Storage
Manager Installation and Configuration" section.
V. INFORMIX STORAGE MANAGER INSTALLATION AND CONFIGURATION
=======================================================
Important ISM 2.0 Information
=============================
IDS 7.31 uses ISM 2.0.
I. Y2K Compliance
ISM is Y2K compliant. ISM supports dates in the year 2000 and
beyond. All internal dates are stored in an internal format that
allows representation of dates from January 1, 1970 through December
31, 2037. ISM correctly interprets the year 2000 as a leap year.
When a year is entered as a two digit specification, ISM interprets
it as follows:
- A year entered in the range of 70 - 99 is interpreted as 1970 - 1999
- A year entered in the range of 00 - 37 is interpreted as 2000 - 2037
- A year entered in the range of 38 - 69 is invalid
II. Bugs Fixed In ISM 2.0
a. savegrp -o does not work on NT
The savegrp -o option has been fixed in this release to work on NT.
b. Can combine "file" type volumes with other types
With this release, the ISM server will not allow you to combine
"file" type volumes with other "non-file" types of volumes.
c. Target sessions for new devices is not 1
This bug has been resolved so that target sessions for a new
device are now set to 1.
d. Carriage returns appear randomly in daemon.log
The format conversion required to fix the carriage return
appearing randomly in the daemon.log has been made so this
problem no longer occurs in this release.
e. This command does not work:
ism_config -volume volume -disable_resore ssid, ssid
A warning message for this command has been included in
this release, which states that the additional ssid will
not be handled.
f. ism_op -detect does not produce error messages when the
command failed.
This bug has been fixed so that an error message is produced
when the ism_op -detect option fails.
g. The ism_clone program can be used without specifying
a pool option.
This bug has been fixed with this release so that the -pool
option is required to run this program.
h. ISM does not execute the ism_start -init command correctly
if the node name contains a hyphen.
This bug has been fixed. If a node name contains a hyphen,
the ism_start -init command strips the hyphen from the hostname
and executes correctly.
III. Known Restrictions
a. When running ISM on Windows NT, XBSA does not report a meaningful
error message if there is a mismatch between the informix
users' environment variables (ISM_DATA_VOLUME_POOL and/or
ISM_LOG_VOLUME_POOL) and the Informix server's configured
values (ISM_DATA_POOL and/or ISM_LOG_POOL) in the ONCONFIG
file. The bar_act.log reports:
XBSA Error (BSACreateObject): A system error occurred.
Aborting XBSA session
There is no message in any of the ISM logs or in the Informix
server message log report.
General ISM Setup Tips
======================
If you change the name of either ISMData or ISMLogs,
you also must do the following steps:
o Update ISM_DATA_POOL and ISM_LOG_POOL in the ONCONFIG
file with the new names.
o Change the create-bootstrap command in the onbar script
($INFORMIXDIR/bin/onbar or onbar.bat).
If Not Using ISM
================
If you choose not to use ISM, remove the create-bootstrap
command from the onbar script or onbar.bat.
ISM Setup Procedure on UNIX Database Servers
============================================
Optionally, add an administrator using the following command:
ism_add -admin $USER
If you are a member of the bargroup group on Solaris, it should be
your primary group. Set $USER to informix.
The following shell script provides the minimum setup required
for ISM operations with ON-Bar. You must edit the locations
for SM_DISKDEV1 and SM_DISKDEV2 as needed. Two of the operations
must be done as root (or informix) as shown in the script comments
below.
echo "ISM setup begins"
# the user must edit these two lines to
# select appropriate disk locations for
# storage manager use.
setenv SM_DISKDEV1 /some/place/on/disk/dir1
setenv SM_DISKDEV2 /some/place/on/disk/dir2
# start ISM server
echo "initialize ISM server, must be done as root"
ism_startup -init
# we need to create some devices and media
echo "create and mount ISM devices and pools"
ism_add -device $SM_DISKDEV1 -type file
ism_add -device $SM_DISKDEV2 -type file
ism_op -label $SM_DISKDEV1 -pool ISMData -volume ISMData
ism_op -label $SM_DISKDEV2 -pool ISMLogs -volume ISMLogs
ism_op -mount $SM_DISKDEV1
ism_op -mount $SM_DISKDEV2
echo "end of ISM setup"
ISM Setup Procedure on NT Database Servers
==========================================
Requirement:
-----------
The Netware IPX and SPX networking protocols should
be installed and enabled on the computer where Informix Dynamic
Server is installed.
Script for Minimum SETUP and STARTUP
------------------------------------
The following batch file provides the minimum setup required
for ISM operations with ON-Bar. This batch file will configure
two devices, both of file type, to back up logical logs and dbspaces.
This will allow you to back up logical logs and dbspaces to disk.
You must edit the locations for SM_DISKDEV1 and SM_DISKDEV2 as needed.
The operations must be done as user informix.
REM setup for Informix Storage Manager
echo "ISM setup begins"
REM the user must edit these two lines to
REM select appropriate disk locations for
REM storage manager use.
set SM_DISKDEV1=\some\place\on\disk\dir1
set SM_DISKDEV2=\some\place\on\disk\dir2
REM we need to create some devices and media
echo "create and mount ISM devices and pools"
ism_add -device %SM_DISKDEV1% -type file
ism_add -device %SM_DISKDEV2% -type file
ism_op -label %SM_DISKDEV1% -pool ISMData -volume ISMData
ism_op -label %SM_DISKDEV2% -pool ISMLogs -volume ISMLogs
ism_op -mount %SM_DISKDEV1%
ism_op -mount %SM_DISKDEV2%
echo "end of ISM setup"
Setup with ISM Administrator GUI
================================
If the Informix Enterprise Command Center component of the
Informix Dynamic Server is also installed, you can configure the
devices with the ISM GUI.
To start the ISM GUI, type at the command line:
start ism /s localhost
To configure a device:
a) Create a device:
Select "New" from the "Devices" menu.
Alternatively, type <CNTRL> + N.
Enter the name of the backup location. This should be a directory
if the backup device is of type file.
Select "file" for the type of device and click <OK>.
b) Label the device:
Select the device and select "Label" from the "Volume" menu.
Alternatively, type <CNTRL> + L.
Select the pool to which the device should belong
(ISMData for dbspaces, ISMLogs for logical logs).
Set the volume number and click <OK>.
c) Mount the device:
Select the device and select "Mount" from the "Volume" menu.
Alternatively, type <CNTRL> + M.
ISM Configurations Not Using ISMData Pool
-----------------------------------------
The onbar script invokes ism_catalog to back up
the ISM bootstrap after successful ON-Bar logical-log and
storage space backups. This ism_catalog invocation explicitly selects
the ISMData pool for storing the ISM bootstrap.
On UNIX, the command in the onbar script is as follows:
${INFORMIXDIR}/bin/ism_catalog -create_bootstrap -pool ISMData
On Windows NT, the command in the onbar.bat script is as follows:
%ISMDIR%\bin\ism_catalog -create_bootstrap -pool ISMData
If you configure ISM and ON-Bar without a ISMData pool device, you
will need to edit the onbar (on UNIX) or onbar.bat (on NT) scripts
to direct ism_catalog to some other existing pool, such as ISMDiskData.
On UNIX, the ism_catalog line of the onbar script would be as follows:
${INFORMIXDIR}/bin/ism_catalog -create_bootstrap -pool ISMDiskData
On Windows NT, the change in onbar.bat would be as follows:
%ISMDIR%\bin\ism_catalog -create_bootstrap -pool ISMDiskData
If the onbar script ism_catalog invocation selects a
non-existent storage pool, ON-Bar will seem to hang and a
message will appear in the ISM log that an operation is waiting
for ISMData pool to be mounted.
For more information, see the documentation notes for ON-Bar in
ONBARDOC_7.3.
The NSRADMIN Utility
====================
The end user should not use the NSRADMIN character-based user
interface unless instructed to do so by Informix Technical
Support. Incorrect use of these tools
could result in problems with your ISM system. These
tools are undocumented.
Do Not Use Rewind Devices with ISM
==================================
The ISM Administrator Guide, on page 3-6, mentions that ISM
writes a file mark at the end of each backup and appends the
next storage volume after this mark. If the tape device rewinds,
the previous backup will be lost.
ISM does not support rewind device types. If you use a "rewind"
tape device, your backups will appear to have completed successfully
but your tapes will contain only the last save set. (A backup
operation might contain several save sets.) If you use a rewind device,
it overwrites the previous save set and data is lost.
Also, using rewind devices degrades your performance severely.
Many tape drives come with two device drivers. One driver provides
"rewind" functionality. The other driver provides "no-rewind"
functionality.
ISM Installation and Uninstallation Problems on Solaris
=======================================================
1. ISM cannot be installed on a machine in which a NetWorker server
or a NetWorker client has already been installed. If such an
installation is attempted, it will fail with the following message:
---------------------------------------------------------------------------
*** The ISM setup script detected that another storage manager is installed
in /nsr, which conflicts with ISM. If you want to setup ISM, you need to
de-install the other storage manager and then run
'$INFORMIXDIR/bin/ism_startup -init'.
---------------------------------------------------------------------------
For ISM to be installed on a machine having a NetWorker
server or client on it, the NetWorker server or client has to be
COMPLETELY de-installed first. (On Solaris, for example, use 'pkgrm',
then remove the entire '/nsr' structure.)
2. A NetWorker server should not be installed on a machine having
ISM already installed. Currently, the NetWorker server installation
cannot detect such a conflict. It is thus the responsibility of the
user to make sure that such a case does not occur (see [3] below, too).
3. The supplied 'ism_shutdown' command simply shuts down the ISM
daemons nsrd, nsrexecd, nsrmmdbd, and nsrindexd. It does not de-install
ISM, that is, it does not remove the ISM executables in
$INFORMIXDIR/bin, the symbolic link /nsr, or the various ISM files in
$INFORMIXDIR/ism.
Installing and Certifying the Storage Manager During Migration
--------------------------------------------------------------
When you convert or revert an Informix database server,
the storage manager that you used on the old version might not be
certified for the version that you are migrating to.
Verify that Informix has certified the storage manager for the
target server version and platform. If not, you need to
install a certified storage manager before performing backups
with ON-Bar.
When you migrate to the new database server version, install
the storage manager BEFORE you bring up the database server.
That way if you have automatic log backup set up on the
database server, ON-Bar can start backing up the logs when the
database server comes on-line.
Hosts File Required When Using ISM With DNS Disabled (Bug 94597)
----------------------------------------------------------------
The domain name service (DNS) translates the host names into IP
addresses. So when your computer is not on the network, DNS is
disabled and you need to provide the IP address and host name in the
hosts file.
For non-network ISM installations with IDS 7.3, create a Windows NT
hosts file with the default local loopback entry as follows:
127.0.0.1 localhost
The hosts file is located in C:\WINNT\system32\drivers\etc\hosts.
If this entry is not present in the hosts file, you might get the
following error when using ISM:
nsrmmd #1: unauthorized READ_LABEL call to mmd 1: Access violation -
[] unknown host: 127.0.0.1
Using HDR with ISM and ON-Bar
=============================
The Legato LGTpa09766 patch is required to use High-Availability Data
Replication with ISM and ON-Bar. The currently available patch
is for UNIX only and is not Year 2000 compliant. No ISM patch is
available for Windows NT as of now.
For the procedure on using HDR with ISM and ON-Bar, see
the Backup and Restore documentation notes (ONBARDOC_7.3).
VI. Enterprise Replication Information
======================================
Restrictions
------------
In 7.30, the following features are disabled and cannot be used:
o Non-root servers
o Intermittent connectivity
o Connect and Disconnect
o Sparse catalogs
o Floating connection threads
In 7.31, the following features are disabled and cannot be used:
o Non-root servers
Other Notes
-----------
Applications must be recompiled to take advantage of the fix for 88803
(applying replicated transactions as table owner).
Applications which use the ER API (such as from within a C program) must use
the 2.01 version of the Client SDK. This restriction does not apply to
usage of the command-line utility.
If you have your NETTYPE=tlitcp,2,,NET parameter
(or >1 poll thread specified), you might possibly
witness some timing issues on disconnects that cause connections to show up as Dropped
(connection lost) rather than Disconnected (administrative close).
You should not perform queries against CDR-related SMI tables while
CDR is shutting down. Such queries might result in a database server crash.
Receive queue dbspace cannot be changed using the
Modify Server command.
When defining replicates, owner name is mandatory.
ER internally retains database connections on tables which are the destination of
replication activity as a performance optimization.
ER drops these connections every minute.
While ER has the connections open, index creation will time out
if you are not using "lock wait." To create an index on a replicated table,
you must use a lock wait value of 1 minute or delete all replicates
on that table.
As with 7.31, 7.30, and 7.2x, the connection state between
database servers are not stable. This means whenever a
database server is bounced, ER attempts to
establish a connection to other applicable servers. ER keeps trying
until the connection succeeds. This effort occurs even if the state of the
connection prior to recovery is Administrative close (i.e. a disconnect command
was issued for this connection).
When an explicit Connect/Disconnect Serv command is issued, the command
will be synchronous and tried only once.
The following are the new onconfig.std parameters for CDR
:CDR_LOGDELTA
The old onconfig.std parameter, CDR_QUEMEM, indicates the amount of memory
that is allocated for Queues. This setting is useful for customers who have a large
log size in order to limit the Queue memory. For customers who have small
log size (required log size is smaller to handle their volume and size
of transaction ), to prevent the Queue memory from being overcommitted
especially during ddr blockout phase, specify a percentage of log
space to be Queue memory as specified by CDR_LOGDELTA. Whichever is lower (QUEMEM or
LOGDELTA) is what will be used when CDR comes up.
CDR_NUMCONNECT is an approximation of the maximum number of connections to other
servers that are expected. CDR_NUMCONNECT does not actually restrict the number
of connections to database servers. Instead it is used as an advisory value for
resource allocation purposes. When the CDR_NUMCONNECT value in the
ONCONFIG file is below 4, a default value of 4 is applied.
CDR_NIFCOMPRESS indicates the compression factor when for network messages. The
possible values are: -1 never, 0 none, 9 max. -1 indicates that
compression will never be done irrespective of whether the target site
has compression or not. 0 indicates no compression will be done locally
unless requested by the peer.
CDR_NIFRETRY indicates the time between retries in the case of all
Non-administrative close situations. A value of 0 indicates do not retry at all.
The following changes are effective for sysmaster:
syscdrq - the lstcommittime and lstquetime columns have been removed.
Two new columns, srcname and srcid have been added to
the syscdrq table. The meaning of the bytesqued column
has changed; bytesqued information is now broken down
according to the server that originated the data.
The new srcname and srcid columns list the relevant server.
syscdrqueued - The lstcommittime and lstquedtime columns have
been removed. The other columns retain their meaning.
syscdrtx - no longer contains avgrcvlatency, avgcmtlatency columns.
syscdrtxproc - no longer contains avgrcvlatency, avgcmtlatency columns.
syscdrserver - no longer contains issporadic, issparse columns.
The new columns include isleaf and isnonroot.
syscdrs - no longer contains issporadic, issparse columns.
The new columns include isleaf and isnonroot.
syscdrrecv - this table no longer exists.
Note: Some ER-related fields in sysmaster have changed from
char(18) to char(128).
Configuration with Informix Enterprise Command Center
=====================================================
This sections describes how to configure an NT system to use the
Replication Manager (ERM) to administer your Enterprise
Replication system.
The "rephosts" file option for server information is no longer
supported. All server configuration information for use by the ERM
must be set up in the NT registry.
1. IECC must be installed on your NT system. You should use the
"typical" installation to ensure that the client configuration piece
gets installed.
2. Start IECC. Expand the Informix Neighborhood folder.
Select the Control Panel. Double-click the Network icon on the right
side of the screen to invoke the client configuration dialog.
3. The machine name field on the Shared Servers page should be the
name of the machine on which you want the registry entries created.
It is best to have this be the local machine (where you have
installed IECC).
To add a db server entry:
------------------------
1) Go to the Servers page and click the Add button.
2) Enter the machine name where your database server resides and
click Next. You might get an error about not being able to connect
to this machine. Click Yes to use that machine name anyway.
3) Enter the database server name and click Next.
4) Click Next again.
5) Fill out the service name and select a network protocol and
click Finish.
Now you need to add a corresponding server group entry:
------------------------------------------------------
1) Go to the Server Groups page and click the New Group... button.
2) Enter the <server group name> that you chose in step 7 above.
3) Check the 'Use group for replication box.'
4) Edit the 'Replication identifier' value to be the server group
id. This value is in the INFORMIXSQLHOSTS file.
5) Click OK.
6) Select the new group that you just created and click the Add
Server button. The server you created above should appear in the dialog
box.
Select it and click OK.
When you have added all the database servers and database server
groups, you need to click the OK button at the bottom of the dialog.
You will get a warning about overwriting the SQLHOSTS registry entries
on the machine that you specified. Click OK.
Now you should be able to run the Replication Manager from IECC
and connect to the servers that you just added to the SQLHOSTS
registry.
Configuration without Informix Enterprise Command Center
========================================================
This section describes an alternate way to configure an NT system to
use the Enterprise Replication Manager (ERM) to administer your
Enterprise Replication system.
If you do not have IECC available, or have difficulty configuring your
NT system for use with the ERM using the IECC client config module,
you can set up the majority of the configuration using Setnet32, as
follows.
Under the servers tab you can set up your server entries and most of
the server group entries.
For the server entry:
--------------------
The Informix Server field should contain the server name.
The HostName field should contain the host machine name.
The Protocolname field should contain the protocol that the server
uses.
The Service Name field should contain the name of the service that
the server uses.
The Options field should contain the string "g=<server group name>"
(g= plus the server group name).
For the server group entry:
--------------------------
The Informix Server field should contain the server group name.
The HostName field should contain a dash ("-").
The Protocolname field should contain the default (this will be
changed later).
The Service Name field should contain a dash ("-").
The Options field should contain the string "i=<server group id>."
To update the NT registry:
-------------------------
1. After applying the changes you make in Setnet32, run regedt32.
2. Find the window titled "HKEY_LOCAL_MACHINE on Local Machine".
Under SOFTWARE->Informix->SQLHOSTS, there should now be a key for
your server group and your server. Select the group key and choose
the Add key from the Edit menu.
Give the new key the name of the server, leave the class
field blank.
2. When the group key is selected you should see four values
on the right side of the screen. Select the value that starts
"PROTOCOL" and edit that field to contain the string "group".
You should now have two keys that look like this:
SQLHOSTS
|
|
|
---<server group name>
| | HOST:REG_SZ:-
| | OPTIONS:REG_SZ:i=<server group id>
| | PROTOCOL:REG_SZ:group
| | SERVICE:REG_SZ:-
| |
| --- <server name>
|
|
---<server name>
HOST:REG_SZ:<host name>
OPTIONS:REG_SZ:g=<server group name>
PROTOCOL:REG_SZ:<protocol>
SERVICE:REG_SZ:<service name>
Using regedt32 to Configure Sqlhosts
====================================
Launch regedt32. (Choose Run from the Start menu and type regedt32.
Click OK). Find the window titled HKEY_LOCAL_MACHINE on the
local machine. Expand the SOFTWARE->Informix key. If the sqlhosts key
exists, select it.
If not, select the Informix key and choose Add Key from the Edit menu.
Type in SQLHOSTS in the Key name field, leave the class field
blank, and click the OK button. Select the newly created SQLHOSTS key.
To add the server key:
---------------------
1. Choose Add Key from the Edit menu. Type in the server name in the
Key Name field, leave the Class field blank, and click the OK button.
2. Select the newly created server key.
3. Choose Add Value from the Edit menu. Type in HOST for the value
name, leave the Data Type as REG_SZ, click OK. Enter the host machine
name in the string entry field that pops up.
4. Add Value OPTIONS, using g=<server group name> as the string.
5. Add Value PROTOCOL, using onsoctcp as the string.
6. Add Value SERVICE, using the service name for this server as the
string.
To add the server group key:
---------------------------
1. Select the SQLHOSTS key.
2. Choose Add Key from the Edit menu. Type in the server group name in
the Key Name field, leave the Class field blank, and click the OK
button.
3. Select the newly created server group key.
4. Add Value HOST, using - as the string
(yes, just the character "-").
5. Add Value OPTIONS, using i=<group id number> as the string.
6. Add Value PROTOCOL, using group as the sting.
7. Add Value SERVICE, using - as the string.
8. Choose Add Key from the Edit Menu. Use the server name as the key
name.
Host Information
================
After configuring the registry using IECC, you need to set up some
host information using Setnet32. If you launch Setnet32 and select the
Environment tab, you should see all the environment variables relevant
to Informix.
For Replication Manager to connect to servers correctly,
the INFORMIXDIR and INFORMIXSERVER variables must be set.
If the INFORMIXSQLHOSTS variable is not set, the
local machine name is used as the default value.
Also, you have to specify login information for the host machines
where the servers are running. This is done under the Host Information
tab. The User Name must be informix and the Password Option
must be Password, with the correct password for informix account on
the specified host entered in the Password field.
These things have to be set up for ESQL/C to work on remote
machines. The ER manager now uses ESQL/C to get information'
from the database server.
Troubleshooting the Enterprise Replication Manager
===================================================
There are several things that need to be configured on the NT machine
before the Replication Manager can successfully connect
to database servers to administer Enterprise Replication. Here is a
brief description of these things:
* On the NT machine, the user must be a member of the Informix-Admin
group.
* Sqlhosts information for all database servers participating in
replication must be set up in the registry.
* The INFORMIXSERVER, INFORMIXDIR, and INFORMIXSQLHOSTS environment
variables must be set.
* A trusted relationship must exist between the NT machine and the
host machine, OR the user and password information must be set up for
each host machine.
* The services used by the database servers must be listed in the
%WINDIR%\system32\drivers\etc\services file.
What follows are the various errors you will encounter if any of
these things are not done.
User Not in Informix-Admin Group
--------------------------------
The user that launches the Replication Manager must belong to the
Informix-Admin group. Windows NT Help includes information on how to
create user groups and add users to them.
Error -25560
------------
If you don't have the %INFORMIXSERVER% variable set in your
environment, you will get error -25560 when you attempt to
connect to the database server.
1. To set the %INFORMIXSERVER% variable, launch Setnet32 and select
the Environment tab.
2. Find INFORMIXSERVER in the list of variables and select
it. Type the server name into the entry box and then click the Set
button.
3. Click the Apply button.
Error -956 (client machine/user not trusted)
------------------------------------------------------------
The host machine where the database servers are running must trust
either the client machine where you are running the Replication
Manager or the user you are connecting with. If you are connecting to NT
database servers and the user information isn't set up, error -956
is returned.
Use Setnet32 to set up the user information for the NT host machine.
1. Launch Setnet32 and select the Host Information tab
(see Figure 2).
2. Type the host machine name in the Current Host field. The
Replication Manager always connects to the host as user informix, so
use informix as the user name.
3. Choose Password as the Password Option and type the appropriate
password for the user informix on the host machine.
4. Click the Apply button.
If you are trying to connect to UNIX servers and you get error -956,
the client machine or user is not trusted. You can fix it in
one of two ways:
o You can use Setnet32 to set up Host Information, just as was
described for NT servers.
o You can set up the client machine and user as
trusted in the hosts.equiv file which can be found in the /etc
directory on the host machine. Edit the hosts.equiv file to contain the
client machine name and the user name informix. In the home directory
of user informix on the host machine, create (or
edit) a file called .rhosts and put the client machine name in it.
Error -931
----------
The services that the servers are set up to use must be put into the
Services file. The Services file can be found in the
%WINDIR%\system32\drivers\etc directory of the client machine.
This is the service listed in the sqlhosts file (for UNIX servers) or
that was specified upon install of the server (for NT servers).
If the services are not listed in the
%WINDIR%\system32\drivers\etc\services file, you will see
this error.
Edit the services file to contain the appropriate services, making
sure the port numbers are correct.
Error -406
----------
If your INFORMIXDIR variable is not set correctly on the NT machine,
or the locale codeset for either the DB_LOCALE or CLIENT_LOCALE
variable does not exist, you will see error -406.
You should set the %INFORMIXDIR% variable to the
full pathname of the directory where IECC was installed. To set the
variable, launch Setnet32 and select the Environment tab. Find
INFORMIXDIR in the list of variables and select it. Type the path name
in the entry box and then click the Set button. Click the Apply
button.
General Notes for the Enterprise Replication Manager
====================================================
1) Certain attributes of replication objects (servers,
replicates, groups and participants) are not modifiable once the
object has been defined. There is a new feature in the scripting view
where fields that are modifiable have a pencil to the left. If you
have multiple objects selected and some are modifiable and some are not,
the pencil is grayed out. If the field is not modifiable, the pencil
does not display.
2) If you define a group with no replicates (which can only be done
through the scripting view) and subsequently add replicates to that
group, you have to reload the replication information before you can
Stop or Suspend the replicates.
3) Resetting the locale does not take effect immediately; you must
restart the Replication Manager for it to take effect.
Migrating and Reverting with Enterprise Replication
===================================================
For important migration information related to Enterprise Replication,
see the Migration Guide documentation notes in the MIGRATEDOC_7.3
file.
Known Defects in Enterprise Replication
=======================================
83817 ER does not work when IDS is started as user "root".
W/A: Start the database server as user "informix."
103179 Dropping of logical log is allowed in certain scenarios even if ER
might have needed them.
W/A: There are a few cases where the DBA is allowed to drop logical files
that ER might need later on. These cases only occur when
ER is currently not running on the server (either because the server
is in quiescent mode (OR) ER was stopped by the DBA.
Please make sure that logical log files are not dropped in the
following scenarios:
o If the server comes to queiscent mode directly from off-line
mode using onmode -s.
o If the server is brought up but ER was stopped (using cdr stop)
before it went down.
Suggested Solutions:
-------------------
1. In both cases, delay dropping logs until after ER
is started back up and the following message has been printed
in the online log:
<time> CDR queuer initialization complete
2. Look in the replay table to see what logs ER needs, using
the following commands:
database syscdr;
select * from replaytab
Then, delete only the log files less than the value reported.
In the following example, it would be safe to drop logs with
log id < 10:
llid llpos cntrlkey1 cntrlkey2
10 4120 0 7
103299 Sysmaster queries on CDR-related SMI tables while CDR is shutting
down can cause access violation.
W/A: Do not perform queries on ER-specific System Monitoring Interface
(SMI) tables while ER is shutting down.
104218 CDR change replicate -D does delete server; does not remove
the participant from replicate.
W/A: Do not include the leading "P" or "R" in the participant
name in a cdr change replicate command.
105977 In some cases, deleting a participant may not result in
queued messages for that participant being deleted.
The symptom is that "onstat -g rqm brief" shows data in
the trg_sendq or trg_receiveq queue that is bound for the
participant that has been removed from replication.
W/A: This data will remain in the queue until ER is stopped and
restarted or the database server is stopped and restarted.
This data that remains in the queue does not harm the
operation of ER. The only effect is that some queue resources
will be in use until ER is restarted.
VII. ON-Bar Information for Restartable Restore
==============================================
A new restartable restore option was added to ON-Bar (onbar -RESTART).
Use this option for a cold restore only, after a database server crash
has occurred during an ON-Bar restore. Restartable restore can be used
for any type of restore if either ON-Bar or the storage manager
crashed. It allows to you restart the ON-Bar restore from the point of
the crash.
You must set the RESTARTABLE_RESTORE ONCONFIG parameter to ON before
the ON-Bar restore crash. For more information, see the
"Backup and Restore Guide."
ALARMPROGRAM Default Value Changed
----------------------------------
The default value for ALARMPROGRAM on UNIX used to be
log_full.sh. Now, if you do not specify a value for ALARMPROGRAM in the
ONCONFIG file, the server uses the no_log.sh value (disables
continuous logical-log backups.)
VIII. Machine-Specific Information for UNIX
===========================================
For information about machine-specific limits or
procedures, see the individual machine notes in the
release/en_us/0333/IDS_7.3 file.
IX. Windows-Specific Information for NT
=======================================
Information About Installing and Using the Database Server on NT
==================================================================
Installation Requirements
-------------------------
The database server was certified on Windows NT 4.00 with service
pack 3 installed, and on Windows NT 4.0 Enterprise Edition with no
service packs.
The database server requires service pack 3 to run successfully
on Windows NT 4.00. If your system does not contain service pack 3 or
greater on Windows NT 4.00, you should install service pack 3 before
running the database server.
Service packs in addition to those required by our software should not
cause any problems, because Microsoft defines service packs as
backward compatible.
NOTE: The 7.31 database server supports Windows NT service pack 4.
User Names
----------
User names that connect to the database server can be a maximum of eight
characters long and are case-sensitive.
Changing the Machine Name
-------------------------
Users should not change the name of the machine after the Informix
Dynamic Server is installed on a machine. If this has to be done, the
Informix Dynamic Server needs to be uninstalled and installed again.
Logon Locally Permissions
-------------------------
You can connect to Informix Dynamic Server as any user. You do
not need to have the "Logon Locally" right for that. However,
to be able to run a system command in a stored procedure, you need
have the "Logon Locally" right. User Manager, a Windows NT Administrator
Tool, can assign this right. A Windows NT workstation automatically
assigns this right to new users. On a Windows NT server, the
Administrator needs to assign this right explicitly.
Use of Multibyte Characters
---------------------------
Do not use multibyte characters for user names, machine names, or
domain names. Such multibyte names are not supported. The GLS8BITFSYS
environment variable for file names is not supported.
Also, do not explicitly use multibyte names when stating object names.
That is, do not add multibyte user names set off by single quotation
marks in a statement similar to the following one:
CREATE INDEX 'dba_one'.newidx ON newtable (intcol)
For example, in this statement, you would not use a multibyte user name
in place of dba_one.
GLS Settings
------------
Informix Dynamic Server 7.22 and later releases support GLS locales
that are based on codesets that contain 1-byte, 2-byte, 3-byte,
or 4-byte characters. Informix clients can use their native codesets
when they connect to Informix Dynamic Server. For more information on
GLS settings, refer to the "Informix Guide to GLS Functionality."
Environment Variables
---------------------
Because Informix Dynamic Server for Windows NT runs as a service, it
does not access environment variables set for the logged-on user. All
environment variables that are passed to Dynamic Server are stored in
the Windows NT Registry under the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Informix\OnLine\<%INFORMIXSERVER%>\Environment
To add your own environment variables, create new values of type
REG_SZ
under this key.
SHMBASE Setting for Large Shared Memory Configurations
-------------------------------------------------------
The default load address for a dynamic link library (DLL) on Windows NT
is 0x10000000. Informix Dynamic server uses a default shared memory
base address (SHMBASE) of 0x0C000000. This means that shared memory in
the engine can grow up to 0x10000000, which corresponds to an
additional 64 MB.
If the Dynamic Server shared memory at startup is more than or close
to 64 MB, a clash of addresses is possible. In this case, set the
SHMBASE value in ONCONFIG to a higher value, for example 0x20000000.
To find the Dynamic Server shared memory size, run "onstat -g seg" and
view the total memory.
NET VPs
-------
On Windows NT, always use NET VPs to run poll threads. The NETTYPE
parameter in the ONCONFIG file should specify NET. Dynamic Server
ignores any CPU VP type in the NETTYPE parameter and uses only NET VPs
for the poll threads. Dynamic Server always creates one poll thread
regardless of the number specified in the NETTYPE parameter in ONCONFIG.
Problem with More than Twelve Informix Server Services
------------------------------------------------------
Description:
The following error is encountered if more than 12 Informix server
services are started on a host.
"user32.dll initialization failed."
Cause:
The system has run out of memory to create a new desktop heap
for the service being started. Microsoft has documented this
as a problem in Windows NT 4.0 operating System.
Workaround:
Please refer to the Knowledge Base Article --
ID: Q142676, from Microsoft.
Stores7 Demonstration Database Batch File
-----------------------------------------
The batch file to create the stores7 demo database (dbaccessdemo7.bat)
has been updated to allow the logging mode, database name, and
destination dbspace to be specified on the command line.
Usage: dbaccessdemo7 [-log] [-dbspace <dbspacename>] [<database name>]
DB-Access Default Editor
-----------------------
When you choose Query Language->Use Editor in DBACCESS.EXE, Notepad
is the default editor. If you choose to use another editor, it should
be a text editor. EDIT.COM will not work.
Informix Dynamic Server Running With Clearcase Software
--------------------------------------------------------
Problems might occur if Informix Dynamic Server is run along with
Clearcase. This can cause errors in shared
memory allocation during run-time.
System Commands In Stored Procedures
------------------------------------
To execute system commands in stored procedures, logon to the
database server with your password. If you have not explicitly
connected to the database server with a valid username and password,
the error returned is -668. This error occurs for both DB-Access and
ESQL/C applications.
The "informix" user must have the following Advanced User Rights:
* Act as part of the operating system
* Increase quotas
* Replace a process level token
System commands should contain the absolute path of the script
or the executable that needs to be executed; for example:
system "c:\temp\test.exe"
If you wish to redirect the output of the command to files, the command
line should include the command shell; for example:
system "cmd.exe /C c:\temp\test.exe > c:\temp\stdout.out
c:\temp\stderr.out"
When you include cmd.exe in the system command, you must specify the
/C option. Without this option, the command shell will not exit,
which causes the database server to wait indefinitely.
The database server will wait for the outcome of the execution of a
system command. Pay close attention to system commands defined in stored
procedures. The client application will hang if the system command never
completes or never returns.
Special Conditions when the Primary Domain Controller is Unavailable
--------------------------------------------------------------------
The following information might apply to you if you
upgraded from an earlier version of the database server.
The 7.31 install always sets REGMACHINE to point to the
local machine. Earlier versions sometimes set REGMACHINE (and
INFORMIXSQLHOSTS) to the Primary Domain Controller for the
domain when a domain install was performed.
When Informix Dynamic Server is installed on a Backup Domain
Controller (BDC) and the Primary Domain Controller (PDC) is unavailable,
the engine will automatically switch to the BDC for dealing with
Windows NT group and user accounts for authentication. This includes
determining whether a user belongs to a group (Informix-Admin, for
instance). In this situation, the Administrator must perform the
following steps in order to support this functionality:
1. Dynamic Server must be shut down.
2. In the registry under
HKEY_LOCAL_MACHINE\Software\Informix\OnLine\<%INFORMIXSERVER%>\Environment
change the values of REGMACHINE and INFORMIXSQLHOSTS to the name of
the local machine (BDC), preceded with 2 back-slashes.
3. Copy the Security key located under
HKEY_LOCAL_MACHINE\Software\Informix\OnLine\<%INFORMIXSERVER%>\
from the PDC to the BDC, including all subkeys.
4. In %INFORMIXDIR%, edit the file setenv.cmd and change the
INFORMIXSQLHOSTS value to the name of BDC.
The PDC can now be shut down and Dynamic Server can be restarted on
the BDC.
There will be a several-second delay when Dynamic Server and any of
the command-line utilities, such as onstat, onmode, or dbaccess are
started, while they try to determine that the PDC is down and switch
to the BDC.
After the initial delay, the performance will be the same as when the
PDC was running.
When the PDC is not available, the following might also have
to be done, if the server is not running on a BDC machine.
1. Shut down the database server.
2. Set the AUTHENTICATION_MACHINE environment variable for the
the server in the registry to point to a BDC machine in the same
domain. For example, under
HKEY_LOCAL_MACHINE\Software\Informix\OnLine\%INFORMIXSERVER%\Environment
create a new value called AUTHENTICATION_SERVER and set it to the
string:
"\DOM_BDC" if DOM_BDC is the name of a BDC for the
domain.
3. Restart the database server.
When the local machine is a BDC, setting AUTHENTICATION_SERVER
is not necessary.
Information Related to the High-Performance Loader
==================================================
High-Performance Loader Configuration
-------------------------------------
In the HPL configuration file specified by environment variable
PLCONFIG:
AIOBUFFERS - (Different from documentation in "Guide to the
High-Performance Loader")
'default value' Maximum of(8,CONVERTTHREADS)
'recommended value Maximum of(8,2*CONVERTTHREADS)
'range of values' Integer value >= 8
Support of Pipes
----------------
Pipes are not supported in this release.
This includes the following usage:
onpload -fp
and
onpload -fa (where the device array includes device type "PIPE")
Support of Custom Drivers
-------------------------
Custom drivers are not supported in this release.
HPL and Pload Limitations (PTS 104108)
-------------------------------
The Windows NT version of HPL is limited to running with a single
CPU VP (virtual processor). If you try to configure or dynamically
add additional CPU VPs to HPL, the database server or HPL will
hang and be unable to do more work.
Information Related to Enterprise Replication
=============================================
REGCDRCL.EXE Utility for Writing Command Line utilities using CDRAPI
--------------------------------------------------------------------
This command-line interface registers the environment
required for running the command-line utilities developed using the
CDRAPI. This utility sets up the environment variable in the section
HKEY_CURRENT_USER on Local Machine, under \Software\Informix key.
This utility creates \Environment and \netrc sub keys.
It offers three modes to register the environments.
a) File Mode.
Description:
Use plain text file in the following format.
<EnvName>=<EnvValue>
Syntax: regcdrcl -f <FileName>
b) One Set Mode.
Description:
Sets one environment specified on the command line.
Syntax: regcdrcl -i <EnvName> <EnvValue>
c) Silent Mode:
Description:
Sets only minimum environment variables required
for running the command-line utilities developed
using CDRAPI.
Syntax: regcdrcl -s
Information Related to Ontape
=============================
Specifying LTAPEDEV and TAPEDEV When Using Ontape
-------------------------------------------------
ON-Bar, which is functionally richer than ontape, is the primary
backup and restore tool for Informix Dynamic Server 7.3. Because ON-Bar
does not use TAPEDEV or LTAPEDEV parameters in ONCONFIG, there is no GUI
interface to set values for these parameters. Users who still wish to
use ontape should manually change these values after installation.
Terminating Ontape
------------------
If you use the ontape utility for a continuous logical-log backup, you
can use Control-C to stop the backup. If ontape does not terminate
after displaying "Interrupt Received", run "onmode -l" and wait for
a few seconds.
Ontape Backups to Compressed Files on NTFS Drives
----------------------------------------------------
The Problem:
A restore from an ontape backup file fails to start the engine when
the backup tape file (pointed to by the TAPEDEV parameter) resides on a
compressed NTFS file system. This problem occurs only if the file has
more than 4 GB of data.
Workaround:
Use tape drives to back up a large amount of compressed data. If
you use ontape to back up data to files, use
uncompressed files only.
Information Related to Optical Libraries
========================================
Clash of Optical Library DLL with Engine's Shared Memory
--------------------------------------------------------
Informix Dynamic Server might fail to initialize the shared memory
with the following error in the database server log file:
15:34:29 shmat: [EINVAL][22]: shared memory base address illegal
15:34:29 using 0xc000000, needs 0x10020000
15:34:29 mt_shm_init: can't create resident segment
This error can happen if the STAGEBLOB and OPTICAL_LIB_PATH are set.
This error occurs because Windows NT loads the optical DLL in the
server address space which clashes with the shared memory address.
You can rebase the DLL using the "rebase" utility supplied with the
Microsoft Platform SDK. The preferred address to rebase the DLL is
between 0x02000000 and 0x03000000. Alternatively, you can change the
SHMBASE to a higher value, but this might reduce the size of
the shared memory that the server uses. You can rebase any DLL
that might clash with the shared memory address space as well as
the optical DLL.
Information Related to Microsoft Clusters
=========================================
Informix Storage Manager and Microsoft Clusters
------------------------------------------------
After the Informix Dynamic Server fails over from node1 to
node2, users cannot restore from the backup made on node1, and
vice versa. In summary, backups made using ON-Bar and Informix
Storage Manager on any node can be used to restore only on the same
node.
Viewing Error Messages from Cluster Service
-------------------------------------------
Informix Database Server Cluster Resource logs error messages in the
default cluster debugging log file.
To enable the cluster debugging log:
* Set the CLUSTERLOG environment variable to a complete path
identifying the location of the log file. The default name for the log
file is cluster.log and the default location is the cluster directory.
* The maximum size of the log file can be set in the ClusterLogSize
entry in the cluster database under HKEY_LOCAL_MACHINE\Cluster. The
size is a DWORD value that indicates the number of megabytes that the
log file can hold. If this value is set to zero, logging is disabled.
Use of Named Pipe Protocol on Informix Dynamic Server on a Cluster
------------------------------------------------------------------
In a cluster, the host name in the SQLHOSTS entry for the Named Pipe
protocol should be the name of the computer on the node.
If you use the TCP-SOCKETS protocol, use the cluster name instead
as the host name in the SQLHOSTS entry. (Use setnet32 to update the
host name.)
Interrupting Long Queries
-------------------------
The SQLBREAK functionality is supported on IDS 7.31.TC1. SQLBREAK
enables you to use the family of functions
sqlcancel(),sqlbreak(),sqlbreakcallback() to interrupt long queries
being executed using NT clients.
To enable this functionality, install the Microsoft 'teardrop' hotfix
on Windows NT 4.0 SP3 - you can obtain the hotfix from the following
URL:
<ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/nt40/hotfixes-postSP3/teardrop2-fix/>
X. KNOWN DEFECTS in 7.30 WITH WORKAROUNDS
KNOWN DEFECTS IN 7.30.UC1 (UNIX) WITH WORKAROUNDS
=================================================
Feature Request
---------------
83394 DUE TO 7.3 ONLINE PRODUCT NAME CHANGE, ONSTAT'S OUTPUT WILL DIFFER.
In 7.30, onstat - returns "Informix Dynamic
Server." Under 7.2x, onstat - returns "INFORMIX-Online."
Some scripts failed because of this database server
name change.
W/A: Be sure to update your scripts for on* utilities such as onstat
if they use the database server name. (The 7.3x database server
was renamed to Informix Dynamic Server.)
Bugs which remain in Informix Dynamic Server - ON-Archive
----------------------------------------------------------
34406 ONARCHIVE /NONOTIFY FLAG DOES NOT WORK.
W/A: ON-Archive always generates a mail even if you use the /NONOTIFY flag.
Refer to Backup and Archive Guide, page 6-20.
Bugs which remain in Informix Dynamic Server - OnSNMP
------------------------------------------------------
89630 ONSNMP/NT TIME ENTRIES FOR SOME MIB TABLES SHOW INCORRECT YEAR;
ER GUI SHOWS "DATA NOT AVAILABLE" AS A RESULT.
Invalid times in the ER Monitor are shown as "Data not available."
This problem only exists on NT.
W/A: No workaround available.
89461 SNMP TABLES CAN'T BE QUERIED AFTER REPLICATE/GROUPS ARE DELETED
WITH ER TOOLS.
Using the ER Manager to delete replicate/groups will cause the
ER Monitor to time out.
W/A: The server must be taken offline and then back online before the
ER Monitor will work again.
Bugs which remain in Informix Dynamic Server - Admin Utilities
--------------------------------------------------------------
86344 ONBAR -R -N LEAVES DBSPACE DOWN AND CHUNKS INCONSISTENT IF
DBSPACE WAS DROPPED.
If a dbspace has been dropped, onbar -r and
onbar -r -t <time to before drop> won't restore it.
W/A: determine in which log file the drop space occurred (use onlog).
onbar -r -n <log>
This will restore all dbspaces. The dropped
dbspace has been re-created, but it is offline
(use onstat -d to verify).
onbar -r <dropped dbspace>
Restores the data in the dropped dbspace.
IMPORTANT: To prevent this problem in the future, be sure to perform a
level-0 backup after adding or dropping a dbspace, chunk, or log, or
after changing the size or location of the physical or logical log.
87991 ONCHECK -PT 0X100002 OR ONCHECK -PT 0X100001 FAILS ON
DATABASE TABLESPACE OR TABLESPACE TABLESPACE : ERROR: TBLSPACE
100002 NOT FOUND IN ANY DATABASE.
Oncheck is currently not able to check the tablespace
tablespace.
W/A: This will be fixed in a future release.
86322 ONSTAT -D RETURNS INCORRECT PATHNAME WHEN DBSPACE IS CREATED.
W/A: If DBSPACES are created using relative path name, ONSTAT -D will
bring an incorrect information about the absolute path of these
dbspaces. An immediate work around is to use absolute path during
dbspace creation. (Relative pathnames are NOT supported for chunks.)
89788 RESTARTED WHOLE SYSTEM RESTORE MAY LEAVE A DBSPACE OFFLINE,
DEPENDING ON
WHEN THE SERVER CRASHED (THE EXACT INSTANCE OF SERVER CRASH IS
SIGNIFICANT).
Here's the scenario:
The user starts whole system restore with RESTARTABLE_RESTORE ON.
Whole system restore fails.
User restarts whole system restore with onbar -RESTART.
server crashes in the short time between when ON-Bar has passed
the last buffer to the server and committed the restore,
but the server has not yet completely finished processing
the buffer.
The effects of this bug are that neither ON-Bar nor the server is
aware that the restore failed. There will be no errors from either.
When the server is brought to on-line or quiescent mode, one space
will be down.
W/A: If it's important that this is a whole system restore, then you
should start over with onbar -r -w. Otherwise, you can just restore the
down space with onbar -r <space> (this will automatically perform a
logical restore as well).
58066 CANNOT DO A LEVEL-1 BACKUP AFTER A LEVEL-0 COLD RESTORE.
Users cannot take a level-1 or 2 backup after a level-0 or
a level-1 restore. They will get an error such as:
"No level-0 archive exists; only level-0 archive is allowed."
W/A: They will always have to take a level-0 backup after a restore.
90881 EXECUTING A SECOND COMPLETE WHOLE SYSTEM RESTORE RESULTS IN ALL THE
BLOBSPACES BEING DETECTED AS OFFLINE.
This is the nature of blobs. If you back up or salvage logs and
a blobspace is down, you might not be able to restore that blobspace.
This has been documented and true since blobs were invented.
ON-Bar writes a warning message so that you know what is going on.
The reason you see a warning message saying that blobs are
down when they really are not and no message when the blobs
really are down is because the oncfg file does not have
the latest data about the state of blobs. If the server crashes,
it might not be able to update the oncfg file, so when a cold restore
is started, the server thinks that a blob is down when
it is really up and visa versa. The contents of the oncfg file are
not guaranteed.
W/A: Use the onstat -d option to verify the status of blobspaces
if you are not sure whether they are on-line or down.
Bugs which remain in Informix Dynamic Server - CSS/CSM
------------------------------------------------------
74999 $CONNECT TO DBNAME@SERVERNAME FAILS IF THE DBNAME CONTAINS
CHARACTERS THAT ARE NOT VALID IN THE CLIENT LOCALE (AFTER
CODE SET CONVERSION).
When client locale and database locale are different and
the database locale codeset contains characters that are not
valid in the client codeset, an SQL statement of the form
$CONNECT TO "DBNAME@SERVERNAME" returns a -909 error (Invalid
database name format).
W/A: Split the CONNECT TO "DBNAME@SERVERNAME" statement into two
statements as follows:
$CONNECT TO "@SERVERNAME";
$DATABASE DBNAME;
Bugs which remain in Informix Dynamic Server - Internal Services
----------------------------------------------------------------
85396 TRANSACTION CAN RELEASE SHARE LOCKS TOO SOON WHEN DELETING FROM A
TABLE USING PAGE LEVEL LOCKING.
A race condition exists such that when deleting from a page locking
table, the delete can return the following errors:
240: Could not delete a row.
126: ISAM error: bad row id
W/A: The row was deleted by another session before the initial transaction
could perform it.
Bugs which remain in Informix Dynamic Server - Enterprise Replication
---------------------------------------------------------------------
For information about Enterprise Replication bugs with workarounds, see
Section VI, "ENTERPRISE REPLICATION INFORMATION."
Bugs which remain in Informix Dynamic Server - RSAM Archive Subsystem
---------------------------------------------------------------------
90519 USING EBR OR ARCHIVING LEVEL-0 VERY INFREQUENTLY CAN CAUSE ARCHIVES TO
MISS PAGES OR RESULT IN FAST RECOVERY ERRORS.
W/A: Take a level-0 backup of all (non-temporary) storage spaces
with reasonable frequency. The definition of "reasonable"
varies with OLTP load, but a good rule of thumb would be to
take a level-0 backup at least every 2-3 weeks. This
recommendation applies especially to storage spaces that
are fairly static.
Note that even when using External Backup and Restore (EBR),
a regular (non-external) level-0 backup should be performed
at least every 2-3 weeks, to avoid bug 90519.
KNOWN DEFECTS IN 7.30.TC1 (Windows NT) WITH WORKAROUNDS
=======================================================
84955 DURING MOVE GROUP OF INFORMIX DYNAMIC SERVER ON A CLUSTER,
SOMETIMES GENERATES A "CORRUPT DISK" WARNING.
When the Informix Server running on a node is moved over to
the second node, the following warning message appears:
"Oninit.exe Corrupt disk
File System structure on the disk is corrupt and unusable.
Please run chkdsk utility on the volume."
W/A: This a spurious error; the Informix Dynamic Server successfully
fails over. There is no disk corruption and no loss of
data. Remove the message box by clicking "OK".
85122 DB-ACCESS CLIENT FROM SPARC MACHINE LOSES CONNECTION IF CONTROL-C
IS PRESSED WHILE WORKING INTERACTIVELY AGAINST A INFORMIX DYNAMIC
SERVER ON A MICROSOFT CLUSTER.
W/A: The user can reconnect and continue.
86433 ONLOAD DOES NOT RETURN PROPER ERROR CODE WHEN AN ERROR IS
ENCOUNTERED IN READING THE TAPE DEVICE.
W/A: The error could be caused by incorrect tape path, tape contents,
or tape block size. Make sure these values are correct and run
onload again.
89628 DB-ACCESS FAILS TO START WITH ERROR "COULD NOT INITIALIZE THE
SECURITY SUBSYSTEM", WHEN THE ENVIRONMENT VARIABLE INFORMIXSERVER
SET TO A REMOTE SERVER.
W/A: DB-Access is failing because it tries to access the following
non-existent registry key and sub keys:
HKEY_LOCAL_MACHINE\Software\Informix\OnLine\<%INFORMIXSERVER%>
<%INFORMIXSERVER%> is the value of the environment variable
INFORMIXSERVER.
A possible workaround is to use a registry editor to create this key
and restore the local INFORMIXSERVER sub key over it. Use this
workaround only if you plan to use this computer solely as a client
to a remote server, because Informix utilities run on or against the
local computer would see a server that does not exist.
Make sure that you back up the
HKEY_LOCAL_MACHINE\Software\Informix registry key before modifying
any Informix registry settings.
Bugs which remain in Informix Dynamic Server - HDR Area
-------------------------------------------------------
89667 SECONDARY SERVER HANGS AT CHECKPOINT DURING FAST
RECOVERY AFTER THE PRIMARY IS KILLED AND ONMODE -D
STANDARD IS ISSUED ON SECONDARY WITH DR_AUTO=0.
W/A: This problem manifests in an HDR pair when the primary is blocked
for a log backup and the secondary is awaiting a checkpoint record from
the primary. If the primary is killed or crashes in this situation
and the secondary is brought to standard mode using onmode -d, restart
the secondary and do a log backup. Then change the secondary to the
standard mode using the onmode -d command.
89697 PRIMARY CRASHED WITH EXCEPTION DURING RECOVERY FROM
TAPE IN DR_AUTO=0 AND WHEN THE TAPE IS MISSING/EMPTY.
W/A: This problem occurs in an HDR pair when the primary server is doing a
crash recovery after it has crashed and the secondary is in standard
mode. When the primary is brought up, if the tape is missing/empty,
it might crash with an assertion.
The workaround is to make sure a correct tape is used for the
recovery of the primary in such a situation.
90919 PRIMARY HANGING AT FAST RECOVERY(CP) WHILE SECONDARY IS OUT OF SYNC
WITH DRAUTO=0
If the Secondary is allowed to time-out when restarting HDR after the
Primary failed and the Secondary was changed to a Standard database
server, the Primary can report "DR: Failure recovery error (2)" in the
message log and stay in Fast Recovery, while the Secondary reports
"DR: Server state incompatible".
W/A: When issuing the command "onmode -d secondary ..." on the Secondary
database server, do not allow the command to time-out and return to
the command prompt while it tries to connect to the Primary database
server.
If this error does occur, bring the Primary instance down, re-issue
the
"onmode -d secondary ..." command on the Secondary, and re-start the
Primary before the onmode command times out on the Secondary.
XI. KNOWN PROBLEMS WITH THE 7.31 BUILDS
The following are known problems with the NT 7.31 build:
1. B104074 (PLOAD) ONPLOAD DOESN'T WORK. CREATES AN EMPTY LOG FILE & DOESN'T
LOAD ANY ROWS.
Effect: onpload, WinPload utilities do not work. WinPload is in IECC.
2. B104076 (INSTALL) REGRESSION: SERVER UNINSTALL REMOVES INFORMIX PROGRAM GROUP
EVEN IF CLIENTSDK HAS BEEN INSTALLED IN THE SAME GROUP & HASN'T YET
BEEN UNINSTALLED.
Effect: ClientSDK program group icons will not be visible after a server
uninstall, if the server and client exist on the same machine, and
have been installed in the same program group.
Workaround: Install ClientSDK product in a different program group than the
one in which the IDS 7.31 server is installed.
3. B103371 (CDR/ASF) LISTENER THREAD READ ERROR CAUSES CONNECTION ATTEMPT BY
SECOND SERVER TO SYNCHRONIZE GLOBAL CATALOG TO FAIL AND SHUTDOWN ER.
Effect: Defining Enterprise Replication through RepMan or the
command line fails.
4. B103060 (INSTALL) INSTALLING 7.31 SERVER AFTER CLIENT SDK 2.20 OVERWRITES
FILES CAUSING AMONG OTHERS SETNET32 TO FAIL.
Effect: If a version of ClientSDK is installed in the same directory
(INFORMIXDIR) as the one used for a subsequent server installation,
I-Connect dlls iregt07b.dll and isqlt09a.dll are overwritten by
the server install. If the ClientSDK is of a different version, client
utilities such as setnet32 might malfunction.
5. B104031 (CDRGUI)LOG CORRUPTION DETECTED OR READ ERROR OCCURRED WHILE SNOOPING
LOGS.
Effect: Logical log corruption or read error upon defining replication
between multiple servers. An error message will display in
the online message log.
6. B97549 (DB-ACCESS) INSTALLING IDS 7.30 ON NT WHEN LOGGED ON AS ADMINISTRATOR
WITH ROLE SEPARATION ACTIVE WILL NOT ALLOW YOU TO RUN DB-ACCESSDEMO7.
Effect: The user cannot perform database activities as Administrator when
the server has been installed with role separation enabled (role
separation is an installation option).
7. 104237 (Silent Install) IN THE META-BUNDLE, IDS INSTALLATION FAILS IN THE
SILENT MODE IN BOTH 7.30 AND 7.31.
Effect: Silent installation cannot be done if an already installed version
of the IDS 7.3x serverdoesn't exist on the machine.
Workaround: Install IDS7.3x server once in interactive mode. Subsequent
installation can be in silent mode with the required parameters stored in
the playback.ini file. To store the parameters in playback.ini, use
the following command in the directory containing the IDS 7.31 media:
setup.exe -s <path to playback.ini> -l <logfile> -apw "<informix password>"
XII. CUSTOMER-REPORTED BUGS FIXED AFTER 7.30.UC1 (UNIX)
Note: The ESQL and TP/XA bugs are not described here because these
products are no longer shipped with the database server.
For information, refer to the client release notes.
PRODUCT NAME : BACKEND
BUG NO. DESCRIPTION
----------------------------------------------------------------------
79464 INCORRECT RESULT RETURNED BY QUERY ON A VIEW CONTAINING
A PROCEDURE CALL THAT HAS A QUERY.
85352 PERFORMANCE DEGRADES SIGNIFICANTLY BETWEEN V5.* AND
V7.* ON A QUERY THAT USED A DYNAMIC COMPOSITE INDEX
IN VERSION 5
91138 INCORRECT RESULTS RETURNED BY A QUERY WITH OR CLAUSES
IN A SPECIFIC SCENARIO
91402 SELECT RETURNS WRONG NUMBER OF ROWS WITH SUBQUERY
FLATTENING
91404 SELECT ... FOR UPDATE IN KEY-FIRST CASE DOES NOT
LOCK ROW BEFORE EVALUATING KEY-FIRST FILTER IF INDEX
IS DETACHED
91913 UPDATE-SELECT SHOWS SIGNIFICANT PERFORMANCE REDUCTION
FOR A PEOPLESOFT QUERY COMPARED TO 7.23
92920 GENLIB DOES NOT ACCEPT DD MMMYYYY AS A VALID INPUT
DATA FORMAT FOR DATE COLUMNS--ERROR RECEIVED IS
-1218 STRING TO DATE CONVERSION ERROR
93161 SLOW INDEX PATH CHOSEN BY OPTIMIZER WHERE AUTOINDEX
IS FASTER. REGRESSION INTRODUCED BY FIX TO B75345
94722 SAP-BIW: INCORRECT JOIN SELECTIVITY USED IN OPTIMIZER
(CHKFLTRS())
94738 SAP-BIW: INCORRECT WEIGHTING FACTORS USED FOR NEW-
GENERATION HARDWARE IN COST-BASED QUERY OPTIMIZER
97765 ONLINE HANGS AFTER REENTRANT CALL TO PUT_READY_TCB
IN ADM VP CAUSED BY MT_EXEC'ING A STORED PROCEDURE
SYSTEM() CALL
98572 OPTIMIZER IS TRUNCATING LOWER INDEX FILTER CAUSING
INCORRECT DATA TO BE RETURNED.
100238 SELECT WITH SUBQUERY RETURN DUPLICATES OF THE SAME
ROW.
101518 PERFORMANCE DEGRADATION WITH FIRST_ROWS HINT
PRODUCT NAME : DB-ACCESS
BUG NO. DESCRIPTION
----------------------------------------------------------------------
88701 839 ERROR AND CORE DUMP FROM DB-ACCESS WHEN USING NON-
EXISTENT TABLE NAME IN TABLE/TABLE_INFO. (SEEMS
TO HAPPEN IF TABLENAME > 18)
89682 GETTING ERROR -454('LOC_READ()' FAILED) AND -847
(ERROR IN LOAD FILE LINE NUMBER) WHEN LOADING INTO
TEXT TYPE COLUMN.
90389 DB-ACCESS CANNOT RENAME COLUMN FROM THE MENU ON ANSI
DATABASES IF THE TABLE IS OWNED BY SOMEONE ELSE
93445 MISLEADING SYNTAX "ERROR IN LINE 1, ETC..." WHEN
SELECTING TEXT COLUMNS IF DBTEMP HAS INCORRECT PERMISSIONS
SET IE 755.
94600 UNLOAD OF TEXT COLUMN TYPE USING JAPANESE LOCALE
MAY GIVE ERROR -451
95300 UNLOAD/LOAD DO NOT COMPLAIN WHEN MULTI-BYTE DELIMITER
IS USED. AN ERROR MESSAGE SHOULD BE RETURNED BECAUSE
THIS IS NOT ALLOWED
97167 SETTING CLIENT_LOCALE=EN_US.UNICODE WILL CAUSE DB-ACCESS
TO SEGV
98604 DB-ACCESS CORE DUMP AFTER YOU FAILED TO INSERT HANKAKU-
KANA DATA
PRODUCT NAME : DBATOOLS
BUG NO. DESCRIPTION
----------------------------------------------------------------------
86105 625 ERROR WHEN ATTEMPTING TO CREATE A TABLE--CAN
ACTUALLY PREVENT DBEXPORT/DBIMPORT FROM WORKING
91302 THE FIX FOR B 79838 CAUSES A REGRESSION IN DBLOAD.
WHEN USED AGAINST SE, DBLOAD EMITS A "SYNTAX DISALLOWED
IN THIS SERVER" ERROR.
93360 DBLOAD RUNS SLOWER AS COMMIT POINT INCREASES
PRODUCT NAME : ESQL/C
BUG NO. DESCRIPTION
----------------------------------------------------------------------
42965 GET DIAGNOSTICS RETURNS ZERO EXCEPTIONS AFTER FETCHING
THE SECOND ROW FROM THE TABLE.
70596 -406 MEMORY ALLOCATION ERROR FOR PUT OF INSERT CURSOR
WHEN CODESET CONVERSION REQUIRED
85468 THE CUSTOMER RECEIVES A 25580 SYSTEM ERROR OCCURRED
IN NETWORK FUNCTION OR SEGV ON EXIT WHEN ISSUING
A ^C IN DB-ACCESS
87345 7.22.UC1 - SOLARIS 2.5.1 - IMPLICIT CONNECT AFTER
EXPLICIT DISCONNECT GENERATES ERROR 1803.
PRODUCT NAME : ISM
BUG NO. DESCRIPTION
----------------------------------------------------------------------
91577 ON SP2 NODE, ISM HAS ERRORS DURING CONFIGURATION,
THEN ONBAR -B FAILS WITH FOLLOWING ERROR: XBSA ERROR:
(BSACREATEOBJECT)
PRODUCT NAME : ONLINE
BUG NO. DESCRIPTION
----------------------------------------------------------------------
33292 MULTIPLE PROCESSES CALLING SAME STORED PROCEDURE
RETURNS ERRORS -211/-107
43670 PHYSIO: NOT OPEN ERROR IF TEMPDBS CHUNK FAILS SANE_
CHOPEN FROM INITCHUNK() REBUILD OF TEMPDBS LATER
IN INIT_DBSPACE() WILL NOT FIX THIS
48531 THE SECONDARY SERVER HANGS ON A CHECK POINT DURING
FAST RECOVERY IF THE INFOMRIXSERVER ENVIRONMENT
VARIABLE IS NOT SET TO XXTTYPE = ONTILTCP.
58663 CDR: ONSTAT -Z DOES NOT ZERO OUT ANY OF THE CDR STATISTICS
71014 ONARCHIVE FAILS WHEN ONCATALGR DIES WHEN IT RECEIVES
SIGPIP - SIGNAL 13
71732 OPTIMIZER SELECTS A QUERY PATH FOR EXECUTION FROM
AVAILABLE CHOICES EVEN WHEN ITS EVALUATED COST IS
NEGATIVE I.E., INVALID.
72146 ASSERTION FAILURE: BUS ERROR/SEGMENTATION VIOLATION
WHEN TRYING TO PERFORM A LEVEL-1 ARCHIVE
73237 SYSTEM HANG, NO THREADS SHOW AS RUNNING ON THE VP,
ONLY READY THREADS. THE VP IS ALSO CLOCKING A LOT
OF CPU TIME.
73376 CANNOT CREATE DATABASE WHEN USING DANISH ISO 7-BIT
CODESET
76354 CODE INSPECTION BUG: TLI/SOCKET LISTENER CAN YIELD
FOR UP TO 3 MINS AND PREVENT FURTHER CONNECTION
ATTEMPTS TO HANG.
76423 A JOIN SELECT WITH THREE TABLES FRAGMENTED OVER 90
DBSPACES AND USING A HUGE IN CLAUSE CAUSE ONLINE
HANG WITH OUT OF VIRTUAL SHARED MEMORY MESSAGE
77476 <GEODETIC> ASSERT FAILURE: ROWID X OT FOUND FOR DELETE
IN PARTNUM WHEN CONSTRAINTS ARE VIOLATED - GEOPOINT
DATA TYPE INVOLVED
79416 ASSERT FAILED: PTHDRPAGE:PTALLOC:BAD PARTN PAGE WHEN
CALLING XA_START() AFTER DROPPING A TEMPORARY
TABLE FOR WHICH A STATEMENT HAS BEEN PREPARED
79489 -1213 CHARACTER TO NUMERIC CONVERSION ERROR WHEN
DOING SIMPLE SELECT OF A MONEY TYPE FIELD WITH WHERE
CLAUSE FROM ONLINE 7 TO ONLINE 5 ENVIRONMENT
80017 A CERTAIN CREATE TRIGGER CREATED BY DBSCHEMA RETURNS
THE SERVER NAME AS PART OF THE TABLE NAME.
81031 NEW: MAIN IN A FLOAT COLUMN THE LIMIT OF VALUE INSERTED
IS DIFFERENT FOR LOAD CLAUSE AND VALUES CLAUSE,
E.G., LOAD TAKES 1.0E-308, VALUES DOESN'T (EW)
81210 NEW: MAIN A HEURISTICALLY ROLLBACKED TRANSACTION PRODUCES
WRONG MESSAGE IN LOG FILE WHEN SERVER IS
RESTARTED, SERVER BLOCKED AT LONGTX
81526 GF_INIT_GLO MAY CLOSE NEEDED FILES WITH ITS CURRENT
IMPLEMENTATION... INIT_ALARM FAILED MESSAGES ARE
1 POSSIBLE INDICATION OF THIS PROBLEM
83542 REGRESSION: SERVER SHUTS DOWN WITHOUT ANY MESSAGE
IN ONLINE.LOG WHILE MULTIPLE PROCESSES ARE DOING
INSERT/UPDATE/DELETE IN FAST RECOVERY TEST
84275 IN COMPUTERS WITH MULTIPLE CPUS BUS CONTENTION ON
THE NETWORK VARIABLE NETGLOBAL->TIME_OF_DAY IS SEEN
84276 NETWORK STATISTICS GENERATE HIGH BUS CONTENTION WHEN
RUNNING ON A COMPUTER WITH SEVERAL CPU VPS.
84526 PERFORMANCE OF QUERY UPDATING MANY KEYED COLUMNS IS
THROTTLED BY BTCLEANER
85128 HDR SECONDARY HANGS AFTER CONNECTING TO PRIMARY WHEN
LOCAL PROTOCOL IS IPCSHM
85268 NEW SERVER CRASHED IN MAKEINDEX FUNCTION
85470 IF PDQPRIORITY IS SET TO 100 AND DS_MAX_QUERIES IS
SET TO 1 AND NUMCPU VPS > 1 THEN ALL CREATE INDEX
STATEMENTS FAIL WITH SQL 212 ISAM 0
86104 NEW: SERVER RETURNS ERROR 105 IF 'ALTER FRAGMENT DETACH'
IS INTERRUPTED BY USER
87185 DATABASE WILL BE UNACCESSIBLE AFTER MIGRATION TO 7.2X
VERSION IF ANY TBLSPACE TBLSPACE PAGE IS
FILLED UP AND SLOT 2 DOESN'T HAVE SPACE
87600 BAD QUERY CAN GRIND ENGINE TO HALT IF SINGLECPU VP,
IT TAKES 60 SECS TO LOG ON TO THE ENGINE.
87615 CONNECTIONS VIA SYNONYMS TO 5.X AND 7.1X SERVERS ARE
2-3 TIMES SLOWER FROM 7.23 SERVER THAN FROM 7.1X
SERVER
87947 SYSDATABASES SHOWS INCORRECT CREATION DATE FOR DATABASE
CREATED AFTER 16:00
88414 UNINITIALIZED CHUNK POINTER CAN CAUSE SEGV IN INIT_
PHR DURING PHYSICAL RECOVERY OF ROOTDBS
88702 IF RECOVERY FAILS AND THERE IS A SUBSEQUENT SUCCESSFUL
RECOVERY, THE STATE OF CDR IN THE CDRSTATE
TABLE ISN'T RESET CORRECTLY.
88739 LEGACY: SERVER GIVES SQL ERR 229 AND ISAM ERR 131
WHILE EXECUTING SELECTS INVOLVING CREATION OF TEMP
TABLES. - MA-SS
88943 NEW: SERVER CRASHES DURING ORDERED MERGER USED FOR
SELECT WITH CORRELATED SUBQUERY USING EXISTS
89175 BAD MEMORY POINTER IN MT_SHM_FREE DUE TO LOCK TABLE
OVERFLOW
89287 73BETA: SEQSCANS FROM SYSPTPROF IN SYSMASTER IS
INCREMENTED WHEN A KEYFIRST INDEX SCAN IS DONE
89521 LARGE QUERY LARGE WHERE CLAUSE WITH ORDER BY CAUSES
MEM LEAK IN RALLOC OPTIMIZER DOES NOT FINISH
OPTIMIZING.
89597 ONLINE CRASH WITH MESSAGE "MT.C LINE # ... INVALID
MUTEX TYPE " AS ONLY INFORMATION IN MESSAGE LOG.
89729 GLS: WITH JA_JP.UJIS TO DB_, CLIENT_ AND SERVER_LOCALE,
ONCHECK -CI SYSUTILS RETURNS ERROR. ALSO CAN'T
CONNECT THE DB FROM DB-ACCESS
89756 7.23.TC9 ER - TIME BASED REPLICATION FAILS TO REPLICATE
UNDER ANY INTERVAL AFTER SECOND OR THIRD INS
ERT-REPLICATION STOPS AFTER THIRD INSERT
89842 QUERY WITH EXTEND SYNTAX DOES NOT YIELD TO OTHER
SQLEXEC THREADS WITH ONLY ONE CPU VP
89957 LEGACY: SECONDARY FAILS DURING INDEX RECOVERY AFTER
BECOMING READ ONLY.
89978 FRAGMENTS ARE NOT BEING ELIMINATED FOR CERTAIN EXPRESSIONS
INVOLVING DATE COLUMNS.
89988 DATA SYNC NOT ELIMINATING INDEX FRAGMENTS DURING
COLLISION DETECTION
90001 NEW AF IN SECONDARY SERVER PAGE CHECK ERROR IN
PHPOSITION:ISFIRST:BAD PAGE
90052 SETTING CLEANERS ONCONFIG PARAMETERS TO MAX VALUE
(128) CAUSES PHYSICAL LOG SIZE TOO SMALL ERROR MESSAGE
TO APPEAR
90123 RAPID INSERTS/DELETES OF THE SAME P.K. ROW CAN CAUSE
SEGV IN GROUPER IF ROW CONTAINS BLOBS
90343 LEGACY: ENGINE CRASHES WHILE STOPPING MIRRORING IF
MIRROR RECOVERY IS STILL IN PROGRESS (EW)
90379 LEGACY: SERVER HANGS IN CKPT REQUEST WAITING FOR
THE BACKUP TO BE TAKEN WHEN THERE ARE FREE LOG FILES
AVAILABLE.
90425 SETTING DBSPACETEMP ENV VARIABLE WITH OPTICAL VP
LEADS TO MT_BIND ERROR: INVALID ARGUMENT FOLLOWED
SHORTLY BY LISTENER THREAD SEGV OR BUS IN T_FREE
90434 LEGACY: REMOTE SELECT FAILS WITH ERR # 529 IF SERVER
HAS MORE THAN ONE NET VPS
90520 ENGINE HUNG ON CHECKPOINT: ARCBACKUP WAITING ON
CHECKPOINT WHILE IN CRITICAL SECTION.
90844 MIGRATING A ONLINE SYSTEM WITH BLOBSPACES TO 7.23
CAN BREAK THE ARCHIVE WITH BLOB PAGE CHECK ERROR AT
RSARCBU.C:3756
90845 PAGE CHECK ERROR IN BTPREV: BAD CURR SLOT WHEN DELETING
FROM A TABLE WITH DESCENDING INDEX. APPLICATION
RECEIVES -243/-172 ERRORS.
90906 CRASH/MEM ASSERTION POSSIBLE WHEN INTERRUPTING A
CLIENT IN THE PROCESS OF CONNECTING.
90909 ATTEMPT TO PUT THE ENGINE IN QUIESCENT MODE FAILS
SOMETIMES LEAVING SYSTEM IN "SHUTTING DOWN" STATE
WITH USERS THREADS THAT DON'T TERMINATE.
91170 REGRESSION: INSERTION INTO 2 BIT BITMAP TABLES CAN
RESULT IN CORRUPTION, WITH ASSERTION FAILURE AND
WARNINGS IN THE ONLINE LOG
91185 ONLINE EXECUTING REMOTE STORED PROCEDURE GIVES ERROR
-403
91235 UNABLE TO ARCHIVE THE SYSTEM IF MORE THAN 10 PAGES
ARE CORRUPT
91286 ENGINE GOES DOWN DUE TO INTERRUPTED SYSTEM CALL ERRNO=4,
IN FUNCTION SYSV_NSF_SENDFD
91291 LATCH DEADLY EMBRACE BETWEEN VP_LOCK AND NOTIFYVP_
LOCK INVOLVING ADM VP AND CPU VP
91299 212/113 ERROR WHEN CREATING AN INDEX ON A TEMP TABLE
FRAGMENTED ACROSS MULTIPLE TEMP DBSPACES IF DATABASE
OR TABLE DOESN'T USE LOGGING
91340 PRECISION VALUES FOR SUM'S ARE TOO SMALL FOR REALISTIC
QUERIES.
91401 NEW: SERVER CRASHED WHILE CREATING INDEX ON DATE
COLUMN WITH ERROR IN FRAGMENTATION EXPRESSION
91495 SERVER CRASHES WITH SEGV IN IS_CONST() WITH CERTAIN
LITERAL EXPRESSIONS
91496 ONLINE SECURITY LEAK USERS WITH ONLY CONNECT PERMISSION
CAN MANIPULATE / DESTROY ANY DATABASE DATA
USING STORED PROCEDURES
91499 LOGICAL RECOVERY AFTER PHYSICAL RESTORE OF WHOLE
SYSTEM TRIES TO START WITH LOG 0 POSITION 0X0
91560 7.24.UC3, OPTIMIZER PICKS WRONG FRAGMENT FOR A NON-
SUBSTRING FRAGMENTED TABLE WHEN SELECT INVOLVES A
SUBSTRING WHERE CLAUSE
91607 TWO QUERIES WAITING ON READY QUEUE: A ON MEMORY GATE,
B ON THE PRIORITY GATE. KILLING A, THERE IS
ENOUGH MEMORY AND SCANS, BUT B DOES NOT RUN
91635 SELECT FROM CERTAIN SYSMASTER TABLES (SYSSQLSTATS)
MAY GENERATE A SEGV
91696 UPDATE OF BLOB COLUMNS USING KEYFIRST SCAN CRASHES
THE SERVER
91697 A EXISTS QUERY WITH VIEW CAUSES A CORE DUMP
91721 SELECTS WITH A SUBQUERY THAT GET RE-OPTIMIZED CAN
CAUSE MEMORY CORRUPTION BECAUSE THEY ACCESS FREED
MEMORY
91788 AFTER REPEATEDLY DEFINING AND DELETING SEVERAL REPLICATION
OBJECTS THE SERVER RUNS OUT OF SHARED MEMORY
91823 ERROR CHECKING OF DATE FIELD DOES NOT CATCH INSERT
OF '01/01/TEST97'
91857 IN CASE OF SELECT ... FOR UPDATE AND KEY-FIRST FILTER
U-LOCK IS NOT RELEASED AT SUBSEQUENT FETCH AND
FOR SOME NON-QUALIFYING ROWS (DATA FILTER)
91875 UNINITIALIZED VARIABLE IN OPTIMIZER CAN CAUSE CORE
DUMP
91889 LOG EVENT PROCESSING TAKING TOO MANY RESOURCES IN
CM AND DATA-SYNC THREADS
91925 103 ISAM ERROR RETURNED WHEN INDEX ON TEMP TABLE IS
CREATED, COMMITTED, THEN DROPPED AND ROLLED BACK,
THEN SELECT FROM WHERE KEY COL = VALUE
91979 SUBQUERY CACHE FEATURE DOESN'T WORK(EFFECTIVELY DISABLED)
ON THE 2ND EXECUTION OF A PREPARED QUERY.
PERFORMANCE PROBLEM.
92118 ENGINE CRASH OPTIMIZING QUERY WITH WHERE CLAUSE OF:
WHERE COL LIKE "%XXX%" ESCAPE '\'
92189 EXECUTING UPDATE STATISTICS ON A TABLE WITH INDEX
CRASHES THE SERVER. THIS IS A TEST STOPPER FOR PEOPLESOFT
APPLICATIONS
92460 SOLARIS STACK TRACES DO NOT SHOW THE MOST IMPORTANT
FUNCTION OF ALL; THE FUNCTION/LOCATION OF THE
SEGV/BUS ERROR IS MISSING.
92478 NEW: 'SELECT PROC1(MIN(CHAR_COL)) FROM TAB' GIVES
ERROR -294 IN 7.30, BUT NOT IN 7.24 OR 9.20.
92522 PERFORMANCE BOTTLENECK WHEN USING MOD FUNCTION ON
FRAGMENTED TABLES
92585 ROLLBACK ERROR 134; ASSERT FAILED: LOGICAL LOGGING
ERROR IN 'ROLLBACK' LEADS TO SERVER CRASH WHEN RUNNING
OUT OF LOCKS FOR 100 REMOTE CONNECTIONS
92594 ERROR -111 FROM DATABASE
92602 CALCULATION FOR FULLNESS OF PAGES IN LIGHT APPEND
ALLOWS TOO MANY SLOTS ON 4K PAGES WHEN PARTITION
INCLUDES VARCHARS
92633 CONCURRENT EXECUTION OF STORED PROCEDURES IN A NON-
LOGGING DB CAN CAUSE ROLLBACK ASSERTION FAILURES
AND CORRUPTION OF SYSPROCPLAN.
92728 CDR STOP HANGS IF DDR_BLOCK IS SET
92738 IF PROGRAM DOES $DATABASE <DBNAME> AFTER A $BEGIN
WORK YOU GET -377 ERROR, BUT THE SERVER LOSES TRACK
OF A SQLISTATEMENT ID AND LEAKS MEMORY
92742 IF A SESSION EXCEEDS 32767 STATEMENT IDS THE ENGINE
WILL SEGV OR BUS ERROR AND CRASH
92746 SEGV AND/OR BAD POOL POINTER CAN OCCUR WITH CDR STOP
92779 REPEATEDLY TRYING TO OPEN A CURSOR AFTER AN ALTER
TABLE CAUSES ENGINE TO SEGV
92791 CDR NIF COMPONENT MAY COREDUMP DURING SHUTDOWN.
92905 SQL LOCKING FREED MEMORY ON DISCONNECT
92917 ROLLBACK ERROR 106: ROLLING BACK A BLDCL RECORD (RO
LLING BACK A TABLE CREATE)
93074 ROLLBACK OF TABLE DROP DOES NOT ALWAYS WORK, SOMETIMES
TABLE IS LOST WITH PTHDRPAGE:PTALLOC:BAD PARTN
PAGE FAILURE.
93107 ONLINE CAN ASSERT FAIL WITH A SEGV IN MARKBLKS WHEN
ONLINE USES A VIRTUAL SEGMENT > 2 GB
93235 BEGIN WORK WITHOUT REPLICATION DOES NOT WORK IF YOU
RAN A REGULAR TRANSACTION FIRST.
93260 NEW: INSERT INTO TEMPTAB W/ SELECT & SELECT HAS '=ANY'
CONSTANT SUBQ & SUBQ HAS 2 TABLE-JOIN GIVES WRONG
RESULT WHEN PDQ=100. WORKS FINE IF NO_SUBF SET
93372 MEMORY CORRUPTION CAN OCCUR IF A SESSION ESTABLISHES
MANY CONNECTIONS (56 OR MORE) TO REMOTE SERVERS
93383 ARITHMETIC EXCEPTION IN USRANDSAMP WITH UPDATE STATISTICS
MEDIUM - DISTRIBUTIONS ONLY
93396 7.2X ENGINE UPGRADED TO 7.3X AND THEN DOWNGRADED
USING ONMODE -B 7.2 CORRUPTS THE DBSPACE RESERVE PAGE
IF MORE THAN 28/56 DBSPACES (2K/4K PAGE)
93600 IMPOSSIBLE TO REDUCE STACK SIZE FOR THE SQLEXEC THREADS,
EITHER USING STACKSIZE IN ONCONFIG FILE OR
INFORMIXSTACKSIZE ENVIRONMENT VARIABLE
93625 ASSERT FAILED: INDEX LEFT INCONSISTENT, ROLLBACK ERROR
100 AND LOGICAL LOGGING ERROR IN
'ROLLBACK,' PANIC: ATTEMPTING TO BRING SYSTEM DOWN
93674 CRASH/MEM ASSERTION POSSIBLE WHEN INTERRUPTING A
CLIENT IN THE PROCESS OF CONNECTING WITH A BAD USER
NAME OR PASSWORD(-952). LOOKS SAME AS B9090.
93710 LBU_PRESERVE CHANGE IN $ONCONFIG IS NOT REFLECTED
IN RESERVE PAGES, ONCHECK -PR GIVES "CONFIG FILE
ERROR ON ELEMENT LBU_PRESERVE"
93716 ROLLBACK OF A STORED PROCEDURE DUE TO SQL ERROR DROPS
TEMPORARY TABLE, BUT DOES NOT REMOVE FROM THE
SESSION LIST
93881 USING AN INDEX IN THE REVERSE ORDER MAY NOT RETURN
THE CORRECT ROWS
94042 CHECKPOINT HANG STARTING PARALLEL PHASE OF ARCHIVE
BUT WITHOUT THE "C-A-X--" USER FLAG SIGNATURE OF
BUG B90520.
94047 ASSERT FAILURE: NO EXCEPTION HANDLER' WHEN CREATING
STORED PROCEDURE.
94075 CLUSTER INDEX ON A TABLE WITH AN EMPTY BLOBSPACE
FIELD RETURNS ERROR -502
94092 DELETING ALL BUT ONE ROW FROM AN INDEX DOES NOT
MERGE/SHUFFLE LEAF NODE. THIS CREATS FAT INDEXES AND
REDUCES PERFORMANCE
94138 CDR HOLDING HANG IF CDROVER_RUN REACHED IN MASTER/
SLAVE ENVIRONMENT
94197 REGRESSION: SELECT SUM() ON INTERVAL MONTH TO MONTH
GIVES -1268: INVALID DATETIME OR INTERVAL QUALIFIER
IN DB-ACCESS/DDL_2/CRK419
94358 SEGV WHEN DELETING DATA FROM TABLE WHERE INDEX CONTAINS
RECORDS > 115,000 ROWS AND KEY COLUMNS ARE BOTH
CHAR(1)
94373 SUBQUERY FLATTENING FOR UNCORRELATED SUBQUERY MAY
SLOW DOWN SOME QUERIES.
94413 IN-PLACE ALTER OF A ROW OF SIZE LARGER THAN ONE PAGE
CRASHES THE ENGINE
94422 REVERTING FROM 7.3 WITH IN PLACE ALTER TABLE DOES
NOT GIVE TABLE NAME IN ERROR MESSAGE
94595 WHEN USING A DBA PROCEDURE FROM ANOTHER DATABASE,
THE DBA ROLE IS NOT GIVEN IN THE CORRECT DATABASE
94607 -710/-101 ON SECOND OPEN/FETCH OF A CURSOR WITH LIKE
OR MATCHES CLAUSE ON ANSI DATABASES
94650 DWOOD STRESS TEST: ENGINE CRASH, INDEX CORRUPTION,
CAN'T ROLLBACK, PG_FRPTR > SLOTBEG, DOITEM FAILED
(ISERRNO=100): COULD NOT DELETE, ETC.
94656 ENGINE CAN CRASH DURING STARTUP DUE TO INTERRUPTED
SYSTEM CALL ERRNO=4 (EINTR) IN FUNCTION SYSV_NSF_
OPENSTREAM()
94660 DR_SECONDARY_PING INITIATES A DSKFLUSH() EVERY DRTIMEOUT
SECONDS WHICH CAN CAUSE PERFORMANCE ISSUES ON
THE SECONDARY SERVER.
94682 NIF RESUME CAUSES EXCESSIVE WORK TO BE DONE
94702 TEMPORARY DBSPACES NOT GETTING RESTORED TO ORIGINAL
SIZE BY BACKUP/RESTORE UTILITIES.
94719 WHEN SELECTING (ROUND X/Y) WHERE Y=0, AND WITH UNION
OF ADDITIONAL SELECT STATEMENT RESULTS IN UNPREDICTABLE
ERROR MESSAGES (ON HP)
94782 PERFORMANCE ENHANCEMENT FOR TABLESPACE BLOBS AND
FRAGMENTED TABLES
94857 SEGV OR MEMORY CORRUPTION IMMEDIATELY AFTER BACKUP
STARTED/COMPLETED MESSAGES ARE PRINTED TO THE ONLINE
MESSAGE LOG
95027 NIF HANG CAN OCCUR WITH RECONNECT AFTER NODE FAILURE
OR DIRTY LINES
95052 INCORRECT FILES/DIRECTORIES CAN BE REMOVED IF ONINIT
IS RUN WITHOUT INFORMIXDIR BEING SET
95279 ENDLESS LOOP IF SEGV OCCURS WITHIN SEGV PROCESSING
DESTROYING SHMDUMP
95336 DEFAULT QUERY PLAN HAS CHANGED IN 7.30 SEQUENTIAL
SCAN PREFERRED OVER INDEX PATH IN SOME JOINS (ALGORITHM
SEEMS TO HAVE CHANGED)
95376 SUBQUERY FLATTENING PRODUCING WRONG RESULTS WITH
EXISTS CLAUSE
95510 UNABLE TO BACKUP LEVEL 1 OR 2 ARCHIVE WITH A TEMP
DBSPACE - ARCHIVE FAILED - NO LEVEL 0 ARCHIVE EXISTS;
ONLY LEVEL 0 ARCHIVE IS ALLOWED.
95659 LEGACY: INVALID CHARACTERS IN YEAR ARE NOT REJECTED.
E.G., "01/02/98XX" IS ACCEPTED AND TREATED AS
"01/02/1998" (ASSUMING PRESENT CENTURY IS 1900).
95709 MISLEADING ERROR MSG (47) WHEN CLOCKS ARE OUT OF SYNC.
95744 DBLOAD FAILS WITH LOC_OPEN() FAILED, NOT OWNER LOADING
A TABLE WITH A BLOB COLUMN FROM A FLAT FILE.
95789 SUBSCRIPTED SELECT STATEMENTS ON A TABLE WHOSE INDEX
IS FRAGMENTED RETURNS NO ROWS
95865 HDR - CREATING INDEX ON PRIMARY CAUSES SECONDARY
TO GO INTO A BLOCKED CHECKPOINT STATE AND EVENTUALLY
PING TIMEOUT
96072 SERVER DOES NOT WRITE DAY/DATE/TIME/YEAR INTO MESSAGE
LOG FILE IF SERVER IS BROUGHT UP ON JANUARY
FIRST IN ANY YEAR. BUG FOUND BY YEAR 2000 TESTING.
96077 MEMORY LEAK IN GLOBAL POOL CAUSED BY MAKING SOCKET
CONNECTION TO PORT ENGINE IS LISTENING ON
96189 LISTENER THREAD CAN GET CAUGHT RUNNING FOREVER IF
POLL THREAD IS BOUND TO THE SAME VP. ENGINE HANGS,
NO NEW CONNECTIONS
96192 DIFFERENT ROWS RETURNED FROM OUTER JOIN QUERY AFTER
UPDATE STATISTICS LOW ON DATABASE
96215 SET LOCK MODE TO WAIT IN STORED PROCEDURES DOESN'T
WORK
96218 GROUPER COMPRESSION TIES UP CPU VP
96479 OUTER JOIN WITH LARGE IN CLAUSE ASSERT FAILS
96481 SELECT NVL(COLNAME,"STRING") FROM TBLNAME; IF COLUMN
NAME IS NULL AND OF TYPE VARCHAR (255), RETURNS NOTHING.
96482 FETCH BUFFER OVERFLOW RESULTS IF NEXT RECORD IS LARGER
THAN REMAINING AVAILABLE SPACE IN BUFFER (FETBUFSIZE),
POTENTIALLY CAUSING SEGV
96492 SHARED MEMORY CONNECTION IGNORES FETBUFSIZE. SQLI
DEBUG SHOWS THAT FETCH BUFFER IS USED AS IF IT WAS
ONLY 1 KBYTE NOT THE REPORTED TUPLE BUFFER SIZE
96575 GROUPER FANOUT ABORT OCCURRING BECAUSE DDRBLOCK NOT
BEING SET CORRECTLY
96676 RTODAY EXPECTS ALWAYS A 32-BIT POINTER, BUT MANY TESTS
PASS THE ADDRESS OF A LONG. THESE TESTS FAIL
IN A 64-BIT QA ENVIRONMENT
96685 DBINFO ('SQLCA.SQLERRD2') RETURNS WRONG VALUES WHEN
USED IN FOR LOOP OF STORED PROCEDURE WHICH IS
SELECTING DATA USING SYNONYMS
96762 MEMORY LEAK WHEN CREATING AND DROPPING A FRAGMENTED
(OR TEMP) TABLE IN A LOOP
96790 CDR - SECONDARY ENGINE CRASHED AFTER A LONG TRANSACTION
IS REACHED ON THE PRIMARY.
96830 PERFORMANCE OF HDR SECONDARY SERVER IS UNUSABLE WHEN
LARGE NUMBER OF ENTRIES FOR A SINGLE TABLE IN
SYSTABAUTH
96966 DBSCHEMA CREATE BOGUS STATEMENT IF THE TABLE HAS
DATE FIELD WITH DEFAULT STATEMENT. WITH THE SCHEMA
TO CREATE TABLE WILL GENERATE ERROR 202
97006 PAGE CLEANERS SET TO 128 GIVES " LOGICAL LOG LAYOUT
MAY CAUSE ONLINE TO GET INTO LOCKED STATE" ERROR
MESSAGE - COSMETIC
97014 GROUPER MUTEX UNLOCKED TWICE, CORRUPTS GROUPER'S
GLOBAL AND POSSIBLY SERIAL AND FREE TX LISTS, MAY
CAUSE GROUPER HANG
97061 CURSOR FOR INSERT TO INSERT NON ZERO SERIAL IN FRAGMENTED
TABLE WITH ROWIDS GET ERR -626 ON 2ND RUN
IF SERIAL VALUES IN DECREASING ORDER
97067 GRANTS/REVOKES CAN CAUSE SYSTEM TO HANG
DUE TO MUTEX DEADLOCK
97140 IF DBSERVERALIASES IS DEFINED WITH MORE THAN 8 ALIA
SES THE ENGINE ABORTS DURING THE ASF INITIALIZATION
PHASE WITH ERROR 25507
97157 HANG/DEADLY EMBRACE CAN OCCUR BETWEEN GROUPER EVALUATORS
DURING COMPRESSION IF MULTIPLE LOCAL DELETE
ERRORS OCCUR
97319 SELECT MAX (DBSNUM) FROM SYSDBSPACES PRODUCES 245/102.
97419 AFTER UPDATE STATISTICS OPTIMIZER CHOOSES WRONG INDEX.
THIS CAUSES THE ORDER BY TO NEED UNNECESSARY
SORTING AND TEMP TABLES.
97421 INSERTING DUPLICATE ON A TABLE WITH A ROWID CLAUSE
AND A UNIQUE INDEX WITH A FILTERING MODE, GET ERROR
-239
97431 DB-ACCESS UNLOAD DOES NOT REPORT ERROR WHEN ENCOUNTERING
BAD DATA PAGE CORRUPTION; IT SIMPLY 'UNLOADS
AROUND' BAD DATA WHEN SELECTING ALL ROWS.
97544 USING AN UPDATE CURSOR WHERE THERE IS AN IN-CLAUSE
IN THE CURSOR DECLARATION YOU GET ERROR 290.
97546 ALTER FRAGMENT (DETACH), REPORTS 407 ERROR WHEN TABLE
IS BEING ACCESSED BY OTHER USERS.
97692 SELECT * FROM TAB1 WHERE EXISTS (SELECT * FROM TAB
2 WHERE TAB2.COL1=TAB1.COL1 ...) FAILS WITH ERROR
407. TAB1 & TAB2 HAVE SAME SCHEMA
97729 CREATE STORES5 DATABASE IN 5.08.UD1, CONVERT TO 7.31,
AND REVERT TO 5.08.UD1. SELECT * FROM CUSTOMER
CRASHES SQLTURBO IN 5.08.UD1
97762 ASSERT FAILED: PTMAP: BAD PAGENUM = XXX -- ONLY XXX
PAGES WHEN RUNNING UPDATE STATISTIC MEDIUM.
97798 TRG HANG WITH RESUME
97885 COMPLEX QUERY WITH CORRELATED SUBQUERY BASED ON A
VIEW RESULTS IN WRONG RESULTS -- SYSTEM HUNG OR
SEGV -- DEPENDING ON QUERY AND ONLINE VERSION
97955 DECIMAL TO DOUBLE CONVERSION WITH MAXIMUM NUMBER OF
DIGITS CAN CRASH SERVER AND PROBABLY FRONTENDS AS
WELL
98089 SERVER SENDS SQ_ISOLEVEL WITHIN A TRANSACTION IN
REMOTE SELECT CAUSING ERROR WITH ODBC GATEWAY.
REGRESSION OF BUGFIX 77685
98235 ENGINE CRASH EXECUTING STORED PROCEDURE HAVING A
SELECT AGGREGATE WHEN THE STORE PROCEDURE PLAN WAS
SAVED WITH PDQPRIORITY > 1.
98238 COMPLEX OR CONDITION MUCH WORSE THAN CORRESPONDING
UNION ALL CONSTRUCT.
98425 QUERY OPTIMIZER CHOOSES WRONG INDEX WHEN NUMBER OF
LEVELS IS HIGHER
98437 IT TAKES TOO LONG TO CONNECT FROM ONLINE 5 TO IDS
7.2 WHEN MAKING A LARGE NUMBER OF CONNECTIONS
98467 QUICK ATTACH USING ALTER FRAGMENT ATTACH. AFTER A
TTACH, STATISTICS ON THE SURVIVING TABLE ARE STILL
INTACT BUT STATISTICS FROM CONSUMED TABLE ARE NOT
98475 INITIALIZING HDR USING PARALLEL BACKUP CAN CAUSE LOG
RECORDS TO BE REPLAYED AND CAUSE HDR TO FAIL
98492 ERROR PROCESSING FOR ROWS CONTAINING BLOBS CAUSING
SEGV
98544 NIF RESUME/UNHOLD CAN CAUSE LOSS OF DATA
98607 A PREPARED SELECT STATEMENT WITH GROUP BY CAN CRASH
THE SERVER WITH SEGV, THIS IS RELATED TO PTS-B # 87086
98619 FRAGMENTED TABLE GIVES 407 ERROR WITH LARGE WHERE
CLAUSE IN SELECT
98727 LOG EVENT PROCESSING USES TOO MANY LOG PAGES RESULTING
IN A CHAIN-REACTION WITH LARGE REPLICATE SYSTEMS
98746 CREATE TABLE WITH ROUND ROBIN FRAGMENTATION AND ATTACHED
INDEX WHICH FOLLOWING TABLE FRAGMENTATION
SELECT MAX(COL) WILL NOT RETURN DATA
98747 SELECTING FROM A REMOTE VIEW PRODUCES -352 ERROR
98852 DROPPING A LOGICAL LOG IS ALLOWED EVEN IF THE LOG
IS NEEDED BY ER
98884 SIGN EXTENSION OF PARTN->PN_FLAGS CAUSES INDEXES
TO NOT BE UPDATED WHEN DELETING ROWS AFTER A LIGHT
APPEND OPERATION.
98911 CDR: MASSIVE UPDATES CAN SLOW REPLICATION TO A CRAWL.
SERVER SLOWS TO A CRAWL TOO.
99075 SELECT VARCHAR CONTAINING A DECIMAL VALUE AFTER UP
DATE STATISTICS MED/HIGH W/DISTRIBUTIONS RETURNS A
-1213 ERROR.
99150 MT_STACK_LIMIT() RETURNS INCORRECT RESULT ON 64-BIT
HP PORT
99153 ONSTAT -Z CAN CRASH SERVER IN DOSPINLOCK()
99238 ARCHIVE RESTORE HANGS WHEN TRYING TO GET EMPTY BUFFERS
IN RSWRITE_PHR()
99271 B88018.OUT SELECT RETURNING INCORRECT AMOUNT OF ROWS.
99327 REVERTING 7.30 TO 7.24 CAN CAUSE A DBSPACE TO GET
OVERWRITTEN
99365 DISTRIBUTED FETCH CRASHES THE SERVER AFTER THE FUNCTION
GET_DIST
99402 CDR GROUPER FANOUT ABORT WITH CERTAIN LOGICAL LOG
CONFIGURATIONS
99405 NEW ARCHIVE ALGORITHM IN 7.30 CLAIMS A LOT OF MEMORY
WHEN INSTANCE HAS A LOT OF PARTITIONS.
99450 MT_STACK_LIMIT CHECKS BOUNDS IN WRONG DIRECTION,
SO THAT RECURSIVE CALLS ALWAYS GET MORE STACK, LEADING
TO HIGH MEMORY USAGE
99470 TABLE WITH DETACHED INDEX, BLOB AND UPDATE TRIGGER
CAUSES ERROR -243 / -102 ON UPDATE
99491 ENGINE SEGV/HANG WHEN DOING SELECT FROM THE FRAGMENT
AND DETACH, ATTACH, DROP OR ADD FRAGMENT IS
RUNNING SIMULTANEOUSLY.
99576 IF A DBSPACE OBTAINS A NULL TERMINATOR YOU CAN'T
PERFORM A WARM RESTORE ON THAT DBSPACE
99761 ONLINE - SPL - 294 IS RETURNED WHEN A SP IS NAMED
IN A SELECT STATEMENT AND A COLUMN IS AN ARGUMENT
TO THE SP AND IS NAMED IN THE GROUP BY CLAUSE
99852 ASSERT FAILURE IN MKREMBUFF IF SUBSELECT AND GROUP
BY IS DONE AGAINST A REMOTE DATABASE
99891 PRIMARY CRASHES IN DR_BT_SENDBT() IF THE RSPNOPEN()
CALL FAILS.
100035 CONCATENATION OF STRING-INTEGER-STRING FAILS ON 7.30
ENGINE WITH STRING LENGTH ERROR -881.
100180 ALTER TABLE ADDS 2 COLUMNS BEFORE COLUMN CRASHES SERVER
100237 CM FANOUT THREAD HANG BECAUSE CDRN_CM WAITING FOR
SQLOCK BUT IS CURRENT OWNER
100287 ALTERING THE NEXT EXTENT SIZE FOR A TABLE WILL CAUSE
THE INDEX EXTENT TO BE CREATED WITH THE SAME SIZE
RATHER THAN BEING CREATED PROPORTIONAL
100364 LEVEL 1 AND 2 ARCHIVES CANNOT BE USED TO SET UP HDR.
BUT THERE IS NO CHECK TO FIND OUT IF USER TRIES
IT.
100371 ENGINE CRASHES IN THE MIDDLE OF EXECUTING STORED
PROCEDURES - MEMORY CORRUPTION
100419 USING NVL FUNCTION ON 7.30 CAUSES 2 OR 3 SHARED MEMORY
SEGMENTS TO BE DYNAMICALLY ALLOCATED, SAME
QUERY WITHOUT NVL FUNCTION DOES NOT.
100447 SIEBEL QUERY PERFORMANCE PROBLEM: SEQUENTIAL SCAN
USED WHEN INDEX SCAN IS MUCH BETTER
100472 INCORRECT NUMBER OF ROWS ON A QUERY RETURNED FROM
A VIEW
100493 CDRNST THREAD DOESN'T GET CLEANED UP WHEN IDLE TIMEOUT
OCCURS FOR SERVERS DEFINED WITH IDLE TIMEOUT
PARAMETER
100545 SIEBEL PERFORMANCE PROBLEM: HASH JOIN IS USED INSTEAD
OF NESTED LOOP JOIN. PERFORMANCE DIFFERENCE: 2X.
100622 -951 ERROR ON CONNECTING TO A DB ON SOLARIS IF PASSWORD
AGING IS USED
100725 ONCHECKS RUN ON THE SECONDARY AGAINST A TABLE BEING
RAPIDLY MODIFIED IN A HDR PAIR CAN HANG THE SECONDARY,
USERS WAITING ON A BUFFER
100836 ADDING A VARCHAR COLUMN VIA ALTER TABLE TO A TABLE
CONTAINING MANY VARCHAR COLUMNS ALREADY CAN YIELD
MEMORY BLOCK HDR CORRUPTION
100880 SERVER CRASHES DURING ROLLBACK OF A TRANSACTION WITH
THE MESSAGE: ASSERT FAILED: NO EXCEPTION HANDLER.
ENGINE PANICS DURING FAST RECOVERY AS WELL
100917 DBEXPORT PRESERVES SYSTEM GENERATED CONSTRAINT NAMES
IN ERROR IF TABLE HAS BEEN ALTERED
100976 CHANGING TRIGGER OR SCOPE ON TRANSACTION CAUSES REPLICATE
TO ALSO BECOME TIME-BASED
100983 CDR LIST REPL COMMAND SHOWS OLD STATE FOR REPLICATES
IN GROUP
101162 CRASH EXECUTING STORED PROCEDURE WHEN REOPTIMIZATION
OCCURS
101167 CDR_DSLOCKWAIT IGNORED WITH TRIGGERS IF REFERENTIAL
CONSTRAINTS EXIST ON TARGET TABLE RESULTING IN ERRONEOUS
107 ERRORS
101236 STDEV FUNCTION IN SELECT STATEMENT WITH A GROUP BY
CLAUSE GIVES ERRONEOUS RESULT
101304 DROPPING A DBSPACE WHILE ARCHIVE IS GOING ON HANGS
THE SERVER IN BLOCKED:DBS_DROP MODE
101365 LARGE DELETE - ASSERT FAILED: PTMAP IN LOG , AND
PTMAP: BAD PAGENUM IN AF FILE.
101457 FEA SHOULD PREVENT PARTITION TABLE DATA SCANS OF
THE CONSUMED TABLE WHEN ALTER FRAGMENT ATTACH FRAGMENT
DOES NOT NEED TO MOVE DATA
101563 REPLICATION OF AN NVARCHAR WHICH IS PART OF THE PRIMARY
KEY WILL CRASH THE SERVER ON WHICH THE
UPDATE WAS INITIATED
101809 RSAM CRASH ON PAGE CHECK ERROR WHEN TX ON FRAGMENTED
TABLE ROLLED BACK
101815 NVL(STORED PROCEDURE(VAR),1) INCORRECTLY RETURNS
NULL
101831 USING DECODE FUNCTION FROM ESQL GIVES ERROR 800
WHEN USED WITH A HOST VARIABLE AS AN ARGUMENT
101959 SELECT STMT CONTAINING COUNT (*) IN HAVING BY
CLAUSE CAUSES THE SERVER TO DUMP CORE
101960 ERROR 397 SYSTEM CATALOG CORRUPT AFTER ALTER TABLE
DROP FOREIGN CONSTRAINT ALSO DROPPED INDEX THAT IS
STILL NEEDED FOR OTHER CONSTRAINTS
102024 RACE CONDITION BETWEEN CDRNRXXX AND REPLTHXX CAN
CAUSE SEGV IN RQMDROPQ DURING CONNECTION SHUTDOWN
102160 UPDATE STATEMENT WITH SET EXPLAIN CAUSES ASSERT
FAILURE/SEGV
102176 SELECT -T1+T2 FROM TABLE ORDER BY 1 WHERE T1 AND
T2 ARE DATETIME COLUMNS WILL CAUSE THE ENGINE TO ASSERT
FAIL
102180 SELECT * FROM TAB1 WHERE DATECOL <> '' RETURNS NO
ROWS BUT THERE ARE ROWS IN TABLE TAB1.
102195 SERVER PANIC WHEN CDR DEFINE SERVER HAS WRONG GROUPS
SERVER NAME
102347 FEA: THE SELF-REFERENTIAL INSERT INTO MYTAB SELECT
FROM MYTAB ... IS NEEDED TO GET PEOPLESOFT TOOLS
RUNNING FOR THIS CUSTOMER
102451 RUNNING OUT OF VIRTUAL MEMORY CAN CAUSE CDRGFAN THREAD
TO SEGV
102570 WRONG ROWS RETURNED FROM A TEMP TABLE MADE FROM A
TEMP TABLE WITH AN INDEX AFTER AN UPDATE
102647 SEGV IN QUEUERGETMESSAGE IF QR_FIT MISSING FROM MESSAGE
IN QUEUE
102793 USE DIRECTIVE TO TURN ON EXPLAIN OUTPUT CRASHED SERVER
WHEN THE SERVER IS INITIALIZED FROM A DIRECTORY
THAT THE USER CANNOT WRITE TO
102989 SELECT USING VIEW IN 7.30.UC3 & 7.30.UC5 TAKES LONGER
THAN SELECT USING VIEW IN 7.2 FAMILY. 7.3
SEE A LOT OF MT_AIO_WAIT ON THE STACK TRACE.
103251 U-LOCKS MAY BE LEFT AFTER THE EXECUTION OF A SUBQUERY
FLATTENING IS IN EFFECT
103257 DBCENTURY ENVIRONMENT VARIABLE IS NOT PASSED TO COMMANDS
EXECUTED BY STORED PROCEDURES WHICH AFFECTS
HPL JOBS RUN THROUGH THE GUI
103418 SELECT MAX(COL) APPEARS TO BE RETURNING THE MINIMUM
VALUE INSTEAD OF THE MAXIMUM VALUE WHEN AN INDEX
IS CREATED IN DESC ORDER.
103421 WHILE ROLLING BACK THE FINAL TRANSACTIONS OF FAST
RECOVERY AFTER A RESTORE A HANG MAY BE ENCOUNTERED
103467 RUNNING 'DB-ACCESS DB' FOR A 7.31.UC1 (N244) DB THAT
CONVERTED FROM A 7.30.UC2 DB GIVES 597: [INTERNAL]
PREMATURE END OF BUFFER.
103473 7.3 CRASH WITH PAGE CHECK ERROR IN UNDOPGALTER:UNDO_
ROWALTER IN A ROLLBACK
104045 CDR DATASYNC REJECTS ROWS WITH ERROR -772 WHEN TARGET
TABLE IS FRAGMENTED BY EXPR AND INDEX HAS SAME
FRAGMENTATION AS THE TABLET VALUE
104091 ONSTAT -Z TO ZERO OUT STATISTICS CAUSES AF IN CDRSTATSZERO.
104188 ONMODE -B 7.2 (FROM 7.30) FAILS TO LIST TABLES THAT
HAVE ACTIVE IN-PLACE ALTER TABLES.
104312 ERROR 217 WHEN DEFINING A CDR SERVER AFTER MIGRATION
FROM 7.30 TO 7.31
104500 SELECT STATEMENT WITH MATCHES & AND/OR CLAUSE AND
OPTCOMPIND SET TO 0 (ZERO) CAUSES INCORRECT RESULTS
TO BE RETURNED.
104775 ERRORS 211(SYSTABLES)/111 WHEN DOING INSERT OR UPDATE
IN A TABLE WITH VIOLATIONS STARTED AND THE TABLE
IS IN ANOTHER DATABASE.
105745 7.30.UC5 OPTIMIZER SELECTS WRONG PATH WITH DISTRIBUTIONS.
PRODUCT NAME : ONUTILS
BUG NO. DESCRIPTION
----------------------------------------------------------------------
60596 WHEN AWAITING USER RESPONSE TO "ABORT?" ONLOG HANGS
CHECKPOINTING, AND PERHAPS MORE.
82110 IF YOU RUN ONCHECK AND LIST MORE THAN 20 TABLES THE
ENGINE WILL CRASH WITH ONLINE DAEMON IS NO LONGER
RUNNING; DAEMON DIED
89187 SUSPENDING AND RESUMING LOGICAL RESTORE VERY FAST
CAN CRASH SERVER IN ISOPEN_LGR()/GET_EMPTY()
90032 HPLOADER LOADS NULLS INTO MONEY COLUMNS WHEN USING
BINARY FIXED FORMAT
90128 ONUNLOAD KEEP TRACK OF TRIGGERS REC IN SYSOBJSTATE
PREVENTING USER TO RE-CREATE THE TRIGGER AFTER THE
ONLOAD. SQL ERR -312 ISAM -100.
90911 INTERRUPT AND OK BUTTONS IN IPLOAD 'ACTIVE JOB' WINDOW
ARE NOT DISABLED/ENABLED CORRECTLY
90912 ONDATARTR PROMPTS FOR WRONG LOGICAL LOG WHEN PROVIDING
INCORRECT SAVESET DURING LOGICAL RECOVERY
91568 WARM RESTORE OF DBSPACE FINDS OLDER LEVEL-1 BACKUP
THAN LEVEL-0 AFTER TIMESTAMP WRAP AROUND
91685 ONPLOAD MAY ABORT WITH CORE DUMP OR UNLOAD NO ROWS
OR CORRUPTED ROWS BECAUSE WE DON'T MAKE SURE THAT
ALL VP ATTACH V SEGMENT AT SAME ADDRESS
91712 HPL LOAD FROM DATA FILE WITH BLOB COLUMN IN BLOBSPACE
AND NOT NULL CONSTRAINT CAUSES ASSERT FAILURE,
ONLINE ENGINE CRASH.
91746 IF IPLOAD RUNS OUT OF MEMORY IT MAY HANG AND EVENTUALLY
RETURN THE MESSAGE "CANNOT ALLOCATE MEMORY"
91764 AFTER RUNNING A SCRIPT THAT DROPS INDEXES, CONSTRAINTS,
TRIGGERS, STORED PROCEDURES AND REVOKES PRIVILEGES,
ONCHECK -CC REPORTS ERRORS
91858 THE BROWSER UTILITY DOES NOT WORK WITH ANY KIND OF
FORMAT, UNLESS YOU VIEW ONLY CHARACTER COLUMNS AND
USE DELIMITED FORMAT
91872 PARALLEL BACKUP OF HUGE NUMBER OF DBSPACES CAN LEAD
TO PROBLEMS UPDATING SYSUTILS AND A FAILURE OF THE
BACKUP WHEN SAME PID REUSED FOR 2 PROCESS
92168 PHYSICAL RESTORE FAILED - THE ARCHIVE BACKUP IS CORRUPTED
ENCOUNTERED IF BLOBS CONTAINS
-1 FOR PAGE ADDRESS AND 5 FOR FLAGS
92203 NEW: MAIN ONTAPE -C GIVES SEGMENTATION FAULT (CORE
DUMPED) IF ENGINE IS SHUT DOWN
92328 RUNNING XTREE FROM COMMAND LINE OR FROM WITHIN ONPERF
WILL PRODUCE THE ERROR "CHANGING DATA STRUCTURE
FORCES TERMINATION OF XTREE"
92346 AFTER A POINT IN TIME (PIT) RESTORE, SALVAGE LOGICAL
LOG FILES ARE NOT BACKED UP (WITH ONBAR -L -S OR
ONBAR -R).
92360 HPLOAD UNLOAD JOB TO AN UNBUFFERED/BUFFERED LOGGING
DATABASE WITH A WHERE CLAUSE THAT SPECIFIES 2-DIGIT
YEAR UNLOADS ALL ROWS. 4-DIGIT YEAR WORKS.
93429 HPL FAILS TO DISPLAY MORE THAN 541 COLUMNS IN THE
TABLE MAP SCREEN. WHEN NUMBER OF COLUMNS IS EQUAL
TO OR GREATER THAN 542 COLUMNS IT IS BLANK.
93468 ONARCHIVE 'COPY/VSET=X/DESTINATION=Y/REQUEST=N' CHEWS
UP CPU AND TAKES VERY LONG TIME TO RETURN COMPLETE
MSG.
93541 TIMING PROBLEM WITH ONPLOAD AND DELUXE MODE LOADS
CAN PREVENT CADILOAD FROM ACKNOWLEDGING THE END OF
STREAM. PLOAD JOB HANGS FAILING TO COMPLETE
93553 INTERRUPTING OF LOGICAL RECOVERY BY CTRL-C NOT ALWAYS
WORKS PROPERLY
93628 FIX TO BUG 52480 DOES NOT WORK WITH OPTICAL BLOBS:
SELECT FROM A TABLE WITH OPTICAL COLUMN THAT HAS
BEEN ONLOADED RETURNS ERROR -602/-135
93653 ONDATARTR DISPLAYS THAT LOGICAL LOGS ARE REAPPLIED
IF A LOGICAL LOG SAVESET ID ID REUSED LATER IN THE
RESTORE SEQUENCE
93673 ENTERING JUST RETURN FOR DIRECTORY CONTAINING LOGICAL
LOG SAVESETS DURING LOGICAL RECOVERY CAUSES ON
DATARTR TO ABORT RECOVERY AFTER ARC-E-01408 ERROR.
93675 IF SMART BLOB PAGE HEADER CONTAINS UNINITIALISED DATA,
ARCHIVE CAN ABORT MISTAKING THE PAGE AS A PG_BLOB
93693 AFTER EXPORT OF ONPLOAD DATABASE THE USER CANNOT VIEW
SQL, MAPS, FORMAT, ETC.
93745 ONPERF TOOLS MENU SELECT QUERY TREE GIVES WARNING:
REPRESENTATION SIZE 4 MUST MATCH SUPERCLASS'S TO
OVERRIDE REPORTCALLBACK
93805 WHEN USING -R OPTION WHILE RUNNING ONPLOAD, PARALLEL
LOADER CRASHES. REMOVING -R OPTION, LOAD JOB
COMPLETES
94384 ONTAPE -S -L 0 SHOULDN'T BACKUP THE INSTANCE WHEN THE
BLOCKSIZE IS ODD
94428 ONBAR -B -L 0 DOESN'T BACKUP CURRENT LOG AND ROLL
FORWARD TO NEXT LOG
94469 THE TABLES IN THE SYSUTILS DATABASE SHOULD USE ROW
LEVEL LOCKING TO MAKE ONBAR MORE RESISTANT TO DEADLOCKS
94549 FEATURE REQUEST - WHEN ONTAPE PROMPTS THE USER TO
INSERT ANOTHER TAPE AND THE TAPE IS NOT AVAILABLE,
EVENTUALLY ONTAPE SHOULD QUIT PROMPTING
94563 DBCENTURY DOES NOT PERFORM AS EXPECTED USING HIGH
PERFORMANCE LOADER
94781 ONPLOAD GIVES "ONPLOAD MUST RUN ON THE HOST (HOSTNAME)
THAT CONTAIN THE TARGET DATABASE" IF MACHINE
HAS 2 ETHERNET CARDS, THEREFORE 2 ADDRESSES
94784 IF KILL SIGHUP/SIGKILL/SIGTERM <THE ONPLOAD UNLOAD
JOB PARENT PROCESS ID>, ASSERT FAILED: CONDITION
FAILED (BAD MEMORY POINTER 0XFFFFFFE8), IN (MT_SHM_FR
94785 IPLOAD NOT SUPPORTING DELIMITED IDENTIFIERS FOR TABLE
DEFINITION IN IPLOAD HAVING ENVIRONMENT VARIABLE
DELIMIDENT SET TO 1
95054 ONCHECK -Q -CI <DATABASE> DOES PRINT A LOT OF NEWLINES
IN 7.3. OPTION -Q SHOULD BE QUIESCENT AS IT WAS
IN 7.2
95205 LOADING, VIA ONPLOAD, A LARGE BYTE BLOB (20K) INTO
A BLOBSPACE WILL CAUSE PLOAD TO HANG AND RETURN 2
: 2: CANNOT OPEN ERROR MESSAGE
95873 ONPERF -> TOOLS -> SESSION ACTIVITY. SESSION ID IS
TRUNCATED (CUT OFF) IF SESSION ID IS OVER 5 DIGITS.
FOR EXAMPLE, SID 109157 DISPAYS AS 109.
95933 ONBAR -B -L 0 DOESN'T BACKUP CURRENT LOG AND ROLL
FORWARD TO N