Siebel System Admin, Install and Upgrade (MOSC)

MOSC Banner

Running siebel upgrade in non-unicode mode on unicode database

in Siebel System Admin, Install and Upgrade (MOSC) 7 commentsAnswered ✓

Dear Team,

We were informed wrongly by our DB that the Siebel DB is non-unicode database and we executed Siebel Upgrade Processes (DEVELOPMENT and PRODUCTION modes) in non-unicode mode for DEV, UAT and PROD environments and all the upgrades are success ( including IRM in DEV) without any issues.

SIT and UAT with load testing went well. PROD sanity went well. We went live and it's been a week from now and observed no issues till now. Lot of transactions made in the application and all look okay.

Now, observed that few fields created with BYTE rather than creating them as CHAR. While researching on this, we found that our DB is unicode database. Since application running fine, can we leave this as is and use non-unicode for next repository migrations or should we fix this if there are any workarounds.??

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

SBL Sys Admin Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center