Hi again folks.
I'm still experimenting the datapump functions in SQLcl and this thing got my attention. When a job completes, the sql prompt is released and I have the control back of my database session. I believed that all the datapump operation correctly finished, but upon checking the dba_datapump_jobs, I noticed many other “finished” jobs hanging in the server with the status NOT RUNNING.
All operations operation seem to finish correctly (regardless of the presence of import errors) since I always get the last message “Job SYS.XXXXXX completed at…” written both on screen and in the log. So why are those jobs left on the server?
I can stop the job with DBMS_DATAPUMP, some times I have to drop the master table, but apparently this does not corrupt the dumpfiles since I can import them normally.
So… another little bug to be investigated? Perhaps add into the DATAPUMP IMPORT/EXPORT command a routine to clean up the job before quitting?