ADSM-L

UNLOADDB Operational Questions

2002-10-13 19:17:21
Subject: UNLOADDB Operational Questions
From: "Seay, Paul" <seay_pd AT NAPTHEON DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Sun, 13 Oct 2002 19:16:58 -0400
Has anyone ever run an unloaddb against a 60GB+ database.  If so, can you
approximate the following:

        What is the size of your database?
        Had it ever been unloaded/loaded before?
        How many database entries where dumped?
        When the last message came out:
                ANR4013I UNLOADDB: Dumped 548859573 database entries
(cumulative).
          How long did it take to finish after the last ANR4013I message?
          How long did it take to get to the last ANR4013I message?
          What comes out after the last ANR4013I message?
        What was your approximate total unloaddb time?
        How long did it take you to do the LOADFORMAT?
        How long did it take you to do the LOADDB?

It just seems to me that something is wrong.  If it is not, I want to write
some requirements so you can tell what is going on and can estimate when the
process will finish.

What I am seeing is this:
        Running for 4 to 5 hours after the last message and it is still
doing a tremendous amount of IO Wait.
        I run out of time for my window and cannot complete the unload.

Doing some simple math:
        548M entries in 22M pages would be 25 entries per page in simple
terms.  What is your ratio?  I have to believe this is somewhat consistent.

What I am after is to figure out how big of window it will take to do the
REORG.  I hear it takes about two-thirds the time to do the load based on
the unload, but I cannot finish the unload to estimate the time required.

Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180

<Prev in Thread] Current Thread [Next in Thread>