Copyright: Repository Mgmt Online Help - V9.0.2.93.7   Copyright © 1995, 2003, Oracle Corporation  All Rights Reserved


About the Repository Administration Utility

Related Topics

The Repository Administration Utility enables the person responsible for administering a repository to install and manage a repository environment. This person is normally the repository owner. For more details on setting up the repository owner’s account, see the Installation Guide for this release.

Note:	Repository users can also use the Repository Administration Utility, but only to migrate a repository from Release 2.1.2 or Release 6.0 of this product to a new one installed for this release.

Therefore, most of the online documentation for the Repository Administration Utility is for the repository owner only.

You can use the Repository Administration Utility to:

•	install a new repository for this product  How

Note:	You must install a repository before you start any modeling, design or generation activities.

•	migrate a repository from Release 2.1.2 or Release 6.0 of this product  How

Note:	To use this release to continue any modeling, design or generation activities, you must first migrate the repository from the earlier release.

•	upgrade a repository from a previous release of this product  How

Note:	To use this release to continue any modeling, design or generation activities, you must first upgrade the repository from the earlier release.

•	check system details and requirements using the Check Requirements Utility, e.g. the system privileges a repository owner requires  About

•	check the status of repository objects and take appropriate action using the Object Status Utility, e.g. recompiling repository objects  About

•	delete all the repository objects belonging to the repository owner  How

•	delete all the database objects belonging to the repository owner, including all the repository objects  How

•	back up the contents of a repository  How

•	restore a repository from a backup  How

•	maintain users' access to the repository  How

•	edit or extend the repository structure using the user extensibility features  About

Note:	To access these features, use the buttons on the Repository Administration Utility.  About

Repository terminology

repository instance

All the database objects (e.g. tables, views, packages) that make up an individual repository. A repository instance can support:

•	the core repository element types (files and folders) required for source control purposes only

•	Oracle Designer

repository owner

A repository user who owns the repository objects and who performs administrative tasks for the repository, e.g. granting access to repository users. Only the repository owner can use all the features in the Repository Administration Utility and cannot be the Oracle users SYSTEM or SYS.

repository user

An Oracle database user who has been granted access to the repository. Repository users can only use the Repository Administration Utility to migrate a repository from Release 2.1.2 or Release 6.0 of this product to a new one installed for this release.

Application Programming Interface (API) packages

PL/SQL packages which manage the storage of all repository data. API packages ensure that tools that store data in the repository validate that data consistently.

instance tables

A subset of the repository tables, used to record the data that repository users enter.

definition tables

A subset of repository tables that contain the lookup or driving data that API packages, generator products and user extensibility features use, e.g. syscase and RM meta tables. Installation, migration and upgrade processes create these tables in the same Oracle schema as the other repository objects.

public synonyms

The method of giving users access to a repository using one set of synonyms, instead of creating one set of synonyms for each user. For each Oracle instance, you can only have one repository accessed using public synonyms.

version control

The process of maintaining multiple versions of software development objects. Version control is the most basic requirement for a software configuration management system.

policies

Repository-wide options that control certain aspects of version control, file naming (case sensitivity) and object dependencies.


About the Repository Administration Utility buttons

Related Topics

To access Repository Administration Utility features, use the following buttons:

Check Requirements

	Opens the Check Requirements Utility. Use it to check system requirements for installing, migrating or upgrading an repository, e.g. required system privileges.  How

Install/Migration/Upgrade

	Opens the Install dialog box. Use it to install a new repository onto a database.  How
	Opens the Migrate dialog box. Use it to migrate an existing repository to a new one installed for this release.  How
	Opens the Upgrade dialog box. Use it to upgrade a repository from a previous release of this product.  How

User Maintenance

	Opens the User Maintenance dialog box. Use it to add and delete repository users and view details of them.  How
	Opens the Select Recreate Option dialog box. Use it to manage the repository structure, e.g. reloading objects.  How
	Opens the Object Status Utility. Use it to view the status of and maintain repository objects.  How
	Opens the Compute Statistics dialog box. Use it to get physical storage statistics for database tables.  How

Deinstall

	Deletes all repository objects belonging to the current repository owner.  How
	Deletes all the database objects belonging to the current repository owner, including all the repository objects.  How

User Extension

	Opens the User Extensibility dialog box. Use it to create, publish, amend and delete user-defined items.  How
	Opens the Open dialog box. Use it to import user-defined items into a repository.  How
	Opens the Save dialog box. Use it to export user-defined items to a dump file.  How

Backup

	Opens the Save dialog box. Use it to back up the contents of the repository to a dump file.  How
	Opens the Open dialog box. Use it to restore the contents of a repository from a dump file.  How


Repository Administration Utility

Introduction

About the Repository Administration Utility

About the Repository Administration Utility buttons

Installing, migrating or upgrading a repository

Checking installation and migration requirements

Installing a repository

Migrating a repository

Upgrading a repository

Log files from an installation or migration

Setting up and using the broadcast service

About the broadcast service

Configuring the broadcast service

Using private or public synonyms for repository access

About public and private synonyms

Changing between public synonyms and private synonyms

Deleting the public synonyms used for repository users

Deleting the private synonyms used for repository users

Maintaining repository users

Granting repository access to an Oracle user

Revoking repository access

Moving user access between repositories

Reconciling the grants for all repository users

Viewing and managing repository information

About the Check Requirements Utility

Viewing system privileges, object privileges and database roles

Viewing tablespace details

Viewing Repository Administration Utility parameter settings

Modifying Repository Administration Utility parameter settings

Creating an HTML report

Viewing and managing repository object information

About the Object Status Utility

About repository object statuses

Viewing details of repository objects

Requerying repository objects

Working with repository objects

Truncating temporary tables

Computing statistics on repository indexes and tables

Editing details of repository indexes and tables

Rebuilding repository indexes

Recompiling repository objects

Reloading repository objects

Removing the reload mark for repository objects

Creating an HTML report

Deleting all objects in the repository

Backing up and restoring the repository

Backing up the repository

Restoring the repository from a backup

Using the user extensibility features

About user extensibility

Using the user extensibility features

Troubleshooting and performing general tasks

Troubleshooting during day-to-day operations

Dealing with reported errors

Changing the database connection

Maintaining repository performance


About user extensibility

Related Topics

Oracle Repository contains the following system-defined element, association and text types (object types), which you can use for your development purposes:

Object type	Definition
Element type	The particular type of an element held in the repository, e.g. table, module. Instances of element types are called elements.
Association type	A relationship between two repository element types, e.g. module table usage. Instances of association types are called associations.
Text type	A classification for free-format text associated with an element type or association type, e.g. description, notes.
Note:	System-defined object types are delivered as part of Oracle Repository. You cannot delete them or amend their details.

However, system-defined object types may not entirely meet your requirements. In these cases, the Repository Administration Utility enables you to create your own object types, which are called user-defined object types. This is user extensibility.

For example, you need a new user-defined element type called Subject Group to represent entities by subject.

Properties and Text Type Usages

You can also define properties for user-defined element types and association types, as well as extra properties for many system-defined element and association types using template user-defined properties.  About

Note:	You cannot amend or delete system-defined properties. You also cannot delete template user-defined properties, but you can amend them.

You can then use text types to help define instances of an element or association type by associating any system-defined or user-defined text type with it. This is a text type usage.

New user-defined element types have two default text type usages, Description and Notes. For example, an instance of the new user-defined element type called Security Policy would include an instance of the text type Description.

Creating user-defined items

The repository contains blank template element types and association types, with short names in the range E0 - E499 (element types) and A0 - A499 (association types). When you create a new element type or association type, the Repository Administration Utility automatically uses the next available template, up to the limit of 500 for each type.

Note:	23 templates are already used for Oracle’s business planning and distributed capability features, e.g. E1 - Objective, A8 - Business Unit to Objective. They are E1 to E6, E20, A1 to A11 and A20 to A24 inclusive.

There are three steps to using user-defined items in the repository:

1.	Enter details of the object type, property or text type usage.  How

2.	Publish the user-defined item. This enables repository users to see the user-defined item, e.g. in the Repository Object Navigator.  How

3.	Reconcile the grants for all repository users (using Full Reconcile). This enables users to create instances of the user-defined items.  How

Note:	You can then edit or delete user-defined object types or text type usages, but you can only edit user-defined properties.


About properties of element and association types

Related Topics

All system and user-defined element and association types have some:

•	system-defined properties, e.g. Name

•	audit properties, e.g. Date Created

Many system and all user-defined element and association types may also have some user-defined properties.

Properties of system-defined element or association types

You cannot amend system-defined properties of system-defined element and association types. For example, the element type Module has the property Language to record the language used to develop a module.

However, many system-defined element and association types also have a set of template properties, with default names in the range Usrx0 - Usrx19. You can edit these templates to define up to 20 extra properties, but you cannot delete them.

For more information on the system-defined element types and association types for which you can define extra properties, see the Oracle Repository API online documentation.

Properties of user-defined element or association types

User-defined element types have two system-defined properties, Name and Comment, which you cannot amend. New user-defined element types also have two default text type usages, Description and Notes. New user-defined association types have the system-defined property Comment and reference the element types it associates.

Both user-defined element types and association types also have a set of template properties with default names in the range Usrx0 - Usrx19, which you can use to define up to 20 extra properties. You cannot delete template user-defined properties.

Audit properties

All system and user-defined element and association types have the following audit properties, the values of which the system automatically maintains:

Date created	Modified by
Created by	Number of times modified
Date modified


User Extensibility dialog box

Related Topics

Enables you to extend the structure of a repository by creating your own element types, association types, text types, properties and text type usages.  How

Note:	You can also use this dialog box to define properties and create text type usages for system-defined element types, association types and text types.

What do the symbols mean?

Dialog box options

Display area

A list of all system and user-defined object types for each chosen type, i.e., Elements, Associations and Text Types. This includes any system or user-defined properties and text type usages.

Elements

Controls the display of system and user-defined element types in the display area.

Associations

Controls the display of system and user-defined association types in the display area.

Text Types

Controls the display of system and user-defined text types in the display area.

New

Enables you to create a new user-defined object type or text type usage.

Edit

Enables you to edit details of the selected user-defined object type, property or text type usage.

View

Enables you to view details of the selected system or user-defined object type, property or text type usage.

Delete

Enables you to delete the selected user-defined object type or text type usage.

Note:	You can only amend user-defined properties of an object type. You cannot delete system-defined object types, properties or text type usages and template user-defined properties. You cannot delete user-defined object types or text type usages after publishing them or if instances of them exist.

Publish

Publishes the selected user-defined object type, property or text type usage.  How

This enables repository users to see the user-defined item, e.g. in the Repository Object Navigator. To enable repository users to create instances of the user-defined item in the repository, you must then use Full Reconcile to reconcile the grants for all users.  How

Unpublish

Revokes publication of the selected user-defined object type, property or usage. You must revoke publication of the user-defined item to edit or delete it, but not to edit its display names.  How

Note:	Before you can revoke publication of a user-defined item, you must ensure no other repository users are using it and no instances of it exist in the repository.

Remap

Enables you to change the short name of the selected user-defined object type, property or text type usage.  About


User Extension Remap Facility dialog box

Related Topics

Enables you to change the short name of the selected user-defined object type, property or text type usage. For example, you would change the short name of a user-defined text type if you need to import it into a repository that contains a user-defined text type with the same short name. This is remapping the object type, property or text type usage.  How

Remap Definition

From

The short name of the user-defined object type, property or text type usage.

to

The new short name for the user-defined object type, property or text type usage.


Element Type Details dialog box

Related Topics

Enables you to create a user-defined element type using a template element type in the repository. You can also edit details of the user-defined element type and view details of a system-defined or user-defined element type.  How

Note:	If a user-defined element type is published, you must first revoke its publication before you can edit it, except for editing the Display Name or Display Plural Name.  How

Dialog box options

Short Name

The short name of the element type.

Note:	For user-defined element types, this is in the range E0 to E499. For new user-defined element types, this is the next available blank template element type.

Name

The name of the element type, displayed in uppercase characters.

Plural Name

The plural name of the element type, displayed in uppercase characters.

Display Name

(Optional)  The element type name that displays in the User Extensibility dialog box. This field is case sensitive. If you do not enter this name, only the short name displays.

Display Plural Name

(Optional)  The plural name of the element type used in other tools, e.g. the Repository Object Navigator. This field is case sensitive. If you do not enter this name, other tools display the name entered in the Name field in uppercase characters instead.

Details

This group gives more display-only details about the element type.

Package Name

The name of the system generated API package for the element type. This is the name of the element type with the prefix CIO.

View Name

The name of the system generated meta model view for the element type. This is the plural name of the element type with the prefix CI_.

User element type

Indicates if this is a user-defined element type. If not checked, this is a system-defined element type.

Has been extended

Indicates if user-defined properties or text type usages exist for the element type.

Note:	This is always checked for user-defined element types.

Published

Indicates if the element type is published. If not checked, the user-defined element type is not published and repository users cannot see it.  To enable repository users to use a user-defined element type, you must first publish it.  How

Note:	This is always checked for system-defined element types.


Association Type Details dialog box

Related Topics

Enables you to create a user-defined association type using a template association type in the repository. You can also edit details of the user-defined association type and view details of a system-defined or user-defined association type.  How

Note:	You cannot create an association type that references a non-shareable element type, except for a business function.

If a user-defined association type is published, you must first revoke its publication before you can edit it, except for editing the Display Name or Display Plural Name.  How

Dialog box options

Short Name

The short name of the association type.

Note:	For user-defined association types, this in the range A0 to A499. For new user-defined association types, this is the next available blank template association type.

Name

The name of the association type, displayed in uppercase characters.

Plural Name

The plural name of the association type, displayed in uppercase characters.

Display Name

(Optional)  The association type name that displays in the User Extensibility dialog box. This field is case sensitive. If you do not enter this name, only the short name displays.

Display Plural Name

(Optional)  The plural name of the association type used in other tools, e.g. the Repository Object Navigator. This field is case sensitive. If you do not enter this name, other tools display the name entered in the Name field in uppercase characters instead.

Details

This group gives more details about the association type.

OWNING ELEMENT: Element Type

The element type of the first element in the association. This is the element that owns the association.

OWNING ELEMENT: Cardinality

The cardinality (Many or One) of the relationship between the owning element and the second element in the association.

TO: Element Type

The element type of the second element in the association.

TO: Cardinality

The cardinality (Many or One) of the relationship between the second element and the owning element in the association.

Package Name

The name of the system generated API package for the association type. This is the name of the association type with the prefix CIO.

View Name

The name of the system generated meta model view for the association type. This is the plural name of the association type with the prefix CI_.

User element type

Indicates if this is a user-defined association type. If not checked, this is a system-defined association type.

Has been extended

Indicates if user-defined properties or text type usage exist for the association type.

Note:	This is always checked for user-defined association types.

Published

Indicates if the association type is published. If not checked, the association type is not published and repository users cannot see it. To enable repository users to use a user-defined association type, you must first publish it.  How

Note:	This is always checked for system-defined association types.


Property Details dialog box

Related Topics

Enables you to define extra properties for system-defined or user-defined element types or association types. You can also edit details of a user-defined property and view details of a system-defined or user-defined property.  How

Note:	If a user-defined property is published, you must first revoke its publication before you can edit it, except for editing the Displayed Name.  How

For more information on the system-defined element types and association types for which you can define extra properties, see the Oracle Repository API online documentation.

Dialog box options

Element Type/Association Type

The short name and the name of the element type or association type.

Property Name

The name of the property for that element type or association type.

Displayed Name

The property name that displays in other tools, e.g. the Repository Object Navigator. This field is case sensitive. If you do not enter this name, other tools display the name entered in the Property Name field in uppercase characters instead.

Note:	For new user-defined properties, this is the name of the next available blank template property, in the range Usrx0 - Usrx19.

Display details

This group gives details on the values a user can enter for a property and how it displays in other tools, e.g. the Property Palette of the Repository Object Navigator.

Datatype

The data format in which users can enter values for the property:  CHAR, NUMBER or DATE.

Length

The maximum length in characters of values for the property.

Precision

The maximum number of digits, including those after the decimal point, that a user can enter for values of this property.

Note:	This only applies to NUMBER datatypes.

Scale

The maximum number of digits after the decimal point that a user can enter for values of this property.

Note:	This only applies to NUMBER datatypes.

Sequence

The position the property appears in relative to other properties, e.g. a property with a sequence number of 1 appears above one with a sequence number of 2.

Note:	For user-defined properties of system-defined element types or association types, this only affects the display in a group of user extensibility properties.

Updateable

(Optional)  Indicates if users can enter or edit a value for the property. If not checked, users cannot enter or edit a value.

Other details

This group gives more details about the property, including some display-only details.

Case mode

The character format in which users must enter values for the property:  MixedCase (default), UpperCase or LowerCase.

Mandatory

(Optional)  Indicates if users have to enter a value for the property. If not checked, users do not have to enter a value.

User property

Indicates if this is a user-defined property. If not checked, this is a system-defined property.

Has been extended

Indicates if user-defined items exist for the property.

Note:	This box is always checked for user-defined properties. If not checked, this is a system-defined property.

Published

Indicates if the property is published. If not checked, the property is not published and repository users cannot see it. To enable repository users to use a user-defined property, you must first publish it.  How

Note:	This is always checked for system-defined properties.

Base table

The name of the repository table that contains details of the element type or association type to which this property belongs.

Base column

The name of the column in the base table that contains details of this property.


Text Type Details dialog box

Related Topics

Enables you to create a user-defined text type. You can also edit details of the user-defined text types and view details of a system-defined or user-defined text type.  How

Note:	If a user-defined text type is published, you must first revoke its publication before you can edit it.  How

Dialog box options

Name

The name of the text type (up to 6 uppercase characters).

Details

This group gives more details about the text type, including some display-only details.

Description

(Optional)  A description of the text type, which displays in the User Extensibility dialog box and Property Palette of other tools, e.g. the Repository Object Navigator. This field is case sensitive. If you do not enter this description, the name entered in the Name field displays instead.

Extended

Indicates if this is a user-defined text type. If not checked, this is a system-defined text type.

Published

Indicates if the text type is published. If not checked, the text type is not published and repository users cannot see it. To enable repository users to use a user-defined text type, you must first publish it.  How

Note:	This is always checked for system-defined text types.


Text Type Usage Details dialog box

Related Topics

Enables you to add system-defined or user-defined text types to system-defined or user-defined element types or association types.  How

Note:	If a user-defined text type usage is published, you must first revoke its publication before you can edit it.  How

Dialog box options

Text Type

The name of the text type that you want to add.

Element Type

(Optional)  The element type to which you want to add the text type.

Association Type

(Optional)  The association type to which you want to add the text type.

Details

This group gives more details about the text type usage, including some display-only details.

Display Sequence

The position in which the text type appears in other tools relative to other properties, e.g. a text type with a sequence number of 1 appears above one with a sequence number of 2.

Note:	For user-defined text type usages of system-defined element types or association types, this only affects the display in a group of user extensibility properties.

Extended (user usage)

Indicates if this is a user-defined text type. If not checked, this is a system-defined text type.

Published

Indicates if the text type is published. If not checked, the text type is not published and repository users cannot see it. To enable repository users to use a user-defined text type usage, you must first publish it.  How

Note:	This is always checked for system-defined text type usages.


Using the user extensibility features

Creating and defining user-defined items

Creating element types

Creating association types

Creating text types

Defining properties for element types and association types

Adding text types to element types and association types

Working with system-defined and user-defined items

Viewing details of system-defined or user-defined items

Editing user-defined items

Changing the short name of user-defined items

Publishing user-defined items

Revoking publication of user-defined items

Deleting user-defined items

Importing and exporting user-defined items

Importing user-defined items

Exporting user-defined items


Symbols for system and user-defined items

When you open the User Extensibility dialog box, you can see the following symbols:

 Element types

 Association types

 Text types

As you expand the nodes, Blue symbols indicate parent nodes. Red symbols indicate unpublished items, while Green ones indicate published items:

Parent	Item
Element type	Published element type
	Unpublished element type
Association type	Published association type
	Unpublished association type
Property	Published property
	Unpublished property
Text type	Published text type
	Unpublished text type
Text type usage	Published text type usage
	Unpublished text type usage


Creating element types

Related Topics

User extensibility enables you to create your own element types.  About

To create an element type:

1.	In the Repository Administration Utility, open the User Extensibility dialog box.  How

2.	Expand ELEMENT TYPES and select User Defined Elements.

3.	Click New to open the Element Type Details dialog box.

4.	Enter details of the element type. For more information, see the Element Type Details dialog box.

5.	(Optional)  Define extra properties for the element type.  How

6.	Publish the element type.  How


Creating association types

Related Topics

User extensibility enables you to create your own association types. However, it cannot reference a non-sharable element type, except for a business function.  About

Note:	You cannot create an association type that references a non-shareable element type, except for a business function.

To create an association type:

1.	In the Repository Administration Utility, open the User Extensibility dialog box.  How

2.	Expand ASSOCIATION TYPES and select User Defined Associations.

3.	Click New to open the Association Type Details dialog box.

4.	Enter details of the association type. For more information, see the Association Type Details dialog box.

5.	(Optional)  Define extra properties for the association type. How

6.	Publish the association type.  How


Creating text types

Related Topics

User extensibility enables you to create your own text types.  About

To create a text type:

1.	In the Repository Administration Utility, open the User Extensibility dialog box.  How

2.	Expand TEXT TYPES and select User Defined Text Types.

3.	Click New to open the Text Type Details dialog box.

4.	Enter details of the text type. For more information, see the Text Type Details dialog box.

5.	Publish the text type.  How


Defining properties for element and association types
Defining properties for element types or association types

Related Topics

All element types and association types have system-defined properties, but some system-defined and all user-defined ones can also have user-defined properties.  About

You can define up to 20 extra properties for these element types and association types.

To define a property for an element type or association type:

1.	In the Repository Administration Utility, open the User Extensibility dialog box.  How

2.	Expand ELEMENT TYPES or ASSOCIATION TYPES as appropriate.

3.	Expand System Defined or User Defined as appropriate, then expand the element type or association type for which you want to define the property.

4.	Expand Properties and select the Usrxn name for the property you want to define.

Note:	If no template properties display for a system-defined element type or association type, then you cannot define extra properties for it. For more information on which system-defined element types and association types you can define properties for, see the Oracle Repository API online documentation.

5.	Click Edit to open the Property Details dialog box.

6.	Enter details of the property. For more information, see the Property Details dialog box.

7.	(Optional)  Publish the property. You can publish the property now or when you publish the user-defined element type or association type for which the property exists.  How

Note:	Repository users can only use a user-defined property if you also complete and publish the user-defined element type or association type.


Adding text types to element and association types
Adding text types to element types and association types

Related Topics

Element or association types may use text types to help define instances of that object type. These are text type usages.  About

You can add any text type to any element type or association type.

To add a text type to an element type or association type:

1.	In the Repository Administration Utility, open the User Extensibility dialog box.  How

2.	Expand ELEMENT TYPES or ASSOCIATION TYPES as appropriate.

3.	Expand System Defined or User Defined as appropriate, then expand the element type or association type to which you want to add the text type.

4.	Select Extended Text Usages.

Note:	You can also create a text type usage using the Extended Usages node. To see it, expand the appropriate text type under Text Types.

5.	Click New to open the Text Type Usage Details dialog box.

6.	Enter details of the text type usage. For more information, see the Text Type Usage Details dialog box.

7.	Publish the text type usage.  How

Note:	Repository users can only use a user-defined text type usage if you also complete and publish the user-defined element type or association type for which it exists.


Viewing details of system-defined or user-defined items

Related Topics

You can view details of all system-defined and user-defined object types, properties and text type usages.

To view details of a system-defined or user-defined item:

1.	In the Repository Administration Utility, open the User Extensibility dialog box.  How

2.	Expand ELEMENT TYPES, ASSOCIATION TYPES or TEXT TYPES as appropriate.

3.	Expand System Defined or User Defined to see the appropriate object type.

4.	(Optional)  To view details of a property or text type usage, expand the object type then Properties or Extended Text Usages as appropriate.

5.	Select the object type, property or text type usage, then click View.


Editing user-defined items

Related Topics

You can edit details of all user-defined object types, properties and text type usages. However, you cannot edit system-defined object types, properties or text type usages.

Note:	If a user-defined object type, property or text type usage is published, you must first revoke its publication before you can edit it, except for editing its display names.  How

To change the short name of a user-defined object type or property use Remap, because you do not have to first revoke its publication.  How

To edit a user-defined item:

1.	In the Repository Administration Utility, open the User Extensibility dialog box.  How

2.	Expand ELEMENT TYPES, ASSOCIATION TYPES or TEXT TYPES as appropriate.

3.	Expand User Defined to see the appropriate object type.

4.	(Optional)  To edit details of a property or text type usage, expand the object type then Properties or Extended Text Usages as appropriate.

5.	(Optional)  Revoke publication of the user-defined item.  How

6.	Select the object type, property or text type usage, then click Edit.


Changing the short name of a user-defined item
Changing the short name of user-defined items

Related Topics

If necessary you can change the short name of a user-defined object type, property or text type usage.  About

Note:	This is called remapping the object type, property or text type usage. You do not have to first revoke publication of the user-defined item.

To remap a user-defined item:

1.	In the Repository Administration Utility, open the User Extensibility dialog box.  How

2.	Expand ELEMENT TYPES, ASSOCIATION TYPES or TEXT TYPES as appropriate.

3.	Expand User Defined to see the appropriate object type (or System Defined to remap a user-defined property for a system-defined object type).

4.	(Optional)  To remap a property of a user-defined object type, expand the object type then Properties.

5.	Select the object type or property you want to remap, then click Remap to open the User Extension Remap Facility dialog box.

6.	Enter the new short name for the object type or property. For more information, see the User Extension Remap Facility dialog box.


Publishing user-defined items

Related Topics

To enable repository users to see a user-defined object type, property or text type usage, you must publish it.  About

If you publish a user-defined object type, you must then use Full Reconcile to reconcile grants for all repository users. This enables repository users to create instances of the object type, e.g. in the Property Palette of the Repository Object Navigator.  How

Note:	If you defined extra properties for an element type or association type but did not publish them, you can publish them at the same time.

To publish a user-defined item:

1.	In the Repository Administration Utility, open the User Extensibility dialog box.  How

2.	Expand ELEMENT TYPES, ASSOCIATION TYPES or TEXT TYPES as appropriate.

3.	Expand User Defined to see the appropriate object type (or System Defined to publish a user-defined property or text type usage for a system-defined object type).

4.	(Optional)  To publish a property or text type usage, expand the object type then Properties or Extended Text Usages as appropriate.

5.	Select the name of the object type, property or text type usage you want to publish.

6.	Click Publish.

7.	Reply OK to the message to confirm your action.

8.	(Optional)  Reply Yes or No if you see a message which asks if you want to publish the unpublished properties that exist for this object type.

9.	(Optional)  Use Full Reconcile to enable repository users to create instances of the user-defined object type.  How


Revoking publication of user-defined items

Related Topics

If you want to edit or delete a published user-defined object type, property or text type usage, you must first revoke its publication. This means repository users can no longer see or create instances of it.

Note:	Before revoking publication of a user-defined item, ensure no other repository users are using it and no instances of it exist in the repository. For user-defined object types, you must also revoke publication of and delete any properties and text type usages.

To revoke publication of a user-defined item:

1.	Ensure no other repository users are using or need to use the user-defined item for which you want to revoke publication. You can search for instances of the item using the search feature in the Repository Object Navigator.  How

2.	Delete all instances of the user-defined item from the repository. To avoid repository users using it, this may involve temporarily removing their access to the repository.

3.	In the Repository Administration Utility, open the User Extensibility dialog box.  How

4.	Expand ELEMENT TYPES, ASSOCIATION TYPES or TEXT TYPES as appropriate.

5.	Expand User Defined to see the appropriate object type (or System Defined to revoke publication of a user-defined property or text type usage for a system-defined object type).

6.	(Optional)  To revoke publication of a property or text type usage, expand the object type then Properties or Extended Text Usages as appropriate.

7.	Select the object type, property or text type usage for which you want to revoke its publication.

8.	Click Unpublish.

9.	Reply OK to the message to confirm your action.

Note:	If instances of the user-defined item still exist, a message appears stating that you cannot revoke publication. Restart this task at step two.


Deleting user-defined items

Related Topics

You can delete a user-defined object type or text type usage providing no other repository users are using it and no instances of it exist in the repository. If the user-defined item is published, you must also first revoke its publication.  How

Note:	You cannot delete system-defined object types, properties or text type usages. You also cannot delete template user-defined properties, but you can amend them.

To delete a user-defined item:

1.	Ensure no other repository users are using or need to use the user-defined item you want to delete. You can search for instances of the item using the search feature in the Repository Object Navigator.  How

2.	Delete all instances of the user-defined item from the repository. To avoid repository users using it, this may involve temporarily removing their access to the repository.

3.	In the Repository Administration Utility, open the User Extensibility dialog box.  How

4.	Expand ELEMENT TYPES, ASSOCIATION TYPES or TEXT TYPES as appropriate.

5.	Expand User Defined to see the appropriate object type (or System Defined to delete a user-defined property or text type usage for a system-defined object type).

6.	(Optional)  To delete a text type usage, expand the object type then Extended Text Usages.

7.	Select the object type or text type usage.

8.	(Optional)  Revoke publication of the object type or text type usage.  How

9.	Select the unpublished object type or text type usage.

10.	Click Delete.

11.	Reply OK to the message to confirm your action.


Importing user-defined items

Related Topics

You can import user-defined object types, properties and text type usages. You may have previously exported this data to a dump file from this or another repository.

The import process creates log files named CK_UE_LD.LIS and dumpfile_name.IMP. To find the location of CK_UE_LD.LIS, see LOG_DIRECTORY_RAU under Parameter Settings in the Check Requirements Utility.  How

The file dumpfile_name.IMP is stored in the same directory as the dump file from which you import the repository data.

The CK_UE_LD.LIS log file contains details of the user-defined items imported. This may be useful for recovery purposes. The .IMP log file contains details of the import process and may be useful if the process fails.

To import user-defined items:

1.	In the Repository Administration Utility, click Load User Extensions to open the Open dialog box.

2.	Select the dump file containing the repository data you want to import.

3.	Click Open. You can control the import process while it is in progress.  How

Note:	A list of the user-defined items to import displays. This will be the output log file CK_UE_LD.LIS.

4.	Close the window containing details of CK_UE_LD.LIS.

5.	Do one or more of the following for the messages that may now display:

Message	Action
Do you want to delete the output?	Reply No (creates the output file CK_UE_LD.LIS).
Do you wish to proceed with the loading of User Extension meta data?	Reply Yes.
Before proceeding please check the following log files for errors...	1. Record the name and location of the files. 2. Check the files and correct any errors. 3. Click OK.
Do you wish to proceed with the loading of User Extension meta data?	Reply Yes.
Operation Complete	Click OK.


Exporting user-defined items

Related Topics

You can extract all the user-defined object types, properties and text type usages from the repository to a dump file. You can then import this data into the same or a different repository.

The export process creates log files named CK_UE_EX.LIS and dumpfile_name.EXP. To find the location of CK_UE_EX.LIS, see LOG_DIRECTORY_RAU under Parameter Settings in the Check Requirements Utility.  How

The file dumpfile_name.EXP is stored in the same directory as the dump file.

The CK_UE_EX.LIS log file contains details of the user-defined items exported. This may be useful for recovery purposes. The .EXP log file contains details of the export process and may be useful if the process fails.

To export user-defined items:

1.	In the Repository Administration Utility, click Extract User Extensions to open the Save As dialog box.

2.	Specify the name and location of the dump file that should contain the user-defined items. If necessary, record the file name and location to help you find it if you need to import the user-defined items later.

3.	Click Save. You can control the export process while it is in progress.  How

Note:	A list of the user-defined items now held in the repository extract tables displays. The export process has yet to write this data to the dump file.

4.	Close the window containing the list.

5.	Do one or more of the following for the messages that may now display:

Message	Action
Do you want to delete the output?	Reply No (creates the output file CK_UE_EX.LIS).
Operation Complete	Click OK.
Note:	To help avoid losing any user-defined item data permanently, check that the dump file exists.


About the broadcast service

Related Topics

The broadcast service is a feature that notifies repository users immediately of changes made to repository elements in other tools or by other users. If a user changes a repository element, e.g. a table definition, the broadcast service displays a [image] symbol against the change. Any user can then use the requery feature to see the change.

You can configure the broadcast service to run on individual client workstations only or on a network using the broadcast server. This involves setting the broadcast options available in other Oracle tools, e.g. the Repository Object Navigator. Users can also enable or disable the broadcast service as appropriate using these broadcast options:

Option	Description
Disabled	Broadcast service is turned off. The user’s workstation cannot receive or send details of changes to repository elements.
Desktop Only	Broadcast service runs on an individual client workstation only and starts when a user starts an Oracle tool. Any changes to repository elements are broadcast to that workstation only.
Network	Broadcast service runs on a network using the broadcast server. This can run on the default client workstation, another workstation or another machine, e.g. the database server.
Note:	You can only configure the broadcast server to work on Intel Win32 Windows NT machines and TCP/IP networks. The default client workstation is the one that runs the Repository Administration Utility.

Configuring the broadcast service


Configuring the broadcast service

Related Topics

You can configure the broadcast service to run on individual client workstations only or on a network using the broadcast server.

To configure a broadcast service for a client workstation:

1.	Set the Desktop Only broadcast option for the workstation.  How

2.	Test the broadcast service.  How

To configure the broadcast service for a network:

1.	Install the broadcast server files.  How

2.	Specify the broadcast server host.  How

3.	Set the Network broadcast option on every client workstation.  How

4.	Run the broadcast server.  How

5.	Test the broadcast service.  How


Installing the broadcast server files

Related Topics

Appropriate client-side installation processes copy to a client workstation the files needed to run the broadcast server on that client.

To run the broadcast server on another machine on a network (e.g. another workstation or the database server), you must first install the broadcast server files onto that machine.

Note:	The broadcast server only works on Intel Win32 Windows NT machines and on TCP/IP networks. For a network, you must also install Net8 and the Oracle TCP/IP protocol adapter onto the same machine.

To install broadcast server files:

1.	Insert the product CD in the CD-ROM drive. If the Oracle Installer does not start immediately:

a.	Select Start→Run.

b.	Enter d:\SETUP.EXE, where d is the CD-ROM drive, then click OK.

2.	Click OK for each dialog box until the Package Installation Settings dialog box appears.

3.	Select Broadcast Server (NT only), then click OK.

Note:	If you do not want to install any other tools, e.g. Oracle Repository Tools and API, deselect the other check boxes.

4.	Click OK for each subsequent dialog box to start the installation.


Specifying the broadcast server host

Related Topics

The machine that runs the broadcast server is the broadcast server host. By default, this is the same client workstation that runs the Repository Administration Utility. However, you can run it on another workstation or machine on a network.

To specify the broadcast server host:

1.	In the Repository Administration Utility, choose Tools→Configure Broadcast Server.

2.	(Optional)  To run the broadcast server on a different machine from the client workstation running the Repository Administration Utility, clear Local Server Host.

3.	In the Server Host field, type the name of the machine you want to use on the network. The default port number for this machine displays in the Server Port field.

4.	(Optional)  In the Server Port field, type the new port number.

Note:	Normally, you only need to change the default port number if you want to use the broadcast server feature for more than one repository on one host machine. In this case, you specify one broadcast server with a unique port number for each repository.


Running the broadcast server

Related Topics

You can start or stop the broadcast server using a console-mode application, CKRN61. When you run CKRN61, it performs one operation, e.g. run it once to start the broadcast server, then run CKRN61 again to stop it.

Note:	This means you have to start a new Command Prompt every time you run CKRN61.

You can also run CKRN61 in batch mode, e.g. starting or stopping the broadcast server in scripts that also control your database and TNS Listener.

Note:	The broadcast server only works on Intel Win32 Windows NT machines and on TCP/IP networks. For a network, you must also install Net8 and the Oracle TCP/IP protocol adapter onto the same machine.

To start the broadcast server:

1.	Specify a machine as the broadcast server host.  How

Note:	You can only start the broadcast server on the server host.

2.	Start the Windows NT Command Prompt and run the following command:

d:\oracle_home\BIN\CKRN61 username/password@alias start

Note:	username, password and alias specify a connection to the database on which you want to run the server. Only start the broadcast server after starting the database and TNS Listener.

You can enter a parameter after the start command to specify how many applications will use the broadcast server, e.g. start 123. The parameter has no upper limit, but other factors may affect the number the broadcast server can support, e.g. server host memory.

To stop the broadcast server:

•	Start a Windows NT Command Prompt and run the following command:

d:\oracle_home\BIN\CKRN61 username/password@alias stop

Note:	You can stop the broadcast server from any network machine.


Testing the broadcast service

Related Topics

You can test the broadcast service for an individual client workstation or for a network.

To test the broadcast service:

1.	Run the broadcast server.  How

2.	In an Oracle tool, e.g. the Repository Object Navigator, ensure that the broadcast option is set to Desktop Only or Network as appropriate.

3.	In a different tool, e.g. Design Editor, change an element property (e.g. a table name).

Note:	If you are testing the broadcast service on a network, change an object property on another client workstation.

4.	In the first tool, e.g. the Repository Object Navigator, a [image] symbol should appear against the object name.

Note:	The [image] symbol only appears if you are already viewing the element, e.g. if you expand a node to see the element, up to date details display automatically. To remove the symbol, requery the element against the repository.  How


About National Language Support (NLS)

Related Topics

National Language Support (NLS) enables you to change the language in which users see some text stored in the repository. On NLS versions of Oracle Repository, you can change this display language for the following text (for the display languages that Oracle Repository supports):

•	datatype values

•	element type names

•	property names

•	text type descriptions

•	report group names

•	report parameters

•	report title names

If you also use Oracle Designer Generator tools, you can change the display language for Generator preference descriptions and their valid value meanings.

Note:	The display language only applies to the repository to which you are connected. To change the display language for another repository, you must first connect to it.

If you change the display language, when a user next views the text, e.g. using the Repository Object Navigator, it displays in that language.  How

The oracle_home\REPADM61\NLS directory contains the translated text files for the display languages that Oracle Repository supports. To use a display language, you may need to load the translated text files first.  How


NLS Load Summary dialog box

Related Topics

Enables you to view details of the translated text files loaded into the repository for a display language that Oracle Repository supports. It displays the number of words loaded for each type of translated text, which you select in the NLS Translation dialog box.  About

Dialog box options

Translated Text Property - Essentials

The translated text you must load to be able to use the display language.

Translated Text Property - Optionals

The translated text you can also load and use in the specified display language for Oracle Designer Generator tools.

Estimated Num.

The estimated number of words in the repository for that type of text. These words are stored in US English, the default display language.

<Language>

The number of translated words loaded for that type of text. These words correspond to the words stored in the repository in the default display language.

Note:	When a file load is complete, this number equals Estimated Num.

Missing

The number of words in the repository for which there was no translation in the text file.

View Log

Displays the log file for the last load of that translated text file. The log file gives details of the database rows inserted. You can check if a type of text is loaded by clicking on View Log. If the text is not loaded, a message appears stating there is no log file. If a load fails, the log file gives details of the errors that cause it to fail.


Changing the display language

Related Topics

On National Language Support (NLS) versions of Oracle Repository, you can change the language used to display some text stored in the repository, e.g. datatype values, for the display languages that Oracle Repository supports.

To change the display language:

1.	In the Repository Administration Utility, choose Utilities→NLS to open the NLS Translation dialog box.

2.	In the Repository Language group, select the display language you want to use.

Note:	If the display language you want to use is not listed, you must first load its translated text files, providing Oracle Repository supports it.  How

3.	Click Set.

Note:	When a user next views the text, e.g. using the Repository Object Navigator, the data displays in the specified display language.


Loading language text files

Related Topics

To be able to select a display language that Oracle Repository supports, you must first load all its translated text files. In some cases, you may need to reload these files, e.g. if a previous load of translated datatype values failed.

To load a language text file:

1.	In the Repository Administration Utility, choose Utilities→NLS to open the NLS Translation dialog box.

2.	In Language in the Translated Text group, select the display language you want to load.

Note:	The Language field only lists those display languages supported, as stored in the oracle_home\REPADM61\NLS directory.

3.	In the Essentials - Required for Oracle Repository Core group, select which translated text to load. For more information, see the NLS Translation dialog box.

Note:	Each check box corresponds to a translated text file. To use the language as a display language, you must select all the check boxes. To reload any files, select which text to reload as appropriate.

4.	In the Optionals - Required for Oracle Designer Generators group, select which translated text you want to load for any installed Oracle Designer Generator tools.

5.	Click Load. The NLS Load message box displays, giving details of the load process.

When the load process is complete, the NLS Load Summary dialog box displays, giving details of the text loaded. If you reload any text files, you can use it to check that all the other files are loaded.  About

6.	(Optional)  Change the display language to the language loaded.  How


About the Object Status Utility

Related Topics

The purpose of the Object Status Utility is to help you check the status of repository objects and take appropriate action depending on their status. For example, you can check that a repository is installed correctly, edit the storage details of index of tables or rebuild an index.

Using the Object Status Utility helps you to determine what action is necessary. You can check the status and other details of all the objects that make up the repository by object type.

You can then take specific action as appropriate, e.g. computing statistics on indexes and tables to maintain repository performance or recompiling objects for which you have corrected errors.  About

The Object Status Utility contains the following components:

Component	Purpose
Navigator	Lists the types of repository object for which you can check the status, and other details of the objects that exist.  About
Details window	Shows details of the repository objects that exist for the selected type of repository object.  About
Error window	Shows details of any errors that cause the selected repository object to have a status of INVALID.  About


About repository object statuses

Related Topics

The various types of repository object can have the following statuses:

Object type	Object status
	Valid	Invalid	Enabled	Disabled	Missing	Reload
	Constraints
	Functions
	Indexes
	LOBs
	Package bodies
	Packages
	Sequences
	Synonyms
	Tables
	Triggers
	Type bodies
	Types
	Views
Objects must have a status of VALID or ENABLED, depending on their type, for them to work. VALID objects have no errors, e.g. a function that compiles correctly. ENABLED objects are set to execute as necessary, e.g. triggers. DISABLED objects may have no errors, but will not execute.

Note:	For a trigger to work, it must have a status of VALID and ENABLED.

An object is INVALID if it has errors, e.g. a view may be invalid because it refers to a table that does not exist. An object has a status of MISSING if it does not exist, which may occur after installing, migrating or upgrading the repository.

Note:	Installing, migrating or upgrading a repository should ensure all required object types and objects exist, with each object having a status of VALID. If any objects have the status INVALID or MISSING, contact Oracle Support before taking any more action.

Objects with a status of RELOAD are objects marked for recreating in the repository. You can recreate an object and perform other actions depending on its type and status.  About


Working with repository objects

Related Topics

To help manage the repository, you can perform the following actions on some objects depending on their type and status, e.g. computing statistics to improve performance:

Object type	Actions
	Compute Statistics	Quick Edit	Recompile	Rebuild	Mark for Reload
	Constraints
	Functions
	Indexes
	LOBs
	Package bodies
	Packages
	Sequences
	Synonyms
	Tables
	Triggers
	Type bodies
	Types
	Views
Note:	You cannot perform any actions on a type body or type. You can only mark constraints, indexes, LOBs, sequences, synonyms or tables for reloading into the repository if their status is MISSING.

Computing statistics on repository indexes and tables

Editing details of repository indexes and tables

Rebuilding repository indexes

Recompiling repository objects

Reloading repository objects

Removing the reload mark for repository objects


Object Status Utility Details window

Related Topics

Displays details of the repository objects that make up the repository for the selected object type. The total number of objects in the repository for that object type displays in the top left hand corner of the window.

Details of any action you take also appear in the top left hand corner, e.g. Rebuilding index <index name>.

For all repository object types, the Details window displays the:

•	name and status of the repository object  About

•	name of the SQL script that creates the object and the directory that contains it

Note:	If the object has a status of INVALID, details of the errors that make it invalid display in the Error window.  About

For repository indexes and tables, the following details also display:

Item	Description
Tablespace	The name of the tablespace that stores the index or table.
Bytes	The total size, in bytes, of the index or table.
Extents	The number of extents that the index or table already uses.
Initial Extent	The size, in bytes, of the first extent in the index or table.
Next Extent	The size, in bytes, of the next extent to be allocated to the index or table.
Max Extent	The total number of extents, including the first, that can be allocated to the index or table.
% Increase	The amount by which the third and subsequent extents grow in size over the preceding extent, e.g. 50 means each subsequent extent is 50% bigger than the preceding one. 0 means all extents after the first are the same size.
Note:	You can amend details of the index or table extents or move an index to another tablespace, e.g. to enable the size of an index to increase.  How


Object Status Utility Error window

Related Topics

Displays details of the errors that make the selected repository object invalid.

An object is invalid because it has errors, e.g. a view may be invalid because it refers to a table that does not exist. You need to correct all the errors for the object to work. You can then recompile the object to check it is correct and has a status of VALID.  How

The Error window displays the following details about each error:

Item	Description
Line No.	The line of PL/SQL that contains the error.
Position	The position in the line of PL/SQL that the error occurs.
Error text	A description of the error.


Checking the status of repository objects

Related Topics

Managing the repository involves taking action to ensure:

•	all required repository objects exist in the repository and do not have any errors

•	temporary tables do not become too large and fragmented and therefore degrade repository performance

•	users have the necessary roles, grants and synonyms for using the repository  How

The Object Status Utility enables you to determine what action is necessary. You can check the status and other details of all objects that make up the repository by object type.  About

To check the status of repository objects and take appropriate action:

1.	In the Repository Administration Utility, open the Object Status Utility.  How

2.	(Optional)  To find details of all objects in the repository for a specific status, select that status from the Object Status List in the toolbar. The default is to show details of all the objects for the selected object type.  About

3.	(Optional)  In the left-hand Navigator, expand Repository Objects, then expand All Objects to see a list of all the repository object types.

4.	Select the object type for which you want to check details of the objects in the repository. These details display in the right-hand Details window.  About

Note:	To check if temporary tables are fragmented, select Tables, then check the Extents column.  Which tables are temporary tables?

5.	Select a repository object and depending on its type, status and other details do one of the following as appropriate:

•	Truncate the temporary table.  How

•	Compute statistics for a repository index and table.  How

•	Edit details of a repository index and table.  How

•	Rebuild a repository index.  How

•	Recompile the repository object.  How

•	Mark the repository object for reloading into the repository.  How

•	Remove the reload mark from the repository object.  How


Truncating temporary tables

Related Topics

Depending on how your organization uses the repository and its utilities, temporary tables that the repository uses can grow very large and fragmented. You should check them regularly and truncate them to avoid degrading repository performance.

You can check the size of temporary tables using the Object Status Utility.  How

Note:	Truncating temporary tables applies to all temporary tables. You cannot truncate specific tables.

To truncate temporary tables:

1.	In the Repository Administration Utility, open the Select Recreate Option dialog box. How

Note:	Use the Check Requirements Utility to ensure you can truncate the temporary tables, e.g. do you have the required system privileges?  About

2.	Select Truncate Temporary Tables, then click Start.

3.	Reply Yes to the message confirming your action.

Note:	You can control this process while it is in progress. How

4.	Click OK for the message that displays stating the process is complete.


Temporary tables

Related Topics

The temporary tables that the repository uses are:

CDDL_TMP_TBL	CK_TEMPORARY_SET
CDI_DELTAB	CK_TEMP_COPY_EL_IDS
CDI_FUNNET	CK_TEMP_EL_IDS
CDI_MODNET	I$SDD_DELETED_OBJECTS
CDI_TEMP_ASSOC_ELEMENTS	I$SDD_INVALID_OBJECTS
CDI_TEMP_ATOMIC_ELEMENTS	RM$ACTIVITIES
CDI_TEMP_RPT_TABLES	RM$DEFERRED_CHECKS
CDRF_TMP_TBL	RM$DEFERRED_QUERIES
CDRK_TMP_TBL	RM$SESSIONS
CK_CHK_REF_SET	RM$VIOLATIONS
CK_CKDBSZ_DBU_TMP	SDD_DPND_DAR_RESULT
CK_CKDBSZ_KEY_TMP	SDD_DPND_QUERY_IN_WA
CK_CKDBSZ_ODB_TMP	SDD_DPND_QUERY_OUT_OF_REPOS
CK_CKDBSZ_OTB_TMP	SDD_DPND_QUERY_OUT_OF_WA
CK_CKDBSZ_TBI_TMP


Computing statistics on repository indexes and tables

Related Topics

You should compute statistics on the physical storage characteristics and data distribution of repository tables and indexes regularly. The Oracle database server can then use the statistics to choose the most efficient execution plan for SQL statements that access these objects.

You can compute statistics on:

•	selected repository indexes or tables (using the Object Status Utility)

•	all repository tables only (using the Compute Statistics dialog box)

Note:	There is no output when you compute statistics because the Oracle database server uses them to choose execution plans internally.

To compute statistics for selected repository indexes or tables:

1.	In the Repository Administration Utility, open the Object Status Utility and select the repository indexes or tables for which you want to compute statistics.  How

2.	Click the [image] toolbar button.

To compute statistics for all repository tables:

1.	In the Repository Administration Utility, open the Compute Statistics dialog box.  How

2.	(Optional)  Enter the sample size of each repository table to use for computing the statistics, as a percentage of the total table size. The default is 20%.

Note:	The sample size you use depends on your repository data and business activities. For example, if your repository contains many types of elements, consider using a higher sample size to represent the repository contents more accurately and result in more efficient queries. However, computing statistics may take longer if you use a higher sample size or repository table sizes are large.

3.	Click Compute.

Note:	The log file CKCOMPST.LIS lists the tables used. You can find the directory that stores this log file using the Check Requirements Utility.  How


Editing details of tables and indexes
Editing details of indexes and tables

Related Topics

The Object Status Utility enables you to edit details of repository indexes or tables, e.g. the size of the next extent to be allocated. This helps you to ensure that your indexes and tables remain large enough to store your data and to maintain repository performance.

Note:	You can also move repository indexes to another tablespace, e.g. to improve performance or to enable you to increase the size of the index.

To edit details of a repository index or table:

1.	In the Repository Administration Utility, open the Object Status Utility and select the repository index or table you want to edit.  How

2.	Click the [image] toolbar button.

3.	(Optional)  Edit details of the repository index or tablespace, e.g. the total size, in bytes, of all the extents allocated for the table. For more information, see the Quick Edit dialog box.

4.	(Optional)  Select the new tablespace that will contain the repository index.

Note:	If you move an index to another tablespace, you should consider rebuilding the index before using it to ensure the index is valid.  How


Rebuilding repository indexes

Related Topics

Rebuilding an index means recreating it in the repository. This may be necessary if, e.g. the index becomes fragmented or you move it to another tablespace to increase the size of the index or improve repository performance.

To rebuild a repository index:

1.	In the Repository Administration Utility, open the Object Status Utility and select the repository index that you want to rebuild.  How

2.	Choose the [image] toolbar button.


Recompiling repository objects

Related Topics

A repository object may have a status of INVALID because it has errors. For example, a view refers to a table that does not exist. After correcting the errors, you need to recompile the object to check it is now valid.

Note:	You can recompile functions, package bodies, packages, triggers and views.  About

You can recompile selected invalid repository objects using the Object Status Utility or all invalid objects using the Select Recreate Option dialog box.

Note:	Recompiling a selected object may be quicker than recompiling all invalid repository objects or, e.g. installing, migrating or upgrading the repository again.

To recompile a repository object:

1.	In the Repository Administration Utility, open the Object Status Utility and select the repository objects you want to recompile.  How

2.	Click the [image] toolbar button.

3.	Check the recompile is successful and the object now has the status VALID.

To recompile all invalid objects in the repository:

1.	In the Repository Administration Utility, open the Select Recreate Option dialog box.  How

Note:	Use the Check Requirements Utility to ensure you can recompile the repository objects, e.g. do you have the required system privileges?  About

2.	Click Recompile Objects, then click Start. You can control this process while it is in progress.  How

3.	(Optional)  When this process ends, check if there are still invalid objects in the repository to ensure all objects recompiled successfully.  How

4.	Use the Object Status Utility to check the recompile is successful and that all objects now have the status VALID, e.g. recompiling one object may cause other objects to be invalid. If necessary, repeat steps one to four.


Reloading repository objects

Related Topics

Reloading a repository object recreates it in the repository. This may be necessary if, e.g. the object is still invalid after recompiling it. You also need to reload objects that have a status of MISSING, e.g. you delete it by mistake or the object is not installed, migrated or upgraded correctly.  About

You can reload any object type except type bodies or types. You can only reload constraints, indexes, LOBs, sequences, synonyms or tables if their status is MISSING.

Installing, migrating or upgrading a repository should create all the required repository objects, with a status of VALID.

Warning:	If any repository objects have the status MISSING, contact Oracle Support before taking any more action.

To reload a repository object, first use the Object Status Utility to mark it and any other objects for reloading as appropriate. You can remove this mark if necessary. You can then reload the object immediately or later using the Select Recreate Options dialog box.

To reload a repository object immediately:

1.	In the Repository Administration Utility, open the Object Status Utility and select the repository object you want to reload.  How

2.	Choose Object→Mark for Reload.

Note:	You can remove this mark if necessary.  How

3.	Close the Object Status Utility.

4.	Reply Yes to the message which asks if you want to reload all repository objects marked for reload now or later.

Note:	You can control this process while it is in progress.  How

To reload all repository objects marked for reload later:

1.	In the Repository Administration Utility, open the Select Recreate Option dialog box.  How

Note:	Use the Check Requirements Utility to ensure you can reload the repository objects, e.g. do you have the required system privileges?  About

2.	Choose Reload Flagged Objects, then click Start.

3.	(Optional)  Specify the index and table tablespaces used to store each category of repository data.  About

4.	Reply Yes to the message to confirm your action.

Note:	You can control this process while it is in progress.  How


Removing the reload mark from repository objects

Related Topics

To reload a repository object, you first mark it for reloading using the Object Status Utility. You can then reload the object immediately, or later using the Select Recreate Options dialog box. You can then remove this mark, e.g. you mark an object for reload by mistake, providing you have not already started the reload.  About

To remove the reload mark for a repository object:

1.	In the Repository Administration Utility, open the Object Status Utility and select the repository object that you do not want to reload.  How

2.	Choose Object→Unmark for Reload.


Requerying repository objects

Related Topics

The repository object details that display in the Details window of the Object Status Utility may become out of date with the repository. This can occur if you work in a multi-user environment, e.g. as you view details of your repository indexes, your Oracle database administrator moves one to another tablespace.

The requery feature enables you to ensure that the Object Status Utility displays the latest object details stored in the repository.

To requery all repository object details for all object types:

•	In the Object Status Utility Navigator, expand Repository Objects, then select All Objects.

Note:	Depending on the size of your repository, requerying all object details may take some time.

To requery repository object details for a specific object type:

•	Choose Edit→Requery

Note:	If you select an object type in the Navigator or take action on a repository object, the Object Status Utility requeries the object details for that type automatically.


Repository Installation Options dialog box

Related Topics

Enables you to select which server side components to install for this release to support other products.  How

Dialog box options

Support for Repository (Core) objects

Installs a repository that supports the core repository element types (files and folders). This is all you need to use the repository for source control purposes only.

Note:	This check box is always checked.

Support for Oracle Designer Objects

Installs a repository that will support Oracle Designer. If you do not select this check box, you will not be able to use Oracle Designer with the repository.

Note:	This check box is checked by default if you have already installed Oracle Designer on the client workstation. If not, you can install the repository first and install Oracle Designer later.


Install a Repository instance dialog box

Related Topics

Enables you to select the tablespaces to use for repository indexes and tables when you install a new repository, migrate or upgrade an existing repository or reload repository objects. If you are installing a repository, you can also select the repository size, which determines the size of these tablespaces.

Note:	Depending on which action this dialog box displays for, some fields are dimmed, e.g. you do not specify a rollback segment when you install a repository.  About

If you are installing a repository, you must first create tablespaces to store each category of repository data, then select them in this dialog box.  How

Note:	If you migrate or upgrade an existing repository or reload repository objects, this dialog box displays the same values specified when you installed the repository for this release. You should not normally need to change these defaults.

Dialog box options

Index Tablespaces

The index tablespaces used to store each category of repository data.  About

Note:	You must use a temporary data tablespace of the type PERMANENT because the repository uses it for creating temporary tables.

Table Tablespaces

The table tablespaces used to store each category of repository data.  About

Note:	You must use a temporary data tablespace of the type PERMANENT because the repository uses it for creating temporary tables.

Repository Size

The default size of the repository you install. The default is Small. The value you select depends on your business activities, e.g. do you need to migrate existing repository data? Depending on which size you select, the index and table tablespace used for each category of repository data has a different default size. For a list of these default tablespace sizes, see the Installation Guide for this release.

Note:	This list box is only available if you are installing a repository.

Nominate a Rollback Segment

The non-system rollback segment to use with the migrated (target) or upgraded repository.

Note:	This list box is dimmed if you are installing a repository.

Start

Starts installing, migrating or upgrading the repository or reloading repository objects as appropriate. You can monitor and control this process.  How

Check Requirements

Opens the Check Requirements Utility to enable you to check that the relevant system requirements exist for your actions before you start.  How


Fields available in the Install a Repository instance dialog box

Related Topics

Depending on if you install, migrate or upgrade a repository or reload repository objects, the following fields are available in the Install a Repository instance dialog box.

Field	Install	Migrate	Upgrade	Reload
Index Tablespaces
System Meta-Data
Temporary Data
Constant Growth Instance Data
Rapid Growth Instance Data
Version Data
Dependency Data
Diagram Data
Table Tablespaces
System Meta-Data
Temporary Data
Constant Growth Instance Data
Rapid Growth Instance Data
LOB Data
Version Data
Dependency Data
Diagram Data
Repository Size
Nominate a Rollback Segment
Note:	If you install a repository, you select which tablespaces and repository size to use. For any other action, the dialog box displays the same values specified when you installed the repository for this release. You should not normally need to change these defaults.


Categories of repository data

Related Topics

Category	Notes
System meta data	Data that defines the repository structure. The tablespace for this data remains static, unless you create user-defined items.  About
Temporary data	Data that some utilities use, e.g. Repository Loader. The size of this data can become very large, depending on how often you use the utilities. Truncate the tablespaces that contain this data regularly.  How
Constant growth instance data	Data that grows in size constantly but slowly, e.g. the table that contains repository user and access rights data.
Rapid growth instance data	Data that can grow in size very quickly, e.g. tables that contain repository object definitions.
LOB data	Large object (LOB) data, stored as text or binary files.
Version data	Data relating to repository objects under version control, e.g. an object’s version history.
Dependency data	Data output from the Dependency Analyzer.
Diagram data	Data created in diagramming tools and stored as binary data, e.g. a Matrix Diagram.


Migration Wizard

Related Topics

Enables you to migrate a repository from an earlier product release (the source repository) to a new repository installed for this release (the target repository).  How

Migrating a repository is necessary if the source repository is not compatible with this release. For more information on which repositories you can migrate, see the Installation Guide for this release.

Dialog box options

Source Designer/2000 Repository

Username / Password

The username and password of the repository owner’s or repository user’s account for the repository you want to migrate. The password appears as asterisks.  About

Connect String

The alias of the repository that you want to migrate.

Target Oracle Designer Repository

New Workarea Name

The name of the workarea in the target repository that will contain the migrated repository data.

If you enabled the version control features of this product when installing the target repository, the default workarea name is WA_, followed by the values entered in the Username and Connect String fields. Change this name as appropriate.

If you did not enable the version control features, the default workarea name is GLOBAL_SHARED_WORKAREA. You cannot change this name.

Purge Previous Abort

Clears the repository data that was not copied completely when a migration process fails or is stopped. You can then try migrating the source repository again. In some cases you may need to correct a problem first, e.g. if there is not enough tablespace.

Start Migration

Opens the Choose the Application Systems to Migrate dialog box, which enables you to select which repository data to migrate.  About


Choose the Application Systems to Migrate dialog box

Related Topics

Enables you to select which repository data to migrate from the source repository to the target repository by selecting the application systems containing that data.  About

Note:	You must select at least one application system to migrate.

Dialog box options

Item list

List the application systems in the source repository that you can migrate. This includes the version number of the application system and the repository user who owns it.

Select All

Selects all the application systems for migrating to the target repository.

Clear All

Clears all the application systems selected for migrating.


Application Systems that will be Migrated dialog box

Related Topics

Displays all the application systems to migrate from the source repository to the target repository. This consists of all the application systems selected in the Choose the Application Systems to Migrate dialog box and any other application systems that share repository elements with them, including any parent application systems.  About

For example, you choose to migrate the repository data in application system A, which refers to a repository element that application system B owns.

Also, application system C refers to a repository element that application system A owns. This means all the repository data for application systems A, B and C is selected for migrating to the target repository. These application systems display in this dialog box.

The process of checking for references is recursive. For example, if application system D refers to repository elements that application system C owns, the repository data in application system D is also selected for migrating. This continues until the application system selected does not have any references, e.g. application system D:

•	only refers to repository elements in application systems A, B or C

•	does not own any repository elements that other application systems refer to

If an application system selected for migrating has a parent application system, the parent is also selected for migrating. However, if a parent is selected for migrating, its child application systems are not migrated. Parent application systems do not contain repository data, so they cannot refer to elements that other application systems own.

Note:	If you do not want to migrate this repository data, click Cancel to close the dialog box and start the migration process again using the Migration Wizard.  About

Dialog box options

Item list

Lists the application systems in the source repository to migrate. This includes the version number of the application system.

OK

Starts migrating the source repository or data into the target repository.

Note:	You can monitor and control this process.  How


Installing a repository

Related Topics

To record all the meta data of your enterprise, e.g. for modeling purposes, you need to install a new repository onto a database. If you have a repository from an earlier release of this product, you can migrate or upgrade it to this new repository as appropriate.

Important - before you start

Before you install a repository, be sure of how you intend to use this repository, for example:

Feature	Description
Synonyms	How many users will use the repository?  Should you give users access to the repository using public synonyms or private synonyms?  About
Version control	Do you need to use the version control features available for the repository data, e.g. for configuration management purposes?  About
Note:	If you use the version control features, you must give repository users the required repository privileges to use them, e.g. to manage workareas.  About

To install a repository:

1.	Ensure you understand how you intend to use the repository.

Caution:	Do not install the repository until you are sure how you will give users access to it and whether you need to use the version control features available.

2.	Follow the instructions in the Installation Guide to install the repository.

Note:	The Installation Guide gives detailed information on how to install a repository for this release, e.g. creating the required tablespaces. You must follow these instructions to install a repository.

3.	(Optional)  After installing the repository, select if you want to enable version control for this repository and its data.

Caution:	You cannot undo this operation.


Migrating a repository

Related Topics

If you have a repository from Release 2.1.2 or Release 6.0 of this product (the source repository), you can migrate the repository data in it (applications systems) to a new one installed for this release (the target repository).

Both the repository owner and repository users can connect to the source repository and migrate it to the target as follows:

Source repository (connected as)	Can migrate to	Target repository (connected as)
Repository owner	→	Repository owner
Repository owner	→	Repository user
Repository user	→	Repository owner
Repository user	→	Repository user
If the original owner of a migrated application system:

•	exists in the target repository, they remain as the owner. If you used a different account to migrate it, that account has the SELECT access right on the application system, and any other access rights previously defined for that user.  About

•	does not exist in the target repository, the account used to migrate it becomes the owner. They have at least SELECT and ADMINISTRATE access rights, plus any other access rights previously defined for that user.  About

Note:	Only your Oracle database administrator (DBA) can create accounts and assign privileges on the source and target repositories.

You can migrate:

•	the whole repository (by selecting to migrate all the application systems)  About

•	specific repository data only by migrating selected application systems  About

•	to a repository regardless of whether it supports version control  About

Important - before you start

If your repository is from an earlier release of this product than Release 2.1.2, you must upgrade it to Release 6.0 before migrating to this release.

If a user starts to migrate a source repository or a migration crashes, other users cannot log in using the same user account and migrate to its target repository at the same time. If a user tries to use the same account, a message displays stating the migration is locked.

Note:	This applies to both the repository owner’s account and repository user accounts.

This is because if more than one user tries to migrate a source repository to the same account, this will corrupt repository data. Therefore, first check no one else is currently migrating to the account you want to use. To continue migrating, click OK.

Caution:	Only continue if you are sure the migration crashed or another user is not currently migrating using the same account you want to use.

If more than one user logs in to a source repository using the same account and starts a migration, this will also corrupt the repository data.

If you are unsure about what action to take, contact Oracle Support for more advice.

We strongly recommend that you ‘clean up’ the source repository before migrating it, e.g. deleting obsolete users or unused application systems. This reduces the time it takes to migrate the source repository.

Note:	The migration process also runs the Repository Analyzer to, e.g. perform referential integrity checks on the repository data and remove any obsolete data.

If you already tried to migrate the source repository but stopped it, you should also purge any repository data that was not copied completely. In some cases you may need to correct a problem first, e.g. if there is not enough tablespace.  About

Caution:	Before migrating the source repository, be sure about how you intend to use the new target repository installed for this release, e.g. will you use the version control features available?  About

You should also use the Object Status Utility to check for missing, invalid and disabled objects in the source and target repository. Before you start migrating, you should:

•	correct any errors  How

•	back up any user-defined items.

Caution:	The migration process does not include user-defined items, so you must import them into the target repository before you start migrating.  How

To migrate a repository:

•	Follow the instructions in the Installation Guide to migrate the repository or specific repository data.

Note:	The Installation Guide gives detailed information on how to migrate a repository, e.g. creating rollback segments. You must follow these instructions to migrate a repository.


Upgrading a repository

Related Topics

Important - before you start

Caution:	Before upgrading the repository, be sure about how you intend to use the new repository installed for this release, e.g. will you use the version control features available?  About

You should also use the Object Status Utility to check for missing, invalid and disabled objects. Before you start the upgrade, you should correct any errors.  How

Caution:	If you stop the upgrade of a repository before it is complete, you may not be able to restart it.  About

To upgrade a repository:

•	Follow the instructions in the Installation Guide to upgrade the repository.

Note:	The Installation Guide gives detailed information on how to upgrade a repository, e.g. creating a rollback segment. You must use follow these instructions to upgrade a repository.


Log files from an installation or upgrade
Log files from an installation, migration or upgrade

Related Topics

Installing, migrating or upgrading a repository creates output log files that give details of different parts of each process. The set of log files created depends on:

•	whether you are installing, migrating or upgrading a repository

•	the products you choose to install or add to a repository that supports or does not support the version control features available

•	whether you are using public or private synonyms

•	the version of Oracle Repository from which you are upgrading

You can find log files in the directory given for the parameter LOG_DIRECTORY_RAU. To check this parameter, use the Check Requirements Utility.  How

Installation and Upgrade log files

Migration log files

Note:	If any of the required log files are missing, the installation, migration or upgrade may be incomplete. In these cases, contact Oracle Support before taking any further action. After installing, migrating or upgrading the repository, check all the log files for any errors.

We recommend you back up log files regularly. If an error occurs during an installation, migration or upgrade and you restart the process, it will overwrite your existing log files. This may make it harder to find the cause of the error.

Installation and Upgrade log files

Log file (.log)	Install	Upgrade	Contains a log of...
CKDES2			importing syscase and RM meta data
CKPREREQ			importing Repository Administration Utility driving data
Log file (.lis)	Install	Upgrade	Contains a log of...
CKALTTB1			amending instance tables before upgrading the instance
CKALTTB2			amending instance tables after upgrading the instance
CKCISYSF			checking in the System Folder for products when adding objects to a repository that uses the available version control features.
CKCOMREP			compiling invalid objects
CKCOMVW			creating common views
CKCONST			creating product specific constraints
CKCRERLE			creating repository roles
CKCRESYN			creating synonyms for user access
CKDEP412			upgrading dependency data
CKDRPAPI			dropping the API
CKDRPCON			dropping constraints
CKDRPIND			dropping indexes
CKDRPSC			dropping syscase and renaming UE reporting meta tables
CKDRPSYN			dropping synonyms
CKGLBWRK			creating the Global Shared Workarea for the repository
CKGRTROL			granting subordinate access to repository roles
CKINDX			creating product specific indexes
CKLDPC			loading the precheck package
CKLDUPG1			loading the upgrade packages for synonyms
CKLDUPG2			loading the upgrade packages (verification)
CKPACCOM			creating common packages
CKPACK			creating product specific packages
CKPRECHK			running the precheck procedure
CKPRIOVW			creating the package resolved meta view on CK_INSTALLED_OBJECTS
CKPOSTUP			post upgrade procedures
CKREPINI			initializing the repository owner’s account and organizing access rights
CKRM409			dropping and renaming Oracle Repository model 4.0.9 tables
CKRM4011			dropping and renaming Oracle Repository model 4.0.11 tables
CKRMTAB			loading RM meta data
CKROLGRT			granting object access to repository roles
CKSEQ			creating product specific sequences
CKSYS412			upgrading the System Folder to Oracle Repository model 4.0.12
CKSYSFOL			creating product specific System Folders
CKTAB411			creating intermediate Oracle Repository model 4.0.11 tables
CKTABS			creating Oracle Designer tables
CKTRIG			creating Oracle Designer triggers
CKTYPE			creating product specific types
CKUDRRES			restoring user defined reports
CKUP4011			upgrading the instance from Oracle Repository model 4.0.9 to 4.0.11.
CKUP4012			upgrading the instance from Oracle Repository model 4.0.11 to 4.0.12.
CKUPGCRC			changing the CRC values on files
CKUPGINI			creating the synonyms for upgrading a repository
CKVERS			updating the dictionary version
CKVIEW			creating product specific views
CKWKC412			compiling all workareas to make new objects in the System Folder visible
JRCON			creating repository constraints
JRFUN			creating repository functions
JRIND			creating repository indexes
JRLOB			creating LOBs
JRODD409			creating product specific odd migration tables
JROPACK			creating registered packages
JRPACK			creating repository packages
JRSEQ			creating repository sequences
JRSYN			creating repository synonyms
JRTAB			creating instance data tables
JRTRIG			creating repository triggers
JRTYPE			creating repository types
JRVIEW			creating repository views
Migration log files

Log file (.log)	Contains a log of...
CMIGREQ	importing Repository Administration Utility driving data
Log file (.lis)	Contains a log of...
CKACCRTS	migrating access rights
CKCOMPST	compute statistics when migrating a full repository (only if you connect to the target repository as the repository owner)
CKCOMREP	compiling the repository (only if you connect to the target repository as the repository owner)
CKFOLMEM	creating folder members
CKMIGCOM	analyzing migration tables
CKMIGDAT	migrating data
CKMIGFUN	creating migration functions
CKMIGIND	creating migration indexes
CKMIGINI	initializing repository objects to migrate (dropping the migration ID mapping table, JR_ID_MAPS)
CKMIGTAB	creating JR_ID_MAPS
CKMIGTYP	updating types in the migration table
CKPOPALG	populating JR_ID_MAPS with application logic
CKPOPELE	populating JR_ID_MAPS with repository elements
CKPOPSDD	populating JR_ID_MAPS with DIAGRAM_SEGS, global names and dependencies
CKPOPSTR	populating JR_ID_MAPS with repository associations
CKPRECOM	analyzing tables in the source repository when migrating a full repository
CKPREMIG	verifying and amending instance data before migrating a full repository
CKPREREC	recompiling packages after running the Repository Analyzer when migrating a full repository
CKPURGE	running the Repository Analyzer before migrating a full repository
CKUPGALT	performing specific upgrade changes to tables
CKUPGCOM	analyzing upgrade tables
CKUPGDRP	dropping upgrade tables
CKUPGEND	verifying and amending specific upgrades
CKUPGIND	creating specific upgrade indexes
CKUPGMCO	performing specific upgrades for reusable module components
CKUPGMOD	performing specific upgrades for modules
CKUPGPAC	loading specific upgrade packages
CKUPGSU	performing summary usages for PL SQL modules
CKUPGTAB	creating specific upgrade tables
CKWKAREA	creating workareas
CKWKCOMP	compiling workareas if the repository uses the available version control features


About public and private synonyms

Related Topics

Depending on how you intend to use a repository and how many users you have, you can give users access to it using public or private synonyms.

Note:	You cannot give a user access to more than one repository at the same time.

Public synonyms enable you to give users repository access using just one set of synonyms, instead of creating one set for each user. For each Oracle instance, you can only have one repository accessed using public synonyms because public database objects must be unique.

Note:	We strongly recommend using public synonyms. Only use private synonyms for a maximum of 10 users. Using public synonyms maintains repository performance, e.g. by reducing the time it takes to complete tasks such as reconciling grants for all repository users.

To use public synonyms, your repository owner’s account must have the required privileges, CREATE PUBLIC SYNONYM and DROP PUBLIC SYNONYM. Only your Oracle database administrator can grant these privileges. They must grant them directly, not as part of a role.  About.

You can check if you have the privileges using the Check Requirements Utility.  About

If you have these privileges, when you install a repository the Repository Administration Utility assumes you will use public synonyms instead of private synonyms. You can switch to private synonyms later if necessary.  How

Any new repository user you add using the User Maintenance dialog box receives repository access immediately using those public synonyms. If you are using private synonyms, you must reconcile the grants for the user to enable to access the repository.

Caution:	We no longer recommend that the repository owner’s account should have the privilege SELECT ANY TABLE if you are installing a repository.

This will give users problems when using this product because their account can see repositories for which they have no access. However, users may need the privilege to use specific repository tools or utilities on a repository.


Changing between public and private synonyms
Changing between public synonyms and private synonyms

Related Topics

You can change between giving users access to a repository using public synonyms or private synonyms at any time. For each Oracle instance, you can only have one repository accessed using public synonyms.  About

Note:	Only new users receive repository access using the type of synonym to which you change. Existing users continue to use the previous synonyms until you delete these synonyms.

To use public synonyms, your repository owner’s account must have the required privileges, CREATE PUBLIC SYNONYM and DROP PUBLIC SYNONYM. You do not need any extra privileges to switch from using public synonyms to private synonyms.

Only your Oracle database administrator can grant these privileges. They must grant them directly and not as part of a role.  About

You can check if you have the privileges using the Check Requirements Utility.  About

Caution:	Switching between public synonyms and private synonyms affects how you maintain repository users.  About

To switch from public synonyms to private synonyms:

1.	In the Repository Administration Utility, choose Options→Enable Private Synonyms. A message displays asking if you want to delete the synonyms previously used.

2.	Click Yes to delete the public synonyms previously used immediately after creating the private synonyms or click No to delete them later.  How

To switch from private synonyms to public synonyms:

1.	In the Repository Administration Utility, choose Options→Enable Public Synonyms. A message displays asking if you want to delete the synonyms previously used.

2.	Click Yes to delete the private synonyms previously used immediately after creating the public synonyms or click No to delete them later.  How

Note:	Deleting private synonyms for more than 30 users may take a long time. If you delete them later, e.g. at the end of the day, repository users can continue to work now.


Deleting the public synonyms used for repository users

Related Topics

If you switch from using public synonyms to give users access to the repository using private synonyms instead, you can delete the public synonyms previously used.  About

To delete public synonyms:

•	In the Repository Administration Utility, choose Options→Drop Public Synonyms.


Deleting the private synonyms used for repository users

Related Topics

If you switch from using private synonyms to give users access to the repository using public synonyms instead, you can delete the private synonyms previously used.  About

To delete private synonyms:

•	In the Repository Administration Utility, choose Options→Drop Private Synonyms.


Select Recreate Option dialog box

Related Topics

The Select Recreate Option dialog box enables you to take action on repository objects, roles, grants and synonyms. This may involve truncating tables and recompiling or reloading objects that had errors or were missing after installing, migrating or upgrading.

Note:	Use the Object Status Utility to determine what action is necessary for repository objects.  About

Dialog box options

Options

Truncate Temporary Tables

Clears the data from the temporary tables used for repository processes. These tables can grow very large and degrade repository performance.  How

Reload Flagged Objects

Recreates in the repository all objects marked for reloading in the Object Status Utility, e.g. an object is missing because you delete it by mistake. You can reload objects immediately in the Object Status Utility, or later using this option.  How

Recompile Objects

Recompiles all repository objects that have a status of INVALID in the Object Status Utility. Invalid objects may have errors or need recompiling to check they are now valid after you correct the errors. You can also recompile objects in the Object Status Utility.  How

Full Reconcile

Organizes the roles, grants and synonyms for all repository users. This is the same as Reconcile, but also grants new user-defined object types to the role ckr_<user> and creates new synonyms for all those object types for all users.  About

You must use Full Reconcile after you publish a new user-defined object type to enable repository users to use it.  About

Caution	If you stop this process before it is complete, users cannot use the repository until you restart the process and complete it.  How

Check Requirements

Opens the Check Requirements Utility, which enables you to check system details and requirements for the action selected in the Options group, e.g. do you have the system privileges required?  About


Compute Statistics dialog box

Related Topics

The Compute Statistics dialog box enables you to compute statistics about the physical storage characteristics of database tables. The Oracle database server can then use these statistics to choose the most efficient execution plan for SQL statements that access analyzed objects.

Enter percentage of table on which to compute statistics

A percentage figure indicating the sample size of each table to use when computing statistics.

Note:	The sample size you use depends on your repository data and business activities. For example, if your repository contains many types of elements, consider using a higher sample size to represent the repository contents more accurately and result in more efficient queries. However, computing statistics may take longer if you use a higher sample size or repository table sizes are large.

Compute

Starts computing statistics. You can control this operation while it is in progress.  How


Control Status dialog box

The Control Status dialog box enables you to control an operation while it is in progress.

Dialog box options

Information about the operation displays in three areas:

Stage Details

The name and description of the current stage of the operation.

Object Details

The type and name of the object currently being processed.

Status Information

The status of the current operation.

Control buttons

Button	Name	Effect
	Start	Restarts an operation that is currently paused.
	Retry	Retries the current stage of the operation.
	Skip	Skips the failed stage of the operation and starts the next one, if any.
	Pause	Pauses an operation, or restarts one that is currently paused.
	Abort	Stops an operation.
Caution:	Only use the Skip Stage option if Oracle Support advises you to.


Error dialog box

This dialog box:

•	indicates the operation during which the error occurred

•	shows the log files that may help you find the cause of the error

•	gives some options for recovery

Dialog box options

An error has occurred whilst:

Indicates the operation, or stage of the operation, during which the error occurred.

Please check logfile(s):

Lists the log files that may help you find the cause of the error.

You can find these log files in the directory specified for the Repository Administration Utility parameter LOG_DIRECTORY_RAU. To check this parameter, use the Check Requirements Utility.  How

Retry Stage

Retries the current stage of the operation during which the error occurred.

Skip Stage

Skips the failed stage of the operation and starts the next one, if any.

Caution:	Only use the Skip Stage option if Oracle Support advises you to.

Abort

Stops the operation at the failed stage.

Note:	Choosing this option may cause problems in using the repository.  About


About the Check Requirements Utility

Related Topics

The Check Requirements Utility enables you to check system details and requirements for installing, migrating, upgrading and using a repository. For example, do you have:

•	the correct version of the import and export utilities used for repository data?

•	the required system privileges to install a repository or to give users access to a repository using public synonyms?

•	a database role that contains the necessary privileges for a repository owner?

•	enough tablespace to migrate a repository?

The Check Requirements Utility contains the following components:

Component	Purpose
Navigator	Enables you to select the following types of information to view in the Details window: • parameter settings  About • privileges  About • database roles  About • tablespaces  About
Details window	Shows details of the selected repository information, e.g. the required system privileges for installing a repository.  How


Parameter Settings

Related Topics

Displays parameter names and their values for Windows Registry keys that the Repository Administration Utility uses.

Each key name has the format HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\key_name:

Registry Key name	Parameter name	Gives the location of (parameter value)
CHELP72	HELP72_RAU	Repository Administration Utility online help
REPADM61	EXECUTE_OBJSTAT	Object Status Utility
	EXECUTE_REPOSPARAM	Check Requirements Utility
	LOG_DIRECTORY_RAU	The directory containing log files from an installation, migration or upgrade
	REPADM61	Files used for repository administration
REPOS61	EXECUTE_EXPORT	Oracle Export Utility
	EXECUTE_IMPORT	Oracle Import Utility
	EXECUTE_PLUS_RAU	Command-line version of SQL*Plus
Note:	You can amend these parameter settings using the Check Requirements Utility or the Windows Registry.  How

Working Directory parameter

The Working Directory parameter is not in the Windows Registry and gives the location of temporary files and output files, e.g. following a back up of the repository.

Note:	You cannot change the working directory.


Privileges

Related Topics

Displays the system privileges, object privileges and database roles defined for the repository owner’s database account you use to connect to the Repository Administration Utility.

Note:	You cannot change privileges and roles in the Repository Administration Utility. Only a user with the appropriate privileges (normally the Oracle database administrator) can change them.

A [image] next to the privilege name means you have that privilege, but [image] means you do not.

Privileges directly granted to user

The system privileges granted to the database account that are not granted through a database role.

Privileges granted for public access

The system privileges granted to enable you to give users access to the repository using public synonyms instead of private synonyms.

Privileges granted to user

All the system privileges granted to the database account, including those granted directly or through a database role.

Required object privileges

The object privileges required for using a repository.

List of required object privileges

Required system privileges

The system privileges required for installing, migrating, upgrading and using a repository.

List of required system privileges

Roles granted to user

The database roles granted to the database account. Each role may contain one or more system privileges.

Note:	To see the privileges granted for a role, expand the node then select the role.


List of system and object privileges
List of required system and object privileges

Related Topics

The system and object privileges a repository owner needs to install, migrate or upgrade and use the repository are:

System privileges

ALTER SESSION

CREATE ANY SYNONYM

CREATE DATABASE LINK

CREATE PROCEDURE

CREATE ROLE

CREATE SEQUENCE

CREATE SESSION

CREATE TABLE

CREATE TRIGGER

CREATE TYPE

CREATE VIEW

DROP ANY SYNONYM

SELECT ANY SYNONYM

Object privileges

EXECUTE ON DBMS_LOCK

EXECUTE ON DBMS_PIPE


Tablespaces

Related Topics

Displays details of the tablespaces in the current database.

Tablespace Name

The name of the tablespace in the database.

Default?

Indicates if this is the repository owner's default tablespace.

Temp?

Indicates if this is the repository owner's temporary tablespace.

Status

Indicates if the tablespace is currently available (ONLINE), e.g. a database administrator may take a tablespace OFFLINE temporarily to correct an error, so users cannot use it.

Initial Extent

The size, in bytes, of the first extent in the tablespace.

Max Extent

The maximum number of extents, including the first, that can be allocated to the tablespace.

Next Extent

The size, in bytes, of the next extent to be allocated to the tablespace.

Largest Extent

The size, in bytes, of the largest possible extent that can be allocated to the tablespace. You can allocate extents of any size up to this limit.

% Increase

The amount that the second and subsequent extents grow in size over the preceding one, e.g. 50 means each subsequent extent is 50% bigger than the preceding one. 0 means all extents after the first are the same size.

Free Space

The size, in bytes, of the free space available for storing data in the tablespace.

User Quota

The size, in bytes, of the tablespace allocated to you. This determines the amount of data that you can store in the tablespace. The value UNLIMITED displays if you can use all the Free Space in the tablespace.

Space Available

The actual size, in bytes, of the tablespace available to you. This is the same as Free Space if the User Quota is UNLIMITED, or the same as User Quota.

Note:	This is the total size of the tablespace that you can use, not the amount of free space remaining after you store data in the tablespace.


Checking system details and requirements

Related Topics

As you work with the repository or before you install, migrate or upgrade one, you can use the Check Requirements Utility to check:

•	parameter settings, e.g. where to find log files from an installation  About

•	the privileges and database roles for the repository owner’s database account  About

•	whether there is enough tablespace, e.g. for installing and using a repository  About

To check system details and requirements:

1.	In the Repository Administration Utility, open the Check Requirements Utility.  How

2.	Do one of the following:

•	To check parameter settings, expand Parameter Settings, then expand the Window Registry key name for which you want to see its parameters.

Select a parameter to see its value.

Note:	You can modify this parameter value.  How

•	To check system privileges, object privileges and privileges necessary for creating public synonyms, expand Privileges, then select which privileges you want to see.

Note:	A [image] means you have that privilege, but [image] means you do not.

•	To check database roles, expand Privileges, then Roles granted to user. A list of all the roles for the repository owner’s database account displays. Select a role to view the privileges granted for it.

•	To check tablespaces, select Tablespaces. A list of tablespace details displays, e.g. the initial extent of the tablespace


Creating an HTML report

Related Topics

The Check Requirements Utility and Object Status Utility enable you to save the information you can view to an HTML file. The HTML file has a report style layout and the information it contains depends on the utility in which you create it:

Utility	Content of HTML file
Check Requirements	All the information available in the Check Requirements Utility, regardless of what currently displays.  About
Object Status	Details of all the repository objects that exist for the selected object type only. These details display in the Details window, e.g. for synonyms, its name, status and PL/SQL that creates it.  About
To create an HTML report in the Check Requirements Utility:

1.	In the Check Requirements Utility, click the [image] button.

2.	Enter the name of the report and select the directory in which you want to save it.

To create an HTML report in the Object Status Utility:

1.	(Optional)  In the Object Status Utility, select the type of repository object for which you want a report of the objects that exist.

2.	Click the [image] button.

3.	Enter the name of the report and select the directory in which you want to save it.


Modifying Repository Administration Utility parameter settings

Related Topics

You can use the Check Requirements Utility to modify the values of parameters for Windows Registry keys that the Repository Administration Utility uses.  About

Note:	You do not normally need to modify the parameter values created when you install Oracle products.

You can also view or edit some parameter settings for any Oracle product using the Registry Editor, e.g. the name of the Oracle home directory or the location of product preference files and help files.

For SQL*Net, parameter settings also determine the driver used for network communications and the values that SQL*Net should use for its operating parameters. For more information on configuration parameters that affect SQL*Net performance, see the SQL*Net documentation.

To modify Repository Administration Utility parameter settings:

1.	In the Repository Administration Utility, open the Check Requirements Utility. How

2.	In the left-hand Navigator, expand Parameter Settings then expand the Window Registry key name for which you want to modify its parameter values.

3.	Select the name of the parameter with the value you want to modify. The parameter value displays in the right-hand Details window.

4.	Select the parameter value, then choose Edit→Modify Variable.


User Maintenance dialog box

Related Topics

The User Maintenance dialog box enables you to add and delete repository users and view details about them.

Note:	The action you take depends on whether you give users access to the repository using private or public synonyms.  About

Dialog box options

Toolbar

	Add	Opens the Repository User Properties dialog box for giving existing Oracle users access to the repository.  How
	Delete	Prevents a repository user from using the repository.  How
	Expand	Expands the selected node.
	Collapse	Collapses the selected node.
	Properties	Displays details about the selected repository user.
Display area

	Roles	A list of the user roles available to assign to users.
	Users	A list of the existing repository users.
Note:	Only a user with the appropriate privileges (normally the Oracle database administrator) can grant roles. The repository owner should have the role CKR_username, which has privileges on all the tables, views and packages belonging to them.

Expanding roles or users displays the following symbols to indicate their status as appropriate:

Symbol	Status	Description
	INSERTED	The name of a new role or user. If you give users access to the repository using private synonyms, you need to reconcile grants for the user.
	VALID	The name of a new role or user. If you give users access to the repository using: • public synonyms, the user has this status immediately after you grant them access • private synonyms, the user has this status only after you reconcile the grants
	DELETED	The name of a deleted role or user. If you give users access to the repository using private synonyms, you still need to reconcile grants for the deleted user.
Expanding the role or user displays the symbol, [image], which lists the workareas, configurations and containers the role or user can access.

Reconcile

Note:	This only applies if you give users access to the repository using private synonyms.

Organizes the private synonyms for the repository user you add or delete. This involves creating or dropping private synonyms for all database objects.

For example, if you add a repository user, use Reconcile to grant the available roles to them. If you delete a repository user, use Reconcile to remove roles from the user.

Note:	If necessary, you can add or delete several repository users before reconciling them. However, they cannot use the repository until you reconcile them.

You can also use Full Reconcile to organize roles, grants and private synonyms.  About


Repository User Properties dialog box

Related Topics

The Repository User Properties dialog box enables you to add a new repository user, or view or edit details of an existing one. This includes which repository privileges they have and the repository tools they can use.

Note:	You can save time by running the SQL script ckupdprv.sql to grant one or more repository privileges for one or more repository users. The script is in <ORACLE_HOME>\REPADM61\UTL. For more information, see the comments in the SQL script.

Dialog box options

Oracle User Name

The name of an Oracle database user. A user must already have an Oracle username before they can be added as a repository user. Only a user with the appropriate privileges (normally the Oracle database administrator) can create Oracle usernames.

Full User Name

(Optional)  The user's real name, if different from their Oracle username (for information purposes only). The default value is the same as the Oracle username.

Date Created

The date the repository user was added (not when the Oracle username was created).

Status

The current status of the repository user.  About

Description

(Optional)  A brief description of the type of access this user should have (for information purposes only). The default value is the same as the Oracle username.

Allow Management Of

Lists the repository features you can enable this user to manage. These are repository privileges.

Workareas

User can create, edit, refresh and delete workareas.

Configurations

User can create, edit, delete and purge configurations.

Containers

User can create, edit, delete and purge containers.

Users

User can create, edit and set these user privileges for other users.

Branch Labels

User can create, edit and delete branch labels for repository object versions.

Dependencies

User can use all the features available in the Dependency Manager. If you do not give a repository user this privilege, they can only use the Dependency Manager in read only mode, e.g. they cannot purge dependency information.  About

Allow User To Perform

Lists the operations you can enable this user to perform on the repository. These are repository privileges.

Registration

Not used in this release.

Set Policy

User can enable or disable repository policies.

Force

User can force delete or purge repository object versions.

Purge

User can purge repository object versions, even if they are checked in.

Global Purge

User can purge any or all versions of an object not owned by a container, e.g. objects in a wastebasket.

Note:	Users can only force delete or purge repository object versions if they have the Delete access right, assigned using the Repository Object Navigator.  About

Allow Connection Via

Lists the repository tools you can enable the user to use to connect to the repository. If a check box is not selected, the user cannot connect to the repository using that tool and therefore, cannot use the tool.


Maintaining repository users

Related Topics

You can use the Repository Administration Utility to manage repository access for existing Oracle users. You can:

Grant repository access to an Oracle user

Revoke repository access

Reconcile the grants for all repository users

Move a user’s access between repositories

Note:	The action you take depends on whether you give users access to the repository using private or public synonyms.  About


Granting repository access to an Oracle user

Related Topics

To create a repository user, you can grant an existing Oracle user access to the repository.

If you intend to move a user’s access from a repository with private synonyms to one with public synonyms, you must

To grant repository access to an Oracle user:

1.	Check that you have the system privileges required to give users access to the repository. You need CREATE ROLE, CREATE ANY SYNONYM and if you use public synonyms to give users repository access, CREATE PUBLIC SYNONYM also.  How

Note:	Only a user with the appropriate privileges (normally the Oracle database administrator) can assign these privileges. They must grant the CREATE ANY SYNONYM and CREATE PUBLIC SYNONYM privileges directly, not as part of a role.  About

2.	Consider which system privileges the repository user will need.  About

Some Repository Object Navigator utilities involve long-running transactions, and therefore enable users to choose a specific rollback segment for the operation. To see the list of online rollback segments, a user needs the DBA privilege SELECT ON DBA_ROLLBACK_SEGS.

Caution:	If an existing Oracle user does not have the system privileges required, contact your Oracle DBA to assign them before taking any more action.

3.	In the Repository Administration Utility, open the User Maintenance dialog box. How

4.	Select Users, then click [image].

5.	In the Repository User Properties dialog box, select the user you want to add from the Oracle User Name list.

6.	(Optional)  Enter other details about this user, e.g. their real name. For more information, see the Repository User Properties dialog box.

7.	Select which repository privileges and tools this user should have for using the repository. For more information, see the Repository User Properties dialog box.

Note:	To save time, you can grant more than one repository privilege for more than one repository user by running the SQL script ckupdprv.sql, stored in <ORACLE_HOME>\REPADM61\UTL. For more information, see the comments in the SQL script.

8.	Click OK to return to the User Maintenance dialog box.

If you currently give users access to the repository using:

•	private synonyms, the new user has the status INSERTED ( [image]). You need to reconcile the grants for the user before they can use the repository.

•	public synonyms, the new user has the status VALID ( [image]) and now has access to the repository using the one set of synonyms defined for all users. Therefore, you do not need to create any synonyms specifically for the user.  About

Note:	You only need to continue with this task if you are using private synonyms.

9.	(Optional)  Click Reconcile.

10.	(Optional)  Click OK at the message reminding you to check that all users have the correct system privileges.

You can control this operation while it is in progress.  How

Note:	Do not stop the reconcile operation before it is complete, otherwise users will not have the synonyms required to access the repository.

If you do not have the repository owner privileges to reconcile grants, a message displays showing the privileges you require. Click Cancel and contact your Oracle DBA to assign you the privileges.


Revoking repository access

Related Topics

You can prevent a repository user from using the repository by revoking their access.

Note:	When you revoke a repository user’s access, the repository owner automatically becomes the owner of all the objects they previously owned.

To revoke a user's repository access:

1.	Check that you have the required system privileges to revoke access to the repository. You need DROP ANY SYNONYM and if you use public synonyms to give users repository access, DROP PUBLIC SYNONYM also.  How

Note:	Only a user with the appropriate privileges (normally the Oracle database administrator) can assign these privileges. They must grant them directly, not as part of a role.  About

2.	In the Repository Administration Utility, open the User Maintenance dialog box.  How

3.	Double-click Users to display the current repository users. Usernames are displayed together with symbols to indicate their status. About

4.	Select the user whose repository access you want to revoke, then click [image].

5.	Click Yes at the message asking you to confirm your action. The user now has the status DELETED ( [image]).

If you are using public synonyms to give repository access to users, you do not need to reconcile grants after deleting them. Public synonyms are one set of synonyms for all users, so there are no synonyms defined specifically for a user.  About

Note:	You only need to continue with this task if you are using private synonyms.

6.	(Optional)  Click Reconcile.

7.	(Optional)  Click OK at the message reminding you to check that all users have the correct system privileges.

You can control this operation while it is in progress.  How

Note:	Do not stop the reconcile operation before it is complete, otherwise users will still have the synonyms required to access the repository.

If you do not have the repository owner privileges to reconcile grants, a message displays showing the privileges you require. Click Cancel and contact your Oracle DBA to assign you the privileges.

When the reconcile is complete, the user no longer displays in the User Maintenance dialog box.


Moving user access between repositories

Related Topics

The action you take to move a user’s access between repositories depending on whether you use private or public synonyms to give access to each repository. If you use public synonyms for a repository, you do not reconcile grants for users.  About

Note:	You cannot give a user access to more than one repository at the same time.

To move a user’s repository access from one repository to another:

1.	Revoke the user’s access to the repository from which you want to move them.  How

2.	(Optional)  Reconcile the grants for the user if you use private synonyms for the repository from which you revoked their access.  How

3.	Grant the user access to the repository to which you want to move them.  How

4.	(Optional)  Reconcile the grants for the user if you use private synonyms for the repository to which you granted them access.  How


Reconciling the grants for all repository users

Related Topics

You need to perform a full reconcile on the grants for all repository users after:

•	registering an Oracle schema in the repository

•	restoring from a full user backup

•	importing data from another repository

•	publishing a user-defined object type

A full reconcile:

•	resolves the ownership of workareas and containers. If the owner is not defined, e.g. due to an error in the date, the repository owner becomes the owner.

•	organizes roles, grants and private synonyms for all repository users. This is similar to using Reconcile in the User Maintenance dialog box, but it also organizes grants and private synonyms for new user-defined object types.  About

Note:	Depending on the number of users, this procedure may take many hours.

To perform a full reconcile:

1.	In the Repository Administration Utility, open the Select Recreate Option dialog box.  How

2.	Click Full Reconcile, then Start. You can control this process while it is in progress.  How

Caution	If you stop this process before it is complete, users cannot use the repository until you restart the process and complete it.


Deleting all objects in the repository

Related Topics

Occasionally you might need to delete all the repository objects belonging to the repository owner. Some examples of situations in which you would need to do so are:

•	prior to installing a new repository, you want to use an existing username for the repository owner but that username has obsolete database objects

•	installation of a new repository did not complete correctly and has to be repeated

•	you want to clear out all the repository objects before restoring from a full user backup

To delete all objects from the repository:

1.	In the Repository Administration Utility, click one of the following as appropriate:

Button	Action
	Deletes all repository objects belonging to the current repository owner.
	Deletes all the database objects belonging to the current repository owner, including all the repository objects.
Warning:	You cannot undo this operation. Do not continue unless you are sure this is what you want to do.

2.	Answer Yes to the message asking you to confirm your action.


Backing up the repository

Related Topics

You can back up the contents of the repository by copying them to a dump file. This may be necessary, for example, for:

•	restoring the repository later

•	data archiving purposes

•	moving the repository to another machine

You can back up repository objects and non-repository objects that belong to the repository owner. Non-repository objects are created outside of the Repository Administration Utility, e.g. tables that Server Generator creates when generating database objects.

Note:	We recommend that you back up your repository regularly.

To back up the contents of the repository:

1.	In the Repository Administration Utility, click on Export to open the Save As dialog box.

2.	Specify the name and location of the dump file that should contain the repository data. By default, dump files have the extension .DMP, but you can give it any name and extension you like.

Note:	We recommend you adopt a naming convention for your dump files to help identify them.

3.	Click Save.

This also creates a log file in the same directory as the dump file. The log file is named dumpfile_name.EXP, where dumpfile_name is the name of the dump file you use.


Restoring the repository from a backup

Related Topics

You can restore the contents of a repository by using the dump file created when you back up the contents of the repository. You must first delete any current contents of the repository.

To restore the repository contents from a backup:

1.	In the Repository Administration Utility, delete all the database objects belonging to the current repository owner. This includes repository objects and non-repository objects, e.g. tables that Server Generator creates when generating database objects.  How

Warning:	You cannot undo deletion of repository objects. Do not continue unless you are sure this is what you want to do.

2.	Answer Yes to the message asking you to confirm your action.

3.	In the Repository Administration Utility, click on Import to open the Open dialog box.

4.	Select the dump file containing the repository data you want to restore.

5.	Click Import.

This also creates a log file in the same directory as the dump file you use to restore the repository. The log file is named dumpfile_name.IMP, where dumpfile_name is the name of the dump file used.

6.	Use Full Reconcile to reconcile grants for all repository users.  How


Maintaining repository performance

Related Topics

Repository performance may depend on the number of concurrent users, the amounts and types of data processed and the transactions that occur.

Note:	Your Oracle database administrator is normally responsible for checking these criteria.

However, there are also several actions that you can take to maintain or improve repository performance:

Editing details of indexes and tables

Checking the size of temporary tables

Computing repository statistics


Dealing with reported errors

Related Topics

If the Repository Administration Utility reports an error during an operation, first check the log files listed in the error message displayed. The log files give a history of the operation up to the error and may show the cause of the error.

If you are backing up or restoring a repository or importing or exporting user-defined items, the log file is in the same directory as the dump file used.

Otherwise, you can find the log files in the directory specified for the Repository Administration Utility parameter LOG_DIRECTORY_RAU. To check this parameter, use the Check Requirements Utility.  How

Note:	Depending on the type of error or its cause, you may need to contact Oracle Support to correct the problem. Oracle Support may ask you to generate a Repository Configuration report. .  How

To deal with a reported error:

•	Depending on the contents of the log file, choose one of the following options on the Control Status dialog box:

Option	Effect
Retry Stage	Retries the stage of the operation during which the error occurred.
Skip Stage	Skips the failed stage of the operation and continues with the next one, if any.
Abort	Stops the operation at the failed stage.
Caution:	Only use the Skip Stage option if Oracle Support advises you to. Stopping an operation may make cause problems in using the repository.  About


Troubleshooting during day-to-day operations

Related Topics

The following information may help you to determine the cause of problems that may occur when using the repository:

Errors when trying to add or remove users

Messages while using the product

Users cannot connect without a connect string

Cannot restart a repository upgrade

Errors reported when exporting a repository

Problems when restoring a repository

Problems with importing LOB data and object type data

Checking for invalid or missing repository objects

Editing details of indexes and tables

Checking the size of temporary tables

Computing repository statistics

Errors when trying to add or remove users

If you try to grant or prevent repository access for users and you do not have the following required system privileges, an error message displays:

Synonyms used	System privileges required
Private and public	CREATE ANY SYNONYM DROP ANY SYNONYM
Public	CREATE PUBLIC SYNONYM DROP PUBLIC SYNONYM
Note:	Only a user with the appropriate privileges (normally the Oracle database administrator) can grant these privileges and they must grant them directly, not as part of a role.  About

You can check if you have the privileges using the Check Requirements Utility.  About

Messages while using the product

When using this product soon after installation, migrating or upgrading a repository, the following message may display:

Message	Possible cause
ORA-04068 existing state of packages has been discarded	An error occurred while attempting to use one of the API packages.  This message is normally accompanied by one of messages ORA-04060 to ORA-04067. Check the appropriate log file and take action for the accompanying ORA message. For more information, refer to the  error messages in the Oracle database documentation. For some messages the recommended action is to recompile the procedure.
Users cannot connect without a connect string

When installing, migrating or upgrading a repository, you can set the LOCAL parameter so users can log on without a connect string. If users have problems connecting to the database, take the following action:

1.	Check that the service name (database alias) is correct as given in the Installation Guide for this release.

2.	Check that the LOCAL parameter is correct using the Windows Registry. This should display under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE) and be the same as the service name (database alias).

3.	Ensure that the following parameters have the correct value (normally set automatically during client-side installation processes):

Parameter	Value
EXECUTE_EXPORT	oracle_home\BIN\EXP.EXE
EXECUTE_IMPORT	oracle_home\BIN\IMP.EXE
EXECUTE_PLUS_RAU	oracle_home\BIN\SQLPLUS.EXE
REPADM61	oracle_home\REPADM61
where oracle_home is the directory in which Oracle products are installed (e.g. C:\ORAWIN95 or C:\ORANT).

To find the parameters, use the Windows Registry or Check Requirements Utility.  How

EXECUTE_EXPORT, EXECUTE_IMPORT and EXECUTE_PLUS_RAU should display under the REPOS61 node. REPADM61 should display under the REPADM61 node.

Cannot restart a repository upgrade

If you stop the upgrade of a repository before it is complete, you may not be able to restart it. This is because the Repository Administration Utility has already recorded the repository version number and assumes that the upgraded repository exists. In these cases, you need to complete the upgrade manually.

To complete the upgrade of a repository:

1.	Reconcile the grants for all repository users.  How

2.	Recompile the repository objects.  How

3.	Compute statistics on the repository tables and indexes.  How

Errors reported when exporting a repository

If you export a repository from an Oracle9i database, the Repository Administration Utility may display the message:

Export may have failed. Please check error log.

On examining the export log file, you may see the error message:

EXP-9I: Exporting questionable statistics

This is simply a warning message and the export has, in fact, terminated successfully, as the last record in the log file indicates. The Oracle9i Export utility attempts to include statistics by default, causing this message to be displayed for each non-SYS table. You can ignore these messages.

Problems when restoring a repository

If you restore a repository from a backup, several warning messages may display on screen and in the log file created. The log file is in the same directory as the dump file you use. The log file is named dumpfile_name.IMP, where dumpfile_name is the name of the dump file used.

The warnings occur because there are unresolved dependencies for the data imported. This means some repository objects may be invalid.

However, these warnings should not cause the import process to fail. After restoring the repository, the Repository Administration Utility recompiles all the repository objects imported automatically to resolve these dependencies. Therefore, you should not need to contact Oracle Support. Instead, you should check:

•	for any errors in the log files

•	if any objects remain invalid or missing using the Object Status Utility  How

You should then run Full Reconcile to reconcile the grants for all repository users.  How

Note:	Before running Full Reconcile, ensure you create all the necessary repository user accounts, otherwise the Full Reconcile process may reassign access rights to the repository owner.

Problems with importing LOB data and object type data

If you restore a repository from a backup, you can only import LOB data if the tablespace name containing the data at the time of exporting exists for the repository to which you want to import. You must also have the necessary quota for that tablespace.  About

You cannot import object types into a schema in the same Oracle instance from which you export them. This is because each object type identifier (OID) must be unique in an Oracle instance. The Oracle Import Utility checks if an OID exists in that Oracle instance for each object type it should import. If the OID exists, it does not import that object type, unless you previously deleted the contents of the repository from which you exported.

For more information about the Oracle Import Utility, see your Oracle Server documentation.

Checking for invalid or missing repository objects

You can avoid some potential problems by checking regularly if any repository objects are invalid. You should also check regularly if any objects that should exist are missing using the Object Status Utility.  How


Generating the repository configuration report
Generating a repository configuration report

Related Topics

Oracle Support may occasionally ask you to generate an SCM Repository Configuration report. This report lists various details from the repository that are of use to Oracle Support when attempting to determine the cause of a problem.

The report contains the following information:

•	installed products

•	general information (e.g. version number, repository owner name etc.)

•	database component versions

•	RAU parameter settings

•	roles and privileges granted to the repository owner

•	missing privileges

•	tablespace information

•	user details

•	object status

•	objects flagged for reload

•	repository patch information

•	database property values (time zone, character set, date format etc.)

•	database initialization parameter settings

To generate a repository configuration report:

•	In the Repository Administration Utility, choose Help→Instrumentation Report.

The report is displayed in a browser window, and is written to the file Oracle_home\REPADM61\LOGS\CKRAUDIA.HTML.


File - Change Connection
   Change Connection (File Menu)

Related Topics

Enables you to specify or change the Oracle database to which the Repository Administration Utility is connected.

Dialog box options

Username

The username of the repository owner on the database to which you want to connect.

Password

The password of the repository owner. The password appears as asterisks.

Connect String

The alias for the database to which you want to connect (remember to specify the alias first in the TNSNAMES.ORA file in your Oracle home directory).


File - Save Results As
   Save Results As (File Menu)

Related Topics

Enables you to save the information you can view in the Check Requirements Utility or Object Status Utility to an HTML file. This option displays the Save As dialog box, in which you specify the file name and where you want to save it.  How

The HTML file has a report style layout and the information it contains depends on the utility in which you create it:

Utility	Content of HTML file
Check Requirements	All the information available in the Check Requirements Utility, regardless of what currently displays.  About
Object Status	Details of all the repository objects that exist for the selected object type only. These details display in the Details window, e.g. for synonyms, its name, status and the name of the PL/SQL script that creates it.  About


File - Exit
Exit (File Menu)

Exits from the tool.


Edit - Modify Variable
Modify Variable (Edit Menu)

Related Topics

Enables you to amend the value of the selected parameter setting for a Windows Registry key that the Repository Administration Utility uses. This option displays the Modify Registry Variable dialog box.

Note:	You can amend the parameter value using the Repository Administration Utility or the Windows Registry.  How


Edit - Requery
 Requery (Edit Menu)

Related Topics

Displays the latest object details stored in the repository in the Object Status Utility Details window.  How


Edit - Select All
Select All (Edit Menu)

Related Topics

Selects all the objects that display in the Object Status Utility Details window.


View - Toolbar
Toolbar (View Menu)

Enables you to view or remove the toolbar.


View - Status Bar
Status Bar (View Menu)

Enables you to view or remove the status bar.


View - List
 List (View Menu)

Enables you to view the name of all the repository objects that exist for the selected object type.


View - Details
 Details (View Menu)

Enables you to view details of all the repository objects that exist for the selected object type.


View - Expand Tree Node
Expand Tree Node (View Menu)

Expands the selected node on the Object Status Utility Navigator to show all nodes below it.


View - Collapse Tree Node
Collapse Tree Node (View Menu)

Collapses the selected node on the Object Status Utility Navigator, including all the levels of nodes below it.


Object - Compute Statistics
 Compute Statistics (Object Menu)

Related Topics

Computes statistics about the physical storage characteristics and data distribution of the selected repository table or index.  How

The Oracle database server can then use the statistics to choose the most efficient execution plan for SQL statements that access these objects.


Object - Quick Edit
 Quick Edit (Object Menu)

Related Topics

Enables you to edit details of the selected index or table, e.g. before you rebuild an index or recreate a table with a status of MISSING.  How

Dialog box options

Object Name

The name of the selected index or table.

Last Analyzed

The date of last computing statistics on the index or table. If you have never computed statistics for this table or index, NOT ANALYZED displays.

Storage

This group gives details about the extents defined for the index or table.

Initial Size

The size, in kilobytes or megabytes, of the first extent of the index or table.

Next Size

The size, in kilobytes or megabytes, of the next extent to be allocated to the index or table.

Increase Size by

The amount by which the third and subsequent extents grow in size over the preceding extent, e.g. 50 means each subsequent extent is 50% bigger than the preceding one. 0 means all extents after the first are the same size.

Maximum Number

The total number of extents, including the first, that can be allocated to the index or table.

Note:	This is the total size of the index or table and is either unlimited or has a defined limit.

Tablespace

The name of the tablespace that stores the index or table.

Note:	This list box is dimmed for tables, but you can move indexes to another tablespace.  How


Object - Recompile
 Recompile (Object Menu)

Related Topics

Enables you to recompile repository objects selected that have a status of VALID or INVALID. You can only recompile certain types of repository object.  About

An object is invalid because it has errors, e.g. a view is invalid because it refers to a table that does not exist. Therefore, before you recompile the object, correct any errors that make it invalid.


Object - Rebuild
 Rebuild (Object Menu)

Related Topics

Enables you to rebuild selected indexes. You cannot rebuild any other type of repository object.  About

Rebuilding an index may be necessary if, e.g. you move it to another tablespace to increase its size or improve repository performance.  How


Object - Mark for Reload
Mark for Reload (Object Menu)

Related Topics

Enables you to mark selected objects for reloading into the repository. You can only reload certain types of repository object.  About

Reloading a repository object recreates it in the repository. This is normally only necessary if the object has a status of MISSING after a installing, migrating or upgrading a repository.

Note:	Installing, migrating or upgrading a repository should create all the required repository object types and objects, with each object having a status of VALID. Therefore, you should not need to reload objects unless Oracle customer support asks you to.


Object - Unmark for Reload
Unmark for Reload (Object Menu)

Related Topics

Enables you to not reload repository objects already selected for reloading into the repository. This only applies to certain types of repository object.  About

Note:	You should not need to mark any repository objects for reloading unless Oracle customer support asks you to.  About


Utilities - Load User Defined Reporting Meta Data
Load User Defined Reporting Meta Data (Utilities Menu)

Loads user defined report definitions into the repository.

When you migrate or upgrade a repository, you can choose to load any user defined reports automatically or later as appropriate. If you defer loading, you can use this option at any time.


Utilities - NLS
NLS (Utilities Menu)

Related Topics

Enables you to change the language used to display some text stored in the repository, e.g. property names. This option opens the NLS Translation dialog box, in which you can select a display language and load language text files.

Note:	This option is available only on National Language Support (NLS) versions of Oracle Repository.

Dialog box options

This group defines the current display language used to display the text.

Repository Language

Language

The display language you want to use. If the display language you want is not listed, you must first load its translated text files using the Translated Text group.

Set

Changes the current display language to the one selected in Language. When a user next views the text, e.g. using the Repository Object Navigator, it displays in that language.

Translated Text

This group defines the display languages and translated text you can use.

Language

The language for which you want to load translated text files.

Note:	The languages listed are the only ones that Oracle Repository supports.

Directory

The location of the translated text files, normally oracle_home\REPADM61\NLS.

Essentials - Required for Oracle Repository Core

This group defines which text displays in the specified display language, e.g. datatype values. When you select a language, every check box is selected by default and each one corresponds to a translated text file in oracle_home\REPADM61\NLS.

To be able to select the language you load as the display language in the Repository Language group, you must load all the translated text files. You can reload the files at any time by selecting the text to reload. Use the Check All or Uncheck All buttons to select or clear the check boxes as necessary.

Optionals - Required for Oracle Designer Generators

This group defines which text you want to display in the specified display language for Oracle Designer Generator tools, e.g. Generator preference descriptions. Each check box corresponds to a translated text file in oracle_home\REPADM61\NLS. If there is no corresponding text file, the check box is dimmed.

You can reload the files at any time by selecting the text to reload. Use the Check All or Uncheck All buttons to check or clear the check boxes as necessary.

Load

Loads the translated text files for the selected text in the Essentials - Required for Oracle Repository Core or Optionals - Required for Oracle Designer Generator groups.

Check Current Status

Opens the NLS Load Summary dialog box, which enables you view details of the loaded translated text.  About


Tools - Configure Broadcast Server
Configure Broadcast Server (Tools Menu)

Related Topics

Enables you to specify the machine that should run the broadcast server. This is the broadcast server host and must be the machine on which you installed the broadcast server files.

Note:	The broadcast server host can be the same client workstation that runs the Repository Administration Utility or another workstation or machine on a network.  About

Dialog box options

Local Server Host

Indicates if the broadcast server will run on the same client workstation as the Repository Administration Utility. If not checked, you can specify another host machine.

Server Host

The name of the host machine that should run the broadcast server on a network.

Server Port

The default port number of the host machine, for example ukp14601 or 138.3.22.24.

Normally, you only need to change the default port number if you want to use the broadcast server feature for more than one repository on one host machine. In this case, you specify one broadcast server with a unique port number for each repository.


Tools - SQL*Plus
   SQL*Plus (Tools Menu)

Opens a SQL*Plus window.


Options - Diagnostics
Diagnostics (Options Menu)

Allows you to set diagnostic file and trace settings. This feature should not be used unless requested to do so by your Oracle customer support representative. If you inadvertently set any of the diagnostic options you may find that the tool's performance is affected. If you do find any degradation in performance, click the Disable Option button to switch off the diagnostics facility.


Options - Enable Version Support
Enable Version Support (Options Menu)

Related Topics

Enables you to use the version control features (e.g. check in, check out and merge) available with this product, e.g. for configuration management purposes.

Caution:	You cannot undo this operation. Before enabling the version control features, ensure this is really necessary for this repository and its data.

By default, the installed repository contains one shared workarea called the GLOBAL SHARED WORKAREA. This workarea does not support any of these version control features.  About

When you install a repository, the repository owner’s account receives limited repository privileges and access rights to prevent them using the version control features. If you enable the version control features, the repository owner’s account receives the required extra privileges and access rights below.

Note:	Repository privileges display in the Repository User Properties dialog box.  About

	Non-versioned repository	Versioned repository
Privilege
Allow Management Of
Workareas
Configurations
Containers
Users
Branch Labels
Dependencies
Allow User To Perform
Set Policy
Force
Purge
Global Purge
Allow Connection via
Repository Object Navigator
Matrix Diagrammer
Reporting Tool
Command Line Interface
Version History Viewer
Version Event Viewer
Access rights
Delete
Administrate
Insert
Select
Update
Version
Compile
Update Spec
Note:	You cannot change the repository privileges and access rights given to the repository owner.

When you grant repository access, you can give users any combination of the same privileges and access rights that the repository owner receives as appropriate, except for:

Repository type	Privilege not allowed for user
Non-versioned repository	Allow Management Of Users Allow User to Perform Set Policy
Granting repository access to an Oracle user

Granting repository access rights

For more information about using the version control features available for configuration management purposes, see the Oracle Repository Configuration Management Overview for this release.


Options - Edit Policies
Edit Policies (Options Menu)

Related Topics

Allows you to set defaults for any or all of the repository-wide policies for:

•	Version control

•	File system files

•	Object dependencies

Versioning

Automatic branching

When selected, objects are checked in to the default branch for the workarea.

Automatic version labeling

When selected, each new object version is automatically assigned a version label on checkin.

Strict locking

When selected, prevents any version of an object being checked out from a branch when one version is already checked out on that branch.

Names of files and folders

Case sensitive uniqueness checking

When selected, activates case sensitivity checking for the names of new file system files and their containers when these are created in the repository.

Dependencies

The following options control the default setting for what happens to dependencies for certain operations on repository objects. In either case the default can be overridden at the time of the operation.

Copy on versioning

When selected, causes object dependencies to be copied by default when a new version of an object is created.

Copy on copying

When selected, causes object dependencies to be copied by default when an object is copied.


Options - Enable Public/Private Synonyms
Enable Public/Private Synonyms (Options Menu)

Related Topics

Enables you to give users access to the repository using private synonyms or public synonyms as appropriate. You can select to use public synonyms or private synonyms when installing the repository or later as necessary.  About

We strongly recommend using public synonyms. Only use private synonyms for a maximum of 10 users. Using public synonyms maintains repository performance, e.g. by reducing the time it takes to complete tasks such as reconciling grants for all repository users.

Note:	For each Oracle instance, you can only have one repository accessed using public synonyms. Public and private synonyms also affect how you maintain users.  About

To use public synonyms, your repository owner’s account must have the required privileges, CREATE PUBLIC SYNONYM and DROP PUBLIC SYNONYM. Only a user with the appropriate privileges (normally the Oracle database administrator) can grant these privileges. They must grant them directly, not as part of a role.  About

You can check if you have the privileges using the Check Requirements Utility.  About

If you have these privileges, when you install a repository the Repository Administration Utility assumes you will use public synonyms instead of private synonyms. You can switch to private synonyms later if necessary.


Options - Drop Public/Private Synonyms
Drop Public/Private Synonyms (Options Menu)

Related Topics

Enables you to delete the public or private synonyms previously used to give users access to the repository as appropriate. This option only applies if you change between using public or private synonyms to give users access to the repository using the other.

For example, if you use private synonyms, but then choose to use public synonyms, the private synonyms previously used still exist for each user.

Note:	This option is dimmed if, after you change between public and private synonyms, no users still have the type of synonym previously used.


Options - Enable Performance Enhancements
Enable Performance Enhancements (Options Menu)

This action is irreversible.

Choosing this menu item will install performance enhancements to the repository.

This menu is enabled only when the requirements for performance enhancements are met and when the performance enhancements are not already installed.

The requirements for performance enhancements are:

- RLS (row level security) is enabled in the database, and

- the repository owner ("repos owner") has execute permissions on DBMS_RLS.


Object Status List
Object Status List (Toolbar)

Related Topics

Enables you to view details of all repository objects for the selected object type that have a specific status, e.g. synonyms with a status of invalid.

Some statuses only apply to specific repository object types.  About

If you use the object status list, the Object Status Utility only queries the repository for objects with that status, and not all repository objects. This may reduce the time needed to complete work tasks, e.g. editing details of specific indexes with a status of valid.

Note:	The default is to display all objects, but you can select to view only objects that are valid, invalid, enabled, disabled, missing or marked for reload.


Help - Instrumentation Report
Instrumentation Report (Help Menu)

Related Topics

Generates a report showing various information about the repository. The purpose of this report is to assist Oracle Support in determining the cause of a problem with the repository.


Help - Help Topics
Help Topics (Help Menu)

Related Topics

Displays a list of the main subject areas in the online documentation system.


Help - Show Keys
Show Keys (Help Menu)

Displays the shortcut keys for the current tool.


Help - How to use Help
How to Use Help (Help Menu)

Related Topics

Displays general information on how to use the Microsoft Windows help.


Help - About
About (Help Menu)

Displays copyright and version number information about this application. You might need to know the version number for product support purposes.


Help - Customer Support
Customer Support (Help Menu)

Displays an Oracle Support Problem Report (displayed in your default ASCII text editor) that you are requested to complete before contacting Oracle Support for assistance. The report asks for details about you, your environment setup and details about the problem, including any steps to reproduce the problem. By completing this form prior to contacting Oracle Support, you will aid the processing and response to your request.

A default text editor is set up for ASCII text based on the settings in the Windows Registry. You can specify an alternative editor by using Options→Text Editor Options.


Context-Sensitive Help button
   Context-Sensitive Help

Related Topics

Provides access to context-sensitive help information about the menu options, standard toolbar and drawing toolbar buttons.

Selecting this button, or pressing SHIFT+F1, and then selecting a menu option, standard toolbar button or palette button, displays help information for the chosen item.