SAP Basis Tech Supports

Symptom
If you upgrade SAP systems with start releases 6.20, 4.6C, 4.6B, 4.5B and earlier on SQL Server 2000 to SAP systems based on SAP NetWeaver 7.0 EHP1, SAP NetWeaver 7.0 EHP1 SR1, or SAP NetWeaver 7.0 EHP2 (and higher), errors occur in phases PARMVNT_SHD and PARCONV_UPG.
This note describes how to avoid or to fix the errors.
This note is not required for SAP systems based on SAP NetWeaver 7.1 and higher
Other terms
SAP NetWeaver 7.0 EHP1 SR1, SAP NetWeaver 7.0 EHP2
Reason and Prerequisites
The rules how to build the DDL statements for SQL Server for the database object create/alter/drop are listed in report SDB2SMSS. The index creation schema in the SDB2SMSS report of the exchange table REPOSRC~ contains a clause (”WITH (ONLINE=OFF)”), which is not supported for SQL Server 2000 (MSSQL 8.00), but for SQL Server 2005 only and higher.
Therefore, upgrades of systems running on SQL Server 2000 encounter errors in phases PARMVNT_SHD and PARCONV_UPG while creating indexes For more information, see SAP note 1180553.
Solution
I How to avoid the index creation errors in phases PARMVNT_SHD and PARCONV_UPG

To prevent the errors in phases PARMVNT_UPG and PARCONV_UPG, you must use the file attached to this note (REP_SDB2SMSS_70.zip) and perform the following steps during the upgrade:
1. Perform the prepare phases of the upgrade (stages initialization, extraction, configuration, checks).2. After the checks step is finished, you are asked whether you want to continue with the preprocessing. Before doing this, unpack the attached REP_SDB2SMSS_70.zip file into the \abap\bin-folder of the upgrade directory, which by default, is the following directory: <drive>:\usr\sap\<SID>\upg\abap\bin.
The REP_SDB2SMSS_70.zip file contains the following files:Breakpoint file: SAPUPPHAS.BRKData file: R095171.Y7AControl file: K095171.Y7ABatch command file: REP_SDB2SMSS_70.bat
(Make sure that after unpacking these files, they are located in the \abap\bin-folder of the upgrade directory)3. Continue the upgrade.
The SAPUPPHAS.BRK in the abap\bin-folder of the upgrade directory causes the upgrade to stop before the phase MAIN_SHADOW/START_SHDI_FIRST.
At this point in time, the exchange tables are already imported and REPOSRC~ contains the SDB2SMSS version, which causes problems for SQL Server 2000.4. Execute the REP_SDB2SMSS.bat file as follows:a) Open a command prompt as OS user <domain>\<sid>admb) Change to the \abap\bin-folder of the upgrade directory.c) Run REP_SDB2SMSS.bat
This runs a R3trans-import of R095171.Y7A into the shadow schema and replaces the exchange table REPOSRC~’s SDB2SMSS with a patched version that is valid for SAP basis release 7.0 (and higher) and for database release SQL Server 2000.d) Check the created trans.log file to make sure that no error occurred.5. Continue the upgrade.
II What to do if you did not perform the steps described in section I and the errors occur in phase PARMVNT_UPG

To finish phase PARMVNT_UPG successfully, you have to repair the TATAF~ entries. For more information, see SAP note 1180553.
Perform the following steps:
1. Start the MS SQL Server Query Analyzer (or SQL Server Management Studio).2. Select the relevant database in the top line of the Query Analyzer and execute the following commmand:
update <sid>.[TATAF~]
set PRTEXT = ‘ ‘
where PRTEXT like ‘%WITH ( ONLINE=OFF )%’;
(<sid> is either dbo, or the name of the schema if you have system with a non-dbo schema)3. To avoid errors in the later phase PARCONV_UPG, you have to repair the SDB2SMSS of the shadow system.
To do this, unpack the attached REP_SDB2SMSS_70.zip file into the \abap\bin-folder of the upgrade directory, which is by default:
<drive>:\usr\sap\<SID>\upg\abap\bin4. Perform steps 4 and 5 as described in section I above.