I'm attempting to export from a physical Oracle 184.108.40.206.0 database to a amazon rds Oracle database. I used the expdp and exported a full database and incurred no errors upon export.
I've moved the copy over to my server running SQL Developer in my AWS environment, and using the impdp command I incur a slew of errors.
I've seen snippets in my searches for a few things, but having tried suggestions, it seems that isn't the error.
c:\Windows\system32\> impdp firstname.lastname@example.org:1521/DATABASE file=e:\export\full_export.sql log=e:\export\import.log
Running the above command I get the below.
Import: Release 220.127.116.11.0 - Production Connected to Oracle Database 11g Release 18.104.22.168.0 - 64bit Production ORA-31626: job does not exist ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_INTERNAL_LOGSTDBY" ORA-06512: at "SYS.KUPV$FT", line 1009 ORA-04045: errors during recompilation/revalidation of SYS.DBMS_LOGREP_UTIL ORA-20900: RDS restricted DDL Found: ALTER VIEW SYS.ALL_CAPTURE ORA-06512: at "RDSADMIN.RDSADMIN", line 367 ORA-06512: at line 2 ORA-04063: view "SYS.DBA_CAPTURE" has errors ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_LOGPREP_UTIL"
I've tried different schemas and all end with the same error. Looking AWS disabled the ... AS SYSDBA option with logging in, so I can't do that either.
I've seen some random web posts regarding datapump and RDS not playing nicely, but I can't get anything concrete.
Our DBA's have assured me that the data pump export worked flawlessly, as they could import it to another physical oracle database. So could this just be an RDS issue and not Oracle?