> We ended up having to halt the server and restart it before we were able
> to complete a successful database backup. We ran into this problem when I
> had tried to delete many filespaces at one time. I believe it was to much
> for the database to handle. We've never had problems after the reboot.
>
>       -----Original Message-----
>       From:   Magura, Curtis [SMTP:curtis.magura AT LMCO DOT COM]
>       Sent:   Sunday, February 07, 1999 8:03 AM
>       To:     ADSM-L AT VM.MARIST DOT EDU
>       Subject:        Database Backup
>
>       Well I've reissued the command at a later time twice - NO LUCK. Also
> went
>       ahead and doubled the size of the log - NO LUCK.  Anyone know how to
> get
>       everything back in order?
>
>       ANR2362E command: Database backup is not currently possible -
> compressed log
>       records
>       exist in the current transaction checkpoint.
>       Explanation: A BACKUP DB command was issued but a database backup
> cannot be
>       started. Log
>       compression has recently taken place, and the compressed log records
> are
>       still part of the current
>       transaction checkpoint. After these log records are no longer part
> of the
>       current checkpoint a backup
>       can take place.
>       System Action: The server does not process the command.
>       User Response: Reissue the command at a later time.
>
>       Curt Magura
>       Lockheed Martin
>       Enterprise Information Systems
>       Gaithersburg Md.
>       301-240-6305