Splus login as sys

Hi,
I'm a newbie in oracle. I have a oracle db 9.0.1.3.0 on windows 2000. I'm tryin to login usin the splplus dialog box as sys..i get teh error connection to sys shud be as sydba.
i try
sql> conn sys/sys@test as sysdba (dos)
it works fine..
wat is the syntax to connect as sys using the sqlplus dilaog box..( Orahome>application development>sqlplus)
kindly advise .
thanx in advance

Hi,
Well you're trying to use the "GUIed SQL*Plus". when the connect dialog pops ther's nowhere to tell it you want to connect AS SYSDBA.
There are different ways to achieve this. For example you can:
- type "/nolog" in the login box, click OK, and then use the sqlplus CONNECT.
- type the full identifier string in the login field "sys/sys@srv as sysdba"
HTH,
Yoann.

Similar Messages

Problem in login with sys

hi,
i have a problem in login with sys, the situation as follows:
1- when i try to connect using : sqlplus "/as sysdba" or "sys/password as sysdba" it connect me to the DB.
2- when i try to connect : sqlplus "sys/password@MYDB as sysdba" it gives me "ORA-01017: invalid username/password; logon denied".
3- when i try to connect with another user i.e : sqlplus "system/password@MYDB" it connect me to the DB.
DB version : 9.2.0.8
OS version : Solaris 10
please advice...

1- when i try to connect using : sqlplus "/as sysdba"
or "sys/password as sysdba" it connect me to
the DB.This works anyway, because you're authenticated by OS. Example :
SQL> conn sys/aaaa as sysdba
Connected.
SQL> conn sys/bbbb as sysdba
Connected.
SQL>
2- when i try to connect : sqlplus "sys/password@MYDB
as sysdba" it gives me "ORA-01017: invalid
username/password; logon denied".Here you need the real password, so make sure you're using the correct one.

Login as sys without supplying the password from the db host

Hi
I have tried today to login into the database as sys user and was able to login by providing a blank password. I tired this from sql plus installed in the db host. Why is the db allowing users to login as sys users with blank password? isnt this a authenticatio issue? is there any explanation or usage of this faciltiy.
Also i have tested to connect using another db user "as sysdba" and got connected with blank password.
Regards
Mahesh

If you connected to server with oracle user, or with user who is owner of Oracle Software, then it means that you're the administrator and you can connect to database without password
Please refer to documentation for more information
[Selecting an Authentication Method|http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/dba.htm#i1006628]
Kamran Agayev A. (10g OCP)
http://kamranagayev.wordpress.com

After 9i (9.2.0.1)Install on Windows 2003 cannot login as sys/sysdba/system

Hello all,
I need to someone's help.
I just installed Oracle After 9i (9.2.0.1)Install on Windows 2003.
I can only login using scott/tiger.
cannot login as sys/sysdba/system
I used Oracle dtabase Configuration Assistant. At the last step it asked me if I want to change sys and system passwords, I did. However, I cannot verify if system took those. The default combinations system/manager sys/change_on_install are not working.
As well as my new passwords.
How can I resolve it?
Thank you in advance,
Sonya

Recall what you used and you should be able to login .
OR
On windows create new password for sys user. This should work for you since you are on windows OS
back up the file in you ORACLE_HOME/database/PWD<SID>.ora
Create a new one using
orapwd file=...database/PWD<sid>.ora password=<new password> entries=5
stop the oracleService<SID>
start the oracleService<SID>
sqlplus /nolog
connect sys as sysdba
Enter password: <new password>
You should be able to login with this new password created
Ss

Login as sys delay

Dear all,
Oracle 11g on sun solaris 10
Login as sqlplus sys/oracle as sysdba takes a lot of time to login where as normal users can be able to login immediately including user system.Please atleast give me a hint to troubleshoot this.
Kai

Dear KaiS,
Please check the alert.log and the listener.log files for further information. Also please check the adump, which sys login actions are being written there.
Sometimes those adump directory gets overloaded and sys user even can not login to the database whereas the other users can connect without any problems. Consider it please.
Regards.
Ogan

MBP NVIDIA blackout - Change auto login in sys pref's?

I have an appointment in a couple of hours @ Apple Store... I when working at home check the auto login to the main user name I use to save time at boot up. Now I have to bring in my MBP and have them work on it. I have some proprietary stuff on the thing that I would like to have not available to who ever works on my computer, so, the question is HOW do I change the System Preferences for the auto startup to just boot up to the login window when I can't see the screen to use the mouse to change it?

Well, I brought it in without changing the auto-login, and they asked for the login password anyway, so I guess that my question was and would have been moot.
The 'genius' that 'helped' me, tested my MBP and said that it "failed - eligible processor not found" - and that I had to pay the flat rate + labor ($310) + taxes. The claimed resolution was to replace the MLB. Which is what they do when NVIDIA card is the claimed problem since it is soldered to the MLB. So, new questions are...
WHAT is the difference between my NVIDIA problem and the one they are claiming is the covered one???????
What recourses are there for we that have a NVIDIA problem that is not covered (other than biting the bullet and paying)??
I left my MBPro for the repair and it should be back in the store today for pickup. Is it possible the repair shop will tell the store to not charge me for the repair? (RE: Article: T52377)
As a MacAholic from 1984, I'm a bit upset at this...

How to prohitbit login as sys?

Hi All...
How to protect login : conn / as sysdba
because beginners also login as sysdba . So i want to protect him to login.
S.

One thing is that dont allow them to connect to the server.
Because, the above command can be done on through the server.
Prevent them entering into the db server, which also prevents them accessing db as sysdba.
Jaffar

Login as SYS using OCI 7

I can not log in as SYS / password as sysdba
using OCI 7..
Do anyone has any ideas, on what to do ?
Thanks

I think that what Nancy is referring to is (from 9.2
docs):
Purpose
Toggles between a V8 or later service context handle and a V7 Lda_Def.
Syntax
sword OCISvcCtxToLda ( OCISvcCtx *srvhp,
OCIError *errhp,
Lda_Def *ldap );
Parameters
svchp (IN/OUT)
The service context handle.
errhp (IN/OUT)
An error handle you can pass to OCIErrorGet() for diagnostic information in the event of an error.
ldap (IN/OUT)
A Logon Data Area for Oracle7-style OCI calls which is initialized by this call.
Comments
Toggles between an OCI release 8 or later service context handle and an Oracle7 Lda_Def.
This function can only be called after a service context has been properly initialized.
Once the service context has been translated to an
Lda_Def, it can be used in release 7.x OCI calls (for
example, obindps(), ofen()).
Note: If there are multiple service contexts which share
the same server handle, only one can be in Oracle7 mode
at any time.
The action of this call can be reversed by passing the
resulting Lda_Def to the OCILdaToSvcCtx() function.
The OCI_ATTR_IN_V8_MODE attribute of the server handle or
service context handle enables an application to determine
whether the application is currently in Oracle
release 7 mode or Oracle release 8 or later mode

Problem login denied as sys as sydba

Hi,
I was able to login as sys/passwd@dbname. But when I tried to connect sys/passwd@dbname as sysdba, I got this error :
ORA-01017: invalid username/password; logon denied
I was doing this using SQL*Plus and on the server where the database resides.
I need to shutdown this database. As far as I know I need to connect "as sysdba", right?
Any help would be appreciated. Thanks!

There are two ways to connect to Oracle as sysdba:
1) through the network using a password file (indeed, when specifying a sid in the connect string you are always connecting this way)
2) internally
For 1) to work, you need to have a password file in place and grant the sysdba rights to the users that can be connected to as sysdba remotely. To do so, the init.ora file needs the setting:
remote_login_passwordfile = exclusive
and you need to use the
orapwd
utility to create the password file. The password file stores the username/password for all connections that may remotely connect as sysdba. When you grant sysdba to a user, this file gets updated. In your case, my guess is that file was not made for the ess04 database and was for the ess03 database. Thus you are left with the following option. :)
For 2) to work, you need to correctly identify your instance. An instance is identified by two things: an ORACLE_SID and an ORACLE_HOME. (reason for this is you can have multiple instances per oracle installation and you can have multiple oracle installations on 1 machine.) Identification can be done by 'normal' environment variables which can be set in
- your registry or
- your machines environment variables or
- your sessions environment variables.
The last is easiest and most flexible if you have multiple instances on 1 machine. Just do this:
set ORACLE_SID=ESS04
set ORACLE_HOME=c:\oracle\ora81 (where oracle is installed, not including the bin directory)
sqlplus /nolog
connect / as sysdbaThis last command basically connects internally using the environment settings and without using the password file. You can only do this as administrator (ORA_DBA group user) on the machine the instance is installed on. Once you can connect internally, you can set up your instance to also allow remote sysdba connections as described in item 1.
This is similar on Unix.
Hope this helps,
Lennert

Can't login isql*plus as sys sysdba

Installed 10g on Windows XP SP3.
Everything works fine except can not login as sys sysdba via url
http://I6000D:5560/isqlplus/dba
It prompts for ONLY username and password and connection ID. however, I don't where to enter 'As sysdba'. Tried put 'as sysdba' in each field but no use.
No problem from DOS command prompt: connect sys/pwd as sysdba

Confused about the info on the web site regarding enabling dba
- Do i do the enabling only, or everything after enabling, like ' To set up the iSQL*Plus DBA URL'?
- for enabling dba access, please provide detailed instructions since I have very little time to get this resolved
That web site pointing to a lot of documents. do not know which doc to look into...
Thanks for the help,
Dennis

Creating a job in schema when can't login in that schema

there is a requirement that I've to create a job in a schema, but i don't have that schema's password,but I've that server's SYSDBA's password,means I can login into SYS account as SYSDBA,
but I've to create a job in that schema.
how is it possible,
EXECUTE IMMEDIATE ' DECLARE '||
' X NUMBER; '||
' BEGIN '||
' SYS.Dbms_Job.SUBMIT '||
' ( job => X '||
' ,what =>'||''''||what ||''''||
' ,next_date => TO_DATE('||''''||next_date||''''||','||''''||'dd/mm/yyyy hh24:mi:ss'||''''||') '||
' ,INTERVAL => '||''''||intervl||''''||
',no_parse => TRUE '||
' );'||
'SYS.Dbms_Output.PUT_LINE('||''''||'Job Number is: '||''''||' || TO_CHAR(x)); '||
'END; ';
help required

A desc on DBA_JOBS reveials the first three:
LOG_USER    VARCHAR2(30)                    USER who was logged in when the job was submitted
PRIV_USER   VARCHAR2(30)                    USER whose default privileges apply to this job
SCHEMA_USER VARCHAR2(30)                    select * from bar means select * from schema_user.bar          Perhaps you could try chang_env:
Use the correct NLSENV, below is just an example:
begin
sys.dbms_ijob.change_env( JOB => 3
,LUSER => '<NEW USER>'
,PUSER => '<NEW USER>'
,CUSER => '<NEW USER>'
,NLSENV => 'NLS_LANGUAGE=''AMERICAN''
NLS_TERRITORY=''AMERICA''
NLS_CURRENCY=''$''
NLS_ISO_CURRENCY=''AMERICA''
NLS_NUMERIC_CHARACTERS=''.,''
NLS_DATE_FORMAT=''DD-MON-RR''
NLS_DATE_LANGUAGE=''AMERICAN''
NLS_SORT=''BINARY''');
end;

DBMS_SCHEDULER.run_chain() only works when connected to DB as sys

Database Version: 10.2.0.4.0
Hello,
I have a problem with DBMS_SCHEDULER.run_chain where the Chain to be run references an external Program.
The Chain runs correctly when run via SQLPLUS when you are connected to the database as SYS but fails to run when you are connected to the Database as the User who owns the Chain.
The complete steps to recreate the problem are below. Any thoughts or suggestions gratefully received.
Thanks,
Andy
STEP 1: Login with sys as sysdba and create a new user
CREATE USER chaintest IDENTIFIED BY password PROFILE DEFAULT ACCOUNT UNLOCK;
GRANT MGMT_USER TO chaintest;
GRANT CONNECT TO chaintest;
GRANT IMP_FULL_DATABASE TO chaintest;
GRANT SCHEDULER_ADMIN TO chaintest;
GRANT MANAGE SCHEDULER TO chaintest;
GRANT EXECUTE ANY CLASS TO chaintest;
GRANT CREATE ANY DIRECTORY TO chaintest;
GRANT CREATE ANY JOB TO chaintest;
GRANT CREATE TABLE TO chaintest;
GRANT EXECUTE ANY PROGRAM TO chaintest;
GRANT CREATE JOB TO chaintest;
GRANT CREATE EXTERNAL JOB TO chaintest;
STEP 2: Create a very simple batch file
Create a folder called c:\chaintest and create a text file in there whose entire contents
is "notepad.exe" followed by a carriage return. The idea is that if this batch file is
called a notepad Window will be opened so we can clearly see if the batch file has run.
STEP 3: Create a DBMS_SCHEDULER Program
BEGIN
DBMS_SCHEDULER.CREATE_PROGRAM (
program_name => 'CHAINTEST.CHAINTEST_PROGRAM',
program_type => 'EXECUTABLE',
program_action => 'C:\WINDOWS\SYSTEM32\CMD.EXE /q /c c:\chaintest\chaintest.bat',
number_of_arguments => 3,
enabled => false);
DBMS_SCHEDULER.define_program_argument(
program_name =>'CHAINTEST.CHAINTEST_PROGRAM',
argument_position => 1,
argument_type => 'VARCHAR2',
default_value => '/q');
DBMS_SCHEDULER.define_program_argument(
program_name =>'CHAINTEST.CHAINTEST_PROGRAM',
argument_position => 2,
argument_type => 'VARCHAR2',
default_value => '/c');
DBMS_SCHEDULER.define_program_argument(
program_name =>'CHAINTEST.CHAINTEST_PROGRAM',
argument_position => 3,
argument_type => 'VARCHAR2',
default_value => 'c:\chaintest\chaintest.bat');
DBMS_SCHEDULER.enable('CHAINTEST.CHAINTEST_PROGRAM');
END;
STEP 4: Create a chain
BEGIN
DBMS_SCHEDULER.CREATE_CHAIN (chain_name => 'CHAINTEST.CHAINTEST_CHAIN');
END;
STEP 5: Create the only Chain Step
BEGIN
DBMS_SCHEDULER.DEFINE_CHAIN_STEP(chain_name=>'CHAINTEST.CHAINTEST_CHAIN'
, step_name=>'STEPA'
, program_name=>'CHAINTEST.CHAINTEST_PROGRAM');
END;
STEP 6: Create Chain Rules
BEGIN
DBMS_SCHEDULER.DEFINE_CHAIN_RULE(
chain_name=>'CHAINTEST.CHAINTEST_CHAIN'
, condition=>'TRUE'
, action=>'START STEPA');
DBMS_SCHEDULER.DEFINE_CHAIN_RULE(
chain_name=>'CHAINTEST.CHAINTEST_CHAIN'
, condition=>'STEPA COMPLETED'
, action=>'END');
END;
STEP 7: Enable the Chain
BEGIN
DBMS_SCHEDULER.enable('CHAINTEST.CHAINTEST_CHAIN');
END;
STEP 8: Run the Chain whilst still connected as sys and observe that a Notepad window opens
confirming that the Batch file ran successfully.
BEGIN
DBMS_SCHEDULER.run_chain(
chain_name=>'CHAINTEST.CHAINTEST_CHAIN'
, start_steps=>NULL);
END;
STEP 9: Connect to the database as the CHAINTEST user and run the same command as in STEP 8 above.
Observe that even though you receive the message "PL/SQL procedure successfully completed." and do
not see any error messages that no Notepad Window is opened indicating that the Batch file was NOT run.
BEGIN
DBMS_SCHEDULER.run_chain(
chain_name=>'CHAINTEST.CHAINTEST_CHAIN'
, start_steps=>NULL);
END;

>
The Chain runs correctly when run via SQLPLUS when you are connected to the database as SYS but fails to run when you are connected to the Database as the User who owns the Chain.
>
Not true based on what you posted. The chain DOES RUN connected as SYS and when connected as the User who owns the chain.
You posted steps that show that SYS is the user that owns the program and thus the chain.
>
STEP 1: Login with sys as sysdba and create a new user
STEP 8: Run the Chain whilst still connected as sys and observe that a Notepad window opens
confirming that the Batch file ran successfully.
>
I don't see where you made any EXECUTE grant to user 'chaintest' that would allow that user to execute the program.
See the Usage Notes in the CREATE PROGRAM section of DBMS_SCHEDULER in the Database PL/SQL Packages and Types Reference
http://docs.oracle.com/cd/B28359_01/appdev.111/b28419/d_sched.htm#CIHEHDHA
>
For other users to use your programs, they must have EXECUTE privileges, therefore once a program has been created, you have to grant EXECUTE privileges on it.
>
Grant the EXECUTE privilege to user 'chaintest' and try it.

Login problem: Oracle 10g EM

Hi,
I installed Oracle 10g (version 10.2.0.3.0) on my system which has Windows Vista Home Basic as its operating system. After successful installation em was started automatically and i tried to login with sys account with below details
uname: sys
pass: which i supplied during installation
connect as: sysdba
when i try to login, it simply returns the login page again. When i supply a wrong password intentionaly, it gives me the usual error message 'wrong uname/pass'. But when i supply authentic info it simply refreshes the page. I checked that the Oracle services are all up and running.
Another interesting behavior is when i try to login with system account (which is by default unlocked) with the password i supplied during installation, it says wrong username/password. I tried a little bit of trial error and saw i can login to the commande prompt with scott/tiger (in case i unlocked it during installation) but i can not login to em with this account. It behaves exactly same, simply refreshes the page and no error message.
Can someone please help me to figure out this problem, i am pretty confused what is going wrong here.
thanks in advance,
Arnab.

user5813004 wrote:
I installed Oracle 10g (version 10.2.0.3.0) on my system which has Windows Vista Home Basic as its operating system. The symptom you describe is exactly the same as most people who install Oracle database on Vista (or XP) HOME.
If you want the Enterprise Manager to work, you are encouraged to upgrade your OS to the minimum certified by Oracle, as discussed in the installation docs.

Login as sysdba problem...

Hi,
I've created my own database to make tests on Oracle and directly after that I've changed the passwords for all the users (sys and system users included).
When I try to login without the sysdba role, Oracle applies the password verification fine.
The problem is when I try to login as sysdba:
$> sqlplus 'sys as sysdba'
I can enter whatever password I want and I'm connected !!!
And it's the same if first I type:
$> sqlplus /NOLOG
SQL*Plus: Release 9.2.0.1.0 - Production on Wed May 7 13:21:44 2003
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> connect sys as sysdba
Could someone help me to find where It comes from and how I do solve this security hole...
Thanks in advance
Paul

What's the OS? Are you signed on to the OS as a user in > the DBA group?I'm using a Debian 3.0 (Woody) operating system with a Linux 2.4.18 kernel
I've got only one user which is a member of the DBA group and what I experienced, It's true, was only when I was logged as this user...
Does it means that when a user is a member of the DBA group on the operating system, even if the remote_os_authent parameter is set to false, he can login with sys as sysdba as he wants trough sqlplus ?
+++++++++++++++++++++++++++++++
Original message:
Hi,
I've created my own database to make tests on Oracle and directly after that I've changed the passwords for all the users (sys and system users included).
When I try to login without the sysdba role, Oracle applies the password verification fine.
The problem is when I try to login as sysdba:
$> sqlplus 'sys as sysdba'
I can enter whatever password I want and I'm connected !!!
And it's the same if first I type:
$> sqlplus /NOLOG
SQL*Plus: Release 9.2.0.1.0 - Production on Wed May 7 13:21:44 2003
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> connect sys as sysdba
Could someone help me to find where It comes from and how I do solve this security hole...
Thanks in advance
Paul
+++++++++++++++++++++++++++++++

Issue encountered when Login as sysdba role using Thin Oracle JDBC Driver

Hello all,
we are now considering to use Thin oracle JDBC driver to create database in our project, but we met one issue when we tried to connect to oracle as sysdba role using Thin driver, and it throws java.sql.SQLException: Io Exception: SO Exception was generated, I have found some tips on oracle jdbc website and it says :
How do I connect as SYSDBA or SYSOPER?
The only way to do this is to use the Properties object when connecting, rather than specifying the username and password as strings. Put the username into the "user" property, and the password into the "password" property. Then, put the mode into the "internal_logon" property. Something like the following:
Properties props = new Properties();
props.put("user", "scott");
props.put("password", "tiger");
props.put("internal_logon", "sysoper");
Connection conn = DriverManager.getConnection (url, props);
When connecting as SYSDBA or SYSOPER using the Thin driver, the RDBMS must be configured to use a password file. See "Creating and Maintaining a Password File" in the "Oracle Database Administrator's Guide".
So, i did execute orapwd command to create a password file and also set remote_login_passwordfile=execlusive in my initxxx.ora initial parameter file, however, when i tried to connect, it failed.
private static void createEmsdbDatabase(){
String url = "jdbc:oracle:thin:@localhost:1521:";
StringBuffer sqlStatement = new StringBuffer();
sqlStatement.append("create database xxx");
sqlStatement.append("maxdatafiles 254 ");
sqlStatement.append("maxinstances 8 ");
sqlStatement.append("maxlogfiles 32 ");
sqlStatement.append("character set UTF8 ");
sqlStatement.append("national character set UTF8 ");
sqlStatement.append("DATAFILE 'c:\\oracle\\xxx\\system01.dbf' SIZE 18M REUSE ");
sqlStatement.append("logfile 'c:\\oracle\\xxx\\redo01.log' SIZE 2M REUSE, ");
sqlStatement.append("'c:\\oracle\\xxx\\redo02.log' SIZE 2M REUSE, ");
sqlStatement.append("'c:\\oracle\\xxx\\redo03.log' SIZE 2M REUSE ");
try {
DriverManager.registerDriver(new OracleDriver());
Properties props = new Properties();
props.put("user", "sys");
props.put("password", "password");
props.put("database","xxx");
props.put("internal_logon", "sysdba");
Connection conn = DriverManager.getConnection(url, props);
Statement statement = conn.createStatement();
statement.executeUpdate(sqlStatement.toString());
statement.close();
conn.close();
} catch (SQLException e) {
e.printStackTrace();
But what made me puzzled a lot is if i use OCI driver, it did work great, why??? guys, anybody knows, please give me some tips, thanks in advance.
regards,
Kaixuan @ Shanghai

clarify my question in detail:
Step 1 : create password file using orapwd command
Step 2 : create database instance using oradim command
Step 3 : login using sys as sysdba to startup database, e.g startup nomount pfile='...\initxxx.ora'
Step 4 : create database.
java code showing below:
private static void createEmsdbDatabase(){
String url = "jdbc:oracle:thin:@localhost:1521:";
StringBuffer sqlStatement = new StringBuffer();
sqlStatement.append("create database xxx ");
sqlStatement.append("maxdatafiles 254 ");
sqlStatement.append("maxinstances 8 ");
sqlStatement.append("maxlogfiles 32 ");
sqlStatement.append("character set UTF8 ");
sqlStatement.append("national character set UTF8 ");
sqlStatement.append("DATAFILE 'c:\\oracle\\xxx\\system01.dbf' SIZE 18M REUSE ");
sqlStatement.append("logfile 'c:\\oracle\\xxx\\redo01.log' SIZE 2M REUSE, ");
sqlStatement.append("'c:\\oracle\\xxx\\redo02.log' SIZE 2M REUSE, ");
sqlStatement.append("'c:\\oracle\\xxx\\redo03.log' SIZE 2M REUSE ");
try {
DriverManager.registerDriver(new OracleDriver());
Properties props = new Properties();
props.put("user", "sys");
props.put("password", "password");
props.put("database","xxx");
props.put("internal_logon", "sysdba");
Connection conn = DriverManager.getConnection(url, props);
Statement statement = conn.createStatement();
statement.executeUpdate(sqlStatement.toString());
statement.close();
conn.close();
} catch (SQLException e) {
e.printStackTrace();
issue was met here, when i tried to login as sysdba using sys, and in my java code, i use Thin driver, it then thrus exception, but when OCI driver is used, it works great, i don't know why.
that is, when i use "jdbc:oracle:oci8:@" as database URL and then properties.put("database","xxx"), it works great. but, when i use "jdbc:oracle:thin:@localhost:1521:" as database URL and then properties.put("database","xxx"), it failed. hopefully, i have clarified my question clearly. thanks.

Splus login as sys

Similar Messages

Maybe you are looking for