Database Change Management

The customer wanted to gate dev changes to a critical Oracle Database, and then apply approved changes quickly andaccurately. A project was created to institute an approval process and then apply the changes.

The Application Support Team (AST) creates a script with the requested changes in IBM Rational ClearCase, and launches the project with the location of the script. This project will require approval, so Odyssey notifies the DBAs that there is a requested change, and a link to the script. The DBA inspects the script. If the DBA deems it necessary, the DBA rejects the request with additional notation as to why. For this rejection, Odyssey notifies both Dev and appropriate third parties, then sends the request to the Dev to be amended or closed without being enacted. If the DBA approves the change, Odyssey notifies both Dev and appropriate third parties, and then makes the scripted change available to apply.

As an added precaution, the AST must then initiate the change. Odyssey gets the script from IBM Rational ClearCase, and copies it to the Production Database server. Then, using an Odyssey Oracle Task Agent, Odyssey applies the script. In case of errors, Odyssey notifies the AST and DBAs, and kicks the process back to the AST. In success, Odyssey notifies the AST and DBAs and completes the project.