Urgent! problem with onload, please help!

Hello, We did an onunload of a database, but we failed to onload it after about 10 minutes or so, is anyone familiar with this error below and do you know a way to get around with it? onload -t mag_tempdb.onuld -b 64 -s 0 -d mag_tempdbdbs mag_tempdbPlease mount tape and press Return to continue ... pagesize of the target dbspace does not match with the pagesize of the partition on tape. ISAM error: Tape might contain a corrupt page (or) if you are executing onloadcommand specify the correct DBspace name using the -d argument. What I've found that most of "mag_tempdb" database's tables reside in mag_tempdbdbs except for one table resides in a different dbspace with a different page size (16K instead of 4K) -- would this be a problem for "onload"? I've had a case open with IBM and they don't have a solid answer for me yet. Thanks in advance. Kern --

Yes. Onunload and onload deal with page images of the table you are loading/unloading. Therefore you must load the data into a dbspace with the same page size as the dbspace that it was extracted from. To migrate data from one dbspace to another with different page sizes within the same server use the ALTER FRAGMENT...INIT IN... statement. To migrate to a different server you either have to unload the data using the dbaccess UNLOAD command and reload it using LOAD or the dbload utility, use Jonathan Leffler's sqlcmd tools to do the same thing, or use my dbcopy utility to copy the data directly from one server to the other. (Dbcopy is part of the package utils2_ak available for download from the IIUG Software Repository - www.iiug.org/software or the Oninit web site - www.oninit.com/utilities.) Art On Sat, Jan 3, 2009 at 10:50 AM, Kern Doe <kern_doe@yahoo.com> wrote: > Hello, > We did an onunload of a database, but we failed to onload it after about 10 > minutes or so, is anyone familiar with this error below and do you know a > way > to get around with it? > > onload -t mag_tempdb.onuld -b 64 -s 0 -d mag_tempdbdbs mag_tempdb> Please mount tape and press Return to continue ... > pagesize of the target dbspace does not match with the pagesize of the > partition on tape. > ISAM error: Tape might contain a corrupt page (or) if you are executing> onload> command specify the correct DBspace name using the -d argument. > > What I've found that most of "mag_tempdb" database's tables reside in > mag_tempdbdbs except for one table resides in a different dbspace with a > different page size (16K instead of 4K) -- would this be a problem for > "onload"? > > I've had a case open with IBM and they don't have a solid answer for me > yet. > Thanks in advance. > Kern -- > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- Art S. Kagel Oninit (www.oninit.com) IIUG Board of Directors (art@iiug.org) Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Oninit, the IIUG, nor any other organization with which I am associated either explicitly or implicitly. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves.

Thank you for your input Art. IBM has confirmed that this is a defect, unfortunately it seems like I was the first to discover this flaw --- that was what they said :( I know there are other alternatives but we could use none as of this moment since we've already lost the database. Perhaps we may have to go thru painful onbar restore. ________________________________ From: Art Kagel <art.kagel@gmail.com> To: ids@iiug.org Sent: Saturday, January 3, 2009 8:36:59 PM Subject: Re: Urgent! problem with onload, please help! [14422] Yes. Onunload and onload deal with page images of the table you are loading/unloading. Therefore you must load the data into a dbspace with the same page size as the dbspace that it was extracted from. To migrate data from one dbspace to another with different page sizes within the same server use the ALTER FRAGMENT...INIT IN... statement. To migrate to a different server you either have to unload the data using the dbaccess UNLOAD command and reload it using LOAD or the dbload utility, use Jonathan Leffler's sqlcmd tools to do the same thing, or use my dbcopy utility to copy the data directly from one server to the other. (Dbcopy is part of the package utils2_ak available for download from the IIUG Software Repository - www.iiug.org/software or the Oninit web site - www.oninit.com/utilities.) Art On Sat, Jan 3, 2009 at 10:50 AM, Kern Doe <kern_doe@yahoo.com> wrote: > Hello, > We did an onunload of a database, but we failed to onload it after about 10 > minutes or so, is anyone familiar with this error below and do you know a > way > to get around with it? > > onload -t mag_tempdb.onuld -b 64 -s 0 -d mag_tempdbdbs mag_tempdb> Please mount tape and press Return to continue ... > pagesize of the target dbspace does not match with the pagesize of the > partition on tape. > ISAM error: Tape might contain a corrupt page (or) if you are executing> onload> command specify the correct DBspace name using the -d argument. > > What I've found that most of "mag_tempdb" database's tables reside in > mag_tempdbdbs except for one table resides in a different dbspace with a > different page size (16K instead of 4K) -- would this be a problem for > "onload"? > > I've had a case open with IBM and they don't have a solid answer for me > yet. > Thanks in advance. > Kern -- > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- Art S. Kagel Oninit (www.oninit.com) IIUG Board of Directors (art@iiug.org) Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Oninit, the IIUG, nor any other organization with which I am associated either explicitly or implicitly. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.