MaxDB 7.8.02.41 released - what is new?

Hi all,

here is a list including most features and patches for our latest update of 7.8 (also part of SAP note 1364181).
For further details about the referred 'PTS' incidents you can access our 'Problem Tracking System'.

Thorsten

SP 2 Patch 41 (7.8.02.41) (January 05, 2015) (9 Features, 37 Patches)

Kernel

• Volume balancing now starts even when a new volume is added to a large number of existing volumes. Previously, this would not have changed the average filling threshold enough to trigger volume balancing (PTS 1242644).
  
• New column LOBCOLUMNCOUNT in system view FILES shows the number of defined LOB columns in the that file (PTS 1252717).
  
• The allowed maximum number of correlated columns in one SQL statement has been increased from 64 to 256 (PTS 1252781).
  
• Fix for database parameter value MaxServerTasks unwantedly increasing during param_checkall operation, if database parameter CheckDataParallelServerTasks> 0 (PTS 1252452).
  
• Fix to reduce probability of undetected deadlocks on database parameter settings involving a large MaxSQLLock value (MaxSQLLocks * RowLocksPerTransactionThreshold > 2147483647) (PTS 1252478)
  
• Fix for performance issue during insert transactions with LOB columns and database parameter EnableLobTransactionConsistency = YES (PTS 1242167).
  
• possible crashes fixed (crash at ALTER TABLE DROP FOREIGN KEY statement, PTS 1251839).
  
• Fix for error BD Buffer limit while using a hash join with extension records and missing SQL optimizer statistics (PTS 1252611).
  
• Possible kernel crash caused by killing the task starting the database analyzer is fixed (PTS 1252487).
  
• Microsoft Windows: Fix for failing backups (Access denied) when writing to a network share (UNC-path) caused by an invalid entry in the access control list of the backup file (PTS 1252703).
  
• Microsoft Windows: fix for database kernel service hanging in state starting, if started via Microsoft Windows Service Manager or Microsoft Cluster Manager (PTS 1252865).

  Interfaces 

• SQLDBC: fix for error -10811 due to numerical overflows on floating point values; to prevent this error, SQLDBC now truncates values with a negative exponent above 64 (PTS 1252847). Fix for possible error -109, LOB file dropped at INSERT statement with IGNORE DUPLICATES, if LOB content size was larger then value in database parameter CommandBufferSize (PTS 1252690).
  
• ODBC (Content Server): fixed crash in reconnect phase (PTS 1252258); fixed crash during startup (PTS 1252346).
  
• ODBC: the SQLExecute/SQLExecDirectcall now returns SQL_NO_DATA_FOUND on a non positional UPDATE or DELETE statement instead of returning SQL_SUCCESS_WITH_INFO and message cursor operation conflict (PTS 1253008).

  Tools 

• Database Analyzer: startup info message changes to add number of tables with packed unicode columns, removed detailed list of tables requiring an UPDATE STATISTICS run (PTS 1252398) and warning added if number of UKTs with user tasks exceeds value of database parameter MaxCPUs (PTS 1252572); new warning added if one of the TaskCluster* database parameters is user modified (PTS 1252663); removed warning messages for high average write times by correcting the thresholds in IOTHREAD_HIGH_READTIME and IOTHREAD_HIGH_WRITETIME (PTS 1252600).
  
• DBM Server: Handling of parameter changes improved - if a database parameter is usermodified (userdefined) a newly entered value that violates the parameter constraint implicitly drops the usermodified/userdefined flag;
  The table ACTIVECONFIGURATION now has a column that shows the database parameter modification by user;
  The database parameter ouput lines in file knlmsg have additional database parameter modification information: '(U)';
  A new DBM command param_resetusermod allows to remove the usermodified/userdefined flag for a single database parameter by resetting the value to its default and recalulating all database parameter dependencies (PTS 1252010).
  
• DBM Server: Fixed X server protocol file being flooded with repeated Cannot flush file error lines if the dbmsrv process crashes and writes a call stacktri into the dbmsrv_<host>.err file) (PTS 1223052).
  
• DBM Server: Fix for a hanging DBM server process waiting for setting a resource lock (PTS 1252224).
  
• DBMCLI: After DBM command recover_config as database system administrator, the wrong user is flagged as DBM operator, which may lead to failing commands like load_systab or db_restart (PTS 1252964) (note 2081702).
  
• DBMCLI: Fixed incomplete information for DBM command dban_state which could lead to missing status information for Database Analyzer in DBA Cockpit (transaction DBACOCKPIT)/Database Assistant (transaction DB50)/liveCache Assistant (transaction LC10) (PTS 1252379).
  
• Loader: bug fix for syntax error when calling the Loader using -n and the -U switch (PTS 1252854).