ASE database backup won't start - flushing some cache resolves this

[Former Member]

Hi,

Has anybody heard of the scenario where ASE database backup won't work and flushing some cache resolves this problem?

I seem to recall this may have been because of previous dbcc work that left the database in unusual state.

Feedback much appreciated.

Kind regards,

G.

[former_member188958]

What exactly do you mean by "doesn't work"?

Is an error output?

Does the command fail silently and just returns a prompt?

Does the command hang?

Is this a classic "dump database <dbname> to <device>" or a more recent variant such as a cumulative / incremental dump?

Local or remote dump?

If the command is hanging, output of dbcc stacktrace on the hanging spid may be helpful:

set switch on 3604

go

dbcc stracetrace(<spid>)

go

ASE version would be helpful.

-bret

[Former Member]

What exactly is meant by "flushing some cache"?  Which cache, where and how?

[Former Member]

Yes, I have... Long time ago, and I don´t remember the solution. It would help if you sent the ASE version string, OS version etc. e.g.

select @@version

uname -a

Good luck.

Jean-Pierre