RE: [INV] cold backup of Inventory database

Rick,

I should have mentioned, in my earlier reply to this thread, that although
you're DB is down, and the IDH =3D = will be writing errors to it's
mcollect.log (depending on logging level) = because =3D of this situation
because RIM can't access the database, you won't = lose any =3D of your
collection data because of this. When the database = starts up, the =3D data
will just start moving into the database again. So, you = don't
*have* to =3D do anything with your collectors unless you start seeing
performance issues with the IDH having too much data to process once the =
DB starts back up.

/Jana

----------------------------------
Jana Garner
Enterprise Consultant
Gulf Breeze Software
jana_garner@xxxxxxxxxxxx
336-253-1184
www.gulfsoft.com
 
 

-----Original Message-----
From: owner-tme10@xxxxxxxxxxxxxxxx [mailto:owner-tme10@xxxxxxxxxxxxxxxx] On
Behalf Of Rick Veenstra
Sent: Tuesday, November 30, 2004 5:52 AM
To: tme10@xxxxxxxxxxxxxxxx
Subject: [tme10] [INV] cold backup of Inventory database

Hi List,

Our Oracle DBAs want to do cold backups of our Inventory database. What can
I do to prevent (RIM-related) errors in our Tivoli logs? Will stopping the
datahandler with 
   wcollect -h graceful @InvDataHandler:inv_data_handler 
(and starting it after the backup) be sufficient?

With kind regards,

-- 
Rick Veenstra
ICT Specialist System management tools
Univé Verzekeringen
The Netherlands