Run this query and see what dbVersion is returned:
select dbVersion from control
- Vivake
On 10/24/06, McKenzie, James J C-E LCMC HQISEC/L3
<[EMAIL PROTECTED]> wrote:
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C6F795.31DCF5B0
Content-Type: text/plain
David:
I did find one thing. Can you connect via SQL*Plus to the Oracle Database
from within the 10g client directory? I had to install two packages that
were not originally installed on my server. The Client should not have
installed without them.
James McKenzie
L-3 GSI
________________________________
From: Action Request System discussion list(ARSList)
[mailto:[email protected] ] On Behalf Of David Yearsley
Sent: Tuesday, October 24, 2006 10:30 AM
To: [email protected]
Subject: 7.00.01 on Solaris
**
System Configuration.
Solaris 5.9
Oracle 9i Release 2.
Oracle Client 10.g Release 2
We are trying to upgrade our Remedy Server to 7.00.01 from 6.03.00 Patch 16.
We are reaching the point in the install where it is trying to start the
7.00.01 Server(Stage 4). The startup fails and we get the error message: The
Database is not the expected version (May need to run upgrade program)
(ARError 36). We tried this upgrade last week and remedy had is install the
upgraded Oracle Client, but it appears that this has not solved the problem.
Has anyone had this problem with the upgrade?
Is there a trick to installing 7.00.01 against an Oracle 9.i Release 2
database?
Is there something in the configuration files we need to check/change?
Thanks
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
__20060125_______________________This posting was submitted with HTML in it___
