Run the Generator

The Oracle Database Metadata Generator is invoked from the command line or embedded in a batch file.

The command-line executable is named sametaexport.

The sametaexport utility is available on both Windows and Linux systems. However, you can only use sametaexport with binary repositories in repository format.

The location of the sametaexport utility is:

ORACLE_HOME/bi/bifoundation/server/bin

sametaexport -r "PathAndRepositoryFileName" [-p repository_password]
-f "InputFileNameAndPath" [options]

The table contains descriptions of the parameters in the command-line executable file.

Parameter	Definition	Additional Information
-r	Repository file name and full path	Quotation marks are required for the file name and path only if the file path is in long format or has spaces. Use the full path if the file isn't in the current directory.
-p	Repository password	The password for the given repository. The password argument is optional. If you don't provide a password argument, you're prompted to enter a password when you run the command. To minimize the risk of security breaches, Oracle recommends that you don't provide a password argument either on the command line or in scripts. For scripting purposes, you can pass the password through standard input.
-f	Input file name and full path	Quotation marks are required for the file name and path only if the file path is in long format or has spaces. Use the full path if the file isn't in the current directory. You specify input files so that you don't have to type all the required information at the command line, and so that you can type international characters. See About the Metadata Input File.

Parameter

Definition

Additional Information

-r

Repository file name and full path

Quotation marks are required for the file name and path only if the file path is in long format or has spaces. Use the full path if the file isn't in the current directory.

-p

Repository password

The password for the given repository.

The password argument is optional. If you don't provide a password argument, you're prompted to enter a password when you run the command. To minimize the risk of security breaches, Oracle recommends that you don't provide a password argument either on the command line or in scripts. For scripting purposes, you can pass the password through standard input.

-f

Input file name and full path

Quotation marks are required for the file name and path only if the file path is in long format or has spaces. Use the full path if the file isn't in the current directory. You specify input files so that you don't have to type all the required information at the command line, and so that you can type international characters. See About the Metadata Input File.

You can include some additional parameters in the input file or at the command line to change various defaults for the Oracle Database Metadata Generator. Parameters specified in the input file take precedence over parameters specified at the command line. You must include these parameters only if you want to change the default values.

The tables describe these optional parameters.

Parameter Definition	Additional Information	Input File Usage Example	Command Line Usage Example
Use schema name from Oracle BI repository	When set to `YES`, the table schema names are used as they're used in the repository. The default value is `YES`.	`USE_SCHEMA_NAME_FROM_RPD = NO`	`-schemafrom rpd NO`
Default schema name	The default schema name is used as the table schema name if the value of `-schemafromrpd` is set to `NO`, or if the repository schema name can't be determined. The default value is `SIEBEL`.	`DEFAULT_SCHEMA_NAME = ORACLE`	`-defaultschema ORACLE`
Oracle schema name	The metadata from Oracle Database Metadata Generator is created under this schema. The default value is `SIEBEL`.	`ORA_DIM_SCHEMA_NAME = ORACLE`	`-orclschema ORACLE`
Logging enabled	Indicates whether to keep a log of the metadata export process. Valid values are `ON`, `OFF`, and `DEBUG`. The default value is `ON`.	`LOGGING = DEBUG`	`-logging DEBUG`
Log file name	The path to the log file. If you provide an invalid path, an error occurs. If you don't provide this parameter, the default log file path is used. The default path is: ORACLE_INSTANCE\diagnostics\logs\ OracleBIServerComponent\ coreapplication_obisn\ OraDimExp.log	`LOG_FILE_NAME = C:\bea_default\instances\instance1\diagnostics\ logs\generator\logfile.log`	`-logfile C:\bea_default\instances\instance1\diagnostics\logs\generator\logfile.log`

Parameter Definition	Additional Information	Input File Usage Example	Command Line Usage Example
Distinct count supported	When set to `YES`, allows measure containing the `DISTINCT_COUNT` aggregation to be exported. The recommended setting and default value is `NO`.	`DISTINCT_COUNT_SUPPORTED = YES`	`-distinct YES`
Statistical functions supported	When set to `YES`, allows measures containing the aggregation `STDDEV` to be exported. The recommended setting and default value is `NO`.	`STATISTICAL_FUNCTIONS_SUPPORTED = YES`	`-stat YES`
Use schema name	When set to `YES`, the Cube Views metadata attributes have columns from tables under a schema name, which are then specified in the parameters. When set to `NO`, the schema names for these tables are empty. The default value is `YES`.	`USE_SCHEMA_NAME = NO`	`-useschema NO`
Use schema name from Oracle BI repository	When set to `YES`, the table schema names are used as they're used in the repository. The default value is `YES`.	`USE_SCHEMA_NAME_FROM_RPD = NO`	`-schemafromrpd NO`
Default schema name	The default schema name is used as the table schema name if the value of `-schemafromrpd` is set to `NO`, or if the repository schema name can't be determined. The default value is `SIEBEL`.	`DEFAULT_SCHEMA_NAME = ORACLE`	`-defaultschema ORACLE`
Cube views schema name	The name of the schema under which the Cube Views metadata is created. The default value is `SIEBEL`.	`CUBE_VIEWS_SCHEMA_NAME = ORACLE`	`-cubeschema ORACLE`
Log file name	The path to the log file. If you provide an invalid path, an error occurs. If you don't provide this parameter, the default log file path is used. The default path is: ORACLE_INSTANCE\diagnostics\logs\ OracleBIServerComponent\ coreapplication_obisn\ CubeViews.log	`LOG_FILE_NAME = C:\bea_default\instances\instance1\diagnostics\logs\generator\logfile.log`	`-logfile C:\bea_default\instances\instance1\diagnostics\logs\generator\logfile.log`
Log failures	When set to `YES`, the log file lists the metadata that was invalidated under a certain rule. The default value is `YES`.	`LOG_FAILURES = NO`	`-logfail NO`
Log success	When set to `YES`, the log file lists the metadata that's been checked under each rule and has passed the check. The default value is `NO`.	`LOG_SUCCESS = YES`	`-logsuccess YES`