[Top] [All Lists]

Re: Compressing object database.. HELP!

To: nv-l@lists.tivoli.com
Subject: Re: Compressing object database.. HELP!
From: Leslie Clark <lclark@US.IBM.COM>
Date: Wed, 7 Apr 1999 21:55:42 -0400
Reply-to: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
Sender: Discussion of IBM NetView and POLYCENTER Manager on NetView <NV-L@UCSBVM.UCSB.EDU>
I used it on a large V5.1 database, but at the time the value_info.pag was
one tenth what yours
was. I could not get it to work until after I put on 5.1.1. It only took a
couple of minutes to run, and
then the synchronization did take a while, maybe five or ten minutes. There
were maybe
13000 objects in the database. It worked fine.  About the 15% free, I
cannot say. I was
paranoid and made sure I had double the size of the value_info.pag.

The next step we took was to go to the nvturbo format of the database. That
uses a different
compression procedure. But you probably want to do this one first to get it
down to a managable


Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager

---------------------- Forwarded by Leslie Clark/Southfield/IBM on 04-07-99
09:49 PM ---------------------------

Rob Wilkinson <Rob.Wilkinson@MBS.GOV.ON.CA> on 04-07-99 10:42:57 AM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L@UCSBVM.UCSB.EDU>

cc:    (bcc: Leslie Clark/Southfield/IBM)
Subject:  Compressing object database.. HELP!

One of my Netview V4 object files is over 2GB as below.. IBM says to run
the procedure below.. Has anybody run this procedure on a file of this
size? How long does it take? (We have an F50 w 1GB ram). du -a show the
file should be 18MB.. He says below we should ensure we have 15% freespace.
Would that be 15% of the file being compressed or 15% in the filesystem?

                    Filesystem    1024-blocks      Free %Used    Iused
%Iused Mounted on
                   /dev/lv11          204800    157248   24%       61
1% /usr/OV/databases/openview

        root@mbems01[/usr/OV/databases/openview/ovwdb/current]>ls -l
total 47600
-rwxr-xr-x   1 root     sys            0 Apr 15 1996  enum_info.dir
-rwxr-xr-x   1 root     sys         8192 Jul 04 1998  enum_info.pag
-rwxr-xr-x   1 root     sys         4096 Apr 15 1996  field_info.dir
-rwxr-xr-x   1 root     sys        16384 Aug 24 1996  field_info.pag
-rwxr-xr-x   1 root     sys            0 Apr 15 1996  id_keeper.dir
-rwxr-xr-x   1 root     sys         8192 Apr 05 00:04 id_keeper.pag
-rwxrwxrwx   1 root     system      4096 Apr 05 00:15 name_info.dir
-rwxrwxrwx   1 root     system   4194304 Apr 07 09:51 name_info.pag
-rwxrwxrwx   1 root     system      4096 Apr 02 22:13 obj_info.dir
-rwxrwxrwx   1 root     system   4169728 Apr 07 09:51 obj_info.pag
-rwxrwxrwx   1 root     system     81920 Apr 06 22:16 value_info.dir
-rwxrwxrwx   1 root     system   2119122944 Apr 07 09:53 value_info.pag

1.cd to /usr/OV/databases/openview/ovwdb/current
2.ls -l value_info.pag (note size in bytes)
3.du -a value_info.pag (note size in 512 byte blocks)
4.multiply size in blocks (from step 3) by 512 and compare to
size in bytes (from step 2).
5.If the size in bytes gets to 50% larger than the size in
blocks, it is time to compress.
To compress the object database:
1.Stop the NETVIEW daemons using ovstop.
2.Tar the databases to create a backup.
3.IMPORTANT: make sure the filesystem containing the database
has at least 15% freespace. If not, the compression process
will probably corrupt the object database.
4.Compress the object database using ovwdbdmap -c
5.After the compression is complete, bring up all the daemons
and gui and allow the synchronization process to complete.
This step will probably take longer than normal, but it is an
important part of the process.
6.Once the newly compressed database is completely synchronized,
it may be used or tar'd for backup (after stopping the daemons

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

Archive operated by Skills 1st Ltd

See also: The NetView Web