OID 11g High Availability

OID 11g 11.1.1.7.0 cluster http://docs.oracle.com/cd/E17904_01/core.1111/e10106/imha.htm#CDEJEEGG

Troubleshooting OBIA 11.1.1.7.1

Doc ID … Installing Oracle BI Applications 11.1.1.7.1 – Troubleshooting and Frequently Asked Questions (Doc ID 1589540.1)

WEBLOGIC 12C FEATURES

On December 1st, Oracle has held an online event to launch the new Weblogic Server 12c, the foundation for the future generation of Fusion Middleware products. Along with 200 new features, this release brings cloud computing capabilities, hence the “c” in 12c, an even tighter integration with the Oracle Database and integration with some new Oracle products, that have just been announced. Below you will find some of the new features that were mentioned during the live launch event: •Oracle Traffic Director, is a new released product, that will offer HTTP requests caching, a reverse proxy function and load-balancing based on other algorithms than just round-robin. It will completely replace Oracle WebCache, and while it will also eliminate the need for the Weblogic web server plugins for fronting a Weblogic cluster, the plugins will still be supported by Oracle for integrating with third party web servers such as Apache, IIS etc. However, the Oracle Traffic Director will initially be available only on the Exalogic platform!! •Oracle Virtual Assembly Builder is another new product announced by Oracle which will allow users to package a multi tier application into a consolidated project and move it easily into a virtual box for development, functional testing or just to accomodate a new developer joining the project, without having to build a new system. So for example if an application has a web module, but also uses Oracle Service Bus and Oracle Database, you can assemble all these into one package and use it on an Oracle VM machine. •The integration between the Weblogic server and Oracle RAC database is even tighter in the new release, by the use of the Active Grid Link, which now introduces session/transaction affinity with the RAC node. This new feature will bring a 3x boost in performance. Actually, that is one of the new strong selling points of the Weblogic Server 12c, which promises to bring important performance improvements. •In the new version, there is also a tighter integration with the Glassfish application server, since now Weblogic will be able to recognize Glassfish deployment descriptors. As a consequence an application that has been developed for Glassfish and deployed on that environment can easily be migrated on a Weblogic platform by a simple re-deploy. Of course, this is subject to discussion depending on the application’s security model for example, since that will have to be accomodated for the Weblogic Security Framework. •Another good news for Weblogic administrators and developers as well is an integration between the Weblogic Diagnostic Framework (WLDF) and JRockit’s Flight Recording functionality which promises to be a big step forward in troubleshooting and performing complex diagnostics on the applications. For Developers, there are good news as well, some of the most noticeable are mentioned below: •Full support for Java EE 6, Java SE 7, HTML5 (by fully supporting annotations, the xml lines in an application can be reduced to up to 80%) •Oracle is launching ADF Mobile which brings a consolidated platform for developing applications which are to be consumed from devices running any mobile platform such as Android, iOS etc •Just for Development or testing purposes, Weblogic will now shift in a super lightweight version (only 168Mb) that will download, unzip and start without the need of running an installer. Even more, one will have the option to start the Weblogic server without the EJB, JMS and JCA containers if only a basic functionality is needed, simply by adding -Dservertupe=wlx to the startup parameters. •In the new release, EJBs can now be packaged directly into war files, eliminating the need for them to be packaged into jar files and then ear files. There are no noticeable differences in the look and feel of the Administration console, and all administrative resources remain the same. The domain upgrade from 11g to 12c is seamless, since a 11g domain will run without any modifications on 12c. Weblogic Server 12c will be available for download in the following days on OTN and all other Fusion Middleware products such as SOA Suite, Identity Management, Webcenter etc will follow during CY2012 and CY2013. http://oraclemiddlewareblog.com/2011/12/02/whats-new-in-oracle-weblogic-server-12c/

Oracle Business Intelligence Applications 11.1.1.7.1 default OracleBIApps.rpd password is Admin123

Default OracleBIApps.rpd password is Admin123

Starting Stopping Weblogic Admin Server Managed Server using WLST with and with out Node Manager

Managing the Server Life Cycle During its lifetime, a server can transition through a number of operational states, such as shutdown, starting, standby, admin, resuming, and running. For more information about the server life cycle, see "Understanding Server Life Cycle" inManaging Server Startup and Shutdown for Oracle WebLogic Server. The following sections describe how to use WebLogic Scripting Tool (WLST) to manage and monitor the server life cycle: Using WLST and Node Manager to Manage Servers Starting and Managing Servers Without Node Manager For information on other techniques for starting and stopping server instances, see "Starting and Stopping Servers" in Managing Server Startup and Shutdown for Oracle WebLogic Server. Using WLST and Node Manager to Manage Servers Node Manager is a utility that enables you to control the life cycles of multiple servers through a single WLST session and a single network connection. (It can also automatically restart servers after a failure.) For more information about Node Manager, see the Node Manager Administrator's Guide for Oracle WebLogic Server. You can use WLST to do the following with Node Manager: Start a Node Manager. Connect to a Node Manager, then use the Node Manager to start and stop servers on the Node Manager machine. See Figure 4-1. Figure 4-1 Starting Servers on a Machine Description of Figure 4-1 follows Description of "Figure 4-1 Starting Servers on a Machine" A Node Manager process is not associated with a specific WebLogic domain but with a machine. You can use the same Node Manager process to control server instances in any WebLogic domain, as long as the server instances reside on the same machine as the Node Manager process. For information about the commands that WLST can use while acting as a Node Manager client, see "Node Manager Commands" in WebLogic Scripting Tool Command Reference. Connect to an Administration Server, then use the Administration Server to start and stop servers in the domain. See Figure 4-2. Figure 4-2 Starting Servers in a WebLogic Domain Description of Figure 4-2 follows Description of "Figure 4-2 Starting Servers in a WebLogic Domain" In this case, WLST is a client of the Administration Server, and the Administration Server uses one or more Node Managers to start Managed Servers. For information about the life cycle commands that WLST can use while acting as an Administration Server client, see "Life Cycle Commands" in WebLogic Scripting Tool Command Reference. Using Node Manager to Start Servers on a Machine WLST can connect to a Node Manager that is running on any machine and start one or more WebLogic Server instances on the machine. A WebLogic domain's Administration Server does not need to be running for WLST and Node Manager to start a server instance using this technique. To connect WLST to a Node Manager and start servers: Configure Node Manager to start servers. See "General Node Manager Configuration" in the Node Manager Administrator's Guide for Oracle WebLogic Server. Start WLST. Start Node Manager. Usually, as part of configuring Node Manager, you create a Windows service or a daemon that automatically starts Node Manager when the host computer starts. See "Running Node Manager as a Service" in the Node Manager Administrator's Guide for Oracle WebLogic Server. If Node Manager is not already running, you can log on to the host computer and use WLST to start it: wls:/offline> startNodeManager() For more information about startNodeManager, see "startNodeManager" in WebLogic Scripting Tool Command Reference. Connect WLST to a Node Manager by entering the nmConnect command. wls:/offline>nmConnect('username','password','nmHost','nmPort', 'domainName','domainDir','nmType') For example, nmConnect('weblogic', 'welcome1', 'localhost', '5556', 'mydomain','c:/bea/user_projects/domains/mydomain','SSL') Connecting to Node Manager ... Successfully connected to Node Manager. wls:/nm/mydomain> For detailed information about nmConnect command arguments, see "nmConnect" in WebLogic Scripting Tool Command Reference. Use the nmStart command to start a server. wls:/nm/mydomain>nmStart('AdminServer') starting server AdminServer ... Server AdminServer started successfully wls:/nm/mydomain> Monitor the status of the Administration Server by entering the nmServerStatus command. wls:/nm/mydomain>nmServerStatus('serverName') RUNNING wls:/nm/mydomain> Stop the server by entering the nmKill command. wls:/nm/mydomain>nmKill('serverName') Killing server AdminServer Server AdminServer killed successfully wls:/nm/mydomain> For more information about WLST Node Manager commands, see "Node Manager Commands" in WebLogic Scripting Tool Command Reference. Using Node Manager to Start Managed Servers in a WebLogic Domain or Cluster To start Managed Servers and clusters using Node Manager: Configure Node Manager to start servers. See "General Node Manager Configuration" in the Node Manager Administrator's Guide for Oracle WebLogic Server. Start WLST. Start Node Manager. Usually, as part of configuring Node Manager, you create a Windows service or a daemon that automatically starts Node Manager when the host computer starts. See "Running Node Manager as a Service" in the Node Manager Administrator's Guide for Oracle WebLogic Server If Node Manager is not already running, you can log on to the host computer and use WLST to start it: wls:/offline> startNodeManager() For more information about startNodeManager, see "startNodeManager" in WebLogic Scripting Tool Command Reference. Start an Administration Server. Connect WLST to the Administration Server instance using the connect command. wls:/(offline)> connect('username','password') Connecting to weblogic server instance running at t3://localhost:7001 as username weblogic ... Successfully connected to Admin Server 'myserver' that belongs to domain 'mydomain'. Warning: An insecure protocol was used to connect to the server. To ensure on-the-wire security, the SSL port or Admin port should be used instead. wls:/mydomain/serverConfig> For detailed information about connect command arguments, see "connect" in WebLogic Scripting Tool Command Reference. Do any of the following: To start a Managed Server, enter the following command, where managedServerName is the name of the server. start('managedServerName','Server') To start a cluster, enter the following command, where clusterName is the name of the cluster. start('clusterName','Cluster') For more information, see "start" in WebLogic Scripting Tool Command Reference. Starting and Managing Servers Without Node Manager The following sections describe starting and managing server state without using the Node Manager: Starting an Administration Server Without Node Manager Managing Server State Without Node Manager If you do not use Node Manager, WLST cannot start Managed Servers. For information on other techniques for starting and stopping server instances, see "Starting and Stopping Servers" in Managing Server Startup and Shutdown for Oracle WebLogic Server. Starting an Administration Server Without Node Manager To start an Administration Server without using Node Manager: If you have not already done so, use WLST to create a WebLogic domain. For more information, see Chapter 3, "Creating WebLogic Domains Using WLST Offline" Open a shell (command prompt) on the computer on which you created the domain. Change to the directory in which you located the domain. By default, this directory is MW_HOME\user_projects\domains\domain_name, where MW_HOME is the top-level installation directory of Oracle WebLogic products. Set up your environment by running one of the following scripts. bin\setDomainEnv.cmd (Windows) bin/setDomainEnv.sh (UNIX: Oracle recommends that you run this script from the Korn shell.) On Windows, you can use a shortcut on the Start menu to set your environment variables and invoke WLST (Tools > WebLogic Scripting Tool). Invoke WLST by as described in Invoking WLST. The WLST prompt appears. wls:/(offline)> Use the WLST startServer command to start the Administration Server. startServer([adminServerName], [domainName], [url], [username], [password],[domainDir], [block], [timeout], [serverLog], [systemProperties], [jvmArgs] [spaceAsJvmArgsDelimiter]) For detailed information about startServer command arguments, see "startServer" in WebLogic Scripting Tool Command Reference. For example, wls:offline/>startServer('AdminServer','mydomain','t3://localhost:7001', 'weblogic','welcome1','c:/bea/user_projects/domains/mydomain', 'true',60000,'false') After WLST starts a server instance, the server runs in a separate process from WLST; exiting WLST does not shut down the server. Managing Server State Without Node Manager WLST life cycle commands enable you to control the states through which a server instance transitions. See "Life Cycle Commands" in WebLogic Scripting Tool Command Reference. Oracle recommends that you enable and use the WebLogic domain's administration port when you connect to servers and issue administrative commands. See Securing the WLST Connection. The commands in Example 4-1 explicitly move a server instance through the following server states: RUNNING->ADMIN->RUNNING->SHUTDOWN. Start WebLogic Server before running this script. Example 4-1 WLST Life Cycle Commands # Connect to the Administration Server connect("username","password","t3://localhost:7001") # First enable the Administration Port. This is not a requirement. # After you enable the Administration Port in a domain, WebLogic Server # persists the setting in its configuration files. You do not need to repeat # the process in future WLST sessions. edit() startEdit() cmo.setAdministrationPortEnabled(1) activate(block="true") # check the state of the server state("myserver") # now move the server from RUNNING state to ADMIN suspend("myserver", block="true") # check the state state("myserver") # now resume the server to RUNNING state resume("myserver",block="true") # check the state state("myserver") # now take a thread dump of the server threadDump("./dumps/threadDumpAdminServer.txt") # finally shutdown the server shutdown(block="true")

Applying Platform Patches for OBIA 11.1.1.7.1

This is an important step to avoid the BI Apps configuration failure irrespective of what type OBIEE installation (software only / Enterprise) you did Applying Platform Patches You must apply Fusion Middleware platform patches. The patches are available for download as part of the Oracle Business Intelligence Applications 11.1.1.7.1 media pack. You will run a script to apply the patches. The script is a Perl script and is available in /biapps/tools/bin/APPLY_PATCHES.pl. Note: When installing and running the Perl script, note the following: For installations on Windows, the perl script uses the WinZip utility to extract the contents of the individual patches. If WinZip is not installed on the machine, then you must use install 7-zip and update the script to use it as follows: 1.Download and install 7-zip in C:\Program Files. 2.Open the APPLY_PATCHES.pl file using a text editor. 3.Modify the following lines in the download_patch routine. From: $DOWNLOAD_EXE = "\"C:${DIRSEP}Program Files${DIRSEP}WinZip${DIRSEP}wzunzip.exe\" -ybc -d"; $cmd = "$DOWNLOAD_EXE $_[0] $PATCHES_HOME"; To: $DOWNLOAD_EXE = "\"C:${DIRSEP}Program Files${DIRSEP}7-Zip${DIRSEP}7z.exe\""; $cmd = "$DOWNLOAD_EXE x $_[0] -o$PATCHES_HOME"; 4.Save and close the file. The Perl script you will run to apply the patches requires a parameter input file (apply_patches_import.txt). In this procedure, before you run the Perl script, you will update the parameter input file to reflect the appropriate directory paths. To apply platform patches: 1.If Oracle BI EE was installed in Enterprise Install mode, then shut down WebLogic Administration Server, Managed Server, and Node Manager. Shut down BI processes using Oracle Process Manager and Notification Server (OPMN). If you installed Oracle BI EE in Software Only mode, then skip this step. 2.Download "Oracle Fusion Middleware Platform Patches for Oracle Business Analytics Applications Suite" from the Oracle Business Intelligence Applications 11.1.1.7.1 media pack on Oracle Software Delivery Cloud, as follows: Download the following three parts from the Oracle Business Intelligence Applications 11.1.1.7.1 Media Pack and unzip them into the same directory location: ◦Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence Applications (Part 1 of 2) ◦Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence Applications (Part 2 of 2) ◦Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence Applications for 3.Extract the ZIP file or files into a Patch Home directory, as follows: Extract the contents of the three downloaded zip files containing the patches into the same directory, for example, C:\patches or PATCH_HOME/patches. Note: The directory structure of the extracted contents is not patches4fa/dist/ps6rc3. The patches are contained in folders: biappsshiphome, odi, weblogic and oracle_common. You do not have to unzip the individual patches. 4.Update the parameter input file (apply_patches_import.txt) to reflect the paths as specified in the text file: a.Create a writable directory where logs and temporary patch files will be stored. In the apply_patches_import.txt file, you will set the WORKDIR= variable to point to the path for this directory. b.Open apply_patches_import.txt, which is located in the /biapps/tools/bin directory. c.Specify the following directory paths: Directory Path JAVA_HOME Path of the JDK you installed for your platform. INVENTORY_LOC Path of the Oracle\Inventory directory. For example: C:\Program Files\Oracle\Inventory. ORACLE_HOME Path of the Oracle Home for BI directory. MW_HOME Path of the Oracle Middleware Home directory. COMMON_ORACLE_HOME Path of the oracle_common directory, which is under the Middleware Home directory. WL_HOME Path of the Oracle WebLogic Server Home directory. ODI_HOME Path of the ODI Home directory. WORKDIR Path of a writable directory where logs and temporary patch files are stored. PATCH_ROOT_DIR Path of the patch directory. For example: C:\patches or, PATCH_HOME/patches 5.Run the following command to apply the patch: $ perl APPLY_PATCHES.pl For example: perl /biapps/tools/bin/APPLY_PATCHES.pl /biapps/tools/bin/apply_patches_import.txt Note: This script can be run from any location if Perl is set in the path variable. If Perl is not set in the path variable, run the script from the following location: /perl/bin> 6.Confirm that all patches have been applied successfully by reviewing the following log files in the directory specified by WORDIR: ◦final_patching_report.log (summary of patch application) ◦biappshiphome_generic_patches.log ◦biappshiphome__patches.log ◦odi_generic_patches.log ◦oracle_common_generic_patches.log ◦weblogic_patching.log Note: The WebLogic Server patches are for WebLogic Server 10.3.6. Therefore, if you have WebLogic Server 10.3.5 installed, the patches will not be installed in your environment, and you will not see the weblogic_patching.log file. Also, the final patching report will show the WebLogic Server patches have failed. You can ignore the WebLogic Server patch failures. 7.If Oracle BI EE was installed in Enterprise Install Mode, then start WLS Admin Server, Managed Server and Node Manager. Start the BI processes using OPMN. If you installed Oracle BI EE in Software Only mode, then skip this step.

Oracle Fusion Middleware required Schemas while executing RCU

Be very carefull in the versions while downloading the RCU .. For Example ,If you are using OAM 11.1.2.1.0 you should download the RCU version 11.1.2.1.0 .. Repository Creation Utility Schemas, IDs, and TablespacesThis appendix lists the available schemas that can be created using RCU, and also their component IDs and dependencies. Table B-1 lists the schemas along with their component IDs, tablespace mappings, and dependencies. The "Schema Owner" is the name of the schema that you will see in RCU and is also the name you must provide in the Fusion Middleware Configuration Wizard on the Configure JDBC Component Schema screen. The "Component ID" is the value you must specify with the -component parameter when you are creating or dropping schemas using the command line. Note: Not all schemas are supported on all database types. For more information, refer to "Repository Creation Utility (RCU) Requirements" in the Oracle Fusion Middleware System Requirements and Specifications document. Table B-1 Schema Component IDs, Tablespace Mappings, and Dependencies Component Schema Owner Component ID Default Tablespace Temp Tablespace Dependencies AS Common Schemas Metadata Services MDS MDS MDS IAS_TEMP None Audit Services IAU IAU IAS_IAU IAS_TEMP None Audit Services for OES IAUOES IAUOES IAS_IAUOES IAS_TEMP None Enterprise Scheduler Service ORAESS ORAESS ORAESS IAS_TEMP None Oracle Platform Security Services OPSS OPSS IAS_OPSS IAS_TEMP Metadata Services (MDS) Identity Management Schemas Oracle Internet Directory ODS OID OLTS_DEFAULT IAS_TEMP None Oracle Identity Federation OIF OIF IAS_OIF IAS_TEMP None Oracle Identity Manager OIM OIM OIM OIM_TEMP Metadata Services (MDS) SOA Infrastructure (SOAINFRA) User Messaging Service (ORASDPM) Oracle Access Manager OAM OAM OAM OAM_TEMP Audit Services (IAU) Oracle Adaptive Access Manager OAAM OAAM BRSADATA BRSATEMP Metadata Services (MDS) Oracle Adaptive Access Manager (Partition Support) OAAM_PARTN OAAM_PARTN TBS_OAAM_DATA TBS_OAAM_TEMP Metadata Services (MDS) Oracle Entitlements Server APM APM APM APM_TEMP Metadata Services (MDS) WebCenter Content Schemas Oracle Information Rights Management ORAIRM IRM ORAIRM ORAIRM_TEMP None Oracle WebCenter Content Server - Complete OCS CONTENTSERVER11 OCS OCS_TEMP None Oracle WebCenter Content Server - Search Only OCSSEARCH CONTENTSERVER11SEARCH OCSSEARCH OCSSEARCH_TEMP None Oracle WebCenter Content: Records URMSERVER URM URMSERVER URMSERVER_TEMP None Oracle WebCenter Content: Imaging IPM IPM IPM IPM_TEMP None Oracle Data Integrator Schemas Master and Work Repository ODI_REPO ODI ODI_USER ODI_TEMP None Oracle Business Intelligence Schemas Business Intelligence Platform BIPLATFORM BIPLATFORM BIPLATFORM BIPLATFORM_TEMP Metadata Services (MDS) WebLogic Communication Services Schemas Presence ORASDPXDMS ORASDPXDMS IAS_ORASDPXDMS IAS_TEMP Metadata Services (MDS) SIP Infrastructure Subscriber Data Service (ORASDPSDS) SIP Infrastructure Location Service (ORASDPLS) User Messaging Service (ORASDPM) SIP Infrastructure Subscriber Data Service ORASDPSDS ORASDPSDS IAS_ORASDPSDS IAS_TEMP Metadata Services (MDS) SIP Infrastructure Location Service (ORASDPLS) SIP Infrastructure Location Service ORASDPLS ORASDPLS IAS_ORASDPLS IAS_TEMP Metadata Services (MDS) SIP Infrastructure Subscriber Data Service (ORASDPSDS) SOA and BPM Infrastructure Schemas SOA Infrastructure SOAINFRA SOAINFRA SOAINFRA IAS_TEMP Metadata Services (MDS) User Messaging Service (ORASDPM) Business Activity Monitoring ORABAM BAM ORABAM IAS_TEMP Metadata Services (MDS) User Messaging Service (ORASDPM) User Messaging ORASDPM ORASDPM IAS_ORASDPM IAS_TEMP Metadata Services (MDS) WebCenter Portal Schemas Portlet Producers PORTLET PORTLET IAS_PORTLET IAS_TEMP None Spaces and Services WEBCENTER WEBCENTER IAS_WEBCENTER IAS_TEMP Metadata Services (MDS) Discussions DISCUSSIONS DISCUSSIONS IAS_DISCUSS IAS_TEMP None Activity Graph and Analytics ACTIVITIES ACTIVITIES IAS_ACTIVITY IAS_TEMP None Portal and Business Intelligence Schemas Discoverer DISCOVERER DISCOVERER DISCO_PTM5_META IAS_TEMP None Portal PORTAL PORTAL PORTAL IAS_TEMP Portlet Producers (PORTLET) Enterprise Performance Management Schemas Registry EPM EPMREGISTRY EPM IAS_TEMP None

weblogic 10.3.6 hangs at 55 % during installation

During the installation of weblogic 10.3.6 if it hangs at 55% It will be due to wrong JAVA_HOME . In Solaris it should be as follows .Use the default jdk 1.7 which comes with the OS apdidm@tidmapp01:~$ which java /usr/bin/java apdidm@mtidmapp01:~$ java -d64 -version java version "1.7.0_45" Java(TM) SE Runtime Environment (build 1.7.0_45-b18) Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode) apdidm@mof-tidmapp01:~$

Delete a Weblogic Domain

Delete a Domain To remove the "testDomain" domain we just created, do the following steps: •Stop the processes associated with the domain. •Remove the relevant domain entry from the "$MW_HOME/domain-registry.xml" file. •Remove the relevant domain entry from the "$WLS_HOME/common/nodemanager/nodemanager.domains" file. #Domains and directories created by Configuration Wizard #Thu Aug 23 22:53:14 BST 2012 testDomain=/u01/app/oracle/middleware/user_projects/domains/testDomain•Delete the "testDomain" application and domain directories. $ rm -Rf $MW_HOME/user_projects/applications/testDomain $ rm -Rf $MW_HOME/user_projects/domains/testDomain

RCU:6107 DB Init Param Error

While Installing Repository Creation Utility (RCU) Installation the following error occurs: RCU:6107 DB Init Param Error This can be removed simply by the following: 1. Login on your database with system user. 2. Write > show parameters processes (which will show the current value of processes). 3. If its value is less than 500 then write the following command: ALTER SYSTEM SET PROCESSES=500 SCOPE=SPFILE; 4. Write > show parameters open_cursors (which will show the current value of open_cursors). 5. If its value is less than 500 then write the following command: ALTER SYSTEM SET OPEN_CURSORS=500 SCOPE=SPFILE; 6. Restart your DB or system. 7. Start the installation now…. There will be no error…..

How to create DSN in windows 8

https://blogs.oracle.com/ExalyticsOBIEE/entry/obiee_11g_excel_connectivity_using OBIEE 11g:Excel Connectivity Using ODBC Drivers By Saresh on Apr 09, 2013 This blog describe the method to connect Excel to BI Server using ODBC. For this you dont need to use the Analytics. You can use Excel to create the report by connecting to BI server using ODBC Datasource. Two steps to achieve this are: Create a system DSN Create the report using Microsoft Query. Step 1: Create the system DSN 1.Go to Control Panel->Administrative Tools->Data Sources (ODBC)->System DSN 2. Select Oracle BI Server and Click Add 3.Click on Finish and enter a name for your DSN and enter the BIServer name and click finish Now your BI Server DSN Configuration is done. Step 2. Create the report using Microsoft Query. 1. Open the Excel and Click on Microsoft Excel->Data->From Data Sources->From Microsoft Query 2. Select the DSN name you created above and enter the credentials to log in to BI Server. 3. A new screen to choose column will appear. 4. Drill down on the dimensions and select the required tables as shown below: 5. If you get a message like below, click on OK 6. Clicking OK will take you to the screen shown below: 7. Click on Add Tables icon from the menu. This will allow you to select the tables that you want in your report. For example, 7.1. In this case we are using Sample Sales lite rpd and we will add the fact table Base Facts (click on Add) 7.2. Base fact will be added to Microsoft query. Drag Actual Unit Price from ‘query from …’ section to the Result pane header. (Note the difference in screenshot from step 6) 8. Close the window for ‘Microsoft Query’. Now ‘Import Data’ wizard will open. 9. Select the type of table you wanted. (In this example we have used the pivot table report) a.Drag Product to Drop Row Field Here b.Time to Drop columns Field Here c.Actual unit price to Drop Data Items here. d.The report will be generated in excel like below:

Creating a Repository Using the Oracle Business Intelligence Administration Tool

http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi1113/biadmin11g_01/biadmin11g.htm

Oracle Business Intelligence Developer Client Tool 11.1.1.7.1

Download BI Admin tool for 32 bit if you are using 64bit OS . Right click on the installer proerties and change the compatability to windows 7.. http://shivabizint.wordpress.com/2010/08/24/obiee-11g-rpd-is-not-opening-in-windows-64-bit-machine/ You need to install a patch : BISHIPHOME_11_1_1_7_0_GENERIC_130409_1210_16492220.zip to get the things working. Download link : http://download.oracle.com/otn/nt/bi/111171/BI_Apps_11.1.1.7.1_generic_part_1of2.zip extract and install just the above patch. After you apply the patchset from oracle to turn Oracle OBIEE 11.1.1.7.0 to 11.1.1.7.131017, go to FusionMiddlewareHome/Oracle_BI1/clients/biserver -->> biee_client_install.exe / biee_client_install_x64.exe and use that to Install on top of the older Client Tools version 11.1.1.7.0. The installer will then update your Client Tools from version 11.1.1.7.0 to 11.1.1.7.131017. There will be no need to download BISHIPHOME_11_1_1_7_0_GENERIC_130409_1210_16492220.zip to get the things working. You already have everything you need within the OBIEE location provided above.