=========================================== ADDENDUM TO RELEASE NOTES FOR INFORMIX DYNAMIC SERVER 7.31.UC4 PRODUCT RELEASE DATE: 24 Sep 1999 =========================================== TABLE OF CONTENTS I. INFORMIX STORAGE MANAGER INFORMATION FOR THE 7.31.UC3 RELEASE II. BUGS FIXED IN THE 7.31.UC3 RELEASE III. INTERPRETATION OF TWO DIGIT YEARS WITHIN OBJECTS IV. BUGS FIXED IN THE 7.31.UC4 RELEASE I. INFORMIX STORAGE MANAGER INFORMATION FOR THE 7.31.UC3 RELEASE IDS 7.31.UC3 uses Informix Storage Manager Version 2.20 IDS 7.31.UC4 on NCR uses Informix Storage Manager Version 2.00 II. BUGS FIXED IN THE 7.31.UC3 RELEASE This section contains the bugs fixed in the 7.31.UC3 Interim Release. BUG NO. DESCRIPTION ---------------------------------------------------------------------- 109895 DETACHED INDEX ON VARCHAR COLUMNS CONTAINING NULLS, CAUSE AF WHEN RUNNING UPDATE STATISTICS ON TABLE. RESULT IN DATA LOSS, AFTER FAST RECOVERY. 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 102350 DELETING LOGICAL LOG FROM ROOTDBS CORRUPTS THE DBSPACE FLAG INFO IN SHARED MEMORY. 1214 ERROR SEEN THROUGH DBACCESS-DATABASE-INFO-DBSPACE. 108594 DBLOAD FAILS WITH LOC_OPEN() FAILED, NOT OWNER LOADING A TABLE WITH A BLOB COLUMN FROM A FLAT FILE. 82258 LEGACY:SELECT FROM TABLE WHERE TRIM(COLUMN NAME) = TRIM(CHAR VARIABLE) GIVES A 674 ERROR 82387 ENGINE CRASHES IN GCVFPRINTF() WHEN RUNNING STORED PROCEDURE WITH SET TRACE ON AND SET DEBUG FILE 90503 VERSTAMP CANNOT STAMP WITH A VERSION NUMBER THAT IS GREATER THAN 10 CHARACTERS SUCH AS 7.23.UC10X1 92602 CALCULATION FOR FULLNESS OF PAGES IN LIGHT APPEND ALLOWS TOO MANY SLOTS ON 4K PAGES WHEN PARTITION INCLUDES VARCHARS 96374 SERVER HANGS WHEN ACCESSING A TABLE IN A 9.X SERVER FROM A 7.3 SERVER 98932 DATA DICTIONARY/DISTRIBUTIONS/PROCECURE CACHES HASH ALGORITHM IS VERY POOR WHEN USING TYPICAL CUSTOMER TABLE NAMES 99153 ONSTAT -Z CAN CRASH SERVER IN DOSPINLOCK() 101361 SUSPENDING AND RESUMING LOGICAL RESTORE LOOSES 1 BUFFER FROM THE QUEUE IN EVERY LOOP 101364 ONMODE -D STANDARD LEAVES PRIMARY IN CONNECTING STATE AFTER HDR FAILURE WHICH CAN PREVENT RESYNCHRONISATION 101879 DR: CHUNK CREATED ON PRIMARY IS REPLICATED TO SECONDARY WITH PO FLAGS INSTEAD OF PI. 102105 ONLINE SYSTEM APPEARS TO HANG ON A SYSTEM WITH 1 CPU VP CONFIGURED BUT A SMALL NUMBER OF THREADS (2 OR MORE) WILL RUN BUT NO OTHER THREADS WILL 102489 SELECT * FROM SYSDIC:SYSMASTER SHOWS INCORRECT INFORMATION 102592 ARCHIVE RESERVED PAGES DON'T GET UPDATED CORRECTLY AFTER TIMESTAMPS COMPLETE FULL CYCLE. THIS PREVENTS AN HDR INSTANCE FROM BEING INITIALIZED. 102951 HDR: ENGINE DOES NOT DESTROY A SESSION WHICH WAS RUNNING DR_PRPING THREAD AFTER DR OUTAGE. 103183 INDEX CORRUPTION WHEN A PARTIAL QUANTITY OF TABLE INDEXES ARE SEPARATED AWAY FROM THE TABLE IF ALL ARE WITH THE TABLE STRUCTURE NO PROBLEM 103198 ASSERT FAILURE CAUSED BY SELECT USING FUNCTION TRUNC AND ALSO AN ALIAS WITH THE SAME NAME AS THE ORIGINAL COLUMN 103323 MEMORY CORRUPTION AND -858 ERROR WHEN ADDING A FRAGMENT TO A FRAGMENTED TABLE WITH A DISABLED INDEX 103496 RESTORE FROM POINT-IN-TIME/LOG, PARALLEL, LEVEL-0 AND INCREMENTAL DOESN'T DISK CLEAR LOGICAL LOGS 103591 BACKUP HIGH FRAGMENTED BAAN SYSTEM CAN CAUSE LOGPUTX(CHCOMBINE) RSBEGIN NEVER CALLED MSG 103720 BLOB FETCH FAILS WHEN BLOB HAS BEEN UPDATED WHILE CURSOR IS OPEN 104115 RUNNING 4GL PROGRAM WITH SCROLL CURSOR ON SELECT * FROM TABLE WHILE SELECT * FROM SYSPTNTAB RUNNING IN BACKGROUND GIVES ERROR 212 AND 106 104328 INTERMITTANT 392 ERROR QUERYING A UNION VIEW IN A STORED PROCEDURE 104562 SERVER CRASHES WITH ASSERT FAILED: ROLLBACK ERROR 126. 104844 LONG TXN ABORT ENCOUNTERED UPON ATTEMPTING TO START 1000 REPLICATES IN A 50 SERVER ENVIRONMENT. 105223 OUTER JOIN:EXECUTION OF PROCEDURE WITH ANSI OUTER JOIN RETURNS ERROR CODE 392. 105305 DATA SYNC THREADS HOLDING LARGE NUMBER OF LOCKS WHEN ATTEMPTING TO APPLY CONTROL MESSAGES FROM OTHER SERVERS. 105425 ONLINE HAD SEGMENTATION VIOLATION AT BLDDICREF() 105505 CREATE INDEX ON NVARCHAR COLUMN WITH CZECH GLS LOCALE CS_CZ.8859-2 PRODUCES CORRUPT INDEX 105532 ATTEMPTING TO DISCONNECT SERVERS THAT DO NOT HAVE EXISTING CONNECTIONS WILL CAUSE THE SERVER ENTRY TO BE REMOVED FROM THE ROOT SERVER. 105558 WHEN THE SERVERS ARE RECOVERED WHILE DATA IS IN THE SENDQ, IT NEVER DRAINS EVEN AFTER ALL THE SERVERS ARE ONLINE. 105597 2 TABLES WITH DIFFERENT OWNER BUT SAME IDENTIFIER ON THE SAME NON-ANSI DATABASE. 105809 ONTAPE:THE SERVER HANGS WHEN RESTORING LOGICAL LOGS IF WE SAY 'Y' TO PRMPT 'RESTORE ANOTHER LOG TAPE?' A FEW TIMES WITHOUT CHANGING TAPE(COOKED FILE) 105813 SM_POLL THREAD CAN ASSERT FAIL BECAUSE OF TIMING ISSUE BETWEEN AN INTERUPTED SHARED MEMORY CONNECTION AND ITSELF 105977 IN SOME CASES, DELETING A PARTICIPANT MAY NOT RESULT IN QUEUED MESSAGES FOR THAT PARTICIPANT BEING DELETED. 105981 SET LOCK MODE TO WAIT INSIDE A STORED PROCEDURE IS NOT WORKING IF THE STORED PROCEDURE RETURNS VALUE 106096 RQM LOCK TIMEOUT ERROR WHEN ATTEMPTING TO START 1000 REPLICATES IN A 50 SERVER ENVIRONMENT 106680 SEGV WHEN INSERTING INTO CHUNK THAT IS FULL - RELATED TO LIGHT APPENDS 106808 PENDING TRANSACTIONS PRESENT IN CONTROL QUEUES THAT NEVER DRAINS. 106813 INCORRECT STATISTICS ARE REPORTED BY ONSTAT -G GRP GT. 106931 ALTER TABLE WILL CORRUPT TABLE IF ADDING A COLUMN AND ALTERING A DECIMAL COLUMN AND SUBSEQUENT SELECT/DROP TABLE WILL ASSERT FAIL 106968 OUTER JOIN: A 22 TABLE CASCADED ANSI OUTER JOIN QUERY PANICS THE SERVER 107221 DUPLICATE ROWS IN ORDERED CURSOR WITH PENDING ALTER TABLE !SAP! 107777 AF: BAD ALLOCATION SIZE (0) FOR POOL SESSION ID IN SEARCH_JOIN_HASH_TABLE() WITH GLS LOCALE LV_LV.1257. SQL ERROR 208 107874 GROUPER COMPLAINS OF UPDBEF WITHOUT UPDAFT AND VICE VERSA 107906 FEWER ROWS RETURNED FROM OUTER JOIN QUERY AFTER UPDATE STATS IS RUN 108014 ONSTAT -G SQL SID AND ONSTAT -G SES SID REPORTS INCOMPLETE/CORRUPTED QUERY STATEMENTS FROM A CLIENT APPLICATION, (IECC, SQL EDITOR) 108076 DEADLOCK DETECTED WHEN ACCESSING ONLY ONE SINGLE ROW !SAP! 108158 DYNAMIC SQL WITH PREPARED CURSOR AGAINST FRAGMENTED TABLE BY EXPRESSION YIELDS INCORRECT RESULTS. DBACCESS/ESQL WITH STATIC LITERALS RETURNS FINE. 108347 CREATING COMBINED INDEX ON COLUMNS OF TYPE SMALLINT AND/OR VARCHAR ON A TABLE WITH DATA PRODUCES CORRUPT INDEX. 109139 TEMP SPACE NOT FREED WHEN FRONT END SESSION IS KILLED, BUT SESSION HAS GONE FROM ONSTAT -U. SPACE RECLAIMED WHEN ENGINE IS BOUNCED. 109146 SERVER GOT BLOCKED BY ARCHIVE WHILE INITIATING ONTAPE LEVEL-0 ARCHIVE WHILE SORTING EXTENTS 109300 MEMORY LEAK USING INSERT CURSOR ON FRAGEMENTED BY EXPRESSION TABLE AND MULTIBYTE LOCALE (EG: KO_KR.KSC ) GLS. 109441 SECONDARY CONFLICT RESOLUTION OF STORED PROCEDURE DOES NOT WORK IF REPLICATE DEFINED WITH TRANSACTION SCOPE 109833 PAGES DON'T GET FREED CORRECTLY WHEN SESSIONS ENCOUNTER MULTIPLE -229/-131 ERRORS 109905 ALTER TABLE RESULTS IN 211/111 FOR TABLE SYSCOLUMNS AND IN MEMORY BLOCK HEADER CORRUPTION IN SUBSEQUENT DDL STATEMENTS 110439 FAILURE OF HUB NODE IN CDR HR MODE CAUSES LOSS OF DATA 110931 CUSTOMER RECEIVES AN ASSERT FAILURE USING THE DBWHO.SQL THAT WE PROVIDED 111693 ATTEMPT TO WRITE SORT FILE > 2 GIG ON SOLARIS MAY RESULT IN AN ERRNO 27 FOLLOWED BY A SIGNAL 31 WHICH RESULTS IN AN ENGINE CRASH 112679 CDR: MEMORY LEAK IN 7.31 112694 REMOVE THE HR RESTRICTION IN GC FOR 7.32 113502 SENDQ ELEMENTS DO NOT DRAIN WHEN LEAVES ARE RECOVERED WHILE DATA TRANSACTIONS ARE BEING CONDUCTED FROM ROOT. 113601 UNDER HIGH USER LOAD THE ONBAR LOGICAL LOG BACKUP REUTRNS THE ERROR WARNING: A LOG BACKUP IS ALREADY RUNNING. CAN'T START ANOTHER. 113745 REPLICATING BLOBSPACE BLOBS LEAKS MEMORY - ATLAS CASE REF# 862439 83817 ER (CDR) DOES NOT WORK WHEN ONLINE IS STARTED AS USER 'ROOT' INSTEAD OF AS USER 'INFORMIX' 101629 ENGINE ALLOWS USERS TO CHANGE CRITICAL ONCONFIG PARAMETERS THAT CAN LEAD TO A FATAL RESTORE PROBLEM 103926 MORE PERFORMANCE ENHANCEMENTS FOR TABLESPACE BLOBS IN FRAGMENTED TABLES 104139 EXCESSIVE OVERHEAD WHEN SEARCHING FOR NEXT DATA PAGE IN A SCAN 104218 CDR CHANGE REPLICATE -D DOES DELETE SERVER DOES NOT REMOVE THE PARTICIPANT FROM REPLICATE. 105229 ALARMPROGRAM IS NOT ALERTED FOR HDR REPLICATION FAILURE MESSAGE: DR: SERVER STATE INCOMPATIBLE 105530 WHEN TZ IS SET TO SOME TIMEZONE+/-OFFSET WHERE OFFSET IS NOT IN WHOLE UNIT OF HOURS, RTODAY DELAYS RETURNING THE CORRECT DAY. 106018 HASH JOIN BUILD ON TABLE WITH MANY NULLS IN THE JOIN KEY IS VERY SLOW. ONLINE VERSION OF BUG B58334 FOR ONLN/XPS. 108317 ONCHECK CAUSES SMALL SERVER MEMORY LEAK PER INVOCATION 108396 POSSIBLE 15 SECOND NETWORK CONNECTION DELAY IF CLIENT HOSTNAME NOT AVAILABLE TO SERVER 108439 A COMPLEX OJ WITH 1 ADDITION NORMAL JOIN, TAKES AROUND 20SEC PER FETCH; DUE TO A SEQUENTIAL SCAN BEING PICKED ON THE LAST TABLE 108815 CDR MODIFY REPLICATE COMMAND DOES NOT UPDATE GLOBAL CATALOG WHEN ATTEMPTING TO DISABLE RIS AND ATS SPOOLING 109239 ARCHECKER REPORTS "UNABLE TO OPEN PARTITION FILE" FOR FREED BTREE PAGES 109546 TIME OUT FEATURE OF REPLICATION NOT WORKING PROPERLY. USING THE -I OPTION FOR DEFINE REPLICATE IS NOT WORKING CORRECTLY. TIIMEOUT. 110622 SLOW CHECKPOINTS IN 7.3/7.31/9.2 DUE TO REDUNDANT WAKEUP OF CLEANERS AND UNNEEDED VISITATION OF MODIFIED LRUS (CASE #842680) 111637 ONMODE -B 7.2 ON AIX 7.31.UC2 WILL NOT DO THE REVISION BUT JUST REPORTS MEMORY FAULT. 112258 A CDR HUB NOT PARTICIPATING IN ANY REPLICATES ALWAYS SPOOLS THE TRANSACTIONS IT FORWARDS 109839 WHEN AN AIO VP HITS MAXFILE_LIM IT REPORTS AN ERROR 9 [EBADF] INSTEAD OF A 24 [EMFILE] IN THE ASSERT FILE AND THE ONLINE LOG 91480 ONBAR HANGS IN A CALL TO SQL_API_DISCONNECT(). THIS PROB IS SEEN WHEN DOING A LOG BACKUP WITH A BLOBSPACE DOWN. 102718 ONSTAT -O CAN BE RUN BY EVERY USER - IT SHOULD ONLY BE POSSIBLE BY USER INFORMIX OR ROOT. 104853 ONPLOAD: LOADING A TABLE WITH CONSTRAINTS DEFINED IN AN ANSI DATABASE FAILS WITH -894/-111 IF THE USER IS NOT THE OWNER OF THAT TABLE 106334 HPL FIXED FORMAT LOAD JOB CORRUPTS DATA IF DATETIME AND DATE COLUMNS EXIST IN THE SAME TABLE. IF THE DATETIME IS REMOVED, THE DATA LOADS CORRECTLY 106533 ON-BAR IS TOO SENSITIVE TO THE FORMAT OF THE FILE SPECIFIED WITH THE -F OPTION 107350 REGRESSION: FIX FOR PTS-B 100718 IS NOT 64BIT CLEAN. RSTOL() NEEDS ADDRESS OF LONG AS SECOND PARAMETER, BUT ADDRESS OF INT4 IS GIVEN 108254 RESTORE FROM ARCHIVE FAILS IF BLOBPAGE SPANS THROUGH ARCHIVE TAPES. 109334 COBOL FORMAT DISPLAY AREA: CURSOR MOVES DOWN TO THE NEXT LINE BUT DISPLAY AREA BLANK AFTER ADDING AND PERFORMING A FORMAT ENTRY. 109750 HPL - ONPLOAD - DATES ENTERED WITH ONE-DIGIT YEARS ARE NOT EXPANDED TO THE CORRECT CENTURY 111399 ONTAPE -R AFTER A SUCCESSFULL LEVEL-0 BACKUP FAILS WITH ERROR "FUNCTION IOCTL FAILED CODE -1 ERRNO 5 ; PHYSICAL RESTORE FAILED" 113298 ONUTILS ONPLOAD UNLOAD JOB CONVERTS "" VARCHARS TO NULL VALUES 101437 A USER OTHER THAN INFORMIX OR ROOT CAN RUN ONCHECK -CI AND REPAIR INDEXES 102449 A STORAGE MANAGER ERROR DURING LOG BACKUP CAUSES ONBAR TO HANG. 113079 UPGRADE OF 7.30 TO 7.31 SYSUTILS DOES NOT ADD INS_REQ_AID COLUMN, USED BY ONBAR IF PREVIOUS DATABASE HAS A DEFINED STORAGE MANAGER 101746 ONPLOAD VIOLATIONS PROCESSING CAUSES CHANGING DATA STRUCTURE FORCED COMMAND TERMINATION ERROR WITH ONSTAT -G SQL 102039 ONPARAMS -A -D DBSPACE GETS ERROR 1 CANNOT ACCESS CONFIGURATION FILE $INFORMIXDIR/ETC/$ONCONFIG 104144 ONTAPE THREAD CRASHES ENGINE DURING INITIALIZATION WITH THE ERROR: I/O BAD REQUEST CHUNK 4095, PAGENUM 1048575, PAGECNT 1 107840 PHYSICAL RECOVERY CAN HANG IN AND ENDLESS LOOP, SO WE REPLACE ALL THE PHYSICAL LOG PAGES BACK OUT TO DISK, CAUSING CORRUPTION 110074 ONMODE -F CAN HANG SYSTEM AS IT CAN ENTER A POTENTIAL LIVE LOCK CONDITION BETWEEN SH_LOCK AND PO_LOCK 104318 NUMCPUVP > 1 CAUSES DELETE STATEMENT WITH 3000+ CHARACTERS TO ASSERT FAIL WITH -243/-172 READ_RECORD DELETED ROWID, PARTNUM III. INTERPRETATION OF TWO DIGIT YEARS WITHIN OBJECTS This section does not apply if this is a first time installation of Informix, or if two digit years are not used in the expressions of the following objects: fragmentation expressions, stored procedures, triggers, check constraints, and user defined routines. Note that not all of these features may be supported on this version of the product. This release introduces a change when date literals with two digit years within expressions of objects are evaluated according to the settings of relevant environment variables, such as, and not limited to, DBCENTURY. Previous to this release, two digit year dates in the expressions of the objects were interpreted by Informix according to the environment variable settings which prevailed at runtime time of the object. However, starting with this release, the date literal will always be interpreted using the environment variable settings prevailing at the creation time or the time of last modification of the object with which the date literal is associated. The settings of environment variable at runtime of the object will not be used. This applies only to date strings having two digit years in the expression of the objects mentioned above; i.e. it does not apply if four digit years are used in the objects. The following two steps are required to take advantage of this change introduced in this software: 1. Upgrade the Informix server to this release 2. Redefine all objects that use two digit year expressions. For fragmentation expression, redefining means detaching and reattaching the expression. For all other objects, the object must be dropped from the database and recreated. Only after the objects are redefined using this new server will the date literals in the expressions within objects be interpreted according to the environment variable settings at the time the object was created or last modified. The reference date used for this interpretation is the creation date or the last modification date of the object and not the current date when a query is run. If the objects are not redefined using this new server, the behavior of the object will remain the same as prior to the upgrade. However, since any new objects created after the software upgrade will behave differently from those created prior to the upgrade, administration of the database may become difficult because the database will have a mix and match of new and old behavior of objects in the database (with respect to when two digit years ithin expressions of objects are evaluated). Therefore, it is recommended that the two upgrade steps above be followed. Lastly, in order to avoid any possibility of misinterpreting two digit years within the objects, it is recommended that this opportunity be used to change the use of two digit years to four digit years instead, if possible. Use of DBDATE to interpret dates within objects This section does not apply if this is a first time installation of Informix, or if date literals are not present in the following objects within the database: fragmentation expressions, stored procedures, triggers, check constraints, and user defined routines. Note that not all of these objects may be supported for this version of the product. In the rare case that the setting of DBDATE prevailing at creation time or time of last modification of the object differs from the one that is in effect at the runtime of the object, you may either get a runtime error from the server or get erroneous results due to incorrect interpretation of the date literal. In order to maintain consistency, starting with objects created or modified using this release, the date literals within expressions of objects will be evaluated according to the setting of DBDATE prevailing at creation time or time of last modification of the object. The settings of environment variable at runtime of the object will not be used to evaluate the date literal within the objects. However, the prevailing setting at runtime of the query will still be in effect for date related data processed within the query. If your operating environment is such that the objects were created using one set of assumptions regarding the DBDATE setting and the runtime environment uses a different setting, you may encounter some problems. It is recommended that the usage of the database be modified so that the settings of DBDATE at creation, modification, and runtime are consistent throughout. IV. BUGS FIXED IN THE 7.31.UC4 RELEASE This section contains the bugs fixed in the 7.31.UC4 Interim Release. BUG NO. DESCRIPTION ---------------------------------------------------------------------- 72865 REGRESSION:MAIN ONLINE GIVES 876: CANNOT ISSUE "SET TRANSACTION" IN AN ACTIVE TRANSACTION WITH SET TRANSACTION ISOLATION LEVEL SERIALIZABLE(FSLR) 100379 DDR_SNOOPY THREAD GOES INTO INFINITE LOOP, HALTING CDR, AND IN SINGLE VCPU MODE, THE WHOLE SERVER 101747 DATE LITERAL INTERPRETATION IN TRIGGER BODY IS DONE INCORRECTLY 101848 DATE LITERAL INTERPRETATION IN PROCEDURE BODY IS DONE INCORRECTLY 104060 EXECUTE PROCEDURE RETURNS 1218 WHILE CONVERTING STRING TO DATE IN A DATABASE AFTER CONVERSION FROM 9.14 TO 9.20 105475 RSIDXINFO() RETURNS INCORRECT NUNIQUE INFORMATION IF THE PAGE HAS DELETED ROWS/SLOTS. 105947 RSAM FAILS TO POSITION WITHIN AN NCHAR INDEX. 108092 Y2K (Y2000) PROBLEM: CHANGING INTERPRETATION OF DATE AND DATETIME VALUES COULD RESULT IN UNEXPECTED AND/OR WRONG RESULTS 108947 SERVER HUNG, CPU VP SPINNING INDEFINITELY, ONLY ONSTAT COMMANDS RESPOND !BAAN! 109257 CAN GET SEMOP() FAILURES ERRNO=34 111592 !SAP 4.5B UPGRADE! SELECT DISTINCT BONBA FROM EKPO RETURNS 1226 ERROR 111681 NOLRUPRIO DOES NOT WORK AND CAN HANG THE SYSTEM. 111975 PARALLEL INDEX BUILD FAILS WITH -212, -179 ERRORS, EVEN IF THERE IS ENOUGH TEMP SORT SPACE TO COMPLETE IT. 112931 PRESS CTRL-C DURING ONLOAD IMMEDIATELY AFTER MESSAGE "PLEASE MOUNT TAPE..." BLOCKS TAPE AND SESSION IS STILL ACTIVE. 113163 SYSTEM CRASHES WITH SEGMENTATION VIOLATION ON UCVDROP() DROPPING INDEX. 113396 JOIN WITH CONVERSION FROM CHAR TO INT RETURNS ERROR 1213 AFTER RUNNING UPDATE STATISTICS HIGH 113959 ENGINE CRASHES WITH MT_NOTIFYVP TIMED OUT MESSAGE WHEN IT DOES PRIVATE_CLOSE FOR A FILE. 114129 Y2K QAINT: INSERTION FAILS WITH ERROR -530 - CONSTRAINT VIOLATION EVEN WHEN CONSTRAINT CONDITIONS ARE MET 114533 SETTING GL_DATE FORMAT STRING TO ANYTHING GREATER THAN 20 CHARACTERS RESULTS IN -1218 STRING TO DATE CONVERSION ERROR ON INSERTS, NOT SELECTS. 114706 Y2K QAINT:FRAGMENT EXPRESSION WITH A 2-DIGIT YEAR DATETIME FIELD RETURNS DIFF. RESULT THAN A FRAGMENT EXPRESSION WITH 4-DIGIT YEAR, ON SAME QUERY. 115202 Y2K QAINT: SAME QUERY RETURNS DIFFERENT RESULT IN ESQLC AND DBACCESS 115327 INDEX PAGES CAN BE INCORRECT SHRUNK SETTING BOTH LEAF AND NODE FLAGS WHICH WILL CAUSE EXCESS PAGES TO BE PLACED IN THE MED_HIGH BUFFER POOL PRIORITY 115351 INCORRECT BEHAVIOR WHILE HANDLING DATE WITH DIFFERENT SETTING FOR DBDATE, REFERS TO XPS BUG:113669, INVALID YEAR RETURNS MAY NOT BE HANDLED BY SERVER 116242 LOG CORRUPTION DETECTED OR READ ERROR OCCURED WHILE SNOOPING LOGS SEE ALSO BUG 104031 116352 DBCENTURY AND DBDATE IS NOT WORKING IN CONJUNCTION WITH DATE IN CHECK CONSTRAINT,FRAGMENTATION,STORED PROCEDURES,AND TRIGGERS. 117402 EXECUTE PROCEDURE RETURNING THE WRONG RESULTS WITH DBDATE SETTING 117496 EXECUTE ARCHIVE COMMAND OF ONARCHIVE FAILES WHEN SETTING SYSTEM DATE TO BEYOND YEAR 2000. 99152 INDEX ON NCHAR COLUMN IN AN 8-BIT GLS DATABASE SEQUENTIALLY SCANNED 107287 IF A SPECIFIC CODESET CONVERSION FILE DOES NOT EXIST, THE SERVER TRIES TO OPEN IT AT EVERY NEW CONNECTION AGAIN 108113 QUERY FALLS INTO A LOOP DOING A LOT OF NREADS AND NEVER RETURNS IN 7.30.UC7 109072 INDEX COST TOO LOW WHEN EQUALITY FILTER COLUMN USES A SUBSCRIPT SUCH AS COL[1,1] = 'H'; RESULTS IN POOR INDEX CHOICE 109571 ENG_TEST PURIFY BUG : SANITY/NEW/SAPIQP PLEASE REFER ALL EMAIL TO ENG_TEST@INFORMIX.COM TO GET A QUICK REPLY. 112446 PARALLEL INDEX BUILD SHOULD CALCULATE ESTIMATE NUMBER OF TEMP SORT PAGES REQUIRED BEFORE STARTING SORT. 95599 REGRESSION: RECEIVED INCORRECT ERROR MESSAGE -1204 INSTEAD OF EXPECTED -271/-883 USING DBDATE 104143 ONCHECK PRINTS JUNK CHARACTER FOR DATABASE NAME IF PARTNUM IS USED FOR PRINTING TABLESPACE REPORT (EW) 102039 ONPARAMS -A -D DBSPACE GETS ERROR 1 CANNOT ACCESS CONFIGURATION FILE $INFORMIXDIR/ETC/$ONCONFIG 114151 ONPLOAD ON IRIX PLATFORM GIVES FATAL ERROR: CANNOT SUCCESSFULLY MAP SONAME 'LIBPLCD.SO'. 117966 ONPARAMS -A -D DBSPACE GETS ERROR 1 CANNOT ACCESS CONFIGURATION FILE $INFORMIXDIR/ETC/$ONCONFIG 118591 SELECT ROWID STATEMENT RETRIEVES ONLY ONE ROW AFTER TABLE HAS BEEN ALTERED !SAP!