RE: column size - SQLPATH question
- From: "Mark W. Farnham" <mwf@xxxxxxxx>
- To: <painterman@xxxxxxxxx>, <zhuchao@xxxxxxxxx>
- Date: Thu, 21 Aug 2008 10:07:28 -0400
Try "which sqlplus" or "whence sqlplus" or whatever the correct name of that
command is for your shell. It will probably find a sqlplus file that is
probably a wrapper script that truss cannot execute.
_____
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of David Pintor
Sent: Thursday, August 21, 2008 9:51 AM
To: zhuchao@xxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: column size - SQLPATH question
Thanks for your mail.
It looks like the files are being opened indeed... these are the last
entries in staging:
...
open("/etc/ttysrch", O_RDONLY) = 8
open("/u01/oracle/ora92/rdbms/mesg/oraus.msb", O_RDONLY) = 8
open("/u01/oracle/ora92/sqlplus/mesg/sp1us.msb", O_RDONLY) = 3
open("/u01/oracle/ora92/sqlplus/mesg/sp2us.msb", O_RDONLY) = 4
open("/u01/oracle/ora92/sqlplus/admin/login.sql", O_RDONLY) = 8
open("/u01/oracle/ora92/sqlplus/admin/glogin.sql", O_RDONLY) = 11
The problem now is that I can't compare with production as when I truss the
sqlplus command in there I get the error below:
truss: cannot find/execute program: sqlplus
I'm trying to find out where is the truss problem coming from... but if you
have any other ideas in the meanwhile please let me know.
Thanks!!
David
2008/8/21 <zhuchao@xxxxxxxxx>
Try:
Truss -o /tmp/a.log sqlplus /
Exit
And grep open /tmp/a.log see which file the sqlplus opened?
Sent via BlackBerry by AT&T
_____
From: "David Pintor" <painterman@xxxxxxxxx>
Date: Thu, 21 Aug 2008 12:36:06 +0100
To: <oracle-l@xxxxxxxxxxxxx>
Subject: column size - SQLPATH question
Hello,
- Oracle 9.2.0.8.0
- Solaris 8
I have two servers as above. One for production and one for staging.
In both I have an oracle user, in which profiles I have the following lines:
export ORACLE_HOME=/u01/oracle/ora92
...
export SQLPATH=$ORACLE_HOME/sqlplus/admin
I have the same default glogin.sql in the SQLPATH for both but also a
login.sql with the following lines:
define editor=vi
set lines 150
set pages 999
The configuration looks exactly the same for me.
However, when I go to prod and type something like 'show parameter sga' I
get:
NAME TYPE VALUE
------------------------------------ -----------
------------------------------
lock_sga boolean FALSE
pre_page_sga boolean FALSE
sga_max_size big integer 3222769816
And the same in staging gives me:
NAME TYPE VALUE
------------------------------------ --------------------------------
------------------------------
lock_sga boolean FALSE
pre_page_sga boolean FALSE
sga_max_size big integer
2098694720
I don't understand why the size of the columns is different if all in
SQLPATH is exactly the same and the Oracle version (and patch) are at the
same level.
Any ideas?
Thanks for your help!
David
Other related posts:
