Re: Connect as an INTERNAL

From: Gerard H. Pille <ghp_at_infosoft.be>
Date: 1996/07/18
Message-ID: <4sm0f7$g2n_at_news.Belgium.EU.net>#1/1

In article
<Pine.SGI.3.93.960715170241.8167B-100000_at_heart.engr.csulb.edu>, Shin-e Fan (shinfan_at_engr.csulb.edu) says...
>
>Hi,
> I try connect as an INTERNAL in sqldba, I was in the oracle
owner
>account and group id is dba, but it still said not enough privilige, how
>can I be connect as an INTERNAL and what is 'orapwd' can I use it to
>create an INTERNAL account, how.
>
> thanks in advance
> shinfan
>
Maybe you are using Multi Threaded Server, and user oracle is trying to connect via the listener (is environment variable TWO_TASK set when you are logged on as oracle?) while the listener doesn't accept external DBA's. In that case, 'unset TWO_TASK' or let the listener accept external DBA's.

-- 
Kind reGards
     \ /   |
      X    |
     / \   s
     Gerard

Received on Thu Jul 18 1996 - 00:00:00 CEST

This message: [ Message body ]
Next message: ps_at_netvigator.com: "Re: PL/SQL in FORMS won't understand ROWTYPE in procedure parameter"
Previous message: Gerard H. Pille: "Re: Help! SQL tuning: using ALL indexes"
In reply to: Shin-e Fan: "Connect as an INTERNAL"
In reply to DBA: "Re: Connect as an INTERNAL"
Next in thread: ps_at_netvigator.com: "Re: PL/SQL in FORMS won't understand ROWTYPE in procedure parameter"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message