proutil db-name -C enableauditing area Area-Name [indexarea Index-Area-Name ][deactivateidx ]
Parameters
db-name
Name of the database to be enabled for auditing.
area Area-Name
Name of the area where the auditing data tables are located. If Area-Name contains spaces, you must enclose the name in quotation marks.
indexarea Index-Area-Name
Name of the area where the indexes for the auditing data tables are located. If Index-Area-Name contains spaces, you must enclose the name in quotation marks.
deactivateidx
Deactivate all non-primary indexes for the auditing tables.
Ensuring the security of your audit data requires that the audit data tables be empty when you enable auditing. When you enable your database for auditing, your database can be in one of two possible states: auditing is disabled (or has never been previously enabled) or auditing is deactivated.
If your database has auditing disabled, successfully enabling the database results in the following message:
Auditing has been enabled for database db-name. (12479)
If your database is disabled, and your audit data tables are not empty, the following error message is displayed:
Auditing can not be enabled because auditing data tables are not empty. (13650)
If your database has auditing deactivated, successfully enabling the database results in the following message:
Auditing has been activated
For more information on auditing states, see Auditing states.
Notes
When auditing is first enabled for a database, the meta-schema to support auditing is added to the database, and the event table is populated.
The database must be offline when enabling auditing.
While not required, it is recommended that the auditing tables and indexes be placed in their own area.
Deactivating non-primary indexes is available as an option to improve performance when using database auditing. Deactivated indexes may be activated using PROUTIL IDXBUILD. The non-primary indexes are useful for reporting and should be activated on your audit archive database.
See Auditing tables for brief descriptions of the meta-schema tables created when auditing is enabled and the indexes that can be deactivated. For detailed information, see OpenEdge Getting Started: Core Business Services - Security and Auditing.