1Z0-184-25 Question 182
Single answerYou are migrating a table containing high-dimensional vector data in a custom object type named VEC_OBJ_TYPE from your on-premises Oracle Database to an Autonomous Database on Oracle Cloud Infrastructure. The table also has a vector-based index on this type. You want to ensure that both the vector data and associated index definitions are properly preserved when using Oracle Data Pump. Which approach is required to achieve this?
- A
Create the custom object type VEC_OBJ_TYPE in the target database prior to import and then run Data Pump so the DDL and data for the vector columns and index can be applied cleanly.
- B
Use the Data Pump parameter FULL=Y to guarantee that the custom type and associated index are always re-created correctly without any other prerequisites.
- C
Include the TRANSFORM=SEGMENT_ATTRIBUTES:N parameter to ensure that custom objects and any indexes on them are transformed into standard Oracle data types during import.
- D
Export only the data rows (CONTENT=DATA_ONLY) to avoid any custom object conflicts, then manually create the VEC_OBJ_TYPE and index on the target after the import.
Show answer and explanation
Correct answer: A
Explanation
When using Oracle Data Pump with custom object types (such as specialized vector data types), the target environment must either already have or be prepared with the same object type definitions as the source. Otherwise, the import job will fail to recreate the data and associated indexes correctly. For more detailed guidance, refer to the Oracle Data Pump documentation and the section on migrating user-defined object types.
- A. Correct.
Correct. When using Oracle Data Pump to migrate custom types such as a vector object type, you must create that object type in the target database before performing the import. This ensures the vector columns and related index definitions are recognized and preserved during the Data Pump job.
- B. Incorrect.
Incorrect. Using FULL=Y exports and imports all objects, but it does not automatically create custom object types in the target if they do not already exist. The type definition must be present in the target schema (or created beforehand) for the import to succeed.
- C. Incorrect.
Incorrect. TRANSFORM=SEGMENT_ATTRIBUTES:N does not convert custom object types to standard Oracle types. Instead, it omits segment attributes (e.g., storage parameters) during import. This parameter will not handle vector data types.
- D. Incorrect.
Incorrect. Exporting DATA_ONLY can preserve table rows but will not include the structural definitions (DDL) for the custom object type or the vector index. Manually creating the type and index post-import is prone to errors if the definitions do not precisely match the source.