Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: If anyone should bother

Re: If anyone should bother

From: Sybrand Bakker <postmaster_at_sybrandb.demon.nl>
Date: Mon, 27 Dec 1999 14:06:53 +0100
Message-ID: <946300083.26395.0.pluto.d4ee154e@news.demon.nl>


Most likely both problems have to do with an incorrect setting of the parameter remote_login_passwordfile.
If you want to be able use sysdba for sys the parameter needs to be set to shared.
If you want to be able to grant sysdba to any user it needs to be set to exclusive.
You can change the parameter by modifying (or adding) it in %ORACLE_HOME%\database\init%ORACLE_SID%.ora

Please note : sysdba is a very powerful privilege, I would use sysoper for 'normal' cases. sysoper can do anything except creating a database.

Hth,

--
Sybrand Bakker, Oracle DBA
news <john_at_someplace.com> wrote in message news:38673274.0_at_news.pacifier.com...
> Just playing with it. Installed trial version of O8i. Absolutelly new to
> databases.
> os: win2000 workstation
>
> problems:
>
> 1. neither sys or system default users can grant sysdba privilege to
> whatever 'new_user'.
> 2. neither sys or system default users can startup || mount database
created
> at install time. Note that both sys and system users have been added to
the
> os users list with the corresponding database privileges. Also the Oracle
> Administration Assistant for NT has been configured for that purpose.
>
> Just spent a weekend on this DB. Anyone can help? Thanks.
>
>
>
Received on Mon Dec 27 1999 - 07:06:53 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US