| Nick Elson 2005-06-21, 9:23 am |
| Do you know that the occurrence is a hard assertion? In other words, does
it
persist after being detected? Even after rebooting the system?
If it turns out to be a soft assertion then rebuilding may not be helping
and
would not be necessary.
Even if it is a hard assertion, rebuilding should not be necessary. You
should
be able to recover from the backup and apply transaction logs (as per the
documentation) give you are make regular and proper backups.
Unfortunately I do not see any known bugs related to that assertion number
that had not been fixed in 7.0.4 ebf 3369 or earlier. But unfortunately
7.0.4 has reached the end of it's support so even if this is a limitation
or bug of the product, there will be not be any more bug fixes made
for it.
HTH
If not familiar with assertions, visit the document available at
http://www.ianywhere.com/developer/.../assertion.html
"Benny" <benny@holmedal.se> wrote in message news:42b7c08f@forums
-2-dub...
> One of our customers have serious problem with a ASA 7.0.4 build 3541
> after rebuild of the database it's takes about two, three days then we get
> the error again.
>
> --
>
> Mvh
> Holmedal Data AB
> Benny Jönsson
> +46 (0)431 747 00
> benny@holmedal.se
>
|