Allow Dynamic Changes

Often, administrators must set a trace or performance parameter while the domain is up and running. If you enable this option, then you don't need to reboot the domain for the modified parameter value to take effect.

Enter y or n to enable or disable dynamic changes. When disabled, you must reboot (or cycle the processes) for changes to take effect.

When enabled, the server checks an internal time stamp for a particular service request to see if any values have changed for the parameters for which dynamic changes are valid. If values have changed, the system uses the modified parameter value.

You should enable this option in your test and development domains. For production environments, you should enable dynamic changes selectively.

These parameters allow dynamic changes:

• Recycle Count.

• Consecutive service failures.

• Trace SQL and Trace SQL Mask.

• Trace PC and Trace PC Mask.

• Trace PPR and Trace PPR Mask.

• Log Fence.

• Enable DB Monitoring.

• Enable Debugging.

• Dump Memory Image at Crash.

• Dump Managed Objects at Crash.

• Log Error Report.

• Mail Error Report.

• SMTP Settings (all except SMTPGuaranteed, SMTPTrace, and SMTPSendTime).

• Analytic Instance Idle Timeout.

• Analytic Per Server Log.

Note:

The parameters that allow dynamic changes are also identified through comments in the PSAPPSRV.CFG file. Look for the phrase “Dynamic changes allowed for X,” where X is the parameter name. This option does not apply to configuration parameters that Tuxedo relies on, such as the number of processes, whether restart is enabled, the port numbers, the amount of handlers, and so on.