Oracle BI Catalog Merging

Ok, now let's talk about migrate catalog of Oracle BI. There was an issue when I wanted to 'merge' or migrate catalog from one server to another. Here some ways to merge the catalogs


• Upgrade catalog
• Archive Unarchive
Details:
a. Find active catalog:
- In folder OracleBIData\web\config, find instanceconfig.xml file.
- Active catalog is referred to in tag .

b. Copy the catalog to desired location (for merging). In our case we should have two offline catalogs; development and production. It is better to put both catalogs on the same machine, related to performance when merging.

c. Choose one of the following ways to merge

d. Upgrade catalog
- Open Catalog Manager
- Open offline one of the catalogs


- Select Tools then Upgrade Catalog


- Choose Original Presentation Catalog and Modified Presentation Catalog. If one of the catalogs is original (has no changes), choose the catalog for Original Presentation Catalog, if both of them have any changes, choose any of them to be the Original Presentation Catalog.

- Notes: Upgrading the catalog only add what is previously not exist in original, any changes on modified catalaog of existing items will not be applied


e. Archive
- Open 2 Catalog Managers
- Open offline both catalogs
- On one Catalog Manager, select folder to archive, then File | Archive.



- On the other one select the folder where we want to unarchive, then File | Unarchive
- Notes: Archiving cannot be performed from root folder, add what is previously not exist in original and any changes on modified catalog of existing items will be applied

OK that's for now.

Why are there many database connections opened by Oracle BI?

Okay, let's start blogging!

Currently I'm in a project that requires me to be able to use Business Intelligence tool: Oracle Business Intelligence Suite Enterprise Edition. Actually it was Siebel's but then -as some big companies love to do- Oracle 'take' it. Oracle, yeah it's expensive! So from that time me and my friend have been trying to learn it and here I want to share.

Let's go to the first issue I want to share.

Why are there many database connections opened by Oracle BI?

If you notice in your database activities that there so many connections opened by Oracle BI but they do nothing (idle). This becomes a problem when DBA(s) limit the connection of user for BIEE application, and they shout at you that BIEE users open connection without doing anything (you should be grateful if your DBA is patience).

Connection idle (opened by Oracle BI)

Actually Oracle BI enables us to use one connection for more than one request. The way it does is by remaining open after one request completed, so if you run another request it won’t open another connection instead it uses the remaining one.

You can set the time for Oracle BI to remain open, by setting Timeout property in database properties options. To change the properties you can follow these steps:

1. Open rpd you want to set in Administration tool
2. On the Physical Layer, right click the connection pool

Connection Pool

3. You can find Timeout property

Connection Pool Properties Dialog Box

4. Set the connection timeout for the connection

Note from help

Setting the timeout depends on your need. Ask your DBA also to have discussion how long it should be specified.