Hi
We are having problems on our BW system when trying to compress requests.
At the moment we're compressing a single request at a time, but more often than not end up using secondary logs, and when those are all used up, the job is cancelled, in which case a database rollback happens. During rollback, the system is unavailable for the 2-3 hours, so batch jobs are put on hold.
This is not ideal.
Is there a way to cancel a compress job, so that a database rollback doesn't happen?
Also, should we be reasonably expecting a compress of 13 million records to complete in an acceptable amount of time, or is this unreasonable.
Basis have already given us the maximum amount of logs, so we can't ask for more. We will also look at breaking the requests up into smaller pieces.
Regards,
Andrew