It did not have a max size set on the pool, but the pool was full enough that it could
not fit 5G more into it. This apparently is treated like a file size limit and tries
to dump the large file directly to tape (at least when the storage pool is not full
enough to trip the migration limits).
Hey Louis,
try doing a Q STGPOOL xx F=D on your disk pool and see what the MAXIMUM
SIZE THRESHOLD is set to. It might be that you disk pool only accepts files
to a maximum of say, 2 GB in size and the Oracle file are trying to backup
looks to be about 5 GB plus.
Rik
-
Thanks, I had looked at these and reset the Novell nodes, just yesterday, I didn't get
around to the Unix ones then or might have avoided this problem today. I did reset
the MAXNUMMP for this node (and my other old nodes), but as I said, I had already
migrated the pool. So, I will have to do
hange
To: [EMAIL PROTECTED]@SMTP@Exchange
cc:
Subject:Re: ANS1301E Error
Thanks for your suggestions.
Yes, I had available drives. The only other process using a drive
was a DB backup.
Yes, the disk pool is shared and was full eno
Thanks for your suggestions.
Yes, I had available drives. The only other process using a drive was a DB backup.
Yes, the disk pool is shared and was full enough that the 5G would not fit, so that
explains the tape mount attempt. But I can still find no reason for the job to fail.
We do have
Do you have available tape drives at that time (it appears that your
are going straight to tape). IF you are not going straight to tape, the DISK
area that you are trying to backup to can't hold your 5+GB file.
Mind you, that if the DISK pool is shared...it could be some percent f
