Update poa database version to 1400

Hi Support team,
After upgrade our system from groupwise 2012 to 2014. The database version of POA is still 12.
How can we upgrade it to 14 ?
As Groupwise 2012, i just run ./gwpoa --show --home xxxx. it will be upgraded.
Thansk
Regards,
Ndhuynh

Originally Posted by dzanre
I'm sorry. I really do not understand what you are asking here. If you are
asking if the GroupWise 2014 client can be used with older databases, the answer
is no. However, I'm not sure if that is really your question.
tks Dzanre
I means what will happen if my groupwise 2014 POA keep running with the old database (Version 12)
I focus to the groupwise POA, it's boring if running groupwise 2014 with "version 12 label" beside POA name.
"If you are
asking if the GroupWise 2014 client can be used with older databases, the answer
is no"
Do you means that the older databases is groupwise 2012 server, not groupwise 2014 with 2012 version database?
- If groupwise 2012 server, i really test with groupwise 2014 client and it didn't work.
- If groupwise 2014 with 2012 version database, The groupwise 2014, 2012 and 8 client can works well with it.
Nice day, Dzanre!

Similar Messages

Long term release of CriticaL Patch Updates: which database version to use?

Hello,
The company i work for ask me to mak a plan to stay up-to-date with each quarterly released CPU's (Critical patch update)
We have 11.1.0.7 databases and 11.2.0.2 databases.
When i look at the latest CPU, docid 1455387.1 , i notice that for each final RDBMS release, a CPU is relased for a very long time, but for recent releases it is not.
For exampe for release 11.1.7.0 a CPU is relased until July 2015, but for 11.2.0.2 final CPU ends already at January 2013.
For 10.2.0.5 i noticed the same behaviour.
This makes me think....
In my opinion i would never upgrade from 11.1 to release 11.2, until the final 11.2. release come out, if i want to stat up-to-date with the cpu's.
Am i right?
And does this mean that if new applications neeed in our company need an 11g daatbase, i better install 11.1.0.7 rather then 11.2?
(if the application does not need 11.2 funtionality of course)
Any comment is appreciated.
Regards,
Harry

Pl see support policies on pages 2 thru 4 in this doc - http://www.oracle.com/us/support/library/lifetime-support-technology-069183.pdf. CPU patches are available only during Premier and Extended Support.
Details are in this MOS Doc
Lifetime Support and Support Policies - Oracle Database Overview [ID 1351163.1]
Release and support schedule is published - see this MOS Doc
Release Schedule of Current Database Releases [ID 742060.1]
It is always recommended to upgrade to the latest database version available, even if you do not need the features. A possible option is to perform upgrades on a yearly basis to whatever is the latest version available and apply CPUs/PSUs for four quarters until the next upgrade cycle
HTH
Srini

Database Version Update

Aloha,
We have 11g version 11.1.0.7 currently and we want to update it to version 11.2... Hope some can help me on the procedure how to update the said DB.
Thanks a lot.
Edited by: TheHades0210 on Apr 28, 2010 9:46 PM

I would also highly recommend that you read thru MOS Doc 785351.1 (Oracle 11gR2 Upgrade Companion) before starting upgrade activities.
HTH
Srini

Since i updated i tunes version 11 i cant sync with the store or database

since i updated my itunes version to 11 i cant sync with itunes or gracenote

Like Jim, mine is mirroring with no problem. I use it several times a week. It would not appear to something Apple needs to fix. As for "all the fixes here" we have no way of knowing what that means, so it is difficult to determine what to recommend.

Selective XML Index feature is not supported for the current database version , SQL Server Extended Events , Optimizing Reading from XML column datatype

Team , Thanks for looking into this ..
As a last resort on optimizing my stored procedure ( Below ) i wanted to create a Selective XML index ( Normal XML indexes doesn't seem to be improving performance as needed ) but i keep getting this error within my stored proc . Selective XML
Index feature is not supported for the current database version.. How ever
EXECUTE sys.sp_db_selective_xml_index; return 1 , stating Selective XML Indexes are enabled on my current database .
Is there ANY alternative way i can optimize below stored proc ?
Thanks in advance for your response(s) !
/****** Object: StoredProcedure [dbo].[MN_Process_DDLSchema_Changes] Script Date: 3/11/2015 3:10:42 PM ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
-- EXEC [dbo].[MN_Process_DDLSchema_Changes]
ALTER PROCEDURE [dbo].[MN_Process_DDLSchema_Changes]
AS
BEGIN
SET NOCOUNT ON --Does'nt have impact ( May be this wont on SQL Server Extended events session's being created on Server(s) , DB's )
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED
select getdate() as getdate_0
DECLARE @XML XML , @Prev_Insertion_time DATETIME
-- Staging Previous Load time for filtering purpose ( Performance optimize while on insert )
SET @Prev_Insertion_time = (SELECT MAX(EE_Time_Stamp) FROM dbo.MN_DDLSchema_Changes_log ) -- Perf Optimize
-- PRINT '1'
CREATE TABLE #Temp
EventName VARCHAR(100),
Time_Stamp_EE DATETIME,
ObjectName VARCHAR(100),
ObjectType VARCHAR(100),
DbName VARCHAR(100),
ddl_Phase VARCHAR(50),
ClientAppName VARCHAR(2000),
ClientHostName VARCHAR(100),
server_instance_name VARCHAR(100),
ServerPrincipalName VARCHAR(100),
nt_username varchar(100),
SqlText NVARCHAR(MAX)
CREATE TABLE #XML_Hold
ID INT NOT NULL IDENTITY(1,1) PRIMARY KEY , -- PK necessity for Indexing on XML Col
BufferXml XML
select getdate() as getdate_01
INSERT INTO #XML_Hold (BufferXml)
SELECT
CAST(target_data AS XML) AS BufferXml -- Buffer Storage from SQL Extended Event(s) , Looks like there is a limitation with xml size ?? Need to re-search .
FROM sys.dm_xe_session_targets xet
INNER JOIN sys.dm_xe_sessions xes
ON xes.address = xet.event_session_address
WHERE xes.name = 'Capture DDL Schema Changes' --Ryelugu : 03/05/2015 Session being created withing SQL Server Extended Events
--RETURN
--SELECT * FROM #XML_Hold
select getdate() as getdate_1
-- 03/10/2015 RYelugu : Error while creating XML Index : Selective XML Index feature is not supported for the current database version
CREATE SELECTIVE XML INDEX SXI_TimeStamp ON #XML_Hold(BufferXml)
FOR
PathTimeStamp ='/RingBufferTarget/event/timestamp' AS XQUERY 'node()'
--RETURN
--CREATE PRIMARY XML INDEX [IX_XML_Hold] ON #XML_Hold(BufferXml) -- Ryelugu 03/09/2015 - Primary Index
--SELECT GETDATE() AS GETDATE_2
-- RYelugu 03/10/2015 -Creating secondary XML index doesnt make significant improvement at Query Optimizer , Instead creation takes more time , Only primary should be good here
--CREATE XML INDEX [IX_XML_Hold_values] ON #XML_Hold(BufferXml) -- Ryelugu 03/09/2015 - Primary Index , --There should exists a Primary for a secondary creation
--USING XML INDEX [IX_XML_Hold]
---- FOR VALUE
-- --FOR PROPERTY
-- FOR PATH
--SELECT GETDATE() AS GETDATE_3
--PRINT '2'
-- RETURN
SELECT GETDATE() GETDATE_3
INSERT INTO #Temp
EventName ,
Time_Stamp_EE ,
ObjectName ,
ObjectType,
DbName ,
ddl_Phase ,
ClientAppName ,
ClientHostName,
server_instance_name,
nt_username,
ServerPrincipalName ,
SqlText
SELECT
p.q.value('@name[1]','varchar(100)') AS eventname,
p.q.value('@timestamp[1]','datetime') AS timestampvalue,
p.q.value('(./data[@name="object_name"]/value)[1]','varchar(100)') AS objectname,
p.q.value('(./data[@name="object_type"]/text)[1]','varchar(100)') AS ObjectType,
p.q.value('(./action[@name="database_name"]/value)[1]','varchar(100)') AS databasename,
p.q.value('(./data[@name="ddl_phase"]/text)[1]','varchar(100)') AS ddl_phase,
p.q.value('(./action[@name="client_app_name"]/value)[1]','varchar(100)') AS clientappname,
p.q.value('(./action[@name="client_hostname"]/value)[1]','varchar(100)') AS clienthostname,
p.q.value('(./action[@name="server_instance_name"]/value)[1]','varchar(100)') AS server_instance_name,
p.q.value('(./action[@name="nt_username"]/value)[1]','varchar(100)') AS nt_username,
p.q.value('(./action[@name="server_principal_name"]/value)[1]','varchar(100)') AS serverprincipalname,
p.q.value('(./action[@name="sql_text"]/value)[1]','Nvarchar(max)') AS sqltext
FROM #XML_Hold
CROSS APPLY BufferXml.nodes('/RingBufferTarget/event')p(q)
WHERE -- Ryelugu 03/05/2015 - Perf Optimize - Filtering the Buffered XML so as not to lookup at previoulsy loaded records into stage table
p.q.value('@timestamp[1]','datetime') >= ISNULL(@Prev_Insertion_time ,p.q.value('@timestamp[1]','datetime'))
AND p.q.value('(./data[@name="ddl_phase"]/text)[1]','varchar(100)') ='Commit' --Ryelugu 03/06/2015 - Every Event records a begin version and a commit version into Buffer ( XML ) we need the committed version
AND p.q.value('(./data[@name="object_type"]/text)[1]','varchar(100)') <> 'STATISTICS' --Ryelugu 03/06/2015 - May be SQL Server Internally Creates Statistics for #Temp tables , we do not want Creation of STATISTICS Statement to be logged
AND p.q.value('(./data[@name="object_name"]/value)[1]','varchar(100)') NOT LIKE '%#%' -- Any stored proc which creates a temp table within it Extended Event does capture this creation statement SQL as well , we dont need it though
AND p.q.value('(./action[@name="client_app_name"]/value)[1]','varchar(100)') <> 'Replication Monitor' --Ryelugu : 03/09/2015 We do not want any records being caprutred by Replication Monitor ??
SELECT GETDATE() GETDATE_4
-- SELECT * FROM #TEMP
-- SELECT COUNT(*) FROM #TEMP
-- SELECT GETDATE()
-- RETURN
-- PRINT '3'
--RETURN
INSERT INTO [dbo].[MN_DDLSchema_Changes_log]
[UserName]
,[DbName]
,[ObjectName]
,[client_app_name]
,[ClientHostName]
,[ServerName]
,[SQL_TEXT]
,[EE_Time_Stamp]
,[Event_Name]
SELECT
CASE WHEN T.nt_username IS NULL OR LEN(T.nt_username) = 0 THEN t.ServerPrincipalName
ELSE T.nt_username
END
,T.DbName
,T.objectname
,T.clientappname
,t.ClientHostName
,T.server_instance_name
,T.sqltext
,T.Time_Stamp_EE
,T.eventname
FROM
#TEMP T
/** -- RYelugu 03/06/2015 - Filters are now being applied directly while retrieving records from BUFFER or on XML
-- Ryelugu 03/15/2015 - More filters are likely to be added on further testing
WHERE ddl_Phase ='Commit'
AND ObjectType <> 'STATISTICS' --Ryelugu 03/06/2015 - May be SQL Server Internally Creates Statistics for #Temp tables , we do not want Creation of STATISTICS Statement to be logged
AND ObjectName NOT LIKE '%#%' -- Any stored proc which creates a temp table within it Extended Event does capture this creation statement SQL as well , we dont need it though
AND T.Time_Stamp_EE >= @Prev_Insertion_time --Ryelugu 03/05/2015 - Performance Optimize
AND NOT EXISTS ( SELECT 1 FROM [dbo].[MN_DDLSchema_Changes_log] MN
WHERE MN.[ServerName] = T.server_instance_name -- Ryelugu Server Name needes to be added on to to xml ( Events in session )
AND MN.[DbName] = T.DbName
AND MN.[Event_Name] = T.EventName
AND MN.[ObjectName]= T.ObjectName
AND MN.[EE_Time_Stamp] = T.Time_Stamp_EE
AND MN.[SQL_TEXT] =T.SqlText -- Ryelugu 03/05/2015 This is a comparision Metric as well , But needs to decide on
-- Peformance Factor here , Will take advise from Lance if comparision on varchar(max) is a vital idea
--SELECT GETDATE()
--PRINT '4'
--RETURN
SELECT
top 100
[EE_Time_Stamp]
,[ServerName]
,[DbName]
,[Event_Name]
,[ObjectName]
,[UserName]
,[SQL_TEXT]
,[client_app_name]
,[Created_Date]
,[ClientHostName]
FROM
[dbo].[MN_DDLSchema_Changes_log]
ORDER BY [EE_Time_Stamp] desc
-- select getdate()
-- ** DELETE EVENTS after logging into Physical table
-- NEED TO Identify if this @XML can be updated into physical system table such that previously loaded events are left untoched
-- SET @XML.modify('delete /event/class/.[@timestamp="2015-03-06T13:01:19.020Z"]')
-- SELECT @XML
SELECT GETDATE() GETDATE_5
END
GO
Rajkumar Yelugu

@@Version : ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Microsoft SQL Server 2012 - 11.0.5058.0 (X64)
   May 14 2014 18:34:29
   Copyright (c) Microsoft Corporation
   Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
(1 row(s) affected)
Compatibility level is set to 110 .
One of the limitation states - XML columns with a depth of more than 128 nested nodes
How do i verify this ? Thanks .
Rajkumar Yelugu

How can i check if a procedure exists in a certain database version

So today i became really frustrated after noticing that the Oracle SQL version on some computer I needed to work on was 10.1. The problem with that was that I needed a procedure called "xmlserialize". I browsed the documentation for it, but I didn't see anything like "since 11.0" or something similar.
So.. how can I see what is the first Oracle SQL version that supported some procedure?
For example, when I check a class definition for Java, I consult the javadoc :
http://docs.oracle.com/javase/7/docs/api/java/math/BigInteger.html
and there there's a field called "Since". For BigInteger ( it's just an example ), it says "Since: JDK1.1", so I know that if I'm using a JDK version earlier that 1.1, I won't have that class.
Is there some similar information for Oracle procedures/ functions/ features/ etc?

>
Let me be more explicit. I've searched for xmlserialize function.
The only place on the website that holds information regarding this function is this page:
>
To paraphrase sybrand - that's utter nonsense. I have never found only one reference to anything on the web.
Your question subject is
>
how can i check if a procedure exists in a certain database version
>
And since you said you were using 10.1 I searched for
>
oracle 10.1 xmlserialize
>
And the very first link on the search results is
>
What's New In Oracle XML DB?
http://docs.oracle.com/cd/B19306_01/appdev.102/b14259/whatsnew.htm
>
That link is for the XML Db Dev Guide for 10g Release 2
Would you like to guess what you find if you search for xmlserialize?
Right on the very first page is this
>
Oracle Database 10g Release 2 (10.2) New Features in Oracle XML DB
SQL/XML Standard Compliance (SQL:2005 Standard Part 14)
Support for the developing SQL/XML standard has been extended. The following SQL functions have been added: XMLPI, XMLComment, XMLRoot, XMLSerialize, XMLCDATA, and XMLParse. Escaping of identifiers has also been updated, in accordance with a change to the SQL/XML standard. See "Generating XML Using SQL Functions".
>
Did you notice the second sentence? I removed the clutter to make it easier to see.
>
The following SQL functions have been added: . . .XMLSerialize. . .
>
Fnding information can't get any easier than that.

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

The SYSVAL table entry for the database version (16) does not match the required version

We upgraded from Tidal Enterprise Scheduler (TES) 5.31 to 6.1 on fresh Windows x64 2008 R2 servers. I did a fresh install but our DBA restored a copy of our database from pre-prod which was at 5.31. I get the error below. Note, SQL went from 2005 to 2012 during this upgrade. Do I need to change a value in this table to reflect the SQL change?
[04/29 12:47:14:198]:TIDAL Enterprise Scheduler: version 6.1.0.133
[04/29 12:47:14:198]:Java version: 1.8.0
[04/29 12:47:14:198]:Java Virtual Machine version: 25.0-b70
[04/29 12:47:14:198]:Start Time : 04/29/14 12:47:14:198
[04/29 12:47:14:198]:----------------------------------------------------------------------------
[04/29 12:47:14:198]:Database URL :jdbc:sqlserver://SQL2012-Host:1433;responseBuffering=adaptive
[04/29 12:47:14:198]:Database Driver :com.microsoft.sqlserver.jdbc.SQLServerDriver
[04/29 12:47:14:198]:Maximum number of log files = 100
[04/29 12:47:14:198]:Added a LogFile called 'RegularFile'
[04/29 12:47:14:198]:LogManager: setting default log
[04/29 12:47:14:214]:Retrieved a LogFile called 'RegularFile'
[04/29 12:47:14:495]:MessageBroker: Instantiated TcpTransportServer (URI = tcp://0.0.0.0:6215)
[04/29 12:47:16:975]:Retrieved a LogFile called 'RegularFile'
[04/29 12:47:17:272]:The SYSVAL table entry for the database version (16) does not match the required version (23). Shutting down.
[04/29 12:47:20:282]:
[04/29 12:47:20:282]:
[04/29 12:47:20:282]:Shutting down the application

I had this error last night while applying a patch to 6.0. However in my case the version was 21 versus a required version of 23.
As far as i know 6.1 is not compatible with the 5 db schema, so you will need an update / migration plan for the db also.

Best way to update DR database from PROD server automatic ?

Hello Gurus,
I want to decide best solution.
Goal: Best way to update DR Database from PROD Server Database automatic.
System: 32 bit Linux system with Oracle Database 10g Release 10.2.0.4.0 - Production (database version) Oracle version is standard.
Please let me know how i can update my DR server with PROD data and this task should be automatic.
Please ask me more information if required to solve this issue.
Thanks- Priyank
Edited by: Oracle DBA P on Nov 19, 2010 3:06 AM

you mean to say data guard needs to implement ? i think that's one option but what you said is different ?
tell me procedure how i can implement your idea ? steps i have to perform.
Thanks
Edited by: Oracle DBA P on Nov 19, 2010 3:38 AM

Alter table script for wrong database version

When we generate an alter table script by connecting to a database, the scripts that get generated are for database version 7.3.
Furthermore we cannot update the field "oracle version" for the database we created.
When we choose a database version from the pulldown box and try to save it, the field is blank again.
We are on Designer 9 on a oracle 10g database and we try to alter the table in a oracle 10g database.

I had this error last night while applying a patch to 6.0. However in my case the version was 21 versus a required version of 23.
As far as i know 6.1 is not compatible with the 5 db schema, so you will need an update / migration plan for the db also.

Update to process version 2010 & smart collection "has adjustments"

Buying the new Lightroom 3 version ofcourse I wanted to profit of the new process version. So I selected all images I had "not adjusted" before and selected Update to Process version 2010. This works great.
However I now have one problem.
I had and have a Smart collection which helps me in my workflow to find all images that have not been touched, so have no adjustments.
This Smart collection has become worthless because of the update to process version 2010 all images have been adjusted.
Ok, this is correct and yet I miss my ability to select images which I have not adjusted.
Once I have set the default process version to 2010 all new images are correctly shown.
Question: how can I select all those images which have only the process version updated, but have no further adjustments?

Changing the process to version 2010 is considered as an adjustment; it will appear in the photo's history in the same way as any other development adjustment. The smart filter condition "Has Adjustments" only has a true or false setting so you can't distinguish the process version adjustment from any other. Instead of using this method to spot the photos I need to work on, I find that I have more control over my workflow by using keywords such as "review", "develop", "print"; you can make these keywords not exportable so that they are not part of the keyword list in exported photos.
Interestingly, when one or more photos are selected in the film strip and the reset button is clicked in develop mode the photo will revert back to its original state, the "Has Adjustments" condition will become false, but the process version will remain at 2010.
If you have a backup of your catalog that precedes the step where you updated the process version of all photos, open this backup, add a keyword of your choice to all the photos that have not been touched, then apply the process version change. You can then change your smart catalog to use this keyword as opposed to the "Has Adjustment" condition and remove the keyword you have set on photos that have not been touched as soon as you are done editing them. IMPORTANT: Any changes you have made following the date and time of the backup will be lost.
If you don't have a backup to go to, you will have to manually identify which photos, which from your point of view, have not been touched.
Some ideas:
If you did not make other edits following the change of the process version, and have not made other edits on that date, you could built a smart collection based on the 'Edit Date" and then reset the develop settings of all the photos in that collection.
Another possible condition is a "Capture Date" range where you know photos haven't been touched yet.
There may be other options, there may be a plugin that can help you, or ultimately there would be means to access the database outside of Lightroom - contact me if you get that desperate to fix this!
http://www.BDLImagery.com

Database version discrepancy...

If I check the properties of my post office in Console One, it says
database version is 12. If I check the configuration through the web
console, it says database version is 8. Why the discrepancy? How do
I fix it?
Thanks,
Ken

Originally Posted by dzanre
KeN Etter wrote:
> I'll try to get a 2012 client installed soon, just to verify. Thanks.
I'd be really surprised if it's not - ConsoleOne reads directly from the
database. The HTTP agents extrapolate their info from XML - so it's likely that
there was a bug with that for the version number.
Danita
Novell Knowledge Partner
Get Healthy with Danita
Which could be from upgrading the agents (inplace) but not running the agent configuration bit? Not sure which version references exactly get updated when running configure agents on an existing server.
-Willem

Application Database Version of HRMS8.9

In the [PeopleTools 8.49 Installation Guide for Oracle|http://download.oracle.com/docs/cd/E05406_01/psft/acrobat/hwtools849_itora.pdf] - Task 7A-4: Updating Database to Latest PeopleTools Release - page 124 - it is said the Application database version of HRMS8.9 is Peopletoos 8.46.
In the [PeopleTools 8.48 Installation Guide for Oracle|http://download.oracle.com/docs/cd/B31343_01/psft/acrobat/itools848_062706_itora.pdf] - Task 7A-4: Updating Database to Latest PeopleTools Release - page 125 - it is said the Application database version of HRMS8.9 is Peopletoos 8.45.
Where is the true ?
Nicolas.
Edited by: N. Gasparotto on Oct 4, 2008 10:58 PM

BI Beans uses a different JAR files to those that ship with Oracle 9iAS. In order to deploy an application built with BI Beans on the same machine as Oracle 9iAS, you must first create a separate instance of OC4J
See...
Setting up a separate OC4J instance in Oracle9i Application Server on Windows/Unix for BI Beans Deployment
On...
http://otn.oracle.com/docs/products/bib/content.html

Patch Set Updates and the version number

Oracle document 854428.1, Patch Set Updates (PSUs) for Oracle Products, has this to say about the version number:
2.3 Baseline Version for Easier Tracking
Oracle associates a version number to the patch. The fifth number of the database version is incremented for each PSU. For example, the initial PSU is version 11.1.0.7.1, the second PSU for Release 11.1.0.7 is 11.1.0.7.2, and so on.
My DBAs just told me that they applied PSU3 to our database, which had version number 11.2.0.2.0. I checked the version number after the PSU was applied, but it is still the same:
SQL> select version from v$instance;
VERSION
11.2.0.2.0
Do the PSUs change the fifth number in the version or not?

SQL> select comments from sys.registry$history where action_time > sysdate - 1
COMMENTS
PSU 11.2.0.2.3
Thankyou, that answers my question. The fifth number in the version column of the v$instance view does not seem to change when a PSU is applied. However, the sys.registry$history view has a record of the PSU with the correct fifth number in the version.

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!!

Update poa database version to 1400

Similar Messages

Maybe you are looking for