InstantClient SQL * more and glogin.sql

SQL * more the default behavior is to
(a) loading login.sql in the current directory
(b) if there is no, put glogin.sql in the + $ORACLE_HOME/sqlplus/admin / + directory

Note of support described the same behavior InstantClient (10g) in + Glogin.sql is not used with Instant Client [946528.1 ID] + too.

The solution to InstantClient 10g is simple. Define + $ORACLE_HOME + variable, it points to your instantclient directory and create the path and the file "+... / sqlplus/admin/glogin.» SQL +'.

However, this now seems to have changed with InstantClient 11 g. This is what the client:
stat64("login.sql", 0xbf9f2c14)         = -1 ENOENT (No such file or directory)
brk(0x856e000)                          = 0x856e000
stat64("glogin.sql", 0xbf9f2c14)        = -1 ENOENT (No such file or directory)
He seeks login.sql in the current directory - as expected. But now, it seems also to glogin.sql in the current directory - and not in a common/shared as directory + $ORACLE_HOME/sqlplus/admin / +.

Which is just silly IMO - like why do glogin.sql now behave like login.sql ? Wait until it is in the current working directory? What is 'global' subject and forced to have a glogin.sql in every single directory you have on your client, where you run SQL * more?

The correct behavior should be to determine the directory of the module (i.e. instantclient dir where sqlplus was executed) and then look for the glogin.sql in there.

Am I missing something here? The old behavior can be executed somehow? Or is there a workaround that can be used?

Hi, for me

[http://docs.oracle.com/cd/B19306_01/server.102/b14357/ape.htm]

especialy:

The directory containing glogin.sql SQLPATH value. For example:

+SQLPath=/usr/lib/Oracle/10.2.0.1/client/lib:${SQLPath}+
Export SQLPATH

works great!

Tags: Oracle

Similar Questions

Maybe you are looking for