Re: SQL Command list history on Linux

From: Sayan Malakshinov <xt.and.r_at_gmail.com>
Date: Tue, 9 Jan 2018 03:44:31 +0300
Message-ID: <CAOVevU6OfUTYCiqDDKmKeDZrHXCA9WfjnWQXY31AOVjj=a5hTw_at_mail.gmail.com>



Mladen,

SQLCl is Linux stuff... using SQLCl on Windows is illegal

I haven't understood your point, especially in context of this error, because you can get the same error on Linux too. Anyway, why do you think so? And when "*SQLCl on Windows is illegal*"?

*SQLcl 17.4.0.354.2224 on Oracle Linux 7.2:*

$ sql / as sysdba

SQLcl: Release 17.4.0 Production on Tue Jan 09 03:36:37 2018

Copyright (c) 1982, 2018, Oracle. All rights reserved.

Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

SQL> cd /tmp
SQL> !pwd
/tmp

SQL> store set settings replace
Wrote file /tmp/settings.sql
SQL> _at_settings
Autotrace Disabled
Usage: SET DESCRIBE [DEPTH {1|n|ALL}] [LINENUM {ON|OFF}] [INDENT {ON|OFF}] SP2-0158: unknown SET option beginning "setlongchu..." SQL> On Sat, Jan 6, 2018 at 11:34 PM, Mladen Gogala <gogala.mladen_at_gmail.com> wrote:

> On 01/04/2018 07:21 PM, Sayan Malakshinov wrote:
>
>> And I've just found another bug: If I save SQLcl settings with "store set
>> sqlplus_settings.sql replace" and execute _at_sqlplus_settings.sql to restore
>> them, SQLcl returns a couple of errors:
>>
>> SQL>store set sqlplus_settings.sql replace
>> Wrote file S:\sqlplus_settings.sql
>>
>>
> Sayan, SQLCl is Linux stuff. I know that it is written in Java and that
> Java is supposed to be portable, but using SQLCl on Windows is illegal in
> some states.
>
>
>
> --
> Mladen Gogala
> Database Consultant
> http://mgogala.freehostia.com
>
>

-- 
Best regards,
Sayan Malakshinov
Oracle performance tuning engineer
Oracle ACE Associate
http://orasql.org

--
http://www.freelists.org/webpage/oracle-l
Received on Tue Jan 09 2018 - 01:44:31 CET

Original text of this message