You have three production database, HRDB, FINDB, and ORGDB, that use the ASM instance. At the end of the day, you execute the following command on the ASM instance to shut down:
SQL> shutdown immediate ;
What is the result of executing this command?
A.
All the instances, including the ASM instance, are shut down in the ABORT mode.
B.
The ASM instance is shut down, but the other instances are still running.
C.
The ASM instance is still functional, but the other instances are shut down.
D.
All the instances, including the ASM instance, are shut down in the IMMEDIATE mode.
E.
HRBD, FINDB, and ORGDB instances are shut down in the ABORT mode and the ASM instance is shut down in the IMMEDIATE mode.
F.
HRDB, FINDB, and ORGDB instances are shut down in the NORMAL mode and the ASM instance is shut down.
Explanation:
When a Datapump Export or Import session is launched, a Datapump Job is automatically started. This way, we can:
* detach from and reattach to long-running jobs without affecting the job itself.
* monitor jobs from multiple locations
* stop a job: suspend it temporarily to leave other applications requesting more resources to get them restart it later
* kill any Datapump job anytime
* see the progress of the import or export operations
You can retrieve the job, ownername and state from the following views:
SQL>SELECT OWNER_NAME,JOB_NAME,STATE FROM DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME STATE
———————-
—————- ————–
SCOTT SCOTTEXP DEFINING
SYSTEM SYSEXP EXECUTING
SYSTEM SYSIMP STOPPING
SYSTEM
FULLEXP NOT RUNNING
SYSTEM EXPFULL IDLINGREF.: Metalink Note: 262557.1