upgrade from 9.2.0.6 to 10G problem with user authentication

[Former Member]

we are calling dbua on solaris 10 for an oracle 10 upgrade and getting a screen up that shows the database ( in var/opt/oracle/oratab) to be upgraded, but we get

you do not have operating system authentication. Specify a user with SYSDBA privileges.

on our dev and qa environment we got this error but we added the o.s user orapr1 to o.s group dba and it worked. On the production it is not working, we have an orapw file , is this the problem??

any ideas

[Former Member]

Mike,

I believe this is related to user settings at OS level. ora<sid> user has to be part of dba group. I suggest that you get hold of oracle installation guide and read on this the topic. I have attached an extract from it.

Creating Required Operating System Groups and Users:

Depending on whether this is the first time Oracle software is being installed on this system and on the products that you are installing, you may need to create several operating system groups and users.

The following operating system groups and user are required if you are installing

Oracle Database:

&#9632; The OSDBA group (dba)

You must create this group the first time you install Oracle Database software on

the system. It identifies operating system user accounts that have database

administrative privileges (the SYSDBA privilege). The default name for this group

is dba.

If you want to specify a group name other than the default dba group, then you

must choose the Custom installation type to install the software or start Oracle

Universal Installer as a user that is not a member of this group. In this case, Oracle

Universal Installer prompts you to specify the name of this group.

&#9632; The OSOPER group (oper)

This is an optional group. Create this group if you want a separate group of

operating system users to have a limited set of database administrative privileges

(the SYSOPER privilege). By default, members of the OSDBA group also have the

SYSOPER privilege.

If you want to specify a separate OSOPER group, other than the default dba

group, then you must choose the Custom installation type to install the software

or start Oracle Universal Installer as a user that is not a member of the dba group.

In this case, Oracle Universal Installer prompts you to specify the name of this

group. The usual name chosen for this group is oper.

&#9632; An unprivileged user

Verify that the unprivileged user nobody exists on the system. The nobody user

must own the external jobs (extjob) executable after the installation.

The following operating system group and user are required for all installations:

&#9632; The Oracle Inventory group (oinstall)

You must create this group the first time you install Oracle software on the system.

The usual name chosen for this group is oinstall. This group owns the Oracle

inventory, which is a catalog of all Oracle software installed on the system.

&#9632; The Oracle software owner user (typically, oracle)

You must create this user the first time you install Oracle software on the system.

This user owns all of the software installed during the installation. This user must

have the Oracle Inventory group as its primary group. It must also have the

OSDBA and OSOPER groups as secondary groups.

A single Oracle Inventory group is required for all installations of Oracle software on

the system. After the first installation of Oracle software, you must use the same

Oracle Inventory group for all subsequent Oracle software installations on that system.

However, you can choose to create different Oracle software owner users, OSDBA

groups, and OSOPER groups (other than oracle, dba, and oper) for separate

installations. By using different groups for different installations, members of these

different groups have DBA privileges only on the associated databases rather than on

all databases on the system.

Note: If Oracle software is already installed on the system, then

the existing Oracle Inventory group must be the primary group of

the operating system user that you use to install new Oracle

software.

Note: In Oracle documentation, this user is referred to as the oracle

user.

See Also: Oracle Database Administrator's Reference for UNIX-Based

Operating Systems and Oracle Database Administrator's Guide for

more information about the OSDBA and OSOPER groups and the

SYSDBA and SYSOPER privileges.

[Former Member]

As you know, you can connect to the database as SYSDBA with a password file or with operating system authentication. (in this case: orapr1 should belong to dba groups)

To which groups does the OS User orapr1 belong?

You need a password file if you want to connect remotely as SYSDBA with a net service name (sqlplus sys/pw@TNS_NAME as sysdba)

But if you connect to the database using operating system authentication (see above), you must set the environment variable specifying the Oracle SID.

How are the environment variables set? e.g. ORACLE_SID, ORACLE_HOME, $PATH etc.

How is the DB Parameter REMOTE_LOGIN_PASSWORDFILE set?

[Former Member]

Hello Mike,

can you log on with this OS user on the database?

sqlplus sys/pw@SID as sysdba

or

sqlplus /nolog

connect / as sysdba

Best regards

Baran

[Former Member]

yes i can connect