Re: SQL*DBA and TWO_TASK

From: David N McCann <cs91dnm_at_brunel.ac.uk>
Date: Fri, 17 Jun 1994 10:41:47 GMT
Message-ID: <CrJF1n.86F_at_brunel.ac.uk>


In article <2tq1b7$1jad_at_postoffice.manassas.ibm.com> beal_at_lfs.loral.com writes:
>I am using Oracle 7.0.13 and SQL*NET 2.0. When I set TWO_TASK and run SQL*DBA,
>I get a prompt for a password when I connect internal. Could someone explain
>why this happens? Is there a way to connect internal without the password
>prompt? I know I can connect as sys and do the same things as connecting
>internal, but I wondering if there is a SQL*NET configuration file option
>to allow me to connect internal. Is there any relationship to the opassword
>file and what is this file used for?

You don't mention which platform you'r erunning on since CONNECT INTERNAL's security is quite platform specific. I've just fought a small battle to understand all this as I installed Oracle7 (7.0.15.4 for IRIX) and the basic point is that 'internal' over a net is protected.

You mention orapassword and this is available in UNIX, so I wonder if you've got that. If so, may I reccommend pages 2-13 and 2-15 of the ORACLE7 Server for UNIX Administrator's Reference Guide, and also pages 1-4 to 1-5 of the ORACLE7 Server Administrator's Guide, which (tries to) explain the setup for Connecting Internal.

        All the best,

        Come back to me if you think I can be of more help,

-- 
			David McCann

Computer Science Yr3                   Faculty Rep: All Comp.Sci Undergrads
Students Union Court Member (elect)    Board of Studies Rep: Comp.Sci 3
Tel: 0956 237670 (any time)            Student Council Rep: Comp.Sci
Received on Fri Jun 17 1994 - 12:41:47 CEST

Original text of this message