Kbase P107530: Are there any specific database features required to enable auditing?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
29/12/2008 |
|
Status: Verified
GOAL:
Are there any specific database features that are required in order to enable auditing on a database?
GOAL:
Are there any database requirements prior to enabling auditing?
FACT(s) (Environment):
OpenEdge 10.1A
OpenEdge 10.1A 64-bit
All Supported Operating Systems
OpenEdge 10.1x
OpenEdge 10.2x
FIX:
Yes. Type II Storage areas are required for the storage of audit data. Prior to enabling auditing, it is required that you create a Type II storage area in the database to be used to store your audit tables and optionally another area for your audit indexes. This can be done using the prostrct add command. It is not recommended that you place your audit tables or audit indexes in the Schema area.
It is also recommended that you take a backup of the database prior to enabling auditing. When you issue the command to enable auditing on a database you will receive a message to the terminal or standard out, asking if you have taken a backup of the database prior to enabling auditing on this database.
Auditing functionality is available with all OpenEdge 10.1A or later version RDBMS products: Enterprise, Workgroup and Personal database. Auditing can only be enabled against a Progress 10.1A or later version database.
Clients that connect to a database will also need to be audit-aware, which means they will need to be upgraded to 10.1A or later version.