Dave,
In the last decade I've been on about 2 client sites where connecting to the
database directly from your desktop was possible.
For all of the others it's usually via something like an RSA token onto a jump
box in the data domain and connect from there, with limited or no
copy/paste/transfer of files to or from the jump box directly. On more secure
sites, it's usually on a totally different network not even accessible from
your normal workstation but via a different workstation (and very very
occasionally I'm not even allowed to touch the keyboard - somebody else does
that)
Neil Chandler
________________________________
From: Dave Herring <gdherri@xxxxxxxxx>
Sent: 04 January 2018 22:09
To: neil_chandler@xxxxxxxxxxx
Cc: Jeff Smith; oracle-l@xxxxxxxxxxxxx; gogala.mladen@xxxxxxxxx
Subject: Re: SQL Command list history on Linux
Maybe I'm missing something, but if you use SQLcl as a client and connect from
your laptop it gets past any issues of red tape, security clearance, etc.
Dave
On Thu, Jan 4, 2018 at 9:56 AM, Neil Chandler
<neil_chandler@xxxxxxxxxxx<mailto:neil_chandler@xxxxxxxxxxx>> wrote:
Jeff,
The main traction against sqlci isn't the several seconds to start rather than
pretty much instant sqlplus (this becomes a factor when calling sqlplus
multiple times in a loop), nor the fact it's far superior to sql*plus, but the
red tape, security clearance, patching, etc, required to get new software
(especially the Java component) onto the all of the DB servers. That pretty
much nobody is using 12.2 in Production yet compounds it, so the red tape is
required. There's nothing you can do about this that time won't cure except
make the sqlci case increasingly compelling.
I use vi and sqlplus because they are guaranteed to be there. If I was a perm
DBA in a company long-term, I'd probably raise the paperwork to get it onto
every DB server purely for the automatic column size adjustments if nothing
else. Love that.
Neil Chandler
________________________________
From: Jeff Smith <jeff.d.smith@xxxxxxxxxx<mailto:jeff.d.smith@xxxxxxxxxx>>
Sent: 04 January 2018 15:11
To: neil_chandler@xxxxxxxxxxx<mailto:neil_chandler@xxxxxxxxxxx>;
oracle-l@xxxxxxxxxxxxx<mailto:oracle-l@xxxxxxxxxxxxx>;
gogala.mladen@xxxxxxxxx<mailto:gogala.mladen@xxxxxxxxx>
Subject: RE: SQL Command list history on Linux
Slow to start? Maybe a second, or 3? If it’s taking longer than that, please
let me know.
Java 8u50 or higher will be ok, which is about 2-2.5 years old?
It’s a 20mb or so download, so takes less than a minute to install if you don’t
have it. Less time than it takes maybe to setup rlwrap…esp if you’re on Windows.
From: Neil Chandler
[mailto:neil_chandler@xxxxxxxxxxx<mailto:neil_chandler@xxxxxxxxxxx>]
Sent: Thursday, January 04, 2018 7:59 AM
To: oracle-l@xxxxxxxxxxxxx<mailto:oracle-l@xxxxxxxxxxxxx>;
gogala.mladen@xxxxxxxxx<mailto:gogala.mladen@xxxxxxxxx>
Subject: Re: SQL Command list history on Linux
Mladen,
What has that go to do with the original posters question?
If you are developing PL/SQL in SQL*Plus, you're probably not doing it
efficiently. SQL Developer is the better (free) tool for that, regardless of
platform.
SQLCI is great, but it's slow to start, requires a fairly recent Java release,
and only natively available from 12.2.
If you want Windows-like editing on a Linux SQL*Plus (or dgmgrl, rman or
whatever), use rlwrap.
regards
Neil Chandler.
Database Guy.
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx>
<oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx>> on behalf
of Mladen Gogala <gogala.mladen@xxxxxxxxx<mailto:gogala.mladen@xxxxxxxxx>>
Sent: 04 January 2018 10:57
To: oracle-l@xxxxxxxxxxxxx<mailto:oracle-l@xxxxxxxxxxxxx>
Subject: Re: SQL Command list history on Linux
On 01/02/2018 04:51 PM, Neil Chandler wrote:
Jeff,
My preferred solution is to install "rlwrap" [ e.g. "yum install rlwrap" -
check out
https://github.com/hanslub42/rlwrap<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_hanslub42_rlwrap&d=DwMFAw&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=N2hWu5HFsaIjmMkjQbnlokJ7uinNZMgPVk8rqPT9esM&m=0bds7QIoykh2KktiFwI5q5NtAunsmhvpPbDLFAGKbBY&s=cRMpNNnqbVGwt9R-SUJkdE4mCdC-1KZy0LkLX77BvUY&e=>
] it provides similar functionality to a windows CMD environment. You just
call the command you want to use via rlwrap
e.g. rlwrap sqlplus, or rlwrap dgmgrl
To keep thing simple, you can alias it
alias rsql='rlwrap sqlplus'
alias rdg='rlwrap dgmgrl'
regards
Neil Chandler
Hi Neil,
Rlwrap is not an equivalent solution. The "rlwrap" trick breaks editing of
PL/SQL code, which can be annoying. If you write a multi-line PL/SQL snippet
and something goes wrong, "ed" will only return a part of the snippet. SQLCl
will do the right thing and give you back the entire procedure. It has a
primitive screen editor built into the code because arrow keys also work when
editing the history commands. Also, SQLCl has "REPEAT" command which turns your
SQLCl session into an instant monitor, if necessary. In addition to all that,
there is Jeff Smith, who has been doing an outstanding job with the product and
explaining it on this list. Jeff is extremely helpful and a very nice guy. And
no, I don't work for Oracle Corp. and I don't plan on working for Oracle
anytime soon.
Regards
--
Mladen Gogala
Oracle DBA
http://mgogala.freehostia.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__mgogala.freehostia.com&d=DwMFAw&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=N2hWu5HFsaIjmMkjQbnlokJ7uinNZMgPVk8rqPT9esM&m=0bds7QIoykh2KktiFwI5q5NtAunsmhvpPbDLFAGKbBY&s=PcMyzBvpXVEJ8OtXmrHXL-cnBgMOPb4mBf88-fufLHU&e=>
--
Dave
