oracle 9.2.0.6 platform aix 5.2 cannot get a sql prompt after sqlplus /nologin

[zronis]

After applying 9.2.0.6 ---
can no longer get in with sqlplus /nolog
must provide sqlplus user/pw
etc.

Problem does'nt appear with Linux.

[aix5t]racle:test92:/m01/home/dba/oracle
$ sqlplus /nolog

SQL*Plus: Release 9.2.0.6.0 - Production on Sat Jan 29 16:36:16 2005

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

SP2-0640: Not connected
SP2-0640: Not connected
Enter value for db_name:

[davey23uk]

scrap original post, whats in you login.sql / glogin.sql

bet it contains a select statement with &db_name in it

[zronis]

that it does

thanks

[rohitsn]

fact: SQL*Plus
symptom: Running SQL*Plus script fails
symptom: SP2-0640: Not connected
change: The following statements were added to the glogin.sql file:

column global_name new_value gname
Select Lower(User)||'@'|| Decode(Global_Name, 'SO817F1','sof1','HO817F1','hof1',
Global_Name) Global_Name
From Global_Name;
set sqlprompt '&gname> '
cause: The script contains the "/NoLog" parameter while calling
SQL*Plus. This means that no initial connection is established to the database.

Since glogin.sql gets executed when starting the SQL*Plus executable, the above
error gets generated if glogin.sql contains a select statement. The select
statement requires that a connection to the database has been established.



fix:

Do not use the "/nolog" parameter when calling SQL*Plus if glogin.sql
contains a select statement.

[jmodic]

Originally posted by davey23uk
scrap original post, whats in you login.sql / glogin.sql

bet it contains a select statement with &db_name in it

You don't need any SELECT to obtain the database identifier in SQL*Plus since 9.2. You have additional system-defined variable available, called &_CONNECT_IDENTIFIER that automaticaly obtains the value of your instance's SID. So in SQL*Plus you can simply define your sqlprompt without any selects by using:

SET SQLPROMPT '&_CONNECT_IDENTIFIER>'