Re: OEM Console on XP / Connect to 10gR2 server - insufficient privileges

On Dec 5, 4:45 am, jeremy <jeremy0..._at_gmail.com> wrote:
> On 5 Dec, 10:32, "Preston" <dontwant..._at_nowhere.invalid> wrote:
>
>
>
> > When you connect 'as sysdba', you're actually connecting as sys,
> > regardless of which userid you use. So there shouldn't be a need to use
> > system as sysdba. Does it work ok if you use another user with dba
> > privileges?
>

No, it won't, as the mechanism to connect as sysdba has not been enabled by one of the two methods described below.

> > As to what's causing the error, no idea, unless someone's removed the
> > dba role from system.
>

The DBA role still exists, else SYSTEM couldn't connect. So that cannot be the issue.

> Hi Preston
>
> The reason I was using the "as sysdba" option was to see if it would
> provide some extra options - e.g. the "locks" option doesn't appear to
> be enabled logged in as "Normal" (even under user system).
>
> E.g. click on Instance in the navigator on the left of the screen and
> to the right it displays a panel of info titled "Instance management"
> one of the options on which is "Monitor locks, sessions...." -
> clicking on the word "locks" should display (well in 9i OEM console) a
> list of the locks. The "locks" option is also not present in the
> navigator (and was in the 9i version).
>
> So a little puzzled.
>
> cheers
>
> --
> jeremy

The ORA-01031 is generated by one of two things:

• remote_login_passwordfile is set to NONE

or

• remote_login_passwordfile is set to SHARED or EXCLUSIVE and you have no password file generated

Connect as SYSTEM and do this from the SQL> prompt:

show parameter password

See how remote_login_passwordfile is set. If it's set to NONE you'll need to set it to EXCLUSIVE (presuming you're not on a RAC configuration) in the spfile (or your pfile, if you're using that antiquated method of setting parameters). If it's set to EXCLUSIVE you're half way there. You'll then need to generate a password file. At the operating system prompt go to %ORACLE_HOME%\dbs and execute orapwd with the file name (usually 'orapw' prepended to the SID), the SYS password and the number of DBA/SYSDBA entries to allow. For example:

C:\oracle\OraHome\dbs> orapwd file=orapwmysid password=mypass entries=5

Restart your database to pick up the changes to the spfile/pfile, then try your connection from OEM again as SYSDBA. It should now work as expected.

Yes, this is a FAQ and a bit of searching in the newsgroup archives would have found this same answer.

David Fitzjarrell Received on Wed Dec 05 2007 - 07:45:48 CST