Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Why does the database size increase after an upgrade?

 During an upgrade of ADSS Server the installation process ensures that the database structure is also upgraded to allow the latest version to run properly. This includes but is not limited to the creation of new tables, insertion of new records or updating of old records. The database size increase is actually negligible due to these structural changes, but the size of database transactional logs increases creating the main reason for the database growth.  The database transaction logs store full information on any insertion, deletion and updating operations on a table. 

 In particular the database transaction log size increases because of the re-calculation of the HMAC values when upgrading. ADSS Server uses Hash Message Authentication Codes (HMAC) for protecting the integrity of its database records. These HMAC values are calculated automatically by ADSS Server whenever a database record is written, and these values can later be verified either manually at the request of the ADSS operator or automatically by ADSS Server if configured. Each HMAC value acts like a fingerprint for the input data it is protecting. Therefore HMAC values depend on the database scheme (i.e. which table column values are included within the HMAC).

When upgrading from a previous ADSS Server release the HMAC values need to be recomputed for any database tables for which the database schema has been changed.  Depending upon the number of records in the database this may take some time. While updating HMACs, the DBMS transactional log may become very large because they store the information relating to the re-calculation of the HMACs.



Truncate the DBMS transactional log after an upgrade to reclaim space OR set your DBMS not to increase the transactional log above a limit. Consult the relevant database documentation on how to truncate transactional logs.
 
 

How to fix the error "Number of locks exceeds the lock table size" when upgrading ADSS Server using MySQL database?


When ADSS Server setup executes the upgrade scripts, it acquires lock on the database tables. If table sizes in the ADSS Server database are very large then MySQL database server may throw this error "Number of locks exceeds the lock table size".  This happens when the MySQL database server doesn’t have enough space to store all the table rows for which lock is acquired. Before ADSS Server upgrade, adjust innodb_buffer_pool_size accordingly and restart MySQL database server.  You may consult your DBA for further instructions.

How to fix the "InnoDB The Table is Full"?

The issue that InnoDB table is full may arise with MySQL database due to the small log file size of InnoDB due to which transactions are not being written to the log file. The resolution is as follows:

  1. In the my.cnf [Linux] or my.ini [Windows] configuration file of your MySQL Server, add/modify the following property right below the mysqld section in the configuration file:
    innodb_data_file_path=ibdata1:1G:autoextend
  2. Restart the MySQL Server for the changes to take effect.