Whenever datapump export is initiated, it should (mainly) either by database level, schema level, or table level. If you omit to tell expdp about the mode of datapump export, ORA-31655 is returned. Therefore, you should always make sure that that you provide level/mode of export datapump whenever you invoke expdp. For example, use parameter full=y for database level export, or schemas parameter for schema level or tables parameter for table level export.
As we can see in below example how ORA-31655 is reproducible.expdp "/ as sysdba" content=METADATA_ONLY dumpfile=data_pump_dir:fullexp_test.dmp logfile=data_pump_dir:fullexp_test.log Export: Release 19.0.0.0.0 - Production on Wed Dec 25 04:56:24 2024 Version 19.22.0.0.0 Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved. Connected to: Oracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production Warning: Oracle Data Pump operations are not typically needed when connected to the root or seed of a container database. Starting "SYS"."SYS_EXPORT_SCHEMA_01": "/******** AS SYSDBA" content=METADATA_ONLY dumpfile=data_pump_dir:fullexp_test.dmp logfile=data_pump_dir:fullexp_test.log ORA-31655: no data or metadata objects selected for job "SYS"."SYS_EXPORT_SCHEMA_01" completed with 1 error(s) at Wed Dec 25 04:56:41 2024 elapsed 0 00:00:12 |
No comments:
Post a Comment