I want to recommend SQL Developer as the user interface for Data Pump jobs (since we do not have OEM).
On the export job interface, the choice "export read-consistent view of data" fails if the SCN is >= 2147483648. I get the error "SCN must be positive integer".
While I'm at it, the "By Date" option fails too, since the date displayed uses local settings and the PL/SQL code generated uses database settings!
This is a show stopper for recommending the tool, since I do want exports to be read consistent...
I'd submit a bug report. Sounds like the value is being stored in an int or interpreted as an int.
Decimal 2147483648 => hex 80000000
Meaning the high order bit is set; when the high order bit is set it indicates a negative number.
See it, logging it. #BUG
What do you think of the rest of it? Up for your users' requirements for their main Data Pump UI?
Jeff, thanks. To tell you the truth, this is for copying parts of databases from one environment to another. What is missing is the transport from the export database to the import database. To be complete, this transfer would have to be either
- Direct: source pushes to target
- Indirect: workstation pulls from source, pushes to target.
The latter option probably sounds as horrible to you as to me, but the direct option would make sense. You could include support for the NETWORK_LINK option...
Thanks so much.
On the date issue:
select current_date, sysdate from dual;
07-OCT-13 15.52.40 07-OCT-13 06.52.40
My current_date is in the Paris time zone, but SYSDATE comes from the OS which uses the Pacific time zone.
You are displaying the date in my time zone and using the same value in the PL/SQL code, which is using a different time zone and thinks that time is in the future.
I would prefer an option "read-consistent as of now", and the PL/SQL code would say
dbms_datapump.set_parameter(handle => h1, name => 'FLASHBACK_SCN', value => dbms_flashback.get_system_change_number);