EB12.1.3 Migration To UTF

[khaledharb72]

- We run dmu on our EBS 12.1.3 and report about 100 tables for data truncation for specific varchar2 columns

- How to solve such data; For example table GL_JE_HEADERS Fields (NAME, DESCRIPTION) need to shorten data for such field before conversion for about 300,000 records

- DMU didn't give me ability to update data using Cleansing Editor (Editor is read only)
- Also Oracle didn't support me in that ; only said to use EBS User Interface to update such fields


Finally what is the best solution for such data truncation problem !!!

[ErmanArslansOracleBlog]

The  length of the contents of those fields should fit your new Character set.

So tell me, from which character set are you trying to convert your database to UTF8?
Also send me the screenshot of the problem.. (I want to see the DMU screen)

[khaledharb72]

Need to convert database character set From  AR8MSWIN1256  to  AL32UTF8 

I send Excel attachment for sample of DMU Data Conversion truncation for columns Report 

Question:

. We found that minimize (shorten) EBS table field data to fit AL32UTF8 is applicable because it related to Key data like table MTL_SYSTEM_ITEMS_B field SEGMENT1

. We need to change nls_length_semantics from BYTE to CHAR on whole database 

  How to do that on already EBS Database data and does this solution applicable for EBS and can work ???

On Tue, Jan 15, 2019 at 10:21 AM ErmanArslansOracleBlog [via Erman Arslan's Oracle Forum] <[hidden email]> wrote:

The  length of the contents of those fields should fit your new Character set. 

So tell me, from which character set are you trying to convert your database to UTF8? 

Also send me the screenshot of the problem.. (I want to see the DMU screen) 

If you reply to this email, your message will be added to the discussion below:

http://erman-arslan-s-oracle-forum.2340467.n4.nabble.com/EB12-1-3-Migration-To-UTF-tp7067p7084.html

To unsubscribe from EB12.1.3 Migration To UTF, click here.

NAML

On Tue, Jan 15, 2019 at 10:21 AM ErmanArslansOracleBlog [via Erman Arslan's Oracle Forum] <[hidden email]> wrote:

The  length of the contents of those fields should fit your new Character set.

So tell me, from which character set are you trying to convert your database to UTF8?
Also send me the screenshot of the problem.. (I want to see the DMU screen)

---

If you reply to this email, your message will be added to the discussion below:

http://erman-arslan-s-oracle-forum.2340467.n4.nabble.com/EB12-1-3-Migration-To-UTF-tp7067p7084.html

To unsubscribe from EB12.1.3 Migration To UTF, click here.
NAML

[khaledharb72]

Need to convert database character set From  AR8MSWIN1256  to  AL32UTF8 

I send Excel attachment for sample of DMU Data Conversion truncation for columns Report 

Question:

. We found that minimize (shorten) EBS table field data to fit AL32UTF8 is applicable because it related to Key data like table MTL_SYSTEM_ITEMS_B field SEGMENT1

. We need to change nls_length_semantics from BYTE to CHAR on whole database 

  How to do that on already EBS Database data and does this solution applicable for EBS and can work ???

---------- Forwarded message ---------
From: khaledharb72 [via Erman Arslan's Oracle Forum] <[hidden email]>
Date: Wed, Jan 23, 2019 at 11:40 AM
Subject: Re: EB12.1.3 Migration To UTF
To: khaledharb72 <[hidden email]>

Need to convert database character set From  AR8MSWIN1256  to  AL32UTF8 

I send Excel attachment for sample of DMU Data Conversion truncation for columns Report 

Question:

. We found that minimize (shorten) EBS table field data to fit AL32UTF8 is applicable because it related to Key data like table MTL_SYSTEM_ITEMS_B field SEGMENT1

. We need to change nls_length_semantics from BYTE to CHAR on whole database 

  How to do that on already EBS Database data and does this solution applicable for EBS and can work ???

On Tue, Jan 15, 2019 at 10:21 AM ErmanArslansOracleBlog [via Erman Arslan's Oracle Forum] <[hidden email]> wrote:

The  length of the contents of those fields should fit your new Character set. 

So tell me, from which character set are you trying to convert your database to UTF8? 

Also send me the screenshot of the problem.. (I want to see the DMU screen) 

If you reply to this email, your message will be added to the discussion below:

http://erman-arslan-s-oracle-forum.2340467.n4.nabble.com/EB12-1-3-Migration-To-UTF-tp7067p7084.html

To unsubscribe from EB12.1.3 Migration To UTF, click here.

NAML

On Tue, Jan 15, 2019 at 10:21 AM ErmanArslansOracleBlog [via Erman Arslan's Oracle Forum] <[hidden email]> wrote:

The  length of the contents of those fields should fit your new Character set.

So tell me, from which character set are you trying to convert your database to UTF8?
Also send me the screenshot of the problem.. (I want to see the DMU screen)

---

If you reply to this email, your message will be added to the discussion below:

http://erman-arslan-s-oracle-forum.2340467.n4.nabble.com/EB12-1-3-Migration-To-UTF-tp7067p7084.html

To unsubscribe from EB12.1.3 Migration To UTF, click here.
NAML

Sample.Critical.EBS.DataTruncationIssues.xlsx (13K) Download Attachment

---

If you reply to this email, your message will be added to the discussion below:

http://erman-arslan-s-oracle-forum.2340467.n4.nabble.com/EB12-1-3-Migration-To-UTF-tp7067p7131.html

To unsubscribe from EB12.1.3 Migration To UTF, click here.
NAML

[ErmanArslansOracleBlog]

There ar 3 choices if you do NOT want dataloss ;

1)enlarge the columns size
2)migrate to CHAR semantics
3)shorten the data.

CHAR schemantics is not supported by EBS.
So what you can do is to enlarge the column size or shorten the data..
Hoıwever; I can't directly recommend any of these, because this is a standard table, and the data inside it is your data..
So, if your organization approves shortening the data, then you can proceed with that.. (I don't think they will approve it, but it depends on the data..)

Englarging the column seems promising, but since it is a standard table, I recommend you to open a SR and get approval from Oracle for that.

Please review this note ->  Changing the NLS_CHARACTERSET to AL32UTF8 / UTF8 (Unicode) in 8i, 9i , 10g and 11g (Doc ID 260192.1)

[khaledharb72]

- I know that you already done successfully a project for changing EBS database character set to UTF ; can you give me a guide line for what you really do !!!

- Our organization didn't approve shorten data Nor Oracle company support to enlarge field length !!!

- Why EBS didn't support CHAR schemantics .. varchar field will be same in length !!!

 On Wed, Jan 23, 2019 at 3:42 PM ErmanArslansOracleBlog [via Erman Arslan's Oracle Forum] <[hidden email]> wrote:

There ar 3 choices if you do NOT want dataloss ;

1)enlarge the columns size
2)migrate to CHAR semantics
3)shorten the data.

CHAR schemantics is not supported by EBS.
So what you can do is to enlarge the column size or shorten the data..
Hoıwever; I can't directly recommend any of these, because this is a standard table, and the data inside it is your data..
So, if your organization approves shortening the data, then you can proceed with that.. (I don't think they will approve it, but it depends on the data..)

Englarging the column seems promising, but since it is a standard table, I recommend you to open a SR and get approval from Oracle for that.

Please review this note ->  Changing the NLS_CHARACTERSET to AL32UTF8 / UTF8 (Unicode) in 8i, 9i , 10g and 11g (Doc ID 260192.1)

---

If you reply to this email, your message will be added to the discussion below:

http://erman-arslan-s-oracle-forum.2340467.n4.nabble.com/EB12-1-3-Migration-To-UTF-tp7067p7138.html

To unsubscribe from EB12.1.3 Migration To UTF, click here.
NAML

[ErmanArslansOracleBlog]

Again, you need to create an SR for this.
Yes, you should never modify the column size attribute in order to accommodate the existing data. Although the DMU allows this, Oracle E-Business Suite does not allow it and will not support a database with a modified column size.
For packaged applications like EBS, application owner (Oracle) should already configured the table columns to support uniform char sizes.

Also, ask your Superuser, if that data can be shortened somehow.