VERSION INFO -> RDB -> Rdb 7.0.6.2
[ Back ] [ Next ]

September, 2001 - Oracle releases Rdb version 7.0.6.2
     [Enhancements] [Bug Fixes]
    Updates to Rdb may be obtained directly from Oracle Support

 

Top New Features and Technical Changes (Rdb V7.0.6.2)
5.2.1	RMU /REPAIR /INITIALIZE ONLY_LAREA_TYPE Keyword
5.2.2	New /TRANSACTION_TYPE Qualifier for RMU /Unload
5.2.3	New /TRANSACTION_TYPE Qualifier for RMU/Extract
5.2.4	Installing Oracle Rdb Images as Resident on OpenVMS Alpha
5.2.5	New DUMP Output Format for LogMiner
5.2.6	Data and Spam Prefetch Screens Added to RMU/SHOW Statistics

Top Problems Corrected (Rdb V7.0.6.2)
2.1.1	Query with UNION Subselect Returns Wrong Results
2.1.2	Excessive Pages Discarded when Using COMMIT TO JOURNAL OPTIMIZATION
2.1.3	Bugchecks at PIOGB$FETCH_FROM_GB + 488
2.1.4	Query with CONCATENATE in BETWEEN Clause Returns Wrong Results
2.1.5	ORDER BY Query With GROUP BY on Two Joined Derived Tables Returns Wrong Results
2.1.6	Left Outer Join Query With CONCATENATE Returns Wrong Results
2.1.7	Query With UNION in German Collating Sequence Returns Wrong Results
2.1.8	Query With OR Predicate on Aggregate Column Returns Wrong Results
2.1.9	Query With Equality Predicate Included in IN Clause Returns Wrong Results
2.1.10	Duplicate Node Algorithm Improved
2.1.11	Bugchecks at DIOCCHDBR$UNLATCH_GRCL With Exception of COSI-F-NONEXPR
2.1.12	Match Strategy on Columns of Different Size, Using Collating Sequence, Returns Wrong Results
2.1.13	Network Link Failure Does Not Allow DISCONNECT to Clean Up Transactions
2.1.14	Failure to Extend a Storage Area May Leave the LEOF of the .RDA File Pointing Beyond the PEOF
2.1.15	Left Outer Join Query With CAST Function on USING Column Bugchecks
2.1.16	Query Using Constant Values in OR Predicates Returns Wrong Results
2.1.17	Manual Open Causes Utility Access State to Persist Until Close
2.1.18	LogMiner Compresses Pre-Delete Record Content
2.1.19	Excessive Disk I/O for DROP TABLE and TRUNCATE TABLE
2.1.20	Query Joining Derived Tables of Union Legs With Empty Tables Returns Wrong Results
2.1.21	Left Outer Join Query With OR Predicate Returns Wrong Results
2.1.22	Query Using Match Strategy With DISTINCT Function Returns Wrong Results
2.1.23	GROUP BY Query With SUM Aggregate Returns Wrong Results
2.1.24	ARBs Exhausted
2.1.25	CLEAN BUFFER COUNT Parameter Not Obeyed
2.1.26	DETECTED ASYNC PREFETCH THRESHOLD Not Obeyed
2.1.27	Page Locks Not Demoted at End of Transaction When FAST COMMIT Enabled
2.1.28	Incorrect Record Written to AIJ for Ranked Indexes
2.1.29	ROLLBACK Hangs Under DECdtm When Called From an ACMS CANCEL Procedure
2.2	SQL Errors Fixed
2.1	Supplied CHR Function Returns Incorrect Value
2.2	IMPORT DATABASE Did Not Substitute New Collating Sequence
2.3	ALTER TABLE Support Extended for Temporary Tables
2.4	ATOMIC Block Not Rolling Back Changes on Error
2.5	GROUP BY Queries Fail With INVALID_BLR Error
2.6	Using Null Indicators With Dynamic SQL and Compound Statements Yields Incorrect Results
2.7	Using the CALL Statement in Dynamic SQL Results in Input Parameters Not Being Written to SQLDA
2.8	New Minimum Value for the INTERVAL Leading Precision
2.9	Command Line Recall Expanded to 255 Lines
2.10	Incorrect Processing of CASE Expression
2.11	%RDB-E-NO_DIST_BATCH_U Error When Executing SET TRANSACTION
2.3	Oracle RMU Errors Fixed
2.3.1	RMU/Extract Fails to Extract IMPORT Script from Multischema Database
2.3.2	RMU/Extract May Abort with ACCVIO and Bugcheck
2.3.3	RMU/Extract /ITEM=WORKLOAD Generates Incomplete Output
2.3.4	RMU Commands May Leave Zero Length Log File
2.3.5	%RDB-E-INVALID_BLR When Group By Count(*)
2.3.6	Full Logical Area Name Displayed in Zoom Screen
2.3.7	RMU /UNLOAD Specifying Both /VIRTUAL and /RECORD_DEFINITION
2.3.8	RMU /SET AFTER_JOURNAL /SWITCH and Automatic Backup Server Does Not Backup All Journals
2.3.9	RMU /VERIFY Constraint Reports Erroneous Error
2.3.10	RMU/DUMP/AFTER /START and /END Qualifiers are Difficult to Use
2.3.11	RMU/LOAD FILACCERR Exception While Reading Input File
2.3.12	RMU/LOAD Access Violation When Table constraints Were Defined
2.3.13	RMU/UNLOAD/AFTER_JOURNAL CPU Loop With Large Fragmented Record
2.3.14	RMU/VERIFY/INDEX/TRANS=READ_ONLY Did Not Detect BADIDXREL
2.3.15	RMU /UNLOAD Closes .RRD File Earlier
2.3.16	RMU /UNLOAD /AFTER_JOURNAL Requires Accurate AIP Logical Area Information
2.3.17	Asterisks Displayed for STID on >99 Attaches in RMU/SHOW STATISTICS
2.3.18	RMU/SHOW STATISTICS Displays Physical Area Name for Page Lock
2.3.19	RMU/SHOW STATISTICS Incorrect AIJ CurrEOF Value
2.3.20	RMU /UNLOAD /AFTER_JOURNAL Excessive Work File I/O
2.3.21	RMU/Extract Not Formatting View Column Expressions Correctly
2.3.22	Recovery Journals With Only Rollback Records Not Handled Correctly
2.3.23	RMU/UNLOAD/AFTER_JOURNAL Fragmented Records Clarification

Top