No, it is not possible to enable auditing on a replicated database. In order to be able to work with both, enable auditing first and then replication.
If Replication has already been enabled before Auditing, the following Steps outline how to enable auditing and replication on two replication enabled databases named source and target:
0) Create a structure file named add_audit.st with the extend definition for auditing :
d "Audit Data":13,128;64 .
#
d "Audit Indexes":14,1;8 .
1) proshut target -by
2) proutil source -C disableSiteReplication target
rm target.repl.recovery
3) proshut source -by
4) proutil target -C disableSiteReplication source
rm source.repl.recovery
5) prostrct add source add_audit.st
6) prostrct list source
7) proutil source -C enableauditing area "Audit Data" indexarea "Audit Indexes"
8) proutil source -C enableSiteReplication source
9) proserve source -S 2755 -DBService replserv
10) probkup online source source.bkp -REPLTargetCreation
11) prostrct add target add_audit.st
12) echo y | prorest target source.bkp
13) proutil target -C enableSiteReplication target
14) proserve target -S 4501 -DBService replagent
15) Load Audit policies on the source database with the Audit Policy Maintenance utility.
For further detail, refer to Article: What is the best way to move audit policies from one database to another?
An enhancement to the product can be requested through the Progress Community via an Ideas submission. Customer feedback is valuable and Idea submissions are monitored by our Product Management team. Enhancement requests are reviewed during the planning phase of each new product release and a list of the enhancements chosen for implementation can be found in the Release Notes documents that accompany each release. Once an Idea is submitted the Progress Software Community will have the opportunity to comment on and vote for the Idea.
For detailed information on how to submit an Idea, please refer to Knowledge Base article How to submit an enhancement request for a Progress product?
