Re: glogin, on windows, affecting all sqlplus sessions.

Sorry, but I see some confusion about glogin.sql and login.sql here.

When sqlplus is started it can run 2 scripts if found: a. glogin.sql in the sqlplus/admin directory under the Oracle home (global login)
b. login.sql in the directory where it is first found, searched in the order:

• current directory
• (Windows) directories in the SQLPATH variable or registry key \\HKLM\Oracle\Home<n>
• (Unix) directories in $ORACLE_PATH variable

So: if you have a Windows client, the glogin.sql in the *client* Oracle home will run. It has sqlplus commands in it, the exe runs on the client, its impossible for it to access the glogin.sql on the server.

Just an idea: you could set up a glogin.sql on each Windows client machine when Oracle software is installed that calls a script in a common directory that is always available for all users and writable for authorised people only. You will have only 1 script to maintain for the entire environment. An alternative is to set up the SQLPATH registry key and include a common directory where login.sql can be found, but if users have access to the registry they could change it again.. as they can with the local glogin.sql probably.

Galen Boyer <galenboyer_at_hotpop.com> schreef in berichtnieuws uadjnhq0c.fsf_at_standardandpoors.com...
| On Tue, 03 Dec 2002, kfarrell_at_belgariad.com wrote:
|
| > In a multi-user system (eg, Unix), you have to put the
| > glogin.sql in a directory that is read-accessible to all users
| > who log in. In a single-user system (eg, Windows), you also
| > have to put it in a directory that is read-accessible to all
| > users - most likely, on a shared network drive. In either case,
| > you have to set the SQLPATH environment variable.
|
| Okay. I guessed correctly then. I'll keep searching cause I
| should have been able to find this in the docs, but it didn't
| jump out at me in the "Configuring SQL*Plus" documentation.
|
| Thanks Karsten.
| --
| Galen Boyer
Received on Tue Dec 03 2002 - 13:02:03 CST