0755-0758

Previous Table of Contents Next

Page 755

CHAPTER 31

Repository
Administration

IN THIS CHAPTER

• The Repository Administration Utility756
• The Matrix Diagrammer762
• The Repository Object Navigator764
• Repository Reports772

Page 756

Before you can begin to use the design and generation tools of Designer/2000, you must create a Repository. The Repository will contain all the objects used in the building of applications, user definitions for security administration, a Matrix Diagrammer, and a set of reports .

The Designer/2000 suite provides four utilities for administration:

• The Repository Administration utility
• The Matrix Diagrammer
• The Repository Object Navigator
• Repository reports

These administration utilities can provide complete access to every aspect of maintaining the Designer/2000 Repository internally. A Repository administrator must oversee operations of the Repository. The person performing these responsibilities should be an experienced designer. Because the Repository often is used to define the database itself, the administrator must work closely with a DBA to define the components used in the database creation ”such as tablespaces, storage definitions, grants, roles, and so on. The Repository is used to document the database and its objects. Data Definition Language (DDL) can be generated directly from the tool, and the resulting files are implemented externally. In addition, you can use the tool to design, document, and generate the application to create form files, report files, PL/SQL triggers, packages, procedures, and functions.

The Repository Administration Utility

As you learned in Chapter 30, "Introduction to and Installation of Designer/2000," the first utility you will use is the Repository Administration Utility (RAU). You use the RAU to install and upgrade the instance and to define and administrate users' security and ownership. In addition, the RAU enables users to back up, upgrade, and extend the Repository by using the user-extensibility feature. The Repository owner is different from the database administrator. The Repository owner exists only within the confines of Designer/2000, and the database administrator exists only in the database itself.

NOTE

Attempting to use the RAU as SYS, SYSTEM, or any other subordinate, regardless of the security level, will result in failure.

When you start the RAU, you see the Repository Administration Utility dialog box with the following options:

• Repository Management, including Install, Upgrade, Re-create, Remove Repository, and Remove All Objects
• Backup, including Import and Export

Page 757

• User Extensions, including Maintain User Extensions, Load User Extensions, and Extract User Extensions
• User Maintenance (Maintain Users)
• Check, including Privileges Objects & Parameters and Tablespaces

The Repository Management Screen

When the RAU starts, the Repository Management screen appears at the top of the RAU dialog box. During the initialization process, a database already must exist for you to use a repository. Based on whether a database exists, the RAU selects Install or Upgrade as the active button. Also, system information is displayed at the bottom of the screen with the user ID and Repository and connection status.

The Create/Re-create Section

The Create section of the screen is available only to current installed versions of Designer/2000. Selecting the Re-create button in this section enables the Repository administrator to re-create specific objects of the Repository instance to correct problems. This may be a quicker solution to fixing problems than running the entire upgrade process again. The radio button options you can select from the Select Re-create Option dialog are as follows :

• Indexes
• Views
• Triggers
• Packages
• Recompile Objects
• Full Reconcile
• Hash Tables

You can also run a precheck by selecting the Precheck button.

The Remove Repository and Remove All Objects Sections

The Remove sections can be very dangerous! The Remove Repository button here drops all database objects created for the Repository instance. The second option is Remove All Objects; choosing this option drops all objects owned by the Repository owner. Again, be aware that objects will be gone after you execute one of these two options.

NOTE

The Remove All Objects option is available when a new install option is detected . This option could be useful for ensuring that the Repository owner owns nothing prior to the Repository installation. It is a good idea for the database administrator to ensure that objects to be dropped are indeed dropped.

Page 758

The Backup Section

The Backup section provides Repository-specific backup capabilities (outside of the backups performed by the database administrator). The Repository manager can export and import by using these methods :

• Using the Oracle Import utility to import tables, views, and packages that belong to the Repository from a previously created Export file.
• Creating an Export file of all Repository tables (only the tables!).
• Creating an Export file of all objects owned by the Repository owner. Objects created outside of the RAU are not included.
• Creating an Export file of all tables owned by the Repository owner, including any table created by using the Generate DDL utility.

Tablespace Selections

The Repository Management screen offers two tablespace selection drop-down listboxes. The Repository manager can use these listboxes to select tablespaces other than the default tablespace setup for the Repository owner. These listboxes also enable you to separate the Repository indexes from the Repository tables for tuning purposes, which is highly recommended.

Buttons

You use the buttons on the Repository Management screen to initiate these actions:

• Continue: Tells the utility to perform whatever action has been selected
• Precheck: Tells the utility to check the Repository owner's privileges and to check the selected tablespaces for the proper amount of space required for the Repository to be installed or upgraded
• Help: Brings up the online help

The Privileges Dialog Box

The Privileges screen displays the privileges necessary to be a Repository owner. If any privilege does not have an X beside it, the DBA must be notified before the installation or upgrade.

If the DBA has created specific roles for Repository owners and users, you can easily view them on the Privileges screen.

The Tablespace Analysis Screen

The Tablespace Analysis screen shows an overview of the tablespaces the Repository owner has access to, as shown in Figure 31.1. The Repository manager uses this screen to monitor the space requirements of the Repository. The RAU utility also identifies the Repository owner's default and temporary tablespaces and user quota, as well as free space and space available.

Previous Table of Contents Next