ASE LDB
| Category | Exception | Description | Action |
|---|---|---|---|
| ASE | exception.db.aseldb.source.backup_files.not.found | For database “{0}” backup files [“{1}”] were not found on the backup path “{2}”. |
Make sure that the backup files are available on the backup path. |
| ASE | exception.db.aseldb.source.dump_database.failed | Failed to dump the database “{0}” on instance “{1}” using backup server “{2}” |
Make sure that the backup servers are configured correctly between the source instance “{1}” and the staging instance “{3}”, and try the operation again. |
| ASE | exception.db.aseldb.source.dump_file.changed | For dSource “{0}”, the found dump file(s) [{1}] are not the same ones discovered previously. |
Make sure the files dumped originally are the same files we are finding now. |
| ASE | exception.db.aseldb.source.dump_file.checksum.failed | For dSource “{0}”, failed to get the checksum of dump file “{1}” at “{2}” for user “{3}”. |
Make sure the path is correct, the file exists at the given path, the directory and file has the correct permissions for the user “{3}”, and try the operation again. |
| ASE | exception.db.aseldb.source.dump_file.disappeared | For dSource “{0}”, the dump file(s) [{1}] were removed before they could be applied to the staging source. |
Make sure the Delphix Engine can reach the files in the designated backup load path. |
| ASE | exception.db.aseldb.source.dump_file.earlier | Dump file “{0}” was taken earlier than the latest backup applied to the database “{1}”. |
Choose a database dump taken after “{2}”. |
| ASE | exception.db.aseldb.source.dump_file.mismatch.db | For dSource “{0}”, dump files [{1}] do not belong to the database “{2}”. | Choose a different set of dump files. |
| ASE | exception.db.aseldb.source.dump_file.not_found | For dSource “{0}”, failed to find the dump file “{1}” at “{2}”. | Make sure the path is correct, the file exists at the given path, the directory and file has the correct permissions, and try the operation again. |
| ASE | exception.db.aseldb.source.dump_file.unloadable | For dSource “{0}”, the dump file “{1}” could not be loaded. | Make sure the path is correct, the file exists at the given path, the directory and file has correct permissions, and try the operation again. |
| ASE | exception.db.aseldb.source.dump_history.no_backups_found | For dSource “{0}” no full backups were found for source database “{1}”. |
Make sure that full backups are available and accessible on the load path and try the operation again. |
| ASE | exception.db.aseldb.source.dump_history.unable_to_find_hist | For linked source “{0}” unable to find history for backup taken at “{1}” using backup files [“{2}”] from dump history file. |
Make sure that “enable dump history” is configured correctly for the instance and perform a SnapSync using a backup that has corresponding history entry in the dump history file. |
| ASE | exception.db.aseldb.source.existing_dump_not_found | For dSource “{0}”, no new backups were found for source database “{1}”. | Make sure that full backups are created after “{2}” UTC and are available and accessible on the load path, and try the operation again. |
| ASE | exception.db.aseldb.source.incorrect.number.of.stripes | Incorrect number of stripes given. | Make sure the number of stripes provided as link parameters match the number of stripes of the backup used for linking. |
| ASE | exception.db.aseldb.source.no_backup.after.restore | For linked source “{0}”, validated sync detected a restore operation on the source database. |
Perform a full backup and manual sync operation to make sure validated sync can ingest subsequent transaction log backups. |
| ASE | exception.db.aseldb.source.restore_header.failed | Failed to restore the header for dump file “{0}” | Make sure the file exists and the backup location for the dSource and its contents are accessible and correct, and if it is a striped backup, all stripe files are available. Then perform a sync on the dSource. |