================================= RELEASE NOTES FOR INFORMIX 7.31.UC3 PRODUCT RELEASE DATE: 20 Jul 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) XIII. FIXED CUSTOMER-REPORTED BUGS in 7.31 (WINDOWS NT) XIV. 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. DCE-GSS CSM is not supported in 7.31 server family. 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: http://www.informix.com/informix/products/year2000.htm. 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 (SELECT * FROM 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 WHERE ... INTO TEMP ; INSERT INTO SELECT * FROM ; DROP TABLE ; Restrictions: ------------- INSERT INTO EXECUTE PROCEDURE (); If procedure scans or updates , 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 7.31 Valid values for < 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 Valid values for < are "7.3" and "7.2" 6. If the reversion test succeeds, then run the actual reversion. % revcdr 7.31 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 + 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 . b) Label the device: Select the device and select "Label" from the "Volume" menu. Alternatively, type + L. Select the pool to which the device should belong (ISMData for dbspaces, ISMLogs for logical logs). Set the volume number and click . c) Mount the device: Select the device and select "Mount" from the "Volume" menu. Alternatively, type + 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 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=" (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=." 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 | | | --- | | HOST:REG_SZ:- | | OPTIONS:REG_SZ:i= | | PROTOCOL:REG_SZ:group | | SERVICE:REG_SZ:- | | | --- | | --- HOST:REG_SZ: OPTIONS:REG_SZ:g= PROTOCOL:REG_SZ: SERVICE:REG_SZ: 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= 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= 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: