Help | Site Map
Connecting Tech Pros Worldwide
 
 
LinkBack Thread Tools
  #1  
Old November 12th, 2005, 11:40 AM
schepers
Guest
 
Posts: n/a
Default Backup fails with SQL2059

Hello,

we are using AIX 5.3 and DB2 V8.2 Fixlevel 9.

The attempt to backup a database of 50 GB leads to a message
SQL2059 and a 1 GB-fragment of the backup although there is sufficient
free space in the filesystem.

The diag2log offers no clues.

Before moving to Fixlevel 9 the backup worked well even with larger
file size.

Regards,
Jörg

--
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/DB2-Backup-f...ict249578.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=864331
  #2  
Old November 12th, 2005, 11:40 AM
Phil Sherman
Guest
 
Posts: n/a
Default Re: Backup fails with SQL2059

I seem to recall seeing this error a long time ago on AIX systems when
there's plenty of space.

Try splitting the backup into two pieces in different directories. If
each goes to 1g then look for file size limitations. If the two files
grow to 500mb each and the backup quits; look for a quota issue. You'll
need assistance from your friendly system administrator to fix either.


Phil Sherman



schepers wrote:[color=blue]
> Hello,
>
> we are using AIX 5.3 and DB2 V8.2 Fixlevel 9.
>
> The attempt to backup a database of 50 GB leads to a message
> SQL2059 and a 1 GB-fragment of the backup although there is sufficient
> free space in the filesystem.
>
> The diag2log offers no clues.
>
> Before moving to Fixlevel 9 the backup worked well even with larger
> file size.
>
> Regards,
> Jörg
>[/color]
  #3  
Old November 12th, 2005, 11:40 AM
jdokos
Guest
 
Posts: n/a
Default Re: Backup fails with SQL2059

It looks like the ulimit for filesize is set to the default (1GB) for
the user that started db2. You can do ulimit -a as that user to
verify, or check the /etc/security/limits file (if you are unsure who
started db2) and confirm that all members of the SYSADM/CTRL/MAINT have
fsize set to -1. If a change is made to a ulimit you will need to
restart db2 as the settings are checked only at start time.

Jeff

 

Bookmarks

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

What is Bytes?

We are a network of experts and professionals in IT and software development that help one another with answers to tough questions and share insights. Get the best answers to your questions from over network members.
Post your question now . . .
It's fast and it's free

Popular Articles