Skip to Content

how to take transactional log backup in sybase ase 15.7?

Hello Experts,

I want to take transactional log backup from sybase as 15.7. But when i executed the following command it got some error.

dump tran PCD to "H:\SAP_DB_Backup\PCD\PCD_dbtrans16_12_2014_backup.bkp"

I searched in net , but i didn't get a proper answer.

Kindly help😢



trans.png (5.7 kB)
Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Dec 16, 2014 at 07:55 AM

    The 'dump tran' command can only be used to dump transactions to a dump file if the log has *NOT* been truncated.

    The message is stating that at some point since the last database dump someone/something has truncated the transaction log (ie, discarded completed transactions from the log).


    If you want to dump the log to a file (eg, to be used later for database recovery) then you'll need to:

    1 - find and disable whatever is truncating your log (eg, make sure db option 'trunc log on chkpt' is not enabled; make sure no threshold actions have been assigned to the logsegment segment which issue a 'dump tran/truncate'; make sure all dbo's/sa's are aware of the consequences of issuing 'dump tran/truncate' and make sure it doesn't occur again)

    2 - perform a full database dump (dump database)

    3 - perform the log dump (dump tran); this will need to be performed on a regular basis (eg, via recurring job/script, via threshold action on the logsegment segment)


    I notice from your sample 'dump tran' command that your file's name is not very unique (eg, it does not contain a datetime component).

    If you plan on taking regular dumps of the transaction log (eg, to keep the log from filling up) then you'll need to make sure each 'dump tran' command references a unique file name (eg, <dataserver>.<database>.YYYYMMDD.HHMMSS.logdump).

    If you issue the same dump command twice (ie, with the same name for the dump file) then each successive 'dump tran' command will overwrite the dump file of the previous 'dump tran' command ... which has the effect of discarding the previous dump ... which means you won't be able to recover your log dumps (if the need arises).

    Add a comment
    10|10000 characters needed characters exceeded

    • Good answer from Mark, but 1 thing missing...

      Why do you want to take the transaction log backup?

      If you just want to make sure the log is free and don't need the log for recovery, you might as well enable database option "trunc log on chkpt"

      If you still run into a log full situation, you might want to check long running transactions or increase the log size of that database

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.