Re: Adjusting to DB2

Mark A wrote:

> nice when compared to the old way of backing up Oracle, but DB2 backups are
> very simple one line commands that backup everything (including logs active
> during the on-line backup) into a single file. When you restore DB2 you
> don't need to rename any log files.

I'm curious: since the maximum file size in, say, an ext3 file system in RHAS is 64Gb, are you saying DB2 backup can only handle a maximum database size of that calibre? What happens then to the claimed multi-Tb dbs it's supposed to handle? Or is it only the "same" mainframe version that can do that? Does it backup a multi-Tb db to a single file? How? Can it do a partial backup then?

> The DB2 export, import and load commands are far superior to SQL*Loader,
> which is primitive by comparison.

Yeah, true. *If* SQL*Loader was an "export and import" product. As it isn't, as usual in cases where folks don't have a clue what they talking about, the comparison doesn't even begin to make sense.

> another half-truth. True, DB2 for iSeries (AS400), DB2 for z/OS, and DB2 for
> LUW (Linux, UNIX, Windows) are not identical, but Oracle does not even run
> on AS/400, and it runs poorly on z/OS.

So, Oracle not running in as400 is justification for the so-called "unique" product to not be the same in zos, iseries and LUW. Obviously.
May I just add another pearl of wisdom?
Blblblblblblbl.
There!...

> When a new release
> or fixpack comes out for DB2 for Linux, UNIX, and Windows , it is always
> simultaneously available on all of its supported OS's, something which
> Oracle does not even approach.

True and granted.

> days max. A few extra days to set up cron jobs for backups, runstats, and
> reorgs, and you are all set.

tsktsktsk... "reorgs"??? What's that?
You mean it *needs* them?
How unkewl! Received on Mon Oct 24 2005 - 20:02:03 CDT