[Oracle] Data Pump detailed tutorial (5)-command interaction mode [Oracle] Data Pump detailed tutorial (4)-network_link http://www.bkjia.com/database/201308/232536.html After starting a datapump job, you can view the current progress through v $ session_longops. [Plain] USERNAME-job owner OPNAME-job name TARGET_DESC-job operation SOFAR-megabytes transferred thus far during the job TOTALWORK-estimated number of megabytes in the job UNITS-megabytes (MB) MESSAGE-a formatted status message of the form: 'job _ name: operation_name: nnn out of mmm MB done' [SQL] SYS @ TEST16> select username, opname, sofar, TOTALWORK, UNITS, message from v $ session_longops w Here opname = 'sys _ EXPORT_FULL_03 '; username opname sofar totalwork units message -------------------------------- ---------- using SYSTEM SYS_EXPORT_FULL_03 4737 35368 MB limit: EXPORT: 4737 out of 35368 MB done, but sometimes monitoring alone is not enough. We may need to modify the corresponding JOB. In this case, we need to perform the datapumo command interaction mode. There are two ways to enter the command interaction mode: 1. in logging mode, press ctrl + C2. expdp or impdp attach = SYSTEM. the Command for SYS_EXPORT_FULL_03 expdp interactive mode is as follows: Activity Command UsedAdd additional dump files. ADD_FILEExit interactive mode and enter logging mode. CONTINUE_CLIENTStop the export client session, but leave the job running. EXIT_CLIENTRedefine the default size to be used for any subsequent dump files. FILESIZEDisplay a summary of available comm Ands. HELPDetach all currently attached client sessions and terminate the current job. KILL_JOBIncrease or decrease the number of active worker processes for the current job. this command is valid only in the Enterprise Edition of Oracle Database 11g. PARALLELRestart a stopped job to which you are attached. START_JOBDisplay detailed status for the current job and/or set status interval. STATUSStop Current job for later restart. the interactive mode Command of STOP_JOB impdp is as follows: Activity command UsedExit interactive-Command mode. CONTINUE_CLIENTStop the import client session, but leave the current job running. EXIT_CLIENTDisplay a summary of available commands. HELPDetach all currently attached client sessions and terminate the current job. KILL_JOBIncrease or decrease the number of active worker processes for the current Job. this command is valid only in Oracle Database Enterprise Edition. PARALLELRestart a stopped job to which you are attached. START_JOBDisplay detailed status for the current job. STATUSStop the current job. the following uses expdp as an example to describe several common commands in STOP_JOB (if you forget the command, use the omnipotent help command ). 1. status: view the status of the current job, such as the completion percentage and concurrency. Each worker represents a parallel process. [SQL] Export> status Job: SYS_EXPORT_FULL_03 Operation: EXPORT Mode: FULL State: EXECUTING Bytes Processed: 8,357,285,928 Percent Done: 23 Current Parallelism: 2 Job Error Count: 0 Dump File: /home/oracle/dump/full _ % u. dmp Dump File:/home/oracle/dump/full_01.dmp bytes written: 8,357,294,080 Dump File:/home/oracle/dump/full_02.dmp bytes written: 4,096 Worker 1 Status: Process Name: DW00 State: EXECUTING Object Type: DATABASE_EXPORT/SCHEMA/TABLE/COMMENT Completed Objects: 5,120 Worker Parallelism: 1 Worker 2 Status: Process Name: DW01 State: EXECUTING Object Schema: P95169 Object Name: GRADE_RCCASE Object Type: DATABASE_EXPORT/SCHEMA/TABLE/TABLE_DATA Completed Objects: 3 Total Objects: 1,866 Completed Rows: 23,505,613 Worker Parallelism: 1 2. parallel: dynamically adjust the degree of parallelism [plain] Export> parallel = 4 3. add_file: Add dumpfile [plain] Export> ADD_FILE = hr2.dmp, dpump_dir2: hr3.dmp 4. stop_job, kill_job, and start_jobstop_job are only paused, and can be restarted with start_job. kill_job is killed directly and cannot be recovered. continue_client: exit the interactive mode and enter the logging mode. exit_client: exit the client.