oracle user being prompted for group password

[Youlette Etienne_2]

Hello,

We have an oracle2 login that belongs to the dba2 group only (oracle2 and dba2 because we have 2 database environments installed, this login is for the Peoplesoft environment). The database was starting without any previous problems, but now it is prompting for a group password as follows:
$ svrmgrl
Oracle Server Manager Release 3.0.5.0.0 - Production

(c) Copyright 1997, Oracle Corporation. All Rights Reserved.

Oracle8 Enterprise Edition Release 8.0.5.1.0 - Production
With the Partitioning and Objects options
PL/SQL Release 8.0.5.1.0 - Production

SVRMGR> connect internal
Password:

Apparently this is not supposed to be happening. It looks as if the login is being prompted for a group password. I have not made any system changes between the time that this previously worked to now, and the dba has checked the oracle database. I of course have no idea what else to look at.

Any help will be greatly appreciated. Thanks

[Jean-Luc Oudart]

If oracle products have been installed with oracle group=dba , I think your oracle2 user must be in the dba group to perform connect internal.

JL

[Sanjay_6]

Hi,

Try to add oracle2 to dba group and oracle to dba2 group and see if that helps. Just edit /etc/group file and do that.

Hope this helps.

regds

[Youlette Etienne_2]

Thanks for your responses. We did additional searches on the forum and still did not find a solution. The dba will contact oracle as well.

Once again thanks for your help

--Youlette

[Jeff Schussele]

Are all the ORA_ variables correct for this user - SID, HOME, etc.?
Could the profile for oracle2 not be set properly - overwritten w/oracle user maybe?
PATH set properly - to correct SHLIB?
echo them to be sure.

HTH,
Jeff

[Niel Greeff_1]

Make sure the ORACLE_SID is set AND exported before running svrmgrl (check the .profile file for the user or any other startup scripts)

[T G Manikandan]

check whether you have a orapw file in the $ORACLE_HOME/dbs directory.
If that exists then delete it.

After deleting it,
Now set a new password using

The syntax is
orapwd -file= password=
$orapwd -file=$ORACLE_HOME/dbs/orapw
password=

Also it the orapw file is not there in the $ORACLE_HOME/dbs directory then
just check whether you have the

remote_login_passwordfile
entry in your init.ora file in the $ORACLE_HOME/dbs directory.

Post results back.

Thanks

[John Palmer]

Hi,

One thing that I've seen cause this problem is when you run svrmgrl and have the exported environment variable TWO_TASK set.

Try the following:

unset TWO_TASK
svrmgrl

Regards,
John

[Mark Waddington]

Oracle, by default, assigns the group "dba" as the OSDBA group (users delonging to this group have dba access). This is compiled into the Oracle executable at install time and does not depend on the group the ORACLE_HOME files or of the database files.

I beleive (but not positive) if you wish to have two differant OSDBA's for differant groups of dba's, it requires two ORACLE_HOME's.

The OSDBA group can be changed by recompiling and linking the Oracle executables. Instructions for doing this can be found on Oracle's metalink site and search for OSDBA. Since they vary by operating system and Oracle version, look for the ones that apply for you. You may also try in technet.oracle.com.


M

[Youlette Etienne_2]

Thanks to everyone who responded. The strangest thing happened. 2 days ago, the network admin disabled the switch port that this server was connected to. Of course I did not know this at the time and went into checking everything I could think of on the server, which was up and running fine, no system or network adapter problems. Then I asked the network admin if he was doing something on the network.

Anyway, he enabled the port. I guess this affected other things on the server because I noticed some strange behaviour with the newgrp command. I needed to reboot the server to make a kernel parameter change, and once the server was rebooted, the database started with no problems.

Well, that works for me!

[Jack C. Mahaffey]

To confirm John Palmers suggestion of removing TWO_TASK. I had the same problem with not being able to login as INTERNAL until I unset the TWO_TASK variable.

jack...