RE: DBMS_OUTPUT changing spaces to tabs

From: Mark W. Farnham <>
Date: Wed, 5 Aug 2009 11:06:39 -0400
Message-ID: <>

Have you checked the contents of the glogin.sql and login.sql files? (Are you in fact invoking the PL/SQL block via sqlplus?)  

Now I've mentioned both glogin and login and that might seem strange. But if memory serves, it is possible due to permissions that oracle can read glogin while dherri cannot. Of course each account might have its own login.sql, or a login.sql found via $SQLPATH. Normally glogin.sql should be readable by the universe at a findable location, and it gets done first. JL has an FAQ posting on this I haven't read, but if my short memory tickler is insufficient it is likely his FAQ is both precise and accurate, and it is likely more digestible than the very fine manual.  

Good luck,  


From: [] On Behalf Of Herring Dave - dherri
Sent: Wednesday, August 05, 2009 9:34 AM To:
Subject: DBMS_OUTPUT changing spaces to tabs  

I'm stumped and need some help. I'm running on a Sun SPARC Solaris 10 (5.10) using Oracle My issue is that output from DBMS_OUTPUT.PUT_LINE is different between 2 OS users.  

When I run under my OS account, everything looks fine. But running under "oracle", some spots of the output have multiple spaces replaced with tabs.  

I'm running an anonymous PL/SQL block, which uses DBMS_OUTPUT.PUT_LINE to report on cursor activity. This is all wrapped in a .ksh script, connecting as the same Oracle user each time.  

When connected as "dherri" and running the script, output (saved to a file) looks fine. But when connected to the server as "oracle" and running the script, multiple spaces are replaced with tabs and lines beyond 61 or 62 characters are wrapped instead of extending to 80.  

My guess is there's some difference in an OS setting between the 2 accounts but I sure can't find it. I've looked for any env variable and stty differences and haven't found any. Any clues?  


Received on Wed Aug 05 2009 - 10:06:39 CDT

Original text of this message