-
1. Re: sqlcl copy failing while it works with sqlplus
Glen Conway Dec 6, 2018 4:01 PM (in response to 3846595)So SQLcl says
Statement create table "SCMHISTORY.TRANSACTION_DATA_ITEMS"
which tells you it is incorrectly enclosing all of <schema>.<table> in double quotes rather than
doing "<schema>"."<table>" instead, as expected.
That looks like a bug, of course, but you can try changing your syntax to
1. Drop the schema name if it is not necessary, as in...
APPEND TRANSACTION_DATA_ITEMS using ...
or
2. Do the double quote enclosure correctly yourself, and maybe SQLcl will skip its own processing...
APPEND "SCMHISTORY"."TRANSACTION_DATA_ITEMS" using...
Cheers
-
2. Re: sqlcl copy failing while it works with sqlplus
3846595 Dec 6, 2018 6:22 PM (in response to Glen Conway)thanks, that seems to have done it.
-
3. Re: sqlcl copy failing while it works with sqlplus
Glen Conway Dec 6, 2018 7:26 PM (in response to 3846595)Out of curiosity, which of the two did you use? Most interesting would be if option (2) worked for you.
Also, please mark the question as answered so others with the same question will know to check here and so any responder can just skip over it.
-
4. Re: sqlcl copy failing while it works with sqlplus
3846595 Dec 13, 2018 1:52 PM (in response to 3846595)the second option worked.. it looked weird, as the insert results are like this <schema>"."<table>
but it did insert the data at the correct table at the destination database..
option one was not an option as I can not log on with the schema user.
-
5. Re: sqlcl copy failing while it works with sqlplus
3846595 Dec 13, 2018 1:53 PM (in response to Glen Conway)the second option worked.. it looked weird, as the insert results are like this <schema>"."<table>
but it did insert the data at the correct table at the destination database..
option one was not an option as I can not log on with the schema user.
-
6. Re: sqlcl copy failing while it works with sqlplus
Glen Conway Dec 13, 2018 4:48 PM (in response to 3846595)Interesting and weird but, as I commented earlier, the quoting logic must have a bug in it. We can hope that will get cleaned up in a future release. For now you have confirmed a workaround exists.