Re: Sysdba privileges

From: <sybrandb_at_my-deja.com>
Date: Mon, 11 Dec 2000 08:58:39 GMT
Message-ID: <9124vu$rtc$1@nnrp1.deja.com>

In article <911vm8$oi5$1_at_flis.man.torun.pl>,   "Chmielewski Jacek" <jacekch_at_mail.atr.bydgoszcz.pl> wrote:
> This is the result of select * from v$pwfile_users statment:
>
> USERNAME
> ----------------------------------------------------------------------

---

> ----
> SYSDBA SYSOPER
> --------------- ---------------
> INTERNAL
> TRUE TRUE
>
> SYS
> TRUE TRUE
>
> It seems my sys operator has sysdba, and remote_login_password_file
 is set
> do exclusive.
> But I cannot login as sysdba using sys/change_on_install.
>
> > There shouldn't be any problem in connecting as SYSOPER. The only
 difference
> > is a SYSDBA has the privilege to create a database.
>
> If I am not sysdba I cannot export or import database, and that is
 what I
> need.
> Best regards from Poland
> Jacek
>

1 One common cause for ORA-1031 in this case is the fact the internal password doesn't equal the sys password. To set the internal password use the orapwd utility.
2 Sorry to say so, but your assertion about export is incorrect. You'll need exp_full_database privilege, which any user with the DBA role has.

Best regards,

--
Sybrand Bakker, Oracle DBA

All standard disclaimers apply
------------------------------------------------------------------------


Sent via Deja.com http://www.deja.com/
Before you buy.

Received on Mon Dec 11 2000 - 02:58:39 CST