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

Messages: D-F

The database name has been converted successfully.
Cause:

Indicates successful completion of the conversion of the specified database.

Action:

None required.

Database name is not revertible...
Cause:

The database has failed one of the reversion checks and is not revertible.

Action:

Take action to correct the error displayed as a separate message.

Database name is revertible...
Cause:

The database has passed all reversion checks and is revertible to the specified version.

Action:

None required.

Database name: Must drop trigger (id = id_number).
Cause:

The database contains a trigger that was created in a version more recent than the one to which you are converting.

Action:

Drop the trigger with the specified trigger identification number and then attempt reversion.

Database name SUCCESSFULLY reverted...
Cause:

Indicates the success of reversion of the specified database.

Action:

None required.

... dropping sysmaster database.
Cause:

The database server is dropping sysmaster database during the reversion process.

Action:

No action is required.

The dummy updates failed while converting database name. This may imply data corruption in the database. If so, restore the original database with the tape backup. For more information, see output_file.
Cause:

During conversion of a database from a version earlier than Version 9.2, dummy update statements are run against the system tables in the database being converted. This message indicates failure in running one of these update statements.

Action:

To retry the dummy updates, run the dummy update script for your old database server version. For instructions, refer to the IBM Informix Migration Guide.

If data corruption occurred, restore the original database with the tape backup. For more information, see the IBM Informix Backup and Restore Guide.

The dummy updates succeeded while converting database name.
Cause:

During conversion of a database from a version earlier than Version 9.2, dummy update statements are run against the system tables in the database being converted. This message indicates successful completion of these updates.

Action:

None required.

Error in slow altering a system table.
Cause:

An internal error occurred while performing reversion.

Action:

Contact Technical Support.

External conversion aborted due to incompatible sysmaster database.
Cause:

The sysmaster database was not converted to the current database server version. A current sysmaster database is needed for external conversion to complete.

Action:

Drop the sysmaster database and reboot the database server. It will build a new sysmaster database and relaunch external conversion automatically.

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