How to guess the "connect internal" password?

[Enrico Venturi]

Hello colleagues,
if I run the sqldba as root user (not in the dba group) when I try to connect internal I'm asked for the password; where can I find the password? Is there any configuration file???

thanks
Enrico

[Graham Cameron_1 · Accepted solution]

It cannot be done from root.
There is no password, this is an 'internal' account and needs to be done from oracle user.
Also connect internal is now deprecated.
From 8i onwards use 'connect / as sysdba'
(but I guess if you are running sqldba you are still on v7)
Whatever, it can't be done from root.

- Graham

[T G Manikandan]

Only a dba can do that.
From root you cannot connect as internal.
Add root user into dba group

[twang]

'CONNECT INTERNAL' and the issues that determine if a user has permission to connect internal or not. The details here apply to releases 7.0.16 through to 8.1. If using Oracle 7.1.6 or higher Oracle strongly advises you use the SYSDBA or SYSOPER privileges instead as 'CONNECT INTERNAL' may be removed after Oracle 8.1 .
It is quite common for the 'root' user to be required to have 'connect internal' privilege. Unfortunately it is also common for the root users primary group to be the group 'daemon' which precludes it from being allowed to connect internal. There are two ways to tackle this problem:
a) Make the root users PRIMARY group the DBA group
or b) Where available use the 'newgrp' command to change the users
primary group to the DBA group.
Eg: $ newgrp dbagroup
$ svrmgrl
SVRMGR> connect internal
This can also be used in shellscripts thus:
:
newgrp dbagroup <

[Yogeeraj_1]

hi,
-
You may also wish to have a look to an existing Oracle Support note #18089.1.
-
and to add to above replies, this is how it works!
-------------------------------------------
the sysdba trick is generally used to allow other NON-SYS users to connect. It is best to use your OWN account that has been granted sysdba!

Anyway, hopeful this will clear up the confusion and show how this works:


$ orapwd file=orapw password=foobar entries=40

I just recreated my password file with a password foobar. My sys password is NOT foobar


$ svrmgrl

SVRMGR> connect internal
Connected.

SVRMGR> startup
ORACLE instance started.
Total System Global Area 193073136 bytes
Fixed Size 69616 bytes
Variable Size 141639680 bytes
Database Buffers 45056000 bytes
Redo Buffers 6307840 bytes
Database mounted.
Database opened.

SVRMGR> connect sys/change_on_install@ora816dev
Connected.

that works OK, lets try as sysdba:

SVRMGR> connect sys/change_on_install@ora816dev as sysdba;
ORA-01017: invalid username/password; logon denied

there I got your error. My SYS password is change_on_install but the password file has foobar in it. SYS is special -- sys connecting as sysdba is like internal -- you have to use the password file password! Lets try that:

SVRMGR> connect sys/foobar@ora816dev as sysdba;
Connected.

SVRMGR> grant sysdba to scott;
Statement processed.

now, we'll see this does not hold true for other users:

SVRMGR> connect scott/tiger@ora816dev as sysdba;
Connected.

That worked great, now lets just modify sys's password (not really, didn't change it but Oracle won't notice that

SVRMGR> alter user sys identified by change_on_install;
Statement processed.


SVRMGR> connect sys/change_on_install@ora816dev as sysdba;
Connected.
SVRMGR>

Hey, now we can use change_on_install -- that is because altering SYS's password will sync up the password in the password file -- sys is a very very close cousin of INTERNAL. sys's password will be burned into the password file now. the password foobar is obsolete

SVRMGR> connect sys/foobar@ora816dev as sysdba;
ORA-01017: invalid username/password; logon denied
SVRMGR>
---------------------------------------------
hope this helps too!
regards
Yogeeraj