Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Connecting as INTERNAL

Re: Connecting as INTERNAL

From: Martin Haltmayer <Martin_Haltmayer_at_KirchGruppe.de>
Date: 1998/03/05
Message-ID: <34FEDF57.CC2230A8@KirchGruppe.de>#1/1

We had the same problem. In our case the "audit_dump_dest" directory was full. This directory is filled by *.aud files that are generated during "connect internal". If server manager cannot write to the "audit_dump_dest" directory a password is requested.

Martin Haltmayer

Douglas B. Dodson wrote:
>
> Hi,
>
> Problem: Connecting as INTERNAL now requires a password.
>
> Specifics:
> - Running Oracle 7.3.3.0.0 on a DEC Alpha running UNIX V4.0D.
> - "dba" and "oper" group ids are setup in the UNIX file /etc/group.
> - During the install (several months ago, I selected NOT to require a
> pasword for connecting as INTERNAL.
> - "oracle" userid setup which was a member of the "dba" UNIX group.
> - Until recently, I could log on to the host as "oracle", go into Server
> Manager (line mode), and CONNECT as INTERNAL without a password requirement.
> - The problem appeared this week, after a re-boot on the node.
> Note: this node was rebooted several times since the install
> and the password requirement never appeared.
>
>
> --
> Douglas B. Dodson Internet: DBD_at_ICF.HRB.COM
> HRB Systems, Inc.
> State College, PA USA
> 16804
>
> Disclaimer!
> ===========
> Any ideas or opinions expressed here do not necessarily reflect the ideas or
> opinions of HRB.
Received on Thu Mar 05 1998 - 00:00:00 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US