SP2-0734 when running Command File saved by plsdev8 in SQL*Plus

[Tim Scott]

I saw a similar post from over 10 years ago, but that related to data output, rather than for a sqlplus script that was saved.

I have never known sqlplus to be capable of ignoring the utf-8 byte order mark / signature in the script files it reads.

There does not seem to be an option to indicate whether or not this byte order mark should be saved. There is nothing evident to indicate that it is present and there does not appear to be an easy way to remove it.

Suggestions welcome.

Thanks,
Tim

 

[Marco Kalter]

If the UTF8 BOM is added, this indicates that your script contains Unicode characters beyond the Windows character set (as defined in the Regional Settings in the Windows Control Panel).

 

[Tim Scott]

That may be so - but SQL*Plus doesn't recognise it !

One can have a perfectly operational SQL*Plus script with Unicode characters in literals or comments, without the BOM.

As a general practice, I would discourage the inclusion of anything non-ASCII in sqlplus scripts, but that's for another thread

Can we have an option to never include the BOM ?
Thanks.

 

[Marco Kalter]

This is on the list of enhancement requests for version 9.0.

 

[Stian]

Have this been implemented?

I would very much like to disable the BOM.

 

[Marco Kalter]

There is an encoding option, but it can only be set to "Autodetect ANSI/UTF8" or "Always UTF8". The autodetect option should always work correctly.

 

[sorcerer]

I am having the same problem.

If I choose the "Autodetect ANSI/UTF8" option, the files are always saved as ANSI Win-1250 encoding, even if I open the file, that was previously converted to "UTF8 without BOM" in another tool.

I also would very much like to disable the BOM.

Regards,
Simon Cevc