When deleting data from the audit trail, it may be backed up in a second audit trail DB, the backup audit trail DB.
To delete or archive the audit trail or parts of it you can use
the Sysconsole command archive. The execution of this tool is
responsible for maintaining the closure of the backed-up objects, e.g.
backing up the corresponding models, model elements and grants. The
backup audit trail may be cumulatively populated.
The Sysconsole archive command allows you to:
Please refer to the section Audit Trail Archive Administration in the chapter The Sysconsole Command to get detailed information on the archive
command and its options.
In case a dead model is deleted from the source database, having grants, these grants get deleted as well if the granted participants do not exist in any other model version.
To archive the database:
-password sysop archiveDDL -schemaName arctarg -file c:/ddlfile.ddl
To upgrade a database, use the sysconsole command upgraderuntime.
sysconsole -upgraderuntime
The following arguments are available:
-data, -a - Performs only data migration, preventing any SQL
DDL execution. Note that the ddl argument always needs to be combined with
-step to guarantee a correct result!-ddl, -l <arg> - Spools the SQL DDL defining the audit trail
schema migration into the specified file. No modifications to the audit trail
will be performed.
Note that the ddl argument needs to be combined with
-step to guarantee a correct result!-describe, -d - Describes the migration steps involved,
including any temporary schema versions. No modifications to the audit trail
will be performed.-ignorelock, -i - forces an upgrade run even if the audit
trail DB is already locked for upgrade.-recover, -r - to force a recovery run of the upgrade.-step, -s - Performs exactly one migration step. May require
multiple invocations to fully perform migrations involving temporary schema
versions.Please refer to the chapter The Sysconsole Command in the Operation Guide for detailed information on using sysconsole commands and their provided arguments.
Suppose you are using a Stardust product version for a long time. So its audit trail has huge data. You have archived the data in a target schema. And now you plan to use a later version of Stardust. In this case, you need to upgrade source and target to the new version.
To archive and upgrade:
upgraderuntime on the target and
source databases: sysconsole -upgraderuntime
Suppose you are working on an earlier Stardust version and you plan to upgrade to a newer one
To upgrade the database:
upgraderuntime to upgrade the
database runtime from the earlier version to the new version sysconsole -upgraderuntime
Suppose the database is archived for 500 rows. Then once again 300 more rows are added to the source database. You want to archive the newly added 300 rows but in this case the archived 500 rows should not be overwritten. The 300 rows should be added to the database in continuation of 500 rows. Thus, the target database should have 800 rows.