Re: connect internal

You ought to be using either SYSDBA or SYSOPER privileges (pretty much the same as a role), as below:

Assuming you have logged into the base OS as "mike", connect to SYSTEM and issue this statement

  GRANT SYSDBA TO mike;

This places an entry into the Oracle password file, if indeed you have opted to use one, which you should.

After that, you can use this command to replace "CONNECT INTERNAL"

  CONNECT mike/xxxx AS sysdba

In "svrmgr", this will give you STARTUP and SHUTDOWN privilege, as well as several others. Using "sysoper" in place of "sysdba" gives you similar privileges - the only restrictions on SYSDBA are that you cannot issue the "CREATE DATABASE" or "RECOVER DATABASE UNTIL TIME" statements.

HTH Jeremy Russell

Mike Burden <michael.burden_at_capgemini.co.uk> wrote:

>I believe it is a special id (similar to system or sys (might be an alias
>or synonym of sys)) that logs on in the same way as $OPS accounts. You
>must be logged on to the base OS using the ID that installed Oracle.
>
>Something like that anyway. I not sure if I'm right but I believe that it
>is now left in for backwards compatibility. What should we use instead.
>$OPS accounts???
>
>Terry Kwok wrote:
>
>> I was wondering what does 'connect internal' mean when in the svrmgrl
>> mode?
>> Thank you
>
Received on Wed Mar 03 1999 - 06:56:18 CST