ASE Staging DB

Category	Exception	Description	Action
ASE	exception.db.asestagingdb.stagingdb.corrupted_manifest_file	After unmounting the database “{0}” on target host “{1}”, the manifest file does not exist or has zero bytes.	Try the operation again. If the problem persists, contact Delphix Support.
ASE	exception.db.asestagingdb.stagingdb.create_database.failed	For dSource “{0}”, failed to create a staging database	Make sure that the SAP ASE instance “{1}” on the staging host “{2}” is up, the database user “{3}” has privileges to create a database on the instance, the staging host has enough resources, and then try the operation again.
ASE	exception.db.asestagingdb.stagingdb.found_half_mb_fragment	For dSource “{0}”, failed to add {1} fragment of size {2}MB: By default fragment additions can only be done in full megabyte increments.	Contact Delphix support with the output of the following query run on your production instance for review: “SELECT * FROM master..sysusages WHERE dbid=db_id(‘‘)”
ASE	exception.db.asestagingdb.stagingdb.init_device.failed	For dSource “{0}” failed to initialize a device with name “{1}”, path “{2}”, size in bytes “{3}”	Make sure that the SAP ASE instance “{4}” on the staging host “{5}” is up, the database user “{6}” has privileges to create a device on the host, the staging host has enough resources, and then try the operation again.
ASE	exception.db.asestagingdb.stagingdb.load_database.failed	For dSource “{0}”, failed to load a source database dump	Make sure that the SAP ASE instance “{1}” on the staging host “{2}” is up, the user “{3}” has privileges to load a database dump on the host, the correct password was provided if the database dump is password protected, the staging host “{2}” has enough resources, and then try the operation again.