CONNECT INTERNAL 시 SYS에 PASSWORD 걸기(SYSDBA, SYSOPER)

제품 : ORACLE SERVER
작성날짜 : 1997-03-31
SYS user 에 passwd 거는 방법
===========================
이를 걸게 되면 connect internal 접속 시 passwd를 물어보게 되며 DBA group이
아닌 다른 user에서도 sys user와 똑같이 작업할 수 있다.
1) initSID.ora 화일에
REMOTE_OS_AUTHENT = TRUE
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
2) ?/dbs 에서
orapwd file=orapwSID password=my_password entries=10
(이 때의 SID는 실제의 ORACLE_SID 를 적어주어야 함.)
3) connect internal 후
grant sysdba to scott
grant sysoper to scott 를 부여한다.
이를 부여하면 sys의 passwd를 알지 못해도
SVRMGR> connect internal;
SVRMGR> passwd ? :
만약 passwd 를 모르면
SVRMGR> connect scott/tiger as sysoper ;
SVRMGR> startup 이 가능하다.
참고) 이의 효과를 위해 /etc/group 화일에 oracle os user가 DBA group 이
아니어야 하며 일반 user에서도 위의 작업을 똑같이 실행하려면 configSID.ora
화일을 oracle user 아닌 다른 user에도 실행이 가능할 수 있도록 실행 MODE가
4755 이어야 한다.

If you want to connect a new user as SYSDBA or SYSOPER, you must first create a repository. Check some document for creating a repository with seperate tablespace.

Similar Messages

Getting ORA-01031: Insufficient privileges when connecting as sys as sysdba

Hi There,
I am running Linux AS version 4, oracle 102.0.1, and logginging as oracle user which belongs to dba group. I got error "ORA-01031: Insufficient privileges" when trying to connect as sys user to bring up database. I wondered what is causing the error. Here is an example
oracle-dev>sqlplus /nolog
SQL>conn as sys/oracle@dev as sysdba
ERROR:
ORA-01031: Insufficient privileges
Any suggestions would be greatly appreciated. Thanks again.
Rich,

Did you create a password file ?
http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b15658/admin_ora.htm#sthref142
Message was edited by:
Paul M.
BTW, the syntax is
SQL>conn sys/oracle@dev as sysdba

Sys as sysdba/sysoper

Hi there
Can any body explain me, why SYS user should always connect to the database as SYSDBA/SYSOPER only?
Why he cannot login without as a SYSDBA/SYSOPER.
TIA
Aqueel.

Though you should understand the implications of making this change. Here's the excerpt from the Oracle docs.
"O7_DICTIONARY_ACCESSIBILITY is intended for use when you migrate from Oracle7 to Oracle9i. It controls restrictions on SYSTEM privileges. If the parameter is set to true, access to objects in the SYS schema is allowed (Oracle7 behavior). The default setting of false ensures that system privileges that allow access to objects in "any schema" do not allow access to objects in SYS schema.
For example, if O7_DICTIONARY_ACCESSIBILITY = false, then the SELECT ANY TABLE privilege allows access to views or tables in any schema except the SYS schema (data dictionary tables cannot be accessed). The system privilege EXECUTE ANY PROCEDURE allows access on the procedures in any schema except the SYS schema.
If this parameter is set to false and you need to access objects in the SYS schema, then you must be granted explicit object privilege. Also, the following roles, which can be granted to the database administrator, also allow access to dictionary objects: SELECT_CATALOG_ROLE, EXECUTE_CATALOG_ROLE, and DELETE_CATALOG_ROLE."

Svrmgrl: connect internal requires password after system crash

Please help.
I'm running Oracle 7.3.4 on SunSolaris 2.6.
It seems we had a system crash.
Message when I try to restart the database
with the runscirpt (rtc2.d....)
"Database "SID" possibly left running when system went down (system crash?).
Notify Database Administrator.
Kennwort:
Kennwort:
SVRMGR> ORA-01031: insufficient privileges
SVRMGR> ORA-01031: insufficient privileges
SVRMGR>"
also when I attemting:
svrmgrl connect internal
I'm prompted for a password (Kennwort).
I don't know the password.
I tried it as root and oracle user.
Any suggestions or help?
Thank you.
null

In the password file I set the password of the os
user oracle which owns installation.The Password for the password file is supposed to be the SYS password and not OS User oracle which owns installation.
I do not think the Oracle OS user password change is the problem. When you alter SYS password using the alter user command, it should change the password file automatically.
Try
SVRMGR> connect sys/sys_password as see whether it works. If it does not, then check other issues.

Sys password issue

We have oracle 10.2.0.1 running on Unix
WE didnt set the password of SYS user in oracle but now we would like to set
I use the command alter user sys identified by password
i got message user altered
Now i tried connection to sys/password@abc as sysdba
but no luck
So i created password file by
orapwd file=orapwdhmo password=password entries=2 force=y
file created but again unable to login
and at OS level
if I set
ORACLE_SID=INSTANCE_NAME
export ORACLE_SID
sqlplus / as sysdba
connected
I am able to
Please let me know how to set password for sys

Is this attempt where the db resides, or from a remote client:
sqlplus "sys/password@abc as sysdba"
On the other hand,
ORA-01031: Message 1031 not found; No message file for product=RDBMS,
facility=ORA
unavoidably means you cannot open error message catalog. Reasons are either:
- Incorrect ORACLE_HOME setting
- Incorrect PATH setting
- files have been removed
And this error message issue must first be solved before you pretend to change sys password.
Changing sys password is as follows:
1. Create a password file
2. Make sure your remote_login_password_file says exclusive
3. rebounce your instance
4. change sys password
5. verify your username is listed at the V$PWFILE_USERS dynamic view
7. change user password.
I suggest you to double check.
~ Madrid.

Error ORA-28009: connection as SYS should be as SYSDBA or SYSOPER

hi,
i try to connect to oracle in c#2005. I'm using oralce 10.2.0.3.0 in window vista.
i can connect as user scott , but can't do the same thing with use sys like sysdba. i encouter error :
"ORA-28009: connection as SYS should be as SYSDBA or SYSOPER"
this is my code :
using System;
using System.Data.SqlClient;
using System.Data.OleDb;
namespace ConsoleApplication2
class Program
static void Main(string[] args)
string connectionString = "provider=MSDAORA;data source=ORCL;user id=sys;password=orcl";
OleDbConnection myOleDbConnection = new OleDbConnection(connectionString);
try
myOleDbConnection.Open();
Console.WriteLine("successfull");
Console.ReadLine();
catch (Exception ex)
Console.WriteLine(ex.Message);
Console.Read();
i
i have google about this error and see that some people use Oracle.DataAccess.Client namespace to solve this error. but i cant find this namespace reference.
i want to connect to oracle in c# 2005 as user id = sys.
so , please help me.
thanks

it should be there regardless of the version you installed, go into your GAC and give it a look over (C:\Windows\assembly) the Oracle.** should be there after a successful installation. It is actually in your best interest to get the latest and greatest, the versions are backward compatible (I believe they all work to 9i++)
You can also goto
%ora_home%\odp.net
it will have sample c# and vb applications there
(%ora_home% tends to be c:\oracle\product\#####\Client_1\)
Have a look over the odp.net demos, that may very well put you on the correct track to getting things working.

ORA-28009: connection as SYS should be as SYSDBA or SYSOPER

Porque este erro acontece?
Acontece porque o parâmetro O7_DICTIONARY_ACCESSIBILITY está configurado como FALSE.
Agora vamos ao que interessa, como resolver:
Conecte-se como SYSDBA
SQL> conn / as sysdba
Connected
Agora vamos configurar aquele parâmetro para TRUE
SQL> ALTER SYSTEM SET O7_DICTIONARY_ACCESSIBILITY=TRUE scope=spfile;
System altered.
Agora você pode fechar o DB e abrir novamente, e logar-se como SYS ( SQL> connect sys/passwd@sv ).

http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:940042518290
"My recommendation would be to leave the the O7_DICTIONARY_ACCESSIBILITY set to false and
change scripts that connect as SYS to connect as some other user. Using the SYS account
should be avoided in any case -- you should never use it to create objects, cannot use it
to create triggers and some commands (for example "set transaction read only") don't even
work when connected as SYS.
Consider SYS to be a special account that you never need to use anymore."

Connect as sys user as sysdba using vbscript

Hi I have to connect to the oracle database using sys user as sysdba using a vbscript.
I have the following part in the script:
Const TARGET_CONN = "DRIVER={Microsoft ODBC for Oracle};SERVER=XYZ;UID=sys;PWD=abc;"
Set conn = CreateObject("ADODB.Connection")
conn.Open TARGET_CONN
When i run the script i get the error: connection as SYS should be as SYSDBA or SYSOPER
Does anybody know how to do resolve this?
Thanks in advance.

Hi,
If you were using Oracle's ODBC driver, you'd add "as sysdba" as part of the password, ie:
"DRIVER={oracle in oradb11g_home1};dbq=XYZ;UID=sys;PWD=abc as sysdba;"
However, you're using Microsoft's driver and I wouldnt be surprised if Microsoft's driver doesnt support it. If it does though, I'm not sure what you need to do.
Greg

Connection sys as sysdba

Hi,
Our DB is in 8.1.7.4 on Win 2003 server. If I connect
SQL> connect sys/mypassword@MYDB as sysdba
I have
ERROR:
ORA-01017: invalid username/password; logon denied
But if I issue :
SQL> connect sys@MYDB as sysdba
Enter password:
It would be OK :
Connected.
What is the problem ?
Thank for help.
In the two cases I entered the correct password and I'm sure of it.

By default, the SYS password on 8i is change_on_install, is it the one you used ?
Furthermore, the user/password used when you are conneting as sysdba doesn't matter :
E:\apps\oracle\ora0817\bin>sqlplus /nolog
SQL*Plus: Release 8.1.7.0.0 - Production on Wed Oct 1 18:44:03 2008
(c) Copyright 2000 Oracle Corporation. All rights reserved.
SQL> conn kuere/eiriuur@DEMO817 as sysdba --obviously this user/password doesn't exists onto the database
Connected.
SQL> show user
USER is "SYS"
SQL> disc
Disconnected from Oracle8i Enterprise Edition Release 8.1.7.4.1 - Production
With the Partitioning option
JServer Release 8.1.7.4.1 - Production
SQL> conn sys/change_on_install@DEMO817 as sysdba
Connected.
SQL> show user
USER is "SYS"
SQL> disc
Disconnected from Oracle8i Enterprise Edition Release 8.1.7.4.1 - Production
With the Partitioning option
JServer Release 8.1.7.4.1 - Production
SQL> conn sys@DEMO817 as sysdba
Enter password:
Connected.
SQL> show user
USER is "SYS"
SQL> disc
Disconnected from Oracle8i Enterprise Edition Release 8.1.7.4.1 - Production
With the Partitioning option
JServer Release 8.1.7.4.1 - Production
SQL> conn /@DEMO817 as sysdba
Connected.
SQL> show user
USER is "SYS"
SQL> show parameter password
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
SQL>Please, check the remote_login_passwordfile parameter value as I showed here above. Are you locally on the server or remote connection ?
Lastly, some unexpected behaviour can come on non-certified config (8i on W2003), but you already know that.
Nicolas.

Connecting as sysdba / sysoper

Hi Guys, If I do this
connect / as sysdba
connect / as sysoper
I am connected but how do I ensure that it prompts me for a sysdba / sysoper password before it connects me.
Thank you.

and the exact to connect would be
$sqlplus "/ as sysdba"
or
$sqlplus
username:/ as sysdba
password:yourwish/nopassword/anything
or
$sqlplus /nolog
sql> conn / as sysdba
But for all these things you need to set up ORACLE_SID,ORACLE_HOME,PATH varibales
but dont use OS authentication

Is possible to connect db with sys/sys as sysdba in SQLPLUS utility

Hi all,
I'm using windows 2000 with oracle 10.1.0
I have to connect server through SQLPLUS utility. I can able to connect system/manager@instance_name
From system user, i cant able to query >archive log list; .Im getting error as permission denaid.
is any possbilities there to login as super user(sys/sys as sysdba) in SQLLUS utility.
Thanks

connect sys/sys@instance_name as sysdbaUses password file in $ORACLE_HOME/dbs, connecting through SQL*NET
connect sys/sys as sysdbaUses the BEQ protocol to connect to the database process directly and uses OS authentication, meaning your can use whatever username or password, it does not matter, same as connect / as sysdba - It will always connect to the SYS schema regardless. For this to work, your account needs to be in the SYSDBA group. (DBA - Linux, OSDBA - Windows).
See the oracle standard documentation for creating a password file under Windows.
When you have created the passwd file, you can reset the password using
sqlplus / as sysdba
alter user sys identified by 'password' ;

Error Usage: CONNECT username [AS SYSDBA|SYSOPER]

Hi,
I am running a request set which starts of with unix shell script.
I get this error:
Invalid option.
Usage: CONNECT <username> [AS SYSDBA|SYSOPER]
Invalid option.
Usage: CONNECT <username> [AS SYSDBA|SYSOPER]
Invalid option.
Usage: CONNECT <username> [AS SYSDBA|SYSOPER]
unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
Can anyone tell me why this is happening/
thanks
Ash

This is the unix script which is used:
Please let me know where is goin wrong:
#!/usr/bin/ksh
##sqlplus -s apps/w0rkin <<-ENDSQL
logi=`echo $1|awk '{print $3 }'`
login=`echo $logi|awk -F'=' '{ print $2 }'|sed 's/"//g'`
org_id=`echo $1|awk '{print $9 }'`
sqlplus -s $login <<ENDSQL
set serveroutput on size 1000000 verify off
define xxdata=${XXDATA}
variable xxdatav varchar2(100)
var status_out NUMBER;
define org=$org_id
DECLARE
v_xxdata_path1 Varchar2(100);
v_xxdata_path2 Varchar2(100);
v_errbuf Varchar2(100);
v_retstat Number;
v_org VARCHAR2(20);
BEGIN
--v_xxdata_path1 := '&xxdata'||'/ont/outbound';
v_xxdata_path1 := '&xxdata'||'/ont/oraout';
v_xxdata_path2 := '${XXDATA}';
dbms_output.put_line('1. XXDATA ='||v_xxdata_path1);
dbms_output.put_line('2. Organization Id ='||'&org');
select decode('&org','""','-1',null,'-1','&org')
into v_org
from dual;
dbms_output.put_line('v_org='||v_org);
xxont_bt_outbound_pkg.create_outbound_btfile(v_xxdata_path1,to_number(v_org),
v_errbuf,v_retstat);
dbms_output.put_line('v_retstat='||v_retstat);
:status_out := v_retstat;
--dbms_output.put_line('2. XXDATA ='||v_xxdata_path2);
:xxdatav := '${XXDATA}';
END;
print :status_out
exit :status_out
ENDSQL
if [ $? -ne 0 ]
then
echo "Outbound file creation failed!!!"
exit 1
else
exit 0
fi

Cannot connect with "SYS@MYDB AS SYSDBA"

Hello,
I logged in as os user oracle and do:
sqlplus "SYS@MYDB AS SYSDBA"
After entering the right password I get this error:
This returns a ORA-01031: insufficient privileges
MYDB is a local database.
sqlplus "SYS AS SYSDBA"
and
sqlplus "/ AS SYSDBA"
both work.
I don't use password files (and I don't want to).
Doing the first statement on a remote database (Win2K) works also. If the remote database is a Linux
machine I receive again a ORA-01031.
Any ideas whats wrong here?
Kai

ensure:
a. The listener is running.Is running.
b. there is a definition for MYDB in the local tnsnames file.Is done. There is also oracle names running. sqlplus scott/tiger@MYDB works. So no problem here.
c. There is an entry like: remote_login_passwordfile=EXCLUSIVE or SHARED in your init file.I don't want to use a password file.
More ideas?
Kai

Unable to connect to sqlplus .. sys as sysdba .. No listener in Oracle 11G

Hi ,
I have installed Oracle 11.2.0 . When connecting to sqlplus with sys as sysdba . Getting error as NO listener .
I started listener . But finally getting the message as
The listener supports no services
The command completed successfully
Kindly help

I am getting the same message
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/product/11.2.0/dbhome_1/log/diag/tnslsnr/oracledb/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oracledb.example.com)(PORT=1521)))
The listener supports no services
The command completed successfully
I don't find the services entry here .

Svrmgrl - disable password for connect internal

I have installed Oracle 8.1.5.
When I tried to create a database using svrmgrl manually, I entered the following:
svrmgrl
svrmgrl> connect internal;
Password:
Please advise how I can turn off the Password option for connect internal as in previous version of Oracle.
Thanks

Christian is absolutely right. The user must be a member of the
dba group which you identified as the default database grup
during the installation.
The default is dba. If you chose another group, run the installer
again and choose Perform Adminstration Tasks, relink the
executables and try again.
Peter CARON
Senior Technical Consultant
Oracle Internal Training
Munich, GERMANY
Christian Pomar (guest) wrote:
: M.Menzel (guest) wrote:
: : Hello linux-users,
: : if i start svrmgrl i have the ora-12546 error, and
: : i have no idea of the password from user internal!
: : Whats my fault?
: : Thanks
: : Mikel
: There is not too much information about your problem, but ...
: are you in the dba group? I you are working directly on the
: server and you are in the dba group, you should be able to
: connect as internal with no problem...
: Hope it helps.
: Christian Pomar
null

CONNECT INTERNAL 시 SYS에 PASSWORD 걸기(SYSDBA, SYSOPER)

Similar Messages

Maybe you are looking for