CONTENTS Title Page Copyright Page Preface Part I Mandatory Update for VAX Rdb/VMS Version 3.1B 1 Installing the Rdb/VMS Version 3.1B Mandatory Update 1.1 Before Installing the Rdb/VMS Mandatory Update Package for V3.1B 1.1.1 Prerequisite Hardware and Software 1.1.2 Back Up All Existing Rdb/VMS Databases 1.1.3 Disk Space Required to Install the MUP 1.1.4 Shut Down the Rdb/VMS Monitor 1.1.5 Obtain the VMS Privileges Required to Install the MUP 1.1.6 Ensure Sufficient Process Account Quotas to Install the MUP 1.1.7 Obtain System Parameter Values Required to Install the MUP 1.1.7.1 Checking System Parameter Values 1.1.7.2 Calculating the Values for GBLPAGES and GBLSECTIONS 1.1.7.3 Changing System Parameter Values with AUTOGEN 1.1.7.4 Setting Dynamic System Parameters 1.1.8 Back Up Your System Disk 1.1.9 Avoid Giving Users Access to HELP 1.1.10 Prevent Interactive Users from Gaining Access to the System 1.2 Installing the Mandatory Update Package 1.2.1 Time Required to Install the MUP 1.2.2 Invoking VMSINSTAL 1.2.3 Steps of the Installation Procedure 1.2.4 Completing the Installation Procedure 1.2.5 Errors That Cause the Installation to Fail 1.3 After Installing the Mandatory Update Package 1.3.1 Accessing the Online Release Notes 1.3.2 Tailoring Your System 1.3.3 Returning the System to Original Settings 2 Software Errors Fixed in the Mandatory Update for Rdb/VMS V3.1B 2.1 General Information 2.1.1 A VMS Sort Utility Problem Affected Rdb/VMS 2.1.2 The VMS Sort Utility for VMS V5.1, V5.2, and V5.3 Caused Problems with Rdb/VMS Databases 2.2 Software Errors Fixed That Apply to All Interfaces in the Mandatory Update for Version 3.1B 2.2.1 Rdb/VMS Returned Errors When Retrying Failed Multidatabase Transactions 2.2.2 Active Transactions in Application Programs Could Not Recover from Network Failures 2.2.3 Data Transfer from the V3.1B Server Caused Problems 2.2.4 A Partitioned Sorted Index Stored the First Record Incorrectly 2.2.5 Certain Queries with Intended MODIFY Operations Within Read/Write Transactions Caused Unnecessary Writes to the F 2.2.6 Partitioned Sorted Indexes Caused Bugchecks 2.2.7 A MODIFY Operation Caused Index Corruption on Partitioned Hash Indexes 2.2.8 Partitioned Sorted Indexes Resulted in Various Problems 2.2.9 With Compression Disabled, Altering the Storage Map STORE Clause and Then Selecting a Row Resulted in a Bugcheck 2.2.10 A Bugcheck Sometimes Resulted When a Sorted Index Rebalanced Itself 2.2.11 Problem Occurred When Rdb/VMS and the User Application Both Allocated Event Flag 63 2.2.12 Query Returned Records in Wrong Order with the SQL ORDER BY <column-name> DESCENDING or the RDO SORTED BY DESCEND 2.2.13 Negate Operator Incorrectly Propagated the NULL Bit While Processing a Record Stream 2.2.14 Query with Computed-By and OR Index Retrieval Strategy Returned Incorrect Results 2.3 RDO, RDBPRE, and RDML Problems Fixed in the Mandatory Update for V3.1B 2.3.1 RDBPRE Generated Incorrect Code for Request Handles 2.4 RMU Problems Fixed in the Mandatory Update for V3.1B 2.4.1 RMU/VERIFY Returned Spurious Errors Involving Fragmented Records 2.4.2 Attempting to Recover a Database from an .AIJ File Using the RMU/RECOVER Command or RDO RECOVER Statement CausedE 3 Known Problems, Restrictions, and Other Notes for the Mandatory Update for Rdb/VMS V3.1B 3.1 Problems, Restrictions, and Notes for All Interfaces 3.1.1 Using Quoted Threshold Values for Binary Data Types for Partitioning Data or Indexes Results in Data or Index Cor 3.1.2 Problem with SQL LIKE and RDO MATCHING Clauses 3.1.3 RDB$REMOTE Account Has SYSTEM as Owner 3.1.4 RDMSHRP_DS Image Displays Incorrect Values 3.1.5 An Arithmetic Exception Results When Joining Integer Columns 3.1.6 Collating Sequences That Use Two-to-Two Character Mapping May Bugcheck 3.1.7 Synchronization Problem for an Empty Sorted Index 3.1.8 Rdb/VMS Does Not Accept the Database File Specification in a Logical Name 3.1.9 Constraints Cause Looping and LCKCCH$COMMIT_SUBTREE Bugchecks 3.1.10 Query Optimizer Does Not Use Index-Only Retrieval When the Dbkey Is Selected 3.1.11 Query Optimizer Chooses an Incorrect Strategy for a Write Operation Within a Selection Loop and Goes into an Infi 3.1.12 Singleton Subselect Statement Returns Incorrect Results 3.1.13 SPAM Pages Are Not Updated Correctly 3.1.14 Rdb/VMS Monitor Fails When the Last User Finishes on a Particular Database 3.1.15 Triggers That Affect Subject Table Rows Can Cause Loops or Inconsistent Results 3.1.16 Query Using Descending Indexes Returns Incorrect Results 3.1.17 Query with a Computed-By Field and OR Logic Returns Incorrect Results 3.1.18 NOWAIT Transactions Have Their Buffers Invalidated at COMMIT 3.2 SQL Problems, Restrictions, and Notes 3.2.1 Using the IGNORE CASE Option of the LIKE Clause Sometimes Results in a Query That Incorrectly Returns No Rows 3.3 SQL/Services Problems, Restrictions, and Notes 3.3.1 SQL/Services VMS API Shipped with the Rdb/VMS Run-Time Kit 3.4 RDO, RDBPRE, and RDML Problems, Restrictions, and Notes 3.5 Rdb/VMS Management Utility (RMU) Problems, Restrictions, and Notes 3.5.1 Do Not Delete After-Image Journal (.AIJ) Backup Files If the AIJ Backup Fails or Is Terminated 3.5.2 EXPORT Operations Fail with an Access Violation When the Database Has a Default Collating Sequence Defined 3.5.3 Use of Undocumented RMU/REPAIR Command Corrupts Databases 3.6 Notes and Restrictions Related to CDD/Plus 3.6.1 Restrictions Lifted by CDD/Plus Version 4.3 3.7 Rdb/VMS Documentation Errors and Omissions in V3.1B 3.7.1 Documentation Error in V3.1 VAX Rdb/VMS SQL Reference Manual , Appendix D.4 4 Optional ECO Patches for the Mandatory Update for VAX Rdb/VMS V3.1B 4.1 Optional ECO Patches That Can Be Applied to the Mandatory Update for Rdb/VMS V3.1B 4.1.1 RDMSHRP ECO 1: Constraints Cause Looping and LCKCCH$COMMIT_SUBTREE Bugchecks 4.1.2 RDMSHRP ECO 14: Query Optimizer Does Not Use Index-Only Retrieval When the Dbkey Is Selected 4.1.3 RDMSHRP ECO 19: Query Optimizer Chooses an Incorrect Strategy for a Write Operation Within a Selection Loop andi 4.1.4 RDMMON ECO 1: Rdb/VMS Monitor Fails When the Last User Finishes on a Particular Database Part II Mandatory Update for VAX Rdb/VMS Version 4.0 5 Installing the Rdb/VMS Mandatory Update for Version 4.0 5.1 Before Installing the Rdb/VMS Mandatory Update Package for Rdb/VMS Version 4.0 5.1.1 Prerequisite Hardware and Software 5.1.2 Back Up All Existing Rdb/VMS Databases 5.1.3 Disk Space Required to Install the MUP 5.1.4 Shut Down the Rdb/VMS Monitor 5.1.5 Obtain VMS Privileges Required to Install the MUP 5.1.6 Ensure Sufficient Process Account Quotas to Install the MUP 5.1.7 Obtain System Parameter Values Required to Install the MUP 5.1.7.1 Checking System Parameter Values 5.1.7.2 Calculating the Values for GBLPAGES and GBLSECTIONS 5.1.7.3 Changing System Parameter Values with AUTOGEN 5.1.7.4 Setting Dynamic System Parameters 5.1.8 Back Up Your System Disk 5.1.9 Avoid Giving Users Access to HELP 5.1.10 Prevent Interactive Users from Gaining Access to the System 5.2 Installing the Mandatory Update Package 5.2.1 Time Required to Install the MUP 5.2.2 Invoking VMSINSTAL 5.2.3 Steps of the Installation Procedure 5.2.4 Completing the Installation Procedure 5.2.5 Errors That Cause the Installation to Fail 5.3 After Installing the MUP 5.3.1 Accessing the Online Release Notes 5.3.2 Tailoring Your System 5.3.3 Returning the System to Original Settings 6 Software Errors Fixed in the Mandatory Update for Rdb/VMS V4.0 6.1 General Information 6.1.1 The VMS Sort Utility for VMS V5.1, V5.2, and V5.3 Caused Problems with Rdb/VMS Databases 6.2 Software Errors Fixed That Apply to All Interfaces in the Mandatory Update for Version 4.0 6.2.1 Wrong RDBINTSHR.EXE Image Was Installed for Interactive License Customers 6.2.2 Active Transactions in Application Programs Could Not Recover from Network Failures 6.2.3 Using Event Flags Caused Conflicts with Other Software Products 6.2.4 An Access Violation Resulted When DECdtm Services and DECnet Services Were Not Running 6.2.5 If a Commit Failed During a One-Phase Commit Protocol When an Explicit Distributed Transaction Was Run, It Cause$ 6.2.6 The Rdb/VMS DISTRIBTRAN Privilege Was Not Available for Remote Database Access 6.2.7 A Partitioned Sorted Index Stored the First Record Incorrectly 6.2.8 A MODIFY Operation Caused Index Corruption on Partitioned Hash Indexes 6.2.9 Partitioned Sorted Indexes Resulted in Various Problems 6.2.10 You Could Not Define Views Based on System Relations 6.2.11 An Incorrect Value Was Stored or a Bugcheck Resulted When Using BEFORE UPDATE or BEFORE MODIFY Triggers 6.2.12 Queries with Computed Expressions and Indexes Returned the Wrong Results 6.2.13 Queries with Computed Expressions Returned the Wrong Results 6.2.14 Some Update-Intensive Applications Experienced a Performance Degradation in Rdb/VMS V4.0 Compared to V3.1B 6.2.15 Poor Performance Was Experienced While Retrieving Views by Dbkey 6.2.16 Wrong Results Were Returned from Queries That Used Collating Sequences and the STARTING WITH "" Relational Operat 6.2.17 Recovery-Unit Journal (.RUJ) Files Could Not Be Created Using Angle Brackets (< >) 6.2.18 A Bugcheck Sometimes Resulted When a Sorted Index Rebalanced Itself 6.2.19 NOWAIT Transactions Started During a Recovery Process Caused an RDMS-F-AREABUSY Fatal Error 6.2.20 The Query Optimizer Caused Various Bugchecks When Queries Were Run 6.2.21 Shared Write Queries Consumed More Memory Than Expected 6.2.22 Locking Protocol Problem Caused Bugchecks 6.2.23 Deleting and Then Creating a Logical Area and Accessing the Schema Caused a Page Checksum Bugcheck 6.2.24 Rdb/VMS Behavior Had Changed so That Buffers Were Emptied on Rollback 6.2.25 Lock-Related Looping Problem 6.2.26 Problem with SPAM Thresholds in a Recover Operation 6.2.27 Query Returned Records in Wrong Order with the SQL ORDER BY <column-name> DESCENDING or the RDO SORTED BY DESCEND 6.2.28 The Predicate CONTAIN Uppercased the Second Byte of Some Two-Octet Characters Incorrectly 6.2.29 Negate Operator Incorrectly Propagated the NULL Bit While Processing a Record Stream 6.2.30 An UPDATE Operation Stored Incorrect Results 6.2.31 An UPDATE Operation Caused a Bugcheck 6.2.32 Query Using Descending Indexes Returned Incorrect Results 6.2.33 Query with SQL LIKE Returned Incorrect Results 6.2.34 Query with Compressed Indexes Returned Incorrect Results 6.2.35 Query Returned Incorrect Results 6.2.36 Poor Performance Was Observed with Queries Using Dynamic OR Optimization Within the Leaf Retrieval 6.2.37 SPAM Pages Were Not Updated Correctly 6.2.38 Global Section Was Corrupted When a User Had Multiple Attaches 6.2.39 Under Certain Circumstances a Committed Update Was Not Completely Written to the .AIJ File 6.3 IMPORT/EXPORT Problems Fixed in the Mandatory Update for Version 4.0 6.3.1 Importing a Database with Tables Containing Lists (Segmented Strings) Failed 6.4 SQL Problems Fixed in the Mandatory Update for V4.0 6.4.1 SQL$STARTUP.COM Startup File Contained an Error in the SQL/Services Startup Logical Name 6.4.2 Opening a Cursor That Was Already Opened Caused the Cursor to Lose Its State 6.4.3 Executing the ROLLBACK Statement with OPEN LIST Cursors Left List Cursors in an Unusable State 6.4.4 Executing the COMMIT Statement with OPEN LIST Cursors Did Not Commit the Newly Created Lists 6.4.5 The OPEN Statement of an INSERT TABLE CURSOR Did Not Properly Return Error Status 6.4.6 Records Included from the Data Dictionary in the C Preprocessor Did Not Null Terminate Character Strings 6.4.7 Triggers Created with Long Source Text Strings Were Improperly Displayed 6.4.8 Triggers Created from Programs Had Their Source Text Truncated by a Word 6.5 SQL/Services Problems Fixed in the Mandatory Update for V4.0 6.5.1 Reinstalling SQL/Services APIs After Installation of Mandatory Update Kit for Rdb/VMS Version 4.0 6.5.2 SQL/Services Sample Application ULTRIX API Compiled with a Syntax Error 6.5.3 SQL/Services MS-DOS IVP Failed with a -2003 and 9 Error Status Codes, Indicating That Numbers Were Not Being AllW 6.5.4 SQL/Services Length Packet Split Problem 6.5.5 SQL/Services ULTRIX API Was Not Freeing Network Connections 6.5.6 SQL/Services Communication Server Did Not Report Error Status 6.5.7 SQL/Services Shutdown Procedure Hung, Causing the Subsequent Startup Procedure Not to Work 6.5.8 SQL/Services Startup File Changes 6.5.9 SQL/Services Macintosh API Code Fixes 6.5.9.1 SQL/Services SQLSRV$Volume Installation Volume Could Not Be Accessed on the Macintosh 6.5.9.2 PATHWORKS DECtask Tool Name Changed 6.5.9.3 SQL/Services Macintosh API Fix for Macintoshes Based on the Motorola 68000 Chip 6.6 RDO, Callable RDO, RDBPRE, and RDML Problems Fixed in the Mandatory Update for V4.0 6.6.1 RDBPRE Generated Incorrect Code for Request Handles 6.6.2 A CDD/Plus Informational Message Caused RDML to Abort Compilation 6.6.3 An RDML-E-READ_ONLY Error Was Returned When Attempting to Update COMPUTED BY Fields 6.6.4 Problem with Callable RDO and Varying String Descriptors 6.7 RMU Problems Fixed in the Mandatory Update for V4.0 6.7.1 RMU/VERIFY Returned Spurious Errors Involving Fragmented Records 6.7.2 RMU/CONVERT Failed with a Default Collating Sequence Defined 6.7.3 The /INTERVAL Qualifier of the RMU/BACKUP/AFTER_JOURNAL Command Miscalculated a Specified Interval Value 6.7.4 Problem with RMU/SHOW USERS and RMU/SHOW SYSTEM Commands and VMS WORLD Privileges 6.7.5 RMU/REPAIR Command Caused Database Corruption-Problem I 6.7.6 RMU/REPAIR Command Caused Database Corruption-Problem II 6.7.7 RMU/DUMP and RMU/CLOSE Commands Required VMS SYSPRV Privilege 7 Known Problems, Restrictions, and Other Notes for the Mandatory Update for Rdb/VMS V4.0 7.1 General Problems, Restrictions, and Notes 7.1.1 VMS Lock Remastering Changed in VMS V5.4 7.2 Problems, Restrictions, and Notes for All Interfaces 7.2.1 Using Quoted Threshold Values for Binary Data Types for Partitioning Data or Indexes Results in Data or Index Cor 7.2.2 Problem with SQL LIKE and RDO MATCHING Clauses 7.2.3 RDB$REMOTE Account Has SYSTEM as Owner 7.2.4 An Arithmetic Exception Results When Joining Integer Columns 7.2.5 Collating Sequences That Use Two-to-Two Character Mapping Can Bugcheck 7.2.6 Query with Keys Scans the Index Instead of Using Direct Tree Lookup 7.2.7 Synchronization Problem for an Empty Sorted Index 7.2.8 Rdb/VMS Does Not Accept the Database File Specification in a Logical Name 7.2.9 Query Optimizer Does Not Choose Index-Only Retrieval When the Dbkey Is Selected 7.2.10 Rdb/VMS Hangs on a SELECT Statement When a Column Data Type Is Changed from INTEGER to CHARACTER to DATE 7.2.11 Rdb/VMS Monitor Fails When the Last User Finishes on a Particular Database 7.2.12 Multisegmented Index Is Not Selected When a Not-Equal Predicate Is Specified 7.2.13 Triggers That Affect Subject Table Rows Can Cause Loops or Inconsistent Results 7.2.14 Singleton Subselect Statement Returns Incorrect Results 7.2.15 Query with a FOR Loop with a MODIFY Statement Followed by a PRINT Statement Can Return Incorrect Results 7.2.16 Query with a Computed-By Field and OR Logic Returns Incorrect Results 7.2.17 Defining a View Causes a Bugcheck When a Sorted Index Was Previously Defined 7.2.18 Problem When Database Is Defined as Remote 7.2.19 An Incompatible Change for RDO Applications: New Update Rules Will Be Enforced by Default in V4.1 7.2.20 Relation Name Must Match Dictionary Record Name 7.2.21 NOWAIT Transactions Have Their Buffers Invalidated at COMMIT 7.3 SQL Problems, Restrictions, and Notes 7.3.1 SQL Deprecated Features and Incompatible Changes for VAX Rdb/VMS Version 4.1 7.3.2 SQL to Support Error Code Values in Rdb/VMS Version 4.1 7.3.3 Using the IGNORE CASE Option of the LIKE Clause Sometimes Results in a Query That Incorrectly Returns No Rows 7.3.4 An SQL SELECT Statement Results in an Invalid BLR Error 7.4 SQL/Services Problems, Restrictions, and Notes 7.4.1 SQL/Services VMS API Shipped with the Rdb/VMS Run-Time Kit 7.4.2 VMS API Installation Without Rdb/VMS 7.4.3 Trailing Characters on SQL/Services Sample Program Error Messages 7.5 RDO, RDBPRE, and RDML Problems, Restrictions, and Notes 7.5.1 RDO IMPORT Does Not Save All SQL Defined Attributes 7.5.2 RDO CONVERT on V3.0 Databases Causes Database Corruption When the Database Is Converted to V4.0 7.6 Rdb/VMS Management Utility (RMU) Problems, Restrictions, and Notes 7.6.1 Do Not Delete After-Image Journal (.AIJ) Backup Files If the AIJ Backup Fails or Is Terminated 7.6.2 Concealed Logicals Are Supported but No Longer Recommended for Use After V4.0 7.6.3 Warnings from an RMU/VERIFY Operation 7.6.4 RMU/VERIFY/INDEX or RMU/VERIFY/ALL Command Causes a Bugcheck If You Have Hashed Indexes Defined 7.7 Notes and Restrictions Related to CDD/Plus 7.7.1 Restrictions Lifted by CDD/Plus Version 4.3 7.8 DECtrace Problems, Restrictions, and Notes 7.8.1 Rdb/VMS Version Number Used for DECtrace Will Remain at V4.0 7.9 Rdb/VMS Documentation Errors and Omissions in V4.0 7.9.1 Buffer Management Changes for V4.0 7.9.2 Incorrect Reference in V4.0 VAX Rdb/VMS SQL Reference Manual , Chapter 3 7.9.3 Printing Error in V4.0 VAX Rdb/VMS SQL Reference Manual , Chapter 4 7.9.4 Documentation Error in V4.0 VAX Rdb/VMS SQL Reference Manual , Appendix D.4 7.9.5 SQL/Services Error Documentation 7.10 SQL/Services Troubleshooting Suggestions 7.10.1 Common SQL/Services Network Errors 7.10.2 Common SQL/Services Fatal Execution Server Errors 7.10.3 Common SQL/Services API Installation Failures 7.10.4 SQL/Services Compatibility Issues 7.10.4.1 SQL/Services V4.0 Server Uses Proxy-Like and Default Access to Authorize V3.0 or V3.1 Client Applications 7.10.4.2 SQL/Services V4.0 Server Error -2031 Returned to V3.1 Client APIs 7.10.4.3 Queue Manager Must Be Started for the SQL/Services IVP to Work 8 Optional ECO Patches for the Mandatory Update for VAX Rdb/VMS V4.0 8.1 Optional ECO Patches That Can Be Applied to the Mandatory Update for Rdb/VMS V4.0 8.1.1 RDMSHRP ECO 30: Poor OR Optimization Performance on Read/Write Transactions 8.1.2 RDMMON ECO 01: Rdb/VMS Monitor Fails When the Last User Finishes on a Particular Database 8.1.3 RDMSHRP ECO 31: Multisegmented Index Is Not Selected When a Not-Equal Predicate Is Specified 8.1.4 RDMSHRP ECO 32: Singleton Subselect Statement Returns Incorrect Results 8.1.5 RDMSHRP ECO 33: Query with a FOR Loop with a MODIFY Statement Followed by a PRINT Statement Can Return IncorrecR A Sample V3.1C Installation B Sample V4.0A Installation EXAMPLES 6-1 Cursor Losing Its State 6-2 Executing ROLLBACK with LIST CURSORS in a Host C Program 6-3 Executing ROLLBACK with LIST CURSORS in SQL Module Language 6-4 Executing COMMIT with OPEN LIST Cursors 6-5 OPEN Statement Not Returning Error Information 6-6 OPEN Statement Not Returning Error Information in SQL Module Language 6-7 Records from the Data Dictionary Not Terminated with the NULL Character 6-8 Triggers Properly Displayed 6-9 Trigger Text Truncated TABLES 1-1 Disk Space Requirements 1-2 Process Account Quotas for the Installing Account 1-3 Required Minimum System Parameter Values 5-1 Disk Space Requirements 5-2 Process Account Quotas for the Installing Account 5-3 Required Minimum System Parameter Values 7-1 SQL/Services Network Errors