• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Prevent JDE from creating Long data type in Oracle in table generation

tethys

Member
Hi
We are (unfortunately) still using JDE B7334 with an Oracle 11G1 database. We are currently implementing a mobile application and we have a new table that acts as an interface between JDE and the mobile app. The application requires a Notes field which we would like to be at least 4000 characters.
When we generate the table in JDE, the column in the Oracle table is generated as data type LONG.
In the data dictionary it is currently defined as Data type 20 (Variable String), Size 4000, Class VARLEN.

Long data types in Oracle are very difficult to manage in SQL because they cannot be parsed.
Does anyone know if there is a way to force JDE to generate the table with a different data type (VARCHAR2 or CLOB)?

Thanks, Paula
JDE 8.0, Oracle 11G1, AIX
 

peterbruce

Legendary Poster
Paula,

Would a "virtual table" work?

Leave the table specs in JDE as they are and create the table in the database with the notes column as VARCHAR or CLOB. Will JDE still work with the notes column? This may be risky and may not work.

Another option may be to reduce the length by 1 and see if a size under 4000 would create a different column data type.

Others may have other options or things you can try.

PS: Assuming a custom table and custom data dictionary items
 
Last edited:

peterbruce

Legendary Poster
Paula,

Have a look at the JDE table F986114A column JDAUDINFO if it exists in your JDE installation. In our installation (9.1 with Oracle Unicode database) the data type is NCLOB.
 

tethys

Member
Thanks Peter - in later versions JDE does not create Long variables because the data type is deprecated by Oracle. And we did try creating the column at 3000 but it still got created as a Long. I am considering a tag table with just the 4000 character variable in it and using Alter Table to set the column to varchar2 - similar to what you suggested.
 
Top