CDB/SafeSTOP. Unlike the IBM –STOP command, CDB/SafeSTOP does NOT put objects in the STOP PENDING state during the stop process. Instead, it only issues the –STOP command when an immediate stop can be achieved without impact to database users.

Should CDB/SafeSTOP be unable to issue a –STOP command successfully without incurring a STOP PENDING condition, the user requesting the –STOP will receive notification that the command cannot be safely executed at that time. This entire process is completely transparent to your database users. No delays, no impacts, no hassles.