Re: need final word on sysdba
- From: "Randy Harris" <randy@xxxxxxxxxxxx>
- Date: Thu, 02 Feb 2006 22:27:10 GMT
"Mark D Powell" <Mark.Powell@xxxxxxx> wrote in message
news:1138907968.824552.60900@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Randy, you need to setup a password file to be able to connect as
sysdba remotely. Otherwise only local sysdba connects are allowed.
I suggest that you do not give the vendor the sys or system ID's.
Rather grant DBA to an ID created for the vendor. The vendor should
not need access to the actual Oracle account and likely just needs a
slew of database object DDL privileges, that is, system privileges like
CREATE TABLE, CREATE VIEW, Unlimited Quota, etc.... Some vendors even
know what privilege their application needs are you can just grant
these rather than sysdba or even DBA.
HTH -- Mark D Powell --
Thanks Mark. Your suggestions make a lot of sense to me. I just had
another vendor finally relent and supply a list of required privileges,
rather than insist on DBA, for their latest product update.
--
Randy Harris
tech at promail dot com
I'm pretty sure I know everything that I can remember.
.
- Follow-Ups:
- Re: need final word on sysdba
- From: Mark D Powell
- Re: need final word on sysdba
- References:
- need final word on sysdba
- From: Randy Harris
- Re: need final word on sysdba
- From: Mark D Powell
- need final word on sysdba
- Prev by Date: Re: oci7 and oracle10g
- Next by Date: Re: Oracle client driver
- Previous by thread: Re: need final word on sysdba
- Next by thread: Re: need final word on sysdba
- Index(es):
Relevant Pages
|
Loading