Which Manager Parameter sets will report current lag every hour and write a critical message for any Extract/Replicate with a lag over 60 minutes?

Which Manager Parameter sets will report current lag every hour and write a critical message for
any Extract/Replicate with a lag over 60 minutes?

Which Manager Parameter sets will report current lag every hour and write a critical message for
any Extract/Replicate with a lag over 60 minutes?

A.
LAGBEPOBTHOURS 1, LAGINFO 1 and LAGCRITICAL 60

B.
LAGREPORTMINUTES 60, LAGINFOHOURS 1

C.
LAGREPOBT 1, I.AGCRITICALHOURS 1

D.
LAGREPOBTHOURS 1, LAGINFOMINUTES 30, LAGCR JTTCAI-M I

Explanation:
Reference :
http://download.oracle.com/docs/cd/E15881_01/doc.104/gg_wux_ref_v104.pdf



Leave a Reply 4

Your email address will not be published. Required fields are marked *


Rahul

Rahul

B is not correct answer

Swall

Swall

B is the correct one.

Use the LAGINFOSECONDS, LAGINFOMINUTES, or LAGINFOHOURS parameter to specify how often to report lag information to the error log. If the lag is greater than the value specified with the LAGCRITICAL parameter, Manager reports the lag as critical; otherwise, it reports the lag as an informational message. A value of zero (0) forces a message at the frequency specified with the LAGREPORTMINUTES or LAGREPORTHOURS parameter.

Use the LAGREPORTMINUTES or LAGREPORTHOURS parameter to specify the interval at which Manager checks for Extract and Replicat lag.

franciscotmjr

franciscotmjr

Hi Swall,

A is the correct one (i guess).

The question asks for which parameter “writes a critical message for any Extract/Replicate with a lag over 60 minutes”. As you have stated: “If the lag is greater than the value specified with the LAGCRITICAL parameter, Manager reports the lag as critical”. So, the correct answer is A.

Regards,

S De

S De

B is correct as per Swall’s explanation.