Wichtige Hinweise
Wir empfehlen, die folgenden Schritte von einem Datenbank-Administrator durchführen zu lassen!
Beachten Sie, dass direkte Änderungen am Datenbankinhalt, d.h. ohne den Einsatz von AE-Programmen, zu einer inkonsistenten Datenbank führen.
Führen Sie die Arbeitsschritte erst durch, wenn die Datenbank gesichert wurde.
Je nach Größe der Datenbank und Umfang des Upgrades kann dieser Vorgang entsprechend dauern. Eventuell müssen auch sehr große Datenmengen bewegt werden.
Sorgen Sie dafür, dass für das \AUTOMIC\DB-Verzeichnis entsprechend viel Plattenplatz frei ist und der LOG-Bereich der Datenbank diese Datenmengen aufnehmen kann.
Die Schemarechte, die der verwendete Datenbank-Benutzer benötigt, sollten nach dem Update wieder entfernt werden. Dadurch sind ungewollte Datenbankveränderungen vermeidbar.
Für Oracle empfiehlt Automic ausdrücklich, nur die Tablespaces UC_INDEX und UC_DATA zu verwenden, da Sie andernfalls alle SQL-Dateien während des Update-Prozesses manuell anpassen müssten.
DB2: After updating the AE database, check the size of the tablespaces and if required, run the following SQL statement:
alter tablespace <UC4 tablespace name> reduce max;
In order to start the utility AE DB Load, users of an ORACLE database require additional rights.
Notes for updating a DB2/ OS390 database from version 6.00A to 8.00A:If the table AH is stored in a 4K tablespace, it will be copied to a larger tablespace of 8K during the upgrade process. Automic recommends providing the corresponding memory before starting to update. No copying process takes place if this table is already available in a bigger tablespace. In this case, use the line "process_sql_file2 chngdb_ah.sql" instead of "process_sql_file2 copy_ah.sql" in the file "UC_UPD_FOR_DB2.OS390.txt".
By default, the table will be copied.
Excerpt from the file "UC_UPD_FOR_DB2.OS390.txt":
message -----------------------------------------------------------------
message Apply chngdb_ah.sql if Table AH is already in an 8K Tablespace!!!
message process_sql_file2 chngdb_ah.sql
message -----------------------------------------------------------------
message -----------------------------------------------------------------
message Remove copy_ah.sql if Table AH is already in an 8K Tablespace!!!!
process_sql_file2 copy_ah.sql
message -----------------------------------------------------------------
Important note for updating the AE database to version 8.00A
As part of the upgrading process to the new data model of version 8.00A, the table structures in the report area (RH and RT) are adjusted. This modification applies to all supported databases.
The available tablespace must be of at least the same size as the database (for example: database size 40 GB, required available space: 40 GB). The RedoLog area must also be dimensioned appropriately.
Note that the conversion process takes some time depending on the complexity of the data involved. The time required for updating the database can be reduced by reorganizing data (especially the reports) beforehand.
Automic recommends testing the conversion process of your production database in a test environment in order to obtain experience values for runtimes and the required space.
You have several options:
- Update the database without storing the reports. Data is deleted and no additional space is required.
- Convert the reports during the updating process.
Note that this process can take some time depending on the amount of data involved. You system is offline during this time.
- Convert the reports after the update installation - only possible for MS SQL Server and Oracle.