8.1.7 Error

[dbadmin]

Hi Gurus,

This issue is eating my brain, but nothing seems to solve the problem. This is what I have and I did.

I have two HP-UX machines and one had Oracle 8i (8.1.7) installed with 4 databases running on it. I can do startup/shutdown etc on this machine without any issues.

Instead of installing Oracle on the second machine, I copied the Oracle install folders and files to the second machine. I did a file compare and everything is same. Now the problem starts. When I do the following after setting ORACLE_HOME and ORACLE_SID env variables

For the first two databases, I get the following message

sqlplus /nolog
SQL*Plus: Release 8.1.7.0.0 - Production on Wed Apr 25 08:51:15 2007

(c) Copyright 2000 Oracle Corporation.  All rights reserved.

connect / as sysdba
Connected to an idle instance.

After getting this message, I could start the database.

For the last two databases I am getting as below

sqlplus /nolog

SQL*Plus: Release 8.1.7.0.0 - Production on Wed Apr 25 08:54:35 2007

(c) Copyright 2000 Oracle Corporation.  All rights reserved.

connect / as sysdba
ERROR:
ORA-01096: program version (8.1.7.2.0) incompatible with instance (8.1.7.0.0)

Why I am getting this error only for the last two databases?

I tried relinking the executables as suggested in one of the Oracle metalink notes and nothing seems to help. Any one out there who had similar issues or could suggest a solution.

Thanks,
dbadmin

 

[hoinz]

Not sure if I understood what you did; so please correct me if I am wrong!

But I guess the problem is this:
You have four databases with four ORACLE_HOME and four sets of datafiles on machine1.
You think that they all have the same version 8.1.7. But actually two of them have 8.1.7.0.0 and the other two have 8.1.7.2.0
Btw, if the databases on machine1 are still available, you may verify it by:
select * from v$version;

So you copied all four databases to machine2, correct?
And for convience, you used the same ORACLE_HOME as the source for all 4 systems, did you?
This should work, if versions were the same...

And what can you do now?
Either copy the correct version of ORACLE_HOME.
Or run an upgrade of your 8.1.7.0.0 databases, to raise them to 8.1.7.2.0
(A long time has passed since I did something like that for Oracle 8i; I remember calling 'startup migrate', but not sure about the details.)

hope this helps

 

[dbadmin]

Hi Hoinz,

Thanks for the reply. All you said is correct. I copied the ORACLE_HOME and the database files to machine 2 for all the 4 databases. Only 2 of them I could connect as SYSDBA and startup. I checked the versions when the databases were on MACHINE1. The output shows this

DB1

sqlplus /nolog

SQL*Plus: Release 8.1.7.0.0 - Production on Thu Apr 26 05:32:26 2007

(c) Copyright 2000 Oracle Corporation.  All rights reserved.

SQL> connect / as sysdba
Connected.
SQL> select * from v$version;

BANNER
----------------------------------------------------------------
Oracle8i Enterprise Edition Release 8.1.7.2.0 - 64bit Production
PL/SQL Release 8.1.7.2.0 - Production
CORE    8.1.7.0.0       Production
TNS for HPUX: Version 8.1.7.2.0 - Production
NLSRTL Version 3.4.1.0.0 - Production

DB2

sqlplus /nolog

SQL*Plus: Release 8.1.7.0.0 - Production on Thu Apr 26 05:33:40 2007

(c) Copyright 2000 Oracle Corporation.  All rights reserved.

SQL> connect / as sysdba
Connected.
SQL> select * from v$version;

BANNER
----------------------------------------------------------------
Oracle8i Enterprise Edition Release 8.1.7.2.0 - 64bit Production
PL/SQL Release 8.1.7.2.0 - Production
CORE    8.1.7.0.0       Production
TNS for HPUX: Version 8.1.7.2.0 - Production
NLSRTL Version 3.4.1.0.0 - Production

The versions are same. Another thing I noticed is I can connect as internal on all these databases on MACHINE1 and 2.

Thanks,
dbadmin

 

[hoinz]

Hm...
I am trying to understand what that 'incompatible' means...
My first guess was wrong, obviously.
What do you get from this:
select version from v$instance;

And if you can connect internal, are you able to start all the databases?

Another thing you could check is environment of the Oracle users; there are four of them on each machine, I presume?
It's not just about ORACLE_HOME and ORACLE_SID; there are others like ORA_NLS32 or something like that.

 

[dbadmin]

I was able to resolve this by doing a connect internal and shutdown abort to release the semaphores and then connect as sysdba and startup the databases. Everything is working as normal.

Thank You
dbadmin