ORACLE BI Apps(7.9.6.X) ONLINE Training

ORACLE BI Apps ONLINE Training

We provide you:

• Training from actual IT industry experience professionals.
• No commutation to training centers, waiting for trainer.
• Curriculum  as per OBI Apps / OBIEE industry requirements.
• Training module with Real time scenario based.
• Assist to
• Get Certification on OBI Apps Implementation specialist.
• Interview process.

OBIA (7.9.6.X) Online Training Curriculum:

1. Oracle OBI Apps (7.9.6.X) overview.
1. OBIA Architecture.
2. DAC Architecture.
1. Overview of DAC
2. DAC behavior.
3. What is necessity of DAC in OBIA ?
3. Informatica ETL Architecture
4. OBIEE Architecture
5. Comparison between OBIEE and OBIA. 
2. OBI Apps Installations and environment setup / Configurations.
1. Demo of following tools installations
1. Informatica
2. DAC
3. OBIEE 
2. General Configurations
1. Configuration in Informatica
2. Configuration in DAC
3. Configuration in OBIEE
3. Finance Analytic s Module for E-Business Suite.(Oracle Apps R12)
1. Configuring Finance analytics Module for EBS.
2. Run the Full load and Incremental Load.
3. BASIC Functional EBS training on AP /AR / GL.
4. Finance Analytic Data model overview
5. Group account configuration
6. Multi currency & Calenders setup
7. RPD Metadata overview
8. Finance related Dashboard and Reports
9. How to customize ?
10. How to Trouble shoot the ETL / DAC / Dashboad / Report errors.
11. Customization hands on with real time scenario.
4. Other modules 
1. HR Analytics.
2. Spend and Procurement Analytics
3. Supply chain and Oder management Analytics
5. Security Implemention in OBIEE
1. How to create Users and provide privileges.

Audience :

• OBIEE Developers / consultants.
• Informatica Developers / Other ETL Developers.
• Datawarehouse developers.
• Report Developers.

Pre- requisite for this Training:

• Basic Data warehousing concepts 
• None
• Freshers.

How to upgrade Web logic Server (WLS) 10.3.5 to 10.3.6 in Windows 64 Bit.

Pr-requisite before Upgrading:

1.ShutdownWebLogic Server and the Oracle Business Intelligence by selecting:

 
 

Start> All Programs > Oracle Business Intelligence > Stop BI Services and stopped Oracle WebLogicNodeManager (c_Middleware_wlserver_10.3) service

 
 

2. Download the  Patch - p13529623_1036_Generic.zip from Oracle Support site.

 
 

How to download the patch ? 

 Screenshot shows the patch for Linux. Similarly you can choose windows from drop down option.

 

 

 
 

 

 

3. Unzipp the p13529623_1036_Generic.zip, you will find the following file:

     wls1036_upgrade_generic.jar

4. Backup Middleware folder and inventory directory.

 

5. Check the Java version.ForWebLogic 10.3.5 installations you need JDK6, but you can also use it for WebLogic 10.3.6 installations.

 
 

6. WebLogic 10.3.6 installations can use either JDK6 or JDK7 depending on your requirements. This is the same JDK7 you will use for development or production servers. Do not use JDK7 for an Oracle BI Apps 11.1.1.7.0 installation.

 
 

7. 

 

Upgrade :

 
 

1. (UNIX or Linux only) Include the -d64 flag in the installation command when using a 32/64-bit  hybrid JDK (such as for the HP-PA, HPIA, and Solaris64 platforms). For example, if installing in graphical mode using the Package installer:

• java -d64 -jar wlsversion_generic.jar
  

2. If you are using the Sun 64-bit JDK, use the following command to install WebLogic Server: Navigate to the patch folder. Run the command

 
 

   java -Xmx1024m -jar wls1036_upgrade_generic.jar

      OR for 32 bit java

   java  -jar wls1036_upgrade_generic.jar

   
 

 

 

3. 

 

     
 

 

4.  For upgrading choose 'Use an existing Middleware Home'  You will see the Middleware Home     Directory greyed out.

 
 

 

5. Next follow the GUI on screen instructions for Upgrade.

 
 

Post Installation : 

 
 

How to check/verify the Weblogicversion ?

 

1.  Once the server is started you can access the administrator console using the "http://hostname:7001/console" URL. Log in using the username and password

 
 

2.   

 

 

 3.

 

 
 

4.   Run the following command

java -cp /optional/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar weblogic.version –verbose

 
 

 

How to upgrade Weblogic 10.3.5 to 10.3.6

How to upgrade Web logic Server (WLS) 10.3.5 to 10.3.6 in Windows 64 Bit.

Pr-requisite before Upgrading:

1.Shutdown WebLogic Server and the Oracle Business Intelligence by selecting:

Start > All Programs > Oracle Business Intelligence > Stop BI Services and stopped Oracle WebLogic NodeManager (c_Middleware_wlserver_10.3) service

2. Download the  Patch - p13529623_1036_Generic.zip from Oracle Support site.

How to download the patch ? 

 Screenshot shows the patch for Linux. Similarly you can choose windows from drop down option.

3. Unzipp the p13529623_1036_Generic.zip, you will find the following file:

     wls1036_upgrade_generic.jar

4. Backup Middleware folder and inventory directory.

5. Check the Java version.For WebLogic 10.3.5 installations you need JDK6, but you can also use it for WebLogic 10.3.6 installations.

6. WebLogic 10.3.6 installations can use either JDK6 or JDK7 depending on your requirements. This is the same JDK7 you will use for development or production servers. Do not use JDK7 for an Oracle BI Apps 11.1.1.7.0 installation.

7. 

Upgrade :

1. (UNIX or Linux only) Include the -d64 flag in the installation command when using a 32/64-bit  hybrid JDK (such as for the HP-PA, HPIA, and Solaris64 platforms). For example, if installing in graphical mode using the Package installer:

• java -d64 -jar wlsversion_generic.jar
  

2. If you are using the Sun 64-bit JDK, use the following command to install WebLogic Server: Navigate to the patch folder. Run the command

    java -Xmx1024m -jar wls1036_upgrade_generic.jar
      OR for 32 bit java
   java  -jar wls1036_upgrade_generic.jar
   

3. 

     

4.  For upgrading choose 'Use an existing Middleware Home'  You will see the Middleware Home 

     Directory greyed out.

 

5. Next follow the GUI on screen instructions for Upgrade.

Post Installation : 

How to check/verify the Weblogic version ?

1.  Once the server is started you can access the administrator console using the "http://hostname:7001/console" URL. Log in using the username and password

2.   

 3.

 

4.   Run the following command

java -cp /optional/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar weblogic.version –verbose

 

DAC 10g Installation error in Linux 5 : oracle reinstall error: “Installation cannot continue...

oracle reinstall error: “Installation cannot continue. Make sure that you have read/write permissions to the inventory directory…”

 $ ./runInstaller

You do not have sufficient permissions to access the inventory '/u01/app/oraInventory'. Installation cannot continue. Make sure that you have read/write permissions to the inventory directory and restart the installer.: Permission denied

 Oracle thinks there is still a oraInventory, even though I got rid of it. There is a file somewhere (not in /u01) telling oracle that oraInventory exists. So I delete the install dir (home/oracle/database) and start over:

 $ rm -rf database/

$ unzip linux.x64_11gR2_database_1of2.zip
$ unzip linux.x64_11gR2_database_2of2.zip
$ cd database/
$ ./runInstaller
You do not have sufficient permissions to access the inventory '/u01/app/oraInventory'. Installation cannot continue. Make sure that you have read/write permissions to the inventory directory and restart the installer.: Permission denied

It wasn’t in the database dir, it was here: /etc/oraInst.loc. After doind a few oracle installs I guessed it was in /etc, but you could use find or locate to find this file.

as root:
rm /etc/oraInst.loc

 as oracle:

$ ./runInstaller
Starting Oracle Universal Installer...

Checking Temp space: must be greater than 120 MB. Actual 9801 MB Passed
Checking swap space: must be greater than 150 MB. Actual 2015 MB Passed
..

It works!

 Or while running DAC installation on linux

 [dac10g@slc01mmi ~]$ cd dac/Disk1

[dac10g@slc01mmi Disk1]$ sh runInstaller

Platform is Linux X86_64

You do not have sufficient permissions to access the inventory '/scratch/rj/oraInventory'. Installation cannot continue. Make sure that you have read/write permissions to the inventory directory and restart the installer.: Permission denied

 $ rm –r scratch/rj/oraInventory

 $ ./runInstaller

You do not have sufficient permissions to access the inventory '/scratch/rj/oraInventory'. Installation cannot continue. Make sure that you have read/write permissions to the inventory directory and restart the installer.: Permission denied

It wasn’t in the database dir, it was here: /etc/oraInst.loc. After doing a few oracle installs I guessed it was in /etc, but you could use find or locate to find this file.

as root:
rm /etc/oraInst.loc

 as su – dac10g

oracle reinstall error: “Installation cannot continue.

oracle reinstall error: “Installation cannot continue. Make sure that you have read/write permissions to the inventory directory…”

 

$ ./runInstaller
You do not have sufficient permissions to access the inventory '/u01/app/oraInventory'. Installation cannot continue. Make sure that you have read/write permissions to the inventory directory and restart the installer.: Permission denied

 

 

Oracle thinks there is still a oraInventory, even though I got rid of it. There is a file somewhere (not in /u01) telling oracle that oraInventory exists. So I delete the install dir (home/oracle/database) and start over:

 

$ rm -rf database/
$ unzip linux.x64_11gR2_database_1of2.zip
$ unzip linux.x64_11gR2_database_2of2.zip
$ cd database/
$ ./runInstaller
You do not have sufficient permissions to access the inventory '/u01/app/oraInventory'. Installation cannot continue. Make sure that you have read/write permissions to the inventory directory and restart the installer.: Permission denied

It wasn’t in the database dir, it was here: /etc/oraInst.loc. After doind a few oracle installs I guessed it was in /etc, but you could use find or locate to find this file.

as root:
rm /etc/oraInst.loc

 

as oracle:
$ ./runInstaller
Starting Oracle Universal Installer...

Checking Temp space: must be greater than 120 MB. Actual 9801 MB Passed
Checking swap space: must be greater than 150 MB. Actual 2015 MB Passed
..

It works!

 

 

 

Or while running DAC installation on linux

 

[dac10g@slc01mmi ~]$ cd dac/Disk1

[dac10g@slc01mmi Disk1]$ sh runInstaller

Platform is Linux X86_64

You do not have sufficient permissions to access the inventory '/scratch/rj/oraInventory'. Installation cannot continue. Make sure that you have read/write permissions to the inventory directory and restart the installer.: Permission denied

 

$ rm –r scratch/rj/oraInventory

 

$ ./runInstaller
You do not have sufficient permissions to access the inventory '/scratch/rj/oraInventory'. Installation cannot continue. Make sure that you have read/write permissions to the inventory directory and restart the installer.: Permission denied

It wasn’t in the database dir, it was here: /etc/oraInst.loc. After doing a few oracle installs I guessed it was in /etc, but you could use find or locate to find this file.

as root:
rm /etc/oraInst.loc

 

as su – dac10g

 

 

Linux New User Account

Create New User Accounts in Linux

Execute the following commands as root (using the sudo command).

Login with ROOT user

1. To find the path of useradd:

whereis useradd

2. To add the user:

sudo useradd -d directory_path username

For example:

sudo useradd -d /scratch/oracle oracle1

Or:

sudo useradd -d /scratch/fmwumbtest/ testUser

(You should create the directory on the local disk. On Linux, that means on /scratch.)

3. Then, change the password:

sudo passwd username

(You get prompted for the password.)

4. Add the user to a group (such as dba and g579):

usermod -G group_name username

5. Test the account by changing user:

su - username

(The dash means run their setup commands in the new account's root dir)

 

Removing User Accounts

On occasion, you may wish to remove a user's access from your server altogether.

If you are a Red Hat user, the easiest way to remove an unneeded user account is with the ``userdel'' command, which must be typed as ``root''. An example follows:

/usr/sbin/userdel baduser

The above command will remove the entry matching the username ``baduser from the ``/etc/passwd'', file, and, if you're using the Shadow password format (which you should be; see Section 6.6 for details), the ``/etc/shadow''.

Note: Note: The ``/etc/group'' is not modified, to avoid removing a group that other user(s) may also belong to. This isn't much of a big deal, but if this bothers use, you can edit the group file and remove the entry manually.

Should you wish to remove the user's home directory as well, add the ``-r'' option to the ``userdel'' command. For example:

/usr/sbin/userdel -r baduser

I recommend not removing an account right away, but first simply disable it, especially if you are working with a corporate server with lots of users. After all, the former user may one day require the use of his or her account again, or may request a file or two which was stored in their home directory. Or perhaps a new user (such as an employee replacement) may require access to the former user's files.

 

Examples

find -name 'mypage.htm'

In the above command the system would search for any file named mypage.htm in the current directory and any subdirectory.

find / -name 'mypage.htm'

In the above example the system would search for any file named mypage.htm on the root and all subdirectories from the root.

find -name 'file*'

In the above example the system would search for any file beginning with file in the current directory and any subdirectory.

Error while connecting to Database

[rjkm@slc01mmi dbhome_1]$ sqlplus / as sysdba

 SQL*Plus: Release 11.2.0.3.0 Production on Sun Sep 1 12:34:23 2013

 Copyright (c) 1982, 2011, Oracle.  All rights reserved.

 Connected to an idle instance.

 SQL> CREATE TABLESPACE INFA_901_TS

       DATAFILE '/scratch/rjkm/app/oradata/OBIAPPS/INFA_901_TS.dbf'

       SIZE 1024M

       EXTENT MANAGEMENT LOCAL AUTOALLOCATE;  2    3    4

     CREATE TABLESPACE INFA_901_TS

*

ERROR at line 1:

ORA-01034: ORACLE not available

Process ID: 0

Session ID: 0 Serial number: 0

 [rjkm@slc01mmi dbhome_1]$ lsnrctl start

 LSNRCTL for Linux: Version 11.2.0.3.0 - Production on 01-SEP-2013 12:38:00

 Copyright (c) 1991, 2011, Oracle.  All rights reserved.

 Starting /scratch/rjkm/app/product/11.2.0/dbhome_1/bin/tnslsnr: please wait...

 TNSLSNR for Linux: Version 11.2.0.3.0 - Production

System parameter file is /scratch/rjkm/app/product/11.2.0/dbhome_1/network/admin/listener.ora

Log messages written to /scratch/rjkm/app/diag/tnslsnr/slc01mmi/listener/alert/log.xml

Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))

Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))

 Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))

STATUS of the LISTENER

------------------------

Alias                     LISTENER

Version                   TNSLSNR for Linux: Version 11.2.0.3.0 - Production

Start Date                01-SEP-2013 12:38:02

Uptime                    0 days 0 hr. 0 min. 0 sec

Trace Level               off

Security                  ON: Local OS Authentication

SNMP                      OFF

Listener Parameter File   /scratch/rjkm/app/product/11.2.0/dbhome_1/network/admin/listener.ora

Listener Log File         /scratch/rjkm/app/diag/tnslsnr/slc01mmi/listener/alert/log.xml

Listening Endpoints Summary...

  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))

  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))

The listener supports no services

The command completed successfully

[rjkm@slc01mmi dbhome_1]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.3.0 Production on Sun Sep 1 12:41:00 2013

Copyright (c) 1982, 2011, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup

ORACLE instance started.

Total System Global Area 1820540928 bytes

Fixed Size                  2229304 bytes

Variable Size             469765064 bytes

Database Buffers         1342177280 bytes

Redo Buffers                6369280 bytes

Database mounted.

Database opened.

SQL> conn infa901/infa901

Connected.

SQL>