Optim™ Database
Administrator reports
describe the changes that you want to make to the database, the impact
from those changes, and the actions that need to be taken due to the
changes that you have made. Optim Database
Administrator also
provides detailed information about the deployment of your change
commands.
Optim Database
Administrator creates
the following types of reports for you in HTML format:
- Summary of Changes report
- Deployment report
All of the reports are stored in the
Other Files folder
in the same project as your change management script.
Summary of Changes report
Optim Database
Administrator automatically
creates a Summary of Changes report in HTML format for you.
When
you specify your changes, you might want to know what impact those
changes will have on the database before you deploy the DDL. The report
helps you take appropriate action before you deploy your changes to
the database. The Summary of Changes report lists all of your changes.
For example, you can see how a change to the name of a table might
affect the triggers, materialized query tables, or views that are
associated with the table.
Tip: You can also view and
manage the objects that will be impacted by your changes in the Impacted
Objects list in the Change Management Script
Editor.
The Summary
of Changes report is divided into sections that are displayed by using
HTML frames. The navigation frame on the left side of the report lets
you move to specific sections of the report.
You might want
to give the report to your supervisor as a summary of what changes
you will make and what maintenance commands you will run to get a
statistics view of the database. Your supervisor could see the approximate
extent of the changes and approve or disapprove them based on the
change report.
In addition, the report provides details about
any problems that were shown in the Problems view.
You can review the Summary of Changes report by clicking View
Change Report in the Commands section
of the Change Management Script Editor.
Example
The following example describes
renaming a table and generating the report to show the changes and
the impact from those changes.
- Create a change management script based on the GSDB database.
- Rename the PTNR_CNTCT table to PARTNER_CONTACT.
- Create a CUST_FED_TAX table, and add a column CUST_TAX_ID.
- Generate the change commands for this change management script.
After you click the Preview Commands link,
the focus of the Change Management Script Editor changes
to the Commands section.
- Click View Change Report.
- Click the links in the left hand navigation frame of
the report to view information in the various sections of the report
that show how each object type is affected by the changes.
- Use the information in the report to determine your
next steps.
Deployment report
The Deployment report
is generated automatically each time you deploy your change commands
to the database. Any commands that fail to deploy are listed in the
report along with information about why they failed.
Deployment
reports will also show you errors, warnings, and success messages
after you deploy your changes.
Tip: You can
also view messages about the change commands that you ran against
the database in the SQL Results view.