Pick the exact syntac for SQL LOADER Utility
-
sqlldr userid=scott/tiger control=emp.ctl log=emp.log
-
qlldr userid=scott/tiger control=emp.ctl log=emp.log data=data1.dat
-
sqlldr userid=scott/tiger control=emp.ctl log=emp.log direct=FALSE
-
sqlldr userid=scott/tiger control=emp.ctl
SQL Loader (sqlldr) invocation syntax: 'sqlldr' followed by 'userid=' for credentials, 'control=' for the control file, 'log=' for log file, 'data=' for input data file, and 'direct=' for load path. All four options show valid syntax variations - the command works with just the mandatory control parameter, or with any combination of the optional parameters.
This is a multi-select of valid Oracle SQL*Loader command lines. The utility executable is 'sqlldr'. Three options are legitimate invocations: 'sqlldr userid=scott/tiger control=emp.ctl log=emp.log' (595655), 'sqlldr userid=scott/tiger control=emp.ctl log=emp.log direct=FALSE' (595657, where direct=TRUE/FALSE selects direct-path vs conventional load), and 'sqlldr userid=scott/tiger control=emp.ctl' (595658, userid+control is the minimum required). Option 595656 as stored — 'qlldr userid=scott/tiger control=emp.ctl log=emp.log data=data1.dat' — is INVALID because the command is misspelled 'qlldr' (missing the leading 's'); no such executable exists, so it is not 'exact syntax' and should not be marked correct. The parameters it uses (data=) are otherwise valid, confirming this is a data-entry typo. Therefore the DB is wrong to flag 595656 as correct; it should be correct=false while 595655, 595657, and 595658 remain correct.