# Save UTF-8 without bom in teamcoding

**URL:** <https://forums.toadworld.com/t/save-utf-8-without-bom-in-teamcoding/54797>\
**Category:** Toad for Oracle & DevOps Toolkit\
**Created:** [March 3, 2022, 4:18pm UTC](https://forums.toadworld.com/t/save-utf-8-without-bom-in-teamcoding/54797 "2022-03-03T16:18:51Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![martin.muhr](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@martin.muhr](https://forums.toadworld.com/u/martin.muhr)\
**Post date:** [March 3, 2022, 4:18pm UTC](https://forums.toadworld.com/t/save-utf-8-without-bom-in-teamcoding/54797/1 "2022-03-03T16:18:51Z")

</div>

Hi,  
when executing sql files generated via teamcoding i always get the following error:

SP2-0734: unknown command beginning "SET DEF..." - rest of line ignored.

I have already learned in the forum that the likely proble is that the files are encoded utf-8 with bom, so i tried to fix it by switching in the editor to utf-8 without bom. This did nothing.

is there any other configuration for teamcoding to do?`

Thanks in advance

---

<div class="post-metadata">

**Author:** ![JohnDorlon](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/johndorlon/32/9997_2.png) [@JohnDorlon](https://forums.toadworld.com/u/JohnDorlon)\
**Post date:** [March 3, 2022, 4:57pm UTC](https://forums.toadworld.com/t/save-utf-8-without-bom-in-teamcoding/54797/2 "2022-03-03T16:57:30Z")

</div>

I am fairly certain that SQL\*Plus can only take ANSI encoded files.

Have you tried Options -\> Files -\> General -\> Default Encoding? (Note, if you change that, it will not modify files already in Team Coding..it would affect new files)

---

<div class="post-metadata">

**Author:** ![martin.muhr](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@martin.muhr](https://forums.toadworld.com/u/martin.muhr)\
**Post date:** [March 4, 2022, 8:13am UTC](https://forums.toadworld.com/t/save-utf-8-without-bom-in-teamcoding/54797/3 "2022-03-04T08:13:40Z")

</div>

Hi,

thanks for your reply. i switched to uft-8 before because of problems with german specific characters. These result in an error when running them via sqlplus.

Ok i have now switched to UTF-8 deleted the files loaded them back in form toad:

 ![image](https://global.discourse-cdn.com/quest/original/2X/e/efcd6896ae8e3627c8845258f1432aec1269f369.png)

The error is still the same:

 ![image](https://global.discourse-cdn.com/quest/original/2X/d/d47b9f98c2d277c7997edef4d29e42bbe2dce109.png)

---

<div class="post-metadata">

**Author:** ![JohnDorlon](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/johndorlon/32/9997_2.png) [@JohnDorlon](https://forums.toadworld.com/u/JohnDorlon)\
**Post date:** [March 4, 2022, 1:59pm UTC](https://forums.toadworld.com/t/save-utf-8-without-bom-in-teamcoding/54797/4 "2022-03-04T13:59:13Z")

</div>

For me, SQL\*Plus only works with ANSI encoded file.

I get the same as you when I save as UTF-8. I get different (but also wrong) results when I use any of the other encodings. Can you specify a character set to use with ANSI so that German characters will work correctly?

Another possibility - you can use QSR instead of SQL\*Plus and it will handle all of these encodings.

---

<div class="post-metadata">

**Author:** ![ralph.schlueter](https://avatars.discourse-cdn.com/v4/letter/r/5daacb/32.png) [@ralph.schlueter](https://forums.toadworld.com/u/ralph.schlueter)\
**Post date:** [November 8, 2022, 11:08am UTC](https://forums.toadworld.com/t/save-utf-8-without-bom-in-teamcoding/54797/5 "2022-11-08T11:08:14Z")

</div>

SQL Plus works with UTF-8 (no BOM)

---

<div class="post-metadata">

**Author:** ![JohnDorlon](https://sea1.discourse-cdn.com/quest/user_avatar/forums.toadworld.com/johndorlon/32/9997_2.png) [@JohnDorlon](https://forums.toadworld.com/u/JohnDorlon)\
**Post date:** [November 8, 2022, 12:55pm UTC](https://forums.toadworld.com/t/save-utf-8-without-bom-in-teamcoding/54797/6 "2022-11-08T12:55:38Z")

</div>

For me, SQL\*Plus does not support unicode, even when encoded as UTF8 (no BOM). See below.

Please let me know some steps to make it work.

![SQLPlusUnicode2](https://global.discourse-cdn.com/quest/original/2X/7/7805f662351723f3e2e3931ebd60d652753496cc.gif)
