Title: RE: sqlplus prompt question in 9i
Thanks David!
That's exactly what I am looking
for.
Guang
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of david hillSent:
Thursday, October 30, 2003 11:30 AMTo: Multiple recipients of list
ORACLE
Title: RE: sqlplus prompt question in 9i
It could be your sql
Here is the prompt I have been using for a while with no problems at all
If the db is down you get a prompt of
Nolog
set termout off
define new_prompt='nolog'
column value new_value new_prompt
select SYS_CONTEXT('USERENV
You could just use login.sql instead, on a per user basis.
If you don't want login.sql to be used, just edit or unset SQLPATH.
Maybe other options available for this in 9i. A perusal of the sqlplus
manual may prove useful.
Jared
Guang Mei [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
:
[EMAIL PROTECTED]Subject: Re: sqlplus prompt question
in 9i
.com
I had same problem with 9i, what I did is at the begining of the
dbstarup or stop script, I mv the glogin.sql to _old, at end of scripts
I mv back to the original name.
Joan
Guang Mei wrote:
Hi:
With Oracle 8i, I always modified $ORACLE_HOME/sqlplus/admin/glogin.sql, and
added
set
Joan:
Thanks for the reply. This would work if dbstart is called when starting
instance. But if I do it manually (although not often I would say), I need
to remember this and do it by hand.
Also I think you only need to do it with dbstart script, not dbshut.
Guang
-Original Message-
Guang,
You don't need to do it manually, you just type what it prompt you, it will
connect to database without any problem. It had problem in crontab batch job
only.
Joan
Quoting Guang Mei [EMAIL PROTECTED]:
Joan:
Thanks for the reply. This would work if dbstart is called when starting
