User connected as sysdba ?

Dear ORACians,
How do i came to know that a connected user is connected as sysdba previlege?
is there any view ?
urs
selvan

SQL> conn sys@test as sysdba
Enter password: ***
Connected.
SQL> create user a identified by a;
User created.
SQL>
SQL> grant create session to a ;
Grant succeeded.
SQL>
SQL> grant resource to a ;
Grant succeeded.
SQL> conn a/a@test
Connected.
SQL> show user
USER is "A"
SQL> conn sys@test as sysdba
Enter password: ***
Connected.
SQL> grant sysdba to a;
Grant succeeded.
SQL> conn a/a@test as sysdba
Connected.
SQL> show user
USER is "SYS"
SQL>

Similar Messages

How to change password of sys user connected as sysdba?

How to change password of sys user connected as sysdba?
I have connected with user name sys as sysdba in oracle 9i with password oracle.
I want to change the password . I typed password and pressed entered. It asks me to type old password, then new password and retype the new password. When I press enter it gives error message "ERROR:
ORA-28008: invalid old password"
Password unchanged.
does anyone know about this...? how to change the password..?

You may be using operating system authentication to log in as sys with sysdba privileges.
By using password utility, you can change the password of sys user (which is in database) which is "change_on_install" when you create a database.
You can change this password.

Error connecting as sysdba

hi all,
i m using oracle 11g ie 11.1.0.6.0... my OS version is solaris10. The OS got corrupted and was again re-installed...Oracle was installed in different mount point,so there was no problem from oracle side as creating the oracle user and the relevent groups were done.
But when connecting as sysdba ie
sqlplus "/as sysdba" gives
ERROR:
ORA-01031: insufficient privileges
but is able to connect as
sqlplus /nolog
SQL>conn sys/****** as sysdba
connected
this problem is occuring after OS-re-installation

Hi,
Please check if OSDBA operating system group was assigned to O/S user.
http://download.oracle.com/docs/cd/B28359_01/server.111/b28310/dba006.htm#sthref89

Connecting as sysdba returns ORA-01017: invalid username/password

SQL Developer on my Win7 x64 Enterprise machine with Oracle 11gR2 Express was working fine until I tried to install the ODAC connectors so I could use Oracle as a data source for C# and VB in Visual Studio 2010.
The connection properties are:
Connection name "/ as sysdba"
Role "default"
Connection Type "basic"
OS Authentication checked
Hostname "localhost"
Port 1521
SID "orcl"
These are the same as when SQL Developer was working.
If I try to log on to SQL*Plus at the user-name prompt with "/ as sysdba", I get "insufficient privileges".
Where and what do I check to fix this?
Thanks.

>
Where would I check for DOMAIN/USER entries?
select username, authentication_type from dba_users;With the prefix, there should be a database user e.g. "OPS$MYDOM\MYUSER" with external identification.
But with Connection type Basic, I assume you would not be able to connect anyway.
Try type TNS to see if that works or changes anything. (That is, if corresponding db user exists for OS authentication.)
Do you have a requirement to use OS authentication? Could you instead use a database user with a password, i.e. uncheck OS Authentication in SQL Developer?
The connections in SQL Developer are the Auto-Generated Local Connections:
/ as sysdbaI've found a few quirks in SQL Developer 3.0.04 with the auto-generated connection named "/ as sysdba". But right now I don't see that its relevant to this case.
Just create your own connection instead. If you need sysdba administrative connection, change Role in connection properties.
>
By the way, the password for SYSMAN will expire in 5 days. How do I update the password?You should separate questions in separate threads and related forums, but lookup the ALTER USER command in the SQL Reference book.
Edited by: orafad on Dec 4, 2011 11:47 PM
Edit:
parenthesis about os auth part
Edited by: orafad on Dec 6, 2011 1:29 AM

Problem connecting as sysdba ....

Hi,
I'm going to manually create manually a database on Windows 2005 server. I have already installed successfully the DB software.
Having set the ORACLE_HOME , ORACLE_SID and created the oradim i 'm trying to connect as sysdba...but the error ORA-01031 is appeared....
SQL> conn /as sysdba
I defined the Administrator user to the ORA_DBA group and tried the above but the same problem insists.....
What may be the reason ...??? Do i have to restart the server after setting the Administrator user to the ORA_DBA group....???
Note: I use Ora Db10g. v.2
Thanks a lot
Sim

Hi,
this line already exists in the file sqlnet.ora... Anyway , i noticed that when i issue the command:
c:>oradim -new -sid orcl -startmode auto -pfile d:\.......\.....initorcl.ora
Instance created.
DIM-00019: create service error.
O/S - Error: (OS 1376) the specified local group does not exit
In fact , the service is created in manual mode. When i press the button start ,in the services window, this service is started .. without any error message.
But when i try SQL>conn /as sysdba ... the error insists (ORA-01031).
Note: I ' m connected as Administrator. I have assigned the Administrator to the ORA_DBA group . I have not restart the system after the assign...
Thanks,
Sim

Connecting as sysdba in OEM

I can connect as sysdba fine through sqlplus.
I can not connect as sysdba using OEM, the famous
'ORA-01031 - insufficient privileges' appears.
What has to be setup to allow 'system' to sign on
to a database using OEM? (Oracle 8.1.6)
Thanks.

Jerry,
If your administrators will be using the OEM console, they do not need to be defined in the database password file. You can get them sysdba prvileges in a database known by OEM by having them access it as a already defined sysdba user.
1. In the OEM console, there is an option called "Manage Administrators" under the "System" menu at the top of the console window. I don't have my server up, but I think I have this right.
2. Define your user as administrator here.
3. When they attempt to access a database from the console, they will be asked how they wish to connect.
4. Have them enter the username/password of a user already defined in that database with sysdba prvileges.
5. Have them select "sysdba" in the "connect as" box.
6. Have them check the save as prefered profile or something like that. ** This one is optional. **
7. Finish connecting to the database.
This way, they don't have to be defined in each database password file and are all managed from the OEM console.
HTH
Al

How connect as SYSDBA after installation

Hello,
i have oracle 10g, windows xp both fresh installation.
After i installed oracle i want use the iSQL*Plus DBA url and Enterprise Manager Database Control URL to connect as SYSDBA, my instllation was basic= i set pass for all sys user. Sysem user works fine but sysdba doesnt work: Your username and/or password are invalid.
I am member of ora_dba group. If it is not possible connect as sysdba using iSQL*Plus DBA what is the best way connect as sysdba?
Thnx.
Message was edited by:
user503518

To set up iSQLPlus for SYSDBA capability, you want to read Chapter 2 & 3 of the SQLPlus Reference manual. It provides step by step instructions. http://www.oracle.com/pls/db102/portal.portal_db?selected=3
Note - the SQLPlus manual, not the SQL manual

How can I find exact username if I connected with sysdba privilege?

I granted sysdba privilge to a database user. I can connect that user as sysdba. From that users session, 'show user' command showing "SYS" and also username from v$session is also showing "SYS". How can I find actual username used for connecting the database as sysdba?
Steve Abraham

user10247588 wrote:
Thanks for the replay..
But my requirement is that in our production system auditors want to give separate username for each administrators (they are not recommending sys and system).
Normal dba privilege is not a problem. But for sysdba privilege every users are showing the user "SYS". How we can I identify which user is login to the database for a particular work if they connected as sysdba. How can I find which user did that (not just want the username "SYS", because all the administrators are identified by sys if they are connected as sysdba). If auditing is enabled how can I find the exact username. Because we are planning to give sysdba privilege to some of the administrators.
Also, is there any option to find the username, if one user is initiate shutdown of the database?First Please close the thread and keep questioning in only one thread.
then do not connect as sysdba

Setting password while connecting as sysdba

dear DBA experts,
how do we set password for sysdba while connecting to database.since we dont have password while connecting as sysdba.pls help me out...pls give me some steps ........
thanks n regards
aryan

The password for the sys user is already set at the time of the database creation and is stored in the password file , available at the *$oracle_home/dbs* (on Linux) platforms. But this file is not used and is bypassed if the o/s user, mostly oracle , is a part of a group called dba group. So if you want the password file to be used, simplest would be to remove the user Oracle from the dba group.
HTH
Aman....

Getting "ORA-12534: TNS:operation not supported" connecting as sysdba

Hi,
We are getting "ORA-12534: TNS:operation not supported" error, while connecting as sysdba.
bash-2.03$ sqlplus '/as sysdba'
SQL*Plus: Release 10.2.0.4.0 - Production on Thu Feb 23 10:16:16 2012
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
ERROR:
ORA-12534: TNS:operation not supported
Enter user-name:
I can able to connect to database using tns entry without any issue.
SQLNET.ORA Contents:
====================
bash-2.03$ cat /var/opt/oracle/sqlnet.ora
ENCRYPTION_WALLET_LOCATION=(SOURCE=(METHOD=FILE)(METHOD_DATA=(DIRECTORY=/dboracle/orabase/product/10.2.0/dbs/wallet/)))
SQLNET.WALLET_OVERRIDE = TRUE
SSL_CLIENT_AUTHENTICATION = FALSE
SSL_VERSION = 0
I am not aware of wallet. Please help me out to resolve this issue.
Thank you.
Regards,
Dasarath

>
SQLNET.ORA Contents:
====================
bash-2.03$ cat /var/opt/oracle/sqlnet.ora
ENCRYPTION_WALLET_LOCATION=(SOURCE=(METHOD=FILE)(METHOD_DATA=(DIRECTORY=/dboracle/orabase/product/10.2.0/dbs/wallet/)))
SQLNET.WALLET_OVERRIDE = TRUE
SSL_CLIENT_AUTHENTICATION = FALSE
SSL_VERSION = 0
>
You may want to replace ENCRYPTION_WALLET_LOCATION keyword with just WALLET_LOCATION in your sqlnet.ora file.
EWL is used only for TDE but if you want to use external password store, you will have to use WALLET_LOCATION rather than ENCRYPTION_WALLET_LOCATION. However if you are going to use both TDE and external password respository, then make sure your sqlnet.ora file has both entries ENCRYPTION_WALLET_LOCATION as well as WALLET_LOCATION
Regards
Venkat

Compile all invalid packages together + connect as sysdba only

Hi
I've installed a Ora 10.2, and imported a dump. This dump contained some users, a lot of tables and stored procs.
My first question: There is an imported user with I can connect as sysdba only. I can't connect as normal... it is problem because there is an application upper the db and I can't tell the applicataion that connect as sysdba. (it is only a sandbox for me...) What should I modify on this user to connect as normal user?
The second question: The schema (upper) contains lot of invalid packages. I have only the free Toad and I can't compile all of them only step by step... (I don't want do this step by step because there are about 300 packages...). How could I complile all of them e.g. from Sqlplus? Any other solution?
Thanks in advance!
Alex

ok, there is a user e.g. "xxxx"
I can connect with this user as sysdba only. "CONNECT xxxx/yyyy@db as sysdba". Without "as sysdba" I got "ORA-01017: invalid username/password; logon denied" So I can connect only as sysdba... but this is a simple user so I don't want to connect as sysdba...

Please Help with ORA-01031 - try to connect as sysdba

The log of the error is as follows:
D:\oracle\product\10.1.0\Db_ra>set oracle_sid
Environment variable oracle_sid not defined
D:\oracle\product\10.1.0\Db_ra>set oracle_sid=ra
D:\oracle\product\10.1.0\Db_ra>connect "/ as sysdba"
'connect' is not recognized as an internal or external command,
operable program or batch file.
D:\oracle\product\10.1.0\Db_ra>sqlplus "/ as sysdba"
SQL*Plus: Release 9.0.1.4.0 - Production on Mon Aug 29 12:31:17 2005
(c) Copyright 2001 Oracle Corporation. All rights reserved.
ERROR:
ORA-01031: insufficient privileges
Enter user-name: sys@ra as sysdba
Enter password:
Connected to an idle instance.
SQL> shutdown immediate;
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SQL> startup;
ORACLE instance started.
Total System Global Area 612368384 bytes
Fixed Size 790096 bytes
Variable Size 170127792 bytes
Database Buffers 440401920 bytes
Redo Buffers 1048576 bytes
Database mounted.
ORA-01092: ORACLE instance terminated. Disconnection forced
I have been trying to work this out, but no success, Thanks in advance for your help.
JA

some part of the alert.log:
Instance terminated by USER, pid = 1212
ORA-1092 signalled during: ALTER DATABASE open ...
Dump file d:\oracle\product\10.1.0\admin\ra\bdump\alert_ra.log
Mon Aug 29 16:40:06 2005
ORACLE V10.1.0.2.0 - Production vsnsta=0
vsnsql=13 vsnxtr=3
Windows Server 2003 Version V5.2 Service Pack 1
CPU : 4 - type 586, 2 Physical Cores
Process Affinity: 0x00000000
Memory (A/P) : PH:3794M/4094M, PG:5823M/5973M, VA:1960M/2047M
Mon Aug 29 16:40:06 2005
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
KCCDEBUG_LEVEL = 0
Autotune of undo retention is turned on.
Dynamic strands is set to TRUE
Running with 2 shared and 18 private strand(s). Zero-copy redo is FALSE
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 10.1.0.2.0.
System parameters with non-default values:
processes = 150
__shared_pool_size = 159383552
__large_pool_size = 4194304
__java_pool_size = 4194304
sga_target = 612368384
control_files = D:\ORACLE\PRODUCT\10.1.0\RA\U02\ORADATA\RA\CONTROLFILE\O1_MF_1GHVSHLJ_.CTL, D:\ORACLE\PRODUCT\10.1.0\RA\U03\ORADATA\RA\CONTROLFILE\O1_MF_1GHVSHNZ_.CTL
db_block_size = 8192
__db_cache_size = 440401920
compatible = 10.1.0.2.0
log_archive_dest_1 = LOCATION=D:\oracle\product\10.1.0\ra\flash_recovery_area
log_archive_format = ARC%S_%R.%T
db_file_multiblock_read_count= 8
db_create_file_dest = D:\oracle\product\10.1.0\ra\u01\oradata
db_create_online_log_dest_1= D:\oracle\product\10.1.0\ra\u02\oradata
db_create_online_log_dest_2= D:\oracle\product\10.1.0\ra\u03\oradata
db_recovery_file_dest = D:\oracle\product\10.1.0\ra\flash_recovery_area
db_recovery_file_dest_size= 10485760000
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain = megatel.hn
dispatchers = (protocol=TCP)
shared_servers = 1
job_queue_processes = 10
background_dump_dest = D:\ORACLE\PRODUCT\10.1.0\ADMIN\RA\BDUMP
user_dump_dest = D:\ORACLE\PRODUCT\10.1.0\ADMIN\RA\UDUMP
core_dump_dest = D:\ORACLE\PRODUCT\10.1.0\ADMIN\RA\CDUMP
sort_area_size = 65536
db_name = ra
open_cursors = 300
pga_aggregate_target = 203423744
MMAN started with pid=3, OS id=1236
RECO started with pid=8, OS id=768
CJQ0 started with pid=9, OS id=1260
Mon Aug 29 16:40:08 2005
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
SMON started with pid=7, OS id=1256
CKPT started with pid=6, OS id=1252
Mon Aug 29 16:40:10 2005
alter database mount exclusive
PMON started with pid=2, OS id=1232
LGWR started with pid=5, OS id=1248
DBW0 started with pid=4, OS id=1244
Mon Aug 29 16:40:13 2005
Controlfile identified with block size 16384
Mon Aug 29 16:40:17 2005
Setting recovery target incarnation to 2
Mon Aug 29 16:40:17 2005
Successful mount of redo thread 1, with mount id 2665279661
Mon Aug 29 16:40:17 2005
Database mounted in Exclusive Mode.
Completed: alter database mount exclusive
Mon Aug 29 16:40:18 2005
alter database open
Mon Aug 29 16:40:18 2005
Beginning crash recovery of 1 threads
attempting to start a parallel recovery with 3 processes
parallel recovery started with 3 processes
Mon Aug 29 16:40:19 2005
Started first pass scan
Log resilvered from block #210 to block #212
Mon Aug 29 16:40:19 2005
Completed first pass scan
210 redo blocks read, 131 data blocks need recovery
Mon Aug 29 16:40:19 2005
Started redo application at
Thread 1: logseq 2213, block 3, scn 0.0
Recovery of Online Redo Log: Thread 1 Group 1 Seq 2213 Reading mem 0
Mem# 0 errs 0: D:\ORACLE\PRODUCT\10.1.0\RA\U02\ORADATA\RA\ONLINELOG\O1_MF_1_1GHVSJOX_.LOG
Mem# 1 errs 0: D:\ORACLE\PRODUCT\10.1.0\RA\U03\ORADATA\RA\ONLINELOG\O1_MF_1_1GHVSJW8_.LOG
Mon Aug 29 16:40:20 2005
Completed redo application
Mon Aug 29 16:40:20 2005
Completed crash recovery at
Thread 1: logseq 2213, block 213, scn 0.8340211
131 data blocks read, 131 data blocks written, 210 redo blocks read
Mon Aug 29 16:40:21 2005
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=15, OS id=2064
ARC0: Archival started
Mon Aug 29 16:40:21 2005
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=16, OS id=2076
ARC1: Archival started
Mon Aug 29 16:40:21 2005
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Mon Aug 29 16:40:21 2005
ARC1: Becoming the heartbeat ARCH
Mon Aug 29 16:40:21 2005
LGWR: Primary database is in CLUSTER CONSISTENT mode
Thread 1 advanced to log sequence 2214
Maximum redo generation record size = 120832 bytes
Maximum redo generation change vector size = 116476 bytes
Private_strands 7 at log switch
Thread 1 opened at log sequence 2214
Current log# 2 seq# 2214 mem# 0: D:\ORACLE\PRODUCT\10.1.0\RA\U02\ORADATA\RA\ONLINELOG\O1_MF_2_1GHVSK69_.LOG
Current log# 2 seq# 2214 mem# 1: D:\ORACLE\PRODUCT\10.1.0\RA\U03\ORADATA\RA\ONLINELOG\O1_MF_2_1GHVSKF3_.LOG
Successful open of redo thread 1
Mon Aug 29 16:40:21 2005
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Aug 29 16:40:21 2005
ARC0: Evaluating archive log 1 thread 1 sequence 2213
Mon Aug 29 16:40:21 2005
ARC1: Evaluating archive log 1 thread 1 sequence 2213
ARC1: Unable to archive log 1 thread 1 sequence 2213
Log actively being archived by another process
ARC1: Evaluating archive log 1 thread 1 sequence 2213
Mon Aug 29 16:40:22 2005
SMON: enabling cache recovery
Mon Aug 29 16:40:22 2005
ARC1: Unable to archive log 1 thread 1 sequence 2213
Log actively being archived by another process
ARC1: Evaluating archive log 1 thread 1 sequence 2213
ARC1: Unable to archive log 1 thread 1 sequence 2213
Log actively being archived by another process
Mon Aug 29 16:40:22 2005
Committing creation of archivelog 'D:\ORACLE\PRODUCT\10.1.0\RA\FLASH_RECOVERY_AREA\ARC02213_0564762704.001'
Mon Aug 29 16:40:23 2005
Successfully onlined Undo Tablespace 1.
Mon Aug 29 16:40:23 2005
SMON: enabling tx recovery
Mon Aug 29 16:40:23 2005
Database Characterset is WE8MSWIN1252
Mon Aug 29 16:40:23 2005
Published database character set on system events channel
Mon Aug 29 16:40:23 2005
All processes have switched to database character set
Mon Aug 29 16:40:25 2005
Starting background process QMNC
QMNC started with pid=17, OS id=2152
Mon Aug 29 16:40:27 2005
replication_dependency_tracking turned off (no async multimaster replication found)
Mon Aug 29 16:40:28 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\udump\ra_ora_1304.trc:
ORA-00600: internal error code, arguments: [kksfbc-reparse-infinite-loop], [], [], [], [], [], [], []
Mon Aug 29 16:40:30 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\udump\ra_ora_1304.trc:
ORA-00600: internal error code, arguments: [kksfbc-reparse-infinite-loop], [], [], [], [], [], [], []
Mon Aug 29 16:40:31 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\udump\ra_ora_1304.trc:
ORA-00600: internal error code, arguments: [kksfbc-reparse-infinite-loop], [], [], [], [], [], [], []
Mon Aug 29 16:40:32 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\udump\ra_ora_1304.trc:
ORA-00600: internal error code, arguments: [kksfbc-reparse-infinite-loop], [], [], [], [], [], [], []
Error 600 happened during db open, shutting down database
USER: terminating instance due to error 600
Mon Aug 29 16:40:33 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\bdump\ra_mman_1236.trc:
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
Mon Aug 29 16:40:33 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\bdump\ra_p002_1984.trc:
ORA-00600: internal error code, arguments: [15784], [600], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
Mon Aug 29 16:40:33 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\bdump\ra_p001_1980.trc:
ORA-00600: internal error code, arguments: [15784], [600], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
Mon Aug 29 16:40:33 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\bdump\ra_p000_1568.trc:
ORA-00600: internal error code, arguments: [15784], [600], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
Mon Aug 29 16:40:33 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\bdump\ra_reco_768.trc:
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
Mon Aug 29 16:40:33 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\bdump\ra_smon_1256.trc:
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
Mon Aug 29 16:40:33 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\bdump\ra_ckpt_1252.trc:
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
Mon Aug 29 16:40:33 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\bdump\ra_lgwr_1248.trc:
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
Mon Aug 29 16:40:34 2005
Errors in file d:\oracle\product\10.1.0\admin\ra\bdump\ra_dbw0_1244.trc:
ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
Instance terminated by USER, pid = 1304
ORA-1092 signalled during: alter database open...

SQL connect /as sysdba;

SQL> connect /as sysdba;
Connected.
what's reason that we can access DB withoug password like that? and what parameter need to adjusted to control this?

This is called OS authentication. It means the OS has positively identified you as a dba, so you are not required to present a password to access the sysdba role.
If you are working on a Windows platform it is enough that two conditions are met, first you must belong to the ORA_DBA privileged group, either the user you use to locally connect or the user to connect through a domain account.
And the parameter SQLNET.AUTHENTICATION_SERVICES= (NTS) at the sqlnet.ora file. If this parameter is commented, you must authenticate using the password.
On a unix platform, you must belong to the privileged group declared at install time. Most frequently it is the dba or oinstall group.
It is only valid if you are logged on the same machine where the ORACLE_HOME resides. Otherwise the use of the password file and the remote_login_passwordfile is required.
~ Madrid.

Trying to connect as sysdba results in ORA-01031

Database server runs in shared server mode,
so in tnsnames I have entry for network service
name with (SERVER = DEDICATED) option to be
able to connect as sysdba, initialization
parameter REMOTE_LOGIN_PASSWORDFILE is set to EXCLUSIVE,
in password file there is one entry for user sys.
I'm trying to connect with user sys as sysdba,
but the result is ORA-01031 error.
Can anybody tell me how can I make it to work?
Thanks for advise a lot,
P.

I have recreated password file,
but it behaves like before, connecting
to database from local machine with
user not in OSDBA or OSOPER group works,
but from other machine it ends with error.
I have one more question: When I connect
from local machine using tnsnames.ora file
in network service name defined in that file
I have (SERVER = SHARED)
and I'm able to connect as sysdba, I thought that
connect as sysdba is possible only with
(SERVER = DEDICATED) when database works in
shared server mode.

Difference between CONNECT and CONNECT As SYSDBA

Hi All,
Can anyone explain me... what is the difference between this two..
SQL> SCOTT/TIGER@my_service;
you get only Scott related objects.
SQL> SCOTT/TIGER@my_service AS SYSDBA;
you get all SYS objects also..
What is happening inside.. how can u allow scott such as ordinary user to login as SYSDBA and giving all datadictionary access..
Thanks in advance

Hi,
This is because of Operating System authentication:test$ id
Here, I am the Oracle software owner, member of the dba group. ORA_DBA on Windows.
uid=103(oracle) gid=103(dba)
test$ sqlplus /nolog
SQL*Plus: Release 9.2.0.7.0 - Production on Ma Fev 7 13:15:47 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
I can connect with whatever user I want. Even if the login doesn't exists. The O.S. authenticates me.
SQL> connect / as sysdba
Connected.
SQL> show user
USER is "SYS"
SQL> connect IDont/Exist as sysdba
Connected.
SQL> show user
USER is "SYS"
SQL> connect / as sysoper
Connected.
SQL> show user
USER is "PUBLIC"
SQL> exit
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.7.0 - Production
test$ su - usernamehidden
Password:
(c)Copyr...
... (1,2).
test> id
Here, the user is member of the DBA group though not being the software owner.
uid=104(usernamehidden) gid=104(groupnamehidden) groups=103(dba)
test> sqlplus /nolog
SQL*Plus: Release 9.2.0.7.0 - Production on Tue Feb 7 13:17:45 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
And I still can connect without Oracle credentials.
SQL>conn / as sysdba
Connected.
SQL>exit
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.7.0 - 64bit Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.7.0 - Production
test>
logout...
test$ su -
Password:
(c)Copyr...
... (1,2).
You have mail.
Value of TERM has been set to "vt100".
WARNING: YOU ARE SUPERUSER !!
# id
User root is not in O.S. group DBA
uid=0(root) gid=3(groupnamehidden) groups=0(groupnamehidden),1(groupnamehidden),2(groupnamehidden),4(groupnamehidden),5(groupnamehidden),6(groupnamehidden),7(groupnamehidden),20(groupnamehidden)
# export ORACLE_HOME=/opt/oracle/Ora9i
# export ORACLE_SID=TEST
# export PATH=$PATH:$ORACLE_HOME/bin
# sqlplus /nolog
SQL*Plus: Release 9.2.0.7.0 - Production on Tue Feb 7 13:26:41 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Hence O.S. user root must provide valid Oracle credentials in order to connect as sysdba.
SQL>conn / as sysdba
ERROR:
ORA-01031: insufficient privileges
SQL>conn sys/invalidpassword as sysdba
ERROR:
ORA-01031: insufficient privileges
SQL>conn sys as sysdba
Enter password:
Connected.This is all writen somewhere in TFM. Check it for further info.
Regards,
Yoann.

User connected as sysdba ?

Similar Messages

Maybe you are looking for