RE: [nv-l] Change the size of ovwdb cache

["Davis, Donald" <donald.davis@firstcitizens.com>]

Swen,
After you make the change in the ovwdb.lrf file, you must also run the following:

/usr/OV/bin/ovdelobj /usr/OV/lrf/ovwdb.lrf
/usr/OV/bin/ovaddobj /usr/OV/lrf/ovwdb.lrf

These two commands modify the /usr/OV/conf/ovsuf file which is what is actually read at daemon startup.
If you check your ovsuf file you will find a record that starts with a zero with the old size (0:ovwdb.....)
After you run these two commands your ovsuf file will contain a 0:ovwdb..... record with the new value and a 1:ovwdb.....

record with the old value.

In the ovsuf file, records that begin with 1: are (comments) historical, records that begin with 0: are active.
(The suf means "start up file")

Don

=======================
Donald Davis
First Citizens Bank
Raleigh, NC.  27603-3526
 

-----Original Message-----
From: Swen.Jedlicka@finanzit.com [mailto:Swen.Jedlicka@finanzit.com]
Sent: Thursday, November 13, 2003 10:53 AM
To: nv-l@lists.us.ibm.com
Subject: [nv-l] Change the size of ovwdb cache

Hello,

NV 7.1.3
Solaris 7

I wanted to change the size of ovwdb cache. But i did not want to use the
"serversetup" tool, because
this tool restarts the daemon immediately. I wanted to restart the daemon
at midnight (with crontab and script)

Yesterday, I manually changed the /usr/OV/lrf/ovwdb.lrf file. At midnight
the daemon was restarted, but with the
old chache size. The entry in ovwdb.lrf was ignored.

What did i wrong ? I thought , a change in ovwdb.lrf is all i have to do.

Thanks

Swen

------------------------------------------------------------------------------
This electronic mail and any files transmitted with it are confidential and are intended solely for the use of individual or entity to whom they are addressed. If you are not the intended recipient or the person responsible for delivering the electronic mail to the intended recipient, be advised that you have received this electronic mail in error and that any use, dissemination, forwarding, printing, or copying of this electronic mail is strictly prohibited. If you have received this electronic mail in error, please immediately notify the sender by return mail.
==============================================================================