Upgrade-deployment in OWB 10.2.

Upgrade-deployment in OWB
As I need to create new partitions for the fact table (with data!), I want to test upgrade-deployments in Control Center Manager.
But I get the error dialog box.
“RTC-5270: Invalid upgrade plan.
The deployment has been aborted due to a problem with generating a valid upgrade plan.”
I have already executed this Sql: grant_upgrade_privileges.sql
and the Location access is: Host:Port:Service
I am using OWB 10.2.0.3.0/33 on Windows
Is it advisable to do upgrade-deployments in a production environments?

I had also the same problem with the upgrade function in OWB. I also executed the SQL Script "grant_upgrade_privileges.sql". But also in my case the error was still present.
On Oracle Metalink I found the Note:387919.1
with this "quiet" interesting side note:
"... Please note that grant_upgrade_privileges.sql script needs to be executed before that table is created (deployed) the first time. If this script has not been executed before the tables are deployed the first time it will not any more be possible to upgrade the table definition. Even if this script is executed it will not any more be possible to upgrade a table deployed before the execution of the script. "
Now, after replacing all tables, I´m able to upgrade them. Luckily I was still in the Development phase when I discoverd this circumstance of OWB behaviour.
But I still have problems to upgrade tables with TIMESTAMPS in it. It seems that Oracle does not support the upgrade function for some Datatypes.
Does anyone of you has some experience in that problem or even better some way to solve (workaround) it?

Similar Messages

How to view the DDL script prior to object deployment in OWB 10g R2?

How to view the DDL script prior to object deployment in OWB 10g R2?
Here is what I' looking for: in 10gR2, let's say I've built dimension X, but it's not deployed yet. I've selected one of the deployment options, let's say: "Deploy to Catalog only". Now, I'd like to see a DDL script that will be executed at the deployment time. Where can I find this script? What screen? What menu?
Thanks,
vr

Viewing the Scripts
After you have generated scripts for your target objects, you can open the scripts and
view the code. Warehouse Builder generates the following types of scripts:
■ DDL scripts: Creates or drops database objects.
■ SQL*Loader control files: Extracts and transports data from file sources.
■ ABAP scripts: Extracts and loads data from SAP systems.
To view the generated scripts:
1. From the Generation Results window, select an object in the navigation tree on the
left of the Generation Results dialog.
2. Select the Scripts tab on the right of this dialog.
The Scripts tab contains a list of the generated scripts for the object you selected.
3. Select a specific script and click the View Code button.
Regards,
Marcos

Specify the AzureFallbackToDeleteAndRecreateIfUpgradeFails in upgrade deployment

Hi,
Anyone has en example how to specify the upgrade deployment property AzureFallbackToDeleteAndRecreateIfUpgradeFails?
I notice it in the Visual Studio Publish Profile XML, also on the VS UI. Is that A VS only feature?
Checked the MSDN page: http://msdn.microsoft.com/library/azure/ee460793.aspx, but can't anything mentioned there about this property.

Hi,
What is AzureFallbackToDeleteAndRecreateIfUpgradeFails property? Could you give me some guidance? If it is under service configuration file, please consider change service configuration file to base-64 encoded, then write this encoded in request Configuration
section.
<Configuration>base64-encoded-config-file</Configuration>
Best Regards,
Jambor
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

How to use weblogic.DDconverter Tool to upgrade Deployment Descriptors.

Hi,
I want to know how to use weblogic.DDconverter Tool to upgrade Deployment Descriptors using EAR of previous verisons(JDK and weblogic).
Regards,
Neeraj

Looks like the protocol is not correct (Unable to connect to 'http://localhost:7001': Destination unreachable)
Could you try the t3 protocol, for example,
java weblogic.Deployer -adminurl t3://localhost:7001 -username weblogic -password welcome1 -listapps

Cant deploy in OWB 9.2.0.4.0 after database upgradation

We are facing a problem with OWB 9.2.0.4.0 after the database is upgraded from[b] oracle 9.2.0.1.0 to 9.2.0.8.0.
Initially OWB 9.2.0.4.0 was working fine with oracle 9.2.0.1.0 (i.e. the owb runtime and target schema was in this database) but due to some urgent requirement we need to upgrade the database to oracle 9.2.0.8.0. After the oracle upgradation we cant deploy any ETL object from the OWB design(9.2.0.4.0) to the runtime. Also we cant create any new runtime repositories into the upgraded database.
Can anyone please suggest whether this is happening due to version incompatability?
or is there any patches/scripts that needs to be run after the database upgradation?
Thanks in advance.

Hi there,
I upgradet a cuple of Times a Database
and use the OWB (and the Workflow) after that again.
I didn´t know exactly what´s going on by you
but maybe after the Upgrade there´re no more OWB Informations in teh Schemata?
You can start the Design Browser (ControlCenter), right?
Question: Is the DesignRepository in the same Instance
as the Runtime Repository?
If not, then i think it´s the best Way to reinstall the OWB Components using the Runtime Wizzards (runtimeinst.sh under UNIX).
If it is the same Instance try to take a look in the Log-Files from the Upgradeprocess.
You can even try to view the Oracle Documentations
about what´s exactly happened during the Upgrade.
Sorry, i think that didn´t help you very much, but i think at least with a new Installation of the OWB Components you can sure to fix your Problem.
Regards
Lone

Post-upgrade tasks for OWB 10g Release 2

Hi,
we're planning to upgrade from OWB 10.1.0.2 to 10.2.x.
Now, I'm trying to get a clear view on what will be the "post-upgrade" tasks, in terms of manual adaptations, corrections, etc. to get everything back up and running after the upgrade ...
E.g. : by means of test al already exported a dimension, and imported it in the 10.2 repository ... Turned out that in the pre-10.2 version, there were no validation problems, but as from 10.2 (although the upgrade and import were successful), I got 19 warnings and 2 errors ... because each level needs to have a business or surrogate key ...
It' s things like that I'm especially interested in, in order to determine the workload after the upgrade ...
So, feel free to share your experiences ; I'm looking forward to read them!
Thanks!
Grtz.

Here are some from my list. I stopped maintaining it a while ago, we have lots more where this came from. Some of it also apply to older versions of OWB.
Key lookup     You are to choose input and output attributes BEFORE being able to choose loookup table, all in a time consuming wizard
Expressions     Copy and paste into expression editor, validation fails for expressions using lowercase (such as "upper" or "substr")
Renaming attributes     Not possible anymore, you need to open details
Adding a table component     You must browse in a tree structure (time consuming), not search functionality anymore
Import     Import converting from 9.2 hangs after 15% in about 10% of all imports
Import     Some mappings are not possible to import, a total rewrite is necessary
Deployment     You can only deploy about 5-10 times before you need to restart OWB
Memory leak     If something goes wrong in OWB, memory is never cleared - JAWAW.exe needs to be removed manually from memory
Import     Importing mappings one by one (as this is sometimes needed due to OWB), the last directory used is OF COURSE not default when importing the next time
OWB GUI / mapping editor     When working with components in the mapping editor, an object hidden behind the object you are actually working with is selected prior to the object in visual focus to the user
BUG!     Urgent: CASE - wrong generated Code
ANSI JOINS     Remove ANSI-SQL from mapping configuration, otherwise (+) outer joins will not work
Transformations     Not possible to enter a transformation such as "sysdate", you must find it in a huge tree structure list (no search available)

Can deployment affect source system due to registering / deployment in owb

HI ,
We have one 3 source system and one target system. Through OWB 10 g r2 we have defined connections for all locations like source staging target repository, workflow manager...etc.
Target system IP address was going to change. So we did reset the IP in our all connection information and register them again. then deployed all the location with the objects like mapping process ..etc.
But Incident happened is,
There is one of source (production) system, which have 10-12 tables. and those tables dropped and create as replace action of deployment.
Ideally It should not happened through ETL tool.
what are the steps or process which will ensure that if any changes need to do at server side (like IP address changes) , will not affect the production source system by re-registration of locations and re-deployment.
needs reply on urgent basis.
any body can help on this ....
Regards
Umesh
Edited by: Umesh2 on Jan 14, 2009 10:38 PM
Edited by: Umesh2 on Jan 14, 2009 10:39 PM

In the Runtime Audit browser you should find a Location Summary report. From here you can view and edit the connection information for the registered location. Note that this information remains in the runtime, and does not get pushed back to the design repository, so if you re-register a location you'll overwrite the changes.
The upgrade action will generate an upgrade plan for any changed objects - eg instead of dropping a table and then creating it again, it may just do an "alter table" statement. This ensures that the data is retained, and is the default deployment action for any data object.
Using hostname instead of IP address is the right way to go, and should mean that when you changed the IP address of a server, the hostname remains the same. Unless you also changed port numbers and service names then you should not need to make any changes to the locations, or perform any redeployments.
The Runtime Audit Browser is installed as part of OWB, so I'm not sure why it's not available in your environment. Could someone have removed the shortcuts from the menus? You could try reinstalling the OWB client and see if the shortcuts re-appear.
Nigel.

Upgrading tables from OWB...

I am trying to upgrade a table in OWB using the deployment action of Upgrade. The old table exists in the target schema.
When I try to upgrade it I get this error:
RPE-01008: Recovery of this request is in progress.
RTC-5351: A serious error occured whilst generating the Impact Report. Please review the Runtime Service Log.
Where can I find the Runtime Service Log? What could be causing this error?
Thank you.
Brian

The runtime log is in:
<oracle_home>\owb\log
They are named after the runtime repos user... I'm guessing something went wrong in a previous deployment.
You can try to stop the runtime service and restart it. Use the start and stop scripts in the owb\rtp\sql directory.
Jean-Pierre

Upgrade patches from OWB 10.2.0.1 to OWB 11.2.0.3

We are upgrading from OWB 10.2.0.1 to OWB 11.2.0.3
We have upgraded database from 10.2.0.1 to 11.2.0.3
What are the patches that needs to be applied before upgrading the repository?
What are the patches that needs to be applied after upgrading repository?

follow this link
http://www.orafaq.com/forum/t/119954/2/
http://wiki.oracle.com/search/threads/10.2.0.1?contains=10.2.0.1
http://www.oraclealchemist.com/oracle/patching-from-10201-to-10203/
also i assume there is no RAC involved in your case.
Edited by: Darthvader-647181 on Dec 2, 2008 8:13 AM
Edited by: Darthvader-647181 on Dec 2, 2008 8:14 AM

ADF 11.1.1.4 to 11.1.1.6 upgrade - deployment issue

Hi all, just wondering if anyone has any thoughts or suggestions on the following.
I have 2 applications that we are in the process of upgrading from 11.1.1.4 to 11.1.1.6, AppA and AppB. These applications use MDS with custom security, so we have a CustomUserCC class. Both applications use the same security model and both have their own copy of the class, they are not pulling it from a separately deployed jar (it's only about a dozen lines of code), so it deploys within the EAR file.
Our WebLogic 10.3.6 server has two managed server instances, one for each application. AppA deploys cleanly and runs on either of the managed servers, but when I try to deploy AppB, to either MS, I get the following:
[August 28, 2013 9:15:31 AM EDT] Initiating deploy operation ...
[August 28, 2013 9:15:31 AM EDT] Saving the oracle configuration changes to archive.
[August 28, 2013 9:15:32 AM EDT] Archive: /oracle/Middleware_10.3.6/user_projects/domains/MyDomain/sysman/upload/deploy/AppB/ archive/AppB.ear
[August 28, 2013 9:15:32 AM EDT] Targeting MDS repository: com.bea:Name=mds-MyRepo,Type=JDBCSystemResource to target MS1.
[August 28, 2013 9:15:32 AM EDT] Targeting MDS repository: com.bea:Name=mds-MyRepo,Type=JDBCSystemResource to target MS1 completed.
[August 28, 2013 9:15:33 AM EDT] [Deployer:149191]Operation 'deploy' on application 'AppB' is initializing on 'MS1'
[August 28, 2013 9:15:39 AM EDT] [Deployer:149193]Operation 'deploy' on application 'AppB' has failed on 'MS1'
[August 28, 2013 9:15:39 AM EDT] oracle.mds.config.MDSConfigurationException: MDS-00035: cannot load the class: com.my.app.faces.mds.CustomUserCC.
[August 28, 2013 9:15:39 AM EDT] MDS-00035: cannot load the class: com.my.app.faces.mds.CustomUserCC.
[August 28, 2013 9:15:40 AM EDT] Deploy operation failed.
The 11.1.1.4 version of both apps always deployed just fine on our WebLogic 10.3.4 servers, and both apps run just fine from within JDeveloper 11.1.1.6. I've checked in the EAR file and the class is there.   I've also checked the adf-config.xml files for both apps, and I don't see any significant differences. Both apps also use the same MDS repository; they use different partitions, but changing the partition doesn't seem to help.
The only other difference between the two apps is that AppA was built in 11.1.1.4, but AppB was built in ADF 10 and upgraded to 11.1.1.4. The CustomeUserCC class wasn't added until after the upgrade, since MDS wasn't available in 10.
I'm checking to see if there's any library differences in the applications, but so far I haven't spotted anything.
Looking in the domain logs from the admin server I see the following stack trace, but I don't know if it's much help.
Message ID    BEA-149078
Message Level    1
Relationship ID    0
Component    AdminServer
Module    Deployer
Host    weblogic302.my.domain
Host IP Address    172.25.105.242
User    <WLS Kernel>
Thread ID    [ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'
ECID    dcd1267481484937:77815f4a:140bade15de:-8000-000000000000161a
Message    Stack trace for message 149004
oracle.mds.config.MDSConfigurationException: MDS-00035: cannot load the class: com.my.app.faces.mds.CustomUserCC.
at oracle.mds.config.CustConfig.getCustClassList(CustConfig.java:365)
at oracle.mds.config.CustConfig.loadFromBean(CustConfig.java:277)
at oracle.mds.config.CustConfig.<init>(CustConfig.java:242)
at oracle.mds.config.MDSConfig.loadFromBean(MDSConfig.java:781)
at oracle.mds.config.MDSConfig.loadFromElement(MDSConfig.java:848)
at oracle.mds.config.MDSConfig.<init>(MDSConfig.java:491)
at oracle.mds.config.MDSConfig.<init>(MDSConfig.java:440)
at oracle.mds.internal.lcm.deploy.DeployManager.deploy(DeployManager.java:516)
at oracle.mds.internal.lcm.deploy.DeployManager.startDeployment(DeployManager.java:204)
at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:215)
at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:77)
at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)
at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62)
at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:284)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:209)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: oracle.mds.config.MDSConfigurationException: MDS-00035: cannot load the class: com.my.app.faces.mds.CustomUserCC.
at oracle.mds.config.CustConfig.getCustClassList(CustConfig.java:365)
at oracle.mds.config.CustConfig.loadFromBean(CustConfig.java:277)
at oracle.mds.config.CustConfig.<init>(CustConfig.java:242)
at oracle.mds.config.MDSConfig.loadFromBean(MDSConfig.java:781)
at oracle.mds.config.MDSConfig.loadFromElement(MDSConfig.java:848)
at oracle.mds.config.MDSConfig.<init>(MDSConfig.java:491)
at oracle.mds.config.MDSConfig.<init>(MDSConfig.java:440)
at oracle.mds.internal.lcm.deploy.DeployManager.deploy(DeployManager.java:516)
at oracle.mds.internal.lcm.deploy.DeployManager.startDeployment(DeployManager.java:204)
at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:215)
at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:77)
at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:199)
at weblogic.application.internal.flow.BaseLifecycleFlow.preStart(BaseLifecycleFlow.java:62)
at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:284)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:649)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:209)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:749)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:160)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:171)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:47)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

I've tried repeatedly slamming a brick into my monitor, no change.
Then this is very good monitor
Maybe you can compare files before and after MDS is enabled and see what files are changed in this process.
So create new blank app, make backup, enable/configure MDS, add CC class and then use some file compare tool(WinMerge, ...) to compare this with your backup.
Hopefully after that you will know where to look in original app.
Also, you can put CC in separate jar and check if this will work.
Dario

BI deployment from OWB 10.2 (Paris)

Hi all,
I'm curious what success or lack thereof you have had in deploying dimensions and cubes relationally to Discoverer with OWB 10.2.
Do you deploy item folders for dimensions and cubes seperately?
Do you create item folders for every level of your dimensions?
Do you create "complex" item folders instead having the dimensions and cubes prejoined?
I'm working on our BI deployment and would love to know some of your experiences with either method. Also, are you able to fully manage your EULs with OWB or do you have to use Discoverer Administrator post-deployment?
Thanks in Advance,
Mike

Hi Mike.
Do you create item folders for every level of your dimensions?You must create item folders for all information you want to show to end-euser or you need to add to a calculation, hierarchy, join, etc. It depends on how you have imported the folder in discoverer. Make sure the item you want to add to a folder is not already there.
Do you create "complex" item folders instead having the dimensions and cubes prejoined?Read the best practices document/thread. You'll see that using db views might be an alternative.
I never tried this using OWB 10g R2. In previous releases you'd have to create collections, export/import it to discoverer and that was the most you could do using OWB.
As far as I've read the documentation, the "Defining Business Intelligence Objects" chapter in OWB users guide, it seems like there's a lot stuff you can do in OWB.
However you'll see the need to edit the Business Areas using Discoverer Adm Edition. Read this thread, you'll see there's plenty of stuff you won't be able to do using OWB (like editing security/privileges, for instance):
Discoverer Adm. Best Practices
Also, read the following document:
http://www.oracle.com/technology/products/discoverer/pdf/Discoverer_10_1_2_BestPractices.pdf
You'll find answers for most of your questions.
Regards,
Marcos

Scripts generated post deployment in OWB

Hi,
I have a query regarding the sccripts generated after deployment of any object in OWB.
When we create a map in OWB and deploy it, two scripts are generated. one is the package which physically create the mappning process in target schema. The other script is a ddl script e.g. map_name_drop.ddl.
Can you provide me an understanding why this ddl script is generated.
Many Thanks

Nothing specific at the moment but would like to know if its possible and to what level its possible to interact via scripts or other methods with the applications in CS6 after deployment
Can projects be opened in Captivate via script?
Can publishing settings be set for labs of captivate installs so all have a common set of custom settings?
Can projects be published via scripting?

Deployment in OWB

Hi,
I have developed a mapping in OWB.Now there is a new source which is added in the mapping.
Is it possible to execute the mapping with the new changes without deploying the mapping or re-deploying the changed mapping.
Is there any option in OWB for deployments where in I can execute the changed mapping (with the changes incorporated)without re-deploying the mapping
Thanks in advance

Hi,
As far as I know you can't. "Deploying" means that you (re)create the mapping code in the package in your target schema in the database.
When you "run" a mapping, it means that you execute that package.
So, if you change your mapping and want to run it with the new design, you will have to redeploy, to get the changes into the package body. Otherwise it will keep running the 'old' design mapping code.
Hope this helps,
Kind regards,
Ed

Deployment of OWB-ETL? How did you do it?

Hi folks,
I'm considering the deployment of a large set of Mappings in OWB that are part of the population of a Data Warehouse.
I see that the the Process Flow/Oracle Workflow is one suggestion for developing and deploying the framework for bringing these various Mappings under one logical unit.
However I'm begining to wonder if the investment in the skills and training and effort required to implement the process flows in Oracle Workflow are worth it.
I want to take a poll and also find out what people who implemented medium to large ETL using OWB have to say about this.
a) What tool did you use to logically bind together the various mappings in your Warehouse.
b) If you did create process flows, were you able to implement it with Oracle Workflow, and if so whats the stability of that system?
c) If you did indeed create a Process Flow, have you tried running or implemented that workflow (XPDL file) in any of the other commercially available or Open Source workflow engines out there? If so please detail your experience.
Thanks,
Sridhar

I have done a nuance of this with one SFDC instance partitioned with multiple Record Types (a virtual new instance) The record type kept the contact from being visible to multiple business units and allowed for 'intentional' duplicates.
We had at one time 5 different BUs with possible contact overlap.
I have also implemented a single Eloqua instance with 2 BUs and 2 CRMs. The logic for lead flow was the big challenge. We turned off the native Activity write to the CRM systems and instead used the contact activity overview link. Though not ideal, it solved for a ton of failed API calls where the contact/lead ID did not exist in Eloqua.
Every situation is unique, there are no easy answers for this scenario.
I am happy to get on the phone with you to talk more.
Nathan

Execute a mapping deployed with OWB 9.0.4 from SQL*Plus

Hello,
I could execute a mapping designed with OWB 9.0.3 from SQL*Plus with the next sentence:
SQL> exec my_mapping.main;
But now, with OWB 9.0.4, mappings are deployed as functions (in 9.0.3 were deployed as procedures) and they need parameters.
Somebody know how I can execute deployed mappings with OWB 9.0.4 from SQL*Plus? I don't know the parameters I need to call a mapping.
Thanks in advance,
Pedro.

Well, I've solved the problem with roles but
I've executed the script called sqlplus_exec_template.sql and it fails at Stage 2 because the next sentence
l_audit_execution_id := wb_rt_api_exec.open(l_task_type, l_task_name, l_location_name);
returns me NULL.
It is not clear the value that the variable called l_location_name have to stored. The script explain that this variable store the physical name of the
location to which the task was deployed. I understand that this variable have to store the schema where the mapping was deployed. That's right?
So I called the script in this manner:
SQL> @sqlplus_exec_template OWBRUN904I OJBHT PLSQL MY_MAPPING "," "," ;
where OWBRUN904I is the name of the Runtime Repository Schema, OJBHT is the
schema where MY_MAPPING is deployed, PLSQL is the task type and MY_MAPPING is
the name of the mapping I've designed.
Can you tell me why the scripts fails?
Regards,
Pedro

Upgrade-deployment in OWB 10.2.

Similar Messages

Maybe you are looking for