Erroneous disk full message during backup 
Author Message
 Erroneous disk full message during backup

I'm trying to backup a DB2 SMS DB under OS/2. The DB is about 3Gb and
the disk still has 10Gb available, yet I get a SQL2419N Disk full
message. I managed to export the DB into IXF files which I then imported
into an empty DMS DB (2 containers of 1.6 Gb each, even added a 3rd one)
created on another server but the backup still fails for the same
erroneous disk full code. We run DB2/2 2.1 (I know it's about time we
upgrade, tell my boss!)

Any hint or idea? Other DBs in same situations get backed up monthly
with no problem.

--
Luc Le Blanc



Tue, 17 Aug 2004 04:48:32 GMT
 Erroneous disk full message during backup

Luc,

Well, when DB2 2.1 came out the biggest disks were in the hundreds of
megabytes range.

I suspect this old version has a problem with files > 2G-1 (2^31-1)
bytes.

If this is the case, you might be able to backup to multiple paths.  I
don't remember if 2.1 supported this, but if it does, the backup should
be split across multiple files, giving you a better chance of being
within the 2GB limit.

And you really should upgrade <VBG>.  You'll run into more and more
problems like this.

Quote:

> I'm trying to backup a DB2 SMS DB under OS/2. The DB is about 3Gb and
> the disk still has 10Gb available, yet I get a SQL2419N Disk full
> message. I managed to export the DB into IXF files which I then imported
> into an empty DMS DB (2 containers of 1.6 Gb each, even added a 3rd one)
> created on another server but the backup still fails for the same
> erroneous disk full code. We run DB2/2 2.1 (I know it's about time we
> upgrade, tell my boss!)

> Any hint or idea? Other DBs in same situations get backed up monthly
> with no problem.

> --
> Luc Le Blanc

--
====================================
To reply, delete the 'x' from my email

Jerry Stuckle
JDS Computer Training Corp.

====================================



Tue, 17 Aug 2004 06:58:36 GMT
 Erroneous disk full message during backup

Quote:
> I'm trying to backup a DB2 SMS DB under OS/2. The DB is about 3Gb and
> the disk still has 10Gb available, yet I get a SQL2419N Disk full
> message. I managed to export the DB into IXF files which I then imported
> into an empty DMS DB (2 containers of 1.6 Gb each, even added a 3rd one)
> created on another server but the backup still fails for the same
> erroneous disk full code. We run DB2/2 2.1 (I know it's about time we
> upgrade, tell my boss!)

You're probably running into the 2GB file-size limit in OS/2.  Once you
hit the limit, the backup process can't write any more so it fails (with
the wrong message, alas).

The workaround is to have multiple streams of data in the backup:

   db2 backup db foo to C:\,C:\

This will create two backup files, each around 1.5G in size.  The RESTORE
utility knows to look for all the streams that you generated for the
BACKUP, so you won't have to do anything special there.

dave



Tue, 17 Aug 2004 06:30:59 GMT
 Erroneous disk full message during backup

I think it relates to an os limit.  2gig per file i think.

I suggest you search google.com, groups for the error message you get.
I think this has been answered in the past.

PM



Tue, 17 Aug 2004 00:45:55 GMT
 Erroneous disk full message during backup
David Mooney a crit :

Quote:

> > I'm trying to backup a DB2 SMS DB under OS/2. The DB is about 3Gb and
> > the disk still has 10Gb available, yet I get a SQL2419N Disk full
> > message. I managed to export the DB into IXF files which I then imported
> > into an empty DMS DB (2 containers of 1.6 Gb each, even added a 3rd one)
> > created on another server but the backup still fails for the same
> > erroneous disk full code. We run DB2/2 2.1 (I know it's about time we
> > upgrade, tell my boss!)

> You're probably running into the 2GB file-size limit in OS/2.  Once you
> hit the limit, the backup process can't write any more so it fails (with
> the wrong message, alas).

> The workaround is to have multiple streams of data in the backup:

>    db2 backup db foo to C:\,C:\

> This will create two backup files, each around 1.5G in size.  The RESTORE
> utility knows to look for all the streams that you generated for the
> BACKUP, so you won't have to do anything special there.

I tried the multiple destinations on the SMS DB but I get a SQL098C error with
SQLSTATE 58005, yet the backup disk has 14 Gb free while the DB directory is
2.11 Gb, with the biggest file holding 2.047Gb. This could be the problem: the
database's biggest file/table (same under SMS) has reached OS/2's file size
limit. Is this a valid reason to make the backup fail? Any solution or
workaround?

--
Luc Le Blanc



Sun, 05 Sep 2004 22:16:05 GMT
 Erroneous disk full message during backup

Quote:
> I tried the multiple destinations on the SMS DB but I get a SQL098C error with
> SQLSTATE 58005, yet the backup disk has 14 Gb free while the DB directory is
> 2.11 Gb, with the biggest file holding 2.047Gb. This could be the problem: the
> database's biggest file/table (same under SMS) has reached OS/2's file size
> limit. Is this a valid reason to make the backup fail? Any solution or
> workaround?

You're saying that one of the container files in the database itself has
reached 2G in size?  I would not expect that to cause the backup to fail,
since the backup utility should be able to read any file that the database
engine is able to create.  Are there any interesting messages in the
db2diag.log file?

dave



Mon, 13 Sep 2004 04:27:52 GMT
 Erroneous disk full message during backup
Hi, Dave,

Unfortunately, Luc is probably correct - the standard OS/2 calls only
allow up to 2^31-1 byte files.  Since his file is 2.047GB, it looks like
he's hit that limit.  I don't remember the exact return code OS/2
returns when it hits this limit, but I suspect DB2 backup is
interpreting it as disk full (it might even be the same RC).

A few fixpaks ago IBM added some new calls to OS/2 to handle larger
files - but they are new calls, not extensions of existing calls.  And
being new calls, they aren't compatible with older versions of OS/2.

What I don't understand is why the backup wasn't split when he used
multiple destinations.  Rather than the 1 2Gb file it looks like he got,
he should have had several smaller files.  

Quote:


> > I tried the multiple destinations on the SMS DB but I get a SQL098C error with
> > SQLSTATE 58005, yet the backup disk has 14 Gb free while the DB directory is
> > 2.11 Gb, with the biggest file holding 2.047Gb. This could be the problem: the
> > database's biggest file/table (same under SMS) has reached OS/2's file size
> > limit. Is this a valid reason to make the backup fail? Any solution or
> > workaround?

> You're saying that one of the container files in the database itself has
> reached 2G in size?  I would not expect that to cause the backup to fail,
> since the backup utility should be able to read any file that the database
> engine is able to create.  Are there any interesting messages in the
> db2diag.log file?

> dave

--
====================================
To reply, delete the 'x' from my email

Jerry Stuckle
JDS Computer Training Corp.

====================================



Mon, 13 Sep 2004 06:10:57 GMT
 Erroneous disk full message during backup

Quote:
> Unfortunately, Luc is probably correct - the standard OS/2 calls only
> allow up to 2^31-1 byte files.  Since his file is 2.047GB, it looks like
> he's hit that limit.  I don't remember the exact return code OS/2
> returns when it hits this limit, but I suspect DB2 backup is
> interpreting it as disk full (it might even be the same RC).

I understand that.  What I interpreted his message to say was that one of
his database containers had somehow made it past 2G and that the backup was
{*filter*} on that.  I would find that scenario to be somewhat surprising.

dave



Mon, 13 Sep 2004 23:46:54 GMT
 Erroneous disk full message during backup
Hi, Dave,

I understand.  I read it as  the directory had 2.11GB, but the largest
file was 2.047GB.  Depending on what he was using to see the file size,
it could actually be reporting in MB - or 2,047MB which would be about
2GB.

Quote:


> > Unfortunately, Luc is probably correct - the standard OS/2 calls only
> > allow up to 2^31-1 byte files.  Since his file is 2.047GB, it looks like
> > he's hit that limit.  I don't remember the exact return code OS/2
> > returns when it hits this limit, but I suspect DB2 backup is
> > interpreting it as disk full (it might even be the same RC).

> I understand that.  What I interpreted his message to say was that one of
> his database containers had somehow made it past 2G and that the backup was
> {*filter*} on that.  I would find that scenario to be somewhat surprising.

> dave

--
====================================
To reply, delete the 'x' from my email

Jerry Stuckle
JDS Computer Training Corp.

====================================



Tue, 14 Sep 2004 04:36:55 GMT
 
 [ 9 post ] 

 Relevant Pages 

1. Disk full message during installation

2. BUG: Dialog Box Opens During Backup Process Prompting You To Insert Disk

3. Error 3266 during disk backup

4. Full Database Backup During Online Possible!

5. Is the transaction log truncated during a full database backup

6. transaction log runs full during backup

7. ISM message during onbar backup

8. ISM Message during onbar backup

9. DBCC check can return erroneous message??

10. Seemingly Erroneous PK Message

11. A Strange Error Message when running Full Backup

12. Backup device vs. backup to disk


 
Powered by phpBB® Forum Software