A.Running a query on a table returns "ORA-600： Internal Error."
B.Inserting a value in a table returns "ORA-01722： invalid number."
C.Creating a table returns "ORA-00955： name is already used by an existing object."
D.Inserting a value in a table returns "ORA-00001： unique constraint （SYS.PK_TECHP） violated."
E.Rebuilding an index using ALTER INDEX ...REBUILD fails with an error "ORA-01578： ORACLE data block corrupted （file # 14， block # 50）.

A.Running a query on a table returns "ORA-600： Internal Error."
B.Inserting a value in a table returns "ORA-01722： invalid number."
C.Creating a table returns "ORA-00955： name is already used by an existing object."
D.Inserting a value in a table returns "ORA-00001： unique constraint （SYS.PK_TECHP） violated." 
E.Inserting a row in a table returns "ORA-00060： deadlock detected while waiting for resource."

A.ORACLE_HOME/dbs
B.ORACLE_HOME/rdbms
C./u01/app/oracle/admin/orcl/adump
D./u01/app/oracle/flash_recovery_area
E.ORACLE_BASE/diag/rdbms/orcl/orcl/alert
F.ORACLE_BASE/diag/rdbms/orcl/orcl/trace

A.in the BACKGROUND_DUMP_DEST location； in text format
B.in the BACKGROUND_DUMP_DEST location； in XML format
C.in the BACKGROUND_DUMP_DEST location； in both text and XML format
D.in the DIAGNOSTIC_DEST/diag/rdbms/orcl/orcl/alert directory； in text format
E.in the DIAGNOSTIC_DEST/diag/rdbms/orcl/orcl/alert directory； in XML format
F.in the DIAGNOSTIC_DEST/diag/rdbms/orcl/orcl/alert directory； in both text and XML format

A.7，1，5，2，3，6，4
B.1，5，7，2，3，6；step 4 is not required
C.7，1，5，2，3，6；step 4 is not required
D.1，2，3，5，6，4；step 7 is not required

A.init.ora
B.spfile.ora
C.initorcl.ora
D.spfile+ASM.ora

A.The online redo log files and online data files are opened.
B.All the online data file headers are checked for consistency.
C.Instance recovery is performed before opening the database.
D.The path and existence of all the log file members are checked

A.renaming the control files
B.re-creating the control files
C.dropping a user in your database
D.dropping a tablespace in your database
E.configuring the database instance to operate in the ARCHIVELOG or NOARCHIVELOG modes

A.The SGA_TARGET is a static parameter.
B.The instance is started， but the database is not yet open.
C.The server parameter file （SPFILE） was used to start the instance.
D.The SGA_TARGET parameter does not have any effect onthe databaseinstance untiltheSGA_MAX_SIZE parameter is specified.

A.An SPFILE is a binary file.
B.An SPFILE cannot reside on a client.
C.An SPFILE cannot contain static parameters.
D.An SPFILE can store changes persistently across instance restarts.
E.An SPFILE can be read by the database server， but it is not written to by the server.
F.An SPFILE must be created manually， before creating a database， even if you use the DatabaseConfiguration Assistant （DBCA） to create the database.

A.LOG_BUFFER
B.SORT_AREA_SIZE
C.JAVA_POOL_SIZE
D.STREAMS_POOL_SIZE
E.DB_16K_CACHE_SIZE
F.DB_KEEP_CACHE_SIZE