API5036: Client Version 10.1.0.4 is not compatible with Repository version

I have an OWB repository version 10.1.0.1.0 and a client of 10.1.0.2.0. We have have been running this fine. I need to upgrade to 10.1.0.4.0 of OWB so I can begin to use a 10gR2 database as my target. I exported (database wise) my repository and imported it into the 10.2.0.1 database - all went well. I now went to upgrade the repository from 10.1.0.1.0 to 10.1.0.4.0 and ran the shell in the ../bin/unix dierctory. It ran fine, yet when I connect to the repository using the 10.1.0.4 client I get the "API5036: Client Version 10.1.0.4 is not compatible with Repository version 10.1.0.1.0" as if I never ran the DT upgrade shell. I then noticed the shell provided with the 10.1.0.4 install is DTupg92to10g.sh and I am not upgrading a 92 repos to a 10 repos. Is there a upgrade for 10.1.0.1.0 to 10.1.0.4.0?
Thanks,
Sean

for OWB metadata, run this following script
<OWB_HOME>/owb/reposasst/upg/upg10gTo10104.sql
For runtime data
<OWB_HOME>/owb/bin/unix/RT_upgrade_to_10_1
     This is only if it's NOT upgrading to 10gR2 database
If you are upgrading to Oracle10g Release 2 with partial export and
import and if you are changing the database instance or the computer
hosting the database, then run the migration script:
– For UNIX, navigate to OWB_HOME/owb/bin/unix and run
RT_migrate_to_10_1.sh.
The RT_migrate_to_10_1.sh prompts you for several parameters:
the User Name and Password of your original Runtime Repository
schema, the database connection string for your original Runtime
Repository (in the form of host:port:servicename), the User Name
and Password for your new Runtime Repository schema (whose values
should match the original Runtime Repository), and the database
connection string for the new Runtime Repository (also in the form of
host:port:servicename). Additionally, as it runs, the script prompts
you for SYS User Names and Passwords for the Oracle Database
instances for any Target Schemas and Oracle Workflows being upgraded.

Similar Messages

  • API5036: Client version 10.2.0.1.31 is not compatible with repository ver..

    API5036: Client version 10.2.0.1.31 is not compatible with repository version 10.2.0.2.0
    I got this error after upgraded with patch p5696353_10202_AIX64-5L
    I tried to log in but there was a pop up dialog told me about this error. Do I have to install new client version?? I cannot find owb client 10.2.0.2.0 on the download site. Would you guys help me to get though this please?? Any solotion if I still used owb client version 10.2.0.1??
    Rgds,
    Godtee

    Hi Godtee,
    you have to use the same version on the client as on the server.
    There is only one software package containing owb client and server components. Use it for server and client side installations.
    It seems that you have patched your server installation to 10.2.0.2.0. Apply this patch to your client installation and you will be able to connect to the repository with version 10.2.0.2.0
    Regards,
    Carsten.

  • OMS version 10.2.0.4.2 is not compatible with repository version 10.1.0.4.0

    Im trying to start the database enterprise manager and I get this error on the log file:
    OMS version 10.2.0.4.2 is not compatible with repository version 10.1.0.4.0 Repository needs to be patched.
    Database version is 11.2
    O.S. version is: Linux 2.6.9-78.0.0.0.1.ELsmp #1 SMP Fri Jul 25 14:41:56 EDT 2008 i686 i686 i386 GNU/Linux
    I use this to upload database and console:
    export ORACLE_HOME=/opt/oracle/product/11.2.0/dbhome_1/
    export ORACLE_BASE=/opt/oracle/
    export ORACLE_SID=orcl
    /opt/oracle/product/11.2.0/dbhome_1/bin/lsnrctl start
    /opt/oracle/product/11.2.0/dbhome_1/bin/dbstart /opt/oracle/product/11.2.0/dbhome_1/
    /opt/oracle/product/11.2.0/dbhome_1/bin/emctl start dbconsole
    when I excecute that, I see this on the console:
    Oracle Enterprise Manager 11g Database Control Release 11.2.0.1.0
    Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
    https://192.168.2.210:1158/em/console/aboutApplication
    Starting Oracle Enterprise Manager 11g Database Control ........... started.
    Logs are generated in directory /opt/oracle/product/11.2.0/dbhome_1/machine_one_lega/sysman/log
    So I try to go there, and the web browser shows this:
    503 Service Unavailable
    Service is not initialized correctly. OMS version 10.2.0.4.2 is not compatible with repository version 10.1.0.4.0.
    Can you help me find this solution?
    thanks

    Hi Ingenio,
    This problem sometimes occur when the listener is not running, hence connection cannot be done without listener.

  • OMS can not start - OMS not compatible with repository version.

    Hello,
    I have Enterprise Manager 11g installed on a Unix environment. The OEM was running successfully at beginning. But after the database was restarted, I got the below error when I tried to start OMS.
    -bash-3.00$ /OMS_HOME/bin/emctl start oms
    Oracle Enterprise Manager 11g Release 1 Grid Control
    Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
    Starting WebTier...
    WebTier Successfully Started
    Starting Oracle Management Server...
    Oracle Management Server is not functioning because of the following reason:
    Oracle Management Server version is not compatible with repository version. Repository needs to be Upgraded.
    I run ./emca -config dbcontrol db -repos recreate, but the problem is still there.
    My database is 11.2.0.1.0
    Grid control is 11.1.0.1
    Weblogic is 10.3.2
    I can open Weblogic Server 11g Administration Console but not /em.
    -bash-3.00$ ./emctl start oms
    Oracle Enterprise Manager 11g Release 1 Grid Control
    Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
    Starting WebTier...
    WebTier Successfully Started
    Starting Oracle Management Server...
    Oracle Management Server is not functioning because of the following reason:
    Oracle Management Server version is not compatible with repository version. Repository needs to be Upgraded.
    Please help,
    Thanks,
    George J

    See note "Oracle Enterprise Manager 10g Grid Control Certification Checker \[ ID 412431.1 \]". There is a nice application which shows all the compatible combinations. Only 10.2.0.4 is supported with 10GR4 OMS (10.2.x repository version).

  • Client version 10.2.0.2.8 is not compatible with repository 10.2.0.1

    What should I do to correct the error below?
    I have a database 10.2.0.1 and client 10.2.0.2.8
    TIA

    Hi,
    as I understand you have patched OWB client with 10.2.0.2 patch but forget to upgrade OWB repository
    Regards,
    Oleg

  • OMS version 10.2.0.4.0 is not compatible with repository version 10.2.0.1.

    I restored database resulting in the above error.
    I guess my database backup was taken before grid control upgrade to 10.2.0.4.
    how to fix this? Thanks.

    See note "Oracle Enterprise Manager 10g Grid Control Certification Checker \[ ID 412431.1 \]". There is a nice application which shows all the compatible combinations. Only 10.2.0.4 is supported with 10GR4 OMS (10.2.x repository version).

  • OMS version 10.2.0.4.0 is not compatible with repository version 10.1.0.5.9 Repository needs to be patched.

    I received this message when attempting to restart the oms after performing:
    emca -deconfig dbcontrol db
    emca -repos recreate
    emca -config dbcontrol db
    in an effort to fix the problem:
    Getting Chrome browser error "SSL connection error" Error code: ERR_SSL_PROTOCOL_ERROR after upgrade
    Can you advise me as to where I may find this 10.2.0.4 patch for my repository?

    OMS is a term used with Grid Control (OMS app tier with Repository database and multiple agents).
    emca is used with DB Express on a single database instance to manage the DB Express repository info.
    They cannot be used together.
    Did you have Grid Control?:  If so, i believe you've corrupted your repository and need to restore, or contact Oracle Support.

  • Urgent Please!!! API5036 Client version 10.1.0.4 is not compatible...

    I have a new server with W2003, Oracle 10.2.0.1 and OWB 10.1.0.4
    My old server have W2000, Oracle 9.2.0.6 and OWB 9.0.4.10
    I have a Project with OWB 9.0.4.10 and I have done the Migration Procedure explained on the OWB 10g Installation Manual “Chapter 3 - Upgrading to 10g Release 1 (10.1) and Migrating Data” and when I want to connect to OWB Client Repository I receive the error:
    API5036 Client version 10.1.0.4 is not compatible with repository version 10.1.0.1. OWB will now exit.
    Why is it????? What happens???? Could you help me please!!!
    Thanks very much in advance!!!!

    for OWB metadata, run this following script
    <OWB_HOME>/owb/reposasst/upg/upg10gTo10104.sql
    For runtime data
    <OWB_HOME>/owb/bin/unix/RT_upgrade_to_10_1
         This is only if it's NOT upgrading to 10gR2 database
    If you are upgrading to Oracle10g Release 2 with partial export and
    import and if you are changing the database instance or the computer
    hosting the database, then run the migration script:
    – For UNIX, navigate to OWB_HOME/owb/bin/unix and run
    RT_migrate_to_10_1.sh.
    The RT_migrate_to_10_1.sh prompts you for several parameters:
    the User Name and Password of your original Runtime Repository
    schema, the database connection string for your original Runtime
    Repository (in the form of host:port:servicename), the User Name
    and Password for your new Runtime Repository schema (whose values
    should match the original Runtime Repository), and the database
    connection string for the new Runtime Repository (also in the form of
    host:port:servicename). Additionally, as it runs, the script prompts
    you for SYS User Names and Passwords for the Oracle Database
    instances for any Target Schemas and Oracle Workflows being upgraded.

  • Error :"The provider is not compatible with the version of Oracle client"

    Hi guys!
    I'm facing this problem:
    When my .Net application tries to access the DB, I get this error message above.
    The application is into the same machine of DB and the operational system is Windows Server Enterprise 64 bits.
    I'm comparing to another machine that has the same scenario but runs in Windows Vista 64 bits. This problem doesn't happen and I can normally access the DB.
    The both database versions are 10g Release 2 (10.2) and all components from Oracle Database Components 10.2.0.2.21 are installed as the containing bellow:
    -Oracle Data Provider for .NET 1.x 10.2.0.2.20
    -Oracle Data Provider for .NET 2.0 10.2.0.2.20
    -Oracle Developer Tools for Visual Studio .NET 2003 10.2.0.2.20
    -Oracle Developer Tools for Visual Studio 2005 10.2.0.2.20
    -Oracle Provider for OLE DB 10.2.0.2.20
    -Oracle Objects for OLE 10.2.0.2.20
    -Oracle Services For Microsoft Transaction Server 10.2.0.1.0
    -Oracle Net 10.2.0.1.0
    -Oracle Universal Installer 10.2.0.2.0
    Oracle.DataAcces.DLL is 2.102.2.20 and it is reference in my .Net app (that is published and located into IIS).
    These are the Oracle assemblies installes in 'C:\Windows\Assembly':
    Windows Vista Machine:
    ASSEMBLY NAME VERSION CULTURE PUBLIC KEY TOKEN PROCESS ARCHITECTURE
    Oracle.DataAccess 10.2.0.100 Neutral 89b483f429c47342
    Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
    Oracle.DataAccess.resources 10.2.0.100 pt-BR 89b483f429c47342
    Oracle.DataAccess.resources 10.2.0.100 it 89b483f429c47342
    Oracle.DataAccess.resources 10.2.0.100 fr 89b483f429c47342
    Oracle.DataAccess.resources 10.2.0.100 es 89b483f429c47342
    Oracle.DataAccess.resources 10.2.0.100 de 89b483f429c47342
    Oracle.Management.Omo 2.102.2.20 Neutral 89b483f429c47342 x86
    Oracle.VsDevTools 2.102.2.20 Neutral 89b483f429c47342 x86
    Policy.10.1.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
    Policy.10.2.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
    Windows Server Machine:
    ASSEMBLY NAME VERSION CULTURE PUBLIC KEY TOKEN PROCESS ARCHITECTURE
    Oracle.DataAccess 10.2.0.100 Neutral 89b483f429c47342
    Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
    Oracle.DataAccess 2.102.2.20 Neutral 89b483f429c47342 x86
    Oracle.DataAccess.resources 10.2.0.100 pt-BR 89b483f429c47342
    Oracle.DataAccess.resources 10.2.0.100 zh-CHT 89b483f429c47342
    Oracle.DataAccess.resources 10.2.0.100 zh-CHS 89b483f429c47342
    Oracle.DataAccess.resources 10.2.0.100 ko 89b483f429c47342
    Oracle.DataAccess.resources 10.2.0.100 jp 89b483f429c47342
    Oracle.DataAccess.resources 10.2.0.100 it 89b483f429c47342
    Oracle.DataAccess.resources 10.2.0.100 fr 89b483f429c47342
    Oracle.DataAccess.resources 10.2.0.100 es 89b483f429c47342
    Oracle.DataAccess.resources 10.2.0.100 de 89b483f429c47342
    Policy.10.1.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
    Policy.10.2.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
    Policy.9.2.Oracle.DataAccess 10.2.0.100 Neutral 89b483f429c47342
    Policy.9.2.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
    What should I check and do to solve this problems?
    Thanks for help,
    Anderson

    Hi,
    Often the error "The provider is not compatible with the version of Oracle client" is raised when the unmanaged dll OraOpsX.dll can't be found, can't be loaded, or is the wrong version. For version 10.2.0.x of ODP.NET and .NET Framework 2.x the file should be called "OraOps10w.dll" and should be found in the %ORACLE_HOME%\bin directory.
    Since the ODAC pieces are installed on the same host as the database, are they in a separate Oracle Home or the same Oracle Home as the database software? If there are multiple Oracle Home directories, which one is in the system path first?
    I would start with verifying the version of OraOps10w.dll and the system path on the server. You might also confirm that the Oracle Home directory (and everything under it) has the following permissions for Authenticated Users:
    - Read & Execute
    - List folder contents
    - Read
    Regards,
    Mark

  • The provider is not compatible with the version of Oracle client

    We are running Server 2012 64 bit with multiple homes one is 32 bit and the other 64 bit. We installed the 64 bit first then the 32 bit next in order to get our Classic ASP WebSite that is using COM+ and OLEDB to see the provider.
    C:\oracle\product\12.1.0\x86
    C:\oracle\product\12.1.0\x64
    The other Websites are ASP.Net 4.0 and are running in 64 bit application pools. They are using a DAL .Net assembly built x64 with a reference to the 64 bit ODP.Net version 4.121.1.0 in C:\oracle\product\12.1.0\X64\client_1\odp.net\bin\4.
    I also see there is another folder C:\oracle\product\12.1.0\X64\odac_1\odp.net\bin\2.x with version 2.121.2.0. We are on running Framework 4.0 but when I switch to this version it works but with the version out of the bid\4 we are receiving the following error when the 64 bit Websites call the assembly:
    The provider is not compatible with the version of Oracle client
       Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 
    Exception Details: Oracle.DataAccess.Client.OracleException: The provider is not compatible with the version of Oracle client
    Source Error:
    Line 87: mDataSource = dataSource
    Line 88: mConnectionString = GetDBConnectionString(dataSource)
    Line 89: mConnection = New OracleConnection(mConnectionString)
    Line 90: mParams = New List(Of IDbDataParameter)
    Line 91: End Sub
    I have not been successful in getting this to work after spending endless hours, so any help would be appreciated.

    Hi,
    Oracle Client/ODP build with certified Visual C++ Libraries so application using ODP.NET requires "runtime components of Visual C++ Libraries" to be installed.
    Oracle Database Client installation includes the Visual C++ Libraries but ODAC doesn't contain these libraries which may cause such issue.
    Please check the Note 43208.1 for the particular version of Visual C++ installs with Oracle Database Client installation(e.g. 11.2.0 Database Client installs  Visual C++ .NET 2005) and also you can refer the windows event log error massage to verify which version of Visual C++ is missing.
    thanks and regards
    Venkat

  • 'The provider is not compatible with the version of Oracle client' exceptio

    Hi
    I installed ODAC-11.1.0.7.10 Beta on my development system and developed a .net application which uses Oracle.DataAccess.dll to connect to Oracle10g database.
    the application is working fine, means opening connection successfully when I run it from my development system. but the same application is throwing
    'The provider is not compatible with the version of Oracle client' exception when I run it on my 10g database server system.
    what I need to do to run the application successfully on the machine where 10g server exists?
    any help is appreciated.
    thanks,
    harry

    Hi Harry,
    I am not sure why you installed 11.1.0.7.10 Beta as 11.1.0.7.20 has been released and you should not be using the beta at this time. That error message is because the dependencies being loaded by the process are the wrong version. When you deploy an ODP .NET application using 11.1.7.x, you need to make sure you deploy it to a machine where the 11.1.0.7.x dependencies are installed. My guess is if I read your poat correctly is that Oracle.DataAccess.dll version 11.1 is loaded but its finding 10.2 dependencies on the target deployment box.
    HTH
    Jenny

  • Provider is not compatible with this version of Oracle client

    I am trying to access Oracle(10.2) DB from a .NET 2.0 Console Application.(.exe) in a Win 2008.Web code is also on the same Win 2008 system
    The Web application works fine and connects to teh DB , but when I try to run any of the Console applications it gives the error as:
    Provider is not compatible with this version of Oracle client.
    The Oracle.Dataaccess.dll versions which are available in GAC are 1.102.2.20 and 2.102.2.20.
    and the Oracle client installed is 10.2.0.100
    The complete error message is:
    Unhandled Exception: Oracle.DataAccess.Client.OracleException The provider is not compatible with the version of Oracle client
    at Oracle.DataAccess.Client.OracleInit.Initialize()
    at Oracle.DataAccess.Client.OracleParameter..ctor(String parameterName, OracleDbType type, ParameterDirection direction)
    Can any of you help me find a reason for this error.
    Thanks in advance!!

    Hi Greg,
    I found out another reason this error was appearing.I am compiling the Console application in a 32-bit machine on 32-bit Oracle client.
    The pre-compiled DLL and EXE is then exported to a 64-bit Win 2008 machine.
    Also,The code has been compiled with ‘Any CPU’ .
    The Web Application on the same system is working because the "Enable 32-bit Applications" is set to True.
    Are there any DLLs or EXEs created when compiling in the 32-bit machine which is not compatible with the 64-bit machine?
    Please help!!
    Thanks,
    Veena

  • Another: The provider is not compatible with the version of Oracle client

    Hi everybody,
    We still have problems with the ODP dll. with our .Net development. I copied all the dlls as mentioned here: [http://splinter.com.au/blog/?p=156] and in many other posts here in the forum. The .Net development works fine on our Development PCs (WIN XP32) and on many other PCs in the company. But we still have some PCs (As well WIN XP32) that come up with the Error: The provider is not compatible with the version of Oracle client.
    Has anyone an idea???
    Thanks a lot for your help
    Best Jan

    Hi Jan,
    If there has never been any Oracle Client software installed on the machines, it seems unlikely that there would be Oracle policy files and version(s) of Oracle.DataAccess in the GAC. But, yes, the CLR will look to the GAC first for loading the Oracle.DataAccess assembly. I'm not sure what Framework or Domain setting would be involved here if there is no Oracle client installed. Are the machines configured the same as far as Regional/Language settings, etc?
    One thing you might be able to try is to create an application configuration file and enable ODP.NET trace in the file. This is an ODP.NET 11.1 new feature. However, it's possible the error will prevent the trace file from being created. You would create a file named YourApplicationName.exe.config and here is a sample of the minimum content to enable ODP.NET trace:
    {noformat}
    <?xml version="1.0" encoding="utf-8" ?>
    <configuration>
     <oracle.dataaccess.client>
       <settings>
         <add name="TraceFileName" value="c:\odpnet2.trc"/>
         <add name="TraceLevel" value="1"/>
       </settings>
     </oracle.dataaccess.client>
    </configuration>
    {noformat}
    I wish I had an easy answer for you!
    Regards,
    Mark

  • The provider is not compatible with the version of Oracle client... again!

    Please, please, please help me!
    I get the error, "The provider is not compatible with the version of Oracle client", intermittently on my Test Server. Strangely, without restarting the server or IIS, my application suddenly decides that I don't have the right Oracle client. I don't have any such issue on my local machine even though I'm using the same Oracle 11g client from Beta 1.
    I have Oracle 11g (D:\Oracle11g\product\11.1.0) installed. I tried specifying which assembly to use in my web.config:
    <compilation debug="true" defaultLanguage="c#">
    <assemblies>
    <add assembly="Oracle.DataAccess, Version=2.111.5.10, Culture=neutral, PublicKeyToken=89b483f429c47342" />
    </assemblies>
    </compilation>
    I'm not even trying to use a 10g client with the Providers as discussed here: "The provider is not compatible with the version of Oracle client"
    What I don't understand is why this error comes and goes?!?! Has anyone experienced anything like this?

    The server is Win 2003. The local development machine is WinXP.
    ...I was trying to wait to install Beta 2 because of the nasty bugs reported on this forum.
    I'm now seeing that ORACLE_HOME wasn't set on my server because my co-worker removed the path. Somehow it was able to find an Oracle Home on the server, but apparently, it didn't always find the same home causing this error intermittently.
    Now, my question is how can I get my application to use the 11g Client as its Oracle Home, while my co-worker can use 10g Client as his Oracle Home? To be a bit more specific, he needs to use an ODBC client to connect because his application uses Classic ASP.
    Is this possible, or are we going to have to set up separate machines?
    Bee

  • 'The provider is not compatible with the version of Oracle client error' popping up randomly

    I have several asp.net pages running on an application server which generally work without issue. However I've had the Server error "The provider is not compatible with the version of Oracle client error" crop up twice seemingly randomly that affects all of my pages that interact with the DB server. A simple reboot of the application server solves the issue and the pages run again with no problems. What could be causing this problem?

    Sorry if I wasn't clear initially. Basically I've got 2 different applications in 2 different IIS folders on the webserver, each with several asp.net pages. They work fine for a period of time and then inexplicably that error gets thrown and affects all of my asp.net pages in both applications. The admin tells me that the other older applications on the same server are unaffected. A simple reboot of the server fixes the issue until the next time it happens (I can't identify any consistent point where this crash happens, the admin originally suggested that there might be something in my code causing a memory issue). I had the same applications hosted on my local machine for a time and this never happened as well as it never happening when I run them in localhost. How can I trace whether or not another part of my application is trying to load ODP.NET by itself? How can I verify the DLL search order for my application?

Maybe you are looking for

  • Pages, printing: still problem with drop shadows . Frustrated.  :

    Hi - I've spent most of the afternoon trying to get my Pages document to print properly. I am experiencing the drop-shadow issue :heavy black clump instead of artfully placed& delicate. Printouts do not resemble what is onscreen or in preview etc. Ha

  • Bulk fetch taking long time.

    I have created a procedure in which i am fetching data from remote db using database link. I have 1 million data to fetch and the row size is around 200 bytes ( The table is having 10 attribute sizing 20 bytes each ) OPEN cur_noit; FETCH cur_noit BUL

  • Problem in Popup Window in OAF

    Hi, We are populating a table results page in OAF based on the search items. In the Results table, we have a link(to a new page that has only one table region) on a column(itemstyle: link) so that it should open in a popup modal window. On closing th

  • OLAP variable / bex variable, need help !

    Dear All, I will definitely award point for this solution. I have a new assignment on another client, and they had activate BW customer exit, RSR00001 BW: Enhancements for global variables in reporting for almost 5 years ago. As a consequences, inclu

  • Needed smartform to determine page format automatically.

    Hi I have a reqirement to print the smartform output in Letter format paper for one company code and it should print it in A4 size paper for rest of the company codes. I am using R/3 4.6c I tried with this code data: lx_sf_header(31) type c, field-sy