Wednesday, April 15, 2015

Purge OBIEE Cache Using Oracle Data Integrator Automatically when Load Completes


Purge OBIEE Cache Using Oracle Data Integrator Automatically when Load Completes


Step 1:  Create file purge.txt and write  CALL SAPURGEALLCACHE();  and save the file in below Location
C:\OBIEE_HOME\instances\instance1\bifoundation\OracleBIApplication\coreapplication\setup
Step 2: Create a Shell Script purgecache.sh and save it any location or in Custom scripts location and insert below Unix code in purge.sh file, this code will clear both Presentation Server and Query Cache
#!/bin/bash
#Script to purge the cache

#Declare variables
SETUP_DIR=$/u01/app/biapps/instances/instance1/bifoundation/OracleBIApplication/coreapplication/setup
NQCMD_DIR=$/u01/app/biapps/Oracle_BI1/bifoundation/server/bin
RUNCAT_DIR=$/u01/app/biapps/instances/instance1/bifoundation/OracleBIPresentationServicesComponent/coreapplication_obips1/catalogmanager
LOG_FILE=$/u01/app/biapps/Oracle_BI1/logs/purgecache.log
CAT_URL=http://bi-dev2:9704/analytics/saw.dll?
USR_NM=`awk -F”=” ‘{print $2}’ $SETUP_DIR/catmancredentials.properties|xargs|cut -d’ ‘ -f1`;
PASS=`awk -F”=” ‘{print $2}’ $SETUP_DIR/catmancredentials.properties|xargs|cut -d’ ‘ -f2`;

#Initialize the environment
source $SETUP_DIR/bi-init.sh;

#Run Server cache Purge command
$NQCMD_DIR/nqcmd -d AnalyticsWeb -u $weblogic -p $Admin123 -s $SETUP_DIR/purgecache.txt -o $LOG_FILE;

#Run Web Cache Purge command
$RUNCAT_DIR/runcat.sh -cmd clearQueryCache -online $CAT_URL -credentials $SETUP_DIR/catmancredentials.properties >> $LOG_FILE;

SUCCESS_FLG=`grep -E ‘Operation SAPurgeAllCache succeeded|Cleared the query cache successfully’ $LOG_FILE|wc -l`;

if [ $SUCCESS_FLG = 2 ]
then
        echo “———————————————-“;
        echo “Cleared Server and Web cache successfully”;
        echo “———————————————-“;
else
        echo “Error clearing cache. Please check the log file: $LOG_FILE”;
fi

Step 3:
 Create ODi Package and call OS Command 1:










Step 4: Click on OS Command 1 and go to Properties and enter the command








Step 5: Generate Scenario








Call the Scenario in the Last task of Load Plan and Regenerate the Load Plan, This will Purge the OBIEE cache immediately after Load completes automatically

Saturday, April 4, 2015

How to clear the BI Server cache using OBIEE Issue SQL page


How to clear the BI Server cache using  OBIEE Issue SQL page

Login to OBIEE Analytics: http://localhost:9704/analytics  Using Administrator User name and Password

Click on Administration








Go to Maintenance and Trouble shooting and liik for Issue SQL










Click on Issue SQL and Write Purge Code











Execute it you need to get the below result















Friday, April 3, 2015

Steps for ODI Migration from One Environment to other


Steps for Code Migration from DEV to other Environment


(On Target Environment) Take backup of Security Settings and ODI Repository.

·         ODI Repository: Backup the target ODI repository by taking a database dump of the ODI repository schema using Oracle Database export utility.

·         Security Backup: Similarly, you may backup just the security metadata from the target ODI repository. To do this, invoke the security export dialog as  shown below.









































































\And Now Click on “Export”.


STEP 5 : On Source Environment: Now, login to the ODI repository in the source environment from ODI Studio. Export the customized objects using Smart Export by clicking on the icon on the top right of the Designer tab and choosing “Export…” as shown. Then choose “Smart Export” in the dialog that pops up.
















When you drag the objects into the Smart Export, the dependent objects are computed and automatically dragged in as well. For example, when task folders containing interfaces are dragged in, the data stores corresponding to the interfaces are automatically dragged in. Thus, if you have changed an interface and the corresponding target data store, it is enough to drag the interface/task folder and the data store will be automatically exported. After you drag and drop the required objects into the smart export window, you can review what is going to be exported including the dependent objects before executing the export.

Note: When dragging and dropping mapping folders, you may be asked for a confirmation whether to automatically add all objects with the same release tag; in this case, select NO.










On Target Environment: Copy the export files to a drive on the target machine. Log in to the ODI repository in target environment from ODI Studio. Invoke the “Import” -> “Smart Import” option by clicking on the same icon on the top right of the Designer tab. Select the file to be imported; in case of multiple files to be imported, select the files one at a time in the same sequence as they were exported.



Verify Things and Click “Next”  and then Click on “Finish” .

Click Next and  review the import before submitting. Complete the import.

 On Target Environment Now Import topology settings which we have taken in STEP 4 Now, you need to import the topology settings from the backup taken in step 4. For this, click on “Import” from topology navigator and  then “Smart Import”. Select the xml file that was created in step 4 and complete the import.





Review and Close.

Go to “Topology” then “Physical Architecture” then “Oracle” then “BIAPPS_ODIREP” and Double Click on it.





























2: Go to “Definition” tab and now you will see the User and Password box.
If these details are not there then put the right credentials as below.



















3: Then go to “JDBC” tab and check JDBC Driver and JDBC URL details. If these details are not present then put these details.









4:  Now Click on “Test Connection”






























Check Default Checkbox is enabled for all physical schema or not ?

1) Connect to the ODI repository using ODI client

2)  Navigate to ODI > Topology > Physical Architecture > Technologies >  Oracle and Expand  BIAPPS_BIACOMP ( CM Read only Data server used for ETL ) data server.

3) Click on Physical schema registered under this data server.

4) Check for Default check box option is selected or not.

 If not please check this option and save the physical schema changes.

5). Each of the Datawarehouse (DW), ODI_REP or BIACM data servers should have a default data schema.
So, if not already done, perform the above steps for DW data server as well

Wednesday, April 1, 2015

Renumbering ODI Repositories


Steps for Renumburing ODI Repositories

Step 1:   (On Target) renumbering a repository consists of changing the repository ID and the internal ID of the       objects stored in the repository. Renumbering a repository is advised when two repositories have been created with the same ID. Renumbering one of these repositories allows object import/export between these repositories without object conflicts.

Renumbering a Master Repository

1.       In the Topology Navigator, go to the Repositories panel. 


















2.       Expand the Master Repository’s node and right-click the master repository you want to renumber.


















 3: Select Renumber and In the Renumbering the Repository - Step 1 dialog click Yes








4: In the Renumbering the Repository - Step 2 dialog enter a new and unique ID for the master repository and click OK.









5: . The master repository and all the details stored in it such as topology, security, and version management details are renumbered.









Renumbering a Work Repository

To renumber a work repository:
1.       In the Topology Navigator, go to the Repositories panel.
2.       Expand the Work Repositories node and right-click the work repository you want to renumber.
3.       Select Renumber...
















4.       In the Renumbering the Repository - Step 1 dialog click Yes.











5: Enter a new and unique ID for the work repository and click OK.









6. The work repository and all the objects attached to it are renumbered.
7. The master repository and all the details stored in it such as topology, security, and version management details are renumbered.

Step 2:   (On Target) After renumbering the repository, the ODI J2EE agent, “oraclediagent” needs to be restarted. For this, login to WLS Admin Console (E.g  http://localhost:7001/console)
Click on Deployments from the Domain structure tree and navigate to “oraclediagent”. Select the checkbox beside it and select “Stop -> Force Stop Now” option from the top.





















Navigate again to “oraclediagent”, check the box and select “Start -> Servicing all requests” to restart.

















Navigate again to “oraclediagent”, check the box and select “Start -> Servicing all requests” to restart.