Already a member?
Sign in
Welcome! This is a website that everyone can build together. It's easy!
Location: Oracle Warehouse Builder
Discussion: OWB Installation Considerations
Keyword tags:
Installation consideration
OWB
Watch
|
htu htu |
OWB Installation Considerations
Nov 21 2007, 11:25 AM EST If you plan to install Oracle Warehouse Builder, Here are the things that you need to consider: 1. Choose your implementation strategy: Basic Implementation, Traditional Client/ Server Implementation or Split Repositories Implementation. 2. Choose what versions to be installed on a server and clients. Here are the products and their versions that we have installed: a. Oracle Database on the server - Oracle DB 10gR2 (10.2.0.1) - Oracle DB patch set (10.2.0.3) b.Oracle Warehouse Builder on the server and clients OWB 10.2.0.1 - OWB patch set 5696353 (10.2.0.2) - OWB one-off patch: 6270894 + Fix Stack over flow problem +Must apply on client side (readme file is not clear) and can also apply on server + Will not get fixed until OWB 10.2.0.4 (OWB 11g = 10.2.0.3) c. Repository Owner - Only one OWB repository owner in the database is recommended 3. Layout your project structure 4. Plan storage (tablespace) for projects 7 out of 12 found this valuable. Do you? |
|
htu htu |
RE: OWB Installation Considerations
Dec 3 2007, 3:57 PM EST Additional to the one-off patch 6270894, we found out that we need to have an updated ManagePrivilegeFromDB package reinstalled, in order to get around the propagation error that we are experiencing. The propagation error only happen when a project has internal dangling objects exist in the repository. The questions are 1) how do you identify internal dangling objects? 2) how do trace back the objects to corresponding projects? 0 out of 3 found this valuable. Do you? |
|
htu htu |
RE: OWB Installation Considerations
Dec 3 2007, 4:00 PM EST Here is how you can identify the internal dangling objects: PROMPT List Of REAL FCO with Duplication:; SELECT realfco, count(*) as cnt, min(creationtimestamp) as created_tm, max(updatetimestamp) as updated_tm FROM $a0.cmpACLContainer_v GROUP BY realfco HAVING count(*) > 1 ORDER BY max(updatetimestamp); PROMPT Full List Of REAL FCO with Duplication:; SELECT * FROM $a0.cmpACLContainer_v WHERE realfco IN ( SELECT realfco FROM $a0.cmpACLContainer_v GROUP BY realfco HAVING count(*) > 1 ) ORDER BY realfco,logicalname; PROMPT Full List Of First Class Objects:; SELECT * FROM $a0.firstclassobject_v WHERE elementid IN ( SELECT realfco FROM $a0.cmpACLContainer_v GROUP BY realfco HAVING count(*) > 1 ); 0 out of 2 found this valuable. Do you? |
|
htu htu |
RE: OWB Installation Considerations
Dec 3 2007, 4:02 PM EST Tracing back those objects back to their projects, it is not as simple as finding them. I had to develop a stored procedure to do that. The stored procedure is based on the suggestion from Sophia Chen from Oracle OWB group. I will post the code as attachment. 0 out of 2 found this valuable. Do you? |
|
htu htu |
RE: OWB Installation Considerations
Dec 3 2007, 4:10 PM EST Just uploaded the stored procedure: sp_get_pm.sql. You need to change the two variables to use in your database: define tgt=owb_admin define own=owb_rep2 You can find out more detailed information regarding this issue at this SR: https://metalink.oracle.com/metalink/plsql/f?p=110:20:12601260482989641240::::P20_TARNUM,P20_CTRYCODE:18172998.6, 0 out of 2 found this valuable. Do you? |
