9i Database Problem

[Ablakios]

Hi
We created an Oracle 9i database and deployed our reporting application on it. Our vendor insisted to install 8.0.5 client on the server as their application still use 8.0.5 client. Since then, connecting SYS OR SYSTEM is a problem.
From the DOS prompt
SQLPLUS/NOLOG
(You will see another DOS prompt window opened with

SQL*Plus: Release 8.0.5.0.0 - Production on Thu Mar 11 14:10:57 2004

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

SQL*Plus: Release 8.0.5.0.0 - Production on Thu Mar 11 14:10:57 2004

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

SQL> connect sys/*******@vault as sysdba
ERROR:
ORA-01031: insufficient privileges


Or
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>set ORACLE_SID=vault
C:\set ORACLE_HOME=c:\oracle9i

CONNECT SYS/*****@vault AS SYSDBA

and still unable to connect with the 9i TNSNAMES.ORA. but you can connect with 8.0.5 as the application owner.

Any idea.

[nagarjuna]

check out your sqlnet.ora file and uncomment the "SQLNET.AUTHENTICATION_SERVICES" parameter

[kausik_m123]

Hi Nagarjuna,
Can u just clarify how does this parameter affect our connection. This is just for my information. U can also provide me with some links explaining this...
Thanks
Kaushik

[Ablakios]

Naga
I have uncommented the SQLNET.AUTHENTICATION_SERVICES and still unable to connect as SYS
Maybe if I use ORADIM to recreate the PWD file I might be able to. but I am skeptical about that 8.0.0 client install on the 9i Server

[Ablakios]

Anybody to suggest a solution to this?
why should one install 8.0.5.client on 9i database server anyway?

[adewri]

Originally posted by Ablakios
Anybody to suggest a solution to this?
why should one install 8.0.5.client on 9i database server anyway?

I think thats something that you should ask your vendor. Ask them to specify what exactly is their application using that needs Oracle 8.0.5 client and that is not available in Oracle9i client.

[ldanicsk]

Hi,

You can see an init.ora parameter O7_DICTIONARY_ACCESSIBILITY with the default value of FALSE. Switch it to TRUE (the database will restart) and this will solve your problem. I tried it and worked with 8.0.5 client.

details:
http://www.softtreetech.com/cgi_bin/...g.cgi?read=558