PARCONV phase Index could not be created ERROR

Question

Upgrading Solution Manger 3.2 to 7.0  Windows Nt SQL Server 2000
We are in teh PARCONV phase now and getting errors regarding tables with missing indexes.
Example from PARCONV.ELG file:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CONVERSION ERRORS and RETURN CODE in NCONV00.TS3
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2EEGT236 The SQL statement was not executed
2EEDI006 Index " " could not be created completely in the database
  Long text:
    Cause
      It was not possible to create the index in the database.
      This could be caused by the fact that an index with the same name
      exists in the database, but it is unknown to the ABAP/4 Dictionary.
      Activating the index in the ABAP/4 Dictionary is possible, but it is
      not possible to create it in the database.
    System Response
    What to do
      For more information about the cause of the error, analyze the SQL
      error messages in this log.
2EEGT221 Creation of secondary indexes for table "BBP_PDHGP" failed
  Long text:
    Cause
      There might be a SQL error.
    System Response
    What to do
      Check the SQL codes for errors.
2EEGT239 Error in step "BBP_PDHGP-STEP6"
2EEGT094 Conversion could not be restarted
  Long text:
    Cause
      The conversion could not be restarted, i.e. it was not possible to
      continue the conversion at the point where it was interrupted.
    System Response
    What to do
      Information about the cause of the error can be found in the restart
      log.
2EEGT236 The SQL statement was not executed
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I have gone into se14 the index name exists but the index doesn't exist on the database.  I've tried using the Create to create teh index on the databse but that fails with a name may already exist.
How to I clear these errors?
Thanks
Laurie  McGinley

Answer 1

It appears on all the ABAP Dictionary: Restart Log List, that the same error is occuring on creating the secondary indexes...
Database error 170 at EXE
Line 1: incorrect syntax near '('
Same error occurs if I use the SE14 to "Continue Adjustment".
Note 1180553 u2013 Syntax error 170 during index creation on SQL 2000 and
Note 1346662 u2013 Avoid index creation errors in 7.0 EHP and higher upgrades.
Note 1365755 - Scripts to fix fillfactor issues on SQLServer 2000
These seem to be the key.... but...
I ran the scripts in 1180553 ... no change in the errors.  In fact, there isn't a dbo.[TATAF~] table and the dbo.[TATAF] table doesn't have the 'With fillfactor" entry.  So i wonder if  I'm at a different phase?
I'm looking at 1365755 and think I'd like to give that one a try, but it says to unpack the ZIP file in the <upgr dir>\abap\bin directory.  Well there isn't one.  I have the upgrade dir \usr\sap\put and its subdirectories, but no \abap\bin dir.
So I'm not sure where to unpack this to give it a try.
Perhaps it would be better to go back to teh beginning of the UPGRADE (after PREPARE) and start again?
I didn't upgrade to SQL Server 2005 because the version of SolMan we are on isn't certified on it, so thought I'd get through the Sol Man upgrade then do SQLServer 2005... maybe need to rethink this to?
I'm open you suggesions, ideas, answers!
Thanks
Laurie McGinley
Edited by: Laurie McGinley on Sep 28, 2009 12:23 PM