1Z0-184-25 Question 22
Select 2You have a table named PRODUCT_EMBEDDINGS in your Oracle Autonomous Database that stores a vector column EMBEDDING with product recommendation embeddings. You need to update the embeddings for a subset of products while ensuring high concurrency and consistent results in vector-based queries. Which two statements are correct about performing DML operations on the EMBEDDING column?
- A
A: You can use a standard UPDATE statement to fully replace the vector values, and the vector index will be refreshed upon commit.
- B
B: MERGE statements allow both updating and inserting vectors in a single operation, preserving concurrency control for relevant rows.
- C
C: You can partially update individual dimensions of the vector in place using SQL syntax, without having to replace the entire stored vector.
- D
D: The system automatically maintains real-time vector search results as soon as the row is updated, even before you commit the transaction.
Show answer and explanation
Correct answers: A, B
Explanation
To maintain consistency and concurrency while performing DML operations on vectors, Oracle Database updates the vector index after the transaction commits. Standard UPDATE or MERGE statements can replace or upsert the entire vector, ensuring that vector-based queries accurately reflect the latest embeddings. Partial dimension-level updates are not supported, and changes only become visible once committed. Refer to Oracle Database 23c (and later) Vector Search documentation for guidelines on managing vector columns and indexes.
- A. Correct.
A: Correct. When you replace the vector column using a standard UPDATE, Oracle Database refreshes the vector index as part of the commit. This ensures your vector-based queries see the updated data once the transaction completes.
- B. Correct.
B: Correct. MERGE statements can upsert vectors in one pass, handling updates for existing rows while inserting new ones. This is helpful when synchronizing partial sets of embeddings from an external ML pipeline, and it respects concurrency.
- C. Incorrect.
C: Incorrect. While future releases may evolve, current best practice typically involves replacing or appending the entire vector in one operation. Oracle Database does not support partial dimensional edits of a single vector column via DML syntax.
- D. Incorrect.
D: Incorrect. The updated vector information is not visible to vector-based queries until after the transaction is committed. Oracle Database requires a commit to finalize DML changes in any column, including vectors.