Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.misc -> Re: Spaces converting to Tabs
Is this running from different sessions and
different SQL*Plus logins, or always the
same Unix id and SQL*Plus login in the
same directory ?
For multiple SQLs it could be local login.sql.
For multiple Unix IDs it may be differen $SQLPATH again causing different login.sql.
For Multiple Unix IDs it may be something to do with the sed initialisation file (I think it uses .exrc ) which could be forcing some entab/detab algorithm.
One possible avoidance mechanism:
set space 0
set linesize 10
set trimspool on
etc.
select ltrim(to_char(seq.nextval,'0000000000')) from dual;
and cut out sed
You can also cut out the intermediate file with something like (the syntax will be shell-specific):
set m_var `sqlplus -s userid/pq <<-!!!
set commands to avoid garbage select ...... exit
--
Jonathan Lewis
Yet another Oracle-related web site: www.jlcomp.demon.co.uk
Wayne Miner wrote in message <7e1hp3$43_at_bolt.sonic.net>...
>Have a baffling situation.
>
>I'm running Oracle 7.3 on a Sequent Box, dynix operating system.
>
>We invoke sqlplus from a korn shell script, retrieve the nextval from
>a sequence generator, redirect the output to a file and...
>
>then fire up sed and replace all leading spaces with zeros.
>
>Things usually work fine, however (sporadically), if the nextval is a
>2 digit number (the sequence is defined as a NUMBER 10), the file
>contains a \t character, instead of the 8 leading spaces.
>
>This is causing some major headaches.
>I've verified that it is not terminal emulation.
>I don't see any obvious environment variables being set....
>This happens on at least two of the Sequent Boxes we're running
>
>Any ideas?
>
>Any suggestions sincerely appreciated
>
>Best Regards
>
>Wayne
>
>
>--
>
>Wayne Miner Speedware Programmer
>aka wayne_at_sonic.net
>Good things: Newfoundland Dogs, Am Flyer trains Bad things: The FDA
Received on Fri Apr 02 1999 - 02:34:20 CST
![]() |
![]() |