1Z0-027 · Question #44
Which two are true concerning the allocation of I/O resources by the IORM within the CELLSRV process?
The correct answer is A. Control File I/O is managed automatically at high priority by IORM. E. Database Writer I/O is managed automatically at normal priority by IORM. IORM is only "engaged" when needed. / (A) Redo and control file writes always take precedence. / (E) DBWR (database writer) writes are scheduled at the same priority as user IO. / IORM does not intervene if there is only one active consumer group on one database. / Any disk…
Question
Which two are true concerning the allocation of I/O resources by the IORM within the CELLSRV process?
Options
- AControl File I/O is managed automatically at high priority by IORM.
- BControl File I/O is considered part of the SYSTEM resource Consume group by IORM.
- CLog Writer I/O to the Smart Flash Log is considered part of the SYSTEM resource consumer group
- DLog Writer I/O to the Smart Flash Log is managed automatically at high priority by IORM.
- EDatabase Writer I/O is managed automatically at normal priority by IORM.
- FDatabase Writer I/O is considered part of the SYSTEM resource consumer group by IORM.
How the community answered
(43 responses)- A81% (35)
- B2% (1)
- C9% (4)
- D2% (1)
- F5% (2)
Explanation
IORM is only "engaged" when needed. / (A) Redo and control file writes always take precedence. / (E) DBWR (database writer) writes are scheduled at the same priority as user IO. / IORM does not intervene if there is only one active consumer group on one database. / Any disk allocation that is not fully utilized is made available to other workloads in relation to the configured resource plans. / Background IO is scheduled based on their priority relative to user IO. / For each cell disk, each database accessing the cell has one IO queue per consumer group and three background / Background IO queues are mapped to "high", "medium", and "low" priority requests with different IO types mapped to each queue. / If no intradatabase plan is set, all non-background IO requests are grouped into a single consumer group called OTHER_GROUPS.
Topics
Community Discussion
No community discussion yet for this question.