Migration to 10.2: Target Schema managed by old Control Center/Runtime Rep

Hi
We are migrating from OWB10gR1 to R2 (10.2.0.4)
After loosing (!) the old 10.1 runtime repository "OWBRUN" we created a new Design Repository.
Then we wanted assign an old target schema named "TARGET" to the new one (with Security -> User -> New ...)
Unfortunately we receive the message:
User "TARGET" is managed by another control center: OWBRUN
How can we remove this connection between "OWBRUN" and "TARGET" ?
Otherwise we can not use this schema as a target, and therefore we can't deploy mappings to it.
Beat

I solved my problem using the 10gR2-Repository Assistant:
1. Installing a new Control Center with the name of the old one (OWBRUN exactly!).
2. Register the target schemas to this new CC (as before in 10gR1)
3. Unregister those targets from OWBRUN
4. Register the targets to the correct CC (OWBRUN1020)
(5. Deinstall CC OWBRUN)
Beat

Similar Messages

ATI Catalyst Install Manager and catalyst Control Center Help

I just run the Windows 7 Upgrade
advisor report and it said that I should uninstall the ATI Catalyst Install Manager and Catalyst Control Center then reinstall after upgrade..
Could someone direct me where I might t find these programs for Windows 7

You must not do this. Just continue upgrade installation.
On my Satellite I got the same message but I have simply continued with upgrade.
At the end everything went fine.

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

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

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

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

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

DMO - ECC Migration to HANA, wrong Target DB SID was given

Dear Experts,
I am migrating our ECC system to HANA DB, Currently the long running phase ACT_UPG is going on. During the configuration phase by mistake i have given Target DB SID as source system SID which is wrong , Target HANA DB SID is different. Would i be able to change this setting in upcoming phases ? Would system prompt me to change DB SID after failing to connect to the given SID ? , I tried looking for config file which is similar to keydb.xml to edit this, but i am not able to find such kind of config file.
Please advise, i am worried if i need to redo everything
Thanks,
Aravind

Hi Jeena,
My last reply was logical assumption.
You have used DMO with SUM, at least one SP should be applied.
Refer: 1813548 - Database Migration Option (DMO) for Software Update Manager
If you are on 7.31 or 7.4 ---- your target can be 7.31 or 7.4 - your choice.
Divyanshu

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

Deploying mappings in non-target schema

Hi,
How can I deploy my mappings in a different schema other than the target schema(where all the target facts/dimensions are present). I want the OWB generated mapping packages in a different schema. How can I accomplish this!!
Thanks,
Srinivas.

Hi Srinivas,
You connect to the runtime repository using the runtime access user.
The you register your factual target users (you now would have 2). Then when you deploy objects to the target locations (a.k.a users) they will end up in that user, not in the stuff you log on with...
If you want to do all of this nicely (just realized that) you should have 2 modules in the design. If you do this you do not need the synonyms..
So you would have a module called packages, a module called schema_objects. Then you have 2 locations related to these 2 modules (package_location and object_location respectively).
When you go to the deployment manager, you will see a tree with package_location and object_location. Click register for those.
Package_location will be user PACK
object_location will be user OBJECTS_HERE
Deploy the lot (packages into PACK of course) and make sure to deploy the connector (this allows OWB to generate the required schema references, replacing the synonyms I suggested before).
Jean-Pierre

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

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

How to create/import a target schema from a source schema using data pump?

I have seen some examples where schema remapping will be done through remote link which I cannot as both the target schema and source schema are in same machine ...but I am not sure how to do it with out using remote link? I would be great if some one could provide a example
Thanks in Advance

I'm not sure what you are asking here, but I'll try to give some examples on remapping a schema:
expdp prived_user/password schemas=orig_schema_1 directory=dpump_dir dumpfile=orig_schema_1.dmp
impdp prived_user/password schemas=orig_schema_1 directory=dpump_dir dumpfile=orig_schema_1.dmp remap_schema=orig_schema_1:new_schema_1
If you want to try without a dumpfile then you need a loop back dblink. (A dblink on your database that points to the same database. This would be your command:
impdp prived_user/password schemas=orig_schema_1 directory=dpump_dir network_link=loop_back_link remap_schema=orig_schema_1:new_schema_1
Hope this helps. If not, can you explain your question a little more?
Dean

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

Xslt transformation - single tag to unbounded element in target schema

I am trying xslt in JDev11g. My source has tags like soldTo, shipTo and BillTo customer details. I need to map these in the target schema <PARTIES> unbounded element in the 2nd, 4th and 5th iteration. I am unable to map multiple times into the target. Can this be done? Target example is below:
<PARTNERS/>
<PARTNERS>
<PARTYTYPE>ShipTo</PARTYTYPE>
<PARTNRNDX>BMW1702</PARTNRNDX>
</PARTNERS>
<PARTNERS/>
<PARTNERS>
<PARTYTYPE>SoldTo</PARTYTYPE>
<PARTNRNDX>BMW2521</PARTNRNDX>
</PARTNERS> ....
Thanks
Shanthi

Hello Folks,
I have a similar issue. I have a particular unbounded element which i have to display multiple times ( mapping it to different source tags from the source schema) . I am able to do it in the source view and my transformation works fine when i test it. I am able to get the XML what i need. How ever when i switch to the design view, i get this error
Transformation_1.xsl
Error: This node is already mapped, repeating nodes not supported : "/mstns:OrderCreate/mstns:OrderCreateProperties/mstns:PartnerInformation/@partnerRoleIndicator"
Error: This node is already mapped, repeating nodes not supported : "/mstns:OrderCreate/mstns:OrderCreateProperties/mstns:PartnerInformation/mstns:PartnerIdentifier/@partnerIdentifierIndicator"
Is it ok to proceed and deploy with the current code? Or should i modify my source schema (which is in my control) to fetch multiple rows, use a for-each to achieve this functionality?
Thanks

Migration to 10.2: Target Schema managed by old Control Center/Runtime Rep

Similar Messages

Maybe you are looking for