The existing DB2 probe deployment does not support the retention of the 2 new required variables during the configuration step. We would provide all the required information about how the probe needs to/should work up-front, instead of configuring the profile with "not all the required information". The existing method causes a probe start failure.
In order to enable the probe, we have to go through the DB2 probes one-by-one, make the required changes on the probe configuration file, then restart the probe. This is an inefficient method as we deploy several probes at the same time.