166. You are monitoring the redo log buffer. How would you check whether the user processes have to wait for the space in the redo log buffer?
A.by checking the V$WAITSTAT view for the "log buffer space" class
B.by checking the "redo buffer allocation retries" statistic in the V$SYSSTAT view
C.by checking the alert log file for the message "CHECKPOINT NOT COMPLETE"
D.by checking the "Log File Switch Completion" event in the V$SYSTEM_EVENT view
ANSWER: B
167. You queried the V$SYSTEM_EVENT view and noticed that there are waits for the "Log File Switch Completion" event. What could be the reason for these waits?
A.The number of ARCn processes is not sufficient.
B.The number of DBWRn processes is not sufficient.
C.There is disk I/O contention on the online redo log files.
D.The value set for the FAST_MTTR_TARGET initialization parameter is too high.
ANSWER: C
168. You require that a session should be killed with an out-of-memory failure when the session's Java state exceeds 2GB. Which parameter would you modify?
A.SESSION_CACHED_CURSORS
B.JAVA_MAX_SESSIONSPACE_SIZE
C.JAVA_SOFT_SESSIONSPACE_LIMIT
D.SESSIONS and JAVA_SOFT_SESSIONSPACE_LIMIT
ANSWER: B
169. You require that a warning is written to a trace file without impacting the application when the session's Java state exceeds 2GB. Which parameter would you modify?
A.JAVA_MAX_SESSIONSPACE_SIZE
B.JAVA_SOFT_SESSIONSPACE_LIMIT
C.SESSIONS and JAVA_SOFT_SESSIONSPACE_LIMIT
D.LOG_ARCHIVE_TRACE and JAVA_MAX_SESSIONSPACE_SIZE
ANSWER: B
170. View the Exhibit and examine the parameters. Why would the DBA specify different values for the SESSIONS and SHARED_SERVER_SESSIONS parameters?
A.to reserve sessions for the dispatcher processes
B.to reserve user sessions for dedicated connections
C.to reserve sessions for Oracle server's internal sessions
D.to reserve sessions for use when the database instance is hung
ANSWER: B
Tags:
Post comment:
◎welcome to give out your point。