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

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

Target Schema Registered to Multiple Repository

Hello Everybody,
We have OWB 10G2 installed on a linux server and some target schemas are associated to the OWB repository. Now We want to create another OWB repository on Windows server but would like to use the same target schema which the other OWB repository is using.
I was going through the OWb istallation guide and it says "One target schema associated with multiple repositories, however, is not permitted".
Is there any other way out to do this...and incase we need to register other schema as target schema to the new repository..Is it compulsory to have that target schema on the same database on which the repository is installed.
Please suggest.
Thanks in advance.
Regards,
Sunil

Hi Sunil,
a target schema is always assiciated to one repository. That repository is the runtime environment for your mappings.
You may have two repositories for development on different machines and deploy the the same target, but I would not recommend it.
But it is common the other way round: you have one repository on machine A where you do the development of your mappings, then you deploy to a target on machine B (for testing) and to a target on machine C (production).
See the manual for different architecture scenarios.
Regards,
Carsten.

Target Schema creation with Warehouse Builder

Hi,
I have installed Oracle Enterprise 9.2.0.1.0 and Warehouse Builder 9.2.0.2.8.
The repository, the runtime and the target schema have been created without problem.
I also have created some test jobs and everything run fine.
My question is:
Can we create a target schema without those tables
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.
Thanks for your answers.

Theoretically you can, but you need these objects accessible from the mapping code, as they log information in these tables.
So you can create synonyms into the target schema, just make sure you have the correct privileges (complete read/write).
Jean-Pierre

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 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

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

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

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.

Connecting the source and target schemas to ODI

Hi ,
I have recently started learning ODI tool for data integration. I need to use this tool as a part of Deal Management product related work.
I have gone thru the documentation available in OTN for ODI. they were describing everything using the demo environment.
problem:
Can any one please tell me how to connect source schema and target schema to the ODI ...?
Both the source and target schema are in the Oracle database of the loaclhost.

Hi,
Right Click ur Dataserver , In the bottom u will have option insert physical schema.
Click that u will have window opened........
In the Definition Tab:
Specify ur Schema name and Work schema .......u r going to use .
Enable the default option also....
In Context Tab:
Specify ur context Name and Type in the Name u want to have for ur logical Schema, it autmatically creates the logical schema ...for u.
and click ok .
hope it helps u.....
Thanks
AK

Target Schema and Runtime Instance of Oracle Database

I am new to OWB and starting to understand its architecture.
Does the Runtime Access User, Runtime Repository Schema and Target Schema (discussed a the Runtime Instance) need to be installed on every database that will be a target? For example, if I have a data warehouse and two data marts, with I have three installations?

Hi,
You need to run the OWB Runtime Assistent for every target schema, that is correct (it will add the auditing stuff that enables you to monitor what's happening deployment and execution wise).
Whether you need to create a Runtime Repository and its accompanying Runtime Access User(s) for each and every target I'm not sure.
If your target schema's are on the same instance I'd say that you can use as few or many Runtime Repositories as you wish.
When on different instances I think it's necessary to create them.
Hopefully other forum-attendees can add some more if they have definite answers.
Cheers, Patrick

Error saving map. Stored procedure returned non-zero result. Check if source and target schemas are present.

I am using VS 2012 and BizTalk 2013 and attempting to deploy an application to BizTalk when I get these errors:
Error 47
at Microsoft.BizTalk.Deployment.Assembly.BtsMap.Save()
at Microsoft.BizTalk.Deployment.Assembly.BtsArtifactCollection.Save()
at Microsoft.BizTalk.Deployment.Assembly.BtsAssembly.Save(String applicationName)
at Microsoft.BizTalk.Deployment.BizTalkAssembly.PrivateDeploy(String server, String database, String assemblyPathname, String applicationName)
at Microsoft.BizTalk.Deployment.BizTalkAssembly.Deploy(Boolean redeploy, String server, String database, String assemblyPathname, String group, String applicationName, ApplicationLog log)
0 0
Error 49
Failed to add resource(s). Change requests failed for some resources. BizTalkAssemblyResourceManager failed to complete end type change request. Failed to deploy map "XXX.BTS2013.XXX.Maps.map_XXXX_R01_InsLabProc".
Error saving map. Stored procedure returned non-zero result. Check if source and target schemas are present. Error saving map. Stored procedure returned non-zero result. Check if source and target schemas are present.
0 0
Error 46
Failed to deploy map "XXX.BTS2013.XXX.Maps.map_XXXX_R01_InsLabProc".
Error saving map. Stored procedure returned non-zero result. Check if source and target schemas are present.
0 0
I also tried to Import a MSI file from our test environment to see if that would work...got the same errors. After spending hours (not kidding) looking for an answer, all I could find is that a hotfix would work. So, I got the hotfix from Microsoft
Support and applied it then rebooted. Still getting the same errors. I'm absolutely at a stand still. Interesting that I got this application to deploy yesterday and then the next time I deployed it I started getting these errors. I'm
ready to pull my hair out!
Is there an answer for this out there somewhere? Any help would be appreciated.
Thanks,
Dave

Hi Dave,
Which hotfix have you applied? I don't think a hotfix of this issue is available for BizTalk 2013 yet. You should create a
support ticket with Microsoft to get a solution.
If this answers your question please mark as answer. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Difference between target schema and target user

hi,
Can anyone explain to me what is the difference between target schema and target user? examples will be more welcome then theoratical explanation.
thanks so much

In Oracle database schema and user is the same things (if you use general authentication by database).
When used external authentication (for example with Windows domains/active directory) schema is a owner of database objects group and you should specify mapping between external usernames and schema to which this user has access when connects to database.
For example:
- windows domain user CORPDOMAIN\USER1 can connect to oracle database schema SCOTT;
- windows domain user CORPDOMAIN\USER2 can connect to oracle database schema SCOTT;
- windows domain user CORPDOMAIN\ADMIN can connect to oracle database schema SYSTEM;
Oleg
Message was edited by:
tsiboleg

OWB10gR2 and target schema a DB2 database

Does the OWB10gR2 support the target schema to be a DB2 database using a ODBC connection ?

Yes. Just add the table from the DB2 module to the map as a target. note the map still deploys to an oracle location (since the oracle db is the etl engine).

Error in target schema defining

Hi
I have installed OWB in machine called A and taken same as my target schema and i could load data into target schema(A) from another source database
But now i want to take an anothe machine say B as my target databse,for that i have created a Repository user/manager in machine B and registered same user/manager in the design center as target schema user and defined the target location even then i am getting the below error can anybody please help me in this what else i need to do to load data in to machine B by using OWB
RPE-01012: Cannot deploy PL/SQL maps to the target schema because it is not owned by the Control Center
Also is it mandatory to have JVM installed on the target machine?
If so do i need to excute the bellow SQLs?
call dbms_java.grant_permission('OWB_REPO_OWNR', 'java.util.PropertyPermission','*','read,write');
call dbms_java.grant_permission('OWB_REPO_OWNR', 'java.net.SocketPermission','10.23.7.8','resolve')
call dbms_java.grant_permission('OWB_REPO_OWNR', 'java.io.FilePermission','F:\owb_oracle_home\jdk\jre\bin\javaw.exe','execute');
Regards
Venu
Edited by: 648738 on Sep 16, 2008 10:05 PM

Hi, did you start Control Center on server B?
Did you define new Control Center record in Design Center?
(I guess you still connect with Design Center to OWB repository on server A)
Of course you need to install JVM option into target database.
Regards,
Oleg

OWB and Stage/Target Schema Options?

Similar Messages

Maybe you are looking for