Encoding problem with Oracle 12c after update to dbForge 4

[SergeyPechenik]

We updated from dbForge 3 to version 4.

Oracle server: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
Collation:
NLS_SORT BINARY
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CHARACTERSET AL32UTF8

Columns type NVARCHAR2

But we get strange strings now. It's looks like that:
Original string: Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

readed string: \0L\0o\0r\0e\0m\0 \0i\0p\0s\0u\0m\0 \0d\0o\0l\0o\0r\0 \0s\0i\0t\0 \0a\0m\0e\0t\0,\0 \0c\0o\0n\0s\0e\0c\0t\0e\0t\0u\0r\0 \0a\0d\0i\0p\0i\0s\0c\0i\0n\0g\0 \0e\0l\0i\0t\0,\0 \0s\0e\0d\0 \0d\0o\0 \0e\0i\0u\0s\0m\0o\0d\0 \0t\0e\0m\0p\0o\0r\0 \0i\0n\0c\0i\0d\0i\0d\0u\0n\0t\0 \0u\0t\0 \0l\0a\0b\0o\0r\0e\0 \0e\0t\0 \0d\0o\0l\0o\0r\0e\0 \0m\0a\0g\0n\0a\0 \0a\0l\0i\0q\0u\0a\0.\0 \0U\0t\0 \0e\0n\0i\0m\0 \0a\0d\0 \0m\0i\0n\0i\0m\0 \0v\0e\0n\0i\0a\0m\0,\0 \0q\0u\0i\0s\0 \0n\0o\0s\0t\0r\0u\0d\0 \0e\0x\0e\0r\0c\0i\0t\0a\0t\0i\0o\0n\0 \0u\0l\0l\0a\0m\0c\0o\0 \0l\0a\0b\0o\0r\0i\0s\0 \0n\0i\0s\0i\0 \0u\0t\0 \0a\0l\0i\0q\0u\0i\0p\0 \0e\0x\0 \0e\0a\0 \0c\0o\0m\0m\0o\0d\0o\0 \0c\0o\0n\0s\0e\0q\0u\0a\0t\0.\0 \0D\0u\0i\0s\0 \0a\0u\0t\0e\0 \0i\0r\0u\0r\0e\0 \0d\0o\0l\0o\0r\0 \0i\0n\0 \0r\0e\0p\0r\0e\0h\0e\0n\0d\0e\0r\0i\0t\0 \0i\0n\0 \0v\0o\0l\0u\0p\0t\0a\0t\0e\0 \0v\0e\0l\0i\0t\0 \0e\0s\0s\0e\0 \0c\0i\0l\0l\0u\0m\0 \0d\0o\0l\0o\0r\0e\0 \0e\0u\0 \0f\0u\0g\0i\0a\0t\0 \0n\0u\0l\0l\0a\0 \0p\0a\0r\0i\0a\0t\0u\0r\0.\0 \0E\0x\0c\0e\0p\0t\0e\0u\0r\0 \0s\0i\0n\0t\0 \0o\0c\0c\0a\0e\0c\0a\0t\0 \0c\0u\0p\0i\0d\0a\0t\0a\0t\0 \0n\0o\0n\0 \0p\0r\0o\0i\0d\0e\0n\0t\0,\0 \0s\0u\0n\0t\0 \0i\0n\0 \0c\0u\0l\0p\0a\0 \0q\0u\0i\0 \0o\0f\0f\0i\0c\0i\0a\0 \0d\0e\0s\0e\0r\0u\0n\0t\0 \0m\0o\0l\0l\0i\0t\0 \0a\0n\0i\0m\0 \0i\0d\0 \0e\0s\0t\0 \0l\0a\0b\0o\0r\0u\0m\0.

Another one:
Was: У попа была собака он её любил, она съела кусок мяса он её убил, закопал её в могилу на могиле написал, у попа была собака он её любил...
Became: # ?>?0 1K;0 A>10:0 >= 5Q ;N18;, >=0 AJ5;0 :CA>: <OA0 >= 5Q C18;, 70:>?0; 5Q 2 <>38;C =0 <>38;5 =0?8A0;, C ?>?0 1K;0 A>10:0 >= 5Q ;N18;...

if i adding new string from new dbforge, in sql developer it looks like that:
䕮捯摩湧⁰牯扬敭⁷楴栠佲慣汥‱㉣⁡晴敲⁵灤慴攠瑯′⸲⁅䘠捯牥


How to solve this problem?

[alexa]

Could you please describe the way you are adding records and let us know where exactly you were setting NLS parameters?

Also, please provide us the CREATE definition of the table.

Are you using Direct or TNS?

You can send a reply straight to our support system at alexaATdevartDOTcom and supportATdevartDOTcom .

[SergeyPechenik]

1) Could you please describe the way you are adding records: The records was added in previos version of dbForge by table editor
2) let us know where exactly you were setting NLS parameters: NLS_NCHAR_CHARACTERSET = UTF8 , it has not been changed
3) Create script example:
CREATE TABLE ITEMSSTORE (
ID NUMBER(38, 0) NOT NULL,
BIGNUM38 NUMBER(38, 0),
BIGINTCOL NUMBER(19, 0),
INTCOL NUMBER(10, 0),
GUIDCOL RAW(16),
DATECOL DATE,
DATETIMEOFFSETCOL TIMESTAMP(6) WITH TIME ZONE,
DECIMALCOL NUMBER(28, 0),
STRINGCOL NVARCHAR2(2000),
DATETIMECOL TIMESTAMP(6),
TIMECOL INTERVAL DAY(2) TO SECOND(6),
CONSTRAINT ITEMSSTORE_PK PRIMARY KEY (ID)
4) We using direct mode, in TNS mode all works fine

[alexa]

Thank you for the reply.

We will investigate this issue and will answer you as soon as possible.

[alexa]

Sorry for the delay on this.

We will fix this issue in one of the next product builds and will notify you once it's available for downloading.

[SergeyPechenik]

Hello! Is there any progress on this issue? The problem is still relevant. (ver. 4.1.48)

[alexa]

The new version with the fix should be released within about 6 months.