Note that you can only use
prunerpd with binary repositories in RPD format.
This appendix contains the following topics:
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.
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:
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.
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.
Deletes the database named "Paint."
Deletes the column named "AGREE_CD" located in a table or alias named "W_AGREE_D" from the Physical layer.
I "External Metadata Strings"
Deletes the initialization block named "External Metadata Strings."
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).
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.
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]
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.
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
Deleting repository objects has a cascading effect. This section describes the deletion rules.
If a physical column or a table is deleted, then all of the affected keys, foreign keys, and complex joins are deleted as well. The internal obsolete attribute definition (attr defn) that links a logical column to a physical column is also removed.
Empty schemas, catalogs, and databases are removed.
If a table is deleted, then all its columns are deleted.
If a regular column (not an aggregate or derived column) is not mapped in any logical source, then it is deleted. The keys, including the level key and the logical key, are also removed.
If the source column for a derived column or its referenced variable is deleted (corrupted), then the column is removed.
If an aggregate rule or override aggregate rule for an aggregate column is corrupted (due to a logical column deletion), then the column is removed.
If a logical table is removed (because its underlying physical table was deleted), then the keys, foreign keys, logical joins, sources, and source folder are removed.
If a logical table source does not have any valid mapping, then it is deleted.
If a logical table source is retained, but its aggregate content or filters are corrupted, then the corresponding expressions are set to null. The join specification is also removed.
If a logical table, dimension, or business model is empty (contains no meaningful child), then it is deleted.
If a logical column is removed (because its underlying physical column was deleted), then any corresponding presentation columns are removed.
If a presentation table or subject area does not contain children, then it is removed.
If a security filter for a user or application role becomes corrupt due to deletion, then the filter is removed. If all filters are removed for a user or application role, then the internal privilege object is deleted.
Even if all filters for an application role are deleted, the application role is still maintained.
To remove an application role from the repository, you must explicitly delete it. See Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition for information about deleting application roles.
Initialization blocks are deleted if the underlying connection pool is deleted.
Repository and session variables are deleted if the associated initialization blocks are deleted.
If a session variable is deleted and its parent initialization block does not contain variables, then the initialization block is removed.
If an initialization block is deleted, then its variables are removed.
Qualified list items are deleted if the associated cache catalog, GUID column, or qualified column is deleted.
Target levels are deleted if the associated catalog (Segmentation Catalog name) is deleted.
List catalogs are deleted if the associated catalog, table, or column is deleted.
Conforming dimensions are deleted if the associated catalog, table, or column is deleted.