Media controller -- Disk full encountered

[kaissoun]

despite the disk is not full but i have this message :Media controller
-- Disk full encountered

[kaissoun]

DB2 8.2 on linux suse

[Matt Emmerton]

"kaissoun" <ka****@yahoo.fr> wrote in message
news:11*********************@g14g2000cwa.googlegro ups.com...

despite the disk is not full but i have this message :Media controller
-- Disk full encountered

How big is your database?

Some filesystems have single-file limits of 1GB or 2GB, which you may be
hitting if your database is larger than this. You can either recreate the
filesystem you're using for your backup to allow larger files, or you can
work around the problem by creating multiple directories (ie,
/backupfs/dir1, /backupfs/dir2, etc) and then specifying all of these on the
backup command. If your database was 3GB and you specified 4 files, then
you'd have 4 files of 750MB, all of which are under the 1GB filesystem
limit.

You may also be running into a ulimit limit. Do "ulimit -a" and see if
there is a limit on file sizes, and change it to "unlimited".

--
Matt Emmerton

[Knut Stolze]

Matt Emmerton wrote:

"kaissoun" <ka****@yahoo.fr> wrote in message
news:11*********************@g14g2000cwa.googlegro ups.com...

despite the disk is not full but i have this message :Media controller
-- Disk full encountered

How big is your database?

Some filesystems have single-file limits of 1GB or 2GB, which you may be
hitting if your database is larger than this. You can either recreate the
filesystem you're using for your backup to allow larger files, or you can
work around the problem by creating multiple directories (ie,
/backupfs/dir1, /backupfs/dir2, etc) and then specifying all of these on
the
backup command. If your database was 3GB and you specified 4 files, then
you'd have 4 files of 750MB, all of which are under the 1GB filesystem
limit.

You may also be running into a ulimit limit. Do "ulimit -a" and see if
there is a limit on file sizes, and change it to "unlimited".

Another possibility is that a long-running transaction wrote lots of logs
records and that filled up the disk. When this transaction is rolled back,
the logs are freed again (assuming circular logging).

--
Knut Stolze
DB2 Information Integration Development
IBM Germany

[kaissoun]

ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
stack size (kbytes, -s) unlimited
cpu time (seconds, -t) unlimited
max user processes (-u) 16384
virtual memory (kbytes, -v) unlimited

[kaissoun]

Log retain for recovery enabled (LOGRETAIN) = RECOVERY