What I usually do to create a private DB link or stop or start another user's DBMS job, is to create a temporary procedure in that schema: conn system create or replace procedure yhuang.p as begin execute immediate 'create database link remotedb connect to remoteuser identified by thepassword using ''remotedb'''; end; / exec yhuang.p drop procedure yhuang.p; The advantage is you don't change that user's password even for a subsecond. So there's no risk in that respect. I wish Oracle would support "create database link theuser.linkname...", or give us a general method as Windows's "Run as" functionality. Yong Huang > Date: Wed, 20 Aug 2008 12:36:10 -0500 (CDT) > Subject: Re: Becoming a user - 10g issue > From: "Rich Jesse" <rjoralist@xxxxxxxxxxxxxxxxxxxxx> > > I've needed to do this in order to create private database links for a > particular schema. And as luck would have it, I documented the procedure > for public viewing: > > http://asktoad.com/DWiki/doku.php/howto_create_dblinks_database_links_in_another_schema > > As SYSDBA, these actions aren't normally in the Oracle audit trail, but > that's another thread... :) > > HTH! GL! > > Rich -- //www.freelists.org/webpage/oracle-l