If this is your first visit, be sure to check out the FAQ by clicking the link above.
You may have to register before you can post: click the register link above to proceed.
To start viewing messages, select the forum that you want to visit from the selection below.
Are there any messages in the diag? Is it an online backup? Is it possible that somewhere along the way the archiving process stopped working - maybe the disk is full? Or that there's a transaction which spans all primaries and secondaries and cannot complete? If the database is across multiple nodes then ensure that you're looking on all nodes. There has to be a transaction out there which isn't committing. When the backup fails does it cite the log full condition as the reason?
I ran an offline backup to get the tablespaces back to normal and increased the log parameters, logfilesiz, logprimary and logsecondary to accomodate the transaction processing.