CONTENTS Title Page Copyright Page Preface 1 Software Problems Fixed in Rdb/VMS V4.0B 1.1 General Information 1.1.1 Privileges Required to Execute the RMU/DUMP, RMU/OPEN, and RMU/CLOSE Commands 1.2 Software Problems Fixed That Apply to All Interfaces of Rdb/VMS V4.0B 1.2.1 Total Relation Boolean Was Not Generated Properly in a Leaf Strategy 1.2.2 ALTER STORAGE MAP Statement Caused Rdb/VMS to Bugcheck When Combined with Disabling Compression 1.2.3 SQL or RDO Hung During INTEGRATE Operation 1.2.4 Optimizer Did Not Recognize That an Index Segment Was Compressed 1.2.5 Defining a Remote Logical Name Denied Access to the Local Node 1.2.6 Transfer of Large Blocks of Data over the Network Resulted in an Error 1.2.7 COBOL Lines Generated That Did Not Comply with the ANSI Standards 1.2.8 Optimization of Constraint Processing Was Limited 1.2.9 NOWAIT Transactions Started During a Recovery Process Caused an RDMS-F-AREABUSY Fatal Error 1.2.10 DACCESS Audit Event Required a Minimal Set of Privileges for Auditing to Occur 1.2.11 UPDATE Privilege Access for Table with DACCESS Audit Event Was Not Captured 1.2.12 Virtual Memory Increased with Some Fourth Generation Languages 1.2.13 Collating Sequence Problems 1.2.14 Improper Error Displayed When Exporting and Importing to Use a Different Collating Sequence 1.2.15 Multisegmented Index Was Not Selected When a Not-Equal Predicate Was Specified 1.2.16 Privilege Violation in Batch-Update Caused Database Corruption 1.2.17 A Join Query Matched a Null Aggregate or Expression to a Column with Zeros or Blanks and Produced Incorrect Resul 1.2.18 Bugcheck Occurred with an Exception at RDMS$$RSS$ASN_FOR_RSS$NDX 1.2.19 Incorrect Results Returned on Join Operations Using Partitioned Indexes 1.2.20 Arithmetic Exception Resulted When Joining Integer Columns 1.2.21 Query with Computed-By Field and OR Returned Incorrect Results 1.2.22 CHANGE DATABASE Statement Resulted in Bad Parameter Error Message 1.2.23 Defining a Partitioned Hashed Index Resulted in Corruption 1.2.24 Change in Operation of Index Deletion 1.2.25 Rdb/VMS Monitor Failed When the Last User Finished on a Particular Database 1.2.26 Comparing Integer and Text Fields Caused Problems 1.3 SQL Problems Fixed in Rdb/VMS V4.0B 1.3.1 REORGANIZE Clause Caused a Bugcheck 1.3.2 Updating the Cardinality of a Relation Caused a Bugcheck 1.3.3 Memory Lost Between Database Attaches 1.3.4 Incorrect Conversion of Numeric Data Types Caused Erroneous Values for Scales 1.3.5 Using the IGNORE CASE Option of the LIKE Clause Sometimes Resulted in a Query That Incorrectly Returned No Rows 1.3.6 Record Parameters Could Not Be Used Where Values Were Expected 1.3.7 Certain Trigger Definitions Caused a Bugcheck 1.3.8 SQLTYPE Value Fixed in the SQLDA 1.3.9 Bugcheck Returned by System When User with Incorrect Privileges Showed Protection on a Schema 1.3.10 SQL Incompatibilities in Rdb/VMS V4.0 That Are Fixed in Rdb/VMS V4.0B 1.3.10.1 Incompatibilities Between Object Modules 1.3.10.2 Incompatibilities Between TABLE and LIST Cursors 1.3.10.3 Incompatibilities Between Cursors and COMMIT or ROLLBACK Statements 1.3.11 Message Vector Contained Erroneous Information About the Number of Longwords Used 1.3.12 Common Data Dictionary (CDD/Plus) Fields with Scales Were Not Always Properly Translated 1.3.13 UNION Queries Returned Incorrect Data on Numeric Data Types 1.3.14 Modules That Used the DECLARE TRANSACTION Statement Were Ignoring TXN Attributes 1.3.15 Embedded SQL Ada Programs Could Not Use LIST Cursors 1.3.16 Views That Selected Dbkeys Caused a Bugcheck 1.3.17 Dynamic SQL Statements with Indicator Arrays Were Not Correctly Handled Prior to Rdb/VMS V4.0B 1.3.18 SQL Allocated More Memory Than Necessary During a Dynamic SET TRANSACTION Statement 1.3.19 Preparing a Statement with D-float Parameters Caused a Bugcheck 1.4 SQL/Services Problems Fixed in Rdb/VMS V4.0B 1.4.1 Unpredictable Results Occurred When Trying to Store Segmented Strings from the Macintosh Environment Using DECnet 1.4.2 Certain Calls to the sqlsrv_fetch_many Routine Caused Problems 1.4.3 Authorization Failure Occurred When SYSUAF Flag LOCKPWD Was Set 1.4.4 Column Limit Raised to 500 1.4.5 SQL/Services Failure Did Not Produce a Bugcheck File 1.4.6 VMS Application Programming Interface (API) Installation Failed Without Rdb/VMS 1.4.7 SQL$STARTUP.COM Startup File Contained an Error in the SQL/Services Startup Logical Name 1.4.8 SQL/Services MS-DOS API Installation Failed 1.4.9 Macintosh API Installation Failed 1.4.10 Node Names Containing Numeric Characters Were Improperly Made Uppercase in OS/2 API 1.5 RDO, Callable RDO, RDBPRE, and RDML Problems Fixed in Rdb/VMS V4.0B 1.5.1 Incorrect Value Was Stored During an RDO STORE or MODIFY Operation 1.5.2 Multiple RDO Commands in a FOR Loop Caused Unpredictable Results 1.5.3 A Query Using Static OR and a Common Subexpression in Two or More OR Legs Produced Incorrect Results 1.5.4 RDB$INTERPRET Now Fully Supports VS (Varying String) Descriptors 1.5.5 Query with a FOR Loop and MODIFY Statement Followed by a PRINT Statement Returned Incorrect Results 1.5.6 Bugcheck Returned Because CHANGE FIELD Had No VALID IF 1.5.7 Shared Fields in a Relation and a View Caused a Bugcheck 1.5.8 Changing Records in CDD/Plus Caused an Error 1.6 RMU Problems Fixed in Rdb/VMS V4.0B 1.6.1 RMU/VERIFY Reported False MINGTRSIZ Error Messages 1.6.2 RMU/VERIFY Reported False AIPENTMBZ Warning Messages 1.6.3 Index Cardinality Not Maintained When an Application Performed Only a Few Insertions or Deletions 1.6.4 RMU/CLOSE/CLUSTER/WAIT Hung the Database in a Cluster Environment 1.6.5 SPAM Threshold Calculations Resulted in Errors Reported by the RMU/VERIFY Command 1.6.6 Hashed Index Verification Caused Buffer Flushing Problem 1.6.7 RMU/COPY or RMU/MOVE Command Incorrectly Copied Area Inventory Pages (AIP) 1.6.8 TA90E and TA91 Tape Drives Were Not Recognized in Rdb/VMS V4.0B 2 Known Problems, Restrictions, and Other Notes for Rdb/VMS V4.0B 2.1 General Problems, Restrictions, and Notes 2.1.1 Singleton Subselect Statement Returning Incorrect Results Partially Fixed in Rdb/VMS V4.0A But Not Fixed in V4.0B 2.1.2 VMS Lock Remastering Changed in VMS V5.4 2.2 Problems, Restrictions, and Notes for All Interfaces 2.2.1 Queries Using LIKE Predicate Run Slowly 2.2.2 Sequential Retrieval Causes Problems with Dynamic Optimizer 2.2.3 Anomalous Update Occurs with Subqueries 2.2.4 INSERT Command to Double the Contents of a Table Results in an I/O Loop 2.2.5 A Problem in PSII$DELETE_EMPTY_NODE Causes an Error 2.2.6 Range Query Returns Unexpected Results 2.2.7 Cannot Correctly Import a Database That Contains Computed-By Fields That Reference Other Computed-By Fields 2.2.8 Using Quoted Threshold Values for Binary Data Types for Partitioning Data or Indexes Results in Data or Index Cor 2.2.9 Problem Comparing Different Data Types 2.2.10 RDB$REMOTE Account That Has SYSTEM as Owner Creates Installation Problems 2.2.11 Read/Write Query with Multiple Range Predicates on an Index Column Performs Poorly 2.2.12 Synchronization Problem for an Empty Sorted Index 2.2.13 Query Optimizer Does Not Choose Index-Only Retrieval When the Dbkey Is Selected 2.2.14 Rdb/VMS Hangs on a SELECT Statement When a Column Data Type Is Changed from INTEGER to CHARACTER to DATE 2.2.15 Triggers That Affect Subject Table Rows Can Cause Loops or Inconsistent Results 2.2.16 Relation Name Must Match Dictionary Record Name 2.2.17 NOWAIT Transactions Have Their Buffers Invalidated at Commit Time 2.3 SQL Problems, Restrictions, and Notes 2.3.1 SQL Deprecated Features and Incompatible Changes for VAX Rdb/VMS V4.1 2.3.2 SQL to Support Error Code Values in Rdb/VMS V4.1 2.3.3 An SQL SELECT Statement Results in an Invalid BLR Error 2.4 RDO, RDBPRE, and RDML Problems, Restrictions, and Notes 2.4.1 An Incompatible Change for RDO Applications: New Update Rules Will Be Enforced by Default in Rdb/VMS V4.1 2.4.2 Aggregate Expressions in RDO Return an Error 2.4.3 Certain Reserved Words Cannot Be Used as Database Handles for RDBPRE or as Aliases for SQL$PRE and SQL$MOD 2.4.4 Wrong Number of Records Returned by a Query in an Inner FOR Loop 2.4.5 RDO IMPORT Statement Does Not Save All SQL Defined Attributes 2.4.6 RDO CONVERT Statement on V3.0 Databases Causes Database Corruption When the Database Is Converted to V4.0B 2.5 Rdb/VMS Management Utility (RMU) Problems, Restrictions, and Notes 2.5.1 Do Not Delete After-Image Journal (.AIJ) Backup Files if the AIJ Backup Fails or Is Terminated 2.5.2 Concealed Logicals Are Supported but No Longer Recommended for Use After V4.0 2.6 Problems and Restrictions Related to the Common Data Dictionary (CDD/Plus) 2.6.1 RDO or SQL INTEGRATE Statement Fails with a NO_META_UPDATE Error 2.6.2 Restriction with CDD/Plus V4.3 2.7 Rdb/VMS Documentation Errors and Omissions in V4.0 2.7.1 Undocumented SQL ALTER DOMAIN and RDO CHANGE FIELD Statement Restriction 2.7.2 Documentation Error Regarding Microsoft C Compatible Assembler Required for the SQL/Services MS-DOS Application I 2.7.3 Incorrect Reference in V4.0 VAX Rdb/VMS SQL Reference Manual , Chapter 3 2.7.4 Printing Error in V4.0 VAX Rdb/VMS SQL Reference Manual , Chapter 4 2.7.5 Documentation Error in V4.0 VAX Rdb/VMS SQL Reference Manual , Appendix D.4 2.7.6 SQL/Services Error Documentation 2.7.7 RDMS$BIND_VALIDATE_CHANGE_FIELD Logical Name Was Not Documented in V4.0 2.7.8 RDMS$BIND_VM_SEGMENT Logical Name Was Misnamed in the V3.1 Documentation and Was Not Documented in V4.0 2.8 SQL/Services Troubleshooting Suggestions 2.8.1 Common SQL/Services Network Errors 2.8.2 Common SQL/Services Fatal Execution Server Errors 2.8.3 Common SQL/Services API Installation Failures 2.8.4 SQL/Services Compatibility Issues 2.8.4.1 SQL/Services V4.0B Server Uses Proxy-Like and Default Access to Authorize V3.0 or V3.1 Client Applications 2.8.4.2 SQL/Services V4.0B Server Error -2031 Returned to V3.1 Client APIs 2.8.4.3 Queue Manager Must Be Started for the SQL/Services IVP to Work 3 Optional ECO Patches for VAX Rdb/VMS V4.0B 3.1 Optional ECO Patches That Can Be Applied to Rdb/VMS V4.0B 3.1.1 RDMSHRP ECO 30: Poor OR Optimization Performance on Read/Write Transactions TABLES 2-1 SQL/Services Network Errors