Solved

Oracle Upgrade issue

Posted on 2009-05-08
12
807 Views
Last Modified: 2013-12-18
I had upgraded oracle databases from 10.2.0.3 to 10.2.0.4.  Everything completed correctly.  Prior to the upgrade the compatibilty parameter was set to 10.2.0.2.  I needed to put back some 'custom' parameters and at the same time changed the compatibily parameter to 10.2.0.
When bringing up the database i received the following error:
ORA-00201: control file version 10.2.0.2.0 incompatible with ORACLE version
10.2.0.0.0    ORA-00202: control file:

I put back the compatibility to 10.2.0.2 and it came up fine.  Any idea as to why this error occurred?
0
Comment
Question by:sqlnewbie08
  • 4
  • 3
  • 3
  • +1
12 Comments
 
LVL 40

Expert Comment

by:mrjoltcola
ID: 24336501
You cannot change it backwards, on the fly like that. You must set it prior to creating a database.

The compatibility param controls what Oracle can not only support in the instance, but also what it writes to disk, and it is the disk that is important in this case, it tracks it in the control file as well. Once the database is created, you cannot go backwards because Oracle might have written structures to disk that are incompatibile.

You can move it forward, but not backwards, without an export and import.
0
 
LVL 47

Expert Comment

by:schwertner
ID: 24336507
10.2.0.
is not a legal Oracle version
0
 

Author Comment

by:sqlnewbie08
ID: 24336696
The compatible parameter in our production databases is set to: '10.2.0', which based on documentation is valid.

I was upgrading an existing database from 10.2.0.3 to 10.2.0.4.  The database prior to the upgrade had compatible set to 10.2.0.2.  Afterwards, in order to gain the functionality of the new version, changed it to 10.2.0     That's when the error occurred.
0
 
LVL 34

Expert Comment

by:johnsone
ID: 24336877
10.2.0 is less than 10.2.0.2.  As stated already, you cannot go backward.  To get all the functionality possible, compatible should be set to the database version, 10.2.0.4.
0
 

Author Comment

by:sqlnewbie08
ID: 24336907
Ok.. then why in our production envirnment is 10.2.0 working when the version is 10.2.0.3... just a little confused.  thanks!
0
 
LVL 34

Expert Comment

by:johnsone
ID: 24336923
Did you change your it from 10.2.0.2 to 10.2.0 in production?
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 40

Expert Comment

by:mrjoltcola
ID: 24337038
>>then why in our production envirnment is 10.2.0 working when the version is 10.2.0.3..

Likely because it was 10.2.0 when you created your database, or either it was previously an even earlier version (8i or 9i perhaps) that was also upgraded and set to 10.2.0

Just because it runs with 10.2.0 in production is irrelevant, what is relevant is that you _changed_ a later version to 10.2.0.

The use of the compatible parameter is clear, it directs Oracle to or not to make use of certain features as well as _disk structures_ based on compatibility, so by definition moving _backwards_ is a problem, just like trying to open a 10.2.0.4 database with a 10.1.0 binary is also a problem.
0
 

Author Comment

by:sqlnewbie08
ID: 24338229
Regarding production... yes it was an earlier version 9i, that was upgraded to 10g.  I apparently misunderstood the setting.  I was understood it that 10.2.0 would apply to all versions and not that it would be 'downgraded' version.  So, bottom-line, change it to 10.2.0.4 to match the version that is running to get use of any new features...
0
 
LVL 40

Expert Comment

by:mrjoltcola
ID: 24338308
I typically never set it except at database creation, or major version upgrade. Not during patches, so I recommend you leave it as it was.
0
 
LVL 34

Accepted Solution

by:
johnsone earned 500 total points
ID: 24338431
Personally, I set it to whatever version of the database is running.  In your case, I would set it to 10.2.0.4.
0
 
LVL 47

Expert Comment

by:schwertner
ID: 24339206
Mr. johnsone is absolutly correct.
This parameter is set only when you expect version conflicts
with some components and would like the installation to
function like the version you mention.
But I do not have evidence you need something like this.
There are more then 300 init parameters, but we change only a couple of them
and do major changes when we need to change the behavior of the DB.
0
 

Author Closing Comment

by:sqlnewbie08
ID: 31579445
thank you
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Article by: Swadhin
From the Oracle SQL Reference (http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/queries006.htm) we are told that a join is a query that combines rows from two or more tables, views, or materialized views. This article provides a glimps…
Using SQL Scripts we can save all the SQL queries as files that we use very frequently on our database later point of time. This is one of the feature present under SQL Workshop in Oracle Application Express.
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.
This video shows how to recover a database from a user managed backup

920 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now