I'm facing a strange behaviour with Forms 10g and NLS_LANG=UTF8.
DB 11G withcharset in AL32UTF8 on Linux
Forms 10G on Linux
We are currently upgrading our application form DB 10G to DB 11G + UTF8.
After coping DB data from 10G to 11G, we changed columns sementics from BYTE to CHAR in DB 11G.
Migration worked fine.
Now we try to connect our application in Forms 10G to the new DB 11G + UTF8.
First we faced the error ORA-01461"can bind a long value only for insert into a long column".
To solve this error, we specified the NLS_LANG=american_america.utf8 in default.env.
This problem is fixed now.
We have specified the following parameters while compiling:
The application runs fine except for some ITEMs which display #### when their content is too long.
For exemple with an ITEM Varchar2(5) length_semantics=NULL (So the compiler uses the NLS_LENGTH_SEMANTICS specified during compilation).
-- When I fill it with 'xxxxx' it works fine.
-- When I fill it with 'xxxxé' it displays '#####'. The ITEM behave like in Excell when cell data cannot be displayed in a whole.
Any idea on how I can avoid this behaviour ?
Thanks in advance.
It looks like you have compiled the form with UTF8 semantics, which (I believe) does not handle multi-byte characters.
But then you try to enter a non-8-bit character, é, which would make the number of bytes in the field > than the allowed length of 5.
So it makes sense that you would get a field overflow issue.
That AL32UTF8 character set has prevented earlier versions of Forms to fail at startup.
There is a bug in Forms 10.1.2.3 for when the length of an item in BYTE exceeds the CHAR data length # are displayed.
length('xxxxx') = lengthb('xxxxx')
length('xxxxä') < lengthb(xxxxä')
so you'll get #.
there is a one-off patch for that which number I can't remember. The patch is bundled in the last patch bundles for Forms #9593176 and #13095466 which will also give you the benefits of being able to run your 10g Forms with Java7 (though it's not certified).
We met again on the same subject.
Thanks for your help.
By giving me the number of the patch to apply, I saved hours of research in Metalink.
I really didn't know how to search on Metalink for this kind of issue.
Here is the link to the Bug explanation:https://support.oracle.com/epmos/faces/DocContentDisplay?id=728689.1
And the link to the one-off patch: https://support.oracle.com/epmos/faces/ui/patch/PatchDetail.jspx?patchId=7126045