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

Similar Messages

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.

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

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

SPROX_CHECK_IFR_ADDRESS - Repository Version

Hello Friends,
I am doing SPROXY configuration between ECC & PI. When I run the report "SPROX_CHECK_IFR_ADDRESS", the message "Cannot determine repository version" is coming.
What is repository version ? Where this is maintained ?
Can you kindly clarify ?
Kind regards
Jegathees P.

Use the following:
Create RFC dest : SAP_PROXY_ESR (use same name)
Connection type : G
Description : -
Target host : Your PI IP address
Path prefix : /rep
Service number : 50__00 (__ = instance of PI)
Logon procedure : Basic authentication
SSL : Inactive
user : of PI user
PW : of PI user
This will solve your problem.
I am sure it will work.

Headstart patch level vs. Repository version

What is the highest version(patch level) of Headstart that we can go to without changing our Repository version? We are currently at Repository version 4.0.12.80.6.

Hi Randy,
No not really, but as patch level 20 is the highest on sapgui 6.40, i would guess that it is a 6.20 gui...
On the other hand highest patchlevel on 6.20 gui is 64, so it is a really old installation....
You should ask them to click on the icon in the upper left corner of the saplogon / saplgpad screen and then select "About SAP Logon", a window will tell the sapgui version and patchlevel...
Regards
Rolf

Designer 9i vs 10g & repository versions

Description:
- our developers currently are using 9.2.0.7 against a repository built using the 9.2.0.7 client install.
- they need to be able to create export sets to send to a third-party company that is using 9.2.0.6
- we are rolling out forms/reports/discoverer 10g (9.0.4.0.1) and I would prefer to only have one iDS footprint for all developers
questions:
1. can we use the 9.0.4.x Designer (10g) against the existing repository that was created using 9.2.0.7?
2. if so, can we transmit (successfully) designer object data (via the built-in export functionality in the object navigator) to this client site that uses 9.2.0.6?

Hi Bob,
I'm assuming you mean version 9.0.2.7 (not 9.2.0.7) of Designer.
Q1.
You probably can't use 9.0.4 clients against 9.0.2.7 - but I've not tried it. It's usually the case that when you upgrade the repository you also have to upgrade all the clients as well. Having said that, there have been cases when the repository hasn't changed and the clients could be mixed.
Q2.
As far as exporting from 9.0.2.7 and importing into 9.0.2.6 is concerned I can't be sure (I don't have easy access to both versions). I can say that, in general, repository exports are designed to be forward compatible - that is, it should be possible to import an export done on an older version (within reason). The converse is not necessarily true, however, so you may fail to import an export done on a newer version.
However, this all depends on whether there have been changes in the underlying repository - if not, then in all probability, it could work. I suggest you give it a try and see what happens - but don't rely on this in future releases, for the reasons given above.
There may also be issues with the underlying server versions since SCM uses the server's exp and imp utilities.
I hope this helps a bit.
Keith Bremer (Oracle SCM Curriculum).

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.

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.

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.

Issues in exporting/importing repository fromInformatica version 8.6 to 9.1

Hi There,
I completed Informatica 9.1 hotfix2 server and client installation successfully in a seperate computer(system).
Also configured repository and integration services in version 9.1.
Now I need to export Informatica 8.6 repository and import into Informatica 9.1.
Are there any steps which I need to follow to complete this process?
Can someone pls help me with these steps.
Thanks in advance,
Rag

Thanks Srini.
I tried to restore version 8.6 repository into version 9.1 repository.
I got the below error log.
Is it not possible to restore 8.6 repository into 9.1? Any ideas pls....
My email and cell numbers are: [email protected], 9652227856
-------------------Log-------------------------------------------------------------------------------------------------------------------
Rep_57106 repository operation error.
Restore Contents operation on repository [REP_TEST91] started at 01/07/2013 11:08:25.
Restoring repository contents from file [C:\Informatica\9.1.0\server\infa_shared\Backup\DEV_INFA_REP_03JAN2013.rep].
domain name: DNE_INFA_TEST
Backup file repository version : 179     Current repository version : 181
File backup version : 10     Current backup version : 10
Backup file is valid : Yes
Backup file code page id : 106     Current code page id : 106
This backup file is from a different version of the Informatica Repository.
Unable to restore Repository.
Restore Contents operation on repository [REP_TEST91] ended at 01/07/2013 11:08:25. Elapsed time is 0:00:00.
Thanks,
Raghu

I am trying to start DAC 11g server in AIX but getting erorr (MESSAGE:::Schema version is missing or old).

OS detected: AIX
Jan 14, 2014 4:33:52 PM com.siebel.etl.etlmanager.DerivedConstants getDacDomainHome
INFO: The DAC_DOMAIN_HOME set to /apps/DAC11g/dac
Jan 14, 2014 4:33:52 PM com.siebel.etl.etlmanager.DerivedConstants getDacConfigLocation
INFO: The DAC_CONFIG_LOCATION value hasn't been found, the USERDIR value was used instead
Jan 14, 2014 4:33:52 PM com.siebel.etl.etlmanager.DerivedConstants getDacConfigLocation
INFO: The DAC_CONFIG_LOCATION set to /apps/DAC11g/dac
Jan 14, 2014 4:33:52 PM com.siebel.etl.etlmanager.DerivedConstants getOracleDacHome
INFO: The BI_ORACLE_HOME value hasn't been found, the USERDIR value was used instead
Jan 14, 2014 4:33:52 PM com.siebel.etl.etlmanager.DerivedConstants getOracleDacHome
INFO: The ORACLEDIR set to /apps/DAC11g/dac
Jan 14, 2014 4:33:53 PM com.siebel.etl.bootup.ApplicationManager <init>
INFO: Application booting up...
Jan 14, 2014 4:33:54 PM oracle.security.jps.internal.common.util.XmlSchemaValidationUtil$StrictErrorHandler warning
WARNING: Failed to validate the xml content. SchemaLocation: schemaLocation value = 'http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd' must have even number of URI's. Location: line 2 column 272.
Jan 14, 2014 4:33:56 PM com.siebel.etl.database.ConnectionManager init
INFO: Creating repository pool
Jan 14, 2014 4:34:00 PM com.siebel.etl.database.ConnectionManager init
INFO: Repository pool created
Jan 14, 2014 4:34:00 PM com.siebel.etl.net.QServer <init>
GLOBAL: DAC Version: Dac Build AN 11.1.1.6.4.20121119.2022
Jan 14, 2014 4:34:00 PM com.siebel.etl.net.QServer <init>
GLOBAL: Process name: 18940116@lfx007qpa
Jan 14, 2014 4:34:00 PM com.siebel.etl.net.QServer <init>
GLOBAL: The System properties are: java.assistive       ON
java.runtime.name       Java(TM) SE Runtime Environment
ibm.signalhandling.rs   false
sun.boot.library.path   /usr/java6_64/jre/lib/ppc64/default:/usr/java6_64/jre/lib/ppc64
java.vm.version 2.4
com.ibm.oti.configuration       scar
java.vm.vendor IBM Corporation
java.vendor.url http://www.ibm.com/
path.separator :
java.vm.name    IBM J9 VM
user.country    US
sun.java.launcher       SUN_STANDARD
user.dir        /apps/DAC11g/dac
java.vm.specification.name      Java Virtual Machine Specification
java.runtime.version    pap6460sr9fp1-20110208_03 (SR9 FP1)
java.fullversion        JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr9-20110203_74623 (JIT enabled, AOT enabled)
J9VM - 20110203_074623
JIT - r9_20101028_17488ifx3
GC   - 20101027_AA
java.awt.graphicsenv    sun.awt.X11GraphicsEnvironment
java.endorsed.dirs      /usr/java6_64/jre/lib/endorsed
os.arch ppc64
com.ibm.vm.bitmode      64
java.io.tmpdir /tmp/
line.separator
com.ibm.util.extralibs.properties
java.vm.specification.vendor    Sun Microsystems Inc.
user.variant
java.awt.fonts
os.name AIX
sun.java2d.fontpath
java.jcl.version        20110203_01
sun.jnu.encoding        ISO8859-1
java.library.path       /usr/java6_64/jre/lib/ppc64/default:/usr/java6_64/jre/lib/ppc64:/usr/java6_64/jre/lib/ppc64:/usr/java6_64/jre/lib/ppc64/default:/usr/java6_64/jre/lib/ppc64/j9vm:/usr/java6_64/jre/lib/ppc64:/usr/java6_64/jre/../lib/ppc64:/apps/oracle/oraclehomes/11.2.0/lib:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1:/apps/Informatica9/9.0.1/ODBC6.0/lib:.:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/usr/lib:/apps/Informatica9/9.0.1/server/bin:/apps/oracle/oraclehomes/11.2.0/lib:/apps/Informatica9/9.0.1:/apps/Informatica9/9.0.1/ODBC6.0/lib:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/apps/Informatica9/9.0.1/server/bin:/usr/lib
jxe.current.romimage.version    15
com.ibm.oti.vm.bootstrap.library.path   /usr/java6_64/jre/lib/ppc64/default:/usr/java6_64/jre/lib/ppc64
com.ibm.cpu.endian      big
java.specification.name Java Platform API Specification
java.class.version      50.0
ibm.system.encoding     ISO8859-1
java.util.prefs.PreferencesFactory      java.util.prefs.FileSystemPreferencesFactory
os.version      6.1
com.ibm.oti.vm.library.version 24
com.ibm.jcl.checkClassPath
user.home       /home/snlmgr
user.timezone   America/Los_Angeles
java.awt.printerjob     sun.print.PSPrinterJob
file.encoding   ISO8859-1
java.specification.version      1.6
user.name       snlmgr
java.class.path ./lib/msbase.jar:./lib/mssqlserver.jar:./lib/msutil.jar:./lib/sqljdbc.jar:./lib/ojdbc6.jar:./lib/ojdbc5.jar:./lib/ojdbc14.jar:./lib/db2java.zip:./lib/teradata.jar:./lib/terajdbc4.jar:./lib/log4j.jar:./lib/tdgssjava.jar:./lib/tdgssconfig.jar:./lib/nzjdbc.jar:./lib/bijdbc.jar:./lib/ttjdbc6.jar:./lib/orai18n.jar:./lib/timestenjmsxla.jar:./lib/jms.jar:./lib/javax.jms.jar:./DAWSystem.jar:./lib/biacm.paramproducer.jar::./lib/oracle_common/modules/oracle.pki_11.1.1/oraclepki.jar:./lib/oracle_common/webservices/wsclient_extended.jar:./lib/oracle_common/modules/oracle.jmx_11.1.1/jmxspi.jar:./lib/oracle_common/modules/oracle.odl_11.1.1/ojdl.jar:./lib/oracle_common/modules/oracle.jps_11.1.1/jps-internal.jar:./lib/oracle_common/modules/oracle.jps_11.1.1/jps-platform.jar:./lib/oracle_common/modules/oracle.jps_11.1.1/jps-se.jar:./lib/oracle_common/modules/oracle.idm_11.1.1/identitystore.jar:./lib/oracle_common/modules/oracle.jps_11.1.1/jps-az-rt.jar:./lib/oracle_common/modules/oracle.jps_11.1.1/jacc-spi.jar:./lib/oracle_common/modules/oracle.iau_11.1.1/fmw_audit.jar:./lib/oracle_common/modules/oracle.jmx_11.1.1/jmxframework.jar:./lib/oracle_common/modules/oracle.igf_11.1.1/identitydirectory.jar::./lib/oracle_common/jlib/help-share.jar:./lib/oracle_common/jlib/ohj.jar:./lib/oracle_common/jlib/jewt4.jar:./lib/oracle_common/jlib/share.jar:./lib/oracle_common/jlib/oracle_ice.jar:
com.ibm.oti.shared.enabled      false
java.vm.specification.version   1.0
sun.arch.data.model     64
sun.java.command        com.siebel.etl.net.QServer
java.home       /usr/java6_64/jre
com.ibm.oti.jcl.build   20110202_1316
user.language   en
ibm.signalhandling.sigint       true
java.specification.vendor       Sun Microsystems Inc.
os.encoding     ISO8859-1
oracle.security.jps.config      /apps/DAC11g/dac/conf/security/jps-config-jse.xml
java.vm.info    JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr9-20110203_74623 (JIT enabled, AOT enabled)
J9VM - 20110203_074623
JIT - r9_20101028_17488ifx3
GC   - 20101027_AA
java.version    1.6.0
java.ext.dirs   /usr/java6_64/jre/lib/ext
jxe.lowest.romimage.version     15
sun.boot.class.path     /usr/java6_64/jre/lib/ppc64/default/jclSC160/vm.jar:/usr/java6_64/jre/lib/annotation.jar:/usr/java6_64/jre/lib/beans.jar:/usr/java6_64/jre/lib/java.util.jar:/usr/java6_64/jre/lib/jndi.jar:/usr/java6_64/jre/lib/logging.jar:/usr/java6_64/jre/lib/security.jar:/usr/java6_64/jre/lib/sql.jar:/usr/java6_64/jre/lib/ibmorb.jar:/usr/java6_64/jre/lib/ibmorbapi.jar:/usr/java6_64/jre/lib/ibmcfw.jar:/usr/java6_64/jre/lib/rt.jar:/usr/java6_64/jre/lib/charsets.jar:/usr/java6_64/jre/lib/resources.jar:/usr/java6_64/jre/lib/ibmpkcs.jar:/usr/java6_64/jre/lib/ibmcertpathfw.jar:/usr/java6_64/jre/lib/ibmjgssfw.jar:/usr/java6_64/jre/lib/ibmjssefw.jar:/usr/java6_64/jre/lib/ibmsaslfw.jar:/usr/java6_64/jre/lib/ibmjcefw.jar:/usr/java6_64/jre/lib/ibmjgssprovider.jar:/usr/java6_64/jre/lib/ibmjsseprovider2.jar:/usr/java6_64/jre/lib/ibmcertpathprovider.jar:/usr/java6_64/jre/lib/ibmxmlcrypto.jar:/usr/java6_64/jre/lib/management-agent.jar:/usr/java6_64/jre/lib/xml.jar:/usr/java6_64/jre/lib/jlm.jar:/usr/java6_64/jre/lib/javascript.jar
java.vendor     IBM Corporation
file.separator /
java.compiler   j9jit24
sun.io.unicode.encoding UnicodeBig
ibm.signalhandling.sigchain     true
Jan 14, 2014 4:34:00 PM com.siebel.etl.engine.core.ETLUtils logException
SEVERE:
ANOMALY INFO::: QServer will stop owing to repository version mismatch: Schema version is missing or old.
Try upgrading repository.
MESSAGE:::Schema version is missing or old.
Try upgrading repository.
EXCEPTION CLASS::: com.siebel.etl.upgrade1.VersionMismatchException
com.siebel.etl.upgrade1.UpgradeUtils.isRepositoryValid(UpgradeUtils.java:96)
com.siebel.etl.net.QServer.versionIntegrityCheck(QServer.java:461)
com.siebel.etl.net.QServer.<init>(QServer.java:132)
com.siebel.etl.net.QServer.main(QServer.java:499)

(1) Download the Windows Installer CleanUp utility installer file (msicuu2.exe) from the following Major Geeks page (use one of the links under the "DOWNLOAD LOCATIONS" thingy on the Major Geeks page):
http://majorgeeks.com/download.php?det=4459
(2) Doubleclick the msicuu2.exe file and follow the prompts to install the Windows Installer CleanUp utility. (If you're on a Windows Vista or Windows 7 system and you get a Code 800A0046 error message when doubleclicking the msicuu2.exe file, try instead right-clicking on the msicuu2.exe file and selecting "Run as administrator".)
(3) In your Start menu click All Programs and then click Windows Install Clean Up. The Windows Installer CleanUp utility window appears, listing software that is currently installed on your computer.
(4) In the list of programs that appears in CleanUp, select any iTunes entries and click "Remove", as per the following screenshot:
(5) Quit out of CleanUp, restart the PC and try another iTunes install. Does it go through properly this time?

Repository version 10.1.2.0.2 s/b 10.1.2.3.0

Similar Messages

Maybe you are looking for