ORA-16826: apply service state is inconsistent with the DelayMins property

 ORA-16826: apply service state is inconsistent with the DelayMins property

We will get this Error mostly when we start the standby database redo apply Manually when the db broker is configured .. when the db broker is configured we should use the db broker to stop and start the redo apply
When the error is noted we have to disable and enable the configuration of the db broker to clear the error
In this same practice you can find the details how to stop and start the redo shipping using the db broker
Step 1 check the database status in the dbbroker 
Login to the db broker and check the status of the configuration and check the status of the database

  

Step 2 Disable the configuration and enable it 
Legends
show configuration := the command which is used to show the configuration of the db broker
Disable configuration := Disable the Configuration  the db broker will stop processing
enable  configuration :=  enables the configuration of the db broker

In the Primary  database dbbroker log file we will get the below message
07/31/2014 18:33:04
Data Guard Broker Status Summary:
  Type                        Name                             Severity  Status
  Configuration               OMOICDR                           Warning  ORA-16608
  Primary Database            OMPROD                            Success  ORA-00000
  Physical Standby Database   OMDRDB                            Warning  ORA-16826
07/31/2014 18:33:20
DISABLE CONFIGURATION
Command DISABLE CONFIGURATION completed
07/31/2014 18:33:34
DISABLE CONFIGURATION
Command DISABLE CONFIGURATION completed
07/31/2014 18:33:50
ENABLE CONFIGURATION
07/31/2014 18:34:29
Command ENABLE CONFIGURATION completed

In the Standby database logfile we will get the below details
Redo Apply is running without USING CURRENT LOGFILE option while DelayMins=0
07/31/2014 18:30:17
DMON Deregistering service OMDRDB_DGB with listener(s)
07/31/2014 18:30:50
DMON Registering service OMDRDB_DGB with listener(s)
07/31/2014 18:30:55
Redo Apply is running without USING CURRENT LOGFILE option while DelayMins=0
07/31/2014 18:31:24
Command ENABLE CONFIGURATION completed

Check the configuration of the 'OMDRDB'

STOP REDO SHIPPING USING DB BROKER

To stop the redo shipping by using the db broker we can Use
Edit database <database_name> set state='TRANSPORT-OFF';  then check the configuration of the primary database
if we use this command it will globally stop the redo shipping to all the stand by database we have
If we have three standby database and we need to stop apply for one database then we need to execute the command as
EDIT DATABASE < name pf stadnby database for which we to stop log shipping> SET PROPERTY LogShipping=OFF;

when you stop the redo shipping using the db broker the log_archive_dest_state_2 will be changed to the reset mode.. as we have configured only one destination for the stand by database

SQL> show parameter log_archive_dest_state_2

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_state_2             string      RESET

Check the log file sequence from the Primary
SQL> select RESETLOGS_CHANGE#, THREAD#, min(SEQUENCE#) mins, max(SEQUENCE#) maxs from v$log_history group by RESETLOGS_CHANGE#, THREAD#;

RESETLOGS_CHANGE#    THREAD#       MINS       MAXS
----------------- ---------- ---------- ----------
       2.3900E+10          1       4283       8646
       2.3900E+10          2       3203       6141


Check the log file sequence from the Stand by
SQL> select al.thrd "Thread", almax "Last Seq Received", lhmax "Last Seq Applied"
  2  from (select thread# thrd, max(sequence#) almax
  3  from v$archived_log
  4  where resetlogs_change#=(select resetlogs_change# from v$database)
  5  group by thread#) al,
  6  (select thread# thrd, max(sequence#) lhmax
  7  from v$log_history
  8  where resetlogs_change#=(select resetlogs_change# from v$database)
  9  group by thread#) lh
 10  where al.thrd = lh.thrd;

    Thread Last Seq Received Last Seq Applied
---------- ----------------- ----------------
         1              8644             8644
         2              6140             6139

SQL>
Now you can clearly find the difference between the two log sequecne as the redo shipping had been stooped if you want to enable the redo shipping then again change the transport on property

START REDO SHIPPING USING THE DB BROKER

To start the redo shipping again we need to edit the parameter of the database in the db broker and change to  EDIT DATABASE '<primary database name>' SET STATE='TRANSPORT-ON';

 

 SQL> show parameter log_archive_dest_state_2

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
log_archive_dest_state_2             string      ENABLE

Once you enable the transport-on in the db broker then the parameter state is turned to enable 

Check the log sequence from the Primary

SQL> select RESETLOGS_CHANGE#, THREAD#, min(SEQUENCE#) mins, max(SEQUENCE#) maxs from v$log_history group by RESETLOGS_CHANGE#, THREAD#;

RESETLOGS_CHANGE#    THREAD#       MINS       MAXS
----------------- ---------- ---------- ----------
       2.3900E+10          1       4287       8648
       2.3900E+10          2       3204       6144

SQL>

Check the log sequence from the stand by

SQL> select al.thrd "Thread", almax "Last Seq Received", lhmax "Last Seq Applied"
  2  from (select thread# thrd, max(sequence#) almax
  3  from v$archived_log
  4  where resetlogs_change#=(select resetlogs_change# from v$database)
  5  group by thread#) al,
  6  (select thread# thrd, max(sequence#) lhmax
  7  from v$log_history
  8  where resetlogs_change#=(select resetlogs_change# from v$database)
  9  group by thread#) lh
 10  where al.thrd = lh.thrd;

    Thread Last Seq Received Last Seq Applied
---------- ----------------- ----------------
         1              8648             8648
         2              6144             6143

Now both Primary and standby are sync again

Warning: ORA-16714: the value of property is inconsistent with the database setting

 Warning: ORA-16714: the value of property LogArchiveMaxProcesses is inconsistent with the database setting

When we are editing the init parameter's which is effecting the DB broker then we need to change the property value in the db broker also .. 

when we changed the property in of the SQL> alter system set log_archive_max_processes=10 scope=both sid='*'; then we need to change the same property in the db broker configuration file also by following method 

you can find what are the int parameter's used by the db broker by using the show database verbose <database_name>

Step 1 Check the status in the dgmgrl When we get the error in Db broker config  then we need to check the  particular database

Step 2 check the two database's configuration

For checking the configuration of the each database we need to type the command as show configuration <database_name>

As when we are checking the Stand by database We are getting the inconsistent property error for the LogArchiveMaxProcesses .. because we had changed the process  in the standby database by using the alter system command

Step 3 check the inconsistent properties

For checking the Inconsistent Properties we need to give the command show database<database name> InconsistentProperties

it will show what are the process are inconsistent in the below example we have two process because we are using the two node rac as the stadnby database

Legends

Instance_name:=Name of the instance where the inconsistent properties are located

Property_Name :=  Name of the inconsistent  Property 

Memory_value:=  10[the value which is located in the memory of the database]

Spfile_value:=     10[the value which is specified in the spfile]

db broker_value:=4[the value which is specified in the db broker ]

INCONSISTENT PROPERTIES
   INSTANCE_NAME      PROPERTY_NAME            MEMORY_VALUE  SPFILE_VALUE    BROKER_VALUE
   OMDRDB1            LogArchiveMaxProcesses                               10               10              4
   OMDRDB2            LogArchiveMaxProcesses                               10               10              4

Step 4 Set the Properties which had been change and set the correct value

Once we had identified the wrong propery value we need to edit the property of the database 

for editing the property of the database

edit database <db_name> SET PROPERTY property_name=value

Here in the below example we are editing the database to have max of 10 processes

Once you changed the property they you will not able to find the values when you query for inconsistent property then no values are displayed

  Finally check the configuration again and check now both the configuration are successful

Configuring BIAPPS 11.8 and ODI for Fusion applications

CONFIGURING BIAPPS 11.8 For FUSION APPLICATIONS 

As in this part we are going to configure the Bi apps and the ODI .. we need to extend the existing the bi domain for the configuration of the biapps

Step 1 Starting the Configuration

Start the configuration from the  by invoking the configapps.sh 

 

Step 2  Prerequisite Check

Check all the prerequisites are completed successfully

Step 3 Extending the Domain

As we have installed the ODI and BIapps in the same middle ware home where the BI had been installed we need to extend the weblogic Domain to add the new managed server for the ODI
Host name  :     Middle ware Host name where the Bi had been installed
Port            :     BI Weblogic Port Number
User Name  :    Weblogic_super_user_name
User Password  Weblogic Password Name

Step  4 Details of the BI Domain
We need to specify the path's and details of the Bi Domain
Middle ware Home : The Middle where home where the BI,BIAPPS,ODI are installed
Oracle Home          :BI Oracle Home
Weblogic Server Home : MW_Home/wlsserver_10.3
Domain_Home               :BI Domain Home
Instance Home               :BI Instance home
Instance Name               :Bi Instance Name

Step 5 :=Details of configuration components

Check the Oracle Business Intelligence Applications and Bi applications components

Step 6 :=RPD Password 
Provide the RPD Password which will be used to open the RPD in the bi admin toll later while mapping and developing the subject area's

Step 7 := Admin user Name Password 

Provide the Admin User Name Password

Step 8 :=MDS schema Details 
Database Type       :Oracle database
Connect String        :Hostnameod dw database :port number:<data ware house service name>
MDS Schema Username : User_ending with the MDS which is created by BI apps RCU
MDS Schema Password  :password for MDS Schema

Step 9 := BIACOMP user details 
Database Type :=Oracle database
Connect String :=Data ware House DB Host name: DB port:DB service
ODI Repository Schema Username:=User created by the ODI RCU ending with BIACOMP
BIA Components Repository Schema Schema Password: Password for biacomp

Step 10 BI analytic schema

Database Type :=Oracle database
Connect String :=Data ware House DB Host name: DB port:DB service
Business Analytic Ware House Schema Username:= user ending with the DW create by the RCU
Business analytic warehouse Schema Password :=  password for the user _DW

Step 11 Bi applications ODI
Database Type :=Oracle database
Connect String :=Data ware House DB Host name: DB port:DB service
ODI Repository Schema Username :=User name end with BIA_OIDREPO
ODI Repository Schema Password  : -password for the BIA_OIDREPO

Step 12 Port Configuration
We had select the auto port to go with the default port values .. if you had specified the custom port values during the installation of software .. then use the same staticport.ini file for defining the ports

Step 13 Summary Page 

Step 14 Configuration Process 

Step 15 Complete the Configuration 

Note: On success full  completion of the configuration Start the Node manager ,admin server and the two admin server's one for BI and another for ODI

ODI and BIAPPS Installation for BIAPPS 11.8

ORACLE DATA INTEGRATOR AND BI APPLICATIONS[11.8] INSTALLATION [part 4] 

In This practice [part 4] we go through the  steps for installing the ODI and BIAPPS binaries and once we apply the required patches we will go through the configuration steps in next part

Step 1
When you start the Installer the installer will Prompt  for the jdk location we need to specify the jdk location of the BI
Start the Installer an click the next page to Proceed

Step 2 Software updates 

Skip software Updates and Proceed for Next Page

Step 3 selecting the install products 
Select the Product for the installation
 we need to select the ODI studio,ODI SDK ,java EE Installation Java EE Agent,ODI console,Public Web service

Step 4 Prerequisite checking

Once all the Prerequisite's are completed then go with the next step

Step 5 MW_HOME Selection

Oracle Middle ware Home := provide the existing oracle MW_Home which is used for the BI installation
Oracle Home Directory      :=Oracle_OID1[it will be create in the MW_HOME]

Step 6 Choosing the application server

ODI can be installed in web logic or WebSphere since we had installed the BI on weblogic we need to install the ODI in the weblogic as we are going to extend the existing domain for ODI

Step 7 repository configuration 

Skip the ODI configuration we can configure after all the Patches had been applied

Step 8 installation summary 
Check the Installation Summary

Step 10 Configure Progress

Once the Installation process completes and  the configuration process starts..
The configuration Process Finishes successfully then we can go the next Page

Step 11 Install complete 

Save the config file for further reference and finish to complete the installation

INSTALLING BIAPPS 11.8

Download the BI Apps binaries from the oracle site and unzip in the temporary folder and Navigate to Disk1 and start the runinstaller 

Step 1

Run the installer and provide the jdk location  when it is asked 

Step 2 click next to proceed with the installation 

Step 3 Prerequisite checks 

Once all the requisite checks had been successful then proceed to next step

Step 4 MW_HOME and ORACLE_HOME location

Oracle Middle ware Home := [Provide the Middle ware Home Location where the BI Had been installed]
Oracle Home Directory      :=Provide the BI[OBIEE] oracle home

Step 5:=Check the summary page

check the summary page and save the summary file for further reference

Step 6 Installation IN Progress

Once the installation completes click next to proceed

Step 6

Save the Repository file for further reference and click finish

APPLYING PATCHES FUSION MIDDLE WARE ARTIFACTS FOR BIAPPS 11.8


Step 1
unzip all the patches in the directory and modify the  apply_patches_import.txt  file with the necessary changes MW_HOME/Oracle_BI1/biapps/tools/bin/

[orabi@biapp bin]$ cat /u02/app/oracle/fmw/Oracle_BI1/biapps/tools/bin/apply_patches_import.txt
# Required JAVA_HOME - Java home
JAVA_HOME=/u02/app/oracle/fmw/Oracle_BI1/jdk
# Required INVENTORY_LOC - Inventory Location
INVENTORY_LOC=/u01/app/oracle/oraInventory
ORACLE_HOME=/u02/app/oracle/fmw/Oracle_BI1
MW_HOME=/u02/app/oracle/fmw
COMMON_ORACLE_HOME=/u02/app/oracle/fmw/oracle_common
WL_HOME=/u02/app/=oracle/fmw/wlserver_10.3
SOA_HOME=
ODI_HOME=/u02/app/oracle/fmw/Oracle_ODI1
SKIP_BITECH_PATCHES=false

WORKDIR=/home/orabi/Patch/log

PATCH_ROOT_DIR=/home/orabi/Patch

Legends

JAVA_HOME:=Provide the value of the OBIEE java Home the java located inside the bi oracle home

INVENTORY_LOC:=Provide the central inventory Location 

ORACLE_HOME:=Provide the Location of the Bi oracle Home

MW_HOME:=Provide the Location of the Middle ware Home 

COMMON_ORACLE_HOME:=Provide the location of oracle_common directory which resides in MW_HOME

WL_HOME:=Provide the Location of the Weblogic Home

ODI_HOME:=Provide the Location of the ODI home

WORKDIR:=Create the Directory with read and write permission for the BI /Os user to create the log file

PATCH_ROOT_DIR:=Directory where the patch are  unzipped 

Step 2
Run the APPLY_PATCHES.pl  from the MW_HOME/Oracle_BI1/biapps/tools/bin with the
MW_HOME/Oracle_BI1/biapps/tools/bin/apply_patches_import.txt

[orabi@biapp bin]$ perl /u02/app/oracle/fmw/Oracle_BI1/biapps/tools/bin/APPLY_PATCHES.pl /u02/app/oracle/fmw/Oracle_BI1/biapps/tools/bin/apply_patches_import.txt

----------START OF PATCHING REPORT------------------

Current PLATFORM Detected :linuxx8664

* BIAPPSSHIPHOME Patching Report ..........
Patch Succeded: fsmlitedb_rel8pmlr2_17937188.zip
Patch Succeded: p17463314_111170_Generic.zip
Patch Succeded: fsmlite_rel8pmlr2_18529692.zip
Patch Succeded: p16913445_111170_Generic.zip
Patch Succeded: fsclite_rel8pmlr2_17937189.zip
Patch Succeded: p17463403_111170_Generic.zip
Patch Succeded: p17300045_111170_Generic.zip
Patch Succeded: p16997936_111170_Generic.zip
Patch Succeded: atglite_rel8mlr12_17657541.zip
Patch Succeded: atglite_rel8mlr11_database_17533000.zip
Patch Succeded: BIFNDNEPM_11_1_1_7_0OBIEEBP_LINUX_X64_130816_0640_17314326.zip
Patch Succeded: BISERVER_11_1_1_7_0OBIEEBP_LINUX_X64_130919_2217_17463395.zip
Patch Succeded: BIFNDN_11_1_1_7_0OBIEEBP_LINUX_X64_131008_1224_5_17463376.zip
Patch Succeded: p16569379_111170_Linux-x86-64.zip

* Oracle Common Patching Report ..........
Patch Succeded: EM_p14670290_111170_Generic.zip
Patch Succeded: WebCenter_BP8REL8_2_17483105.zip
Patch Succeded: p16433036_111170_Generic.zip
Patch Succeded: JDEVADF_REL8MLR9-RT_17611288.zip
Patch Succeded: idmpatch-1309a-ps6-17440204-urapi.zip
Patch Succeded: fmw_diagnostics_17714493.zip
Patch Succeded: idmpatch-1310a-ps6-17447428-owsmrel8.zip
Patch Succeded: SOACOMMON_REL8B7_17549390.zip
Patch Succeded: J2EE_Patch-3-PS6RC3_bug-17237952.zip
Patch Succeded: Webservices_Patch-2-PS6REL8_bug-17629596.zip
Patch Succeded: p16080773_111170_Generic.zip
Patch Succeded: p16830801_111170_Generic.zip
Patch Succeded: appstrace_17363039.zip
Patch Succeded: T2P_FW_REL8_Patch2_17353546.zip
Patch Succeded: p16433147_111170_Generic.zip
Patch Succeded: idmpatch-1311a-ps6-17665823-opss.zip

* SOA Patching Report ..........
 Not applying SOA Patches since SOA Home (SOA_HOME) value is not specified

* ODI Patching Report ..........
Patch Succeded: p18204886_111170_Generic.zip

* Weblogic Patching Report ..........
Successfully installed Patch ID:  2GH7
Successfully installed Patch ID:  W3Q6
Successfully installed Patch ID:  RJNF
Successfully installed Patch ID:  FKGW
Successfully installed Patch ID:  JEJW
Successfully installed Patch ID:  LJVB
Successfully installed Patch ID:  IHFB
Successfully installed Patch ID:  6AEJ
Successfully installed Patch ID:  EAS7
Successfully installed Patch ID:  TN4A
Successfully installed Patch ID:  KPFJ

----------END OF PATCHING REPORT------------------

This final patching report log file is also located at: /home/orabi/Patch/log/final_patching_report.log


Check the Log files for the Each location
[1]check the  biappshiphome_generic_patches.log and verify Patches had Been applied
Verifying the update...
Patches 16913445,16997936,17300045,17463314,17463403,17533000,17657541,17937188,17937189,18529692 successfully applied.
Log file location: /u02/app/oracle/fmw/Oracle_BI1/cfgtoollogs/opatch/opatch2014-07-13_17-20-50PM_1.log
OPatch succeeded.

[2]Check biappshiphome_linux64_patches.log as we are using the Linux 64x84 

Verifying the update...

Patches 16569379,17314326,17463376,17463395 successfully applied.

Log file location: /u02/app/oracle/fmw/Oracle_BI1/cfgtoollogs/opatch/opatch2014-07-13_17-29-05PM_1.log

OPatch succeeded.

[3] Check the odi_generic_patches.log 

Verifying the update...

Patches 18204886 successfully applied.

Log file location: /u02/app/oracle/fmw/Oracle_ODI1/cfgtoollogs/opatch/opatch2014-07-13_17-40-39PM_1.log

OPatch succeeded.

[4]Check the oracle_common_generic_patches.log

Verifying the update...

Patches 14670290,16080773,16433036,16433147,16830801,17237952,17353546,17363039,17440204,17447428,17483105,17549390,17611288,17629596,17665823,17714493 successfully applied.

Log file location: /u02/app/oracle/fmw/oracle_common/cfgtoollogs/opatch/opatch2014-07-13_17-37-25PM_1.log

OPatch succeeded.

[5] cat weblogic_patching.log

Identifying patches that may be installed ...

Installable patches:[2GH7, RJNF, FKGW, JEJW, LJVB, IHFB, 6AEJ, EAS7, W3Q6, TN4A, KPFJ]

Identifying patches that may be removed ...

Remove candidates: [GFWZ, ITL9, P9A6, H2FT, 6D9T, TWDG, GVYL, 7AAZ, 9BPB, LYRQ, SRUM, TZFH, TL3Y, 99BQ, LWLH, HYKC, Z8MQ, 91SX, A1DL, S39F, I3HZ, AW1V, 3DM4, 81X7, 4GG5, 3BBT, 7YZB, IUZI, 7BG3, 956R, 9887, S76X, 6X2J, 4GPI, GKQW, 6V9V, IH4D, QKPF, HS7H, XA6W, 8JYQ, U1RB, 2277, ZR38, 27QC, S4BN, 81QF, YJI2, EUW3, 7YU1, YHFH, RFP7, 16ZR, 61K2, 9T2G, ZPB8, 1IHE, WYRU, ALFS, CHEE, JG58, 56MM, HW5A, SFAZ, GP9A, F89C, G72F, EG2S, FL81, SZXM, QEUF, ANVN, KIGI, 1PI6, RNQP, BS5P, W4F6, CM69, Q1UZ, UDN7, F6G7, 7WVY, JZED, E9FL, RPI1, 9264, SKLY, B8V1, 9I9D, MYFD, F31P, BCSD, XLVS, FFRX, BADF, K1J3, 2NUX, RIPQ, CLLX, 1NRR, XIJ8, QK63, JLJ6, RUNT, AI76, 4SYF, V41Y, XLUK, YJTB, 72TK, MB4Y, Z4W7, EF1X, BEJG, BJY4, 879N, 546H]

Removable patches:[]

Installing patches ...

Patches to be installed in following order: [2GH7, W3Q6, RJNF, FKGW, JEJW, LJVB, IHFB, 6AEJ, EAS7, TN4A, KPFJ]

Installing patch: KPFJ

Sun Jul 13 18:06:11 GST 2014: Executing command:

  /u02/app/oracle/fmw/Oracle_BI1/jdk/jre/bin/java

  -Duser.country=US

  -Duser.language=en

  -jar

  /u02/app/oracle/fmw/utils/bsu/patch-client.jar

  -prod_dir=/u02/app/oracle/fmw/wlserver_10.3

  -install

  -patchlist=KPFJ

  -log=/tmp/bsu-wrapper-logs/bsu-wrapper-2014.07.13.17.41.10.log

  -log_priority=debug

Checking for conflicts...

No conflict(s) detected

Installing Patch ID: KPFJ.

Result: Success

Once the Patching Process complete's  Successfully start the Node manage and Weblogic server through wls script

ATGLITE Upgrade
Run the below command to upgrade the ATG
[orabi@biapp lib]$ /u02/app/oracle/fmw/Oracle_BI1/jdk/bin/java -jar  biappsrepositoryutil.jar upgradeATG bi.oracle.home=/u02/app/oracle/fmw/Oracle_BI1/ work.dir=/home/orabi/Patch/log biacomp.user=BIAPPS_BIACOMP  biacomp.password=OMsys123 db.conn.sid.url=<hostname>:1521:<SID> atg.db.seed.url=<hostname>:1521/<service_name> db.sys.user=SYS db.sys.password=<passowrd>

Jul 13 2014 19:58:07 INFO : Connecting to database: user:SYS as sysdba, connectString:jdbc:oracle:thin:SYS as sysdba/*****@<hostname>:1521:biapp

Jul 13 2014 19:58:07 INFO : Finished   ATGSeedDataUpgradeTask execution.

Jul 13 2014 19:58:07 INFO : Completed upgrade task: ATGSeedDataUpgradeTask

Jul 13 2014 19:58:07 INFO : Completed  upgrade command execution for component -ATG

Jul 13 2014 19:58:07 INFO : Completed component upgrade - ATG

UPGRADING FSM

 /u02/app/oracle/fmw/Oracle_BI1/jdk/bin/java -jar  biappsrepositoryutil.jar upgradeFSM bi.oracle.home=/u02/app/oracle/fmw/Oracle_BI1/ work.dir=/home/orabi/Patch/log biacomp.user=BIAPPS_BIACOMP  biacomp.password=OMsys123 db.conn.sid.url=<host_name>:1521:biapp fsm.db.seed.url=<host_name>:1521/<service_name>  db.sys.user=SYS db.sys.password=OMsys123

Jul 13 2014 20:18:19 INFO : Calling JDBCEngine constructor

Jul 13 2014 20:18:19 INFO : Connecting to database: user:SYS as sysdba, connectString:jdbc:oracle:thin:SYS as sysdba/*****@192.168.4.120:1521:biapp

Jul 13 2014 20:18:19 INFO : Finished   FSMSeedDataUpgradeTask execution.

Jul 13 2014 20:18:19 INFO : Completed upgrade task: FSMSeedDataUpgradeTask

Jul 13 2014 20:18:19 INFO : Completed  upgrade command execution for component -FSM

Jul 13 2014 20:18:19 INFO : Completed component upgrade - FSM

RCU for BIAPPS and ODI

BI APPS 11.8 Installation[CREATING RCU for ODI and BIAPP]part -3

In this Part 3 of Bi Apps Installation we will  have the Practice of Installing the RCU for BI APPS and ODI

for Running the Rcu we need to download the  software and unzip in the database server temp folder 

 

CREATING RCU FOR BIAPPS

Step 1

Navigate to the /home/oracle/rcu/bin-- rcu is the staging directory where we unzip the V44918-01.zip 

run ./rcu to invoke the installer 

Step 2
Click create Button to create the RCU for BIAPPS

Step 3
Provide the data warehouse database details 
Host name      :=data warehouse database host name
Port               :=  Database Port
ServiceName  :=Data warehouse database service Name
Username       :=SYS
Password       :=Password of SYS user

Once the Prerequisite check completes fine then click ok and proceed to next step

Step 3
Create the Prefix as BIAPPS
and select the Oracle Business Analytic Warehouse-- it will create only the BI apps repository and we will create the ODI repository later

Step 4 

Provide the password for the BIAPPS schema user

Step 5
we need to provide the dump file location .. there are three dump file available and two of  ODI and one for BIAPPS

[oracle@biapp schema]$ pwd
/home/oracle/rcu/rcu/integration/biapps/schema
[oracle@biapp schema]$ ls
-rwxrwxr-x. 1 oracle oinstall 379461632 Apr 18 18:43 obia_comp.dmp
-rwxrwxr-x. 1 oracle oinstall 125952000 Apr 18 18:43 obia.dmp
-rwxrwxr-x. 1 oracle oinstall 857681920 Apr 18 18:42 obia_odi.dmp
-rwxrwxr-x. 1 oracle oinstall                70 Apr18 18:43 dmplabel.txt
[oracle@biapp schema]$
if you are installing the BI rcu from the different server then we need to keep this three files in the DW database server tmp directory and we need to mention the location in the value column

Step 6

Check the table space the will be create for the new schema

Increase the size of the  table space according to the requirement

Step 7
Check the summary and proceed with the installation of RCU

Step 8

Check the summary and click finish for complete the RCU

CREATING RCU FOR ODI

Step 1

Run the ./rcu from the /home/oracle/rcu/bin  /home/oracle/ruc is the staging directory where the ruc software had been unzipped 

Step 2
Click create to create the new RCU

Step 3
Host name    Data Warehouse  database host name
Port              Database port
Service         Database Port
User Name  SYS
Password    OMsys123
check ok after the prerequisite check's had been completed successfully

Step 4

Create the prefix for the ODI Scheme's

select the components show in screen  to create the ODI schema

Step 5

[oracle@biapp schema]$ pwd
/home/oracle/rcu/rcu/integration/biapps/schema
[oracle@biapp schema]$ ls
-rwxrwxr-x. 1 oracle oinstall 379461632 Apr 18 18:43 obia_comp.dmp
-rwxrwxr-x. 1 oracle oinstall 125952000 Apr 18 18:43 obia.dmp
-rwxrwxr-x. 1 oracle oinstall 857681920 Apr 18 18:42 obia_odi.dmp
-rwxrwxr-x. 1 oracle oinstall                70 Apr18 18:43 dmplabel.txt
[oracle@biapp schema]$
provide the path in the value

Step 6

Step 7

Check the summary