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

Similar Messages

Oracle 11R2 remote login as sysdba fails

Hello
i cant connect remotely as sysdba from client to server - oracle version SQL*Plus: Release 11.2.0.2.0
the configuration is the following
orapwd file=orapwdTESTDB entries=30 password=mypassword force=y
on the init.ora i have the following
remote_login_passwordfile=EXCLUSIVE
and while going to another server i keep getting the following error message
sqlplus sys/mypassword@testdb as sysdba
SQL*Plus: Release 11.2.0.2.0 Production
Copyright (c) 1982, 2010, Oracle. All rights reserved.
ERROR:
ORA-01031: insufficient privileges
What else im missing? i had this configuration in oracle 10G and worked fine
thanks

Did you ever get this to work? I'm having the same problem. If I remote to the server and log on directly as sys, I can do fine. If I try from my PC, I get the insuff priv error. I can connect to other databases fine from my PC, but not this particular one.
thanks,
Carl

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.

ORA-01031: when login as sysdba

We have Oracle 11.2 on Redhat 5.6. on the server box, I can login as sysdba by doing sqlplus / as sysdbaBut failed when I do sqlplus sys/****@cchdev as sysdba
ERROR:
ORA-01031: insufficient privileges or In sqlplus conn sys/****@cchdev as sysdba
ERROR:
ORA-01031: insufficient privilegesI suspect the password is wrong, then I changed password. But I got the same error when using new password.
I could login all three way above last time. WHat is wrong?

Here is the result od env|sort[oracle@cchORdev1 ~]$ env|sort
BI_CONFIG_DIR=/u01/app/obiee/server/Config
_=/bin/env
BI_OC4J_DIR=/u01/app/obiee/oc4j_bi
BI_RPD_DIR=/u01/app/obiee/server/Repository
CLASSPATH=/u01/app/oracle/product/11.2.0/dbhome_1/JRE:/u01/app/oracle/product/11.2.0/dbhome_1/jlib:/u01/app/oracle/product/11.2.0/dbhome_1/rdbms/jlib
CVS_RSH=ssh
G_BROKEN_FILENAMES=1
HISTSIZE=1000
HOME=/home/oracle
HOSTNAME=cchORdev1
INPUTRC=/etc/inputrc
KDEDIR=/usr
KDE_IS_PRELINKED=1
KDE_NO_IPV6=1
LANG=en_US.UTF-8
LD_LIBRARY_PATH=/u01/app/oracle/product/11.2.0/dbhome_1/lib:/lib:/usr/lib
LESSOPEN=|/usr/bin/lesspipe.sh %s
LOGNAME=oracle
LS_COLORS=no=00:fi=00:di=00;34:ln=00;36:pi=40;33:so=00;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=00;32:*.cmd=00;32:*.exe=00;32:*.com=00;32:*.btm=00;32:*.bat=00;32:*.sh=00;32:*.csh=00;32:*.tar=00;31:*.tgz=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.zip=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:*.bz=00;31:*.tz=00;31:*.rpm=00;31:*.cpio=00;31:*.jpg=00;35:*.gif=00;35:*.bmp=00;35:*.xbm=00;35:*.xpm=00;35:*.png=00;35:*.tif=00;35:
MAIL=/var/spool/mail/oracle
OBI_BASE=/u01/app/obiee/
OBI_PRESENTATION_CONFIG=/u01/app/obiee//web/config
ORA_ALERT_DIR=/var/oracle/diag/rdbms/cchdev/CCHDEV/trace
ORA_BI_HOME=/u01/app/obiee
ORACLE_BASE=/u01/app/oracle
ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
ORACLE_SID=cchdev
ORACLE_TERM=xterm
ORA_DUMP_DIR=/u05/oracle/dpdump
PATH=/u01/app/oracle/product/11.2.0/dbhome_1/bin:/sbin:/usr/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/oracle/bin:/u01/app/oracle/product/11.2.0/dbhome_1/jdk/bin
PWD=/home/oracle
SHELL=/bin/bash
SHLVL=1
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
SSH_CLIENT=10.2.0.54 6032 22
SSH_CONNECTION=10.2.0.54 6032 10.2.0.200 22
SSH_TTY=/dev/pts/1
TERM=xterm
TMPDIR=/tmp
TMP=/tmp
TNS_ADMIN=/u01/app/oracle/product/11.2.0/dbhome_1/network/admin
USER=oracle
[oracle@cchORdev1 ~]$Edited by: user623617 on Apr 16, 2010 12:11 PM

SQLPLUS login as SYSDBA

Hi Guys,
When I try to login as SYS, oracle complains that I should connect as SYSDBA or SYSOPER. Fine. Now I enter the login user as SYSDBA and enter the password..it fails. However, if I login as user scott and password tiger, I can login. Then from the SQL prompt I do:
connect SYS/<password> as SYSDBA;
and it works. So my question is, when I use the same <password> as login prompt and user as SYSDBA or SYSOPER, why does that fail and how can I change to make that work directly without loggin in as some other user and then manually change to SYS.
Thanks

you must use a special screen
http://machine_name.domain:port/isqlplus/dba
check your sqlplus manualAre you sure?
I always do:
http://machine_name.domain:port/isqlplusdba
Note that in that case you must use htpasswd before ...

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
+++++++++++++++++++++++++++++++

Login as sysdba for patch R12 problem

Hi,
I am trying to apply the patch 12.0.3 for R12.
On of the items is to run a script under a SYSDBA user, however I am not able to login as Sysdba, also not the sys user.
The scripts :
SQL> select * from v$pwfile_users;
no rows selected
Seems that my passwordfile is missing ?
Running orapwd gives me the following result :
[root@linux12 bin]# ./orapwd file=$ORACLE_HOME/dbs/orapw password=manager entries=30
Unable to find error file.
Anybody can help me ?

Yes it is ,see :
[root@linux12 ~]# echo $PATH
/oracle/VIS/apps/tech_st/10.1.3/perl/bin:/oracle/VIS/apps/tech_st/10.1.2/bin:
/oracle/VIS/apps/apps_st/appl/fnd/12.0.0/bin:/oracle/VIS/apps/apps_st/appl/ad/12.0.0/bin:
/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/jre/bin:/oracle/VIS/apps/apps_st/comn/util/unzip/unzip/unzip-5.50::
/oracle/VIS/apps/tech_st/10.1.2/bin:/usr/bin:/usr/ccs/bin:
/usr/sbin:/oracle/VIS/apps/tech_st/10.1.3/bin:/oracle/VIS/inst/apps/VIS_linux12/ora/10.1.3/opmn/bin
:/oracle/VIS/inst/apps/VIS_linux12/ora/10.1.3/Apache/Apache/bin:/oracle/VIS/apps/tech_st/10.1.3/Apache/Apache/bin:/oracle/VIS/apps/tech_st/10.1.3/oui/bin:/oracle/VIS/apps/tech_st/10.1.3/OPatch:/oracle/VIS/apps/tech_st/10.1.3/jdk/jre/bin:/oracle/VIS/apps/tech_st/10.1.3/perl/bin:/usr/bin:/usr/ccs/bin:/usr/sbin:/usr/lib/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/oracle/VIS/apps/tech_st/10.1.3/appsutil/jdk/bin:/root/bin
[root@linux12 ~]# path
[root@linux12 ~]#

Remote login as sysdba, ORA-01031

I am trying to connect to a remote database which is installed on HP-UX from Windows-XP machine, as sysdba.
1. When I try to login from sqlplus system does not prompt for the password and gives following error:
SQL> connect sys@dcoemrep as sysdba
ERROR:
ORA-01031: insufficient privileges
2. When I try to connect using Toad or on the local machine (HP-UX), I am able to connect as sysdba
3. I have configured the following parameters and other settings
a. Created the password file using orapwd utility on target box (HP-UX)
b. Changed remote_login_passwordfile to EXCLUSIVEc. Changed SQLNET.AUTHENTICATION_SERVICES to NONE in sqlnet.ora
d. I have also tried to change remote_login_passwordfile to REMOTE
e. Also tried Changing remote_login_passwordfile to EXCLUSIVE. Changed SQLNET.AUTHENTICATION_SERVICES to NTS in sqlnet.ora
Current Parameter Setting:
===========================================
SQL> show parameter remote
remote_archive_enable string true
remote_dependencies_mode string TIMESTAMP
remote_listener string
remote_login_passwordfile string SHARED
remote_os_authent boolean FALSE
remote_os_roles boolean FALSE
SQL> show parameter os
optimizer_index_cost_adj integer 100
os_authent_prefix string
os_roles boolean FALSE
remote_os_authent boolean FALSE
remote_os_roles boolean FALSE
timed_os_statistics integer 0
Current sqlnet.ora
===========================================
SQLNET.ORA Network Configuration File: C:\oracle\ora92\network\admin\sqlnet.ora
# Generated by Oracle configuration tools.
#SQLNET.AUTHENTICATION_SERVICES= (NTS)
SQLNET.AUTHENTICATION_SERVICES=(NONE)
#NAMES.DIRECTORY_PATH= (TNSNAMES)
TRACE_LEVEL_CLIENT = OFF
sqlnet.authentication_services = (NONE)
names.directory_path = (TNSNAMES, HOSTNAME)
names.default_domain = world
name.default_zone = world
automatic_ipc = off
Oracle Database Version
===========================================
Oracle9i Enterprise Edition Release 9.2.0.1.0

Hi,
i found a similar problem when we changed the sys password of a living instance of Oracle. First of all, check that the password you are typing is correct (with the pwDBNAME file). Toad saved the password? If you can see an error message restarting the db if you have a problem on this file. If you can perform all test on teh server avoiding to use the server string but just setting the SID. Are you sure that the server string points to the right db?
Hope this helps
Sam
Message was edited by:
Samuele Ghilardi

Unable to login as sysdba after installing ODAC and Oracle developer tools

Hi..I was able to login with
sqlplus / as sysdba and unlock scott account.
I then installed ODAC and now when i try to login as sysdba i get Insufficient privileges error.
also tried sys/password , sys/change_on_install, system/manager but no luck.
Please help.I am using a desktop and logged in as an administrator.

989994 wrote:
Hi..I was able to login with
sqlplus / as sysdba and unlock scott account.
I then installed ODAC and now when i try to login as sysdba i get Insufficient privileges error.
also tried sys/password , sys/change_on_install, system/manager but no luck.
Please help.I am using a desktop and logged in as an administrator.I think we are missing some information here. Are you trying to connect via Server Explorer?
If so, you need to choose the drop down box and set it to "SYSDBA".

Database Login - Can not login as sysdba

I have a userid for a database on a separate server. I can login as sysdba on the server with the database and from the OEM server. I can not login as sysdba from OEM. Is there a change that needs to be made to the password file or does there need to be password file on the OEM repository server?

What do you mean with OEM server here? Centralized gridcontrol server? That's a different concept, you connect to a specific administration user (often SYSMAN), 'sysdba' is not applicable here. Otherwise a server, which hosts a standalone DBConsole is not different from any other database server.
Werner

SYS login

hi all:
I am trying to config my oracle9i portal through the config Assistant. On the second step it asks for the SYS password and connect information.
In attempt to make sure that the SYS password is correct, I went and reset my SYS password and try to log in the DB as SYS, that is when the problem occurred. I keep on getting this error message saying that connection to sys should be as sysdba or sysoper.
It seems to me that the portal config assistant requires me to use SYS, but I can't use SYS to login the DB.
can some one help me with this problem ??
thanks in advance
james chen

Hi,
Both these statements will make you connect to the database as Sys user(as sysdba).
The first statements
sql > conn / as sysdbaThis will connect as sysdba to the database. THis is a windows Authentication method of connecting to the database. Username and password are authenticated at the Operating system level and while connecting to the database you dont need to give the login details. '/' means root user.
In the second statement
sql > conn sys/sys as sysdbaThis will also make you connect as Sys user(as sysdba) to the database. But the authentication mode is not Operating system rather it is Oracle authentication. In this case, Oracle's Password file will be used for the authentication. In your case Sys is the use and Password for sys is also sys. As sysdba means that you are the connecting as Sysdba which means super user in basic language

How can i find out how many users can login as sysdba using password file

can any one please tell me how can i find out how many users can login as sysdba using password file
please reply
asif

SYS@db102 SQL> select * from v$pwfile_users;
USERNAME                       SYSDB SYSOP
SYS                            TRUE TRUE
SYS@db102 SQL>

Only able to login as sysdba?

I just installed 11g2 on Redhat 5. I logged in using sqlplus as follows:
$sqlplus sys/abcabc as sysdba
I created a user as follows:
sqlplus> create user "xyz"
profile "DEFAULT"
identified by "abcabc"
default tablespace "MYTAB"
temporary tablespace "TEMP"
account unlock;
sqlplus> grant dba to "xyz"
sqlplus> commit;
sqlplus reported user created and dba granted. No errors were repored by sqlplus.
Now when I try to login as follows:
$sqlplus xyz/abcabc
I get a login prompt again and after 3 retries, I'm kicked out.
BUT, if I login as follows:
$sqlplus xyz/abcabc as sysdba
I get logged in.
What could be the problem? I've followed the exact same procedure for creating a user many times before and it always worked. What is different this time that I need to login as sysdba?
Thanks

sb92075 wrote:
Aman.... wrote:
Not sure how it worked for you in the past but its not a good way to create usernames and passwords.
Aman....different version behave differently regarding usernames & passwordsYep, just noticed that OP is using 11.2 which has case-sensitive passwords .
Aman....

Remote login in SM51 Fails / ECC 6.0 / HP-UX / Oracle 10

Hi All,
We had a cluster, 4 physical servers / 14 SAP Instances / HP-UX - Oracle 10G / ECC 6 EHP 3.
Basically we have a general RFC problem in the system. You can reproduce it simply in transaction sm51: In most of the instances whenever you try to change to an instance that has the same instance number than the one you are logged on at this moment, you will come back to this instance, e.g.:
you are logged on at host1_SID_01, start sm51 and try to change to the instances:
host2_SID_01,
host3_SID_01 or
host4_SID_01
(or you try to display the system log or other). You will see (System - Status) that you don't change to these instances but will stay on host1_SID_01.
We found the SAP Note 662895 - Remote login using SM51 Fails. In this note they refer to the error: "Transaction termination 14 025".
Now we have this error (we upgraded from SAP 46C with another error in sm21).
The problem is that we really donu2019t understand exactly what they want to do in the SAP Note 662895:
Summary
Symptom
Remote login in SM51 by double-clicking R/3 instances fails
Solution
You can use transaction SM51 to log in to another application server using RFC, without entering a password. Server "A"
Server "A"                                          Server "B"
        <--Remote logon via RFC   <--
GUI
      sm51
Double-click on the server B entry --->
If host name "B" was entered on server "A" as the gw/alternative_hostnames profile parameter, the local SAP gateway from server "A" is used when you log on to server "B". This results in the syslog message "Transaction termination 14 025".
The same error occurs if you try to open a new external mode on server "A".
Who is the origin server? Host A? Host B? In fact sometimes you can go from A to B and vice versa. So changing the gw/alternative_hostnames parameter doesn't appear to be a solution.
I would appreciate some tips about this Note / Problem.
Best Regards,
Erick Ilarraza

Hello, thanks a lot for your replyes.
Abhijeet Siras, the command /etc/ping <host> works prefectly.
Sergo,
Exactly we have 3 host each one with 4 dialog instances. 1 host with 2 dialog instances and one host with the central instance.
Not all instances have this problem, only the following combination:
     Origin                     Destination
host4_SID_01    - >     host1_SID_01
host2_SID_03    - >      host3_SID_03
host1_SID_01    --> host3_SID_01
host1_SID_02   -->     host3_SID_02
host1_SID_03   -->     host3_SID_03
host1_SID_04   -->     host3_SID_04
host2_SID_01   -->     host3_SID_01
host2_SID_02 -->     host3_SID_02
host2_SID_03 -->     host3_SID_03
host2_SID_04 -->     host1_SID_04
host2_SID_04 -->     host3_SID_04
host3_SID_04 -->     host1_SID_04
host4_SID_01 -->     host1_SID_01
host4_SID_02 -->     host1_SID_02
host4_SID_02 -->     host2_SID_02
host4_SID_02 -->     host3_SID_02
The problem is between *_NUMBER to *_NUMBER!
For example from Dialog Instance 3 running on host 2 to Dialog Instance 3 running on host 3
For example host4_SID_01 means the Dialog Instance 1 running on host 4.
Best Regards,
Erick Ilarraza

Error while login as sysdba for creating a new db

Hi DBAs,
i need to create a new database base, so trying to login as sysdba after exporting <ORACLE_SID> and <ORACLE_HOME> and getting the following error, need your help urgently.
SQL> conn / as sysdba
exec(): 0509-036 Cannot load program oracleDBDOC because of the following errors:0509-150 Dependent module /data/oracle/product/10.2.0.3/lib/libjox10.a(shr.o) could not be loaded.
0509-022 Cannot load module /data/oracle/product/10.2.0.3/lib/libjox10.a(shr.o)0509-026 System error: The file access permissions do not allow the specified action.
Regards
Asif

I am not very sure about the error but it seems to some permission related error on oracle binaries. Can you check those permissions.
Have you created pwd file for db ?
Cheers

Sys login as sysdba fails in OEM

Similar Messages

Maybe you are looking for