1Z0-902 · Question #30
Which dbmcli command is NOT valid on Exadata X9M?
The correct answer is C. dbmcli -e "LIST IBPORT DETAIL". Option C specifies LIST IBPORT, which references InfiniBand ports - but Exadata X9M replaced InfiniBand interconnects with RoCE (RDMA over Converged Ethernet), making any IB-specific dbmcli commands invalid on that platform. Options A and B are valid because LIST METRICHISTORY…
Question
Which dbmcli command is NOT valid on Exadata X9M?
Options
- Adbmcli -e "LIST METRICHISTORY WHERE name LIKE 'DS_.*'"
- Bdbmcli -e "LIST METRICCURRENT WHERE name = 'DS_TEMP' "
- Cdbmcli -e "LIST IBPORT DETAIL"
- Ddbmcli -e "LIST ALERTHISTORY WHERE agelnMinutes < 15"
How the community answered
(46 responses)- A11% (5)
- B26% (12)
- C57% (26)
- D7% (3)
Explanation
Option C specifies LIST IBPORT, which references InfiniBand ports - but Exadata X9M replaced InfiniBand interconnects with RoCE (RDMA over Converged Ethernet), making any IB-specific dbmcli commands invalid on that platform. Options A and B are valid because LIST METRICHISTORY and LIST METRICCURRENT are standard dbmcli metric query commands that work across Exadata generations, including X9M. Option D is also valid - LIST ALERTHISTORY with a time-based filter like agelnMinutes is a supported query on X9M storage cells.
Memory tip: Think "X9M = eXited InfiniBand" - the X9M generation is the one where Oracle switched from IB to RoCE, so any command with "IB" in it is a red flag on X9M hardware.
Topics
Community Discussion
No community discussion yet for this question.