I ran into a similar situation years ago. I emailed Debbie Saugen, the
Backup/Recovery wizard @ IBM, and she got the answer from the database
folks. To paraphrase (from memory) it's an issue of allocation and
extents. When the system creates the object, it gets space dynamically.
When it restores the object, it knows how much space to allocate right
off the bat.
My original question was in response to an audit of our backup/restore.
On a test, the object sizes differed - some larger, some smaller.
john.earl@xxxxxxxxxxxxxx 12/08/2009 12:26:03 PM >>>
Has anyone ever heard of a restored save file being of a different
size than the original save file that was saved?
We have a situation where we wrote a save file with 5300+ objects in
it to tape, then later restored the save file and to the same system
and found that the size of the restored file was about 190K smaller
than the the original save file.
A DSPSAVF indicates that the same number of objects are in the save
file, and there is no obvious loss of data. The next step is to do a
object by object inspection, but before I go down that road I was
wondering if there might be a simple explanation that I am just not
aware of.
Thanks,
jte
--
John Earl
President and CEO
Patrick Townsend Security Solutions
"The Encryption Company"
Olympia, WA | www.patownsend.com
Office: 360-357-8971 Ext 118
midrange.com
