E. The default unit type for the MAX_DUMP_FILE_SIZE parameter is blocks.

C, D, E. The SGA_TARGET parameter specifies total memory available for sizing the SGA. This includes both automatically sized and manually sized components. The Java pool is an automatically sized component, so its size is unknown, but it will never shrink below the size specified in the JAVA_POOL_SIZE parameter. The streams pool is a manually sized component, so it receives a static allocation of 500MB.

C. ASMM is dependent on Oracle statistics and requires a STATISTICS_LEVEL of either TYPICAL or ALL. If the STATISTICS_LEVEL parameter is set to BASIC, ASMM will not function.

A. Only option A is correct. Wildcards are not allowed in the tcp.invited_nodes parameter, so only exact matches will be allowed.

C. The EXTPROC_DLLS environment variable limits the available shared libraries that the agent can access. Since the ONLY option is not included in the example, the specified libraries are available in addition to the default libraries (those in the $ORACLE_HOME/lib directory).

A, C. The alert log can be used to find error messages and other significant events, along with a timestamp. Trace files from background sessions may also be helpful to determine the cause of the problem. User trace files can be helpful to resolve errant SQL statements, but those are not classified as database problems. External procedure files do not exist.

B. The alert log details all startup events, including listing all of the non-default initialization parameters that were set.

D. If the PGA_AGGREGATE_TARGET parameter is not explicitly set, it will default to the greater of 10MB or 20 percent of the SGA size (800MB). Therefore, it will default to 800MB.

E. A new alert log will be created automatically the next time Oracle needs to write an alert log entry, so no action is required. You may indeed wish to restore the last backup of the alert log if you want it for historical purposes, but that has no effect on the Oracle instance itself.

C. Though Java stored procedures utilize Java pool memory, the usage is minimal. A large sort operation, on the other hand, is greatly impacted by the size of the SQL work area available to it.

B. Because the archiver is a background process, it will follow the naming conventions and storage locations used by all background processes. The TRACEFILE_IDENTIFIER parameter has no effect on background processes, so it is ignored.

C, D, E. All of the information specified in C, D, and E is logged to the alert log. Listener attacks would be logged in the listener log, not the alert log. External procedure executions are not logged.

C. Configuring the listener on a non-standard port may offer a slight security increase, but port-scanning programs could still easily locate the listener. Therefore, it is not a recommended security measure.

B, C. Manually editing the listener.ora file will result in a password that is stored in plaintext, whereas lsnrctl will store the password in an encrypted format. Also, you cannot manually edit the listener.ora file if you don't have access to the operating system (for example, if you need to perform the change remotely, but don't have an operating system account). In this situation, lsnrctl could be used from a remote location.

E. None of these components are automatically sized by ASMM. They are all manually sized SGA components, except for the SQL work area. The SQL work area isn't a part of the SGA at all. It is managed by APMM.

A. Index lookups are not memory intensive, whereas sort operations, bitmap merges, bitmap creation, and bulk load operations tend to be very memory intensive. Therefore, the SQL work area size has a major impact on their performance.

C. When the ADMIN_RESTRICTIONS option is enabled, all changes to the listener are disabled, except through manually editing the listener.ora file. This protects from changes being made remotely by unauthorized individuals.

D. Dirty blocks in the database buffer are tracked in the write list. The write list is accessed by the DBWR process to write dirty blocks back to disk.

D. The ORA-01169 message indicates a failed password attempt. Repeated occurrences of the message likely indicate that someone is trying to hack the password through a brute force attack.

C, E. When the WORKAREA_SIZE_POLICY parameter is set to AUTO (the default setting), APMM will dynamically size the SQL work area. Therefore, the amount of memory actually allocated is unknown. The *_AREA_SIZE parameters have no meaning unless the WORKAREA_SIZE_POLICY is set to MANUAL.