Home | Previous Page | Next Page   Appendix E. Error Messages > Conversion/Reversion Messages >

Messages: A-C

Cannot revert constraint with id id (in syschecks).
Cause:

The database has a constraint that was defined in a version more recent than the one to which you are reverting.

Action:

Drop the specified constraint and retry reversion.

Cannot revert new fragment expression for index index, tabid id.
Cause:

The index fragmentation was defined in a version more recent than the one to which you are reverting.

Action:

Drop the problem index-fragmentation scheme and retry reversion.

Cannot revert new table fragment expression for table with id id.
Cause:

The fragmentation of this table was defined in a version more recent than the one to which you are reverting.

Action:

Drop the problem table fragmentation scheme and retry reversion.

Cannot update page zero.
Cause:

Attempt to write page zero failed.

Action:

Contact Technical Support.

Checking database name for revertibility.
Cause:

Indicates that start of the reversion checks on the specified database.

Action:

None required.

Conversion of pre 7.3 in-place alter started status.
Cause:

The database server is converting data structures for in-place alters to the new format.

Action:

None required.

Conversion of pre 9.2 database tablespaces status.
Cause:

The database server is converting tablespaces to the new format.

Action:

None required.

The conversion of the database name has failed.
Cause:

Indicates that the conversion of the specified database has failed.

Action:

Connect to the database. This action triggers conversion of the database. If it fails, the relevant error message appears. Contact Technical Support.

Converting database name...
Cause:

This message appears at the start of conversion of each database in the system.

Action:

None required.

Converting in-place alters to new format.
Cause:

The database server is converting data structures for in-place alters to the new format.

Action:

None required.

Converting 'onpload' database...
Cause:

Printed in online.log at the beginning of onpload conversion.

Action:

None required.

Converting partition header from version 7.x.
Cause:

The database server is converting the partition header page to the new format that contains the chunk number and offset.

This message is optional verbose output that is logged only if you start oninit with the -v flag.

Action:

None required.

Converting partition header page address.
Cause:

The database server is converting the partition header page to the new format that contains the chunk number and page offset.

This message is optional verbose output that is logged only if you start oninit with the -v flag.

Action:

None required.

Converting partition header pages status.
Cause:

This message tracks the progress of the conversion of the partition header pages. The status is identified as follows:

Action:

If the status is started or succeeded, no action is required.

If conversion of the partition header pages failed, restart the database server. It will attempt to continue converting where it left off in the restartable conversion phase. If this action fails, diagnose the problem, restore from tape, fix the problem, and retry conversion.

Converting partition keys to 9.2.
Cause:

The database server is converting the partition keys to the Version 9.2 format.

This message is optional verbose output that is logged only if you start oninit with the -v flag.

Action:

None required.

Converting partition name for databasename:tablename.
Cause:

The database server is converting the partition name for the databasename:tablename.

This message is optional verbose output that is logged only if you start oninit with the -v flag.

Action:

None required.

Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]