1Z0-184-25 Question 170
Single answerYou have a CSV file containing latitude and longitude columns that you need to load into an existing table on Oracle Autonomous Database in Oracle Cloud Infrastructure. The table has a column defined with the SDO_GEOMETRY data type, and you want SQL*Loader to automatically convert the latitude and longitude columns into a valid SDO_GEOMETRY object during the load. Which approach should you take?
- A
Define a field expression in the SQL*Loader control file that invokes the SDO_GEOMETRY constructor for each row using the latitude and longitude columns.
- B
Rely on SQL*Loader� automatic geometry parsing by setting the field type to 'GEOMETRY' in the control file, requiring no further configuration.
- C
Convert the latitude and longitude columns to Well-Known Text (WKT) manually in the CSV file before running SQL*Loader, then store them as a VARCHAR2 in the table.
- D
Disable the Spatial index on the SDO_GEOMETRY column before loading, so latitude and longitude data are converted automatically.
Show answer and explanation
Correct answer: A
Explanation
When loading vector (geospatial) data into an SDO_GEOMETRY column using SQLLoader, you need to instruct SQLLoader on how to construct the geometry object from your source columns. A common practice is to define a field expression in the control file that calls the SDO_GEOMETRY constructor (or another function such as SDO_GEOMETRY from WKT) and passes in the appropriate coordinate system. Refer to the Oracle Spatial and Graph documentation for details on setting up the column definition and constructor in your SQL*Loader control file.
- A. Correct.
Correct. By using the SDO_GEOMETRY constructor (e.g., SDO_GEOMETRY(2001, 8307, SDO_POINT_TYPE(:LAT, :LON, NULL), NULL, NULL)) in the SQL*Loader control file, you ensure each row� latitude and longitude are transformed into an SDO_GEOMETRY object at load time. This is the recommended approach to loading and converting vector data on the fly.
- B. Incorrect.
Incorrect. While SQL*Loader is flexible, it does not automatically recognize latitude and longitude columns as geometry objects. You must define how to convert those columns into SDO_GEOMETRY� simply setting a field type to 'GEOMETRY' is not supported in the control file syntax.
- C. Incorrect.
Incorrect. Manually converting to WKT and storing as VARCHAR2 loses the benefit of storing geospatial data in its native SDO_GEOMETRY type. Additionally, SQL*Loader cannot automatically convert WKT strings into SDO_GEOMETRY unless you explicitly call a function in the control file to do so.
- D. Incorrect.
Incorrect. Disabling the Spatial index before loading can help performance when loading large volumes of geometry data, but it does not automate the conversion from latitude and longitude columns to a valid geometry object. You still must specify the SDO_GEOMETRY constructor or a suitable function in the control file.