

Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2018-11-06
08:57
585 views
ZoomDB
Hi,
This is 4.7.1 on SLES12SP3.
I have a driver (not NetIQ) running as a RL and there were a bunch of
events in the driver cache it was processing.
I stopped the driver and disabled it, 0 events in the driver cache.
As soon as I started the driver again it started pumping commands to the RL.
Nothing was happening in the IDV and the driver cache was still empty.
So I found this directory that was 165MB,
/var/opt/novell/eDirectory/data/dib/dx1437166.zoomdb/
Looking at the files I could see the IDM XML of the events.
So it seems we have two caches now, the regular driver cache that comes
before subscriber event transformation and a secondary that comes after
the output transformation.
How do we manage it?
I need a way to do the same things I can do with a regular driver cache
using the DirXML LDAP API:
* View the cache size, number of entries, type of events, oldest, newest
* Export entries from the cache
* Most important, empty the cache without resorting to rm -rf
Anyway, stopping the driver and deleting the zoomdb directory solved the
issue, the events were no longer being sent to the RL.
-alekz
--
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
This is 4.7.1 on SLES12SP3.
I have a driver (not NetIQ) running as a RL and there were a bunch of
events in the driver cache it was processing.
I stopped the driver and disabled it, 0 events in the driver cache.
As soon as I started the driver again it started pumping commands to the RL.
Nothing was happening in the IDV and the driver cache was still empty.
So I found this directory that was 165MB,
/var/opt/novell/eDirectory/data/dib/dx1437166.zoomdb/
Looking at the files I could see the IDM XML of the events.
So it seems we have two caches now, the regular driver cache that comes
before subscriber event transformation and a secondary that comes after
the output transformation.
How do we manage it?
I need a way to do the same things I can do with a regular driver cache
using the DirXML LDAP API:
* View the cache size, number of entries, type of events, oldest, newest
* Export entries from the cache
* Most important, empty the cache without resorting to rm -rf
Anyway, stopping the driver and deleting the zoomdb directory solved the
issue, the events were no longer being sent to the RL.
-alekz
--
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
0 Replies