Kbase P128752: Getting error 735 when trying to modify the database schema after Auditing is enabled.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/19/2010 |
|
Status: Verified
SYMPTOM(s):
Getting error 735 when trying to modify the database schema after Auditing is enabled.
** Incomplete write when writing to the server. (735)
An area to hold the auditing data has been defined and added to the database structure.
The proutil command to enable auditing was given correctly.
Customer defined Auditing policy was defined and activated.
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.1x
CAUSE:
There are some baseline auditing definitions which must be configured and active before additional schema modifications may occur after auditing has been enabled. A Progress / OpenEdge baseline auditing policy is shipped with each 10.1x installation in the $DLC/auditing/policies.xml file.
FIX:
Use the Auditing Policy Maintenance tool to import the default policies.xml file.
1) Launch the Auditing Policy Maintenance Tool
2) Under the file menu - select Connect and choose the audit enabled database.
3) Under the file menu - select Import Policy...
4) Choose the <OpenEdge installation directory>/auditing/policies.xml
5) After the file has loaded choose the Commit option under the file menu.
This policy will activate when loaded.
This policy defines some of the inherent behaviors and auditing choices which are expected for the OpenEdge Schema.