ODI repository version conflict

I just finished installing ODI 11.1.1 on my laptop, however when when I tried to connect to a Repository I get a message telling me that the repository I am trying to access is on version 10.1.3.5 and I cannot connect to it. This repository is part of an App install which I wanted to analyze since I will have to make changes to it.
Is there a way to do this with the version I have installed (11.1.1) or do I have to install 10.3.5?
If I have to install 10.1.3.5, can I have two installs on my Windows 7 laptop? (using one at a time, of course) or do I need to uninstall 11.1.1 and install 10.1.3.5?
Thanks,
Dan

You can install both alongside each other and indeed will have to as the 11g client is not compatible with 10g , the repository structure is different.
Just put them in different homes and you will be fine.

Similar Messages

  • Possible version conflict, sending purchase order to SUS in MM-SUS scenario

    We are currently trying to get the MM-SUS scenario working. In this
    scenario, we create a purchase order in the ERP/MM system. The
    purchase order is then transferred into SUS via XI/PI.
    After creating a purchase order in the MM system, the purchase order
    reaches the SUS system, but then errors-out in the SUS system upon
    posting. The specific error is paraphrased as follows:
    No interface action for sender or receiver found (from Trace)
    PARSE_APPLICATION_DATA
    CX_ST_MATCH_ELEMENT
    System expected the element http://sap.com/xi/SAPGlobal20/Global;
    PurchaseOrderRequest
    We suspect a version conflict. The SUS version is 7.01. The XI/PI
    system is version 7.11.
    Can you confirm or rule-out a version conflict?
    The Integration Builder scenario we are using is Plan
    Driven Procurement with Supplier Enablement.
    We have tryed many variations in Integration Builder, but all
    produce errors in SUS.  The test tool in Integration Builder also shows errors
    for certain message types.  The message type ORDERS.ORDERS02
    needed to be added manually, and did not come along with the scenario.
    Edited by: Bill Guderian on Mar 19, 2010 4:53 PM

    Any clue from here.
    Note 936003 - ERS Invoice causes conversion error within SRM
    When the SRM system attempts to process an ERS Invoice sent from the MM backend, a PARSE_APPLICATION_DATA CX_ST_DESERIALIZATION_ERROR fault is thrown.
    Other terms
    CX_ST_DESERIALIZATION_ERROR PARSE_APPLICATION_DATA SUS SRM EBP ERS Invoice XI Exchange Infrastructure Mapping
    Reason and Prerequisites
    This error will occur when the IDOC does not have a VPREI value; it is the result of an error within the divide logic of the XI mapping operation.  This operation is performed within the XI system.  A calculation of NETWR/MENGE is performed; however, the result is not properly formatted.  As such, 72.30/10 produces a result of 7.2300002. This value is too long for the inbound SRM proxy and hence the error is thrown.
    Solution
    The solution to this problem is to add a FORMATNUM function within the XI mapping operation.  This restricts the result to 2 decimal places, which adheres to the definition of the inbound proxy.
    Step by step directions on how one implements the FORMATNUM function are as follows:
    1. Log into the XI system with SAPGUI
    2. Start the Integration Builder:Design tool (for steps on how to do this, review the steps below):
        a. Run transaction sxmb_ifr
        b. This will cause a browser to come up.  Select the Integration Repository link
    3. In the left pane, select the Objects tab
    4. Navigate to the SAP SRM SERVER ' SAP SRM SERVER 5.0 ' http://sap.com/xi/SRM/SupplierEnablement/Global --> Mapping Objects --> Message Mappings folder
    5. Double-click on MM2SUSInvoice
    6. The right pane will display the mapping object
    7. Select Edit mode
    8. In the box that contains the output (Message Type: InvoiceRequest), navigate to InvoiceRequest ' Invoice ' Item ' Price ' NetUnitPrice
    9. Double-click on the Amount element and you should see the mapping, represented graphically in the bottom pane
    10. In the status line of the graphical editor, select Arithmetic from the list box:
    11. To the right of the listbox, scroll until you see the FormatNum function
    12. Click on FormatNum, which will cause the function to be added to the graphical editor.  You may drag the box as desired
    13. Select the connection that binds the if/then/else to the Amount box by grabbing the arrow within the input of the Amount
    14. Release the drag of the connection while over the input to the FormatNum box.  This will reassign the output of the if/then/else to the input of FormatNum
    15. Create a connection between the output of the FormatNum box and the input of the Amount box.  You accomplish this by clicking within the output and releasing within the input (respectively).
    16. Save the modified mapping object
    17. Activate the changes
        a. In the left pane, select the Change Lists tab
        b. Navigate to the Standard Change List entry
        c. Right-click the Standard Change List entry and select Activate
        d. Select only MM2SUSInvoice if more than one item is available, and press the Activate button
    18. This will complete the required modification.

  • 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 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).

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

  • Using JCO error Wrong repository version = 0 encountered.

    Hi Guru,
    We convert our existing Java Jco program to call RFC Sender adapter and XI should forward the request to RFC receiver adapter to our ECC.
    We found that when we create client connection using gwhost, gwserv and tpname which is config in RFC sender adapter.
    In our Java program throw error in the step of mRepository.getFunctionTemplate.
    The error is "Wrong repository version = 0 encountered.".
    It seems the program can not access function template from repository.
    Anyone have this experience before, please advise
    Thanks you.

    It's working now.
    For your knowledge, it seems it was something wrong inside the jrfc.jar.
    The problem is not exactly the same but the solution is to apply OSS note 816491.

  • Version conflict in PI QA system

    Hi All,
    We are facing version conflict issue in QA system.
    We transported a Mapping object from Dev to QA and after transporting it is giving Version conflict at QA.
    This thing happen because some user has edited mapping program at QA level and activated .
    We thought of transporting a deleted object first then the latest active version. But my doubt is that when we transport the same mapping program with same name PI will bring back object along with its history.
    Can anyone having any idea about how to resolve this conflict.
    Regards,
    Navneet

    Hi Ninu,
    Thanks.
    We activated the conflicting version from conflict tab and then transported the dummy changes from DEV to QA to verify it wont give version conflict any more.
    it worked fine and conflicting version which we activated at QA considered as latest version for transport.
    Regards,
    Navneet

  • File Transport: Version conflict.

    Hi,
    I have a doubt on a particular scenario while transporting object from QA to PRD using File transport.
    I have exported a tpz file say 1.tpz from QA with say the following objects
    Obj_1(ver 1.0)
    Obj_2(ver 1.0)
    Obj_3(ver 1.0)
    Now before this 1.tpz is imported in PRD few more changes happend to Obj_3 and I exported again a file say 2.tpz
    Now this 2.tpz has only Obj_3(ver 2.0)
    Now the basis has by mistake Imported this 2.tpz file before importing the 1.tpz file. SO in my PRD the object Obj_3 is existing  with a advance version i.e 2.0
    Now my doubt is can we Import 1.tpz now in PRD and then again import 2.tpz ?
    I am having a feeling that we will definately get in version conflict. Even if I ignore the warning during transport and go ahead with this procedure of importing 1.tpz and then 2.tpz again, will it impact my scenarios.
    I am lookign for a quick suggestions.
    Regards,
    Rahul.

    Hi Rahul,
    If you import V1 file first & later V2, it will not impact on your scenarion & you wil be able to see latest object in PRD.
    But V2 is already imported so import of V1 may not be successful.
    You may generate a new export if possible & transport this. It should include all object with their lastest version.
    Regards
    Sushil

  • Repository version 10.1.2.0.2  s/b  10.1.2.3.0

    Hi all,
    i was upgraded my as 10g 10.1.2.0.2 and bi 10.1.2.0.2 to 10.1.2.3.0
    following the instruction from the patch 10.1.2.3 . i did update the database to 10.1.0.5 successfully, upgrade infrastructure to 10.1.2.3.0 and also upgrade BI to 10.1.2.3.0
    they are all up but when i checkthe BI it is still using REPOSITORY VERSION 10.1.2.0.2
    would someone please advise for me how to bring this repository to version 10.1.2.3.0
    Thanks in advance.
    Regards,

    please make sure that you have followed all steps of this Patch 10.1.2.3.
    specifically. that you applied SW Upgrade to all instances (infra and all midtiers) and later applied metadata repository upgrade.
    thanks
    AMN

  • XI 3.0 Version Conflict after SP 10 import

    My XI 3.0 integration builder shows a version conflict for IDOC adapter meta data after we have implemented support package 10.
    What needs to be done ?

    Hi Peter,
    We have this issue as well. not sure it is too much of an issue though.
    Cheers
    Colin

  • API5036. Repository  version nul ??

    API5036: Client version of 10.1.0.2.0 is not compatible with repository version null. OWB will now exit.
    installed the runtime repository
    installed the target repository
    installed the design repository
    tried to connect using the owb client. which gave the above error.
    I use 10g both owb and database locally, my operating system is windows 2000
    how can i solve this problem?

    Most likely your design repository installed was not successful. Please see this previosu post on further diagnostic tips: Re: OWB API5036 err
    Nikolai Rochnik

  • ODI repository and Java EE agent on different servers

    Hi all,
    I ahd created ODI repository on one data server(172.18.59.67) through RCU. Now due to some memory issues i ahd to install the ODI software on another server (172.18.41.44) and also configured the java ee agent on this second server. Will that be a problem while invoking web service through ODI?
    Thanks and Regards,
    Sourav

    Hi SH
    But while testing a web service through ODI web service (my agent is connecting successfully)... i am getting this error:-
    1#Error in ODI invocation WS ODIInvoke. ODI-1274: Agent Exception
    Caused by: oracle.odi.core.config.WorkRepositoryResourceFailureException:
    oracle.odi.core.exception.OdiRuntimeException:
    oracle.odi.core.exception.OdiRuntimeException:
    Failed to lookup dataSource from JNDI for name {java:comp/env/jdbc/odiWorkRepository
    where am i going wrong?
    Regards,
    Sourav

  • Odi repository passwords got reset

    Our ODI repository passwords got reset(both work and master).
    I have used agent encode to encode the master rep password, and changed it in the odiparams file.
    I am still unable to login to our production odi-which is execution only.
    Is there any other place where we should insert the new password?

    Fixed it.Had to login to topology and change the work rep password there.

  • Version conflict while targeting a vi to RT engine

    When i  am targeting a vi to Labview RT engine the message "Version Conflicts between Host Labview and RT engines" is coming.
    I am using a CFP-2100 and want to run a vi on it. (No PC should be connected with it)
    After targetting how will i execute it on CFP? is it automatically executable?
    Please reply me
    --Alok Trivedi
    Pune
    -AL☼K

    Thanx for replying me so soon.
    I am still stucked with the problem.
    I have Labview 7.0 installed on my computer and where i am making a vi which is to b loaded into CFP - 2100.
    Here are other versions i am using.....
    Field point VI manager 3.1.0
    Field point Drivers 5.1.0
    Data socket for Labview Real Time 4.2
    Labview Real Time 7.1
    NI-Irda RT 1.0.1
    NI-Serial RT 2.5.4
    NI-VISA 3.2
    NI-Watchdog 2.1.2
    When i switch the execution target to RT engine for remote device and enter the machine IP address it shows me "Version Conflict while targeting a VI to RT engine".
    I talked to Rahul about this and he well told me how to repair version conflicts between Host machine and RT engine. I went to remote machine and by right clicking on "software" installed all the versions to remote machine according to the host machine.
    the interesting thing is here it's not showing any version mismatch all the versions shown above are same as the host machine......but whenever i try to target the execution to RT engine it shows the version conflict.
    now what all questionis running in my mind are :
    1. Why the version conflict is occuring?
    2. If I get succeed to targeting the execution of vi onto RT engine how would i install it to CFP, if i just copy and paste it via FTP how will it know what vi is to run? i think we'r missing some way to "install" the vi into CFP.
    3 What is "RT Communication wizard for".......why it makes 3 other vi's....
    4. what are the total ways to run a vi onto CFP
    Waiting for your reply...
    thanks again
    -Alok Trivedi
    Pune
    -AL☼K

  • Version conflict between XE's ODP and VS2005/ODT's ODP

    Suppose you've just built an application with VS2005, .NET Framework 2.0, and Oracle Developer Tools for Visual Studio .NET with Oracle10g Release 2 ODAC 10.2.0.2.20 which uses Oracle.DataAccess.dll version 2.102.2.20. You want to be able to run the application on a client machine that has an Oracle XE database installed locally. Perhaps you even require that the client machine runs the Oracle XE Client. Unfortunately, even with both there seems to be a version conflict regarding Oracle.DataAccess.dll. Can anyone say what are the best practices for such a situation?

    Situation:
    1) Oracle XE (database with/without client) installs with the following two files in the <ORACLEXE_SERVER_HOME>/BIN directory:
    Oracle.DataAccess.dll v10.2.0.100 (for .NET Framework 1.0)
    OraOps10.dll v10.2.0.100 (for .NET Framework 1.0)
    2) Applications built with VS2005, .NET Framework 2.0, and Oracle Developer Tools for Visual Studio .NET with Oracle10g Release 2 ODAC 10.2.0.2.20 use Oracle.DataAccess.dll v2.102.2.20 (for .NET Framework 2.0).
    3) The client machine will be missing the following two files vital to the application: Oracle.DataAccess.dll v2.102.2.20 (for .NET Framework 2.0), OraOps10w.dll v2.102.2.20 (for .NET Framework 2.0). These two files can be found on the development machine in the <ORACLE_ODAC HOME>/odp.net/bin/2.x  and <ORACLEODAC _HOME>/bin directories, respectively.
    Action:
    When installing the application on the client's machine, place copies of the two missing files into the client's <ORACLEXE_SERVER_HOME>/BIN directory, overwriting the existing Oracle.DataAccess.dll v10.2.0.100 (for .NET Framework 1.0).
    Result:
    The application performs as expected.
    My immediate concern is that the client may object to replacing the existing Oracle.DataAccess.dll v10.2.0.100 (for .NET Framework 1.0). What are the best practices for such a situation?

Maybe you are looking for