TARGET database is not compatible with RMAN version

Hi all,
we have an issue related to RMAN version.
A few weeks ago we update our 10.2.0.1 Oracle Database to 10.2.0.4 using 6810189 pacth set.
Now when we try to execute RMAN this is the output:
Recovery Manager : Release 11.1.0.6.0 - Production on Jue Nov 20 12:20:57 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.2.0.4 needed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN
(I translate the spanish message, maybe the words is not exactly the same in the english version)
As is shown in the output the RMAN version installed by the pacthset is higher than database version, is there a way to downgrade RMAN or to solve this issue?
Thanks in advance,
Alex

I'm pretty sure patchset 6810189 does not install RMAN executable 11g. I did several patchings to 10.2.0.4 and that never happened. Patching may sometimes leave components at a lower level than the patchset,but never the opposite is true. That would be definitely a bug. So you (or someone else) installed 11g software.
Werner

Similar Messages

  • TARGET database is not compatible with this version of RMAN

    I am trying to register a database (version 8.0.4) on my catalog database which is version 8.1.7.
    I get the following error:
    RMAN-06185: Recovery Manager incompatible with TARGET database: RMAN 8.0.4 to 8.0.4 required
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-06429: TARGET database is not compatible with this version of RMAN
    Does this mean that my RMAN database has to be 8.0.4 ?
    What happens if my RMAN database is 8.0.4 and target is 8.1.7 ?
    Thanks for any help,
    Sameer

    check RMAN compatibility matrix
    Target/Auxiliary Database|| RMAN Executable|| Catalog Database ||Catalog Schema
    8.0.3 8.0.3 >=8.x 8.0.3
    8.0.4 8.0.4 >=8.x >= 8.0.4, see "Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases"
    8.0.5 8.0.5 >=8.x >= 8.0.5, see "Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases"
    8.0.6 8.0.6 >=8.x 8.0.6
    8.0.6 8.0.6 >=8.1.x >=8.1.x
    8.1.5 8.1.5 >=8.1.x >= 8.1.5
    8.1.6 8.0.6.1 >=8.x 8.0.6
    8.1.6 8.0.6.1 >=8.1.x >= 8.1.x
    8.1.6 8.1.x >=8.1.x >= RMAN executable
    8.1.7 8.0.6.1 >=8.x 8.0.6
    8.1.7 8.0.6.1 >=8.1.x >=8.1.x
    8.1.7 8.1.x >=8.1.x >= RMAN executable
    9.0.1 >=9.0.1 >=8.1.x >= RMAN executable
    In other words to backup 8.0.4 version u need a separate schema in catalog database and which will be only used for 8.0.4

  • RMAN-06429: TARGET database is not compatible with this version of RMAN

    he Hi,
    how can i solve this issue . how i will upgrade the Rman. My production database details are below
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
    PL/SQL Release 10.2.0.1.0 - Production
    CORE 10.2.0.1.0 Production
    TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
    NLSRTL Version 10.2.0.1.0 - Production
    while i'm configuring rman i'm getting below error . please help me.
    C:\Documents and Settings\vj.dcruz>rman target / catalog rman01/rman01@upp
    Recovery Manager: Release 11.2.0.1.0 - Production on Wed Sep 14 08:18:02 2011
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.2.0.0 required
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-06429: TARGET database is not compatible with this version of RMAN
    rgds,
    john

    Johnvd wrote:
    Hi Hemant,
    i'm doing same thing login 10.2.0.0 database and configure the rman but while connect target its saying that my Recovery Manager: Release 11.2.0.1.0 - Production on Wed Sep 14 09:04:59 2011
    how its happening is there any where i have to change the path.
    Regards,
    johnJohn, you need to use the RMAN binary which is located in bin folder of Oracle Database (ie /u01/oracle/product/10.2/db1/bin). You shouldn't use "rman which comes with Oracle 11g client".
    If you are using windows, run the following commands in command prompt and then copy/paste the output:
    echo 5ORACLE_HOME%
    echo %PATH%
    If you are using unix, run the following commands in terminal and then copy/paste the output:
    echo $ORACLE_HOME
    echo $PATH
    Regards
    Gokhan

  • RCVCAT database is not compatible with this version of RMAN

    I am getting the below error while trying to configure rman catalog datababse.
    rman target prod_dba/Pass1234@proddb catalog cat_dba/Pass1234@catdb
    Recovery Manager: Release 9.2.0.1.0 - Production
    Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
    connected to target database: TESTDB (DBID=2409515669)
    connected to recovery catalog database
    recovery catalog is not installed
    RMAN>
    RMAN> register database;
    recovery catalog is not installed
    recovery catalog is not installed
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of register command at 07/20/2007 19:05:40
    RMAN-06429: RCVCAT database is not compatible with this version of RMAN
    RMAN>
    And Oracle version is same in proddb and catdb
    SQL> select * from v$version;
    BANNER
    Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
    PL/SQL Release 9.2.0.1.0 - Production
    CORE 9.2.0.1.0 Production
    TNS for 32-bit Windows: Version 9.2.0.1.0 - Production
    NLSRTL Version 9.2.0.1.0 - Production
    any inputs...
    Thanks.

    Hi,
    when upgrading catalog am getting the error like,
    error occurred in source file: krmk.pc, line: 6986
    text of failing SQL statement: ╠≥`☺
    ORACLE error from recovery catalog database: ORA-00942: table or view does not e
    xist
    error occurred in source file: krmk.pc, line: 6986
    text of failing SQL statement: ╠≥`☺
    ORACLE error from recovery catalog database: ORA-00942: table or view does not e
    xist
    error occurred in source file: krmk.pc, line: 6986
    text of failing SQL statement:µ`☺
    ORACLE error from recovery catalog database: ORA-00942: table or view does not e
    xist
    Whether i need to run catpath.sql etc on the db?

  • RMAN-06429: RCVCAT database is not compatible with this version of RMAN

    Hi There,
    I just want to confirm there is no work around for the issue I am having. Here is my situation:
    I have four Oracle 8i databases that can not be removed because of client requirements. These 8i databases have there own RMAN catalog which is 10G (Originally there were Oracle 8i, 9i and 10g databases using it but are now moved to 11g catalog). Databases are backing up fine. However, all the other databases are using the RMAN 11g Catalog. I want to point the Oracle 8i databases to point to the RMAN 11g recovery catalog. I created an 8i schema, however, i'm getting the following error message: RMAN-06429: RCVCAT database is not compatible with this version of RMAN. It's pretty straight forward, however, I wanted to put the question out there to see if there are any work arounds. I would prefer to have only one RMAN recovery catalog.
    Thanks in advance.
    J

    Hello;
    I know of no way around the RMAN Compatibility Matrix. I would keep a second catalog DB for these older databases. Or go NOCATALOG. I checked all my sources and if there's a better option I sure did not find it. What breaks if these go to Oracle 9?
    http://arjudba.blogspot.com/2010/03/about-rman-compatibility-matrix.html
    Ask Tom
    http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:518622203320
    Additional Information :
    OERR: RMAN 6429 %s database is not compatible with this version of RMAN [ID 70776.1]
    RMAN-06439: Compatibility Between 8.1.5 RMAN Executable and 8.1.6 Catalog [ID 104728.1]
    Best Regards
    mseberg
    Edited by: mseberg on Sep 7, 2012 8:27 AM
    Edited by: mseberg on Sep 7, 2012 10:53 AM

  • Unable to refresh the schema of FIM MA.Getting an error in Event viewer ""the current version of database is not compatible with the one expected by Forefront Identity Manager service. The current version of database is : 1116. The expected version is :1"

    Hi,
    We have installed FIM MA with an account that have all the sufficient rights.It got created successfully and worked for Full Import and Full Sync. But, due to some version incompatabilities, we have installed a patch.PFB link for the patch.
    http://support.microsoft.com/en-us/kb/2969673/en-us
    Now, we are trying to refresh the schema of FIM MA. While doing that we are facing an error "Failed to connect to database". The user account with which we are connecting has read and write permissions on DB.In the event viewer some errors are
    logged like  "the current version of database is not compatible with the one expected by Forefront Identity Manager service. The current version of database is : 1116. The expected version is :1122" with event ID 3. PFB images for more detailed
    view.
    Please advice how to fix the issue.
    Thanks
    Prasanthi.

    Hello,
    seems to me that you maybe only updated the syncengine but not portal/webservice.
    I had that error once after an recovery from scratch and forgot one of the hotfixes to apply to all services.
    -Peter
    Peter Stapf - ExpertCircle GmbH - My blog:
    JustIDM.wordpress.com

  • This database was connected to a Microsoft Access Services site that is not compatible with this version of Microsof Access. You cannot make design changes or modify data in database.

    Hello All,
    I am getting this error while I am connecting my access database website for the change
    "This database was connected to a Microsoft Access Services site that is not compatible with this version of Microsof Access. You cannot make design changes or modify data in database."
    I am using SharePoint 2010 and Microsoft Office 2010.
    I have created one Contact Database Site and now I am trying to modify the layout of the form in Access. and I am getting the error that I have mentioned.
    Please provide help on it.
    Thanks in Advance....

    Hello All,
    I got the answer, we have to enable the port 80 or where the access service is deployed and we have to change Trust setting and also, enable the macro from Access.
    Hope this will help to other....

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

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

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

  • 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 version of this file is not compatible with the version of Windows you're running.[...]".What can I do?

    I must run a 32-bit programe  on a windows 64-bit operating sistem, and i receive this message:"The version of this file is not compatible with the version of Windows you're running.[...]". I tried with Troubleshoot compatibility - didn't
    work. I tried set to run in compatibility mode for Windows XP in file properties window and it didn't work.  What can I do more? I
    must run this programe to acces my database.

    Hello qqnicol,
    What program do you run?
    Please contact the software provider to confirm if this 32-bit program can run in 64-bit Windows.
    As some programs can only run in specific version of Windows, please download the right version of software.
    Most programs designed for the 32-bit version of Windows will work on the 64-bit version of Windows. Notable exceptions are many antivirus programs.
    Device drivers designed for the 32-bit version of Windows don't work on computers running a 64-bit version of Windows too.
    Best regards,
    Fangzhou CHEN
    Fangzhou CHEN
    TechNet Community Support

  • Windows desktop application -- version of this file is not compatible with the version of Windows you're running

    I am developing on 64-bit Windows7 Enterprise using VisualStudio 2013.  I created a new Windows desktop VB.net application and just created a release build of the default solution/project targeting "Any CPU".  I provided the EXE to a
    colleague who is also running 64-bit Windows7 Enterprise but receives the following error...
    "The version of this file is not compatible with the version of Windows you're running.  Check your computer's system information to see
    whether you need an x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher."
    I changed the build configuration to create a "x86" build but my colleague received the same error.  Any ideas why this would be happening (I checked and my colleague has .Net4 Framework installed as well)?  Thank you for your time and
    response!
    Sunish Abraham
    "The version of this file is not compatible with the version of Windows you're running. 
    Check your computer's system information to see whether you need an x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher."

    Hi sunisha,
    According to your description, you'd like to run the application in your colleague's computer.
    I provided the EXE to a colleague who is also running 64-bit Windows7 Enterprise but receives the following error...
    If you want to test the application, you could provide the whole Debug folder to colleague instead of the single exe.
    "The version of this file is not compatible with the version of Windows you're running. Check your computer's system information to see whether you need an x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher."
    Check if the collegue's computer is running 64-bit windows:
    Enter Control Panel, click on System and Security.
    Under this, you can view the system type. This will describe whether you have 32-bit or 64-bit.
    You can also try compatiblity mode.
    If the program is not compatible, then you may try to install and run the program in compatibility mode.
    Use the following steps:
    1)   Right click on the Program
    2)   Click on Properties
    3)   Click on Compatibility tab
    4)   Select Run this program in compatibility mode and select Windows Vista or whatever operating system the program was running successfully.
    And if you still have questions, I suggest you deploy the application to the Local Network with clickOnce, then your collegue can install the application from the network.
    #ClickOnce deployment
    http://msdn.microsoft.com/en-us/library/t71a733d(VS.80).aspx
    And also, you could recreate a new small application in your computer in Any CPU, then check if this small new application can work well in your colleague's computer. This can judge if the problem is caused by your application.
    If you have any other concern regarding this issue, please feel free to let me know.
    Best regards,
    Youjun Tang
    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.

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

Maybe you are looking for

  • Integrating XI 3.0 with PI 7.1 directly

    Hi    We have a need to directly integrate XI 3.0 ( SP23 ) with another Pi 7.1 ( SP7 ). Can we use XI adapter type to do this communication - has anybody out there done this and not faced issue using XI adapters to do this  owing to this version diff

  • XSL ABAP:  XI runtime parameters

    Hi all I have created an XSL Transformation on the ABAP stack to use in an interface mapping that is called in a Business Process. In this XSLT mapping I need to include the MessageId. According to http://help.sap.com/saphelp_nw04s/helpdata/en/83/220

  • TRUE/FALSE problem

    I got a wired situation with a VI I wrote. I have a case TRUE/FALSE structure, and first of all, the true-part is ALWAYS first executed. When this part is done, I execute the false-case, for message handling and so on. But in the true case, I generat

  • Help signing in

    Hi, I have set up a new account as I can't sign in. I requested a new password but it sent the request email for the new account. Therefore I can't get to my old account. The online help just keeps looping and not solving the problem. Therefore, How

  • Unable to install apps on iphone 3

    Hi Can any one help please. My iphone for some reason will not update or install any further apps.  I select the app that I want to install and it prompts me for my password, I put in my password and the icon appears for a short second then disappear