- Le plus récent
- Le plus de votes
- La plupart des commentaires
Thank you for reaching us. Prior reaching out to RDS Support Team I will also recommend to check if you are passing on the correct extension by listing all the files in data_pump_directory:
SELECT * FROM TABLE(rdsadmin.rds_file_util.listdir('DATA_PUMP_DIR')) ORDER BY MTIME;
[+] Importing using Oracle Data Pump - Step 6: Clean up - https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Oracle.Procedural.Importing.DataPump.html#Oracle.Procedural.Importing.DataPumpS3.Step6
If the file name provided in FREMOVE utility is correct then reaching out to Support should be right course of action
I would suggest reaching AWS support by creating Support case and provisioned RDS instance details, so internal teams can validate and remove those dump files.
Thank you for your responses. The filename (including extension) is correct and I have confirmed using rdsadmin.rds_file_util.listdir. When I intentionally use an incorrect filename the error returned changes from "cannot open file" to "nonexistent file or path". I assume the problem is an operating system file permission issue. As suggested I have opened a case with AWS Support. Thank you for your help.
Contenus pertinents
- demandé il y a un an
- demandé il y a 4 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 4 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 4 ans