Feature list for liveCache/MaxDB 7.7
[feature] [feature tool] [liveCache] [maxdb] [upgrade]
Related:
- MaxDB release for virtual systemsSymptom You want to use MaxDB/liveCache in virtual systems (VMware,...
- MaxDB / liveCache Performance on HP-UXSymptom - You want to optimize performance of your MaxDB...
- Parameter check for liveCache/MaxDB instancesSymptom You want to use an automatic check to check...
- Additional information about MaxDB version upgrade to 7.8Symptom This note provides supplementary information about the version upgrade...
- Parameter recommendations for OneDB systemsSymptom This note provides recommendations regarding configuration parameter settings for...
Symptom
This note provides an overview of the most important changes (features) for Release 7.7.
Contents:
1. Preface
2. Major Features 7.7 (sorted in accordance with note changes)
3. Features and Patches 7.7 for each release
———————————————————————–
1. Preface
The PTS numbers specified below refer to the internal “Problem Tracking System” of the database development and represent a selection only. You can use PTS to create complete ‘Change Lists’ (http://maxdb.sap.com/webpts).The date in parentheses for ‘Features and Patches for each Release’ refers to the completion of a status in an SAP development location, but not to the general availability. You can view and download the available status from the SAP Software Distribution Center. Furthermore, newer versions are provided at short notice according to customer requests (by SAP message) using a Web Link, provided there is a release in the SAP environment.The latest versions of the tools Database Manager and SQL Studio as well as the “Eclipse”-based successor database studio (Administration & SQL) are available on SAP Service Marketplace.Since all of the tools are downward compatible, you should set the current level together with the database in each case.’Database Studio’ is compatible with all MaxDB/liveCache versions as of 7.5 and higher.Database Manager and SQL Studio have been released up to and including MaxDB 7.7.Up to and including Release 7.7, the feature lists are created in German and then translated. In cases of doubt, the German original is the correct version. For all feature list notes as of 7.8, the master language is English, so that in cases of discrepancies, the content of the English version is correct.
———————————————————————–
Other terms
MaxDB, liveCache, upgrade, feature, 7.7
Solution
2. Major Features 7.7 (sorted in accordance with note changes)
New FEB/09/2009: Prefetching
parallel ‘read ahead’ import of data pages from the hard disk to the data cache.
(see Note 1255050)(7.7.07.04, downport to 7.6.06.02)
JAN/12/2009: Parameter limit increased in SQL statements
Up to 10,000 input parameters (previously: 2000) are supported in SQL statements.
(see Note 655018)(7.7.05.03, 7.7.06.08, 7.7.07.04, Downport to 7.6.06.02)
JAN/12/2009: Volume balancing after ‘add_volume’
automatic equal distribution of data across all volumes. Controllable using parameter EnableDataVolumeBalancing.
(see Note 1173395)(7.7.06.08, 7.7.07.05)
Jan/12/2009: ‘Star Join’ optimization
BW systems: Performance gain for certain SQL joins (if the optimizer displays at least one dimension table before the first fact table in ‘Explain’.
(see Note 1040431 – ‘BW Feature Pack’)(7.7.04.32, 7.7.06.08, 7.7.07.05, feature from 7.6.01.07)
APR/28/2008: Renaming all parameters
all database parameters were adjusted to new naming conventions.
The change list is available at:
http://maxdb.sap.com/doc/7_7/44/bd1ec6a5d51388e10000000a155369/frameset.htm
(7.7.03. 00)
Nov/24/2007: Online snapshots
Creating and deleting snapshots during operation.
(7.7.04. 06)
APR/23/2007: Compressed Tables
Unicode compression of table columns to UTF8 (using ALTER TABLE … PACKED UNICODE).
(7.7.07. 01)
BW systems: Compressed storage of numerical fields (affectd dimension tables) (using ALTER TABLE … PACKED).
(7.7.01. 23, 7.7.02.11, 7.7.03.17)
JUL/27/2006: Clustering
Currently used only in BW systems: Consecutive data pages are transferred together and sorted into 64 K blocks (= ‘Cluster’) to the I/O system.
(-> see Note 1264776 – “Cluster table attribute” and Note 1040431 – “BW Feature Pack”) (7.7.04, feature from 7.6.05.08)
JAN/1/2006: New message file format
The old ‘plain text’ file format for ‘knldiag’, ‘knldiag.err’ and other database logfiles is no longer supported. The new files ‘KnlMsg’ or ‘KnlMsgArchive’ are written in ‘Pseudo XML’. To read those files, they must first be converted using ‘protconv’ (automatic process in Database Studio, DBMGUI or DB50/LC10).
For additional information, see SDN:
‘HowTo – New knldiag Message File Format in MaxDB 7.7′ (https://wiki.sdn.sap.com/wiki/x/PwErAg)
(7.7.00. 00)
———————————————————————–
3. Features and Patches 7.7 for each release
7.7.08.00 split from 7.7.07.06 on April 29, 2009
- – - – - – - – - – - – - – - – - – - – - – - – - – - – - – - -
Support Package 7 patch 05 (7.7.07. 05)(April 08, 2009)(28 features, 139 patches)DBAnalyzer: Several new features, including a warning when an obsolete configuration file is used for the automatic parameter check and a workload caused by DBAnalyzer (PTS1160860, PTS1173692).Kernel: Default value for parameter UseLobClustering is now “Yes” (PTS1157371).Kernel: Equal distribution of the data on the volumes after “add_data” (PTS1159841).Optimizer: “Star-Join” reactivated (PTS1160467).Optimizer: Fix for “key strategy although index strategy is more selective” (PTS1161354).Optimizer: Corrections for “aggregation over join result” in conjunction with certain functions (PTS1173657).DBMServer: Various corrections, including for “Administration not possible after software upgrade” (PTS1173193, PTS1159649, PTS1162291, PTS1160477, PTS1162574, PTS1172479, PTS1172547).Kernel: Stability improved (PTS1159138, PTS1161112, PTS1161139, PTS1161139, PTS1162688, PTS1172516, PTS1173093, PTS1160251, PTS1160556, PTS1160744, PTS1161121, PTS1161856, PTS1170773, PTS1171823, PTS1173144, PTS1155811, PTS1156755, PTS1160219, PTS1173569).
Support Package 7 patch 04 (7.7.07. 04)(6 features, 41 patches)Kernel: Prefetching support activate (Note 1255050)(PTS1159939, PTS1158825).Kernel: Parameter limit increased to 10000 in SQL statementst (PTS1156037).Kernel: Improved stability (PTS1159205, PTS1159187, PTS1159376, PTS1159461, PTS1159613, PTS1159971, PTS1160119, PTS1160131, PTS1159185, PTS1159829).Optimizer: Correction for ‘join select with group by clause’ (PTS1159713) and ‘outer join select’ (PTS1159604).
Support Package 7 patch 03 (7.7.07. 03)(NOV/24/2008)(3 features, 16 patches)Correction for sporadically high CPU consumption by DBMServer (PTS1158879, PTS1158935).Optimizer: Correction for ‘join select with correlated subquery’ (PTS1158271):Windows Vista: Connection problem with client installation to database server solved (’Could not create comm. shared memory, rc = 5′)(PTS1158770).
Support Package 7 patch 02 (7.7.07. 02)(OCT/28/2008)(7 features, 43 patches)DBMServer: the option ‘clearuserdefined’ deletes the ‘user-defined’ flag for parameter values so that the parameter is calculated automatically using ‘cserv.pcf’ (PTS1158240).
Support Package 7 patch 01 (7.7.07. 01)(SEP/04/2008)(14 features, 24 patches)Improved deadlock analysis: With the new parameter DeadlockDumpFilename, a binary dump of the lock list is generated if a deadlock occurs (PTS1156335).The new parameter IOWorkerStackSize determines the stack size of the I/O worker threads; 256 KB is intended as the default value (PTS1157126).
Support Package 7 patch 00 (7.7.07. 00)(AUG/12/2008)(22 features, 97 patches)Kernel: The stability has been improved (PTS1155934, PTS1156500).Problem when reading LOB data types solved (PTS1158315).Data may be lost in the long fields if the data cache is very small (PTS1156642).7.7.07.00 split from 7.7.06.03 on July 11, 2008
- – - – - – - – - – - – - – - – - – - – - – - – - – - – - – - -
Support Package 6 patch 15 (7.7.06. 15)(May 25, 2009)(1 feature, 10 patches)Check Data: Enhanced to include a check of the file directory structure (PTS1177380).Kernel: Stability improved during index scan (PTS1175403) and during statistics update (PTS1177232).”Fixed columns” type columns may be handled incorrectly (PTS1177319).
Support Package 6 patch 14 (7.7.06. 14)(May 04, 2009)(0 features, 7 patches)DBAnalyzer: New features have been added, including a workload caused by DBAnalyzer and information about “clustered I/O” and “free clusters” (PTS1175348).Correction for “incorrect file directory counters for indexes” (PTS1175065).
Support Package 6 patch 12 (7.7.06. 12)(April 23, 2009)(1 feature, 7 patches)Optimizer: Crashes during “QueryRewrite” (PTS1174567) and when accessing the Catalog Cache (PTS1174473) have been solved.
Support Package 6 patch 11 (7.7.06. 11)(April 15, 2009)(4 features, 54 patches)liveCache: “Pinning of liveCache content” using the parameter ‘EnableLivecachePinAreaUsage’ (PTS1172362).DBMServer: Various corrections, including for “Administration not possible after software upgrade” (PTS1173192, PTS1172557, PTS1173940, PTS1174065, PTS1174204).JDBC: Incorrect “Autocommit” mode after reconnect (PTS1172974).Optimizer: Correction for error -602 during “select <aggregation with distinct column>” (PTS1171922).Optimizer: Corrections for “aggregation over join result” in conjunction with certain functions (PTS1173656).Kernel: Stability improved (PTS1172284, PTS1173092, PTS1174116, PTS1173568, PTS1172201)
Support Package 6 patch 10 (7.7.06. 10)(FEB/23/2009)(0 features, 16 patches)Kernel: Correction for ‘add_volume crashes in admin mode’ (PTS1162687).QueryRewrite: Correction for ‘Incorrect push down predicates in case of outer joins’ (PTS1170895).SQLDBC: Correction for ‘Wrong (doubled) output when reading DATE columns)(PTS1171874).
Support Package 6 patch 09 (7.7.06. 09)(FEB/05/2009)(1 feature, 19 patches)Kernel: Stability has been improved (PTS1159213, PTS1161111, PTS1161138, PTS1160752, PTS1161829).
Support Package 6 patch 08 (7.7.06. 08)(JAN/12/2009)(7 features, 46 patches)Optimizer: Performance improvement in Business Warehouse by ‘Star Join’ feature (PTS1160584).Kernel: Parameter limit increased to 10000 in SQL statementst (PTS1159014).Windows Vista: Connection problem with client installation to database server solved (’Could not create comm. shared memory, rc = 5′)(PTS1158769).Kernel: automatic distribution of data to all volumes using parameter EnableDataVolumeBalancingKernel: Improved stability PTS1157851, PTS1159375, PTS1159469, PTS1159612, PTS1159970, PTS1160118, PTS1160132, PTS1160218, PTS1159828, PTS1160521).Optimizer: various corrections (PTS1159137, PTS1159721, PTS1159802, PTS1160104, PTS1160250, PTS1159603).
Support Package 6 patch 07 (7.7.06. 07)(NOV/06/2008)(3 features, 10 patches)improved external backup support using “db_execute save data quick to ‘<dummy tapename>’ external [medianame '<external identifier string>']” (PTS1158073).
Support Package 6 patch 06 (7.7.06. 06)(OCT/20/2009)(2 features, 35 patches)Optimizer: Correction for ‘join select with correlated subquery’ (PTS1158279):Optimizer: Improved performance for ‘inner join select’ (PTS1154919) and other problems solved (PTS1158298, PTS1158346).Improved stability (PTS1157212, PTS1158345)
Support Package 6 patch 05 (7.7.06. 05)(SEP/23/2008)(0 features, 1 patch)Problem during treatment of BLOB data solved (length -1 instead of correct value)(PTS1155527).
Support Package 6 patch 04 (7.7.06. 04)(SEP/12/2009)(6 features, 19 patches)The new parameter IOWorkerStackSize determines the stack size of the I/O worker threads; 256 KB is intended as the default value (PTS1157127).Changes were made in the area ‘cluster compression’ (PTS1156865, PTS1157099, PTS1157145).
Support Package 6 patch 03 (7.7.06. 03)(AUG/06/2008)(8 features, 64 patches)DBAnalyzer enhanced: New file DBAN_USER_TASK_ACT_DETAIL.csv in expert analysis and further improvements (PTS1155818).Potential memory leak in DBAnalyzer corrected (PTS1156628).Data may be lost in the long fields if the data cache is very small (PTS1156643).
Support Package 6 patch 02 (7.7.06. 02)(JUL/07/2008)(4 features, 22 patches)’diag_pack’ is used to translate the MaxDB log files from “pseudo XML” into a readable text file and to pack it into an archive (PTS1155614).Two new table attributes have been introduced:
CACHE: table should be kept in data cache
NOCACHE: table pages will leave data cache earlyA potential performance problem that occurs during the statistics update without “sampling” is corrected (serialization for large tables)(PTS1155550).
Support Package 6 patch 01 (7.7.06. 01)(JUN/16/2009)(6 features, 29 patches)New directory ‘oap_logs’ in the run directory of the database. You can now query with OAPLOGS using the DBMServer (PTS1154908).Defined setting of the environment when the user is changed (previously: automatic inheritance of environment variables); as before, you must add “dbm_configset Set_Variable_X <varname> <value>” to the database-kernel-specific environment (PTS1155041).
Support Package 6 patch 00 (7.7.06. 00)(MAY/28/2008)(41 features, 80 patches)MaxDB JDBC driver supports JDBC 4.0 (PTS1153373).The ‘x_cons’ application PID is no longer ‘0′ for Java connections, but is now the PID of the Java VM (PTS1153981).Two new ‘x_cons’ commands ‘SHOW DESCRIPTOR’ (lists all open descriptors (for example, network connections) managed by pollsets) and ‘CLOSEDESC <ID>’ (closing a descriptor with given ID (for example, when the connection hangs for a long time)) were introduced (PTS1154568).7.7.06.00 split from 7.7.04.17 on April 04, 2008
- – - – - – - – - – - – - – - – - – - – - – - – - – - – - – - -7.7.05.07 continued as 7.8.00.00 on April 15, 2008
- – - – - – - – - – - – - – - – - – - – - – - – - – - – - – - -
Support Package 5 patch 07 (7.7.05. 07)(APR/15/2008)(13 features, 23 patches)New database parameter UseExtendTimeMeasurement introduced (in the same way as TIME_MEASUREMENT in Release 7.6)(PTS1153399).
Support Package 5 patch 06 (7.7.05. 06)(MAR/31/2008)(8 features, 16 patches)Corrections in the Optimizer (PTS1139734, PTS1146587, PTS1152901, PTS1153841, PTS1147805, PTS1153777).
Support Package 5 patch 05 (7.7.05. 05)(MAR/19/2008)(13 features, 24 patches)DBMServer command ‘inst_reg’ enhanced with [SYSTEM|NOSYSTEM] [ISOLATED|NOISOLATED] (PTS1153598).Automatic configuration of the parameter CacheMemorySize to 25% (liveCache) or 50% (OLTP) of the main memory (PTS1153692).Features ‘coroutines’ and ‘load-balancing’ available for all instance types (PTS1147311).
Support Package 5 patch 04 (7.7.05. 04)(MAR/11/2008)(7 features, 19 patches)DBAnalyzer: Among other things, number of W3 warnings reduced (PTS1153484).Parameter USE_OPEN_DIRECT reintroduced for migrations and automatic parameter settings (PTS1153648).
Support Package 5 patch 03 (7.7.05. 03)(MAR/04/2008)(6 features, 23 patches)The limit for the ‘host variables’ in SQL statements was increased from 2000 to 10000 (PTS1148119).
Support Package 5 patch 02 (7.7.05. 02)(FEB/20/2008)(10 features, 19 patches)Improved savepoint synchronization (PTS1152937)The column SEPARATORCOUNT is added to the system table SYSINFO.TABLESTORAGEDETAILS (PTS1152860).New system table SYSINFO.PAGELOCKS (PTS1153101).Security fix (PTS1146882, PTS1153119).
Support Package 5 patch 01 (7.7.05. 01)(5 features, 12 patches)DBMServer: The patch for shared memory problem and security has been improved (PTS1146420, PTS1152818).
Support Package 5 patch 00 (7.7.05. 00)(JAN/09/2008)(12 features, 34 patches)New features in the Database Analyzer. For example, “CPU consumption” display and the new file DBAN_SV.csv in the expert analysis for “server task activities” (PTS1151155).7.7.05.00 split from 7.7.04.08 on December 12, 2007
- – - – - – - – - – - – - – - – - – - – - – - – - – - – - – - -
Support Package 4 patch 35 (7.7.04. 35)(May 18, 2009)(0 features, 3 patches)Kernel: Crash during “Index Read Scan” has been solved (PTS1175406).SQLDBC: The system may no longer be able to read the contents of “Fixed Columns” (PTS1177318).
Support Package 4 patch 34 (7.7.04. 34)(May 07, 2009)(0 features, 14 patches)Kernel: The database may crash if a “clustered index” from Release 7.6 is used with MaxDB 7.7 (PTS1159188).A performance problem may occur due to an incorrect file directory counter for indexes (PTS1175063).
Support Package 4 patch 33 (7.7.04. 33)(April 06, 2009)(0 features, 28 patches)High-Availability: A communication problem that occurs with the cluster software during the DBMServer command “exec_lcinit” has been solved (PTS1162292).DBMServer: After an upgrade to the database software, you cannot start any new DBMServer processes if required (PTS1173189).Optimizer: Correction for a problem during the hash join and join aggregation (PTS1171096, PTS1173653).SQLDBC: Error during treatment of DATE columns solved (PTS1171866, PTS1170660).
Support Package 4 patch 32 (7.7.04. 32)(JAN/29/2009)(1 feature, 18 patches)Optimizer: Performance improvement in Business Warehouse by ‘Star Join’ feature (PTS1160585).SQLDBC: Error (invalid length information) during treatment of ‘LOB’ values solved (PTS1162101).Kernel: Stability has been improved (PTS1159206, PTS1161110, PTS1161138, PTS1160749, PTS1159827).
Support Package 4 patch 31 (7.7.04. 31)(JAN/20/2009)(0 features, 1 patch)SQLDBC: Error during treatment of ‘LOB’ data solved (PTS1161826).
Support Package 4 patch 30 (7.7.04. 30)(DEC/09/2008)(0 features, 24 patches)100 % CPU consumption by DBMserver processes corrected (PTS1158875).JDBC: Improved performance (driver blocks in finalizer thread)(PTS1158389).Recovery: Problem for log recovery has been corrected (PTS1157849).Optimizer: ‘join select with group by clause but without set function and OR conditions on columns from different tables’ has been corrected (PTS1159718).
Support Package 4 patch 29 (7.7.04. 29)(OCT/31/2008)(1 feature, 17 patches)possible problems during migration/installation solved (PTS1157829, PTS1157840).Optimizer: Problem for ‘join select with correlated subquery’ solved (PTS1158272) and additional corrections (PTS1158733, 1159060).
Support Package 4 patch 28 (7.7.04. 28)(SEP/23/2008)(2 features, 10 patches)new parameter IOWorkerStackSize defines the stack size for I/O worker threads (PTS1157136).Improved stability (PTS1157209, PTS1157188).Problem when reading LOB values solved (PTS1151408).
Support Package 4 patch 27 (7.7.04. 27)(AUG/26/2008)(3 features, 20 patches)HP-IA64 platforms only: The compiler upgrade MaxDB kernel requires new OS patches (PTS1156368).The DBAnalyzer memory consumption has been reduced (PTS1156627).DBMServer error correction (PTS1156634, PTS1156653, PTS1156665, PTS1156722, PTS1156732, PTS1156775)IPC resources are automatically deleted after each restart so that starts cannot fail due to IPC resources that still exist (PTS1156489).
Support Package 4 patch 26 (7.7.04. 26)(AUG/22/2008)(0 features, 1 patch)Optimizer: Correction if a termination occurs for ‘Clustered I/O’ and join select (PTS1157054).
Support Package 4 patch 25 (7.7.04. 25)(AUG/08/2008)(0 features, 1 patch)Optimizer: Performance issue with ‘inner join’ solved (PTS1156841).
Support Package 4 patch 24 (7.7.04. 24)(AUG/04/2008)(2 features, 15 patches)DBAnalyzer enhanced: New file DBAN_USER_TASK_ACT_DETAIL.csv in expert analysis and further improvements (PTS1155819).Data may be lost in the long fields if the data cache is very small (PTS1156637).
Support Package 4 patch 23 (7.7.04. 23)(JUL/10/2008)(2 features, 27 patches)’diag_pack’ is used to translate the MaxDB log files from “pseudo XML” into a readable text file and to pack it into an archive (PTS1155615, PTS1155859).DBAnalyzer: Elimination of problem that occurs when you access DB instance 7.5 (PTS1156123).A potential performance problem that occurs during the statistics update without “sampling” is corrected (serialization for large tables)(PTS1155551).Optimizer: Fehler ‘-2000, row too long’ in the join in corrected (PTS1155789)
Support Package 4 patch 22 (7.7.04. 22)(JUN/24/2008)(0 features, 1 patch)liveCache: Dbmserver crash during lcinit is eliminated (PTS1155860).
Support Package 4 patch 21 (7.7.04. 21)(JUN/18/2008)(0 features, 1 patch)only two corrections (error ‘vak506 7′ in the LOB update/insert) and error ‘-1103′ during the select with about 1300 IN conditions)(PTS1155612, PTS1155623).
Support Package 4 patch 20 (7.7.04. 20)(JUN/03/2008)(0 features, 5 patches)LOB handling correction (upsert command; LOB length = -1)(PTS1155515, 1155400).liveCache: small corrections (PTS1155164, PTS1155077, PTS1154206).
Support Package 4 patch 19 (7.7.04. 19)(MAY/28/2008)(0 features, 10 patches)The problem with ‘Check Data with Update’ and ‘container free page chains’ was eliminated (PTS1155301).The error ‘-3987′ that occurred during the ‘LOB’ insert or update was eliminated (PTS1155173).Defined setting of the environment when the user is changed (previously: automatic inheritance of environment variables); as before, you must add “dbm_configset Set_Variable_X <varname> <value>” to the database-kernel-specific environment (PTS1155384, PTS1155042).
Support Package 4 patch 18 (7.7.04. 18)(MAY/23/2008)(5 features, 27 patches)Two new ‘x_cons’ commands ‘SHOW DESCRIPTOR’ (lists all open descriptors (for example, network connections) managed by pollsets) and ‘CLOSEDESC <ID>’ (closing a descriptor with given ID (for example, when the connection hangs for a long time)) were introduced (PTS1154567).Problems that occurred when handling ‘LOB’ were eliminated (PTS1154991, PTS1154829).
Support Package 4 patch 17 (7.7.04. 17)(APR/23/2008)(1 feature, 14 patches)Possible problems with ‘cluster compression’ and savepoints solved (PTS1154546).Data backup problem with ‘new mixed cluster mode’ corrected (PTS1154198).Approximate 60-second blockade by ‘x_cons’ commands corrected (PTS1154333).
Support Package 4 patch 16 (7.7.04. 16)(APR/15/2008)(0 features, 7 patches)Restart problem corrected (Could not read file directory page <xxx>)(PTS1153984).The database may retain the remote connection when the application crashes. This may lead to a delayed commit or rollback response and, therefore, to unwanted lock situations (PTS1154338).
Support Package 4 patch 15 (7.7.04. 15)(APR/09/2008)(2 features, 21 patches)Transactions can explicitly be assigned to a certain ‘Log Queue’ using the SQL statement ‘LIMIT TRANSACTION LOG’; this may be useful for transactions that cause a high logging volume (PTS1154293).LOB handling: improved insert/update performance and error correction (PTS1153881, PTS1153839); possible endless loop corrected (PTS1153778); problem with ‘row-wise binding of LOB values’ corrected (PTS1153821).
Support Package 4 patch 14 (7.7.04. 14)(MAR/26/2008)(3 features, 18 patches)Database analyzer: minor features/corrections (PTS1153482)Optimizer: Corrections for ‘outer join select, if functions are used on outer table columns’ (PTS1151624), join performance (PTS1153663), and ‘execution of right outer join’ (PTS1153688).Log backup fails if MAXCPU = 1 or if log queue = 1 under certain circumstances (PTS1153700).
Support Package 4 patch 12 (7.7.04. 12)(MAR/04/2008)(0 features, 2 patches)The stability has been improved (QueryRewrite)(PTS1153595)
Support Package 4 patch 11 (7.7.04. 11)(MAR/04/2008)(2 features, 21 patches)Optimizer: the join performance has been improved (PTS1153420)The error that occurred during the catalog migration has been corrected (’-915, no more memory’; ‘-100, missing views’)(PTS1153417, PTS1153465).
Support Package 4 patch 10 (7.7.04. 10)(FEB/11/2008)(4 features, 8 patches)New system view SYSINFO.PAGELOCKS is available (PTS1153102)Optimizer: Correction for “wrong strategy decision for outer join selects with more than two tables, if outer table not last one in from clause” (PTS1152862).Optimizer: Small corrections (PTS1153103, PTS1153034, PTS1153164).UNIX: Potential problem in the DB restart has been eliminated (PTS1152973).SQLDBC: Potential deadlock when selecting LOB values (PTS1153155).
Support Package 4 patch 09 (7.7.04. 09)(JAN/30/2008)(0 features, 11 patches)Security leak is removed (Note 1132010)(PTS1152820, PTS1152191)
Support Package 4 patch 08 (7.7.04. 08)(JAN/17/2008)(16 features, 43 patches)Optimizer (PTS1151949, PTS1152107, PTS1152165, PTS1152166Stability database kernel (PTS1152026, PTS1151928, PTS1151987, PTS1152319)JDBC: -109 Error during mass updates to LONG values corrected (PTS1152040).
Support Package 4 patch 07 (7.7.04. 07)(NOV/28/2008)(13 features, 28 patches)You can configure the Database Analyzer so that it automatically checks whether the database parameters are set as recommended in Note 1004886 (Note 1111426) (PTS1151591).
Support Package 4 patch 06 (7.7.04. 06)(NOV/24/2008)(21 features, 28 patches)’db_admin’, ‘db_online’, ‘db_restart’: You can use the new option ‘-x’ to load specific ‘kernel executables’ for diagnostic purposes (PTS1151438).You can create and delete several snapshots in online mode (PTS1123960).SharedSQL: The memory leak and the memory consumption have been corrected (PTS1150592, PTS1151677).Copying error during ‘SQL Insert into’ in ‘LOBs’ larger than 16200 KB (PTS1151537).SQLDBC: possible wrong result when reading numeric values with a SQL_NUMERIC structure (PTS1151568).
Support Package 4 patch 05 (7.7.04. 05)(NOV/21/2007)(11 features, 26 patches)JDBC: ‘blocking situations due to unnecessary synchronization removed’ (PTS1151222).
Support Package 4 patch 04 (7.7.04. 04)(OCT/08/2007)(5 features, 13 patches)The stability has been improved (PTS1150887, PTS1151019).
Support Package 4 patch 03 (7.7.04. 03)(OCT/24/2007)(19 features, 36 patches)Optimizer: Correction for ’select with correlated subqueries’ (PTS1150818); correction for ’select on clustered table with key strategy’ (PTS1150836).
Support Package 4 patch 02 (7.7.04. 02)(OCT/04/2007)(3 features, 20 patches)There is the new system view MEMORYALLOCATORDETAILS (PTS1150016).The memory leak in the DBMServer has been corrected (PTS1150630).SharedSQL: The stability has been improved (PTS1150368).
Support Package 4 patch 01 (7.7.04. 01)(SEP/17/2007)(10 features, 31 patches)SharedSQL: The stability has been improved (PTS1150230, PTS1150369).Memory leaks have been eliminated (PTS1150126, PTS1150200).
Support Package 4 patch 00 (7.7.04. 00)(SEP/03/2007)(13 features, 39 patches)DBAnalyzer: SystemPageCache and SystemHeap (allocation/deallocation) have been included in DBAN_SYALLOCATION (PTS1150031).Optimizer: Corrections have been provided for ‘inserts with long columns in autocommit mode’ (PTS1146197); the performance has been improved for views (PTS1148950); corrections have been provided for joins with ‘join transition via clustered key’ (PTS1149905).SharedSQL & QueryRewrite stability: (PTS1150136, PTS1150225, PTS1150280).7.7.04.00 split from 7.7.03.18 on August 08, 2007
- – - – - – - – - – - – - – - – - – - – - – - – - – - – - – - -
Support Package 3 patch 27 (7.7.03. 27)(NOV/14/2008)(0 features, 19 patches)JDBC: Improved performance (driver blocks in finalizer thread)(PTS1158387).Optimizer: Correction for ‘join select with correlated subquery’ (PTS1158275).Problem when reading LOB data types solved (PTS1151407).
Support Package 3 patch 26 (7.7.03. 26)(NOV/04/2008)(0 features, 2 patches)100 % CPU consumption by DBMserver processes corrected (PTS1158873, PTS1158909).
Support Package 3 patch 25 (7.7.03. 25)(JUL/04/2008)(0 features, 28 patches)Optimizer: Error ‘-2000, row too long’ in the join is corrected (PTS1155795). Correction for ‘hash join using ‘OR’-strategy (PTS1155115).Correction ‘Select count (*)’ Filedirectory Counter (PTS1155647).Stability has been improved (PTS1155936, PTS1155426, PTS1154106, PTS1154185, PTS1155340, PTS1155936).Defined setting of the environment when the user is changed (previously: automatic inheritance of environment variables); as before, you must add “dbm_configset Set_Variable_X <varname> <value>” to the database-kernel-specific environment (PTS1155043).
Support Package 3 patch 24 (7.7.03. 24)(MAR/28/2008)(5 features, 55 patches)’SDBUPD -show_instancedata [<db name>]‘ shows pending upgrades which may prevent new upgrades. ‘SDBUPD -reset_instancedata <db name>’ removes them (PTS1152446).Security patch (PTS1152290, PTS1153121)Optimizer: Corrections for ‘outer join select including functions on outer table columns’ (PTS1151628), ’select on clustered table with key strategy’ (PRS1152146), ‘wrong strategy decision for outer join selects including more than two tables’ (PTS1152863), join performance (PTS1153421), ‘join with local IN/SUBQ strategy as join transition’ (PTS1153165), ‘execution of right outer join’ (PTS1153689)Optimizer: Query rewrite problem for ‘Rule_OptimizeSubqueries’ solved (PTS1152762).LOB handling: improved insert/update performance and error handling (PTS1153882, PTS1153834), wait situation during backup end corrected (PTS1152309), endless loop during LOB read corrected (PTS1153779), deadlock corrected (PTS1153156)Log backup fails if MAXCPU = 1 or if log queue = 1 under certain circumstances (PTS1153701).
Support Package 3 patch 23 (7.7.03. 23)(FEB/07/2008)(0 features, 5 patches)Security leak is removed (Note 1132010)(PTS1152826, PTS1152188)
Support Package 3 patch 22 (7.7.03. 22)(JAN/01/2007)(1 features, 27 patches)Optimizer: Corrections for “Outer Join select, if functions are used on outer table columns in the join predicates where clause” (PTS1151628).Optimizer: ‘Fetch last with rowno’ corrected (PTS1150291).
Support Package 3 patch 21 (7.7.03. 21)(NOV/12/2007)(2 features, 5 patches)Copying error during ‘SQL Insert into’ in LOBs larger than 16200 KB (PTS1151539)SQLDBC: possible wrong result when reading numeric values with a SQL_NUMERIC structure (PTS1151569).
Support Package 3 patch 20 (7.7.03. 20)(NOV/08/2007)(1 feature, 8 patches)only minor corrections (crash when restarting log) (PTS1151421).
Support Package 3 patch 19 (7.7.03. 19)(OCT/24/2008)(4 features, 24 patches)The memory leak in the SharedSQL has been corrected (PTS1150614).
Support Package 3 patch 18 (7.7.03. 18)(OCT/02/2007)(9 features, 60 patches)You can switch on the DBM server trace at any time with ‘dbm_trace’ (PTS1149300).A new core parameter ‘UseUnicodeColumnCompression’ has been added; when you choose ‘Yes’, the system uses UTF8 for Unicode, except for key columns (PTS1147551).
Support Package 3 patch 17 (7.7.03. 17)(JUL/25/2007)(14 features, 41 patches)liveCache: “CreateVersion”, “OpenVersion”, “CloseVersion”, “DropVersion”, “StoreInVersion” and “DeleteInVersion” were added to the view SYSDBA.MONITOR_OMS (PTS1149344).Corrections have been added for the DBMServer (PTS1149316, PTS1149348, PTS1149546, PTS1149550, PTS1149589, PTS1149667, PTS1149712).Table compression ‘CREATE TABLE …PACKED’ also supported in SQL mode ’sapr3/Oracle’ (PTS1149397).
Support Package 3 patch 16 (7.7.03. 16)(13 features, 22 patches)The new DBMServer command ‘instance_create’ is available and is used later to set up “multi db instances” (PTS1149234).Corrections have been provided for the DBMServer and event handling (PTS1149096, PTS1149112, PTS1149558).
Support Package 3 patch 15 (7.7.03. 15)(JUL/06/2007)(11 features, 20 patches)New DBMServer command ‘dbm_stop’: This commands stops DBM server processes that are related to the same database (PTS1140910).The progress of ‘Check Database’ and ‘Check Table’ is logged in the kernel log file ‘KnlMsg’ and an event ‘CheckTableProgressEvent’ is triggered for each percentage (PTS1148419).On 64-bit systems, you can use the parameter XP_DATA_CACHE_RGNS to set the number of data cache regions. However, you should generally use the default value here (PTS1149035).New UKT states ‘Dispatching’, ‘Context Switching’, and ‘Terminated’ added for the console (PTS1148787).
Support Package 3 patch 14 (7.7.03. 14)(JUN/23/2007)(21 features, 32 patches)New column CURRENTSCHEMANAME in SYSINFO.SESSIONS (PTS1148257).Name change: System tables ‘READERWRITER…’ to ‘SHARELOCK…’ (PTS1146035).
Support Package 3 patch 12 (7.7.03. 12)(MAY/30/2007)(6 features, 13 patches)Value “WITHOUT DOUBLE QUOTES” added to ‘NetWorker’ parameter NSR_AVOIDVSSBUG (PTS1148311).
Support Package 3 patch 11 (7.7.03. 11)(MAY/15/2007)(13 features, 24 patches)vtrace ’stop on error’ automatically performs a ‘flush’ (PTS1148220).Windows: New ‘xserver’ options ‘-b’ and ‘-B’ for ‘portable root environments’ (PTS1148002).SQLDBC: SQL Support for ‘? IS NULL’ Statements (PTS1148250).Optimizer: Correction for join aggregation (PTS1148164).
Support Package 3 patch 10 (7.7.03. 10)(MAY/03/2007)(6 features, 30 patches)Optimizer: Correction for ‘fetch last with rowno’ statement and error ‘-7015′ for the update with ‘join-subselect’ (PTS1147934, PTS1147976).Kernel: Stability has improved (PTS1147646, PTS1147850, PTS1147800, PTS1147952, PTS1148189, PTS1147927).
Support Package 3 patch 09 (7.7.03. 09)(APR/28/2007)(8 features, 15 patches)’db_full’ handling during restart has been improved (PTS1147739).The DBMServer supports compressed data transfer to the DBM client, for example, for large log files (PTS1147754).Performance for access to DOMAIN. views has been improved (PTS1147498).Due to an improved data cache allocation, the database takes less time to start in large systems (more than 200GB) (PTS1147689).Optimizer: The problems with join handling are corrected (PTS1147750, PTS1147608).
Support Package 3 patch 08 (7.7.03. 08)(APR/17/2007)(15 features, 31 patches)Database analyzer: New features, for example, new columns in DBAN_CPU_UTILIZATION (PTS1147474).New Dbmserver command ‘instances_enum’ for usage on ‘Multi Database Instances’ (PTS1147385).Optimizer: ‘Duplicate Key’ error with hash join has been corrected (PTS1147338).Parameter _MBLOCK_STACK_SIZE can no longer be set higher than 262136 (PTS1147437).
Support Package 3 patch 07 (7.7.03. 07)(MAR/21/2007)(10 features, 22 patches)The problem with Autorecover using ADSM or TSM has been corrected (PTS1146960).JDBC: ‘Connection listeners’ was not correctly removed (PTS1147042).JDBC: The memory leak has been removed (PTS1147080).Optimizer: correction for ‘outer join with local predicates within or terms’ (PTS1146865).Optimizer: Problem during update of ‘Lobs’ and activated variable input feature has been solved (PTS1147099).
Support Package 3 patch 06 (7.7.03. 06)(MAR/06/2007)(10 features, 21 patches)You can now change parameter DeadlockDetectionLevel online (PTS1146884).New system view LOGPARTITIONSTATISTICS (PTS1146683).Backup templates with more than 64 characters are now allowed (PTS1146719).
Support Package 3 patch 05 (7.7.03. 05)(4 features, 23 patches)Cryptography support with complete or incremental backup (PTS1143932).The possible restart problem when reducing MAXUSERTASKS has been solved (PTS1146566).
Support Package 3 patch 04 (7.7.03. 04)(FEB/08/2007)(11 features, 16 patches)There is the new option “-keep” for the Database Analyzer. You can now enter the maximum number of days for which you want to store Analyzer log files.There are the new options ALL, SYSTEM, ID for the DBMServer command inst_enum. With these options you can display the system installations which are usually hidden (PTS1146064).With the new program DBMDROP you can delete a local database without authentication (PTS1146210).You can set a number of days for the CHECK_AVAILABILITY “Backint for MaxDB” option. For performance reasons, this reduces the quantity of backups for which an “inquire” was set to Backint (PTS1140814).The DBM user can no longer be deleted using a “drop user” (PTS1146143).During the upgrade, the system checks the database for inconsistencies, and records possible errors in the upgrade log file (PTS1146091).The SQL performance is improved with IN and BETWEEN, which were executed for the same column (PTS1146049).Two SQLDBC errors have been corrected: “-10908″ that occurs during the fetch of LONG values, and “-9409″ that occurs when you insert or select LONGs (PTS1146322, PTS1146351, PTS1146264).
Support Package 3 patch 03 (7.7.03. 03)(JAN/23/2007)(10 features, 19 patches)There is the new system view IOJOBS (PTS1145856).The stability was improved (PTS1145690, PTS1145918, PTS1145927, PTS1145775, PTS1145951, PTS1145992).
Support Package 3 patch 02 (7.7.03. 02)(JAN/10/2007)(5 features, 16 patches)SDBINST/SDBUPD/SDBSETUP terminates with error message ‘InstallRegistry: not enough space…’ when there is 2 TB of free space in the file system (PTS1145695).
Support Package 3 patch 01 (7.7.03. 01)(DEC/28/2006)(11 features, 22 patches)The new kernel parameter USERDEFINED was introduced, which indicates whether a parameter value was set automatically or due to a user action (PTS1145462).Starting the database may fail with a ‘bad log volume’ after ‘add log volume’ (PTS1145498).
Support Package 3 patch 00 (7.7.03. 00)(9 features, 24 patches)DBAnalyzer: The support for Java applications was improved (PTS1145362).You do no longer have to stop other databases (higher than 7.6.00.30) during the installation process (PTS1144993).The database catalog is migrated automatically if your start release is 7.4.03 or higher (PTS1145161, PTS1145162).The columns KEYSIZE, KEYPREFIXSIZE and KEYFILECOUNT were added to the system view CLASSCONTAINERS (PTS1145102).’Deadlock’ problems are corrected in the DBM server (PTS1145329).The possible memory leak for the ‘SELECT …OR…’ was removed (PTS1144592).The optimizer was improved (correction for SELECT with at least two subqueries; termination for activated command or resource monitor; ORDERED hint does not always work) (PTS1145443, PTS1145083, PTS1145246).Problems that occur when you update statistics on a shared table in a ‘multidb’ instance were corrected (PTS1145320).7.7.03.00 split from 7.7.02.07 on April 28, 2008
- – - – - – - – - – - – - – - – - – - – - – - – - – - – - – - -
Support Package 2 patch 23 (7.7.02. 23)(NOV/11/2008)(0 features, 25 patches)DBMServer crash due to ‘invalid packages’ (PTS1155133).Problem (NoConverterEntry) during restart corrected (PTS1153986).Recovery: Problem (move error) for log recovery corrected (PTS1155343).Optimizer: ‘join select with group by clause but without set function and OR conditions on columns from different tables’ has been corrected (PTS1159716).Problem during ’select count(*) solved ‘ (PTS1154329).
Support Package 2 patch 22 (7.7.02. 22)(NOV/12/2008)(0 features, 2 patches)high CPU consumption by DBMserver processes corrected (PTS1158872, PTS1159096).
Support Package 2 patch 21 (7.7.02. 21)(MAR/28/2008)(0 features, 20 patches)Optimizer: Corrections for ‘outer join with local predicates within or terms’ (PTS1146868), ‘join select columns with different length joined via hash join’ (PTS1148293), and ‘wrong strategy decision for outer join selects including more than two tables’ (PTS1152854).Optimizer: Corrections for ‘result set with unequal join’ (PTS1153497) and ‘join with local IN/SUBQ strategy as join transition’ (PTS1153166).Optimizer: Query rewrite problem for ‘Rule_OptimizeSubqueries’ solved (PTS1152763).Log backup fails if MAXCPU = 1 or if log queue = 1 under certain circumstances (PTS1153702).LOB handling: Deadlock corrected (PTS1153157), improved insert/update performance (PTS1153917), and endless loop during LOB read corrected (PTS1153761).
Support Package 2 patch 20 (7.7.02. 20)(JAN/30/2008)(1 feature, 9 patches)Security leak is removed (Note 1132010)(PTS1152827, PTS1152551)
Support Package 2 patch 19 (7.7.02. 19)(DEC/21/2007)(3 features, 23 patches)JDBC: -109 Error during mass updates to LONG values corrected (PTS1152042).Optimizer: Fix for ’select on clustered table if a key strategy is used’ (PTS1152147).
Support Package 2 patch 18 (7.7.02. 18)(NOV/14/2007)(1 feature, 16 patches)W64/AMD64: DBM server crash during backup using NetWorker or the command ‘archive_stage’ (PTS1150783).SQL “insert into” may incompletely copy LOB data larger than 16200 KB (PTS1151538).Kernel: Correcting incorrect data page handling by the garbage collector (PTS1151029).SQLDBC: Correction for “reading numeric values with an SQL_NUMERIC structure” (PTS1151570).
Support Package 2 patch 17 (7.7.02. 17)(OCT/01/2007)(2 features, 5 patches)Log recovery was not performed completely (PTS1150730).
Support Package 2 patch 16 (7.7.02. 16)(SEP/14/2007)(1 feature, 11 patches)The possible endless loop during CHECK CATALOG has been eliminated (PTS1149966).SharedSQL: The stability has been improved (PTS1150281, PTS1150227, PTS1150370, PTS1149954).Optimizer: Correction for QueryRewrite (PTS1150271).
Support Package 2 patch 15 (7.7.02. 15)(AUG/24/2007)(0 features, 1 patch)The stability has been improved (liveCache)(PTS1150054)
Support Package 2 patch 14 (7.7.02. 14)(AUG/13/2007)(1 feature, 4 patches)liveCache: A deadlock can occur when you restart (PTS1149867).The memory leak has been corrected (PTS1149951)
Support Package 2 patch 12 (7.7.02. 12)(AUG/07/2007)(0 features, 7 patches)Error ‘-9405′ during the QueryRewrite has been corrected (PTS1148759).
Support Package 2 patch 11 (7.7.02. 11)(JUl/30/2007)(11 features, 33 patches)New UKT states (visible using ’show task’, for example) “Dispatching”, “Context Switching” and “Terminated” have been introduced (PTS1148788).The stability was improved (PTS1149028, PTS1149071, PTS1149102, PTS1149576, PTS1149356).Table compression ‘CREATE TABLE …PACKED’ also supported in SQL mode ’sapr3/Oracle’ (PTS1149398).
Support Package 2 patch 10 (7.7.02. 10)(JUN/29/2007)(3 features, 19 patches)Optimizer: A correction for ‘bad performance on join select using index join strategy on a descending index’ (PTS1148971).
Support Package 2 patch 09 (7.7.02. 09)(JUN/04/2007)(14 features, 46 patches)New column DBPROCID in DOMAIN.DBPROCEDURES, new column FUNCTIONID in DOMAIN:FUNCTIONS, and new column CURRENTSCHEMANAME in SYSINFO.SESSION (PTS1147848, PTS1148420).vtrace ’stop on error’ automatically performs a ‘flush’ (PTS1148223).New page allocator shortens database start time (PTS1147690).Windows: New ‘xserver’ options ‘-b’ and ‘-B’ for ‘portable root environments’ (PTS1148003).
Support Package 2 patch 08 (7.7.02. 08)(APR/04/2007)(4 Features, 15 patches)JDBC: ‘Connection listeners’ was not correctly removed (PTS1147043).Optimizer: Hash joins and outer joins have been improved (PTS1147274, PTS1147339).
Support Package 2 patch 07 (7.7.02. 07)(MAR/20/2007)(34 features, 94 patches)New dbmserver options [(ALL|SYSTEM)[ID]] with command ‘inst_enum’ (PTS1146065).New dbmserver command ‘dbmdrop’ to delete local databases without authentication (PTS1146211).During the upgrade, the system automatically checks the database catalog for inconsistencies (PTS1146096, PTS1145739).An error (endless loop) in dbmrfc and problems in dbmserver have been corrected (PTS1146445, PTS1144715, PTS1144727, PTS1145283, PTS1145626, PTS1146362).Installation in file systems with more than 2 TB is now possible (PTS1145698).JDBC: The memory leak has been corrected (PTS1147070).Optimizer: Correction for ‘Index Only’ strategy (PTS1144725).Optimizer: ‘Autocommit insert’ of ‘Long’ columns has been improved (PTS1146198).Optimizer: Problem during update of ‘Lobs’ and activated variable input feature has been solved (PTS1147098).
Support Package 2 patch 06 (7.7.02. 06)(NOV/11/2006)(4 Features, 23 patches)Migration from a database with _UNICODE = NO are not possible and are terminated by the DBMServer (PTS1144630).’Clear Log’ formats the log area and recreates missing log volumes (PTS1143441).The column LOBSIZE from the system table FILES now always contains the numeric value 0 instead of ‘Nil’. This simplifies the totals formation (PTS1144502).The parameter USE_DIRECT_IO now refers to the backup devices and to formatting volumes (PTS1142978).Due to an error, pages of type ‘Data’ were not checked during ‘Recover_check’ (PTS1144572).
Support Package 2 patch 05 (7.7.02. 05)(NOV/09/2006)(4 features, 27 patches)Description for the new ‘Event dispatcher’ (PTS1143938).During the strategy search (DIFFERENT STRATEGIES FOR OR TERM), the system now considers (independently from the available memory) more than 128 strategies from the optimizer (PTS1143961).You can use parameter USE_BACKUP_SECURITY_DESCRIPTOR to deactivate the Windows security check, for example, so that you can carry out a backup to an ‘SMB share’ (PTS1143917).
Support Package 2 patch 04 (7.7.02. 04)(NOV/11/2006)(11 features, 22 patches)A ‘db_start’ (always executes an implicit ‘db_offline’) only starts the database if the database is in the ‘db_offline’ status, in order to prevent MaxDB from being stopped by accident (PTS1143632).’Deadlock’ problems are corrected in the DBM server (PTS1143582).
Support Package 2 patch 03 (7.7.02. 03)(8 features, 15 patches)The DBMServer commands FILE_GETFIRST and FILE_GETNEXT are accelerated by up to 20% (PTS1142457).The new DBMServer command AUTO_LOAD_SYSTAB enables you to automatically load the system tables if the kernel version is higher than the version specified in the system tables (PTS1143442).The DBMServer is now able to execute ‘auto_extend’ and ‘auto_update_statistics’ in ‘db_offline’ or ‘db_admin’ (PTS1143557).
Support Package 2 patch level 02 (7.7.02. 02)(6 features, 26 patches)The additional parameter INTERVAL <seconds> has been introduced for the automatic log backup. This parameter starts the automatic log backup if it has not been started by reaching the log segment size (PTS1142622).The new DBMServer command AUTO_DBANALYZER enables the automatic start of the Database Analyzer when you start the database instance (PTS1143265).The parameter ALLOW_TIMING_STATISTIC was renamed COLLECT_IO_TIMES (measures I/O time) and is activated by default (PTS1143214).
Support Package 2 patch level 01 (7.7.02. 01)(5 features, 27 patches)The implicit type conversion CHAR / NUMBER is now possible in all SLQ modes (PTS1142871).The ‘db_addvolume’ now has the optional parameter ‘<partition>’, which enables a volume partition on several disks (PTS1141602).
Support Package 2 patch 00 (7.7.02. 00)(12 features, 21 patches)New features were added to the Database Analyzer (PTS1142720).You can now assign the optional parameter TIMEOUT to the DBMServer function DMB_EXECUTE after the command is canceled (PTS1141950).The columns CHANGE in the TPARAMSGET system table allows the values NO, YES and, as of now, OLN. These values indicate whether a parameter can be changed or whether it can be activated online (PTS1142846).7.7.02.00 split from 7.7.01 on August 09, 2006
- – - – - – - – - – - – - – - – - – - – - – - – - – - – - – - -
Support Package 1 patch 23 (7.7.01. 23)(JUL/20/2007)(2 features, 9 patches)Optimizer: The performance when using a Select with 50 ‘OR terms’ has been improved (PTS1148654).Occasionally, the contents of the ‘Knlmsg’ log file were written to another open file (PTS1149199).Table compression ‘CREATE TABLE …PACKED’ also supported in SQL mode ’sapr3/Oracle’ (PTS1149399).
Support Package 1 patch 22 (7.7.01. 22)(JUN/14/2007)(0 features, 4 patches)’variable input’ error has been corrected (PTS1148759).
Support Package 1 patch 21 (7.7.01. 21)(JUN/05/2007)(0 features, 3 patches)I/O error ‘filesystem full’ has been corrected (PTS1148643).
Support Package 1 patch 20 (7.7.01. 20)(MAY/31/2007)(0 features, 5 patches)Optimizer: Correction for join aggregation (PTS1148168).
Support Package 1 patch 19 (7.7.01. 19)(MAY/11/2007)(0 features, 8 patches)The problem with ‘correlated subqueries and rowno predicate’ has been corrected (PTS1147402, PTS1148135).The problem with the delete statement that is qualified using an index has been corrected (PTS1147992).liveCache: The ’shared catalog cache’ grows too much (PTS1148059).The ‘Lock Escalation’ has been improved (PTS1148087).Optimizer: Correction for ‘fetch last with rowno’ (PTS1147939).
Support Package 1 patch 18 (7.7.01. 18)(APR/27/2007)(1 feature, 3 patches)Due to an improved data cache allocation, the database takes less time to start in large systems (more than 200GB) (PTS1147691).Optimizer: The stability with hash joins has been improved (PTS1147769, PTS1147771).
Support Package 1 patch 17 (7.7.01. 17)(APR/13/2007)(0 features, 3 patches)JDBC: ‘Connection listeners’ was not correctly removed (PTS1147044).Optimizer: A problem during update of ‘Lobs’ and activated variable input feature has been solved (PTS1147100).
Support Package 1 patch 16 (7.7.01. 16)(MAR/16/2007)(0 features, 8 patches)JDBC: The memory leak has been corrected (PTS1147078)The stability has been improved (PTS1146977, PTS1147033).
Support Package 1 patch 15 (7.7.01. 15)(MAR/02/2007)(4 features, 6 patches)The lock behavior on ‘lobs’ was improved and this may improve the overall performance (PTS1146560).Line locks are counted in relation to the transaction (and no longer related to a table). There are escalations if a transaction has 50% of the existing locks (PTS1146713).The installation problem on Windows Itanium was corrected (PTS1146580).The problems that occur during restart or during the log recovery were corrected (PTS1146499, PTS1146501).A new volume of the type ‘raw’ could not be added under AIX (PTS1146645).
Support Package 1 patch 14 (7.7.01. 14)(FEB/12/2007)(0 features, 6 patches)SQLDBC: The errors -10908 and -9409 that occurred when you were dealing with LONGs were corrected (PTS1146321, PTS1146352).liveCache: Some minor errors for the “-8″ problem were corrected (PTS1146410).’Check Catalog With Update’ now also repairs database catalog inconsistencies of the type NEWLONGVARCOLNO and NEWLONGVARCOLNO (PTS1146138).
Support Package 1 patch 12 (7.7.01. 12)(FEB/07/2007)(2 features, 14 patches)If there are inconsistencies in the database catalog, these are logged in the upgrade log file (PTS1146098, PTS1145748).The Redo error that occurred during the alter table and during the log recovery using DBMGUI was corrected (PTS1145575, PTS1145970).
Support Package 1 patch 11 (7.7.01. 11)(JAN/10/2007)(0 features, 5 patches)SDBINST/SDBUPD/SDBSETUP terminates with error message ‘InstallRegistry: not enough space…’ when there is 2 TB of free space in the file system (PTS1145699).Under certain circumstances, it was not possible to create new DMServer session for the database (PTS1145812).
Support Package 1 patch 10 (7.7.01. 10)(DEC/27/2007)(3 features, 32 patches)There may be a performance problems for the ‘Select count(*)’ because the new file directory counters were not used (PTS1145613).A data backup ‘Recover_Check’ did not check dataN pages, which is incorrect (PTS1144575).Error the database catalog (’Longvarcolcount’ problem) solved – contact SAP Support if a ‘Check Catalog’ executed by the SYSDBA user returns an error (PTS1144863, PTS1144954).The problem in the timer thread was corrected (the timer task can no longer be accessed, savepoints are no longer possible) (PTS1143945).
Support Package 1 patch 09 (7.7.01. 09)(NOV/10/2006)(0 features, 2 patches)Two errors related to a potential crash and an incorrect ‘history not found’ in the liveCache were corrected (PTS1144520, PTS1144618).
Support Package 1 patch 08 (7.7.01. 08)(NOV/02/2007)(0 features, 20 patches)The performance for commit/rollback was improved (PTS1143436).There was a correction in the optimizer (PTS1143530).The problem that occurred with separators for records larger than 8KB was corrected (PTS1143457).
Support Package 1 patch 07 (7.7.01. 07)(23 features, 59 patches)Tables with rows longer than 8KB are supported (PTS1141749).JDBC supports the special isolation level 50 and 60 (consistent read – related to statement and transaction) (PTS1142604).Hash join algorithm is now possible for index accesses (PTS1142131).The additional parameter INTERVAL <seconds> has been introduced for the automatic log backup. This parameter starts the automatic log backup if it has not been started by reaching the log segment size (PTS1139929).The minimum for _PACKET_SIZE was increased from 32KB to 48KB (PTS1142510).
Support Package 1 patch 06 (7.7.01. 06)(10 features, 21 patches)There is the new return code -4001 for ‘wrong user/password-combination in ADMIN-mode’ instead of ‘-4008, unknown user/password combination’ (PTS1142171).The columns USEDPERMANENTCONVERTERSIZE, USEDTEMPORARYCONVERTERSIZE, USEDSNAPSHOTSIZE and USEDSHADOWSIZE were added to the internal system table SYSINFO.DATASTATISTICS and the new columns MAXNEEDEDSIZE and USEDSIZE were added to SYSINFO.SNAPSHOT (PTS1141010).The UNUSED value from the system table SERVERDBSTATISTICS now also contains the pages from the “shadow memory” which are released only for the next savepoint (PTS1142122).
Support Package 1 patch 05 (7.7.01. 05)(13 features, 27 patches)Asynchronous execution of DBMServer commands (PTS1141321).You can execute an “old user <usr> add/drop password <pwd>” even if the user is ‘connected’ (PTS1137819).It is possible to install Windows (on portable media, for example) without registry entry using the environment variable SDB_PORTABLE_ROOT (PTS1141224).
Support Package 1 patch 04 (7.7.01. 04)(9 features, 18 patches)The normal CHECK DATA now always contains the parameter ‘extended’, which was optional up to now. Therefore, the separator sequence is now always checked, and the addition ‘extended’ is obsolete (PTS1141379).New features were added to the Database Analyzer (PTS1141689).
Support Package 1 patch 03 (7.7.01. 03)(12 features, 21 patches)Support for networker parameter NSR_AVOIDSSBUG (PTS1141569).
Support Package 1 patch 02 (7.7.01. 02)(11 features, 30 patches)You can now run SUBTIME at midnight (SUBTIME (x,y), where y > x )(PTS1141488).The ’statistics counters’ in the file directory are updated automatically in the background from table SYSUPDATECOUNTERWANTED (PTS1136827).
Support Package 1 patch 01 (7.7.01. 01)(16 features, 40 patches)The following changes were made to the diagnosis files: The new file KnlMsg (pseudo xml) contains the former ‘knldiag’ and in the KnlMsgArchive the ‘knldiagerr’ and ‘dbm.utl’ are collected; ‘KnlMsg’ and ‘KnlmsgArchive’ can now only be read with the tool ‘protconv’ (PTS1136144).The two new system views EADERWRITERLOCKINFORMATION and READERWRITERLOKKWAITINGTASKS were added (PTS1134581).There are three new system views REGIONINFORMATION, REGIONSTATISTICS and REGIONSTATISTICSRESET (PTS1136376).7.7.01.00 split from 7.7.00 on May 02, 2006
- – - – - – - – - – - – - – - – - – - – - – - – - – - – - – - -
Support Package 0 patch 21 (7.7.00. 21)(6 features, 17 patches)There are the new system tables SYSINFO.TABLESIZE, SYSINFO.INDEXSIZE and SYSINFO.SCHEMASIZE (PTS1140928).A log backup may fail after ‘Point-in-Time’ recovery (PTS1141061).
Support Package 0 patch 20 (7.7.00. 20)(14 features, 22 patches)The ‘db_addvolume’ now has the optional parameter ‘<partition>’, which enables a volume partition on several disks (PTS1139017).Using the DBMServer command ‘file_getlist’, you can convert the new log files KNLMSG and KNLMSGARCHIVE into readable formats, or convert them into old file formats, such as ‘knldiag’, which, as of 7.7, are no longer available in the standard system (PTS1137704).
Support Package 0 patch 19 (7.7.00. 19)(11 features, 18 patches)The new Backint parameter CHECK_AVAILABILITY enables you to deactivate the availability check to accelerate the display of the backup history (PTS1132559).The new column KERNELPROCESSID was added to the system view INSTANCE (PTS1140569).
Support Package 0 patch 18 (7.7.00. 18)(10 features, 16 patches)There is a trace option for the DBMServer. A trace file is written if the executable ‘dbmsrv_diag’ is used instead of the DBMServer.
Support Package 0 patch 17 (7.7.00. 17)(10 features, 25 patches)The new function INTTORAW(<integer>) converts an integer into a CHAR (8) BYTE value (PTS1135489).Preparations for the BW feature pack (PTS1138413, PTS1140021, PTS1140022).
Support Package 0 patch 16 (7.7.00. 16)(6 features, 19 patches)The parameter UPDATESTAT_SAMPLE_ALGO enables new sample algorithms for the statistics update (PTS1139497).TOTALCLUSTERAREASIZE, RESERVEDCLUSTERAREASIZE and USEDCLUSTERAREASIZE were added to the system view DATAVOLUMES (PTS1139724).
Support Package 0 patch 15 (7.7.00. 15)(5 features, 18 patches)Improvements for the SharedSQL (PTS1138528).
Support Package 0 patch 14 (7.7.00. 14)(7 features, 18 patches)There are the new programs dbmreg and dbmunreg. They work in the same way as the dbmcli command db_reg/db_unreg, but for which you do not need an authorization (PTS1139560).You can now explicitly exclude tables from the ‘Update Statistics *’, by setting the sample size to 0 (= ‘Alter Table <tablename> Sample 0 Rows’) (PTS1137889).
Support Package 0 patch 12 (7.7.00. 12)(10 features, 24 patches)There are the following new system views: SYSINFO.OMSVERSIONS, SYSINFO.OMSPROCEDURESTATISTICS, SYSINFO.TABLESIZEDETAILS (PTS1135457).MinRuntime and MaxRuntime were added to the system view MONITOR_OMS.
Support Package 0 patch 11 (7.7.00. 11)(13 features, 21 patches)In the JDBC driver, various errors were corrected and various features were adjusted (PTS1135283, PTS1135865, PTS1139071, PTS1139014, PTS1139095, PTS1139097, PTS1139099, PTS1139103, PTS1139185, PTS1139187, PTS1139189).
Support Package 0 patch 10 (7.7.00. 10)(15 features, 19 patches)The performance for creating the index was improved (PTS1138618).The access to the LOB file directory was improved (PTS1138618).
Support Package 0 patch 9 (7.7.00. 09)(9 features, 22 patches)There is the new optional parameter DB for the DBMServer command ‘db_reg’ and the new DMBServer command ‘db_unreg’ (PTS1137099).
Support Package 0 patch 8 (7.7.00. 08)(6 features, 13 patches)The new parameter PREALLOCATE_IOWORKER was added (PTS1138362).
Support Package 0 patch 7 (7.7.00. 07)(10 features, 24 patches)With the new Windows program ’sdbconfig’ you can change the registry entries for ‘IndepData’ and ‘IndepPrograms’ (PTS1138308).The new columns INDEXUSEDRESETDATE and INDEXUSEDRESETTIME were added to the system view DOMAIN.INDEXES (PTS1138257).
Support Package 0 patch 6 (7.7.00. 06)(11 features, 20 patches)The loader was corrected and improved (PTS1135502, PTS1135773, PTS1136416, PTS1137970, PTS1137898)
Support Package 0 patch 5 (7.7.00. 05)(10 features, 21 patches)The precompiler support was set, MaxDB 7.7 now uses the new interface SQLDBC (PTS1137775).
Support Package 0 patch 4 (7.7.00. 04)(13 features, 22 patches)There are new or changed file keys for the DBMServer command ‘file_getfirst’ to convert the new database log files from PseudoXML to plain text (these keys are as follows: KNLDIAG, KNLMSG, KNLMSGX, KNLDIAGERR, KNLARC, KNLARCX, KNLDIAGOLD, KNLMSGOLD, KNLMSGOLDX)(PTS1136153).
Support Package 0 patch 3 (7.7.00. 03)(7 features, 37 patches)Index statistics are now determined using a counter in the file directory. This counter indicates, for example, how often an index was used (PTS1136378, PTS1136566).
Support Package 0 patch 2 (7.7.00. 02)(7 features, 29 patches)There is the new system view DOMAIN.CONSTRAINTCOLUMNS (PTS1137112).SQL-’like’ now accepts parameter lengths of up to 8.000 (4.000 for Unicode) (PTS1137203).
Support Package 0 patch 1 (7.7.00. 01)(10 features, 11 patches)’Update Statistics’ or ‘Update Statistics Column’ now can process large tables in parallel (PTS1135215).
Support Package 0 patch 0 (7.7.00. 00)(103 features, 227 patches)dbmgetf now supports the option ‘-U’ for XUser access (PTS1134712).You can set the DBMServer parameters DBM_KTO_SUCCESS and DBM_KTO_FAILURE to override the standard kernel timeout, which is the time that the DBMServer can wait for the database kernel to reply to see whether a recovery/backup was successful or aborted (PTS1134497).When the parameter is changed, you can now add a comment (PTS1133875). A new DBMServer command ‘db_deletevolume’ allows deleting volumes (PTS1134489).There is the new system view DOMAINCONSTRAINTCOLUMNS (PTS1136331).liveCache: The new diagnosis commands DIAGNOSE CHECK INDEX FOR CONTAINER <i> and DIAGNOSE REPLACE INDEX FOR CONTAINER <i> check or create indexes for OmsKeydObjects (PTS1134858).With the new parameter OPTIMIZE_FIRST_ROWS you can accelerate statements with ‘rowno_predicate’ (PTS1136000).liveCache: The Garbage Collector no longer prevents a savepoint if you delete large tables or indexes (PTS1134155).The cost calculation for the operator join can be parameterized using OPTIMIZE_OPERATOR_JOIN_COSTFUNC=YES/NO (PTS1134356).liveCache: There are the new system tables CONSISTENTVIEWS and CONSISTENTVIEWOPENTRANSACTIONS (PTS1134576).There is the new system table DATASTATISTICSRESET (PTS1135941).You can use the new parameter SHOW_MAX_KB_STACK_USE to determine the latest stack requirements (only use this parameter for the analysis and do not use it permanently, since it has a negative effect on the performance) (PTS1136090).There are the new system tables HISTORYCLEANUPSTATISTICS and HISTORYCLEANUPSTATISTICSRESET (PTS1136442).There is the new system table IOBUFFERCACHES (PTS1134608).