Incorrect DB schema version

When I try to start the BPEL PM Server, it stalls just after initializing the Oracle Application Server Containers for J2EE 10g (10.1.2.0.0). Higher up in the command window is the following error message:
Incorrect DB schema version.
The database schema version 2.0.2 from the database does not match the version 2.0.3 expected by the server.
The database schema currently in place has probably been configured for a previous release; please re-install the database schema and try to start the server again.
I am using a 10g Release 2 EE database, not Oracle Lite. Is 10g Release 2 incompatible with the 10.1.2 BPEL PM Server? Is there another reason for this error message?
Thanks.
Chris

Hi,
run the following commands as orabpel user and restart the bpel server.
update version_server set guid='2.0.3';
commit;
Thanks,
Narasimha

Similar Messages

ORABPEL - 03003 Incorrect db schema version

Hi,
Os: windows 2000
I had installed OraBPELServer (version 10.1.2.0.0) in the location D:\OraBPELPM which is runing on the oc4j.it was running perfectly with out any startup exception. Then i installed new OracleBPELPM which use JBoss at c:\OraBPEL_Jboss.The new one also runs correctly.
The problem is when start my old Oc4jOracleBPEL it is not starting it's giving the following exception .
Detected data source 'olite'
06/08/03 08:25:49 ORABPEL-03003
Incorrect db schema version.
The database schema version "2.0.3" from the database does not match the version "2.0.2" expected by the server.
The database schema currently in place has probably been configured for a previo
us release; please re-install the database schema and try to start the server again.
06/08/03 08:25:49 at om.collaxa.cube.engine.adaptors.util.BaseSchemaManag
er.getSchemaVersion(BaseSchemaManager.java:90)
06/08/03 08:25:49 at com.collaxa.cube.engine.adaptors.util.DataSourceSchem
aUtils$1.validateCompatibility(DataSourceSchemaUtils.java:72)
Can any one please tell me how to re-install the database schema in (Oralite).
Thanks
Bogi

the script to re-install the olite object can be found at:
ORACLE_HOME\integration\orabpel\system\database\scripts
and look for the olite scripts. Install the script with msql.

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?

Fatal Error: The schema version of the database is from a newer version of WSUS

Hello,
CM2012 R2 RTM on Server2012 R2 RTM with SQL2012 SP1
installed SQL, WSUS and then CM.
When finished adding WSUS, there was a post installation message but I skipped it and continued to CM installation, as suggested on some blogs. WSUS in CM seems to be a real mystery... and there are multiple workarounds and suggestions.
Now my CM is ready to GO. Configured discovery, boundaries. All components appear green OK. My hand shaked when I click on post Deployment message related to WSUS in server manager. So I clicked it. And received: Post Deployment Failed. There is
a path to log file. The error:
Fatal Error: The schema version of the database is from a newer version of WSUS
than currently installed. You must either patch your WSUS server to at least
that version or drop the database. WSUS was installed with SQL DB.
What do you suggest?
Thanks.
Please see full log:
2013-12-01 06:58:24 Postinstall started
2013-12-01 06:58:24 Detected role services: Api, Database, UI, Services
2013-12-01 06:58:24 Start: LoadSettingsFromXml
2013-12-01 06:58:24 Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentLocal
2013-12-01 06:58:24 Value is true
2013-12-01 06:58:24 End: GetConfigValue
2013-12-01 06:58:24 Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentDirectory
2013-12-01 06:58:24 Value is D:\sources\wsus
2013-12-01 06:58:24 End: GetConfigValue
2013-12-01 06:58:24 Content directory is D:\sources\wsus
2013-12-01 06:58:24 Start: GetConfigValue with filename=UpdateServices-DB.xml item=InstanceName
2013-12-01 06:58:24 Value is confman
2013-12-01 06:58:24 End: GetConfigValue
2013-12-01 06:58:24 SQL instance name is confman
2013-12-01 06:58:24 End: LoadSettingsFromXml
Post install is starting
2013-12-01 06:58:24 Start: Run
2013-12-01 06:58:24 Fetching WsusAdministratorsSid from registry store
2013-12-01 06:58:24 Value is S-1-5-21-1033354796-2088831985-1429053453-1003
2013-12-01 06:58:24 Fetching WsusReportersSid from registry store
2013-12-01 06:58:24 Value is S-1-5-21-1033354796-2088831985-1429053453-1004
2013-12-01 06:58:25 Configuring content directory...
2013-12-01 06:58:25 Configuring groups...
2013-12-01 06:58:26 Starting group configuration for WSUS Administrators...
2013-12-01 06:58:26 Found group in regsitry, attempting to use it...
2013-12-01 06:58:28 Writing group to registry...
2013-12-01 06:58:28 Finished group creation
2013-12-01 06:58:28 Starting group configuration for WSUS Reporters...
2013-12-01 06:58:28 Found group in regsitry, attempting to use it...
2013-12-01 06:58:28 Writing group to registry...
2013-12-01 06:58:28 Finished group creation
2013-12-01 06:58:28 Configuring permissions...
2013-12-01 06:58:28 Fetching content directory...
2013-12-01 06:58:28 Fetching ContentDir from registry store
2013-12-01 06:58:28 Value is D:\sources\wsus
2013-12-01 06:58:28 Fetching group SIDs...
2013-12-01 06:58:28 Fetching WsusAdministratorsSid from registry store
2013-12-01 06:58:28 Value is S-1-5-21-1033354796-2088831985-1429053453-1003
2013-12-01 06:58:28 Fetching WsusReportersSid from registry store
2013-12-01 06:58:28 Value is S-1-5-21-1033354796-2088831985-1429053453-1004
2013-12-01 06:58:28 Creating group principals...
2013-12-01 06:58:28 Granting directory permissions...
2013-12-01 06:58:28 Granting permissions on content directory...
2013-12-01 06:58:29 Granting registry permissions...
2013-12-01 06:58:29 Granting registry permissions...
2013-12-01 06:58:29 Granting registry permissions...
2013-12-01 06:58:29 Configuring shares...
2013-12-01 06:58:29 Configuring network shares...
2013-12-01 06:58:29 Fetching content directory...
2013-12-01 06:58:29 Fetching ContentDir from registry store
2013-12-01 06:58:29 Value is D:\sources\wsus
2013-12-01 06:58:29 Fetching WSUS admin SID...
2013-12-01 06:58:29 Fetching WsusAdministratorsSid from registry store
2013-12-01 06:58:29 Value is S-1-5-21-1033354796-2088831985-1429053453-1003
2013-12-01 06:58:29 Content directory is local, creating content shares...
2013-12-01 06:58:29 Creating share "UpdateServicesPackages" with path "D:\sources\wsus\UpdateServicesPackages" and description "A network share to be used by client systems for collecting all software packages (usually applications)
published on this WSUS system."
2013-12-01 06:58:29 Deleting existing share...
2013-12-01 06:58:29 Creating share...
2013-12-01 06:58:29 Share successfully created
2013-12-01 06:58:29 Creating share "WsusContent" with path "D:\sources\wsus\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
2013-12-01 06:58:29 Deleting existing share...
2013-12-01 06:58:29 Creating share...
2013-12-01 06:58:29 Share successfully created
2013-12-01 06:58:29 Creating share "WSUSTemp" with path "C:\Program Files\Update Services\LogFiles\WSUSTemp" and description "A network share used by Local Publishing from a Remote WSUS Console Instance."
2013-12-01 06:58:29 Deleting existing share...
2013-12-01 06:58:29 Creating share...
2013-12-01 06:58:29 Share successfully created
2013-12-01 06:58:29 Finished creating content shares
2013-12-01 06:58:29 Stopping service WSUSService
2013-12-01 06:58:29 Stopping service W3SVC
2013-12-01 06:58:32 Configuring database...
2013-12-01 06:58:32 Configuring the database...
2013-12-01 06:58:32 Establishing DB connection...
2013-12-01 06:58:32 Checking to see if database exists...
2013-12-01 06:58:32 Database exists
2013-12-01 06:58:32 Switching database to single user mode...
2013-12-01 06:58:32 Loading install type query...
2013-12-01 06:58:32 DECLARE @currentDBVersion       int
DECLARE @scriptMajorVersion     int = (9600)
DECLARE @scriptMinorVersion     int = (16384)
DECLARE @databaseMajorVersion   int
DECLARE @databaseMinorVersion   int
DECLARE @databaseBuildNumber    nvarchar(10)
IF NOT EXISTS(SELECT * FROM sys.databases WHERE name='SUSDB')
BEGIN
    SELECT 1
END
ELSE
BEGIN
    SET @currentDBVersion = (SELECT SchemaVersion FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
    SET @databaseBuildNumber = (SELECT BuildNumber FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
    DECLARE @delimiterPosition INT = CHARINDEX('.', @databaseBuildNumber)
    IF (@delimiterPosition = 0)
    BEGIN
        RAISERROR('Invalid schema version number', 16, 1) with nowait
        return
    END
    SET @databaseMajorVersion = SUBSTRING(@databaseBuildNumber, 1, @delimiterPosition - 1)
    SET @databaseMinorVersion = SUBSTRING(@databaseBuildNumber, (@delimiterPosition + 1), (10 - @delimiterPosition))
    IF @currentDBVersion < 926
    BEGIN
        SELECT 3
    END
    ELSE
    BEGIN
        IF (@scriptMajorVersion > @databaseMajorVersion OR
           (@scriptMajorVersion = @databaseMajorVersion AND @scriptMinorVersion > @databaseMinorVersion))
        BEGIN
            SELECT 2
        END
        ELSE IF (@scriptMajorVersion = @databaseMajorVersion AND
                 @scriptMinorVersion = @databaseMinorVersion)
        BEGIN
            SELECT 0
        END
        ELSE
        BEGIN
            SELECT 4
        END
    END
END
2013-12-01 06:58:33 Install type is: UnsupportedFuture
2013-12-01 06:58:33 DB is a higher version than the config scripts
2013-12-01 06:58:33 Swtching DB to multi-user mode......
2013-12-01 06:58:33 Finished setting multi-user mode
2013-12-01 06:58:33 Microsoft.UpdateServices.Administration.CommandException: The schema version of the database is from a newer version of WSUS
than currently installed. You must either patch your WSUS server to at least
that version or drop the database.
   at Microsoft.UpdateServices.Administration.ConfigureDB.CheckForUnsupportedVersion(DBInstallType installType, Boolean dbExists)
   at Microsoft.UpdateServices.Administration.ConfigureDB.ConnectToDB()
   at Microsoft.UpdateServices.Administration.ConfigureDB.Configure()
   at Microsoft.UpdateServices.Administration.PostInstall.Run()
   at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
Fatal Error: The schema version of the database is from a newer version of WSUS
than currently installed. You must either patch your WSUS server to at least
that version or drop the database.
"When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

Gerry,
1. I uninstalled WSUS, removed DB, restarted. And reinstall WSUS again. This time MS Management Console of WSUS could not be started. I did it after WSUS was added following your blog pix.
I checked c:\program files\update services, there were couple of missing directories by comparison what was in case when I installed WSUS after SQL but before CM: Tools, Shema, and another A.. something. I saw this issue on NOOB. And people copied these
directories from previous installation.
How we can explain this behavior on RTM version?
Then I uninstalled it again. And give another try... Here I found another interesting thing. Please compare your slide number 5 from your link and attached one. You can see that on Add Roles and Features Wizard page are missing items. Some
of them were found in next screen of my installation (I am using RTM server) but one API and Power shell cmdlets were not listed on final screen before start install. May be those are note important...
I reinstall again... and the MS Management Console fails again. Exactly the same thing that I saw during 2 weeks of trying to make works. Don't see what I can screw up here.
What about missing directories after reinstalling WSUS. Is that normal? And in IIS there is no WSUS.
I don't see here any difficult thing, just simple wizard... But it not works. Second CM server.
What I do wrong here to create a failure of MMC. There is any blog with examples of RTM Server 2012 and CM RTM. All stuff is 2012. So kind of guesses and no precise thing to do...
Sorry for my cry :). The only solution is to call MS and pay $250 for SUCH a trivial thing that not works.
Any help? Please see pics. Can you confirm that you have the same or more directories in Update Services
Thanks.
API and Power Shell Cmdlets feature missed if compare with yours slides.
"When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

Schema version is lower than expected value

While configuring the database at Step 3 of 9, it threw me an exception: INST-6177 OIM Schema version is lower than expected value.
Create OIM 11g schema using repository creation utility and proceed with configuration.
Now, Please help me...

For the exception, the trace says that:
[2011-05-19T14:29:10.511+01:00] [as] [NOTIFICATION] [] [oracle.as.install.engine.modules.validation.oracle.as.install.engine.modules.validation.handler.oimQueriesHandler.checkForUpgrade] [tid: 11] [ecid: 0000J08SN_J6UOYFLrvH8A1DpHfc000002,0] [[
[OIM_CONFIG_INTERVIEW] MDS Schema Version is correct
[2011-05-19T14:29:10.527+01:00] [as] [NOTIFICATION] [] [oracle.as.install.engine.modules.validation.oracle.as.install.engine.modules.validation.handler.oimQueriesHandler.checkForUpgrade] [tid: 11] [ecid: 0000J08SN_J6UOYFLrvH8A1DpHfc000002,0] Exiting method executeHandler
[2011-05-19T14:29:10.527+01:00] [as] [NOTIFICATION] [] [oracle.as.install.engine.modules.validation.oracle.as.install.engine.modules.validation.handler.oimQueriesHandler.checkForUpgrade] [tid: 11] [ecid: 0000J08SN_J6UOYFLrvH8A1DpHfc000002,0] [[
[OIM_CONFIG_INTERVIEW] Database is not encryped. This is not an upgrade flow.
[2011-05-19T14:29:10.527+01:00] [as] [NOTIFICATION] [] [oracle.as.install.engine.modules.validation.oracle.as.install.engine.modules.validation.handler.oimQueriesHandler.checkForUpgrade] [tid: 11] [ecid: 0000J08SN_J6UOYFLrvH8A1DpHfc000002,0] Could not fetch the schema version from the database
[2011-05-19T14:29:10.527+01:00] [as] [NOTIFICATION] [] [oracle.as.install.engine.modules.validation.oracle.as.install.engine.modules.validation.handler.oimQueriesHandler.checkForUpgrade] [tid: 11] [ecid: 0000J08SN_J6UOYFLrvH8A1DpHfc000002,0] [[
ERROR ====>>>>:INST-6177
[2011-05-19T14:29:10.527+01:00] [as] [NOTIFICATION] [] [oracle.as.install.engine.modules.validation.oracle.as.install.engine.modules.validation.handler.oimQueriesHandler.checkForUpgrade] [tid: 11] [ecid: 0000J08SN_J6UOYFLrvH8A1DpHfc000002,0] [[
Cause:OIM Schema version is lower than the expected value
[2011-05-19T14:29:10.527+01:00] [as] [NOTIFICATION] [] [oracle.as.install.engine.modules.validation.oracle.as.install.engine.modules.validation.handler.oimQueriesHandler.checkForUpgrade] [tid: 11] [ecid: 0000J08SN_J6UOYFLrvH8A1DpHfc000002,0] [[
Action:Create OIM 11g schema using Repository Creation Utility and proceed with configuration.
[2011-05-19T14:29:10.527+01:00] [as] [NOTIFICATION] [] [oracle.as.install.engine.modules.validation.oracle.as.install.engine.modules.validation.handler.oimQueriesHandler.checkForUpgrade] [tid: 11] [ecid: 0000J08SN_J6UOYFLrvH8A1DpHfc000002,0] [[
[OIM_CONFIG_INTERVIEW] Retrieving default locale set in the machine.
[2011-05-19T14:29:10.527+01:00] [as] [NOTIFICATION] [] [oracle.as.install.engine.modules.validation.oracle.as.install.engine.modules.validation.handler.oimQueriesHandler.checkForUpgrade] [tid: 11] [ecid: 0000J08SN_J6UOYFLrvH8A1DpHfc000002,0] Exiting method executeHandler
[2011-05-19T14:29:10.527+01:00] [as] [NOTIFICATION] [] [oracle.as.install.engine.modules.validation] [tid: 11] [ecid: 0000J08SN_J6UOYFLrvH8A1DpHfc000002,0] Handler launch end: oimQueriesHandler.checkForUpgrade
[2011-05-19T14:29:10.527+01:00] [as] [NOTIFICATION] [] [oracle.as.install.engine.modules.validation] [tid: 11] [ecid: 0000J08SN_J6UOYFLrvH8A1DpHfc000002,0] Handler returned status: FAILED
[2011-05-19T14:29:10.527+01:00] [as] [NOTIFICATION] [] [oracle.as.install.engine.modules.validation] [tid: 11] [ecid: 0000J08SN_J6UOYFLrvH8A1DpHfc000002,0] Error in validating schema details

Report Server Web Site isn't Working (Incorrect security descriptor version)

Hello,
we have microsoft sql 2012 sp1 on windows server 2012 64 bit.
and we have scom 2012 sp1
we had use the reporting sevices succesfully. somehow it gave an error that "An internal error occurred on the report server. See the error log for more details. (rsInternalError)"
when i m looking the logs, i saw the error about that : Incorrect security descriptor version
have can i fix this ?
library!ReportServer_0-3!d58!06/02/2014-09:28:37:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: Incorrect security descriptor version, Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details.;
note:i already re-install the reporting services.

This could be several things;
1. If there is a pending Windows Update you might need to restart to install the updates. In any case, a restart could help
2. Try to use ResetSRS Tool -
http://technet.microsoft.com/en-us/library/bb309637.aspx (SCOM 2007, but still applicable for SCOM 2012)
3. Check that the Reporting Service is running
www.coretech.dk - blog.coretech.dk
there isnt any updates that stay pending on the server.
and yes reporting service is running. but when i try to run resetsrs i have got the error message.

JPS-00080: Credential store schema version 12.1.2.0.0 is less than the latest schema version 12.1.3.0.0, upgrade the Credential store schema to latest version.

JPS-00080: Credential store schema version 12.1.2.0.0 is less than the latest schema version 12.1.3.0.0, upgrade the Credential store schema to latest version.
Hi All,
When trying to extend my domain, it fails with above error.
any suggestions on fix?
is this related to Fusion Infrastructure ADF RCU utility?
thanks

Hi JCGO,
The Schema installed on your DB is 12.1.2.0.0 but the Domain Extension requires 12.1.3.0.0.
One solution is to run the 12.1.3.0.0 RCU, drop the existing schema on your DB, followed by installation 12.1.3.0.0 schema on the DB, so that the Domain extension gets the 12.1.3.0.0 schema
One more solution is to open the template on which you are extending the domain. The templates are present in ${MW_HOME}/oracle_common/common/templates/wls , explore to the required configuration inside yourtemplate.jar and comment out the Credential store schema version pre-requisite. This is not a good approach, but still it'll be a good workaround since 12.1.2.0.0 and 12.1.3.0.0 schema wont have much difference.
Thanks,
Shiva Shankar B N

Which schema version is in use

How can I tell whether a Directory Server is using schema version 1 or 2?

Schema 1 versus Schema 2 is really an application usage question. However, there are a few quick things to look at.
If you are using any of the iPlanet/SunOne Messaging Server 5.x versions, your directory probably has Schema 1 data.
If you have a suffix of 'o=internet', it's probably Schema 1.
If you are using any of the JES versions of Messaging Server or Access Manager, you are probably using Schema 2.
If you have only one suffix, and in that suffix there is a 'ou=services' branch, then it's likely Schema 2.
If you've never installed Messaging server or Access Manager, then you aren't using either Schema 1 or Schema 2.

Hello, I have a license to acrobat standar, but acrobat standar is not available only acrobat pro and my license code is incorrect for this version

Hello somebody can help me.
Hello, I have a license to acrobat standar, but acrobat standar is not available only acrobat pro and my license code is incorrect for this version.

Downloadable installation files available:
Suites and Programs: CC 2014 | CC | CS6 | CS5.5 | CS5 | CS4, CS4 Web Standard | CS3
Acrobat: XI, X | 9,8 | 9 standard
Premiere Elements: 13 | 12 | 11, 10 | 9, 8, 7 win | 8 mac | 7 mac
Photoshop Elements: 13 |12 | 11, 10 | 9,8,7 win | 8 mac | 7 mac
Lightroom: 5.7.1| 5 | 4 | 3
Captivate: 8 | 7 | 6 | 5.5, 5 | 1
Contribute: CS5 | CS4, CS3 | 3,2
FrameMaker: 12, 11, 10, 9, 8, 7.2
Download and installation help for Adobe links
Download and installation help for Prodesigntools links are listed on most linked pages. They are critical; especially steps 1, 2 and 3. If you click a link that does not have those steps listed, open a second window using the Lightroom 3 link to see those 'Important Instructions'.

ODM and ODM schema versions are incompatible please use ODM api version ver

Hi,
I am with a problem, I am with the version of Oracle 10g 10.1.0.3 EE in Linux As 3 and I am not getting to rotate Oracle it Dates Mining, when I am going login in the program him of the the following mistake,
ODM and ODM schema versions are incompatible please use ODM api version version 10.1.0.3
excuses for bad English!
tks,
Welvis Douglas
Msn : [email protected]

Hi,
When using Data Miner, the api that it uses to connect to the ODM database option must have the same version number as the db itself.
See the following page:
http://www.oracle.com/technology/products/bi/odm/odminer.html
And scroll down to the section on the 10.1.X apis:
"Data Miner requires that the version of odmapi.jar in the Data Miner lib directory be the same as the version of odmapi.jar installed with ODM. The version of odmapi.jar shipped with Data Miner is 10.1.0.2. Here are the additional patch versions of odmapi.jar for download:"
There are links there to get the .jar files required for the version you are using (10.1.0.3).
Thanks, Mark.

Followed instruction, but still API vs schema version incompatibility

Hello,
I have a DB patched to 10.1.0.4, use ODMiner 10.1.0.2, and have copied the 10.1.0.4 odmapi.jar into the jdev/lib/ext directory of JDeveloper. However, when trying to connect the JDeveloper DM4J extension to the ODM demo user schema, it still gives me the error: 'ODM API and ODM schema versions are incompatible. Please use ODM API version 10.1.0.4.0'.
ODM, the DB and JDev definitely use the same odmapi.jar file version. Moreover, I tried it with JDev 9.0.5.1 as well as the latest 10g version. Nothing works. Now I ran out of ideas how to debug that problem. Has someone of you an idea what the problem could be and how to solve it? By the way everything runs on WinXP.
Thanks in advance for any advice.
Best regards Holger

Hi Dr. Holger,
Sorry about the confusion.
The ODM 10.1.0.2 Code Generator JDeveloper Extension was not published to OTN as it should have been.
I have just made the request to have this done, but it may take a couple of weeks.
In the meantime you can workaround this problem by replacing the ODM 10.1.0.1 odminer.jar with the one from Data Miner 10.1.0.2 as well as replacing the odmapi.jar with the ODM 10.1.0.4 odmapi.jar.
You can get all of the above from the following otn link:
http://www.oracle.com/technology/products/bi/odm/odminer.html
Thanks, Mark

Categorization schema version

Hi All,
I am trying to create a draft version for Categorization schema from active version, active version has subject codes assigned at last level, while creating a draft version these subject codes are not copied to draft version. Please suggest.
Regards,
S Reddy

dear friend,
1. select the 'Active' version and hit New
2. edit your new cat. schema ; goto General Data and set Valid-From Date and Valid-From Time, also set Status 'Released'
3. 'Save' your new schema
await for that date/time (you've just set as Valid-From), log in to WebUI and check it out
good luck!

Extracting latest schema version from view tables

Hi
We have a shell script, which runs sql against the oracle designer tables to extract table, column info. This used to run fina against our pre 6i designer version.
eg
select rtrim(lower(t.name))
     from ci_table_definitions t,ci_application_systems a
     where a.latest_version_flag = 'Y'
     and a.name = 'KERNEL_MASTER'
     and t.application_system_owned_by = a.id
     order by t.name asc;
we have upgraded to Designer 6i now and this has resulted in our script not working. The above sql complains about the fields latest_version_flag and application_system_owned_by not existing, which they don't.
Does anyone know what fields we can used to acheive the same result on the designer 6i setup?
Basically we are trying to extract the table definitions for the latest version of a schema ( we called 'KERNEL_MASTER')
Any ideas?

Here's a copy of old Oracle Support note:190516.1 to give you some idea where to start:
Differences in the Repository API between Designer 6.0 and Designer 6i
1) Tables SDD_ELEMENTS and SDD_STRUCTURE_ELEMENTS
In Designer 6.0, all repository elements were hold in 2 main tables called
SDD_ELEMENTS and SDD_STRUCTURE_ELEMENTS. Those tables don't exist anymore.
Any API script that references those tables will fail with the following error:
ORA-00942: table or view does not exist
To avoid this error, replace the reference to SDD_ELEMENTS or
SDD_STRUCTURE_ELEMENTS by the corresponding API view CI_... (as it was
recommended in previous releases of Designer).
2) new Columns IRID and IVID
In Designer 6.0, the elements were uniquely identified by the column ID.
In Designer 6i the column IRID (Internal Repository IDentifier) identifies the
object tree. Every element version has the same IRID, but it has a different
version label and a different version identifier, called the IVID (Internal
Version IDentifier). An IVID is unique over all versions of all elements.
To avoid select statements returning different rows for different versions of
the same object, you should define the Context Workarea before executing
a statement (See next point).
3) Context workarea
The result of a select from a CI_... views may include the same object several
times, because the repository includes several versions of the object.
To avoid this, you should specify the context workarea.
A workarea is a specific view on the repository which contains at most one
version of each element. In other words, a workarea is version resolved.
You can specify the context workarea by using the following PL/SQL call:
jr_context.set_workarea('<workarea_name>');
Once done, you will work within the context of this workarea only.
4) Column APPLICATION_SYSTEM_OWNED_BY
In Designer 6.0, all CI_... views for Primary Access Elements (PACs) included a
column APPLICATION_SYSTEM_OWNED_BY for the reference of the application system
owning the element. This column doesn't exist in Designer 6i anymore.
Any API script that includes this column will fail with the following error:
ORA-00904: invalid column name
With Oracle Repository, the reference to the application of an element can only
be found through the table SDD_FOLDER_MEMBERS. The column MEMBER_OBJECT refers
to the IRID of the element, and the column FOLDER_REFERENCE refers to the IRID
of the folder or application system containing the element:
CI_..............SDD_FOLDER_MEMBERS........CI_APPLICATION_SYSTEMS
....................FOLDER_REFERENCE >--------- IRID
IRID ---------------<MEMBER_OBJECT
Suppose for example the following SQL that worked fine in Designer 6.0:
select ent.name
from ci_entities ent
, ci_application_systems app
where app.name = '&App_Name'
and ent.application_system_owned_by = app.id;
This Select should be re-written like the following to run on Designer 6i:
select ent.name
from ci_entities ent
, sdd_folder_members mem -- the application system reference goes through sdd_folder_members
, ci_application_systems app
where mem.member_object = ent.irid
and mem.folder_reference = app.irid
and app.name = '&App_Name';
Note: this query only returns rows if the user who is executing it has been
granted SELECT privilege on application '&App_Name'

Incorrectly Declaring Schemas as Invalid???

I am having some problems with the document validation of DBXML. I have a few schemas that I wrote using XMLSpy 2004 (I know it's a little old). They validate through XMLSpy. I also validated them against the W3C validator and they all passed. However, when I try and run a document that references them through DBXML, I get the following error:
Error: XML Indexer: Parse error in document at line, 1, char 536. Parser message: Complex type 'RecordType' violates the Unique Particle Attribution rule in its components 'bytes' and '##other', errcode = INDEXER_PARSER_ERROR
The complexType 'RecordType' is defined below:
     <xs:complexType name="RecordType">
          <xs:sequence minOccurs="1" maxOccurs="1">
               <xs:element ref="ad:adminData"/>
               <xs:choice>
                    <xs:element name="bytes" type="xs:base64Binary"/>
                    <xs:any namespace="##other" minOccurs="0" maxOccurs="1" processContents="skip"/>
               </xs:choice>
          </xs:sequence>
     </xs:complexType>
If I remove one of the lines from the <xs:choice> element (bytes, or any) it works just fine.
Thanks in advance,
Brian J. Clark

After doing a lot of experimentation, I don't think the problem is on my end. I think DBXML (meaning Xerces-C) has a problem with <xs:any> elements. I have created a very basic xsd file and a very basic xml file that contain nothing but a root element with one child. They validate against XMLSpy just fine.
Schema:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="info:rfa/rfaRegistry/xmlSchemas/iwsaDeposit" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ad="info:rfa/rfaRegistry/xmlSchemas/adminData" xmlns:col="info:rfa/rfaRegistry/xmlSchemas/collection" xmlns:dc="info:fra/fraRegistry/xmlSchemas/dcInfo" xmlns="info:rfa/rfaRegistry/xmlSchemas/iwsaDeposit">
     <xs:annotation>
          <xs:appinfo>
               <dc:title>RFA Item-Level Deposit Record</dc:title>
               <dc:creator>Jeffrey A. Young</dc:creator>
               <dc:date>2006-08-31</dc:date>
          </xs:appinfo>
     </xs:annotation>
     <xs:element name="data" type="dataType" />
     <xs:complexType name="dataType">
          <xs:sequence>
               <xs:any processContents="strict"/>
          </xs:sequence>
     </xs:complexType>
</xs:schema>
XML File:
<?xml version="1.0" encoding="UTF-8"?>
<da:data xmlns:da="info:rfa/rfaRegistry/xmlSchemas/iwsaDeposit"
xmlns:ad="info:rfa/rfaRegistry/xmlSchemas/adminData"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="info:rfa/rfaRegistry/xmlSchemas/iwsaDeposit
D:/Data/eclipse/workspace/GDFRPrototype/xml/xsd/iwsaDeposit-2.xsd
info:rfa/rfaRegistry/xmlSchemas/adminData
D:/Data/eclipse/workspace/GDFRPrototype/xml/xsd/adminData.xsd">
     <info>Stuff</info>
</da:data>
I get the following error from DBXML:
com.sleepycat.dbxml.XmlException: Error: XML Indexer: Parse error in document at line, 1, char 458. Parser message: Unknown element 'info', errcode = INDEXER_PARSER_ERROR

Incorrect link to version of PS in Prefs of LR4

I have a Windows 7 Pro 64-bit OS
I have Photoshop 12.1 [extended version]; Photoshop 13 Beta; Lightroom 4
I originally had Photoshop 12 [standard version] when I loaded Lightroom 3 and Lightroom 4. When LR 4 beta was upgraded to the current version, I uninstalled LR3 and Photoshop 12.0 as I had the extended version of PS and it was [and is] working correctly. However, here is where the problem exists with LR4. It points to the standard version of PS 12 in Edit|Preferences|External Editing. I do not know how to point the software to the current version of PS or even the Beta version of PS 13.
If you look at the top, it states that it is looking for Photoshop CS5 instead of Photoshop CS5.1 so the option is grayed out on any image opened in LR4.
How do I change this pointer to the correct location?

Sorry but that did NOT correct the problem. I have even rebooted following installation but it still shows the original folder.

Incorrect DB schema version

Similar Messages

Maybe you are looking for