OWB Target Schema Tables

OWB installs some tables under the target schema (including, for example, WB_RT_PARAMETERS, WB_RT_PLATFORM_PROPERTIES). These tables are in the same schema as all of our application target tables. Our DBAs want to know:
(1) Is there some way to have OWB build all these tables under a schema separate from the schema in which all of our application tables reside?
And, if not:
(2) Is there some way to identify the tables (and other objects) created by OWB. Are they only the objects prefixed with WB? Or are there others?
The DBAs would like to script some changes to the tables in our target schema but of course do not want to modify the OWB-specific tables, so we would like to identify the objects that are OWB-specific.

Barbara,
Following are all objects in a new target schema:
FUNCTION OWBRTPS_KEY_TO_INSTANCE
OWBRTPS_KEY_TO_VERSION
OWBRTPS_KEY_TO_VERSION_STRING
WB_CAL_MONTH_NAME
WB_CAL_MONTH_OF_YEAR
WB_CAL_MONTH_SHORT_NAME
WB_CAL_QTR
WB_CAL_WEEK_OF_YEAR
WB_CAL_YEAR
WB_CAL_YEAR_NAME
WB_DATE_FROM_JULIAN
WB_DAY_NAME
WB_DAY_OF_MONTH
WB_DAY_OF_WEEK
WB_DAY_OF_YEAR
WB_DAY_SHORT_NAME
WB_DECADE
WB_HOUR12
WB_HOUR12MI_SS
WB_HOUR24
WB_HOUR24MI_SS
WB_IS_DATE
WB_IS_NUMBER
WB_IS_SPACE
WB_JULIAN_FROM_DATE
WB_MI_SS
WB_RT_INTEGER_VERSION_NUMBER
WB_RT_IS_PLATFORM_REPOSITORY
WB_RT_MINIMUM_SERVICE_VERSION
WB_RT_PLATFORM_REPOSITORY
WB_RT_VERSION
WB_WEEK_OF_MONTH
WB_XML_LOAD_F
INDEX PK_RTL
PP_PK
PP_UK
SYS_C0036660
SYS_C0036661
SYS_IOT_TOP_101865
WB_RT_PARAMETERS_PK
JAVA CLASS oracle/wh/resource/RuntimeXMLExceptions
oracle/wh/runtime/mm/Alg
JAVA RESOURCE META-INF/MANIFEST.MF
LOB SYS_LOB0000101839C00003$$
SYS_LOB0000101942C00002$$
PACKAGE OWBXMLTK
OWB_MATCH_MERGE
WB
WBRTTIME
WB_RT_MAPAUDIT_UTIL
PROCEDURE WB_ABORT
WB_ANALYZE_SCHEMA
WB_ANALYZE_TABLE
WB_COMPILE_PLSQL
WB_DISABLE_ALL_CONSTRAINTS
WB_DISABLE_ALL_TRIGGERS
WB_DISABLE_CONSTRAINT
WB_DISABLE_TRIGGER
WB_ENABLE_ALL_CONSTRAINTS
WB_ENABLE_ALL_TRIGGERS
WB_ENABLE_CONSTRAINT
WB_ENABLE_TRIGGER
WB_OLAP_LOAD_CUBE
WB_OLAP_LOAD_DIMENSION
WB_OLAP_LOAD_DIMENSION_GENUK
WB_TRUNCATE_TABLE
WB_XML_LOAD
SEQUENCE WB_RT_MONTH_SEQ
WB_RT_PLATFORM_PROPERTIES_SEQ
WB_RT_QUARTER_SEQ
WB_RT_TEMPCONS_SEQ
WB_RT_TEMPINDEX_SEQ
WB_RT_TEMPTABLE_SEQ
WB_RT_WEEK_SEQ
WB_RT_YEAR_SEQ
TABLE CREATE$JAVA$LOB$TABLE
JAVA$CLASS$MD5$TABLE
WB_RT_EXCEPTIONS
WB_RT_PARAMETERS
WB_RT_PLATFORM_CONFIG
WB_RT_PLATFORM_PROPERTIES
WB_RT_POSTLOAD_EXCEPTIONS
WB_RT_SEEDED_STRINGS
WB_RT_TIME_SRC
TRIGGER WB_RT_PARAMETERS_AUDIT
WB_RT_SEEDED_STRINGS_AUDIT
I.e. most objects start with WB... a few are created as part of the deployment of Java to the database (some of the tables and the LOBs). Unfortunately, as you notice, there are still a few OWB objects that do not start with OWB. If you drop all WB objects and OWBRTPS_KEY_TO_INSTANCE, OWBRTPS_KEY_TO_VERSION, OWBRTPS_KEY_TO_VERSION_STRING, I think all Warehouse Builder objects will be removed.
The objects are there to enable remote node installation. If you remove the definitions... then unfortunately you are not supported, even though I am sure you can get things to work with synonyms instead of tables.
Thanks,
Mark.

Similar Messages

Deploying the code in OWB in same target schema

i have created one staging area and and enterpise model in OWB to deploy my mappings. to deploy the staging area and enterpisre model mapping i have one TARGET SCHEMA.
now when i want to deploy my enterpise model mapping to the target schema(where i have deployed staging area mapping) OWB is showing the error
ORA-06550: line 127, column 9:
PL/SQL: ORA-00942: table or view does not exist
thank you

Use sca-deploy.xml... Check the documentation here...
http://docs.oracle.com/cd/E14571_01/integration.1111/e10224/sca_lifecycle.htm#CACCDBHG
Cheers,
Vlad

How to deploy mapping in TARGET SCHEMA in OWB

i have created one staging area module and and enterpise model module in OWB to deploy my mappings. to deploy the staging area and enterpisre model mapping i have one TARGET SCHEMA.
now when i want to deploy my enterpise model mapping to the target schema(where i have deployed staging area mapping) OWB is showing the error
ORA-06550: line 127, column 9:
PL/SQL: ORA-00942: table or view does not exist
IS IT NOT POSSIBLE TO DEPLOY STAGING AND WAREHOUSE TABLES TO SAME SCHEMA ?
thanks
Message was edited by:
[email protected]

Good morning Kunal,
Naren is right, no problem deploying the content of different modules in the same schema.
In case you are using OWB 9.0.4 or more recent, have you defined module locations and connectors properly and have you registered the locations in the Deployment Manager?
Good luck, Patrick

OWB and Stage/Target Schema Options?

OWB and Stage/Target Schema Options?
=========================
Thanks for your replies.
As we know that we need to have Landing, Staging and Target (Data Warehouse) areas in ETL process. We are able to configure in multiple ways in OWB.
Option 1
Keep everything in single schema/oracle instance with different object naming convention.
Option 2
Keep each one in separate schema such as Landing schema, Staging schema and Target schema in single oracle instance.
Option 3
Keep each one in separate server such as Landing server, Staging server and Target server in multiple server/oracle instance.
What are the advantages/disadvantages on above options?
Which of the above options worked better in OWB environment for you?
There are some folks suggests to work with out staging schema. Is it a good idea?
Do you have any pointer?
Thanks in helping out.

Option 1
Best for small Project .Some 15-10 Target tables.
Difficult to manage and Recovery will be difficult
Small team Managing Everything
Option 2
Best for Big project having lots for tables .
Easy to manage.
Option 3
NA
Cheers
Nawneet

OBIEE to properly query tables in target schema using "Mixed_Case" names

We encounter the following error when using the BI Administration tool (to update a row count of a physical table) or the Analysis tool (to run a query) 11g against our target schema:
View Display Error
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 17001] Oracle Error code: 942, message: ORA-00942: table or view does not exist at OCI call OCIStmtExecute. [nQSError: 17010] SQL statement preparation failed. (HY000)
SQL Issued: SELECT 0 s_0, "OTM"."Cheese"."Cheese" s_1 FROM "OTM" FETCH FIRST 65001 ROWS ONLY
The reason for this error seems to be that our target schema contains tables that have quotes in the name when the table is created, which I understands enforces the preservation of letter case-- in this case Mixed_Case names. Since this is not "our own" application, we don't really have any control over how the schema is created or the table/views named. Interestingly enough, the table appears in the BI Administration with the expected columns though the querying for rows count and data fails.
One way we've worked around this is to manually create a VIEW of the table of interest in the target schema using all capitals. This works, but seems unnecessarily messy, especially if we are interested in using a VIEW that is already created as part of the schema.
I have found the following various discussions about setting the NQSConfig.ini file on line, but changing the value and restarting the OBIEE server doesn't seem to make a difference.
# Case sensitivity should be set to match the remote
# target database.
CASE_SENSITIVE_CHARACTER_COMPARISON = ON;
Are there other ways to get OBIEE to recognize mixed-case table names?

BI Admin: Physical / Database / Features tab / (scroll to bottom or use Find) IDENTIFIER_QUOTE_CHAR: set this to a double quote: "

How to unselect a schema as a target schema in the old version OWB?

Hi all,
I am upgrading my OWB from 9.0.5 to 10.2.0.3. When I deploy the mapping, I get the error message saying "cannot deploy the map to the target schema because it is not owned by the control center". So I log in as the repository owner, and want to add this schema to be the repository user, also to be the target schema. When I do this, I get a error message saying "The following user can not be registered as a target schema, as it is alreday being managed by a different control center", which is my old repository in 9.0.5. Does anybody know how to unselect the schema as the target schema in OWB 9.0.5?
thanks a lot

Hi,
for OWB 9.2 and later this can be performed with Runtime Assistant, for details look at
http://download.oracle.com/docs/html/B11000_02/04deinst.htm#1146937
I have little experience with pre 9.2 OWB releases, but I think that this procedure is very similar across all OWB versions. I think you need check this in Installation guide for OWB 9.0.5
Regards,
Oleg

One schema for OWB Design repository, runtime repository and target schema

Currently we have contents of OWB Design schema, runtime schema and target schema all combined into one schema of the same database in OWB 9.0.2 as well as OWB3i. We like to move to OWB10g in very near future. Can we keep the same structure for convenience of migration in OWB10g? Is it mandatory that OWB design repository (and components) must be separate from OWB run time repository (and components) and target schema? In other words is it possible and workable to use only one schema to contain OWB design repository, OWB run time repository and target schema in OWB10g environment with repositories to be situated on Oracle v9.2.0.1.0? Also what special considerations should be taken to create the database v9.2.0.1.0 and installation of OWB10g. What are the problems/side-effects to have all in one schema?
Also please let me know how to install Oracle Workflow server to be used along with OWB. Will OWB10g work with repository on Oracle database v9.2.0.1.0?
Your prompt advice will be very well appreciated.
Sankar

The design repo is a metadata repo that stores all the design-time objects and so forth.
It is an architectural decision that you or your team need to decide on. There are many flexible ways to architect an OWB infrastructure.
Also, your repository users will be using the design repository on the the other DB instance to do their design work...potentially less people always hitting the target database all the time.
-Greg

How can I change the Tablespace of a Target Schema?

We have OWB 9.2.0.2.8.
We have created a target schema âAAAâ in a Development server and I have defined the Tablespace âUsersâ for the data and the Tablespace âIndexesâ for the indexes.
But in the target schema âAAAâ in the Production server we have defined the Tablespace âDWH_Dataâ for the data and the Tablespace âDWH_Indexâ for the indexes.
How can I change the default tablespaces for the data and the indexes in the Development server?

Do you want to do this in the design repository? In there you can do this on the module, as long as you don't do this on the tables.
You can also update this using scripting, which would be fastest if you need to do this for a lot of stuff...
Jean-Pierre

Wb_rt_api_exec in pl/sql as OWB target

I've got a question similar to the one posted by Donna Kelley on 26-mar-2007 (
Re: 10gR2: How do you run OWB from Enterprise Manager (OEM) and Scheduler?
I'm unable to figure out the grants needed to execute wb_rt_api_exec.run_task within a pl/sql procedure when the procedure is being run by the OWB target user.
We just upgraded OWB in devo from 10.1.0.4 to 10.2.0.1.31. In the earlier version, there was no problem with the target user executing wb_rt_api_exec (although we used open, execute, close instead of run_task). The runtime repository owner granted execute on wb_rt_api_exec to the target schema. And then the 2 roles wb_r_owbruntime and wb_u_owbruntime were also granted to target. That's all it required.
In the new version, I can execute wb_rt_api_exec only as the design repository owner. I've granted the target user execute on wb_rt_api_exec. Also granted the 2 roles owb_d_owbowner and owb_o_owbowner roles to the target user (see sqlplus_exec_template.sql). But within a pl/sql procedure with the procedure run as the target user, the return code is 3 (failure). I can also not run sqlplus_exec_template as the target user. But I can run it successfully as the design repository owner.
This seems strange. We're running ETL mappings to populate target tables. It should be easy to run the pl/sql procedure as the target user. I don't want to run it as the repository owner because that would involve a bunch of grants on target tables. Seems silly.
I'd welcome any thoughts and advice.
Many thanks.
Gary

First, David, thanks very much for your help. Based on your example, what I'm trying to do should work.
Below is a very simplified example that demonstrates the problem. Note that executing the procedure as the target user produces an error (ie, the return value is 3) while executing it as the design repository owner succeeds.
Comments and advice are welcomed from all. I very well could be missing something obvious. Thanks to all.
devo> @who
OWBTARGET
devo> start t1
devo> create procedure t1 authid current_user as
2      sql_stmt varchar2(50) := 'set role owb_d_owbdesign, owb_o_owbdesign';
3 begin
4      execute immediate sql_stmt;
5      dbms_output.put_line(to_char(owbdesign.wb_rt_api_exec.run_task(
6      'RPTDEVO_LOC', 'PLSQLMAP', 'TERM_TO_DMS_CURR', ',', ',', 0, 0)));
7 end;
8 /
Procedure created.
devo> grant execute on t1 to owbdesign;
Grant succeeded.
devo> exec t1
Stage 1: Decoding Parameters
| location_name=RPTDEVO_LOC
| task_type=PLSQLMAP
| task_name=TERM_TO_DMS_CURR
Stage 2: Opening Task
| l_audit_execution_id=5390
Stage 3: Overriding Parameters
Stage 4: Executing Task
| l_audit_result=3 (FAILURE)
Stage 5: Closing Task
Stage 6: Processing Result
| exit=3
3
PL/SQL procedure successfully completed.
devo> @check_role_privs owbtarget
devo> select grantee "grantee",
2      granted_role "role",
3      admin_option "option"
4 from dba_role_privs
5 where grantee = upper('&1')
6 order by 2
7 ;
admin
grantee role option
OWBTARGET AQ_USER_ROLE NO
CONNECT NO
OLAP_USER NO
OWBR_OWBDESIGN NO
OWB_D_OWBDESIGN NO
OWB_OWBDESIGN NO
OWB_O_OWBDESIGN NO
RESOURCE NO
SELECT_CATALOG_ROLE NO
9 rows selected.
devo> connect owbdesign
Connected.
devo> @who
OWBDESIGN
devo> exec owbtarget.t1
Stage 1: Decoding Parameters
| location_name=RPTDEVO_LOC
| task_type=PLSQLMAP
| task_name=TERM_TO_DMS_CURR
Stage 2: Opening Task
| l_audit_execution_id=5400
Stage 3: Overriding Parameters
Stage 4: Executing Task
| l_audit_result=1 (SUCCESS)
Stage 5: Closing Task
Stage 6: Processing Result
| exit=1
1
PL/SQL procedure successfully completed.

Do I need to deploy Public Synonym in Target Schema?

Hi,
I need to develop and deploy a mapping. I need to use source table in source schema but a Public Synonym for a terget table. This destination table for the public synonym is not target_schema where mapping is to be deployed. Do I still need to deploy the public synonym into my target schema where mapping is or not? I was 3wandering since its a public synonym and the actual destination table is already in database I may not have to deploy this synonym. Thanks for the help in advance..

OWB does not currently directly support public synonyms. You will have to deal with these synonyms outside OWB and if you use the synonym from a mapping you can trick OWB to use it by creating and using a dummy table in the mapping.
Regards:
Igor

Is it possible to have source and target schema in the same DB instance ?

Hi All,
I'm using Oracle 11gR1.
I have switched source locations from other server to the one with OWB.
During deploy I get VLD-3064 and I can't deploy mapping because of many 'table or view does not exist' warnings.
Is it possible to have source and target schemas in the same instance ??
How to do it ?
Regards,
Martin

Hi Jörg,
Thanks for your help and quick answer.
I'd like to clarify a little your answer :
1. Are the any special privilages I need to set ? Currently I have only 'RESOURCE' and 'CONNECT' (I think I didn't have to add any other privs when that schema was located on other instance...)
2. Also VLD-3064 states that : 'Owning and referenced location of this connector are on the same database instance. Unless explicitly referenced in configuration settings no generated code will use the dataabase link resulting from deployment of this connector'. Does it mean I have to put something in configuration ?
Thanks,
Martin

Repository / Target schema.

Hi all...
Is the following right?
The repository has the function to store owb objects. Such as pre defined owb procedures. On the database level is just a schema into a databse. Projects can use the same repository. Is this recremended?
The target schema is an other db schema where you create the new object, like new tables and where you load the data to. Each project will use his own target schema?

Projects can use the same repository.For what projects can use the same repository?
Projects is no more than set of objects (tables, mappings, etc.) in OWB design repository.
The target schema is an other db schema where you create the new object, like new tables and where you load the data to.
Each project will use his own target schema?Each project may has several target schemas (target modules).
But all target modules in one project and even all modules in all your projects can use the same LOCATION -
in this case all projects will use single target schema in database.
Also look at this threads:
How to create a runtime repos in 10gR2
OWB Standalone Target Schema - Split Architecture
Regards,
Oleg

OWB error log table

Hi All,
I am using OWB 11.2. In the target table property inspector under error table i have specified a error table and when i deploy my mapping it gets created on my target schema. Is there any way i can change the setting and get the error table created on some other schema.? We dont want to have the error table and reporting/target tables on the same reporting/target schema.
Please suggest.
Thanks
Kanwar

Hi Kanwar,
you cannot create the error table in another schema using owb. You have to do it manually:
as user1:
begin
dbms_errlog.create_error_log('DIM_DEMO','DIM_DEMO_ERR', 'USER2') ;
end;
/as user2:
grant select, insert, update , delete on USER2.dim_demo_err to USER1;In the mapping, you can specify the error table with schema: USER2.dim_demo_er
Regards,
Carsten.

Target Schema cluttering

My target schema is starting to contain a lot of "garbage" such as:
* DBG$ tables that where not automaticly deleted
* obsolete tables/views deleted in OWB, but not dropped in the target
* I even have a self-refering synonym.
* there are still packages for mappings I deleted in OWB
How do I clean up my target schema and take a "fresh" start?
thanks,

In general the scenario that is described in the original question works, specifically if the schemas are on the same machine. Warehouse Builder will generate <schema>.<object> references. Make sure you do have at least select privileges on the source tables.
If they are not, then in OWB92 you would have to use mapping configuration parameters if you want to generate: <schema>.<object>@<db link>.
Mark.

I' m not able to create a new Target Schema

Hi folks,
Always I tried to create a new Target Schema using OWB Runtime Assistant, installing into a new user schema or into an existing user schema I've got a Target Schema Installation Error. The log file shows the following error lines:
(Spawn Token) Error loading Java into DB:
Sun Feb 22 11:37:32 BRT 2004
oracle.wh.util.DebugUtility: [processSPAWN]: A spawned program error. Exception = java.lang.Exception: java.io.BufferedInputStream@2cd19d
Sun Feb 22 11:37:32 BRT 2004
oracle.wh.util.DebugUtility: [processSPAWN]: Get the error, stop processing...
Sun Feb 22 11:37:32 BRT 2004
oracle.wh.util.DebugUtility: Files\Java\j2re1.4.0_03\lib\ext\QTJava.zip""=="" was unexpected at this time.
Sun Feb 22 11:37:36 BRT 2004
oracle.wh.util.DebugUtility: Assistant operation is unsuccessful ...
I've installed both OWB Design Time and OWB Server Side, in the same machine using 2different Oracle_Homes.
Please, tell me what I can do to overcome this.
Thanks all,
Ismael

Hi Pierre,
Thank you for your response.
Actually, I've installed the OWB Server Side because I was getting the same problem using the OWB Run Time Assistant of the OWB Design Time that I've installed before. In the OWBInstallGuide I read the following text, recommending not to use the same Oracle_Home:
"2.5 Step 4. Perform the OWB Server Side Install using Oracle Universal Installer
Install the OWB Server Side components on the machine where your Oracle Database Server is installed.
When you performed the OWB Design Time installation, you also installed the runtime components. Therefore, if you are performing the OWB Server Side install on the same machine as the OWB Design Time install, you are installing the runtime components twice. If you decide to go forward with this configuration, make sure to specify a separate ORACLE_HOME for each install."
Any way I'm going to try your suggestion but I'm afraid it couldn't work because of the above text. I'm running out of time, I'm supposed to start a project next Monday and I'm stuck on this problem.
Please, if you have any other hints let me know. I'll keep you informed after using the same Oracle_Home for both.
Thanks again,
Ismael

OWB Target Schema Tables

Similar Messages

Maybe you are looking for