LDQ Flush Job

[former_member185875]

HI,

i have searched about LDQ

i found the LDQ stands for "Local Data Queue".

i need know the significance of ''LDQ Flush" job in sdoe_bg_job_monitor

could please explain about it?

Regards

lakshman balanagu

Edited by: lakshman balanagu on Mar 10, 2010 4:16 PM

[VikasLamba · Accepted solution]

YEs you can do it even now. It won't cause any harm although the first run may take long time, but being a background job I hope it would not load your system greatly. Better to schedule the firt run in odd hours and then do a regular scheduling as per your need.

[VikasLamba]

Hi,

You are absolutely correct!!

Cheers,

Vikas

[former_member185875]

Dear Vikas,

I am newly comming for support for existing MI 7.1 implementation.

Here the implementation is done 2 years back.

from there onwards 'LDQ Flush Job' not configured.

If i configier it from today for everyday.

is there any effect to the system?

regards

lakshman balanagu.

[VikasLamba]

In DOE, the device outbound queues work on the Local Data Queue technology where all pre calculated messages for the devices are kept. The synchronization protocol takes care of acknowledging those messages which have been successfully downloaded by the device. Thus every time a message is downloaded the DOE sync layer will update the read counter of the corresponding LDQ by 1. But this update does not physically removes the messages, it only updates the counters.

The background job takes care of deleting all the entries across queues which have been acknowledged and need not be kept on the queue. This is required since with time the DB space due to unnecessary entries on the server will keep on increasing.

Thus scheduling this job is very criticial for DB performance.

Regards,

Vikas

[former_member185875]

Hi Vikas,

We have implemented custom client.

As per your replay

Thus every time a message is downloaded the DOE sync layer will update the read counter of the corresponding LDQ by 1. But this update does not physically removes the messages, it only updates the counters.

i assuming that

While calling "MMW_CONFIRM_MSG_RCVD"

Itu2019s not delete the messages from outbound queue. Increment the counter by 1.

so, I can schedule the job every day.

What I am assuming is right?

I am waiting for your replay.

lakshman balanagu

[former_member185875]

hi Vikas

Thus scheduling this job is very criticial for DB performance.

means?

can you please elaborate it?

lakshman balanagu