Upgrade Fails at step RDDCP4TB (SQL Server 2005)

Question

During the process of upgrading to ECC 6.0 from 4.6c, you may also encounter the following error during the SAPUP step RDDCP4TB:
<b>BATCH JOB RDDCP4TB FAILED
SEVERE ERROR: Batch job "RDDCP4TB", job count "timestamp" aborted</b>
If you log into the system and check the short dump generated, you will find the following:
<b>SAPSQL_ARRAY_INSERT_DUPREC</b>
The system thinks that it is attempting to enter a duplicate record into the TADIR table, but in fact it is a collation issue.  In our particular case, the collation of the SAP database was correct, but the Server collation was not.  To check that your server collation is correct, run the following query:
<b>use <DATABASE>
go
declare @dbn sysname
set @dbn = db_name()
select 'Server' as [Type ],(select convert(varchar(30),
serverproperty('collation'))) as [Collation] union
select 'Master',(select convert(varchar(30),
databasepropertyex('master','collation'))) union
select 'Model',(select convert(varchar(30),
databasepropertyex('model','collation'))) union
select 'TempDB',(select convert(varchar(30),
databasepropertyex('tempdb','collation'))) union
select 'SID',(select convert(varchar(30),
databasepropertyex(@dbn,'collation')))
go</b>
Your results should be as follows:
<b>Server SQL_Latin1_General_CP850_BIN2
Master SQL_Latin1_General_CP850_BIN2
Model SQL_Latin1_General_CP850_BIN2
Temp SQL_Latin1_General_CP850_BIN2
SID SQL_Latin1_General_CP850_BIN2</b>
If your server collartion is different than this, detach the SAP database and uninstall SQLServer 2005.  Then reinstall SQLServer 2005 and make sure to set the following collation option:
<b>"Binary order based on code point comparison, for use with 850 (Multilingual)"</b>
See Note 505906 for more information on server collation.
Message was edited by:
        Joey Stephens

Answer 1

Dear,
Thanks for the information.
Best regards,
Lucio Rodrigues
SAP AGS