Loads audit data into your database from your audit archive file.

Syntax

proutil db-name -C auditload archive-file-name
    [-recs num-recs][-checkseal]
    [-userid user-id[-password passwd]]
    [-Cipher cipher-id]

Parameters

db-name

Specifies the database where the archived data is being loaded.

archive-file-name

Specifies the audit archive file to load.

-recs num-recs

Specifies the number of records to load in a single transaction. AUDITLOAD executes a transaction for every num-recs records it loads. The default for num-recs is 100, and the maximum is your current Lock Table Entries (-L) setting. The multi-user default for -L is 8192.

-checkseal

Specifies that AUDITLOAD verify that the seal of each audit data record matches the database MAC key prior to loading it into the archive database. This option requires that the audit policies in effect when the audit data records were generated, specified a Data Security Level of DB Passkey. For more information on creating audit policies and data security, see OpenEdge Getting Started: Core Business Services - Security and Auditing. During the AUDITLOAD, the _db-detail record containing the database MAC key is loaded into the archive database before any of the audit data records, making it available for the verification process.

-userid username

Specifies the user name of the privileged user. If you are using the _User table, username must be defined there, and you must include the -userid parameter to identify the user. If you are not using the _User table, use of -userid is optional; in this scenario, username specifies a local operating system login ID. Regardless of the source, username must have the Audit Data Archiver privilege in order to run AUDITLOAD.

-password passwd

Specifies the password for username. If you are using the _User table, passwd is the password defined for the user there. The value of passwd can be clear text or encrypted. If you are not using the _User table and have specified a local operating system ID with -userid, passwd must be the encrypted value of the DB Pass key. See OpenEdge Getting Started: Core Business Services - Security and Auditing or the Data Administration online Help for information on the DB Pass Key. For information on encrypting a password, see the description of the genpassword utility in OpenEdge Getting Started: Installation and Configuration.

If you do not supply a password corresponding to username, the utility will prompt for it.

-Cipher cipher-id

For an Enterprise database enabled for Transparent Data Encryption, specify -Cipher 11 or -Cipher 12 to indicate that the contents of the archive file being loaded are encrypted. The specified cipher id should match the cipher id specified by the PROUTIL AUDITARCHIVE command at the time the archive file was created. You are prompted to enter the passphrase that was specified when the archive file was created.

Prior to beginning the load, AUDITLOAD verifies the data seal of the archive file. If AUDITLOAD encounters a duplicate record, it is ignored without error.

Loading archived audit data is an auditable event. If the active audit policy on the archive database is configured to audit AUDITLOAD, then every time it runs, an audit event will be generated.

Notes

• The Audit Data Archiver privilege is required to run AUDITLOAD.
• AUDITLOAD runs against a database that is online as well as offline.
• Multiple instances of AUDITLOAD can simultaneously run against the same database.
• AUDITLOAD generates and updates index information for each record at the time it is loaded.
• If the contents of the archive file was encrypted with -Cipher 11 or -Cipher 12 when created, you must specify -Cipher 11 or -Cipher 12 for PROUTIL AUDITLOAD to indicate that the file is encrypted. You are prompted to enter the passphrase entered when the file was created. You cannot load the contents without the passphrase.
• When loading the contents of an encrypted archive file, the loaded records are not encrypted unless there is an active encryption policy on the table before the load begins. See PROUTIL EPOLICY MANAGE qualifier or Transparent Data Encryption for more information on creating an encryption policy.