=========================================== ADDENDUM TO RELEASE NOTES FOR INFORMIX DYNAMIC SERVER 7.30.UC10 PRODUCT RELEASE DATE: 21 Sep 1999 =========================================== TABLE OF CONTENTS I. BUGS FIXED IN THE 7.30.UC2 RELEASE II. BUGS FIXED IN THE 7.30.UC3 RELEASE III. BUGS FIXED IN THE 7.30.UC5 RELEASE IV. BUGS FIXED IN THE 7.30.UC6 RELEASE V. BUGS FIXED IN THE 7.30.UC7 RELEASE VI. BUGS FIXED IN THE 7.30.UC8 RELEASE VII. BUGS FIXED IN THE 7.30.UC9 RELEASE VIII. BUGS FIXED IN THE 7.30.UC10 RELEASE IX. Interpretation of two digit years within objects II. BUGS FIXED IN THE 7.30.UC3 RELEASE 92803 ACCESSING DICTIONARY FOR SPECIFIC TABLE CRASHES ENGINE IN (READCATS) 91875 UNINITIALIZED VARIABLE IN OPTIMIZER CAN CAUSE CORE DUMP 90906 CRASH/MEM ASSERTION POSSIBLE WHEN INTERRUPTING A CLIENT IN THE PROCESS OF CONNECTING. 92594 ERROR -111 FROM DATABASE 91979 SUBQUERY CACHE FEATURE DOESN'T WORK(EFFECTIVELY DISABLED) ON THE 2ND EXECUTION OF A PREPARED QUERY. PERFORMANCE PROBLEM. 92193 INCORRECT QUERY RESULTS FROM CORRELATED SUBQUERY WITH CORRELATED VARCHAR GREATER THAN OR EQUAL TO 128 BYTES IN LENGTH IF SUBQUERY CACHE IS USED. 92434 SIGBUS WHILE RUNNING LEGACY/ONLINE/COL_PSUBQ 91913 UPDATE-SELECT SHOWS SIGNIFICANT PERFORMANCE REDUCTION FOR A PEOPLESOFT QUERY COMPARED TO 7.23 90084 NEW:MA-SS ASSERTION FAILURE AS STORED PROCEDURE CANNOT BE EXECUTED AS USER DID NOT CONNECT THROUGH A PASSWORD 92061 INCORRECT QUERY RESULT ON CORRELATED SUBQUERY WHICH USES SUBQUERY CACHE AND SUBSCRIPTED VARCHARS. 92992 SELECT TEXT COLUMN SUBSCRIPT RETURNS -607 IF SUBSCRIPT UPPER LIMIT IS HIGHER THAN VALUE LENGTH, SHOULD RETURN BLANK PADDED VALUE III. BUGS FIXED IN THE 7.30.UC5 RELEASE 93161 SLOW INDEX PATH CHOSEN BY OPTIMIZER WHERE AUTOINDEX IS FASTER. REGRESSION INTRODUCED BY FIX TO B75345 89682 GETTING ERROR -454('LOC_READ()' FAILED) AND -847(ERROR IN LOAD FILE LINE NUMBER) WHEN LOADING INTO TEXT TYPE COLUMN. 87345 7.22.UC1 - SOLARIS 2.5.1 - IMPLICIT CONNECT AFTER EXPLICIT DISCONNECT GENERATES ERROR 1803. 71732 OPTIMIZER SELECTS A QUERY PATH FOR EXECUTION FROM AVAILABLE CHOICES EVEN WHEN ITS EVALUATED COST IS NEGATIVE I.E., INVALID. 88301 DBSCHEMA FAILED WITH ERROR -100 FOR THE NEWLY CREATED TABLE FROM ALTER FRAGMENT AND ADD A FRAGMENT. 89939 SELECT IN DIRTY READ WITH CONCURRENT DELETE GIVES SPORADIC -243/-111 WITH DETACHED INDEXES 91185 ONLINE EXECUTING REMOTE STORED PROCEDURE GIVES ERROR -403 91286 ENGINE GOES DOWN DUE TO INTERRUPTED SYSTEM CALL ERRNO=4, IN FUNCTION SYSV_NSF_SENDFD 92779 REPEATEDLY TRYING TO OPEN A CURSOR AFTER AN ALTER TABLE CAUSES ENGINE TO SEGV 93107 ONLINE CAN ASSERT FAIL WITH A SEGV IN MARKBLKS WHEN ONLINE USES A VIRTUAL SEGMENT > 2GIG 93232 4GL 7.20.UC1 - A REPORT WITH USING CLAUSES GIVES UNPREDICTABLE RESULTS WHEN USING DATE FIELDS. 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 B90906 94047 ASSERT FAILURE:'NO EXCEPTION HANDLER' WHEN CREATING STORED PROCEDURE. 94075 CLUSTER INDEX ON A TABLE WITH AN EMPTY BLOBSPACE FIELD RETURNS ERROR -502 94607 -710/-101 ON SECOND OPEN/FETCH OF A CURSOR WITH LIKE OR MATCHES CLAUSE ON ANSI DATABASES 94857 SEGV OR MEMORY CORRUPTION IMMEDIATELY AFTER BACKUP STARTED/COMPLETED MESSAGES ARE PRINTED TO THE ONLINE MESSAGE LOG 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. 90032 HPLOADER LOADS NULLS INTO MONEY COLUMNS WHEN USING BINARY FIXED FORMAT 91712 HPL LOAD FROM DATAFILE WITH BLOB COLUMN IN BLOBSPACE AND NOT NULL CONSTRAINT CAUSES ASSERT FAILURE, ONLINE ENGINE CRASH. 91858 THE BROWSER UTILITY DOES NOT WORK WITH ANY KIND OF FORMAT, UNLESS YOU VIEW ONLY CHARACTER COLUMNS AND USE DELIMITED FORMAT 93541 TIMING PROBLEM WITH ONPLOAD AND DELUXE MODE LOADS CAN PREVENT CADILOAD FROM ACKNOWLEDGING THE END OF STREAM. PLOAD JOB HANGS FAILING TO COMPLETE 94563 DBCENTURY DOES NOT PERFORM AS EXPECTED USING HIGH PERFORMANCE LOADER 94784 IF KILL SIGHUP/SIGKILL/SIGTERM , ASSERT FAILED:CONDITION FAILED(BAD MEMORY POINTER 0XFFFFFFE8), IN (MT_SHM_FR) 93383 ARITHMETIC EXCEPTION IN USRANDSAMP WITH UPDATE STATISTICS MEDIUM - DISTRIBUTIONS ONLY 93468 ONARCHIVE 'COPY/VSET=X/DESINTAION=Y/REQUEST=N' CHEWS UP CPU AND TAKES VERY LONG TIME TO RETURN COMPLETE MSG. 90123 RAPID INSERTS/DELETES OF THE SAME P.K. ROW CAN CAUSE SEGV IN GROUPER IF ROW CONTAINS BLOBS 94782 PERFORMANCE ENHANCEMENT FOR TABLESPACE BLOBS AND FRAGMENTED TABLES 71014 ONARCHIVE FAILS WHEN ONCATALGR DIES WHEN IT RECEIVES SIGPIP - SIGNAL 13 98238 COMPLEX OR CONDITION MUCH WORSE THAN CORRESPONDING UNION ALL CONSTRUCT 97883 HUGE PERFORMANCE PROBLEM WITH ONCHECK -CI (UPPER CASE) IN 7.30 COMPARED TO 7.2X 96467 SERVER CRASHES DURING KEYFIRST SCAN 92118 ENGINE CRASH OPTIMIZING QUERY WITH WHERE CLAUSE OF: WHERE COL LIKE "%XXX%" ESCAPE '\' IV. BUGS FIXED IN THE 7.30.UC6 RELEASE 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 89978 FRAGMENTS ARE NOT BEING ELIMINATED FOR CERTAIN EXPRESSIONS INVOLVING DATE COLUMNS. 90729 DBLOAD FAILS WITH SYNTAX ERROR OCCURS ON STATEMENT ABOVE LINE 1 CHARACTER 6 IF THE INPUT FILE NAME IS MORE THAN 18 CHARACTERS LONG. 90844 MIGRATING A ONLINE SYSTEM WITH BLOBSPACES TO 7.23 CAN BREAK THE ARCHIVE WITH BLOB PAGE CHECK ERROR AT RSARCBU.C:3756 90967 CDR GROUPER INCORRECTLY HANDLES UNDO RECORDS FOR PARTITION BLOBS 91291 LATCH DEADLY EMBRACE BETWEEN VP_LOCK AND NOTIFYVP_LOCK INVOLVING ADMVP AND CPUVP 92168 PHYSICAL RESTORE FAILED - THE ARCHIVE BACKUP IS CORRUPTED ENCOUNTERED IF BLOBS CONTAINS -1 FOR PAGE ADDRESS AND 5 FOR FLAGS 92328 RUNNING XTREE FROM COMMAND LINE OR FROM WITHIN ONPERF WILL PRODUCE THE ERROR "CHANGING DATA STRUCTURE FORCES TERMINATION OF XTREE" 92633 CONCURRENT EXECUTION OF STORED PROCEDURES IN A NON-LOGGING DB CAN CAUSE ROLLBACK ASSERTION FAILURES AND CORRUPTION OF SYSPROCPLAN. 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) 93625 ASSERT FAILED:INDEX LEFT INCONSISTENT,ROLLBACK ERROR 100 AND LOGICAL LOGGING ERROR IN 'ROLLBACK',PANIC: ATTEMPTING TO BRING SYSTEM DOWN 93745 ONPERF TOOLS MENU SELECT QUERY TREE GIVES WARNING: REPRESENTATION SIZE 4 MUST MATCH SUPERCLASS'S TO OVERRIDE REPORTCALLBACK 93772 DBIMPORT OF LARGE DBEXPORT GIVE 201 SYNTAX ERROR ON PROCEDURE. IF YOU MOVE PROCEDURE TO THE END OF THE FILE IT IMPORTS CORRECTLY. 94656 ENGINE CAN CRASH DURING STARTUP DUE TO INTERRUPTED SYSTEM CALL ERRNO=4 (EINTR) IN FUNCTION SYSV_NSF_OPENSTREAM() 94781 ONPLOAD GIVES "ONPLOAD MUST RUN ON THE HOST (HOSTNAME) THAT CONTAIN THE TARGET DATABASE" IF MACHINE HAS 2 ETHERNET CARDS, THEREFORE 2 ADDRESSES 95052 INCORRECT FILES/DIRECTORIES CAN BE REMOVED IF ONINIT IS RUN WITHOUT INFORMIXDIR BEING SET 95744 DBLOAD FAILS WITH LOC_OPEN() FAILED, NOT OWNER LOADING A TABLE WITH A BLOB COLUMN FROM A FLAT FILE. 95865 HDR - CREATING INDEX ON PRIMARY CAUSES SECONDARY TO GO INTO A BLOCKED CHECKPOINT STATE AND EVENTUALLY PING TIMEOUT 96189 LISTENER THREAD CAN GET CAUGHT RUNNING FOREVER IF POLL THREAD IS BOUND TO THE SAME VP. ENGINE HANGS, NO NEW CONNECTIONS 96218 GROUPER COMPRESSION TIES UP CPUVP 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. SQLIDEBUG SHOWS THAT FETCH BUFFER IS USED AS IF IT WAS ONLY 1 KBYTE NOT THE REPORTED TUPLE BUFFER SIZE 96575 GROUPER FANOUT ABORT OCCURING BECAUSE DDRBLOCK NOT BEING SET CORRECTLY 96741 WHEN USING ER MONITOR FROM NT TO SEE SENDQ ON UNIX SERVER DOING REPLICATION, IT TIMES OUT AND ONSNMP ON UNIX USES 99% OF CPU TIME 96790 CDR - SECONDARY ENGINE CRASHED AFTER A LONG TRANSACTION IS REACHED ON THE PRIMARY. 97546 ALTER FRAGMENT (DETACH), REPORTS 407 ERROR WHEN TABLE IS BEING ACCESSED BY OTHER USERS. 97944 SYSTEM HANG. NEGATIVE SLEEP TIMES SHOWING. OTHER BAD BEHAVIOR POSSIBLE (I.E. CRASHES, CORRUPTION, ETC.) 97949 ERROR -951 ON CONNECT WHEN USING PASSWD EXPIRATION AND TRUSTED MODE ON HP-UX 97963 ONPLOAD ROUNDS LARGE DECIMAL NUMBERS WHEN LOADING 98467 QUICK ATTACH USING ALTER FRAGMENT ATTACH. AFTER ATTACH, STATISTICS ON THE SURVIVING TABLE ARE STILL INTACT BUT STATISTICS FROM CONSUMED TABLE ARE NOT 98908 SIZE OF BLOBS IN OPTICAL MEDIA DIFFERS WITH SIZE IN MAGNETIC MEDIA IF THE SIZE IS BIGGER THAN OPCACHEMAX OR IN HIGH VOLUME INSERTS 99227 ASSERT FAILURE - NO EXCEPTION HANDLER WHEN CREATING A STORED PROCEDURE 99238 RESTORE HANG WHEN TRYING TO GET EMPTY BUFFERS IN RSWRITE_PHR() 99268 TIME-BASED REPLICATION WORKING AS IMMEDIATE CONTINUOUS REPLICATION, AND PRIMARY SERVER ALLOCATING SHARED MEMORY SEGMENTS INDEFINITELY. 100622 -951 ERROR ON CONNECTING TO A DB ON SOLARIS IF PASSWORD AGING IS USED 100936 ISM_COMPRESSION=TRUE DOESN'T CREATE A COMPRESSED ARCHIVE OF THE DATA ON SEQUENT. 100976 CHANGING TRIGGER OR SCOPE ON TRANSACTION CAUSES REPLICATE TO ALSO BECOME TIME-BASED V. BUGS FIXED IN THE 7.30.UC7 RELEASE 84894 MGM ACTIVE/READY QUEUE BECOMES CORRUPT ON BUSY SYSTEM. THIS CAUSES THE ONSTAT -G MGM OUTPUT TO BE GARBAGE BUT COULD ALSO CAUSE SEGV/BUS ERROR. 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. 97544 USING AN UPDATE CURSOR WHERE THERE IS AN IN-CLAUSE IN THE CURSOR DECLARATION YOU GET ERROR 290. 97885 COMPLEX QUERY WITH CORRELATED SUBQUERY BASED ON A VIEW RESULTS IN WRONG RESULTS -- SYSTEM HUNG OR SEGV -- DEPENDING ON QUERY AND ONLINE VERSION 98235 ENGINE CRASH EXECUTING STORED PROCEDURE HAVING A SELECT AGGREGATE WHEN THE STORE PROCEDURE PLAN WAS SAVED WITH PDQPRIORITY > 1 98437 IT TAKES TOO LONG TO CONNECT FROM ONLINE 5 TO IDS 7.2 WHEN MAKING A LARGE NUMBER OF CONNECTIONS 98884 SIGN EXTENSION OF PARTN->PN_FLAGS CAUSES INDEXES TO NOT BE UPDATED WHEN DELETING ROWS AFTER A LIGHT APPEND OPERATION. 99075 SELECT VARCHAR CONTAINING A DECIMAL VALUE AFTER UPDATE STATISTICS MED/HIGH W/DISTRIBUTIONS RETURNS A -1213 ERROR. 99153 ONSTAT -Z CAN CRASH SERVER IN DOSPINLOCK() 100371 ENGINE CRASHES IN THE MIDDLE OF EXECUTING STORED PROCEDURES - MEMORY CORRUPTION 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 101162 CRASH EXECUTING STORED PROCEDURE WHEN REOPTIMIZATION OCCURS 101043 AIX KAIO HAS A FIXED (NON-TUNABLE) ARRAY OF REQUEST THAT CAN NOT jBE RESIZED LEADING TO THE FOLLOWING ERRORS "_AIOWRITE() RETURNING EAGAIN" 102180 SELECT * FROM TAB1 WHERE DATECOL <> '' RETURNS NO ROWS BUT THERE ARE ROWS IN TABLE TAB1. 102824 ROLLBACK/ROLLFORWARD ERRORS DUE TO LOG RECORD CORRUPTION ON DEC ALPHA AND OTHER PLATFORMS WITH UNSAFE BYCOPY'S 103473 7.3 CRASH WITH PAGE CHECK ERROR IN UNDOPGALTER:UNDO_ROWALTER IN A ROLLBACK VI. BUGS FIXED IN THE 7.30.UC8 RELEASE 98572 OPTIMIZER IS TRUNCATING LOWER INDEX FILTER CAUSING INCORRECT DATA TO BE RETURNED. 85352 PERFORMANCE DEGRADES SIGNIFICANTLY BETWEEN V5.* AND V7.* ON A QUERY THAT USED A DYNAMIC COMPOSITE INDEX IN VERSION 5 101518 PERFORMANCE DEGRADATION WITH FIRST_ROWS HINT 102350 DELETING LOGICAL LOG FROM ROOTDBS CORRUPTS THE DBSPACE FLAG INFO IN SHARED MEMORY. 1214 ERROR SEEN THROUGH DBACCESS-DATABASE-INFO-DBSPACE. 39616 WHEN DBLANG IS SET,IF A REQUIRED .IEM FILE IS FOUND BUT THE REQUIRED MESSAGE NUMBER IS NOT FOUND DBACCESS SHOULD USE THE ENGLISH EQUIVALENT. 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 93881 USING AN INDEX IN THE REVERSE ORDER MAY NOT RETURN THE CORRECT ROWS 94088 ONINIT CORE DUMPS IF INFORMIXDIR VARIABLE IS NOT SET 97014 GROUPER MUTEX UNLOCKED TWICE, CORRUPTS GROUPER'S GLOBAL AND POSSIBLY SERIAL AND FREE TX LISTS, MAY CAUSE GROUPER HANG 97762 ASSERT FAILED: PTMAP: BAD PAGENUM = XXX -- ONLY XXX PAGES WHEN RUNNING UPDATE STATISTICE MEDIUM 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 99365 DISTRIBUTED FETCH CRASHES THE SERVER AFTER THE FUNCTION GET_DIST 100882 DBSCHEMA WITH -D AND -T OPTION CAUSES CORE DUMP IF THE LENGTH OF OWNER.TABLE IS GREATER THAN 17 CHARACTERS. 101809 RSAM CRASH ON PAGE CHECK ERROR WHEN TX ON FRAGMENTED TABLE ROLLED BACK 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. 103257 DBCENTURY ENVIRONMENT VARIABLE IS NOT PASSED TO COMMANDS EXECUTED BY STORED PROCEDURES WHICH AFFECTS HPL JOBS RUN THROUGH THE GUI 103323 MEMORY CORRUPTION AND -858 ERROR WHEN ADDING A FRAGMENT TO A FRAGMENTED TABLE WITH A DISABLED INDEX 103720 BLOB FETCH FAILS WHEN BLOB HAS BEEN UPDATED WHILE CURSOR IS OPEN 104883 CENTURY IS EXPANDED WRONG IN A DATETIME YEAR TO MONTH FIELD IF DBCENTURY (C|P|F) AND CURRENT DAY > MAX. DAY OF ENTERED MONTH(DUP OF 99565) 105501 HITTING CONTROL-C WITHIN DBACCESS WHILE ON A TCP NETWORK CONNECTION LOSES CONNECTION (CORE DUMPS) 105599 STACK TRACE FEATURE DOESN'T WORK ON DIGITAL UNIX 4.0D ALL FUNCTION NAMES ARE DISPLAYED AS ***NOSYMTAB*** 106931 ALTER TABLE WILL CORRUPT TABLE IF ADDING A COLUMN AND ALTERING A DECIMAL COLUMN AND SUBSEQUENT SELECT/DROP TABLE WILL ASSERT FAIL 107324 KERNEL MEMORY LEAK ON NCR WHEN USING KAIO AND DBT/DBIO PACKAGE BUG 49475 NOT COMPLETELY FIXED 104205 ONSTAT -G STK DOES NOT WORK, AND STACK TRACES ARE NOT GENERATED IN AF FILES ON IBM/AIX FOR ONLINE 7.30.UC5 AND 7.30.UC6 100882 DBSCHEMA WITH -D AND -T OPTION CAUSES CORE DUMP IF THE LENGTH OF OWNER.TABLE IS GREATER THAN 17 CHARACTERS. 76354 CODE INSPECTION BUG: TLI/SOCKET LISTENER CAN YIELD FOR UP TO 3 MINS AND PREVENT FURTHER CONNECTION ATTEMPTS TO HANG. 97949 ERROR -951 ON CONNECT WHEN USING PASSWD EXPIRATION AND TRUSTED MODE ON HP-UX 100180 ALTER TABLE ADD 2 COLUMNS BEFORE COLUMN CRASHES SERVER 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 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 103418 SELECT MAX(COL) APPEARS TO BE RETURNING THE MINIMUM VALUE INSTEAD OF THE MAXIMUM VALUE WHEN AN INDEX IS CREATED IN DESC ORDER. 104488 COLMIN AND COLMAX SHOWS NEGATIVE VALUES AFTER UPDATE STATISTICS 105530 WHEN TZ IS SET TO SOME TIMEZONE+/-OFFSET WHERE OFFSET IS NOT IN WHOLE UNIT OF HOURS, RTODAY DELAYS RETURNING THE CORRECT DAY. 104488 COLMIN AND COLMAX SHOWS NEGATIVE VALUES AFTER UPDATE STATISTICS 93221 PAGE_T IS A SYSTEM DEFINED TYPEDEF ON HP 10.20 & ABOVE. THE INFORMIX DEFNUNDER INCL/RSPAGE.H BECOMES A DUPLICATE DEFN 104188 ONMODE -B 7.2 (FROM 7.30) FAILS TO LIST TABLES THAT HAVE ACTIVE IN-PLACE ALTER TABLES. 105890 7.30.UC7 BACKPORT OF BUG B100836 HAS MISMATCHED DEFINES AND LG_TYPES STRINGS. 101866 ONMONITOR DISPLAYS 2 DIGIT YEAR FOR CREATION DATE OF DATABASES, CHUNKS AND DBSPACES. "00" WILL BE DISPLAYED IN YEAR 2000 AS CREATION DATE. 102150 HIGH PERFORMANCE LOADER FAILS TO INSERT ONE ROW WHEN LOADS RECORDS WITH BLOB USING PIPE 102718 ONSTAT -O CAN BE RUN BY EVERY USER - IT SHOULD ONLY BE POSSIBLE BY USER INFORMIX OR ROOT. 99835 Y2000 TESTING-SEVERAL UTILITIES INCORRECTLY DISPLAY DATES GREATER THAN 12/31/1999 101437 A USER OTHER THAN INFORMIX OR ROOT CAN RUN ONCHECK -CI AND REPAIR INDEXES 102039 ONPARAMS -A -D DBSPACE GETS ERROR 1 CANNOT ACCESS CONFIGURATION FILE /usr3/jyang/sqldist_dis/ETC/ VII. BUGS FIXED IN THE 7.30.UC9 RELEASE Note:PTS#99943 fix has been removed from this release because, it causes IECC server agent to break 112605 DCE-CSM REMOVAL FROM SERVER 105771 DBLOAD INSERTS 0 (VALUE ZERO) INTO INTEGER COLUMN INSTEAD OF SPECIFIED INTEGER VALUES ON 64-BIT SYSTEMS 108594 DBLOAD FAILS WITH LOC_OPEN() FAILED, NOT OWNER LOADING A TABLE WITH A BLOB COLUMN FROM A FLAT FILE. 77476 ASSERT FAILURE: ROWID X OT FOUND FOR DELETE IN PARTNUM WHEN CONSTRAINTS ARE VIOLATED - GEOPOINT DATAT TYPE INVOLVE 77844 ONCHECK -CI REPORTS AN INDEX AS BAD, WHEN THERE IS AN UNCOMMITTED TRANSACTION THAT UPDATES THAT INDEX 82387 ENGINE CRASHES IN GCVFPRINTF() WHEN RUNNING STORED PROCEDURE WITH SET TRACE ON AND SET DEBUG FILE 91560 7.24.UC3,OPTIMIZER PICKS WRONG FRAGMENT FOR A NON-SUBSTRING FRAGMENTED TABLE WHEN SELECT INVOLVES A SUBSTRING WHERE CLAUSE 94413 IN-PLACE ALTER OF A ROW OF SIZE LARGER THAN ONE PAGE CRASHES THE ENGINE 95341 ONLINE CRASHES WHEN U DO AN ALTER TABLE, MODIFY COL BOTH IN DBACCESS AS WELL AS ESQL/C CODE 96374 SERVER HANGS WHEN ACCESSING A TABLE IN A 9.X SERVER FROM A 7.3 SERVER 98425 QUERY OPTIMIZER CHOOSES WRONG INDEX WHEN NUMBER OF LEVELS IS HIGHER 98932 DATA DICTIONARY/DISTRIBUTIONS/PROCECURE CACHES HASH ALGORITHM IS VERY POOR WHEN USING TYPICAL CUSTOMER TABLE NAMES 101361 SUSPENDING AND RESUMING LOGICAL RESTORE LOOSES 1 BUFFER FROM THE QUEUE IN EVERY LOOP 101689 ASSERTION FAILURE IN SQLEXEC AFTER A SUCCESSFUL COMPLETION OF A LEVEL 1 ARCHIVE. FOUND IN TEST ONLINE/UTIL/SRC/INC002.JOB STEP 7B. 103231 SERVER HANGS IN LOGICAL RECOVERY WITH USED LOG THAT CANNOT BE BACKED UP IF START LOG UNIQID < STARTING LOG POSITION UNIQID 104144 ONTAPE THREAD CRASHES ENGINE DURING INITIALIZATION WITH THE ERROR: I/O BAD REQUEST CHUNK 4095, PAGENUM 1048575, PAGECNT 1 104318 NUMCPUVP > 1 CAUSES DELETE STATEMENT WITH 3000+ CHARACTERS TO ASSERT FAIL WITH -243/-172 READ_RECORD DELETED ROWID, PARTNUM 105425 ONLINE HAD SEGMENTATION VIOLATION AT BLDDICREF() 106680 SEGV WHEN INSERTING INTO CHUNK THAT IS FULL - RELATED TO LIGHT APPENDS 107217 DEC-ALPHA: DECBYCOPY CAUSES LOGICAL LOG CORRUPTION AND THEN RESULTS IN VARIOUS ROLLBACK AND ROLLFORWARD PROBLEMS INCLUDING ROWID NOT FOUND ERRORS 107221 DUPLICATE ROWS IN ORDERED CURSOR WITH PENDING ALTER TABLE !SAP! 107840 PHYSICAL RECOVERY CAN HANG IN AND ENDLESS LOOP, SO WE REPLACE ,ALL THE PHYSICAL LOG PAGES BACK OUT TO DISK, CAUSING CORRUPTION 107906 FEWER ROWS RETURNED FROM OUTER JOIN QUERY AFTER UPDATE STATS IS RUN 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. 108947 SERVER HUNG, CPU VP SPINNING INDEFINITELY, ONLY ONSTAT COMMANDS RESPOND !BAAN! 109083 A SELECT SUM USING A CASE EXPRESION WITHIN A SUBQUERY RETURNS A INCORRECT SUM VALUE 109139 TEMP SPACE NOT FREED WHEN FRONT END SESSION IS KILLED, BUT SESSION HAS GONE FROM ONSTAT -U. SPACE RECLAIMED WHEN ENGINE IS BOUNCED. 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 89287 73BETA: SEQSCANS FROM SYSPTPROF IN SYSMASTER IS INCREMENTED WHEN A KEYFIRST INDEX SCAN IS DONE 99102 USING NON TCB(TRUSTED COMPUTER BASE ON HP) YOU RECEIVE ERROR 952 IF YOU ENTER A PASSWORD THAT IS GREATER THAN 8 CHARACTERS 101680 USER WILL GET 951 TRYING TO CONNECT IF THEY HAVE NEVER UPDATED THEIR PASSWORD BEFORE 104218 CDR CHANGE REPLICATE -D DOES DELETE SERVER DOES NOT REMOVE THE PARTICIPANT FROM REPLICATE. 105530 WHEN TZ IS SET TO SOME TIMEZONE+/-OFFSET WHERE OFFSET IS NOT IN WHOLE UNIT OF HOURS, RTODAY DELAYS RETURNING THE CORRECT DAY. 108113 QUERY FALLS INTO A LOOP DOING A LOT OF NREADS AND NEVER RETURNS IN 7.30.UC7 108815 CDR MODIFY REPLICATE COMMAND DOES NOT UPDATE GLOBAL CATALOG WHEN ATTEMPTING TO DISABLE RIS AND ATS SPOOLING 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 97883 HUGE PERFORMANCE PROBLEM WITH ONCHECK -CI (UPPER CASE) IN 7.30 COMPARED TO 7.2X 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 103940 ONTAPE DOES NOT REPORTS ABOUT REMOTE TAPE FAILURE REASON 103719 DBSPACE NAME GETS NULL TERMINATED BY ONCHECK, STRTOK IS USED ON DS_NAME 114535 ONPLOAD GETS SEGV WHILE LOADING DATA FILE VIII. BUGS FIXED IN THE 7.30.UC10 RELEASE Note: We also fixed "onstat -g dmp" problem in this release 105601 SINIX/SGI: STACK TRACE WITH KILL -7 ON RUNNING THREADS DOES NOT WORK 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 98607 A PREPARED SELECT STATEMENT WITH GROUP BY CAN CRASH THE SERVER WITH SEGV, THIS IS RELATED TO PTS-B #87086 99153 ONSTAT -Z CAN CRASH SERVER IN DOSPINLOCK() 100142 SAP: INLINE POLL-THREAD CRASHES IN REBUILD_POLL_LIST() ON DIGITAL UNIX 100676 LOG BACKUP FAILS AS QUERY ON SYSMASTER:SYSRSTCB FROM PRRSTCB() RETURNS LESS NUMBER OF COLUMNS(ONE) 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 105714 KAIO DOESN'T WORK ON IRIX 6.2, 6.4 AND 6.5 WITH NEW SGI KAIO PATCHES. SEE DEATILS IN THE LONG DESCRIPTION. 108092 Y2K (Y2000) PROBLEM: CHANGING INTERPRETATION OF DATE AND DATETIME VALUES COULD RESULT IN UNEXPECTED AND/OR WRONG RESULTS 109257 CAN GET SEMOP() FAILURES ERRNO=34 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 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 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. 108317 ONCHECK CAUSES SMALL SERVER MEMORY LEAK PER INVOCATION 109072 INDEX COST TOO LOW WHEN EQUALITY FILTER COLUMN USES A SUBSCRIPT SUCH AS COL[1,1] = 'H'; RESULTS IN POOR INDEX CHOICE 110423 IDS LINUX EDITION: CONNECT WITH USER/PASSWD FAILS ON SERVERS WHICH USE SHADOW OR MD5 PASSWD FILES. NEED FURTHER MODS TO OSPASSWD.C, OSAUTH.C 117867 DEF_BSALIB_PATH SHOULD POINT TO /USR/LIB32 FOR 32-BIT AND /USR/LIB64 FOR 64-BIT SERVER IN ON-BAR/BAR_UNIX.C. CORR. CHANGES WERE MADE ON ISM 2.20. 118155 ALLOW NOLRUPRIO FEATURE IN 7.3X AND FIX BUG 111681 95599 REGRESSION: RECEIVED INCORRECT ERROR MESSAGE -1204 INSTEAD OF EXPECTED -271/-883 USING DBDATE 116509 ONMONITOR: PARAMETERS -> PERFORMANCE RESULTS IN BUS ERROR COREDUMP ON SIEMENS 64 BIT PORT (7.30.FC7) 114197 PERFORMANCE PARAMETERS THAT DON'T HAVE A INTEGER VALUE CONFIGURED IN THE ONCONFIG FILE ARE DISPLAYED WITH VALUE -1 IN ONMONITOR 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 116352 DBCENTURY AND DBDATE IS NOT WORKING IN CONJUNCTION WITH DATE IN CHECK CONSTRAINT,FRAGMENTATION,STORED PROCEDURES,AND TRIGGERS. 118591 SELECT ROWID STATEMENT RETRIEVES ONLY ONE ROW AFTER TABLE HAS BEEN ALTERED 94499 SINIX: ONPERF HELP FUNCTION DOES NOT WORK 117867 DEF_BSALIB_PATH SHOULD POINT TO /USR/LIB32 FOR 32-BIT AND /USR/LIB64 FOR 64-BIT SERVER IN ON-BAR/BAR_UNIX.C. CORR. CHANGES WERE MADE ON ISM 2.20. IX. Interpretation of two digit years within objects 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 in 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, the date literals in the expressions within objects will 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 a 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 run time 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 run time are consistent throughout.