Re: ORACLE Auto Start On ALPHA Boot

-- 
E-mail addresse




In article <1993Sep27.080117.805_at_condor.navsses.navy.mil>, system_at_condor.navsses.navy.mil (Mike Jacobi; CDNSWC 3582; Vax System Manager) writes:
Path: enterprise!butch!uunet!haven.umd.edu!darwin.sura.net!dtix.dt.navy.mil!condor.navsses.navy.mil!system
From: system_at_condor.navsses.navy.mil (Mike Jacobi; CDNSWC 3582; Vax System Manager)
Newsgroups: comp.databases.oracle,vmsnet.alpha
Subject: Re: ORACLE Auto Start On ALPHA Boot
Message-ID: <1993Sep27.080117.805_at_condor.navsses.navy.mil>
Date: 27 Sep 93 08:01:17 -0600
References: <1993Sep24.093807.20525_at_icf.hrb.com> <1993Sep25.173946.118957_at_embl-heidelberg.de>
Organization: CDNSWC, Naval Ship Systems Eng Sta, Phila PA
Lines: 25

In article <1993Sep25.173946.118957_at_embl-heidelberg.de>, hazledine_at_embl-heidelberg.de writes:


> kag_at_icf.hrb.com (Kevin A. Glossner) writes:


> 

>> I am attempting to startup ORACLE automatically on an APLHA upon bootup.
>> ...
>> Upon boot, I get an error indicating that a non-ORACLE User (SYSTEM) cannot
>> perform an ORACLE DBA command (CONNECT INTERNAL).
>> ...


> 

> Under VAX/VMS, the VMS usernames used to issue SQL*DBA commands need the VMS


> rights id ORA_DBA.  Could the absence of the rights id ORA_DBA from the SYSTEM

> username, or something similar, be the problem perhaps?

> 

 
>>With ORACLE7 on VMS an account with a SYSTEM UIC (uic group <= MAXSYSGROUP)
>>*CANNOT* perfrom DBA functions like database startup or shutdown.  What I am
>>doing to start ORACLE7 during the system boot is to have SYSTARTUP_VMS.COM
>>submit a batch job that starts ORACLE7 under the ORACLE7 username.


>>Mike Jacobi

I believe that one can use the SYSTEM account. The trick is to create & assign
the ORA_DBA (actually according to the documentation it should be
ORA_sid_DBA) identifier to the SYSTEM account. You will then be able to
do DBA type stuff from the the account. This is documented in the 
ora_root:[rdbms]readmevms.doc file (important part appended. Anyway, it works,
we use the SYSTEM account for DBA functions.

Section B.   CONNECT INTERNAL

==========   ================
        In order to have CONNECT INTERNAL privilege to the <sid> instance
on VMS, a user must be granted ORA_<sid>_DBA (or ORA_<sid>_OPER) in the VMS
rights database.  It is no longer possible to enable and disable these
rights in the current process (i.e., "$ set rights/enable ora_foo_dba" no
longer works). This is because ORACLE7 now looks for a user's rights in the
rights database instead of in the current process.







Internet	bjohnson_at_summit.decnet.lockheed.com


Brian Johnson

Speaking for myself. My company has nothing to do with this. This is my
opinion. No, I am not an expert. Ignore contents.