You are using DMO of SUM. You defined 40 parallel R3load processes during uptime and 80 parallel R3load processes during downtime. The server provides 8 CPU cores. Phase EU_CLONE_MIG_DT_RUN is…

Question

Options

• AThese are 40 pairs of R3load processes, so there are 80 R3load processes running.
• BThere is a maximum of 40 parallel R3load processes within this specific phase.
• CSUM is still running in uptime; the 40 defined R3load processes are considered.
• DThe number of CPU cores does NOT allow more than 40 R3load processes to be run in parallel.

• A
  57% (13)
• B
  13% (3)
• C
  26% (6)
• D
  4% (1)

Explanation

Option A is correct because in DMO, R3load processes always operate in pairs - one export process (reading from the source database) and one import process (writing to the target database). The Charts Control Center displays process buckets, where each bucket represents one export/import pair. So 40 visible buckets = 80 actual R3load processes, which exactly matches the 80 parallel processes configured for downtime.

Why the distractors are wrong:

• B is incorrect because the phase EU_CLONE_MIG_DT_RUN ("DT" = downtime) means the downtime limit of 80 applies - not a phase-specific cap of 40.
• C is incorrect because EU_CLONE_MIG_DT_RUN is definitionally a downtime phase; the uptime limit of 40 is irrelevant here.
• D is incorrect because 8 CPU cores impose no such hard limit; SUM does not cap R3load parallelism based on a 1:5 or similar fixed CPU-to-process ratio in this way.

Memory tip: Think "buckets = pairs." Whenever you see a process count in Charts Control Center that looks like it matches the uptime setting during a downtime phase, remember that the display unit is pairs - the real process count is double what you see.

No community discussion yet for this question.