RPE-01011

hi friends,
i am receiving a new error during deployment:
RPE-01011: cannot deploy to target database location because it doesn't have a compatible version.
Any help is greatly appreciated.
regards,
-viswanath

Good morning,
Have you checked previous postings on this error message?
Maybe they will tell you how to deal with it:
RPE 01011
Re: Getting RPE-01011
Cheers, Patrick

Similar Messages

OWB 10.1.0.4.0 deployment results in RPE-01011

We are deploying the same project, developed in OWB version 10.1.0.4.0, to both a test and production server. Since a reorganisation of those servers we've been unable to deploy mappings to the production site, due to an apparent version discrepancy:
RPE-01011: Cannot deploy to target database location because it does not have a compatible version.On the test site we have no problems, even though both databases are identical.
In the design repository, the module has system type (on the data target rider in the properties window) set to "Oracle Database 8i/9i/10g". For the same module, the pl/sql generation mode in the generation preferences is configured for "Oracle10g".
Version information of the databases:
Test:
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
PL/SQL Release 10.2.0.5.0 - Production
CORE 10.2.0.5.0 Production
TNS for HPUX: Version 10.2.0.5.0 - Production
NLSRTL Version 10.2.0.5.0 - ProductionProduction:
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
PL/SQL Release 10.2.0.5.0 - Production
CORE 10.2.0.5.0 Production
TNS for HPUX: Version 10.2.0.5.0 - Production
NLSRTL Version 10.2.0.5.0 - ProductionDoes anyone have an idea about what else can be wrong here? The versions are identical, yet OWB does not seem to recognise it as such...

Oops, never mind.. The answer is in here: Error RPE-01011 Raised when Deploying [ID 260860.1]

RPE-01011 target location incompatible / repository and target are same 11g

I got systematically error RPE-01011 signaling my target location is incompatible. My repository and my target are the same instance and i didn't change anything in the settings. The instance is an 11g database. I don't understand what the problem is. All scripts are execting correctly when i install then manually.

I am having the same problem trying to deploy objects created as per Oracle by Example: Oracle Warehouse Builder 11g. The database version is 11g Release 11.1.0.6.0 and all locations have 11.1 version. This is the second time I am running this tutorial, this time I modified the setup scripts to replace 10.2 by 11.1 but after rerunning all previous tutorials I got the same error.

Error RPE-01011 Raised when Deploying

Error RPE-01011 Raised when Deploying
OWB Client: 10.1.0.2.0
OWB Repository 10.1.0.1.0
Database: 10.1.0.2.0
Please Help,
Thanks,
Walter

1) Start the OWB OC4J Instance (start -> programs -> oracle-warehouse builder -> Start OWB OC4J Instance)
2) Once the OWB OC4J Instance is started, start the OWB Runtime Audit Browser (start -> programs -> oracle-warehouse builder -> OWB Runtime Audit Browser)
3) In OWB Runtime Audit Browser window, select the QA User ROLE and fill in the connections informations (runtime repository owner)
4) Click on the View Deployment report
5) Select the Location TAB
6) Select the target locations that have the Type Version still in the previous database version and click on "Unregister Selected Locations " Button
7) Start OWB client (Design)
8) Check that your target locations have the correct database version in the locations properties
8) Start the deployment manager and re-register each locations you unregistered

Deployment of objects in OWB10g with Personal Edition Database

When trying to deploy objects in a Personal Oracle 10g database with OWB10g, the following error occurs:
RPE-01011: Cannot deploy to target database location because it does not have a compatible version.
Deployment on the same database but on Enterprise Edition works fine.
Oracle does not support OWB on Personal Edition, but I found a workaround to use OWB on a Personal Edition database. The problem is that the Deployment Manager checks for the version number from PRODUCT_COMPONENT_VERSION where PRODUCT like 'Oracle%'. It returns the version number, but with this query no rows are returned in Personal Edition because the product name does not begin with 'Oracle' (Personal Oracle Database 10g).
I found a workaround in redefining the definition of the view SYS.PRODUCT_COMPONENT_VERSION so that it returns 'Oracle Database 10g Personal Edition' for the database component. The deployment manager will then find the correct number, and you can deploy just as you would with Enterprise Edition.
Statement used to redefine the view:
create or replace view sys.product_component_version as
(select
substr(banner,1, instr(banner,'Version')-1) product,
substr(banner, instr(banner,'Version')+8,
instr(banner,' - ')-(instr(banner,'Version')+8)) version,
substr(banner,instr(banner,' - ')+3) status
from v$version
where instr(banner,'Version') > 0
and
((instr(banner,'Version') < instr(banner,'Release')) or
instr(banner,'Release') = 0))
union
(select
substr(banner,1, instr(banner,'Release')-1),
substr(banner, instr(banner,'Release')+8,
instr(banner,' - ')-(instr(banner,'Release')+8)),
substr(banner,instr(banner,' - ')+3)
from v$version
where instr(banner,'Release') > 0
and
instr(banner,'Release') < instr(banner,' - ')
AND BANNER NOT LIKE '%Database%')
union
(select
'Oracle Database 10g Personal Edition',
substr(banner, instr(banner,'Release')+8,
instr(banner,' - ')-(instr(banner,'Release')+8)),
substr(banner,instr(banner,' - ')+3)
from v$version
where instr(banner,'Release') > 0
and
instr(banner,'Release') < instr(banner,' - '))
Regards,
Marko Bikker

See Oracle Database Express Edition License Agreement

OWB 9.2 on 10g?

At work, I'm running 9.2.0.2.8 on DBMS 9iR2. So, I export the .mdl file, email it home, and load it to a 9.2.0.2.8 client. I'm also running DBMS 10g. (10.1.0.2.0). I import the .mdl, and try to deploy some objects that are giving me a problem. Then, I get an RPE-01011 "Cannot deploy to target database location because it does not have a compatible version".
Just for fun, I do a SELECT from WB_RT_PLATFORM PROPERTIES, and property.RuntimePlatform.0.version is indeed 9.2.0.2.8, just like my client.
So what does this mean? Version incompatibilities between the original development RDBMS and my personal environment? Or what? The message is just a little bit cryptic!
Best regards,
Donna
p.s. here's the log:
22:46:51 [F4FB3] Runtime Platform Service Version 9.2.0.2.8 starting
22:46:51 [F4FB3] Platform Repository Name OWBRTowner on Service sabrina at Host localhost
22:46:52 [F4FB3] Recovery starting
22:46:52 [F4FB3] Service startup complete
23:20:59 [F4FB3] AuditId=2: Processing unit deployment request
23:20:59 [2BB514] Attempting to create adapter 'class.Oracle Database.9.2.DDLDeployment'
23:21:00 [2BB514] oracle.wh.runtime.platform.adapter.odb.TargetVersionIncompatibilityError: RPE-01011Cannot deploy to target database location because it does not have a compatible version.
     at oracle.wh.runtime.platform.adapter.odb.OdbDeploymentAdapter.deploy(OdbDeploymentAdapter.java:63)
     at oracle.wh.runtime.platform.service.controller.DeploymentController.deploy(DeploymentController.java:213)
     at oracle.wh.runtime.platform.service.controller.DeploymentController.deploy(DeploymentController.java:41)
     at oracle.wh.runtime.platform.service.DeploymentManager.run(DeploymentManager.java:51)
     at java.lang.Thread.run(Thread.java:484)
23:21:00 [2BB514] deploy_unit_done auditId=2
23:21:00 [F4FB3] AuditId=1: Request completed
23:23:02 [F4FB3] AuditId=77: Processing unit deployment request
23:23:03 [1A9334] Attempting to create adapter 'class.Oracle Database.9.2.DDLDeployment'
23:23:03 [1A9334] oracle.wh.runtime.platform.adapter.odb.TargetVersionIncompatibilityError: RPE-01011Cannot deploy to target database location because it does not have a compatible version.
     at oracle.wh.runtime.platform.adapter.odb.OdbDeploymentAdapter.deploy(OdbDeploymentAdapter.java:63)
     at oracle.wh.runtime.platform.service.controller.DeploymentController.deploy(DeploymentController.java:213)
     at oracle.wh.runtime.platform.service.controller.DeploymentController.deploy(DeploymentController.java:41)
     at oracle.wh.runtime.platform.service.DeploymentManager.run(DeploymentManager.java:51)
     at java.lang.Thread.run(Thread.java:484)
23:23:03 [1A9334] deploy_unit_done auditId=77
23:23:03 [F4FB3] AuditId=76: Request completed
23:29:24 [F4FB3] AuditId=100: Processing unit deployment request
23:29:24 [233D48] Attempting to create adapter 'class.Oracle Database.9.2.DDLDeployment'
23:29:25 [233D48] oracle.wh.runtime.platform.adapter.odb.TargetVersionIncompatibilityError: RPE-01011Cannot deploy to target database location because it does not have a compatible version.
     at oracle.wh.runtime.platform.adapter.odb.OdbDeploymentAdapter.deploy(OdbDeploymentAdapter.java:63)
     at oracle.wh.runtime.platform.service.controller.DeploymentController.deploy(DeploymentController.java:213)
     at oracle.wh.runtime.platform.service.controller.DeploymentController.deploy(DeploymentController.java:41)
     at oracle.wh.runtime.platform.service.DeploymentManager.run(DeploymentManager.java:51)
     at java.lang.Thread.run(Thread.java:484)
23:29:25 [233D48] deploy_unit_done auditId=100
23:29:25 [F4FB3] AuditId=99: Request completed

Hi Donna,
Are you implying you want to go from 10g to 9.2 using
import/export of MDL? I don't think this is tested
in-house, so you may want to test this...Hi Jean-Pierre
Umm. Not quite. I run 10g on my personal kit, but was trying to reproduce my client's environment.
Reinstalling 9.2 would work, no problem with that,
simply re-register the locations to the new box and
make sure the setup (runtime repos) runs on 9.2Yeah, true, but sod it. I already got so many version installations, it drives me crazy. I'll use my 10g OWB and that will be that.
(FYI, I have a five machine personal setup, including a huge SMP RAID box. I've got everything since 8.1.6 and Scalpels).
(Also FYI, I am a Principal Consultant in England in OWB, having used it since it first became commercially available). Now see my next post, and see how much help I need (because I am legally blonde).
Best regards,
Donna

Succesfully installed and setup an OWB 10.1.0.4 & Ora10gR2 & Windows 2003?

Hi,
I want to know if anyone has been successful in:
installing
configuring and
having a complete and working development environment using:
Windows 2003 AS SP1
Ora10gR2
OWB 10.1.0.4
Workflow 2.6.3
We tried several times, and after designing our first map we got error ''RPE-01011'' WHEN DEPLOYING A MAP IN OWB 10.1.0.4 RPE-01011
I found several entries reporting the same error, but all the solutions listed didn't work on our environment.
Any help is appreciate
Thanks
Silvio

We had a similar issue and opened a TAR, but no luck from oracle. We figured out that the install looks at 64 bit LD library, but actually uses the 32 bit. After setting this up in the runtime_service.sh script, the deployment went through and we are good to go.
shankar

Database upgrade to 11gR2

Client upgraded the development environment to 11gR2 (11.2.0.1) yesterday, and now mappings generated from OWB (client is 10.2.0.1.31) to development throw an RPE-01011 (incompatible version) error.
The OWB design repository is in a standalone database. That database has not been upgraded yet (at 10.2.0.4).
Would it be possible to use the 11.2 OWB design "piece" against a 10.2.0.1 repository, or is there a patch available that would allow the 10.2.X client to deploy to a 11.2.0.1 database?

Hi,
I wanted to start a new thread, but this one touches a similar problem:
A customer plans to migrate a huge DWH from 10gR2 to 11gR2; but there are over 2000 mappings which he don't want to re-deploy. In general, this is not recommendable, but would it work at all? A 11gR2 runtime executing 10gR2 generated mappings? My first thought was this "incomaptible versions" error. I haven't the infrastructure to test it on the fly, so I'm asking before answering to the customer.
regards
Thomas

False deployment results in SCCM

I have used the Customisation wizard to package a silent install of Adobe Reader X. We are upgrading from version 9. System Centre Configuration Manager reports a successful installation however on some computers this is not the case. On these computers there is an information type entry in the application log of Event Viewer. The source is MsiInstaller, Event ID: 11708 and a description of "Product: Adobe Reader X -- Installation operation failed.". Does anyone have any idea why this is being reported back to SCCM as successful? This also happens on some computers when deploying Acrobat X as well.
Thanks in Advance

Oops, never mind.. The answer is in here: Error RPE-01011 Raised when Deploying [ID 260860.1]

Data Warehouse Builder

I received this message when I attempt to deploy mapping objects:
RPE-01011 Cannot deploy to target database because it does not have a compatible version.

OBE is a good start, also I recommend OWB manuals and other books on OWB and data warehousing in general. Great deal of help you can find on blogs, this forum, and oracle wiki.
http://www.training-classes.com/learn/_k/o/r/a/oracle_warehouse_builder/_t/ilt/
http://blogs.oracle.com/
http://wiki.oracle.com/
And not to forget metalink.
https://support.oracle.com/CSP/ui/flash.html

Deploy OWB10g

I have a problem when i try to deploy:
rpe-01011 Cannot deploy to target database
I have oracle 10.1.0.2.0 DB
and 10.1.0.2.0 OWB
i have read the other post about this problem and didn't find a solution

Hi,
THe error message implies you're working with incompatible versions.
Did you check Metalink notes on this error message?
Try Note:260860.1 and otherwise http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=FOR&p_id=550653.996 or http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=FOR&p_id=500772.996.
Good luck, Patrick

Warehouse builder 9i

Received RPE-01011 Cannot deploy to target database location because it does not have a compatible version.

Hello
OWB is about to be installed and we're searching for a tutorial. A search of OTN and MetaLink has turned up no results. Can someone point me to a tutorial (if one exists)?
Thanks
Steve
[email protected]
There isn't a recent OWB tutorial. The next one being scheduled is for the next major release. Sorry.

RPE-01008: Recovery of this request is in progress in process flows.

Hi,
I am calling shell script as an userdefined activity in a process flows.
All the process flows were working fine.
Today, all the process flows wherever the shell script is called ended up with an error showing " RPE-01008: Recovery of this request is in progress".
Could any one please explain, what might be reason?
Thanks in advance.
Thank you,
Regards,
Gowtham Sen.

Hi,
we have exactly the same problem here.
Does anybody have a solution?
regards
Lutz

RPE-01012 after upgrade to 9.2.0.4

LS,
After upgrading OWB from 9.2.0.2.8 to 9.2.0.4, I'm getting the an error when trying to deploy code.
Getting the following error:
RPE-01012: Cannot deploy to the target location because it is owned by a different runtime platform.
I've read that I need to tell OWB that now it has to use the new (upgraded) repository, so I created a new repository runtime connection, pointing to the new rep-owner, but that was -obviously- to no avail.
Is there something else that needs to be done before code can be deployed again?
Cheers, Patrick

Good morning Nikolai,
I've read that the only new user/schema that needs to be created is for the runtime repository. Somewhere further in the coming 'story' it will appear (bold).
Let me explain how the upgrade went.
This is what the readme says for general steps:
1. Patch the Client Side (Design Time) install
2. Patch the Server Side install
3. Upgrade the Client Side (Design Time) Repository
4. Upgrade the Runtime Repository
5. Re-create the Runtime Repository connections
Also it states the following:
Note: Make sure that you have obtained the patch for the platform where your Server Side install is located. This may not be the same platform as your Client Side (Design Time) install. E.g. If you perform Design Time tasks on Windows, but deploy and execute on Solaris, you will need both the Windows and Solaris versions of the patch.
Since our database (9i) is running on AIX (5L) and the client is Windows 2000 Pro, both patches have been applied.
The DBA's have applied the AIX-patch for the server side, but also for the client (remark of one of the DBA's: "The runntime is installed on database and the client also installed on AIX side. I will do both."), so also "II.4. Upgrading the Design Time Repository".
On Windows I patched client as well as server installation (i.e. the copying of new files to OWB-home with two batch-files).
I did NOT run owb\bin\win32\DTupg92to9204.bat as stated in section II.4.1, because the DBA's had already done this... on AIX though.
Section II.5 has also been performed by the DBA's. Note the following here: "Create a new Runtime Repository in same database as the old Runtime Repository. DO NOT create new Target Schema(s) or new Runtime Access User(s). The In-place Migration will re-associate your current Target Schema(s) and Runtime Access User(s) to the new Runtime Repository. This step must be performed on the Server Side install." I assume the DBA's performed the in-place migration.
After this I was NOT allowed to run the indicated next three steps on the windows environment (I guess that makes sense since the new repository has already been created... but the owb home on my PC therefore is unchanged, don't know whether that matters, I guess it shouldn't).
In II.6 I have to connect to new environment. I therefore connect with my OWB-client using the same usr/pwd as always (since that didn't change), and in OWB I could see my project straight away (therefore I did NOT import the project that I have exported prior to the entire upgrade process).
I created a new runtime repository connection pointing at the new user.
And now the situation where deploying a mapping results in RPE-01012.
The funny thing is that I deployed 3 sequences (which have been defined BEFORE the upgrade), and that worked well. I also created a new table definition and deployed that, also no problem.
So... what's the verdict?
Cheers, Patrick

RPE-02040

I received this RPE-02040 Internal Error while deploying a process flow. I was unable to find any good explanation in Metalink or here on OTN. This error accompanies a cryptic text message.
This is what happened for me:
I changed a mapping so that it no longer accepted an input parameter. I replaced the new mapping in one of my process flows. Upon deployment of the process flow, I received this RPE-02040 error. The reason I got this error is because I replaced the new mapping definition in one of the process flows where it was called, but there were several other process flows that had not been updated with the new mapping. Once I updated all the process flows in the module, it was better. I was then able to deploy with no errors.
Hope this helps somebody. This OWB tool really lacks helpful documentation - online or otherwise. I've found this forum - and the experiences of others - to be the best source of info re: the OWB tool.

Hello!
See metalink note 406250.1 and bug 5742116.
This is the summary:
When binding a parameter of one activity directly to the parameter of another, the following error occurs at deployment:
RPE-02040: Internal error: <ACTIVITY_NAME> cannot be converted to a constant value
Note : This error is not alerted when validating the Process Flow
Cause:
It is not valid to bind a parameter of one activity directly to the parameter of another.
Regards,
Robert

RPE-01011

Similar Messages

Maybe you are looking for