I have been on Sql server and Oracle for past 4 years after starting on
System 34 (1981) and AS/400 in 1989. For me, worse than the corruption
issue, which to date I have seen a few times here, but far worse from my
perspective is how slow both Oracle and SQL Server are. I never had such an
issue where because there are so many records to read, we can't deploy a
simple program. It was far easier to make whatever job adjustments you had
to make and provide the user with their report or screen. Here after
developing some tabs, we had to put some on hold, while we wait for the
other team to provide the data for us in a better way.
I used to say to them many times, what a shame, I never had this issue back
on the 400. Now I just accept it and move on to the next task.
On Wed, Jan 30, 2013 at 7:39 AM, <rob@xxxxxxxxx> wrote:
And those darn *MGTCOL objects used to get damaged so regularly that we
got into the habit of saving them to a save file before saving the entire
system to tape. That way, if the save file save flagged them as damaged
we would delete them before the hours long full system save. I had that
pmr open long enough to cover several releases of the OS. It's resolved
now. And for those of you who decry that a *MGTCOL object doesn't count
because it's not 'database', there was a *FILE object (PF or table) that
was that was also part of performance collecting that I also routinely
saved to save file before the full system save.
And, as others reported, I have had the occasional vendor supplied DB2
type file that got flagged as damaged during the backup.
IBM Certified System Administrator - IBM i 6.1
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
Kendallville, IN 46755
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives