OWB Paris: Recommend version of the Database

Hello everybody.
I would like to know which version of the database is recomended to be used with OWB Paris. We want to use the module of this tool that allows to audit the data quality and we don't know if it's necessary to install an specific version of the database (10gR2) or it can be used with 9i.
Thanks in advance

What versions of Oracle database can I use with OWB 10gR2 Beta 3?
- Oracle Database 10gR2
- Oracle Database 10gR1 with 10.1.0.4 patchset applied.
- Oracle9i Database (9.2). Note that some OWB features are only supported on Oracle Database 10g, as detailed in the Release Notes. Oracle Database 10gR1 is strongly recommended for OWB Paris Beta.
Bye
Detlef

Similar Messages

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

What are the version of the database?

Hi Guru's
What are the versions of the database which is comes with e-business suit?
11.5.10.2 9.2.0.6
11.5.10
11.5.9
11.5.8
Please give me the reply
Thanks

What are the versions of the database which is comes with e-business suit?11.5.10.2 --> 9.2.0.6
11.5.10 --> 9.2.0.5
11.5.9 --> 9.2.0.3
11.5.8 --> 8.1.7.4

Maximum volume of data supported by the version of the database embedded

Hi,
How to know the maximum volume of data supported by the version of the database embedded??
Any help will be needful for me
Thanks and Regards

* 1 EB = 1,000,000,000,000,000,000 B = 1 billion gigabytes
The term exbibyte, using a binary prefix, is used for powers of 1024 bytes.
Source: http://en.wikipedia.org/wiki/Exabyte
Regards
Asif Kabir
-- Mark the answer as correct/helpful

Knowing the exact version of the Database

i am having a hard time knowing the version of the attached database on my server.. Lets says someone created a database using sql
server version xxxx and he created a backup of that DB then he gave me. how do i find the database version then. Thanks.

>>i am having a hard time knowing the version of the attached database on my server.
USE DBNAME
GO
DBCC DBINFO() WITH TABLERESULTS
You can refer the
--dbi_version - New Version of the database
--dbi_createVersion -- The old version of the database
Just compare the output of dbi_createversion with below list to find the source database version.
http://sqlserverbuilds.blogspot.com/2014/01/sql-server-internal-database-versions.html
SQL Server Version
Internal Database Version
Database Compatibility Level
SQL Server 2014
782
120
SQL Server 2012
706
110
SQL Server 2012 CTP1
(a.k.a. SQL Server 2011 Denali)
684
110
SQL Server 2008 R2
660 / 661
100
SQL Server 2008
655
100
SQL Server 2005 SP2+
with VarDecimal enabled
612
90
SQL Server 2005
611
90
SQL Server 2000
539
80
SQL Server 7.0
515
70
SQL Server 6.5
408
65
SQL Server 6.0
60
--Prashanth

Dbsql version of the database how to read noSQL

dbsql version of the database how to read noSQL?
Is there a way to achieve?

Your question is extremely difficult to understand. However, because you are asking about dbsql, I think you are in the wrong forum. This is the BDB JE forum, and BDB JE does not support sql. The BDB (C-based) product does support sql. Please post your questions to the BDB forum:
Berkeley DB
--mark

Updating metadata in OWB after modifying tables in the database

Hi All,
In our data warehouse, one key field will suffer a change in data precision, from number(4) to number(5). This field exists in several tables across the database and I have created a procedure to alter all related tables in Oracle (10g). Is there a way to create a similar procedure or script to modify the metadata in OWB in order to reflect the changes in the altered tables from the database? I think the script should refresh the tables in the metadata but I'm not sure if it would be necessary to sincronize or validate the related mappings.
I'm newbie in OWB so I'm not sure whether this is achievable or not.
Thanks in advance for your guidance.
Regards,
Mauricio
Edited by: mcruz on 21/03/2010 17:07

Below is a OMBPlus tcl script to set the precision and scale of a specific column name in all tables of the current oracle module
Prerequisite is that you have made the connection to the OWB repository in OMBPlus (OMBCONNECT) and have set the context to the right oracle module (OMBCC and set OMBPROMPT ON, the latter to display your current context in the prompt)
Happy scripting.
proc set_nbr_len {p_objtyp p_col_name p_scale p_precision} {
   set tbls [OMBLIST ${p_objtyp}S]
   foreach tbl $tbls {
      set cols [OMBRETRIEVE $p_objtyp '$tbl' GET COLUMNS '$p_col_name']
      foreach col $cols {
       set dattyp [OMBRETRIEVE $p_objtyp '$tbl' COLUMN '$col' \
                     GET PROPERTIES (DATATYPE)]
       if { [string first "NUMBER" $dattyp] != -1 } {
            puts "Column $col scale & precision reset in $p_objtyp $tbl"
                OMBALTER $p_objtyp '$tbl' MODIFY COLUMN '$col' SET PROPERTIES \
                     (SCALE, PRECISION) VALUES \
               ('$p_scale', '$p_precision')
   OMBCOMMIT
set_nbr_len TABLE <your column name> <your precision> <your scale>

Importing New Version of the database

Hello. I don't know if this is the right forum for this question but, we are trying to update our test finanical database by importing a copy from our live finanical database that was exported. We log into SVRMGR as SYSTEM/MANAGER and try to start the import, but we can't get the PO, GL objects to drop. We can get the system objects to drop. When we log in as APPS/APPS, the apps objects drop, but we still can't get the other objects to drop.
Do we have to log into each Oracle Financial object (i.e. PO, GL, etc) in order to drop them so we can import updated data? Or are we missing a command or part of a command when we log into SRVMGR in our to have full access to all the database objects? Our system in Oracle 8.0.5 running on Windows NT server. Thanks for your assistance.
David Correia
MIS
NECMSC

Were covariant return types removed from the compiler? I tried compiling this code:
import java.lang.reflect.*;
class Base implements Cloneable {
    public Base clone() { return null; }
class Derived extends Base {
    public Derived clone() { return null; }
public class Generic {
    public static void main(String[] args) throws Exception {
        Method m = Derived.class.getDeclaredMethod("clone", new Class[] { });
        System.out.println(m.getReturnType());
}And got these errors:
Generic.java:4: clone() in Base cannot override clone() in java.lang.Object; att
empting to use incompatible return type
found : Base
required: java.lang.Object
public Base clone() { return null; }
^
Generic.java:8: clone() in Derived cannot override clone() in Base; attempting t
o use incompatible return type
found : Derived
required: Base
public Derived clone() { return null; }
^
2 errors
I think this same program compiled without error with the first version of the generic compiler.

How can we know version of the database ?

Hi all,
How can we know the version of the under lying database ? Please share your ideas.
Thanks

Hi,
Choose System->Status Menu item to open the status window.
You can see the DB data in the Bottom right.
Regards
Karthik D

Minimum version of the database that can be directly upgrade into 11G2

Dear DBA's,
Where can I find a document from Oracle showing/proving I can upgrade directly from 9.2.0.6 intoi 11.2.0.1?
Txs for your help
Rgds
Carlos

okKarol wrote:
Dear DBA's,
Where can I find a document from Oracle showing/proving I can upgrade directly from 9.2.0.6 intoi 11.2.0.1?
Txs for your help
Rgds
CarlosIn the 11.2 Upgrade Guide, found at http://download.oracle.com/docs/cd/E11882_01/server.112/e10819/preup.htm#i1007814
Or simply go to tahiti.oracle.com, where you will find all of oracle's doc libraries. Drill down to your product and version. The you will find the complete doc set for that product/version, including installation and/or upgrade guides.

E-Business Suite Customisations - which version of the Database can I use?

Hi,
We've made some customisations to the E-Business suite and want to find out what the Oracle official line is on licencing database. We think that making the customisations means that we need more database but could a lower (& cheaper) type of database license be acquired (standard?) to handle the processing for any customs and then, using a link, just load the finished data into the Apps interface, thereby avoiding any customs in the Apps db? If so, can it be on the same server as the Apps?

The best place for such app specific request would be in one of the eBusiness forums.
Nicolas.

BIB-16633 Cannot connect because the database version is incompatible with

BIB-16633 Cannot connect because the database version is incompatible with Feb 15, 2005 9:28 PM
Reply
why is this?
oracle.dss.connection.common.ConnectionException: BIB-16633 Cannot connect because the database version is incompatible with this BI Beans version.
at oracle.dss.connection.server.drivers.mdm.MDMConnectionDriverImpl.connect(MDMConnectionDriverImpl.java:147)
at oracle.dss.connection.server.ConnectionImpl.connect(ConnectionImpl.java:285)
at oracle.dss.connection.client.Connection.connect(Connection.java:425)
at oracle.dss.connection.client.Connection.connect(Connection.java:342)
at oracle.dss.addins.designer.OLAPSource.test(OLAPSource.java:284)
at oracle.dss.addins.wizard.configFileEditor.OlapPanel.testConnection(OlapPanel.java:244)
at oracle.dss.addins.wizard.configFileEditor.OlapPanel.btnTest_actionPerformed(OlapPanel.java:378)
at oracle.dss.addins.wizard.configFileEditor.OlapPanel$3.actionPerformed(OlapPanel.java:120)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:245)
at java.awt.Component.processMouseEvent(Component.java:5100)
at java.awt.Component.processEvent(Component.java:4897)
at java.awt.Container.processEvent(Container.java:1569)
at java.awt.Component.dispatchEventImpl(Component.java:3615)
at java.awt.Container.dispatchEventImpl(Container.java:1627)
at java.awt.Component.dispatchEvent(Component.java:3477)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
at java.awt.Container.dispatchEventImpl(Container.java:1613)
at java.awt.Window.dispatchEventImpl(Window.java:1606)
at java.awt.Component.dispatchEvent(Component.java:3477)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:141)
at java.awt.Dialog$1.run(Dialog.java:540)
at java.awt.Dialog.show(Dialog.java:561)
at java.awt.Component.show(Component.java:1133)
at java.awt.Component.setVisible(Component.java:1088)
at oracle.bali.ewt.dialog.JEWTDialog.runDialog(Unknown Source)
at oracle.dss.addins.wizard.configFileEditor.ConfigFileEditorWizard.run(ConfigFileEditorWizard.java:229)
at oracle.dss.addins.designer.BIDesignerImpl.editConfigFile(BIDesignerImpl.java:1428)
at oracle.dss.addins.designer.BIDesignerAddin.openBIDesignerSettings(BIDesignerAddin.java:990)
at oracle.dss.addins.designer.BIDesignerAddin.actionPerformed(BIDesignerAddin.java:807)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
at javax.swing.AbstractButton.doClick(AbstractButton.java:289)
at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1113)
at javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mouseReleased(BasicMenuItemUI.java:943)
at java.awt.Component.processMouseEvent(Component.java:5100)
at java.awt.Component.processEvent(Component.java:4897)
at java.awt.Container.processEvent(Container.java:1569)
at java.awt.Component.dispatchEventImpl(Component.java:3615)
at java.awt.Container.dispatchEventImpl(Container.java:1627)
at java.awt.Component.dispatchEvent(Component.java:3477)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483)
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
at java.awt.Container.dispatchEventImpl(Container.java:1613)
at java.awt.Window.dispatchEventImpl(Window.java:1606)
at java.awt.Component.dispatchEvent(Component.java:3477)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
Lisa Sherriff
Posts: 137
OTN Member Since: Jan, 2001
Re: BIB-16633 Cannot connect because the database version is incompatible w ( In Reply To : BIB-16633 Cannot connect because the database version is incompatible with ) Feb 16, 2005 1:32 AM
Reply
Hi,
From the 10.1.2 BI Beans Install Guide it says:
OracleBI Beans supports data stored in Oracle9i Enterprise Edition or Oracle Database 10g Enterprise Edition. However, only particular releases and patchsets are supported:
* Oracle9i Release 2 Enterprise Edition, as follows:
o 9.2.0.6 for all platforms.
o 9.2.0.5 with the latest OLAP patch for Windows-only.
* Oracle Database 10g Release 1 Enterprise Edition with the latest OLAP patch.
From the error message it would appear that the Database is not one of the above.
Thanks,
Lisa
JDev QA
401488
Posts: 48
OTN Member Since: Aug, 2002
Re: BIB-16633 Cannot connect because the database version is incompatible with ( In Reply To : BIB-16633 Cannot connect because the database version is incompatible with ) Feb 18, 2005 8:01 PM
Reply
Hi,
Please note that we have follwing versions of DB up and running:-
1)Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
2)Oracle9i Enterprise Edition Release 9.2.0.5.0 - Production
With the Partitioning and Real Application Clusters options
JServer Release 9.2.0.5.0 - Production
Pls let us know the solution to resolve this problem ASAP.
Thanks.

You are not using a supported version of the database. BI Beans/OLAP only support the following database versions:
10g - 10.1.0.3 with additional OLAP patch
9i - 9205 with additional OLAP patch
9i - 9206
I would suggest that you have not applied all the required database patches to your instance.
Hope this helps
Business Intelligence Beans Product Management Team
Oraclc Corporation

How can I find out the database version from an old backupset

Hi,
I have to restore a database using an old backupset (4 years ago) to a new database. My challenge is we don't know what version of the database were used back then. Is there anyway I can find this information. We are using the RMAN catalog.
Or is RMAN restore and recovery can be used to a newer version than the backupset?
Thanks in advance.
Regards,
Sosan Fong

Thanks for the reply and suggestion.
We are using its own software for all databases hosted in the server. So I need to cleanup and reinstall after tested in 11g. A little bit more work, but if it works, that's ok. Is there any other suggestions?
Regards,
S

Lync 2013 Error 31055 ,31059 LS Call Park Service, The database being used by Group Pickup is not the appropriate version and There was a problem communicating with the Group Pickup backend database.

Hello
I have Lync 2013 and 2010 , still i didn't finish my migration completely from 2010 to 2013 .this is coexistence environment that contains both Lync Server 2010 and Lync Server 2013 .
There was no error's in my lync 2013 front end and back end server's and every thing was fine, yesterday I installed windows updated AND CU for my lync 2013 front end and backend server's .
later on after restarting both the front end and the back end server's i start having hundred's of these error's related to "LS Call Park Service".
so any advice for these issue ? and what is the effect for these error .
below is the error I got .
The database being used by Group Pickup is not the appropriate version.
The database is not the correct version:
Connection: Data Source=HQ-LYNC2013-BE.aaaaaaaaaaaaaaaaaaaaaaaaaaa\rtc;Initial Catalog=cpsdyn;Integrated Security=True
Expected... SchemaVersion: 1, SprocVersion: 1, UpgradeVersion: 2
Actual... SchemaVersion: 0, SprocVersion: 0, UpgradeVersion: 0
Cause: The database has not been upgraded.
Resolution:
Upgrade the database to CU1.
==============================================================
There was a problem communicating with the Group Pickup backend database.
There were problems accessing SQL server:
Connection: Data Source=HQ-LYNC2013-BE.aaaaaaaaaaaaaaaaaaaaaaaaaa\rtc;Initial Catalog=cpsdyn;Integrated Security=True
Message: The EXECUTE permission was denied on the object 'DbpGetVersionSchema', database 'cpsdyn', schema 'dbo'.
Error code: -2146232060
Error number: 229
Cause: This may be caused by connectivity issues with the backend database.
Resolution:
Check if SQL backend is running and accepts connections from Group Pickup.
=============================================================================
Kind Regards
MK

Hello
thanks Holger for u r replay .
due to the Microsoft article about the cu :
I run only :
Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn FEBE.FQDN -Verbose
Note In a coexistence environment that contains both Lync Server 2010 and Lync Server 2013 and in which the Central Management Service is located on a Lync Server 2010 pool, do not run the
Install-CsDatabase -CentralManagementDatabase command. If you later move the Central Management Service to a Lync Server 2013 pool, you have to run the
Install-CsDatabase -CentralManagementDatabase command to apply the changes.
here is what I get on my power shell after i run the command : "WARNING: Warning: Failed to execute batch --"
PS C:\Users\MK> Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn HQ-LYNC2013-BE.MyDomain -Verbose
VERBOSE: Creating new log file
"C:\Users\MK\AppData\Local\Temp\2\Install-CsDatabase-82d6613c-f2e3-47e6-8fc4-8f75d2efe6e4.xml".
VERBOSE: Install databases required by Lync Server role(s).
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.BlobStore'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcxds.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.AbsDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcab.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsConfigDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsconfig.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsdyn.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.CpsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database cpsdyn.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.ArchivingDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\arc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsLog.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.MonitoringDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\mon. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsCDR.
VERBOSE: Assigning "BackendStore:BlobStore:LogPath" to F:\CsData
VERBOSE: Assigning "BackendStore:RtcSharedDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ArchivingStore:ArchivingDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:MonitoringDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:QoEMetricsDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ArchivingStore:ArchivingDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:MonitoringDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:QoEMetricsDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ABSStore:AbsDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsConfigDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsDynDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:CpsDynDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "BackendStore:BlobStore:DbPath" to F:\CsData
VERBOSE: Assigning "BackendStore:RtcSharedDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ABSStore:AbsDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsConfigDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsDynDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:CpsDynDatabase:DbPath" to F:\CsData
VERBOSE: Installing "BackendStore" on HQ-LYNC2013-BE.MyDomain\rtc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.BlobStore'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcxds.
Checking state for database rtcxds.
State of database rtcxds is DbState_RequiresMinorUpgrade.
Database rtcxds set to mode Restricted.
Dropping all procedures, functions and views from database rtcxds.
Executing RtcDb.sql...
Adding master role...
Setting owner for database rtcxds to sa.
Creating login MyDomain\RTCHSUniversalServices.
Creating user MyDomain\RTCHSUniversalServices.
Creating Schema MyDomain\RTCHSUniversalServices.
Creating login MyDomain\RTCUniversalReadOnlyAdmins.
Creating user MyDomain\RTCUniversalReadOnlyAdmins.
Creating Schema MyDomain\RTCUniversalReadOnlyAdmins.
Creating login MyDomain\RTCUniversalServerAdmins.
Creating user MyDomain\RTCUniversalServerAdmins.
Creating Schema MyDomain\RTCUniversalServerAdmins.
Adding account MyDomain\RTCHSUniversalServices to role ConsumerRole.
Adding account MyDomain\RTCUniversalReadOnlyAdmins to role ConsumerRole.
Adding account MyDomain\RTCHSUniversalServices to role ReplicatorRole.
Adding account MyDomain\RTCHSUniversalServices to role PublisherRole.
Adding account MyDomain\RTCUniversalServerAdmins to role PublisherRole.
Setting database version: Schema Version 15, Sproc Version 13, Update Version 2.
Setting the database rtcxds to multi user mode.
Database rtcxds is set to multi user mode.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RtcSharedDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcshared.
Database created by script "RtcSharedDatabase" already exists and is current.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-BackendStore-HQ-LYNC2013-BE.MyDomain_rtc-[2014_11_13][14_35_01].log"
VERBOSE: Installing "ABSStore" on HQ-LYNC2013-BE.MyDomain\rtc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.AbsDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcab.
Checking state for database rtcab.
State of database rtcab is DbState_RequiresMinorUpgrade.
Database rtcab set to mode Restricted.
Dropping all procedures, functions and views from database rtcab.
Executing RtcAbTypes.sql...
WARNING: Warning: Failed to execute batch --
-- Copyright (c) Microsoft Corporation. All rights reserved.
exec sp_addrole N'ServerRole'.
Executing RtcAbDb.sql...
Setting owner for database rtcab to sa.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Adding account MyDomain\RTCComponentUniversalServices to role ServerRole.
Setting database version: Schema Version 62, Sproc Version 42, Update Version 3.
Setting the database rtcab to multi user mode.
Database rtcab is set to multi user mode.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-ABSStore-HQ-LYNC2013-BE.MyDomain_rtc-[2014_11_13][14_35_20].log"
VERBOSE: Installing "ApplicationStore" on HQ-LYNC2013-BE.MyDomain\rtc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsConfigDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsconfig.
Database created by script "RgsConfigDatabase" already exists and is current.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsdyn.
Database created by script "RgsDynDatabase" already exists and is current.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.CpsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database cpsdyn.
Checking state for database cpsdyn.
State of database cpsdyn is DbState_RequiresMinorUpgrade.
Database cpsdyn set to mode Restricted.
Dropping all procedures, functions and views from database cpsdyn.
Executing CpsDyn.sql...
Setting owner for database cpsdyn to sa.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Creating login MyDomain\RTCUniversalReadOnlyAdmins.
Creating user MyDomain\RTCUniversalReadOnlyAdmins.
Creating Schema MyDomain\RTCUniversalReadOnlyAdmins.
Creating login MyDomain\RTCUniversalServerAdmins.
Creating user MyDomain\RTCUniversalServerAdmins.
Creating Schema MyDomain\RTCUniversalServerAdmins.
Adding account MyDomain\RTCComponentUniversalServices to role ReadWriteRole.
Adding account MyDomain\RTCUniversalServerAdmins to role ReadWriteRole.
Adding account MyDomain\RTCUniversalReadOnlyAdmins to role ReadOnlyRole.
Setting database version: Schema Version 1, Sproc Version 1, Update Version 2.
Setting the database cpsdyn to multi user mode.
Database cpsdyn is set to multi user mode.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-ApplicationStore-HQ-LYNC2013-BE.MyDomain_rtc-[2014_11_13][14_35_37].log"
VERBOSE: Installing "ArchivingStore" on HQ-LYNC2013-BE.MyDomain\arc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.ArchivingDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\arc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsLog.
Database created by script "ArchivingDatabase" already exists and is current.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-ArchivingStore-HQ-LYNC2013-BE.MyDomain_arc-[2014_11_13][14_35_51].log"
VERBOSE: Installing "MonitoringStore" on HQ-LYNC2013-BE.MyDomain\mon, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.MonitoringDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\mon. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsCDR.
Checking state for database LcsCDR.
Checking state for database LcsCDR.
State of database LcsCDR is DbState_RequiresMinorUpgrade.
WARNING: The database LcsCDR being updated has data file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\DbPath\LcsCDR.mdf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\DbPath\LcsCDR.mdf. Supplied path will be ignored.
WARNING: The database LcsCDR being updated has log file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\LogPath\LcsCDR.ldf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\LogPath\LcsCDR.ldf. Supplied path will be ignored.
Database LcsCDR set to mode Restricted.
Dropping all procedures, functions and views from database LcsCDR.
Executing CdrDb.sql...
Setting owner for database LcsCDR to sa.
Creating login MyDomain\CSAdministrator.
Creating user MyDomain\CSAdministrator.
Creating Schema MyDomain\CSAdministrator.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Adding account MyDomain\RTCComponentUniversalServices to role ServerRole.
Adding account MyDomain\RTCComponentUniversalServices to role ReportsReadOnlyRole.
Adding account MyDomain\CSAdministrator to role ReportsReadOnlyRole.
Setting database version: Schema Version 39, Sproc Version 82, Update Version 2.
Setting the database LcsCDR to multi user mode.
Database LcsCDR is set to multi user mode.
SQL Server Agent is running and its start mode was detected as Auto.
Executing CdrJobs.sql...
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.QoEMetricsDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\mon. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database QoEMetrics.
Checking state for database QoEMetrics.
Checking state for database QoEMetrics.
State of database QoEMetrics is DbState_RequiresMinorUpgrade.
WARNING: The database QoEMetrics being updated has data file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\DbPath\QoEMetrics.mdf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\DbPath\QoEMetrics.mdf. Supplied path will be ignored.
WARNING: The database QoEMetrics being updated has log file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\LogPath\QoEMetrics.ldf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\LogPath\QoEMetrics.ldf. Supplied path will be ignored.
Database QoEMetrics set to mode Restricted.
Dropping all procedures, functions and views from database QoEMetrics.
Executing QoEDb.sql...
Setting owner for database QoEMetrics to sa.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Adding account MyDomain\RTCComponentUniversalServices to role ServerRole.
Setting database version: Schema Version 62, Sproc Version 90, Update Version 1.
Setting the database QoEMetrics to multi user mode.
Database QoEMetrics is set to multi user mode.
SQL Server Agent is running and its start mode was detected as Auto.
Executing QoEJobs.sql...
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-MonitoringStore-HQ-LYNC2013-BE.MyDomain_mon-[2014_11_13][14_35_51].log"
VERBOSE: No changes were made to the Central Management Store.
VERBOSE: Creating new log file
"C:\Users\MK\AppData\Local\Temp\2\Install-CsDatabase-82d6613c-f2e3-47e6-8fc4-8f75d2efe6e4.html".
WARNING: "Install-CsDatabase" processing has completed with warnings. "5" warnings were recorded during this run.
WARNING: Detailed results can be found at
"C:\Users\MK\AppData\Local\Temp\2\Install-CsDatabase-82d6613c-f2e3-47e6-8fc4-8f75d2efe6e4.html".
PS C:\Users\MK>
I hope some one can confirm no issue with what I did ??
Kind Regards
MK

Why do I get a class conflict between the Prepare SQL.vi and the Get Column Name.vi with the SQL Toolkit compatibility vis from the Database Connectivity Toolkit?

I have done extensive programming with the SQL Toolkit with LabVIEW versions through 6.1. My customer now wants to upgrade to Windows 7, so I am trying to upgrade to LabVIEW 2009 (my latest purchased version) using the Database Connectivity Toolkit, and the SQL Toolkit Compatibility vis. Everything seemed to be going okay with the higher level SQL operations, but I ran into trouble with the Get Column Name.vi.
The pictures below show the problem. The original SQL Toolkit connected the Prepare SQL.vi with the Get Column Name.vi with a cluster of two references, one for connection, and one for sql. The new compatibility vis have a class conflict in the wire because the Prepare SQL.vi contains a cluster with connection, and command references, but the Get Column Name.vi expects a cluster with connection and recordset references.
How do I resolve this conflict?
Thank You.
Dan

I've never worked with the old version of the toolkit, so I don't know how it did things, but looking inside the SQL prep VI, it only generates a command, and the the column name VI wants a recordset. I'm not super familiar with all the internals of ADO, but my understanding is that is standard - you only have the columns after you execute the command and get the recordset back. What you can apparently do here is insert the Execute Prepared SQL VI in the middle and that will return what you need.
I'm not sure why it worked before. Maybe the execute was hidden inside the prep VI or maybe you can get the column names out of the command object before execution. In general, I would recommend considering switching to the newer VIs.
Try to take over the world!

OWB Paris: Recommend version of the Database

Similar Messages

Maybe you are looking for