Install, Upgrades & Change Mgmt - JDE1 (MOSC)

MOSC Banner

Collation Conflict Issue in SQL Database after migration from 8.12 to 9.2

edited Jul 28, 2016 2:54AM in Install, Upgrades & Change Mgmt - JDE1 (MOSC) 5 commentsAnswered ✓

Hi All,

Recently we upgraded our PY environment from 8.12 to 9.2 on new servers, now we are facing problem of Collation mismatch, getting error while accessing data. we did following steps:

we restored mdf and ldf files to new 9.2 database server SQL Server 2014. but in 8.12 database server we used collation "SQL_Latin1_General_CP1_CI_AS" and in 9.2 JDE databases come default with Collation "Latin1_General_CI_AS_WS" so we changed the collation to "Latin1_General_CI_AS_WS". the upgrade processes completed successful.

Oracle support suggested to create new database with required collation and run the report R98403E to copy Business Data and Control Tables from current to new database but it is taking 1 and half day to complete so right now we are on Testing Phase and after two months we will go for Live so on that time we cannot wait long.

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

E1 Inst & Change Mgmt 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