Oracle Database: DBMS_SCHEDULER and SQL

Views can be created before their base tables exist in Teradata due to late binding - the view definition is stored but not validated until the view is used. However, if columns specifically referenced in the view definition are altered or dropped, the view becomes invalid and cannot be used.

CONCAT ignores NULL arguments and returns the non-NULL value, making it the correct choice. NULLIF returns NULL when its two arguments are equal, LENGTH returns NULL when given NULL, and INSTR also returns NULL with NULL inputs.

Aggregate functions like COUNT(*) cannot be used in a WHERE clause - they require HAVING after GROUP BY. The WHERE clause filters rows before grouping, while HAVING filters after grouping.

ALL_SCHEDULER_SCHEDULES is the correct Oracle view that provides information about all schedules accessible to the current user. Option B misses the 'S' at the end, while option C has incorrect word ordering.

STOP_JOB is the correct DBMS_SCHEDULER procedure to stop or kill a running scheduled job. There is no KILL or KILL_JOB procedure in the scheduler package.

KILL_JOB is not a valid DBMS_SCHEDULER function - the correct procedure is STOP_JOB for stopping running jobs. DROP_JOB, COPY_JOB, and STOP_JOB are all valid scheduler functions.

For a stored procedure in DBMS_SCHEDULER, the program_type should be 'STORED_PROCEDURE'. PLSQL_BLOCK is for anonymous PL/SQL blocks, and EXECUTABLE is for external executables like shell scripts.

The job_type parameter must be 'EXECUTABLE' (without the S) for shell scripts, not 'EXECUTABLES'. This typo in the job_type value will cause an error when creating the job.

Oracle's Scheduler job run details and execution history are stored in views like DBA_SCHEDULER_JOB_RUN_DETAILS or ALL_SCHEDULER_JOB_LOG. The options provided are misspelled or non-existent, making 'None' the correct choice.

Both DBMS_SCHEDULER (the modern scheduler from Oracle 10g) and DBMS_JOB (the older scheduling package still supported for backward compatibility) provide job scheduling functionality in PL/SQL. DBMS_SCHEDULE is not a valid package.

All four listed views are valid Oracle Scheduler data dictionary views. DBA_SCHEDULER_JOB_RUN_DETAILS shows job execution history, DBA_SCHEDULER_RUNNING_JOBS displays currently executing jobs, DBA_SCHEDULER_PROGRAM_ARGS lists program arguments, and ALL_SCHEDULER_PROGRAM_ARGS provides program arguments accessible to the current user. Therefore option E (All the above) is correct.

ALL_SCHEDULER_SCHEDULES is the correct view that provides all schedules accessible to the current user in Oracle Scheduler. Option B incorrectly uses singular 'schedule', and option C uses 'all_schedule_schedules' which is not a valid view name. Option D is incorrect since only option A is valid.

To schedule a job every Tuesday at 11:24, you need FREQ=WEEKLY (not daily or yearly) with BYDAY=TUE to specify Tuesday, along with BYHOUR=11 and BYMINUTE=24. DAILY would run every day, YEARLY would run once per year, and YEAR is not a valid frequency keyword.

To stop or terminate a currently running scheduler job, Oracle provides the DBMS_SCHEDULER.STOP_JOB procedure. There are no functions/procedures named kill, kill_job, or stop in this package.

DBMS_SCHEDULER contains procedures like drop_job, copy_job, and stop_job. It does not have a kill_job procedure; instead, stop_job is used to terminate running jobs, making kill_job invalid.

The STORED_PROCEDURE program type is specifically used for programs that execute stored procedures. PLSQL_BLOCK is for anonymous PL/SQL blocks, and EXECUTABLE is for external operating system commands or scripts. STORED_PROCEDURE_EXECUTABLE and STORED_EXECUTABLE are not valid program types.