Ora 28009

Ora 28009 : could not connect as sysdba or sysoper. what is the problem how to login.
currently i am loging using scott account and then changing to sysdba account using connect usename/password as sysdba
please help

hi,
>>>
oracle@RRPortaldb>sqlplus sys/XXXXXX
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Jul 30 22:58:18 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
ERROR:
ORA-28009: connection as SYS should be as SYSDBA or SYSOPER
oracle@RRPortaldb>sqlplus sys/XXXXXX as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Jul 30 22:58:59 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL>
Regards
Jafar
http://www.oracledbarea.blogspot.com

Similar Messages

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.

Login error in forms ora-28009

Hi ,
Am trying to login forms 10g as sysdba.But am getting error ora-28009
username:sys
password:sys
connect:oracle causes ora-28009
username:sys as sysdba or sys/ as sysdba or sys/sys as sysdba
password:sys
connect:oracle causes ora-01017
username:sys/sys@oracle as sysdba causes ora-12154
BUT if try other users
username:hr
pasword:hr
connect:oracle it works fine.
i checked connectivity with database,listener all are working fine.
Please help in connecting to forms 10g and reports 10g as sysdba.
Thanks.

ORA-28009:
connection as SYS should be as SYSDBA or SYSOPER
Cause: connect SYS/<password> is no longer a valid syntax
Action: Try connect SYS/<password> as SYSDBA or connect SYS/<password> as SYSOPER
Therefore, Try this
in 10G
C:\>sqlplus
Enter user-name: / as sysdba
Prior to Oracle 10g, when you wanted to connect using / AS SYSDBA on the command prompt, you had to put the connection string between double quotes:
C:\>sqlplus "/ as sysdba"
To specify the connection string; you need the following format: username/password@instance as SYSDBA.

Event test "Archive Full (%)" failed: ora-28009:

Trying to create an event that will send an email with OEM but Im getting this message
Event test "Archive Full (%)" failed: ora-28009: connection to sys should be as sysdba or sysoper in the event viewer.
Im not sure what this refers to though - to connect to Management Server it has to be sysman user. What "connection" is this referring to ???
Oracle 9.2.0.5.0 (due to migrate to 10g at years end hurrah!)
Windows XP (now, but AIX once in production)

OK thanks for that. I went ahead and did this:
Configuration
Manage Administrators
Selected SYSMAN
Preferred Credentials
Selected target database and erased everything from the Database Credentials fields (where previously we had SYS/AS SYSDBA etc. )
I am getting the same darn error as before.
Anyway, the OEM help for this screen says
Role Select the role from the pull-down list. You need to login with the SYSDBA or SYSOPER role to start up or shut down a database.
Still stuck on this. I dont properly understand the error itself - it is telling me that the connection to sys should be as sysdba - and I am connecting as sysdba. ... . not sure what else I can do apart from try and write a script and forget this altogether.
Thanks
DA
Also, in the Event Viewer, according the documentation, there is an "advice" tab. I see no such tab. :(
When I try to create an event without any information supplied to the fields for SYSMAN Preferred Credentials, I get this in Event Viewer:
"Failed - ora-0:normal , successful completion."
Now I am really confused - a "failed, normal completion" ??
Message was edited by:
Dan A
Message was edited by:
Dan A

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."

Error -Job scheduling

Hi
I am getting the following error while scheduling job using OEM:
SQL*Plus: Release 9.2.0.1.0 - Production on Wed Jun 8 12:22:36 2005
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Enter user-name: ERROR:
ORA-28009: connection to sys should be as sysdba or sysoper
Enter user-name: Enter password: ERROR:
ORA-01005: null password given; logon denied
Enter user-name:
ora-28009: connection to sys should be as sysdba or sysoper
Can anybody help me in resolving this issue.
TIA
Aqueel.

Don't connect as SYS, it should not be used for such daily tasks. Use a non-SYSDBA user, if you use SYS it must be a connection as SYSDBA (9i and higher), this is not possible in all OEM areas, so this error message occurs.

Help! Script that works in 8.1.7 does not work in 9.2.0

I have a generic hot backup script that runs well in our 8i environment where I source the username and password for SYS from a secured txt file. However I could not get the script to work in our recently installed 9.2.0 environment.
Below is an extract of the hot backup script:
# Set environment
. ${HOME}/BACKUP/${DBNAME}.env
CONNECT_STRING=`${HOME}/admin/Util/syspass.sh sys $DBNAME`
export CONNECT_STRING
#Define some commands and files
SQLPLUS="${ORACLE_HOME}/bin/sqlplus -s ${CONNECT_STRING}"
TIME_STAMP=`date +"%d-%b-%Y"`
# Test for duplicate filenames
$SQLPLUS <<-EOF
var numfiles number;
BEGIN
SELECT count(*) into :numfiles
FROM dba_data_files a, dba_data_files b
WHERE a.file_name != b.file_name
AND SUBSTR(a.file_NAME, INSTR(a.file_name, '/', -1) + 1)
= SUBSTR(b.file_NAME, INSTR(b.file_name, '/', -1) + 1);
END;
exit :numfiles
EOF
FILE_ERROR=$?
echo "Number of duplicate files $FILE_ERROR"
if [ $FILE_ERROR -gt 0 ]; then
echo "Aborting, ... $FILE_ERROR duplicate filenames"
exit
fi
As per the extract above,
in our 8.1.7 environment,
(1) the command CONNECT_STRING=`${HOME}/admin/Util/syspass.sh sys $DBNAME`
will result in CONNECT_STRING=sys/xxxxxx@<sid>
(2) the command SQLPLUS="${ORACLE_HOME}/bin/sqlplus -s ${CONNECT_STRING}"
will result in SQLPLUS=/usr/oracle/product/8.1.7/bin/sqlplus -s sys/xxxxxx@<sid>
(3) and when issue $SQLPLUS <<-EOF
it connects fine and execute the procedure successfully.
in Oracle 9.2.0,
(1) the command CONNECT_STRING=`${HOME}/admin/Util/syspass.sh sys $DBNAME`
works fine with result same as in 8.1.7 - CONNECT_STRING=sys/xxxxxx@<sid>
(2) the command SQLPLUS="${ORACLE_HOME}/bin/sqlplus -s ${CONNECT_STRING}"
works fine with result SQLPLUS=/usr/oracle/product/9.2.0/bin/sqlplus -s sys/xxxxxx@<sid>
(3) However, when issue $SQLPLUS <<-EOF returns an error:
ERROR:
ORA-28009: connection to sys should be as sysdba or sysoper
How can I fix that??
Is it because of the username/password structure (sys/xxxxxx@<sid>)??
I would like to keep such username/password format if possible.
I have also tried to hard coded the username/password for variable SQLPLUS as:
SQLPLUS="/usr/oracle/product/9.2.0/bin/sqlplus -S '/ as sysdba'"
But it still doesn't work when issue $SQLPLUS, it returns the following:
Usage: SQLPLUS [ [<option>] [<logon>] [<start>] ]
where <option> ::= -H | -V | [ [-L] [-M <o>] [-R <n>] [-S] ]
<logon> ::= <username>[<password>][@<connect_string>] | / | /NOLOG
<start> ::= @<URI>|<filename>[.<ext>] [<parameter> ...]
"-H" displays the SQL*Plus version banner and usage syntax
"-V" displays the SQL*Plus version banner
"-L" attempts log on just once
"-M <o>" uses HTML markup options <o>
"-R <n>" uses restricted mode <n>
"-S" uses silent mode
Any ideas as to how to have the script run in 9.2.0??
Your help is much appreciated.

Hi, I tried CJs suggestion; however it still doesnt work for me.
I tried assigning the command line to a variable, I tried to log in directly from the command line, and both dont work (see below). What did I do wrong??
$ SQLPLUS="/usr/oracle/product/9.2.0/bin/sqlplus -S \"sys/xxxxxx@<sid> as sysdba\""
$ echo $SQLPLUS
/usr/oracle/product/9.2.0/bin/sqlplus -S "sys/xxxxxx@<sid> as sysdba"
$ $SQLPLUS
Usage: SQLPLUS [ [<option>] [<logon>] [<start>] ]
where <option> ::= -H | -V | [ [-L] [-M <o>] [-R <n>] [-S] ]
<logon> ::= <username>[<password>][@<connect_string>] | / | /NOLOG
<start> ::= @<URI>|<filename>[.<ext>] [<parameter> ...]
"-H" displays the SQL*Plus version banner and usage syntax
"-V" displays the SQL*Plus version banner
"-L" attempts log on just once
"-M <o>" uses HTML markup options <o>
"-R <n>" uses restricted mode <n>
"-S" uses silent mode
$ sqlplus "sys/xxxxxx@<sid> as sysdba"
SQL*Plus: Release 9.2.0.4.0 - Production on Wed Mar 24 08:53:05 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
ERROR:
ORA-01031: insufficient privileges

Script that works in 8.1.7 does not work in 9.2.0

I have a generic hot backup script that runs well in our 8i environment where I source the username and password for SYS from a secured txt file. However I could not get the script to work in our recently installed 9.2.0 environment.
Below is an extract of the hot backup script:
# Set environment
. ${HOME}/BACKUP/${DBNAME}.env
CONNECT_STRING=`${HOME}/admin/Util/syspass.sh sys $DBNAME`
export CONNECT_STRING
#Define some commands and files
SQLPLUS="${ORACLE_HOME}/bin/sqlplus -s ${CONNECT_STRING}"
TIME_STAMP=`date +"%d-%b-%Y"`
# Test for duplicate filenames
$SQLPLUS <<-EOF
var numfiles number;
BEGIN
SELECT count(*) into :numfiles
FROM dba_data_files a, dba_data_files b
WHERE a.file_name != b.file_name
AND SUBSTR(a.file_NAME, INSTR(a.file_name, '/', -1) + 1)
= SUBSTR(b.file_NAME, INSTR(b.file_name, '/', -1) + 1);
END;
exit :numfiles
EOF
FILE_ERROR=$?
echo "Number of duplicate files $FILE_ERROR"
if [ $FILE_ERROR -gt 0 ]; then
echo "Aborting, ... $FILE_ERROR duplicate filenames"
exit
fi
As per the extract above,
in our 8.1.7 environment,
(1) the command CONNECT_STRING=`${HOME}/admin/Util/syspass.sh sys $DBNAME`
will result in CONNECT_STRING=sys/xxxxxx@<sid>
(2) the command SQLPLUS="${ORACLE_HOME}/bin/sqlplus -s ${CONNECT_STRING}"
will result in SQLPLUS=/usr/oracle/product/8.1.7/bin/sqlplus -s sys/xxxxxx@<sid>
(3) and when issue $SQLPLUS <<-EOF
it connects fine and execute the procedure successfully.
in Oracle 9.2.0,
(1) the command CONNECT_STRING=`${HOME}/admin/Util/syspass.sh sys $DBNAME`
works fine with result same as in 8.1.7 - CONNECT_STRING=sys/xxxxxx@<sid>
(2) the command SQLPLUS="${ORACLE_HOME}/bin/sqlplus -s ${CONNECT_STRING}"
works fine with result SQLPLUS=/usr/oracle/product/9.2.0/bin/sqlplus -s sys/xxxxxx@<sid>
(3) However, when issue $SQLPLUS <<-EOF returns an error:
ERROR:
ORA-28009: connection to sys should be as sysdba or sysoper
How can I fix that??
Is it because of the username/password structure (sys/xxxxxx@<sid>)??
I would like to keep such username/password format if possible.
I have also tried to hard coded the username/password for variable SQLPLUS as:
SQLPLUS="/usr/oracle/product/9.2.0/bin/sqlplus -S '/ as sysdba'"
But it still doesn't work when issue $SQLPLUS, it returns the following:
Usage: SQLPLUS [ [<option>] [<logon>] [<start>] ]
where <option> ::= -H | -V | [ [-L] [-M <o>] [-R <n>] [-S] ]
<logon> ::= <username>[<password>][@<connect_string>] | / | /NOLOG
<start> ::= @<URI>|<filename>[.<ext>] [<parameter> ...]
"-H" displays the SQL*Plus version banner and usage syntax
"-V" displays the SQL*Plus version banner
"-L" attempts log on just once
"-M <o>" uses HTML markup options <o>
"-R <n>" uses restricted mode <n>
"-S" uses silent mode
Any ideas as to how to have the script run in 9.2.0??
Your help is much appreciated.

My first comment is that even though you are using a secure encrypted text file, putting the SYS password on the command line can make the password available to anyone on the server who can perform a ps command:
shvec320 ECD2 /u01/home/oracle/cronscripts $ sqlplus mark/mark4s@dbnm
SQL*Plus: Release 8.1.7.0.0 - Production on Wed Mar 24 16:47:17 2004
(c) Copyright 2000 Oracle Corporation. All rights reserved.
Connected to:
Oracle8i Enterprise Edition Release 8.1.7.4.0 - Production
With the Partitioning option
JServer Release 8.1.7.4.0 - Production
SQL> !ps -ef | grep mark
oracle 25494 25078 0 16:47:17 pts/4 0:00 sqlplus mark/mark4s@dbnm
oracle 25497 25494 0 16:47:23 pts/4 0:00 grep mark
Consider putting the connect string in the SQL script:
sqlplus /nolog <<-EOF
connect ${CONNECT_STRING}
var numfiles number;
BEGIN
SELECT count(*) into :numfiles
FROM dba_data_files a, dba_data_files b
WHERE a.file_name != b.file_name
AND SUBSTR(a.file_NAME, INSTR(a.file_name, '/', -1) + 1)
= SUBSTR(b.file_NAME, INSTR(b.file_name, '/', -1) + 1);
END;
exit :numfiles
EOF
Starting in Oracle 9 (others will correct me if I am wrong) you cannot connect to the sys account without specifying as SYSDBA or SYSOPER.
My testing (9.2.0.3) resulted in your ORA-1013 using "sys/password@dbname as sysdba". Using "sys/password as sysdba" works just fine. I seem to remember if you want to use @dbname, you will need to use password file authentication instead of OS authentication.
My suggestion -if possible - is to use plain "connect / as sysdba" in your SQL Script and have ORACLE_HOME and ORACLE_SID set correctly in your environment (do it in ${HOME}/BACKUP/${DBNAME}.env) :
sqlplus /nolog <<-EOF
connect / as sysdba;
var numfiles number;
BEGIN
SELECT count(*) into :numfiles
FROM dba_data_files a, dba_data_files b
WHERE a.file_name != b.file_name
AND SUBSTR(a.file_NAME, INSTR(a.file_name, '/', -1) + 1)
= SUBSTR(b.file_NAME, INSTR(b.file_name, '/', -1) + 1);
END;
exit :numfiles
EOF
HTH

ODBC login as sysdba

What is the syntax? From a client desktop I can login to SQL Plus and Enterprise Manager 10g, but not via ODBC (Test Connection) using the same login.
SQL PLUS:
Start/Programs/Oracle - OraDb10g_home3/Application Development/SQL Plus
presents a login box. I enter info as follows, and login is successful
User Name: sys
Password: <mysyspwd>
Host String: ORCL AS SYSDBA
web site to Enterprise Manager also presents a login box
User Name: sys
Password: <mysyspwd>
Connect As <I select SYSDBA from the dropdown list.>
but, ODBC, System DSN tab, Add
Data Source Name: <whatever>
TNS Service Name: ORCL -- or ORCL AS SYSDBA
User ID: sys
Click Test Connection
Password: <mysyspwd>
When the TNS Service name is filled in with only the TNSname,
I get ORA-28009 connection to sys should be as sysdba or sysoper
When the TNS Service name is filled in with TNSname AS SYSDBA,
the error is ORA-12154 TNS:couldnot resolve the connect identifier specified.
When TNS Service name is ORCL and User Id is SYS AS SYSDBA,
the error is ORA-01017:invalid username/password;login denied
The dirver is Oracle in OraDB10g_home3 (10.01.00.02 SQORA32.DLL 2/10/2004)
And I can login via ODBC using
TNS Service Name: ORCL
User ID: scott
Click Test Connection button
Password: tiger
I get Connection successful
Thank you, Nancy
Edited by: user5699535 on Aug 16, 2010 7:29 AM

1 Both are dangerous, but using ODBC you can store the password of the account in the registry or odbc.ini. ODBC connections are usually being distributed to the end-users who don't have the faintest idea what they are doing. However, if they do know how to write a passthrough query, they can do anything.
2 Your database is open to everyone. You are exposing sensitive data. It is in hand of people who might know some SQL. Who might write incorrect queries. Who might doing things which can not be traced, as everything was executed by SYS.
The issue is most developers of commercial software vendors and major consultancies do not care about security at all. I was often instructed to grant the DBA role to the application owner, because otherwise 'the application doesn't work'. There are far more incompetent developers out there than you and I can imagine.
Connecting to the database as SYS, indicates a lack of concern for security, and being too lazy to find out what privileges are really required.
I'm not aware of any reason why the use of SYS should be allowed in any client tool other than sqlplus or maybe sqldeveloper.
Sybrand Bakker
Senior Oracle DBA

Sys login as sysdba fails in OEM

System: Oracle Database 10g 10.1.0.2.0 with Oracle Database 10g Patch 10.1.0.4.0 on a SUN Solaris 9 SPARC machine.
Background:I've made a whole database backup and been trying to recover it back again. First i've tried that with RMAN but i didn't got all my data back in place.
Now i'm trying to run the recovery via the Enterprise manager. I create a job for it, my databases shuts down and I get the possibility to "perform recovery"
Problem:When i'm on the login page to continue with the recovery i have to fill in the Host Credentials and the Database Credentials as sysdba.
I know for sure that what i fill out in those fields is correct. The problem is that i can't login.
As Database Credentials do i fill in for username: sys and password: the correct paswd. It says that the Role = SYSDBA.
the error message: Unable to connect to the database.
ORA-01017: invalid username/password; logon denied
Neither can i log in with sys, password as sysdba via the Enterprise Manager when the database is up and running.
Things i've tried:login with sqlplus works fine
sqlplus "/ as sysdba"SQL> connect sys/<paswd> as sysdba
Connected.
SQL> show user
USER is "SYS"
Question:How can I solve the problem so i can log with sys users as sysdba with the Enterprise Manager?

Hi,
it's not a stupid question, are you really sure your password is correct? In your sqlplus session OS authentification is used, password is irrelevant (OEM does not use OS authentification). Try 'connect sys/abcxyz as sysdba' , it will work. There's a trick to check, if the password is correct.
Issue 'connect sys/<passwd>' (omit as sysdba). If you enter a correct password you will see ORA-28009 (SYS can only connect as SYSDBA or SYSOPER) , otherwise you see ORA-01017 .
In the case of ORA-28009 (password IS correct) there seems to be something wrong with the password file or pfile/spfile:
- REMOTE_LOGIN_PASSWORDFILE is set to NONE
- The password file does not exist
- The password supplied does not match the one in the password file
- The password file been changed since the instance was started
The password is located in $ORACLE_HOME/dbs, it can be recreated using orapwd utility, REMOTE_LOGIN_PASSWORDFILE should be set to EXCLUSIVE .
Regards
Werner

Fusion order aplication demo

Hi
when i Install the Schema for the Fusion Order Demo Application , i get the following message:
BUILD FAILED
C:\fod\Infrastructure\Ant\build.xml:52: The following error occurred while executing this line:
C:\fod\Infrastructure\DBSchema\build.xml:91: The following error occurred while executing this line:
C:\fod\Infrastructure\DBSchema\build.xml:56: The following error occurred while executing this line:
C:\fod\Infrastructure\DBSchema\build.xml:28: java.sql.SQLException: ORA-28009: connection as SYS should be as SYSDBA or SYSOPER
Can someone help me to deploy this application?
Thanx

Edit file C:\fod\Infrastructure\Ant\build.properties and set value of "db.adminUser" to "system" -
db.adminUser=systemRegards,
Anuj

Login problem to oracle 10g

Hi all,
I have installed the oracle 10g (Oracle Database 10g Release 1 (10.1.0.2) for Microsoft Windows (32-bit) ).The installation was sucessful and I created the same password for all the default accounts.I left everything for default like
Global Database name: orcl
SID:orcl
When I tried to enter to sql plus from '' start->all programs->Oracle-OraDb10g_home1->Appliction development ->SQL Plus,
On the logon screen, I entered the following information
user name: sys
password : ************
Host string : orcl
I also tried changing user names to like 'SYSTEM' but nothing works.The error message Iam getting is
ERROR: ORA-28009: connection to sys should be sysdba or sysoper
so I also tried changing the Host String to 'sysdba' and 'sysoper' .but Nothing works.
Please help me.Iam waiting for ur reply folks
Thanks in advance !
Sridhar

When connecting from sqlplus you must provide the as sysdba clause, type this when prompted
sys as sysdba
yourSYSPassword
You can try to connect directly by a command prompt:
sqlplus / as sysdba
It will connect directly to your database.
From the sqlplus (win) you can also try to write at the username prompt: / as sysdba
you are not required to type the sys password, as it is authenticated by the OS and no password is required for sysdba connections if connected directly on the console.
If you try to connect as system you will be prompted for a password. Only sysdba can be OS authenticated. SYSTEM password is the password defined at install time.
~ Madrid.

Oracle 9.2.0.1 Expert cannot collect statistics ( WindowsXP)

I have Oracle 9.2.0.1 and OEM with Diag and Tuning Pack WindowsXP SP1
When I try to collect statistics using Oracle Xpert I get
XP-21161: Database connection attempt has failed
ORA-28009: connection to sys should be as sysdba or sysoper
Cause: Expert was unable to establish the requested
database connection.
Action: Check the accompanying Oracle Server message for
a full description of the connection problem.
It is possible that the service specification
used in the connection attempt is not correct.
Expert accepts 3 types of service information:
o A database alias as defined in the
TNSNAMES.ORA file
o A Net8 descriptor block
o A network port specification using:
<host-name>:<database-port>:<database-sid>
I've tried messing with the Objects in left pane, changing username/password, making sure it says connect as sysdba with no luck, creating new DB object, connecting to a diff DB even. I know its connecting to the right DB cause it shows up in SYS.AUD$ as a logon attempt, but why wont it connect as sysdba?
Thank you I am a forum noob, this is my virgin(ia) post.

I also got the same problem but where i need to set thi parameter 07_DICTIONARY_ACCESSIBILITY=true.i tried in iit.ora but it was giving erro.Can u suggest me abt thi pls
Thanks
anand

Login to SQL Developer as the SYS user for Getting Started tutorial

I went to try and do the following tutorial to learn about SQL Developer 3.0, but I cannot get started because I'm unable to perform Prerequisite #3.
How do I "Login to SQL Developer as the SYS user"?
Dave
Getting Started with Oracle SQL Developer 3.0
Prerequisites
Before starting this tutorial, you should:
1 .
Install Oracle SQL Developer 3.0 from OTN. Follow the readme instructions here.
2 .
Install Oracle Database 11g with the Sample schema.
3.
Unlock the HR user. Login to SQL Developer as the SYS user and execute the following command:
alter user hr identified by hr account unlock;
Note: This tutorial is developed using Oracle SQL Developer 3.0.
4 .
Download and unzip the files.zip to a local folder on your file system. In this tutorial, we use the C:\sqldev3.0 folder.

I installed XE. It asked me to set up a username and password during the install.
How do I login as the SYS user, though?
There is a Connection Name, Username, and Password field when I try to set up a connection in SQL Developer, and I used the username and password I made during the install. I clicked the Test button to test the connection.
I see "Status: Failure -Test failed: ORA-28009: connection as SYS should be as SYSDBA or SYSOPER".
How do I tell SQL Developer "as SYSDBA or SYSOPER"?
Sorry, this is probably easy, and I'm just clueless about it.

How to solve the emca error

how to solve the warning and severe error....................
[oracle@ip-********* Oracle11g_R2]$ emca -deconfig dbcontrol db -repos drop
STARTED EMCA at Mar 29, 2012 10:20:41 PM
EM Configuration Assistant, Version 11.2.0.0.2 Production
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Enter the following information:
Database SID: testdb11g3
Listener port number: 1521
Password for SYS user:
Password for SYSMAN user:
Do you wish to continue? [yes(Y)/no(N)]: y
Mar 29, 2012 10:22:13 PM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at /u02/oracle/Oracle11g_R2/cfgtoollogs/emca/testdb11g3/emca_2012_03_29_22_20_40.log.
Mar 29, 2012 10:22:13 PM oracle.sysman.emcp.EMDBPreConfig performDeconfiguration
WARNING: EM is not configured for this database. No EM-specific actions can be performed.
Mar 29, 2012 10:22:13 PM oracle.sysman.emcp.EMConfig perform
SEVERE: Listener is not up or database service is not registered with it. Start the Listener and register database service and run EM
Configuration Assistant again .
Refer to the log file at /u02/oracle/Oracle11g_R2/cfgtoollogs/emca/testdb11g3/emca_2012_03_29_22_20_40.log for more details.
Could not complete the configuration. Refer to the log file at
/u02/oracle/Oracle11g_R2/cfgtoollogs/emca/testdb11g3/emca_2012_03_29_22_20_40.log for more details.
[oracle@ip-******* Oracle11g_R2]$ cd

tried but getting the same error.............
[oracle@ip-10-68-199-69 oracle]$ lsnrctl start
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 29-MAR-2012 23:37:21
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Starting /u02/oracle/Oracle11g_R2/product/11.2.0/dbhome_1/bin/tnslsnr: please wait...
TNSLSNR for Linux: Version 11.2.0.1.0 - Production
System parameter file is /u02/oracle/Oracle11g_R2/product/11.2.0/dbhome_1/network/admin/listener.ora
Log messages written to /u02/oracle/Oracle11g_R2/diag/tnslsnr/ip-10-68-199-69/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 29-MAR-2012 23:37:21
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u02/oracle/Oracle11g_R2/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u02/oracle/Oracle11g_R2/diag/tnslsnr/ip-10-68-199-69/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
The listener supports no services
The command completed successfully
[oracle@ip-10-68-199-69 oracle]$ sqlplus
SQL*Plus: Release 11.2.0.1.0 Production on Thu Mar 29 23:37:34 2012
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Enter user-name: sys/Ashwin
ERROR:
ORA-28009: connection as SYS should be as SYSDBA or SYSOPER
Enter user-name: sys/Ashwin as sysdba
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> startup
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> shutdown abort
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 1603411968 bytes
Fixed Size 2213776 bytes
Variable Size 402655344 bytes
Database Buffers 1191182336 bytes
Redo Buffers 7360512 bytes
Database mounted.
Database opened.
SQL> exit
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@ip-10-68-199-69 oracle]$ emca -deconfig dbcontrol db -repos drop
STARTED EMCA at Mar 29, 2012 11:55:28 PM
EM Configuration Assistant, Version 11.2.0.0.2 Production
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Enter the following information:
Database SID: testdb11g3
Listener port number: 1521
Password for SYS user:
Password for SYSMAN user:
Do you wish to continue? [yes(Y)/no(N)]: y
Mar 29, 2012 11:55:57 PM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at /u02/oracle/Oracle11g_R2/cfgtoollogs/emca/testdb11g3/emca_2012_03_29_23_55_27.log.
Mar 29, 2012 11:55:57 PM oracle.sysman.emcp.EMDBPreConfig performDeconfiguration
WARNING: EM is not configured for this database. No EM-specific actions can be performed.
Mar 29, 2012 11:55:57 PM oracle.sysman.emcp.EMConfig perform
SEVERE: Listener is not up or database service is not registered with it. Start the Listener and register database service and run EM Configuration Assistant again .
Refer to the log file at /u02/oracle/Oracle11g_R2/cfgtoollogs/emca/testdb11g3/emca_2012_03_29_23_55_27.log for more details.
Could not complete the configuration. Refer to the log file at /u02/oracle/Oracle11g_R2/cfgtoollogs/emca/testdb11g3/emca_2012_03_29_23_55_27.log for more details.

Ora 28009

Similar Messages

Maybe you are looking for