1Z0-184-25 practice question 8 of 15

When using SQL*Loader to load vector data for search applications, what is a critical consideration regarding the formatting of the vector data within the input CSV file?

Full set: 60 questions
Answer options
A: Enclose vector components in curly braces ({}) Correct answer
B: As FVEC is a binary format and the vector dimensions have a known width, fixed offsets can be used to make parsing the vectors fast and efficient
C: Use sparse format for vector data
D: Rely on SQL*Loader’s automatic normalization of vector data
Correct Answer:
A. Enclose vector components in curly braces ({})
Explanation

SQLLoader in Oracle 23ai supports loading VECTOR data from CSV files, requiring vectors to be formatted as text. A critical consideration is enclosing components in curly braces (A), e.g., {1.2, 3.4, 5.6}, to match the VECTOR type’s expected syntax (parsed into FLOAT32, etc.). FVEC (B) is a binary format, not compatible with CSV text input; SQLLoader expects readable text, not fixed offsets. Sparse format (C) isn’t supported for VECTOR columns, which require dense arrays. SQLLoader doesn’t normalize vectors automatically (D); formatting must be explicit. Oracle’s documentation specifies curly braces for CSV-loaded vectors.
Reference:Oracle Database 23ai Utilities Guide, Section on SQLLoader for Vectors.

Scroll to Top