Use the sybdumptran utility to dump the most recent transactions when, due to the server suffering a catastrophic failure so that you cannot use dump tran with no_truncate.
Using dump transaction with no_truncate allows you to dump the last transactions and recover your database. The dump transaction with no_truncate command makes minimal use of the database when creating a transaction log dump. This ensures that no transactions are lost, allowing you to restore your database to its most recent point in time.
However, dump transaction with no_truncate does not work, when the failure is related to an incomplete Adaptive Server installation directory or a missing or corrupt master device, as dump transaction with no_truncate requires a working Adaptive Server in which the master database contains valid metadata from the database that failed.
When this type of a catastrophic failure occurs, use sybdumptran. This standalone utility generates a transaction log dump from the log pages contained in operating system files or raw devices, that were formerly used by the log segment of a database in an Adaptive Server environment. The log devices are located based on information stored in a recent database or transaction log dump, or another metadata file that sybdumptran can generate.
The sybdumptran utility allows you to obtain a transaction log dump of the as-yet-undumped portion of the transaction log in the case of an Adaptive Server catastrophic failure. sybdumptran, is unaffected by your inability to access parts of Adaptive Server, such as sysdatabases, sysdevices, and sysusages, which dump tran with no_truncate needs for information on where the log starts. With sybdumptran, even if such information is destroyed or unavailable, you can still obtain a transaction log, as long as the log devices are available.
sybdumptran [options] -o output_file