Script file in Schema Compare uses wrong encoding

Discussion of open issues, suggestions and bugs regarding database management and development tools for Oracle
Post Reply
amochoru
Posts: 6
Joined: Wed 18 Jul 2018 19:40

Script file in Schema Compare uses wrong encoding

Post by amochoru » Thu 19 Jul 2018 16:02

I am using the dbforge Schema Compare for Oracle tool but when I generate a script file through Synchronization, the file comes out with an encoding of UCS2-LE BOM which then has to be manually converted to UTF-8 using notepad++. What controls the encoding type when generating a script file through synchronization?

alexa
Devart Team
Posts: 2599
Joined: Fri 24 Jun 2011 14:17

Re: Script file in Schema Compare uses wrong encoding

Post by alexa » Thu 19 Jul 2018 17:22

We will review this and will answer you as soon as possible.

amochoru
Posts: 6
Joined: Wed 18 Jul 2018 19:40

Re: Script file in Schema Compare uses wrong encoding

Post by amochoru » Wed 25 Jul 2018 20:12

Are there any updates on this issue?

AlexandrS
Devart Team
Posts: 20
Joined: Mon 22 Jan 2018 11:27

Re: Script file in Schema Compare uses wrong encoding

Post by AlexandrS » Mon 30 Jul 2018 10:34

Hello,

You can edit the existing connection just set Use Unicode check box in the 'Advanced' tab.

amochoru
Posts: 6
Joined: Wed 18 Jul 2018 19:40

Re: Script file in Schema Compare uses wrong encoding

Post by amochoru » Tue 31 Jul 2018 20:53

I do have the use unicode check box checked but my sql file is still being set to UCS2-LE BOM.

alexa
Devart Team
Posts: 2599
Joined: Fri 24 Jun 2011 14:17

Re: Script file in Schema Compare uses wrong encoding

Post by alexa » Thu 02 Aug 2018 12:04

Could you please let us know if the 'Use Unicode' check box is selected for both Source and Target connections?

Also, could you please send us the sync script to supportATdevartDOTcom and alexaATdevartDOTcom?

Post Reply