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:

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:

  1. Create two users. For example, arcsrc and arctarg
  2. Give the DBA grant to the arcsrc user
  3. Configure the workspace
  4. Deploy the model in arcsrc workspace and execute it
  5. 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
  6. Oracle users, change the extension of the file to ddlfile.sql
  7. Execute the ddl file on the target schema using the arctarg user
  8. 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:

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:

  1. Archive the database
  2. 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:

  1. Create the environment for the new version and let it point to the source database of the earlier version
  2. 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.