Oracle Bi Administration Tool 11.1.1.5

Oracle Bi Administration Tool 11.1.1.5 3,8/5 7299 votes
OBIEE 11.1.1.7.150120 on Oracle Linux 6.7 64 bit:
1. Oracle BusinessIntelligence Enterprise Edition (OBIEE) 11.1.1.7 - Common Issues Encounteredwith Installation (Doc ID 1572680.1)
2. http://docs.oracle.com/cd/E28280_01/bi.1111/e10539/toc.htm
3. Patch 20124371 Read me
Environment:
OracleLinux EL 6.7 64bit (6 GB Mem, 120 GB Storage)
/softwareNFS Mount – 120 GB
Process:

  • 1.Oracle Linux 6.7 64bit Install
  • 2.Oracle DatabaseInstall – 11.2.0.4
  • 3.OBIEE Repository RCU Install
  • 4.OBIEE 11.1.1.7.0Install
  • 5.OBIEE Patch 20124371 Application

·Oracle Linux 6.7 64 bit
·Oracle Database – 11gR4– 11.2.0.4
·OBIEE
http://www.oracle.com/technetwork/middleware/bi-enterprise-edition/downloads/bi-downloads-1923016.html
Patch – 20124371
Install Linux:
Follow the link for “How to Install Linux 6.764 bit”
Linux Requirements:
Log in as the root user.
Locate and open the following operating systemconfiguration file:
Look for or modify the following lines in thelimits.conf file:
* hardnofile65536
* hardnproc16384
If you are running Oracle Enterprise Linux 6 orRed Hat Linux 6, locate the following operatingsystem configuration file:
Make sure the same values are added to the90-nproc.conf file; otherwise, the values in the 90-nproc.conf file canoverride the values in the limits.conf file.


  • binutils-2.20.51.0.2-5.28.el6
  • compat-libcap1-1.10-1
  • compat-libstdc++-33-3.2.3-69.el6for x86_64
  • compat-libstdc++-33-3.2.3-69.el6for i686
  • gcc-4.4.4-13.el6
  • gcc-c++-4.4.4-13.el6
  • glibc-2.12-1.7.el6 forx86_64
  • glibc-2.12-1.7.el6 fori686
  • glibc-devel-2.12-1.7.el6for i686
  • libaio-0.3.107-10.el6
  • libaio-devel-0.3.107-10.el6
  • libgcc-4.4.4-13.el6
  • libstdc++-4.4.4-13.el6for x86_64
  • libstdc++-4.4.4-13.el6for i686
  • libstdc++-devel-4.4.4-13.el6
  • libXext for i386
  • libXtst for i386
  • libXi for i386
  • openmotif-2.2.3 forx86_64
  • openmotif22-2.2.3 forx86_64
  • redhat-lsb-4.0-3.el6for x86_64
  • sysstat-9.0.4-11.el6
  • zlib for i386


·Change the value ofSHMMAX to 4294967295 by including the following line in /etc/sysctl.conf:
Activate the new SHMMAX setting by running thecommand:
Start the Oracle Universal Installer andinstall your software.
·Required Locations
$mkdir oracle
$chmod 775 –R /oracle
$mkdir /oracle/oraInvenotry

·Install Oracle Database
Follow the Link for “How to Install Oracle 11gR4 Database”
Repository RCU Install:
·Before installingOracle Business Intelligence, RCU to create the Metadata Services (MDS) andBusiness Intelligence Platform (BIPLATFORM) schemas in the database.
$cd /mnt/software/obiee/rcu/bin
Welcomescreen, click Next. The CreateRepository screen opens.

CreateRepository screen, select Create andthen click Next.

Database Connection Details screen, select the type of database on the system. This is thedatabase in which you create the Oracle Business Intelligence schemas. Providethe necessary credentials for RCU to connect to the database.

Click Next.
CheckingPrerequisites screen, After the checksconclude with no errors, click OK to dismiss the screen and proceed to theSelect Components screen.

SelectComponents screen, near the top of thescreen, select Create a new Prefix. The default prefix is DEV. You can provideanother prefix, if preferred.

Oracle Business Intelligence11g Installer automatically creates schema names in the formatprefix_schemaname. For example, if you provide the prefix BI, RCU creates aschema named BI_BIPLATFORM.
Click the plus sign (+) nextto the Business Intelligence component group. Then, click Business IntelligencePlatform so that a check appears next to it. This action automatically selectsthe Metadata Services (MDS) schema (under the AS Common Schemas group), whichis also required by Oracle Business Intelligence.
Do not select the Oracle AS RepositoryComponents option, as this configures RCU to install many other schemas thatare not required by Oracle Business Intelligence. Click Next
CheckingPrerequisites screen, After the checking iscomplete with no errors, click OK to dismiss the screen and proceed to theSchema Passwords screen.

Passwordsscreen, select Use same password forall schemas, and provide and confirm a password for the schemas. Click Next


MapTablespaces screen, confirm the schemanames. Click Next




After the tablespacesare created with no errors, click OK to dismiss the screen and proceed tothe Summary screen.


Summaryscreen, click Create. The Createscreen opens and RCU creates the schemas. After the schemas are created with noerrors, the Completion Summary screen opens.

Completion Summaryscreen, click Close.



·Execute bellow command

./runInstaller -silentvalidate -response response_file_path
OBIEE INSTALL
OBIEE Architecture:
OBIEE 11.1.1.7.0 Install:
Click Next to continue.

·Install Software Updates: Specify your My Oracle Support accountinformation and software update preferences.

·Select Installation Type:Click Enterprise Install.

Click Next to continue.

·Create or Scale Out BI System:
Click Create New BI System and specifythe following:
The user name and password of the systemadministrator
The domain name for the new OracleBusiness Intelligence system

Specify the Oracle Middleware homelocation.
Domain home location
Oracle instance name

Deselect the boxes next to thecomponents that you do not want to install and configure.

Specify the database type, the databaseconnection string, and the user name and password for the Business IntelligencePlatform schema.

Specify the database type, the databaseconnection string, and the user name and password for the MDS schema.

Click one of the following options:
Auto Port Configuration: Oracle BusinessIntelligence 11g Installer configures the ports automatically.
Specify Ports Using Configuration File:Configure the ports using a configuration file that you specify. Click Browseto navigate to the configuration file and click View/Edit to view and edit it.If you edit the file, click Save to save your changes.

Specify your My Oracle Support accountinformation and security update preferences.

Verify the information on this screen.
Click Back to change the information ina previous screen.
Click Save to save the settings for theinstallation in a response file.

When the installation is 100% complete,Oracle Business Intelligence 11g Installer automatically proceeds to theConfiguration Progress screen.
·Configuration Progress:
When the configuration is 100% complete,click Next to continue.

·Complete:
Click Finish to exit Oracle BusinessIntelligence 11g Installer.

Validate Install:
Screens:

20124371 – Oracle BI EE Suite BundlePatch 11.1.1.7.150120:
Patch Stage:
·Patch20124371 is the top-level patch and it contains all of the cumulative componentpatches. This provides a single patch to download from My Oracle Support,although there are several component patches that must be installed in theOracle BI Home directory.
·Unzip patch
Following files will be extracted:
p19823874_111170_Generic.zip
p20022695_111170_Generic.zip
p19822826_111170_Linux-x86-64.zip
p19822893_111170_Generic.zip
·Patchs details
16913445-Oracle Business IntelligenceInstaller (BIINST)
19822893-Oracle Business IntelligencePublisher (BIP)
19825503-Enterprise PerformanceManagement Components Installed from BI Installer 11.1.1.7.0 (BIFNDNEPM)
19822857-Oracle Business IntelligenceServer (BISERVER)
19822826-Oracle Business IntelligencePresentation Services (BIPS)
16997936-Oracle Business IntelligenceADF Components (BIADFCOMPS)
20022695-Oracle Business IntelligencePlatform Client Installers and MapViewer
·Unzip allsub patches, Patches will ber extracted ./ 20124371/19822857
Environment Values:
-MiddlewareHome Locations - /oracle/middleware/Oracle_BI1
TMPDIR=$TMP; export TMPDIR
ORACLE_HOME=/oracle/middleware/Oracle_BI1;export ORACLE_HOME
JAVA_HOME=$ORACLE_HOME/jdk; exportJAVA_HOME
PATH=$ORACLE_HOME/OPatch:$PATH; exportPATH
Patch Conflicts:
·Check forpatch conflicts by entering the following command:
opatch prereqCheckConflictAgainstOHWithDetail -ph ./
·Examples:
[obiee@obiee Oracle_BI1]$ cd/mnt/software/OBIEE117_Linux64/20124371/16913445
[obiee@obiee 16913445]$ opatch prereqCheckConflictAgainstOHWithDetail -ph ./
[obiee@obiee 16913445]$ cd/mnt/software/OBIEE117_Linux64/20124371/19823874
[obiee@obiee 19823874]$ opatch prereqCheckConflictAgainstOHWithDetail -ph ./
[obiee@obiee 19823874]$ cd/mnt/software/OBIEE117_Linux64/20124371/19822893
[obiee@obiee 19822893]$ opatch prereqCheckConflictAgainstOHWithDetail -ph ./
[obiee@obiee 19822893]$ cd/mnt/software/OBIEE117_Linux64/20124371/16997936
[obiee@obiee 16997936]$ opatch prereqCheckConflictAgainstOHWithDetail -ph ./
[obiee@obiee 16997936]$ cd/mnt/software/OBIEE117_Linux64/20124371/20022695
[obiee@obiee 20022695]$ opatch prereqCheckConflictAgainstOHWithDetail -ph ./
[obiee@obiee 20022695]$ cd/mnt/software/OBIEE117_Linux64/20124371/19825503
[obiee@obiee 19825503]$ opatch prereqCheckConflictAgainstOHWithDetail -ph ./
[obiee@obiee 19825503]$ cd/mnt/software/OBIEE117_Linux64/20124371/19822826
[obiee@obiee 19822826]$ opatch prereqCheckConflictAgainstOHWithDetail -ph ./
[obiee@obiee 19822826]$ cd/mnt/software/OBIEE117_Linux64/20124371/19822857
[obiee@obiee 19822857]$ opatch prereqCheckConflictAgainstOHWithDetail -ph ./
[obiee@obiee 19822857]$ cd/mnt/software/OBIEE117_Linux64/16569379
[obiee@obiee 16569379]$ opatch prereqCheckConflictAgainstOHWithDetail -ph ./
·Reviewthe OPatch prerequisite report to view patches that conflict with the OracleBusiness Intelligence component patch and the patches for which the OracleBusiness Intelligence component patch is a superset.
Patch Installation:
The bifoundationserver directory.
The
  • Then run the migration tool command to setup the jar file: ./migration-tool.sh package bi-migration-tool.jar

    • [username@servername bin]$ ./migration-tool.sh package bi-migration-tool.jar

    The following message would be displayed in putty.exe:

    Logging to: /OBIEE_HOME/user_projects/domains/bi/bilogs/migration/migration-yyyy-mm-dd-hh-mi-ss.log with level INFO

    Packaging migration tool

    Created migration tool JAR: bi-migration-tool.jar

    Migration action succeded

    [username@servername bin]$

    1. In the same bin directory the JAR file named bi-migration-tool.jar will be created. Copy the JAR file into the local system using any FTP tool such as WinSCP.
    2. Copy the BI Migration Tool (bi-migration-tool.jar) from the local system to the 11g system using the same WinSCP. Here the 11g system is in Windows Platform. The JAR file should be placed under the Oracle_BI1 directory.
    3. Stop all the 11g BI Services (BI Presentation, BI Servers, BI Schedulers, BI Cluster Controllers and BI JavaHosts) from Enterprise Manager.
    4. Create a new directory in the BI11g server in the following location for the tool to put the new file (migration-tool is the new directory):

    OBIEE11G_Main_Directoryuser_projectsdomainsbifoundation_domaintmpmigration-tool

    1. Run the BI migration tool placed at: Oracle_BI1 folder to create the export bundle to be created at this temporary directory created above in the windows command prompt in the OBIEE 11g server. The command format is:

    java -jar OBIEE11G_Main_DirectoryOracle_BI1bi-migration-tool.jarout OBIEE11G_Main_DirectoryOracle_BI1

    Piya Re Piya Re - Nusrat Fateh Ali Khan Related to UK Punjabi music,Piya Re Piya Re Download Full Song Mp3 & Lyrics Sung by Nusrat Fateh Ali Khan, Piya. Listen to Nusrat Fateh Ali Khan Piya Re Piya Re MP3 song. Piya Re Piya Re song from the album Price Dil Ka Raja is released on Jan 2013. The duration of. Download piya re piya re thare bina mp3.

    OBIEE11G_Main_Directoryuser_projectsdomainsbifoundation_domain

    OBIEE11G_Main_Directoryuser_projectsdomainsbifoundation_domaintmpmigration-tool-testExport.jar

    1. Running the above commands creates the export bundle in the tmp directory created earlier.

    11. Now, copy the Export.Jar file to the local system through WinSCP and start the BI 11g services stopped earlier. That means this Export.jar file has all the upgraded files from 11g environment to 12c version. Now we have to go to the 12c BI server and deploy this jar file.

    Step 2: – Importing the bundle using OBIEE 12c Migration Tool

    1. The final step is to import this Export.jar file in the BI 12c environment for the upgrade to complete properly.
    2. Copy the Export.jar file to the following location using WinSCP: /OBIEE_HOME/user_projects/migration-tool
    3. Stop all the services in the 12c environment from Enterprise Manager.
    4. Run the BI migration tool on OBIEE 12c to import the export bundle

    /OBIEE_HOME/user_projects/domains/bi/bitools/bin/migration-tool.sh in /OBIEE_HOME//user_projects/migration-tool/Export.jar ssi

    1. It would ask for 11g RPD password. Enter the same.
    2. If the migration is successful, you will see that following message:
    1. Now restart the OBIEE services in the 12c environment from the Enterprise Manager.
    2. Connect to OBIEE analytics using weblogic credentials and check if the reports are running properly. If the upgrade is successful the reports and RPD would behave properly.

    The Catalog, RPD, and Security Model are all included in the BAR export that we can create using the exportServiceInstance() function in the WLST. One can then import these to a 12C environment using the importServiceInstance() function.

    Users

    If the users are maintained in the embedded Weblogic LDAP, one must export them and then re-import them. This process can be done manually or through the WLST using the Current Management Object. If users are maintained through an external Active Directory source, then the configurations will be pulled in with the Security Model in the BAR file. Chitra tamil songs.

    Vbsedit serial key. We need additional contents like a custom style/skin or deployments on the Weblogic Server, configurations, etc. to be deployed/separately than the upgrade process. It is not included in this post as they are not mandatory steps for the upgrade to take place.

    Finally, to make sure the upgrade was successful we use the Oracle’s new Baseline Validation Tool. This is included in OBIEE 12C, and is used to test migrations between environments. The basic steps are:

    • Configure and run the Baseline Validation Tool against the 11g code- before upgrade.
    • Keep the test results.
    • Perform the upgrade.
    • Run the Baseline Validation Tool again to gather the new output, and display the compared results.

    The output will be an HTML file that will let you know what has changed since the last time. Proper upgrade will ensure no major differences.

    1. Existing working 11g environment won’t be messed up with old or deprecated scripts/directories. It will remain the same.
    2. For in place upgrade process multiple upgraded over the years will unnecessary increase the number of unused/deprecated scripts and files. Out of place Upgrade eliminates this risk.
    3. New bugs may appear or old ones may reappear in upgraded environments due to patching of old environments. OOP upgrade is usually free from these kind of issues.