Links
Home
Oracle DBA Forum
Frequent Oracle Errors
TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found'>ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated
ORA-01031

ORA-01031

2004-02-16       - By SRIDHARAN, SAN (SBCSI)
Reply:     1     2  

In the OEM Console, if you try to connect to a database, a
logon dialogue window appears. You have a choice of
connecting as 'Normal ', 'Sysdba ', or 'Sysoper '. You can
connect with the user internal as sysdba but NOT sys or system.
When you attempt this, you receive the error:

ORA-1031 (See ORA-1031.ora-code.com) insuffient privileges

Why? How do you set this to work?


Solution Description
-- ---- ---- ---- --

Run svrmgr30 or svrmgrl (depending on version) and logon
as internal and then issue the following:

grant sysdba to system;
(or any user that you want to have the sysdba role).

Then in OEM, for this user that you setup, you can have
the connect as set to SYSDBA by doing the following:

1. Select FILE- >PREFERRENCES from within the OEM Console.
2. Highlight the database and change the role from NORMAL
to either SYSDBA (or SYSOPER).
3. Click APPLY.

The next time you attempt to connect from the OEM applications,
the application will connect as the role you selected.

Note: Before the SYSDBA role can be granted to a user,
the init.ora file must have the parameter
"REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE ". If you have to
modify the init.ora to include this parameter, you will
need to shutdown and restart your instance.


Explanation
-- ---- ---

By default the internal user has the sysdba privilege.
The system and sys do not. Therefore, you need to grant the
sysdba role to the user.

-- --Original Message-- --
From: John P Weatherman [mailto:asahoshi@(protected)]
Sent: Monday, February 16, 2004 1:44 PM
To: oracle-l
Subject: ORA-01031 (See ORA-01031.ora-code.com)


Hi all,
I have a 9.2.0.4 database on Solaris 2.9 that is being very unhappy with
remote connections as sysdba. The owner of the process (sqlplus for
testing, but IA also as I am ultimately trying to get things scheduled with
Enterprise Manager) is the oracle owner which is in the dba group. If I
"connect sys/ <passwd > as sysdba " on the local machine, it works without any
problems. However, when I throw SQL*Net into the mix ( "connect
sys/ <passwd >@ <sid > as sysdba ") I am getting an ORA-1031 (See ORA-1031.ora-code.com). I have tried
recreating the passwd file and even "resetting " the sys password, just to
make sure the password file is "synchronized " with the actual password (per
a note on google).

Has anyone seen anything like this and have any suggestions?

TIA,
John P Weatherman
Oracle Database Administrator
Advance America

-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --