Audit Trail Archive

When deleting data from the audit trail, it may be backed up in a second audit trail DB, the backup audit trail DB.

Audit Trail Archive Administration

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:

specify the schema containing the backup tables
back up all dead models (i.e. no longer active and with no non-terminated processes)
back up a model with all its dependent objects
back up completed or aborted process instances
delete log entries
delete data values for terminated process instances for a specific workflow data
drop data clusters, enable and verify data clusters. You can create table entries in the archive audit trail, as defined in the cluster definition for the archive audit trail whenever new process instances are added to the archive. You can delete cluster table entries from the source audit trail, whenever the corresponding scope process instances and data value entries are removed by the archiver.

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.

Archiving Dead Models having Grants

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.

Archiving the Database

To archive the database:

Create two users. For example, arcsrc and arctarg
Give the DBA grant to the arcsrc user
Configure the workspace
Deploy the model in arcsrc workspace and execute it
Create the DDL file using the command. This file contains the SQL commands that are required to create the target schema.
```
-password sysop archiveDDL  -schemaName arctarg -file c:/ddlfile.ddl
```
Oracle users, change the extension of the file to ddlfile.sql
Execute the ddl file on the target schema using the arctarg user
Check that the arctarg user has tables generated for it.

Note: Once the data gets copied, check that source schema count is reduced to target schema.

Upgrading the Database

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 audittrail schema migration into the specified file. No modifications to the audittrail 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 audittrail 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.

Archiving and Upgrading

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:

Archive the database
Execute the sysconsole command upgraderuntime on the target and source databases:
```
sysconsole -upgraderuntime
```

Upgrading the Database

Suppose you are working on an earlier Stardust version and you plan to upgrade to a newer one

To upgrade the database:

Create the environment for the new version and let it point to the source database of the earlier version
Execute the sysconsole command upgraderuntime to upgrade the database runtime from the earlier version to the new version
```
sysconsole -upgraderuntime
```

Re-archiving the Database

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.