Configured database is not compatible

When I try to open the inventory I get the error, configured database is
not compatible, trying to access a later version of the database. I have
the database configured for Sybase, which is suppossed to be the
default. However, I don't see a sybase database running on the server, I
do see a my sql database running on the server. Any ideas what to do
next? Thanks.

When in ConsoleOne I go to Tools>ZenWorks Inventory>Configure DB it tells
me the database is configured successfully. I checked the policys and
they seem to be setup correctly. When I try to do an Inventory Query, or
any othe data retrieval, I get the error:
The configured database is not a compatible database.
You are trying to access the later version of the ZenWorks database.
To me, it sounds like the ZenWorks engine and the Sybase database on the
server, are not the same or compatible. How do I check this and correct
this?
Thanks.
>
On Fri, 21 Jul 2006 12:47:48 GMT, [email protected] wrote:
>
> > Do I need to start it somehow? This is my
> > first time trying to use zenworks inventory and the instructions are
not
> > very good.
>
> if it is installed you can start it with mgmtdbs, but you will also
need to
> configure the policies correctly
> --
>
>
> Marcus Breiden
>
> If you are asked to email me information please change -- to - in my e-
mail
> address.
> The content of this mail is my private and personal opinion.
> http://www.edu-magic.net

Similar Messages

The configured database is not a compatible database

Hi, i am experiencing some problems getting our zen servers to carry out
reporting, auditing, etc etc.
Running :
Netware 6.5 sp5
Zenworks Desktops managment 6.5sp1
When i attempt to carry out a report or click on the zenworks inventory
databse object within Console1 - the following error appears:
"the configured database is not a compatible database"
I have checked the Tids below but the settings have not changed:
http://support.novell.com/docs/Tids/.../10097366.html
and (even though this applies to zenworks 7)
http://www.novell.com/documentation/...a/aic80cg.html
I do not know what else to do.
Any assistance on this would be greatly appreciated.
regards
Dennis
IT Support

Dennis,
>
>Hi, i tried something along the lines of your advice, i used the console1
>from the server hosting the zenworks inventory server.
>
>I copied this to my local pc as this would be alot more quicker...and when
>i tried the Inventory reporting ...IT WORKED!!!!
>Resolved the issue of receiving the error message
>"The configured database is not a compatible database"
Nice.
I have seen that happen before and it was caused by Snapin versions. The
error message is a bit bogus. But if you are not seeing issues on the asa
screen of the server, then it's likely not the servers problem, but c1's
problem.
Jared Jennings - Data Technique, Inc.
Novell Support Forums Sysop
My Blog and Wiki with Tips, Tricks, and Tutorials
http://jaredjennings.org

RCVCAT database is not compatible with this version of RMAN

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

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

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

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

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

TARGET database is not compatible with this version of RMAN

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

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

TARGET database is not compatible with RMAN version

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

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

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

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

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

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

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

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

The configure database page not appear in grid control

hi
when i try to configure a database target in grid control appear a error . i know that the nslookup not working correctly because these machines not adding to dns server
it's possible communication between oms and agent whithout an dns server, only adding lines in the /etc/hosts
thanks

Which self Service function you are using to change the assignment ?
Their are two API to update asg values. Try to apply user hook on both of them and retry ur scenario.

Inventory Database not compatible

We are running Zenworks 6.5 for Desktops. We want to start using
Inventory. Everything is configured but when I go to view a workstation
inventory or a query, I get a error message. "The configured database is
not compatible database. You are trying to access the later version of the
ZENworks database.
How do I fix this? I haven't found any help in the manual or TIDs.
Thanks-Tirzah

I can't find that TID anywhere on Novells site. Can anyone help with
this? We are having a similiar problem and are hoping that this will be
a fix. Thanks
Mike
> I got it fix. I had to reinstall the inventory.
>
> TID: 10049948 with some modifications
> The reinstall recreate \\cccu04\vol1\ZENworks\Inv files, we use our
> backup files.
> Had to select Desktop Management database option in Install even though
> the TID doesn't mention it.
>
> > On Thu, 08 Dec 2005 23:05:48 GMT, [email protected] wrote:
> >
> > > How do I fix this?
> >
> > looks like you are not using the right snapins in c1.. try the one
from
> the
> > server running inventory..
> > --
> >
> >
> > Marcus Breiden
> >
> > If you are asked to email me information please change -- to - in my
e-
> mail
> > address.
> > The content of this mail is my private and personal opinion.
> > http://www.edu-magic.net
>

Forms6 LOB not compatible with 9i CLOB

We have a table with some CLOB data type fields. Front-end of this table is forms60 interface. As forms60 has LOB instead of CLOB, we have selected the same for the field in form. When we try to enter data through form, LOB related data missing from database and ### appears in place of LOB data in form.

According to the matrix documentation of 11 release 1 which clearly state that 9.2.0.8 can support all as my installation
as following
databases version (9.2.1.0, 9.2.0.8, 10.2.0.4, 11.1.0.6)
Rman catalog database + Schema + Rman utility is (9.2.0.8) database
Now 11 release 2 matrix documentation says no you have to use 10.2.0.3 even oracle documents are confusing me
I have successfully registered all the database in my catalog as well run ( crosscheck archivelog all, report schema ) was functioning smoothly
when its came to the integration part to HP - Data Protector it started to through me an error ( this version of database its not compatible with recovery manager)
and what does this oracle document senario means
====================
RMAN Compatibility:
Scenario
Assume that you maintain a production databases of the following releases:
9.2.0
10.2.0
11.2.0
You want to record RMAN repository data about these databases in a single recovery catalog database. According to Table B-2, you can use a single 11.2.0 recovery catalog database with a 11.2.0 catalog schema for all target databases. Ensure that the version of the RMAN client used to back up each target database meets the following requirements:
Use the 9.2.0 RMAN executable to back up the 9.2.0 database.
Use either the 9.2.0 or 10.2.0 RMAN executable to back up the 10.2.0 database.
Use any RMAN executable to back up the 11.2.0 database.
==================================
All what i want is to achieve one single catalog for all the above mentioned oracle versions and can be integrated with HP-DP
can anyone explain this doubts and give me a best solution to achieve desire solution if not what are the altarnative ??/
thanks and sorry its quite log post
Regards

Add management server: Setup version: 7.0.9538.0 is not compatible with database version: 7.1.10226.0

I want to add another management server to our existing SCOM environment. But whenever I run this setup on a new server I get stuck in the window for selecting the OperationsManager database. The database field stays blank and in the OpsMgrSetupWizard log
there are lines that the setup version is not compatible with the database version. But I use the same installer as when I installed the other management servers a year ago.
Maybe there is a newer setup installer? But I can't find it.
[10:42:54]: Error:
:Error:setup version: 7.0.9538.0 is not compatible with database version: 7.1.10226.0
[10:42:54]: Info:
:Info:Using DB command timeout = 1800 seconds.
[10:42:54]: Info:
:Info:isOMDatabase: Read returned true. so far, this is OM DB, not an empty DB
[10:42:54]: Debug:
:Connection was not open. We will try to open it.
[10:42:54]: Debug:
:SqlConnectionReady returned True.
[10:42:54]: Info:
:Info:Using DB command timeout = 1800 seconds.
[10:42:54]: Info:
:Info:isOMDatabase: Read did not return true. The MG is missing. This is not OM DB
[10:42:54]: Info:
:Info:Using DB command timeout = 1800 seconds.
[10:42:54]: Always:
:Azman store table not found in OperationsManagerDW table, assuming this is an not a valid OMDB for empty DB scenario.
[10:42:54]: Info:
:Info:DatabaseConfigurationPage: DB connection attempt completed.
[10:42:54]: Info:
:Info:DatabaseConfigurationPage: DB connection attempt completed.

Never mind, found it!
Apparently there was a newer version of SCOM setup in msdn and someone upgraded our existing SCOM environment. Downloaded the new setup, new report viewer controls and a System
CLR Types for Microsoft® SQL Server® 2012 and now it works!!

EXP-00037: Export views not compatible with database version

kindly help with this error. We have already run catexp.sql but still that is not helping, we are still getting the same error.
we are exporting 8i db.
Export: Release 8.1.7.0.0 - Production on Thu Feb 21 14:34:25 2008
(c) Copyright 2000 Oracle Corporation. All rights reserved.
Connected to: Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
EXP-00037: Export views not compatible with database version
EXP-00000: Export terminated unsuccessfully

Does this apply to you?
Error: EXP 37
Text: Export views not compatible with database version
Cause: The Export utility is at a higher version than the database version
and is thereby incompatible.
Action: Use the same version of Export utility as the database.

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

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

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

The product version and database version are not compatible

The following simple program gets an exception {The product version and database version are not compatible} its very hard to proceed from here. Does anybody know what cause this?
Best Regards
Jan Isacsson
using System.Collections.ObjectModel;
using Microsoft.MasterDataServices.Deployment;
using Microsoft.MasterDataServices.Services.DataContracts;
namespace MdsDeploy
    class Program
        static void Main(string[] args)
            try
                ModelReader reader = new ModelReader();
                Collection<Identifier> models = reader.GetModels();
                foreach (Identifier modelId in models)
                    Console.WriteLine(modelId.Name);
            catch (System.Exception ex)
                Console.WriteLine("Error: " + ex.Message);
            Console.ReadKey();

Hi Jan,
For the error "The product version and database version are not compatible", as Emma said, the version number of the Service does not match the database schema version.
In your scenario, which version of database are you using? Please note that MDS update required after SQL 2012 SP1 installation, please refer to the links below to see the details.
http://byobi.com/blog/2012/11/mds-update-required-after-sql-2012-sp1-installation/
http://msdn.microsoft.com/en-IN/library/gg488708.aspx
Regards,
Charlie Liao
TechNet Community Support

Configured database is not compatible

Similar Messages

Maybe you are looking for