Hi All,

I"m attempting DB2 migration from V8 to V9. When i perform the db2ckmig everything turned out fine but when i do the actual migration it's indicating that the database is inconsistent. I checked the db cfg on the database and i noticed the following:

Database is consistent = NO

So, i tried to restart the db but still the db is inconsistent. Has anyone encountered this b4? If so how would i resolve it? Thanks.

Platform: Linux Intel

This information just tells you whether you have changes to the pages of the tablespaces belonging to this database in the buffer pools but not yet written to disk. In other words, some activity is already going on on the database and modifying data. Of course, DB2 won't even try to attempt to always have a consistent on-disk image of the database. Instead, it makes sure that all changes are written to the log and can be retrieved from there if needed. The data on disk is updated later at a more convenient time.

Ok but the migration will not work until the database is in a consistent state. How would i do that?

Attempted the migration again and we're getting the following error message:

DBI1205E One or more local databases have been detected that
cannot be migrated to the newest version. Check the
log file /data/db2inst1/migration.log for the list of errors.

Explanation:

Possible errors on the database are:

o Backup pending

o Roll-forward pending

o Database inconsistent

o One or more table spaces is not in normal state

o Database contains database objects that have a schema name of
SYSCAT, SYSSTAT or SYSFUN

o Database contains database objects that have a dependency on
the SYSFUN.DIFFERENCES function. Possible violated objects
are:

- constraint

- function

- trigger

- view



User Response:

Take the following corrective action for each database from the
file /data/db2inst1/migration.log :

o Backup pending - Perform backup of the database.

o Roll-forward pending - Perform a roll-forward database to end
of logs and stop.

o database inconsistent - Restart database to return it to a
consistent state.

o Table space not in normal state - Perform a roll-forward
database.

o Invalid schema - Drop the object and re-create the object
with a correct schema name (qualifier). If the object is a
table you should first export its data, drop the table,
re-create the table with a correct schema name, and then
import or load the data to the new table.

o Object having SYSFUN.DIFFERENCES dependency -

- Constraint - alter table to drop the constraint

- Function - drop the function

- Trigger - drop the trigger

- View - drop the view

Well, what exactly does the file /data/db2inst1/migration.log say about the issues?

The log is emtpy. I backed up the databases, and made the db's in consistent state. Would it be the instance itself? I'm getting error when i try to migrate the instance.

Have you verified all the possibilities listed in the error message shown above? Did you have a look at the db2diag output?

Yes attempted all

Ok, then I have no further idea myself. Maybe it's time to call IBM support.