Oracle BI Applications
In BI-Admin Tool, Look at SYSTEM SESSION VARIABLE = ‘RUNAS’
It has an Initialization Block = ‘Set_RUNAS’ (Select ‘dummy’ from dual)
In DNC_DW schema, table W_PROXY_ACTAS has 3 columns:
PROXY_USER_ID = ‘WEBLOGIC’
PROXY_TARGET_ID = ‘VC-XYZ’
PROXY_LEVEL = ‘FULL’
For more information see this:
Goto ‘Administration’->’Issue SQL’
and use NQSGetSessionValue or NQSSetSessionValue and click on ‘Issue SQL’ button.
VAR_VALUE shows the value, when GET is used.
For example:
call NQSSetSessionValue(‘Integer LOGLEVEL=5;’)
call NQSGetSessionValues(‘NQ_SESSION.LOGLEVEL’)call NQSGetSessionValues(‘FILTER_METRIC_SPLITTING_LEVEL’)
Export out obia out of the box rpd to xml.
Then you can search all those xml files.
For example:
to search all dimensions and fact objects in Physical layer, related to AP dimensions = PT*Dim*AP*.xml and Facts = PT*Fact*AP*.xml
to search all dimensions and fact objects in BMM layer, related to AP dimensions = LT*Dim*AP*.xml and Facts = LT*Fact*AP*.xml
https://blogs.oracle.com/biapps/configuring-enterprise-calendar-for-oracle-bi-apps-time-dimension
select * from w_mcal_cal_d; — In OBIA Datawarehouse
select * from PS_CAL_DEFN_TBL order by calendar_id; — In PeopleSoft
To see Calendar Definition Table in PeopleSoft
select * from PS_CAL_DEFN_TBL order by calendar_id;
For valid list of combinations of SETID~CALENDAR_ID, run the following query in the OLTP:
SELECT DISTINCT SETID || ‘~’ || CALENDAR_ID FROM PS_CAL_DEFN_TBL;
These combinations of SETID~CALENDAR_ID is also the MCAL_CAL_ID column in w_mcal_cal_d datawarehouse table.
Descriptions MCAL_CAL_NAME in w_mcal_cal_d should match the calendar description DESCR column in PS_CAL_DEFN_TBL PeopleSoft table.
In OBIA:
GBL_CALENDAR_ID: This parameter should be the CALENDAR_ID of the DW generated Calendar (so either 4-4-5 or 13 period calendar).
By default, the 4-4-5 calendar has a CALENDAR_ID of ‘10000’.
By default, the 13-period calendar has a CALENDAR_ID of ‘10001’.
GBL_DATASOURCE_NUM_ID: If Enterprise Calendar is a DW generated Calendar, this parameter should be the DATASOURCE_NUM_ID value of OBIA Datawarehouse. For example, if the DATASOURCE_NUM_ID for your DW is 999, then GBL_ DATASOURCE_NUM_ID should be set to 999.
You can apply a patch to the original file using the patch merge feature in the Administration Tool, using the patchrpd utility, or by running biserverxmlexec with the -B option.
For example, if you have repository versions A0, A1, and A2, and you have an XML patch file called A2-0delta.xml that contains the changes between the latest and original versions, you can run the following command:
biserverxmlexec -I A2-0delta.xml -B A0.rpd -O A2reproduced.rpd
Alternatively, if you stored changes between A0 and A1, and then A1 and A2, you can run two commands to apply the latest changes on the original file:
biserverxmlexec -I A1-0delta.xml -B A0.rpd -O A1reproduced.rpd biserverxmlexec -I A2-1delta.xml -B A1reproduced.rpd -O A2reproduced.rpd
Make sure to specify different names for the -B and -O arguments to avoid overwriting the original repository file.
Use biserverxmlgen to generate an XML file from an existing repository file (RPD). To use this utility, execut
biserverxmlgen -R repository_pathname [-P password] -O output_file_pathname [-8] [-N] [-Q|-S]
Where:
repository_pathname is the name and location of the repository file from which you want to generate XML.
password is the repository password.
output_file_pathname is the name and location of the XML output file you want to generate. It is recommended that you provide an output filename with an .xml extension.
Specify -8 to use UTF-8 encoding in the generated XML file. If you do not specify -8, the generated XML file uses ANSI ISO-8859-1 encoding by default.
Specify -N to generate output without upgrade ids (uids). These are the internal identifiers of objects. Use this if you want to create a new repository without the old upgrade ids.
You can use one of the two options -Q and -S to control the generation of security objects:
-Q to generate output without security objects-S to generate output for only security objectsIf you use both -Q and -S on the same call of biserverxmlgen, the second option on the call command takes precedence, and the first is ignored.
Use biserverxmlcli to execute XML against the Oracle BI Server. This utility is very similar to biserverxmlexec, but is instead used to modify an online repository. An online repository is a running Oracle BI Server instance that has loaded an existing repository into its navigation space.
To use this utility, execute the following at the command prompt:
biserverxmlcli -U user_name [-P user_password] [-R repository_password] -D data_source_name [-w ssl_pass_phrase |-y] -I XML_file_pathname [-N]
Where:
user_name is a valid user name. This user must have the manage repository permission (oracle.bi.server.manageRepositories).
user_password is the corresponding user password.
repository_password is the repository password for the online repository.
data_source_name is the Oracle BI Server ODBC data source name (DSN) to which you want to connect.
ssl_pass_phrase is the SSL passphrase for the Oracle BI Server, if the ODBC connection has been configured to use SSL.
-y is the SSL passphrase to the private key file.
xml_file_pathname is the name and location of the XML input file you want to execute.
Specify -N to ignore all non-fatal errors. Examples of non-fatal errors are unresolved objects, duplicated objects, and broken expressions.