This content has been marked as final. Show 8 replies
user522961 wrote:Please, read the chapter "+Task 1-5-3: Selecting a Database Character Set+" of the installation guide linked below.
Thank you Nicolas.
In both cases :
-For UNICODE ?
-For Non UNICODE ?
Can you also give me the link for Install document for FSCM9.1 ? I did not find it here : http://docs.oracle.com/cd/E17566_01/epm91pbr0/eng/psbooks/psft_homepage.htmHere you go :
in tools 8.52, oracle DB 11 R2, non-unicode (AL16UTF16) three months ego, I have created some databases with NLS_LENGTH_SEMANTICS=BYTE. We reloaded them by datamover and ....
I was not careful to documentation which said :
You are required to set the NLS_LENGTH_SEMANTICS=CHAR init.ora parameter for any PeopleSoft
My questions :
-is it a great mistake ?
-any solution to avoid reconstruct and ???
It's not a mistake since you're on non-uinicode database.
From the documentation you're talinkg about, you could also read the following : +"PeopleSoft PeopleTools 8.48 and later introduced the ability to utilize an Oracle feature called CHARACTER LENGTH SEMANTICS for Unicode databases."+ That means in your case having the default value BYTES is the proper value.
So, is it a problem ? Well, it is a problem only the day you will want to change from non-unicode to unicode.
How to fix it ? I'm afraid, you'll have to rebuilt every single SYSADM's table after setting the parameter to CHAR and bounced the db.
But as long as you working in a non-unicode environment, you should not be so worried.