85
Have you ever run into a situation where certain ER administrative commands executed and that caused ER to fail? Without knowing the exact sequence of activities, it would be very difficult to identify the actual commands that caused the problem. Unfortunately, not all ER commands generate alerts or update message log. If you did not use a script to run ER administrative commands, there would be no easy way to track the sequence of activity caused the failure.
An undocumented mechanism could be use for track ER object state changes. Once you enable this tracking mechanism, Informix server generates information about ER administrative operations in server message log file with full command line arguments, which could help analyzing ER issues. By default it would be disable. To enable the tracking either use –
- Add the following entry to the ONCONFIG configuration file and restart the Informix server.
CDR_FEATURES LOGCOMMANDS
OR
- Dynamically change the configuration settings with following command:
cdr
change onconfig "CDR_FEATURES
LOGCOMMANDS"
For example, if you run 'cdr define server --ats=/test/data2 --ris=/test/data2
--connect cdr2 --init g_cdr2 --sync g_cdr1' to define a replication server that would generate
following information in message log:
10:23:12 CDR
remote administrative operation 'define serv -A /test/data2 -R /test/data2 -S
g_cdr1 -I g_cdr2' execution succeeded.
-Sanjit Chakraborty
