Re: sqlplus cannot connect without qualifier

On May 7, 11:13 pm, Jim Smith <usene..._at_ponder-stibbons.com> wrote:
> In message <1178588669.701731.86..._at_h2g2000hsg.googlegroups.com>,
> d..._at_davehockenberry.net writes
>
> >All:
>
> >I have the following setup:
> > - Server A - Ora10gR2 Win installed; db instance, tables, Stored
> >Proc, etc all configured and reachable
> > - Server B - Ora10gR2 Win installed, with customer app initially
> >using local Server B db instance; db instance, tables, Stored Proc,
> >etc all configured and reachable
> > - Reconfigured app on server B to use DB instance on server A
> >(tnsnames.ora); local Oracle server remain but services turned down;
> >custom app is correctly using db on server A, BUT.....
>
> >While some utiiites can correctly reach the remote Server A DB
> >(TNSPING), sqlplus and other utilities cannot reach the remote server
> >A DB unless fully qualified (e.g. sqlplus system/password not working,
> >but sqlplus system/password_at_dbname is working)
>
> >I have scrubbed the usual suspects (tnsnames, sqlnet, etc) to no
> >success. Funn thing is that I have this exact setup duplicated in a
> >seperte lab, and all of the utilities work, including sqlplus.
>
> >Any ideas?
>
> Without something to tell the client which server to connect to, you
> will always need to provide the service name in the connect string.
>
> tnsping can connect because you give it the service name on the command
> line.
>
> The usual way to do this is to set the environment variable LOCAL to the
> name of the remove service. On windows there is probably a registry
> equivalent.
> --
> Jim Smith
> Ponder Stibbons Limited <http://oracleandting.blogspot.com/>
> RSS <http://oracleandting.blogspot.com/atom.xml>

Jim,

You nailed it......based on your post, I referenced some Oracle materials on the LOCAL param for windows, set the variable to the correct SID at the persistent system level, and this fixed it.

Thanks again! Received on Tue May 08 2007 - 02:15:06 CDT