Re: need final word on sysdba

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 -- Received on Thu Feb 02 2006 - 13:19:28 CST