Skip Headers
Oracle® Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition
11g Release 1 (11.1.1)

Part Number E10540-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

E Deleting Unwanted Objects from the Repository

This appendix explains how to use the command-line pruning utility, prunerpd, to delete unwanted objects in the Oracle BI repository.

Note that you can only use prunerpd with binary repositories in RPD format.

This appendix contains the following topics:

About the Object Pruning Utility

If you have a large number of extraneous or unwanted objects in your repository, you can delete the unwanted objects using the prunerpd command-line utility. You can use prunerpd on both Windows and UNIX systems.

You can delete unwanted repository objects such as databases, tables, columns, initialization blocks, and variables. However, note that the pruning utility does not remove objects from the Oracle BI Presentation Catalog.

Deleting objects from the repository has a cascading effect. For example, if a physical column is deleted, then any mapped logical columns are deleted, as well as any associated presentation columns. See "Deletion Rules for the Object Pruning Utility" for more information.

Using the Object Pruning Utility

You must first create the input file that contains the list of repository objects to be deleted. Then, you must run the utility at the command line, passing the input file as an argument

This section contains the following topics:

Creating the Input File

The prune utility accepts the list of repository objects you want to delete as a text file. The utility can accept multiple input files at a time. The syntax rules for the input file are shown in Table E-1.

Note:

Object names in the input file must match the fully qualified name that is used in the repository. Wildcards (such as "*" and "?") are not supported in the object name.

Table E-1 Syntax Rules for Input File

Object Type Example Action

Database

D "Paint"

Deletes the database named "Paint."

Table

  • T "W_AGREE_D"

  • T "DB"."Catalog"."Schema"."Table"

  • Deletes the table or alias named "W_AGREE_D" from the Physical layer.

  • Deletes the table or alias named "Table" from the schema named "Schema," contained in the catalog named "Catalog," located in the database named "DB," from the Physical layer.

Column

C "W_AGREE_MD"."AGREE_CD"

Deletes the column named "AGREE_CD" located in a table or alias named "W_AGREE_D" from the Physical layer.

Initialization block

I "External Metadata Strings"

Deletes the initialization block named "External Metadata Strings."

Variable

V CURR_USER

Deletes the variable named "CURR_USER."


For example, a text file that contains instructions to delete a database named "Stock Quotes" and a physical column named "S_NQ_ACCT"."USER_NAME" would include the following entry:

D "Stock Quotes" C "S_NQ_ACCT"."USER_NAME"

Use white space as a delimiter in the input file (a single space, tab, or multiple spaces).

Running the prunerpd Utility

Before running prunerpd, you must first run bi-init to launch a command prompt that is properly initialized. See "Running bi-init to Launch a Shell Window Initialized to Your Oracle Instance" for more information.

Syntax 

The prunerpd utility accepts the following parameters:

prunerpd -s source_rpd [-p rpd_password] -f input_file -o output_rpd -l output_log_file -e error_log_file [-8]

Where:

source_rpd is the name and location of the target repository file.

rpd_password is the repository password for the source repository.

The password argument is optional. If you do not provide a password argument, you are prompted to enter a password when you run the command. To minimize the risk of security breaches, Oracle recommends that you do not provide a password argument either on the command line or in scripts. Note that the password argument is supported for backward compatibility only, and will be removed in a future release. For scripting purposes, you can pass the password through standard input.

input_file is the input file name (in text format) that contains the list of repository objects to be removed. Separate multiple file names by spaces. Enclose spaces within a filename with double quotes (" ").

output_rpd is the name and location of the output repository file, also known as the pruned repository.

output_log_file is the name and location of the output log file. All actions performed on the repository are written to this file, including descriptions. The output log file is in XML format. Other messages, such as progress indicators, are sent to the standard output stream.

error_log_file is the name and location of the error log file. The pruning utility writes exceptions and errors to this log. The error log file is in XML format. Other errors are sent to the standard output error stream.

-8 specifies UTF-8 encoding.

Example 

prunerpd -s C:/OBI/Server/Repository/BIApps.rpd 
-f "C:/Remove Oracle EBS Objects.txt"
-o "C:/OBI/Server/Repository/BIApps Pruned.rpd"
-l "C:/temp/BIApps Prunning.log" -e "C:/temp/ BIApps Prunning.err"
Give password: my_repos_password

Deletion Rules for the Object Pruning Utility

Deleting repository objects has a cascading effect. This section describes the deletion rules.

Physical Layer Rules

Logical Table Rules

Presentation Layer Rules

Security Rules

Variable Rules

Marketing Rules