Inventory Roll-up ZfD 3.2 Sp1

Question

I will try not to make this wordy, but I am including details so
responedents don't just throw out have you tried this.
I have walked into a situation were the client has created DBs on each
leaf server. Prior to the server being a leaf w/DB it was a stand alone
w/DB. My trouble is that all the workstaions in the leaf are not
populated in the root. I have verified the last register time of each
imported workstation object. I have also verified that it has an .STR
file. I have verified my my roll-up policy. I made sure that the
roll-up ocurrs at night. The ramdom tick box is unchecked. I saw a TID
somewhere about it causing. The ENTMERGEDB directory fills up daily
with scan records. The intermediates ENTPUSHDB directory gets zip files
from all leafs. All my log state that roll-up is succesful to
intermediate and the intermediate updated the root. If I compare my
imported workstaion objects with the local DB it is correct. When I go
to the root and run a report for just a particular site the numbers
don't match. According to what I am seeing I am missing about 40% of my
workstations in the root DB. Last week I updated the root and
intermediate with SP3. They are local.
Anyone have any ideas? Does anyone have the exact sequence on how the
leaf updates the root? Why isn't there a utility that allows me to
connect to a leaf or intermediate DB and do a send data now.
Oh all the logs in the sys:\pulblic\zenworks\wminv\ whatever\whatever (I
am at home and can't remeber the rest of the path) show no time out
erros or connection errors.
Steve Fullerton
[email protected]

Answer 1

Frank,
Thanks for the info. I believe that I hase soled the issue. AS I
suppected, the Root DB is only updated when there is a change to the
Leaf. Because the client started off the Leaf as a Stand Alone server,
all workstations need to be rebooted to force a scan for delta info.
The change is then made in the Leaf and forwarded to the Root. I have
checked the "Scan Status" on the workstations not found in the Root and
found that they all are scan dates prior to the server change. Now I
just need everyone to reboot their workstations.
For all of those who may look at this thread, unless it is absolutely
necessary, do not create local DBs. It only makes troubleshooting that
much more difficult. If the server abends hard also you need to
re-install the local DB.
Frank Tessnow wrote:
> Steve,
>
> I don't know of a utility, which can send a leave DB to the
> root.
>
> From the point of Your configuration change any scan should
> be imported to the leave and "rolled up" to the root.
> Do You see any workstations after that time, which are in
> the leave and not in the root?
>
> Possible there are workstations in the root DB, which does
> not exist in the NDS and also not physically (there's a TID
> to remove this workstations manually)?
>
> Possible there are workstations in the leave DB, which does
> not exist in the NDS and also not physically. This
> workstations will never be "rolled-up" to Your root!
>
> Search for a workstation, which is in the leave and not in
> the root and look if it is "scanned" after the time of Your
> configuration change. Does this workstation exist? If not:
> Sync the leave DB witch the NDS. (You "clean out" unused
> workstations from the NDS?)
>
> Write, if this does not help (write about the times when a
> "faulty not in sync DB-record" workstation was scanned and
> witch which times You can find it the DB's...)...
>
> HTH - Frank
>