IBM Guide to Resolving SQL0601N and SQL0605W Errors in Database Migration

6320ch_migrating.fm Draft Document for Review July 28, 2004 7:33 pm

[2004.04.29 21:08:36] Error: [IBM][CLI Driver][DB2/NT] SQL0605W The index was not created because the index "DBUSR01.I0000433" already exists with the required description. SQLSTATE=01550

.

.

.

[2004.04.29 21:09:35] Info : CREATE INDEX I0000539 ON contract ( member_id ASC )

[2004.04.29 21:09:35] Error: [IBM][CLI Driver][DB2/NT] SQL0601N The name of the object to be created is identical to the existing name "DBUSR01.I0000539" of type "INDEX". SQLSTATE=42710

.

.

.

[2004.04.29 21:53:37] Info : SELECT MAX(trdrefamt_id) as maxId FROM trdrefamt

[2004.04.29 21:53:37] Info : SELECT * FROM keys WHERE KEYS_ID=-1214

[2004.04.29 21:53:37] Info : Executed command: update.wcs.bootstrap.keys

[2004.04.29 21:53:37] Event: Post migration ends.

[2004.04.29 21:53:37] Event: Migration has terminated successfully.

When we checked the log file after running the migration script we found numerous errors split up in 2 SQL codes ‘SQL0605W’ and ‘SQL0601N’.

Error SQL0605W

A sample of this error in the log:

[2004.04.29 21:08:36] Info : CREATE INDEX I0000433 ON accmbrgrp ( owner_id ASC )

[2004.04.29 21:08:36] Error: [IBM][CLI Driver][DB2/NT] SQL0605W The index was not created because the index "DBUSR01.I0000433" already exists with the required description. SQLSTATE=01550

This SQL code can be ignored as its more a info message than error. The description of the SQL code clearly tells us that the index already exists with the required criteria and thus can be ignored.

Error SQL0601N

A sample of this error in the log:

[2004.04.29 21:09:35] Info : CREATE INDEX I0000539 ON contract ( member_id ASC )

[2004.04.29 21:09:35] Error: [IBM][CLI Driver][DB2/NT] SQL0601N The name of the object to be created is identical to the existing name "DBUSR01.I0000539" of type "INDEX". SQLSTATE=42710

This error can have one of the following meanings:

The index is missing (regardless of the message saying that it already exists). To correct this the index has to be created manually:

212Keeping Commerce Applications Updated WebSphere Commerce 5.1 to 5.6 Migration Guide