You can open a change management script that has been saved
and closed.
About this task
When you work with a change management script, you might
not finish defining all of your changes at one time. Or, you might
decide that you want to run the changes at a later time. Thus, you
save and close the change management script with the plan to work
with the script at a later time.
Procedure
To open a change management script, complete the following
steps:
- In the Administration Explorer,
drill down to and expand the database that you created the change
management script for.
- Expand the Change Management Scripts folder
and double-click the change management script that you want to open. The change management script opens in the Change
Management Script Editor. If the database changed after
the change management script was closed, these situations can occur
in the Object to be Changed list:
- Some objects are missing from the Object to be Changed list.
- Some objects in the Object to be Changed list
are marked with an error icon.
When you open a change management script,
Optim™ Database
Administrator validates
the changes in the script against the database catalog. Each object
to be changed (created, altered, or deleted) is checked against the
catalog to determine if the change can still be supported. An object
is removed from
Objects to be Changed list
for these situations:
- An object is to be created, but the object already exists in the
database
- An object is to be altered, but the object no longer exists in
the database
- An object is to be dropped, but the object no longer exists in
the database
When Optim Database
Administrator detects
a difference between the change management script and database catalog
and determines that the object to be changed can be corrected, the
object remains in the Objects to be Changed list.
The object is flagged with an error icon. For example, in the Change
Management Script Editor, you altered a table to drop a column and
then closed the change management script. Then, a new column was added
to the table. When you open the change management script, Optim Database
Administrator cannot
determine if the two columns have the same name and are in conflict
with each other. So, the object remains in the Objects
to be Changed list.
- Resolve the issues with any objects that are flagged with
an error icon in the Objects to be Changed list.
- Select an object in the list with an error icon and
click Compare. A wizard opens
that lets you compare the object to the database catalog. The wizard
opens in read-only mode, and you cannot make any changes to the object
in the wizard.
- Use the wizard to analyze the differences, and close
the wizard after you have identified the differences.
- Either use the Change Management Script Editor to
change the object with the error to resolve any identified differences,
or click Ignore to remove the error marker
from the object if you determine that the differences are not a problem.
What to do next
You can continue to work in the Change Management
Script Editor. You might want to add more changes, generate
the change commands, or run the generated change commands.