Oracle datapump status

Oracle logoDuring a import run of a +100GB Oracle database I was curious what the current progress was. I discovered you can press Ctrl+C to go to an interactive command mode during a import of export using datapump (impdp of expdp). In the interactive you can request the current status of the job(s). It is also possible to stop, start and resume jobs. For all options just type ‘HELP’. See the example below:

Import> status

Operation: IMPORT
Mode: FULL
Bytes Processed: 0
Current Parallelism: 1
Job Error Count: 0
Dump File: /usr/local/oracle/import/a01act-20140811-%u.dmp
Dump File: /usr/local/oracle/import/a01act-20140811-01.dmp
Dump File: /usr/local/oracle/import/a01act-20140811-02.dmp
Dump File: /usr/local/oracle/import/a01act-20140811-50.dmp
Dump File: /usr/local/oracle/import/a01act-20140811-51.dmp

Worker 1 Status:
Process Name: DW00
Object Schema: ****
Object Name: PTL*****
Completed Objects: 1
Completed Rows: 122,772
Completed Bytes: 102,619,789,192
Percent Done: 49
Worker Parallelism: 1


So I’m almost halfway now.

To return to the logging mode:


VirtualBox snapshots using the CLI

oracle-virtualbox-logoThis is how I use the VirtualBox snapshot option on my headless server. I use this feature for creating a restore point for a critical mail server upgrade I will soon post about. Because I will use this option more often it comes handy when recorded somewhere.


  • Debian 6.0.6 “Squeeze”
  • Virtualbox 4.1.22-80657

See the Virtualbox snapshot syntax below

VBoxManage snapshot         |
take  [--description ] [--pause] |
delete | |
restore | |
restorecurrent |
edit ||--current
[--name ]
[--description ] |
list [--details|--machinereadable]
showvminfo |


Oracle ASM lifesaver

I had a very nasty experience with Oracle ASM recently. A long story short, ASM crashed on both our RAC nodes when removing a corrupted archive file on file and incarnation number (removing it on it’s name didn’t work). Starting the instance failed. When removing the failing diskgroup ASM was happy again. Luckily the failing diskgroup only housed archivelog files, except for one database it also held it’s index datafile.  So that one wouldn’t come up. If you’re in such a situation, you can use the Oracle tools amdu in combination with kfed to extract the missing datafile or archivelogs (in our situation) from a dismounted diskgroup. If I knew that from the start it saved me alot of frustrating hours.