PRO - PL SQL Programming

View the Exhibit to examine the PL/SQL block.

DECLARE

      TYPE population IS TABLE OF NUMBER

          INDEX BY VARCHAR2(64);
 
      city_population population;

      i VARCHAR2(64);

BEGIN

       city_population('Smallville') := 2000;

       city_population('Midland')  := 750000;

       city_population('Megalopolis') := 1000000;

       city_population('Smallville')  :=2001;

       i := city_population.FIRST;
        
        WHILE i IS NOT NULL LOOP

            DBMS_Output_PUT_LINE('Population of ' || 'is' || 
                               TC_CHAR(city_population(i)));

            i := city_population.NEXT(i);

        END LOOP;

 END;

/

Which statement is true about the execution of the PL/SQL block?

View the Exhibit to examine the PL/SQL block.

DECLARE

      TYPE population IS TABLE OF NUMBER

          INDEX BY VARCHAR2(64);
 
      city_population population;

      i VARCHAR2(64);

BEGIN

       city_population('Smallville') := 2000;

       city_population('Midland')  := 750000;

       city_population('Megalopolis') := 1000000;

       city_population('Smallville')  :=2001;

       i := city_population.FIRST;
        
        WHILE i IS NOT NULL LOOP

            DBMS_Output_PUT_LINE('Population of ' || 'is' || 
                               TC_CHAR(city_population(i)));

            i := city_population.NEXT(i);

        END LOOP;

 END;

/

Which statement is true about the execution of the PL/SQL block?

1 Mark(s)

It executes successfully andgives the desired output.
It does not execute because the definition of type population is indexed by VARCHAR2.
It executes, and the string keys of an associative array are not stored in creation order, but in sorted order.
It does not execute because the value that is once assigned to the element of the associative array cannot be changed.

View the Exhibit to examine the PL/SQL code:

SQL > desc emp

Name           Null?         Type
-------------  ------------- ------------
EMPNO           NOT NULL     NUMBER(4)

ENAME                        VARCHAR(10)

JOB                          VARCHAR(9)

MGR                          NUMBER(4)

HIREDATE                     DATE

SAL                          NUMBER(7,2)

COMM                         NUMBER(7,2)

DEPTNO                       NUMBER(2)




DECLARE

x NUMBER = 5;

y NUMBER = NULL;

IF x!=y THEN  /* yields NULL,not TRUE */

DBMS_OUTPUT.PUT_INE('x=y'); /* not run */

ELSEIF x=y THEN /* also yields NULL */

DBMS_OUTPUT.PUT_LINE('x=u');

ELSE

DBMS_OUTPUT.PUT_LINE

('can't tell if x and y are equal or not');

END IF;

END;

/

which statement is true about the output of the PL/SQL block ?

View the Exhibit to examine the PL/SQL code:

SQL > desc emp

Name           Null?         Type
-------------  ------------- ------------
EMPNO           NOT NULL     NUMBER(4)

ENAME                        VARCHAR(10)

JOB                          VARCHAR(9)

MGR                          NUMBER(4)

HIREDATE                     DATE

SAL                          NUMBER(7,2)

COMM                         NUMBER(7,2)

DEPTNO                       NUMBER(2)




DECLARE

x NUMBER = 5;

y NUMBER = NULL;

IF x!=y THEN  /* yields NULL,not TRUE */

DBMS_OUTPUT.PUT_INE('x=y'); /* not run */

ELSEIF x=y THEN /* also yields NULL */

DBMS_OUTPUT.PUT_LINE('x=u');

ELSE

DBMS_OUTPUT.PUT_LINE

('can't tell if x and y are equal or not');

END IF;

END;

/

which statement is true about the output of the PL/SQL block ?

1 Mark(s)

The output is x = y.
It produces an error
The output is x ! = y
The output is Cant tell if x and y are equal or not

Which two tasks should be created as functions instead of as procedures? Choose that to apply

1 Mark(s)

Reference host or bind variables in a PL/SQL block of code
Tasks that compute and return multiple values to the calling environment
Tasks that compute a value that must be returned to the calling environment
Tasks performed in SQL that increase data independence by processing complex data analysis within the Oracle server, rather than by retrieving the data into an application

Which two statements are true about the instead of triggers? Choose that to apply.

1 Mark(s)

Delete operations cannot be performed using the instead of triggers.
The instead or triggers must be created to add or modify datathrough any view.
The instead of triggers can be written only for views, and the before and after timing options are not valid
The check option for views is not enforced when Insertions or updates to the view are performed by using the instead of triggers.

View the Exhibit and examine the code.

CREATE OR REPLACE PROCEDURE wording IS

 TYPE Definition IS RECORD {

         word VARCHAR2(20),

         meaning VARCHAR2(200));

 lexicon Definition;

 PROCEDURE add_entry (word_list IN OUT Definition)

       BEGIN

           word_list.word := 'aardvark';

           lexicon word :=  'aardwolf';

       END add_entry;

  BEGIN

       add_entry(lexicon);

       DBMS_OUTPUT.PUT_LINE(word_list.word);

       DBMS_OUTPUT.PUT_LINE(lexicon.word);

 END wording;

/

Why does the code give an error on execution?

View the Exhibit and examine the code.

CREATE OR REPLACE PROCEDURE wording IS

 TYPE Definition IS RECORD {

         word VARCHAR2(20),

         meaning VARCHAR2(200));

 lexicon Definition;

 PROCEDURE add_entry (word_list IN OUT Definition)

       BEGIN

           word_list.word := 'aardvark';

           lexicon word :=  'aardwolf';

       END add_entry;

  BEGIN

       add_entry(lexicon);

       DBMS_OUTPUT.PUT_LINE(word_list.word);

       DBMS_OUTPUT.PUT_LINE(lexicon.word);

 END wording;

/

Why does the code give an error on execution?

1 Mark(s)

because the WORD_LIST variable is not visible in procedure wording
because the lexicon variable is not visible in procedure ADD_ENTRY
because the lexicon variable is not initialized in procedure wording
because the WORD_LIST parameter in out mode cannot be of a record data type

Identify two situations where the DBMS_SQL package should be used? Choose that to apply.

1 Mark(s)

The SELECT list is not known until run time.
The dynamic SQL statement retrieves rows into records.
You do not know how many columns a select statement will return, or what their data typeswill.
You must use the % found SQL cursor attribute after issuing a dynamic SQL statement that is an insert or update statement.

View the Exhibit and examine the structure of the employees table.

Name            Null?         Type
--------------- ------------  -----------
EMPLOYEE_ID     NOT NULL      NUMBER(6)

FIRST_NAME                    VARCHAR2(20)

LAST_NAME       NOT NULL      VARCHAR2(25)

HIRE_DATE       NOT NULL      DATE

JOB_ID          NOT NULL      VARCHAR2(10)

SALARY                        NUMBER(8,2)

COMMISSION_PCT                NUMBER(2,2)

MANAGER_ID                    NUMBER(6)

DEPARTMENT_ID                 NUMBER(4)

Examine the following block of code

SQL > DECLARE

           v_sal NUMBER;
  
           v_name  VARCHAR2(30);

           v_tenure  NUMBER;

           v_hire_date  DATE;

       BEGIN
        
          SELECT AVG(salary) INTO v_sal FROM employee;

          SELECT hire_date,DECODE(salary,v_sal,last_name,'NA')

                           INTO v_hire_date,v_name

                           FROM employees

                           WHERE employee_id = 195;

          v_tenure := MONTHS_BETWEEN {CURRENT_DATE,v_hire_date);

       END;

/

What is the outcome when the above code is executed?

View the Exhibit and examine the structure of the employees table.

Name            Null?         Type
--------------- ------------  -----------
EMPLOYEE_ID     NOT NULL      NUMBER(6)

FIRST_NAME                    VARCHAR2(20)

LAST_NAME       NOT NULL      VARCHAR2(25)

HIRE_DATE       NOT NULL      DATE

JOB_ID          NOT NULL      VARCHAR2(10)

SALARY                        NUMBER(8,2)

COMMISSION_PCT                NUMBER(2,2)

MANAGER_ID                    NUMBER(6)

DEPARTMENT_ID                 NUMBER(4)

Examine the following block of code

SQL > DECLARE

           v_sal NUMBER;
  
           v_name  VARCHAR2(30);

           v_tenure  NUMBER;

           v_hire_date  DATE;

       BEGIN
        
          SELECT AVG(salary) INTO v_sal FROM employee;

          SELECT hire_date,DECODE(salary,v_sal,last_name,'NA')

                           INTO v_hire_date,v_name

                           FROM employees

                           WHERE employee_id = 195;

          v_tenure := MONTHS_BETWEEN {CURRENT_DATE,v_hire_date);

       END;

/

What is the outcome when the above code is executed?

1 Mark(s)

It executes successfully.
It gives an error because decodecannot be used in a PL/SQL block.
It gives an error because the AVG function cannot be used in a PL/SQL block
It gives an error because the MONTHS_BETWEEN function cannot be used in a PL/SQL block.
It gives an error because both the AVG and decodefunctions cannot be used in a PL/SQL block.

Which statements are true about PL/SQL procedures? Choose that to apply.

1 Mark(s)

Users with definers rights who are granted access to a procedure that updates a table must be granted access to the table itself.
Reuse of parsed PL/SQL code that becomes available in the shared SQL area of the server avoids the parsing overhead of SQL statements at run time.
Depending on the number of calls, multiple copies of the procedure are loaded into memory for execution by multiple users to speed up performance.
A PL/SQL procedure executing on the Oracle database can call an external procedure or function that is written in a different programming language, such as C or Java.

View the exhibit and examine the structure of the products table.

Name                Null?        Type
------------------- ------------ --------------
PROD_ID             NOT NULL     NUMBER(4)

PROD_NAME           NOT NULL     VARCHAR2(10)

PROD_LIST_PRICE     NOT NULL     NUMBER(0,2)

PROD_VALID                       VARCHAR2(1)

Examine the following code:

CREATE TABLE debug_output (msg VARCHAR2(100));

CREATE OR REPLACE PROCEDURE debugging (msg VARCHAR2) AS
  
  PRAGMA AUTONOMOUS_TRANSACTION;
   
  BEGIN
        INSERT INTO debug_output VALUES (msg);
         
        COMMIT
  
  END debugging;
  
  /
 
  CREATE OR REPLACE PROCEDURE delete_details(p_id NUMBER) AS


  msg VARCHAR2(100);

  BEGIN
 
       DELETE FROM products WHERE prod_id = p_id;

       COMMIT;
  
  EXCEPTION
        
       WHEN OTHERS THEN

       msg := SUBSTR(sqlerrm,100);

       debugging (msg);

  END delete_details;

  /

Which statement is true when the procedure DELETE_DETAILS is invoked ?

View the exhibit and examine the structure of the products table.

Name                Null?        Type
------------------- ------------ --------------
PROD_ID             NOT NULL     NUMBER(4)

PROD_NAME           NOT NULL     VARCHAR2(10)

PROD_LIST_PRICE     NOT NULL     NUMBER(0,2)

PROD_VALID                       VARCHAR2(1)

Examine the following code:

CREATE TABLE debug_output (msg VARCHAR2(100));

CREATE OR REPLACE PROCEDURE debugging (msg VARCHAR2) AS
  
  PRAGMA AUTONOMOUS_TRANSACTION;
   
  BEGIN
        INSERT INTO debug_output VALUES (msg);
         
        COMMIT
  
  END debugging;
  
  /
 
  CREATE OR REPLACE PROCEDURE delete_details(p_id NUMBER) AS


  msg VARCHAR2(100);

  BEGIN
 
       DELETE FROM products WHERE prod_id = p_id;

       COMMIT;
  
  EXCEPTION
        
       WHEN OTHERS THEN

       msg := SUBSTR(sqlerrm,100);

       debugging (msg);

  END delete_details;

  /

Which statement is true when the procedure DELETE_DETAILS is invoked ?

1 Mark(s)

It executes successfully but no error messages get recorded in the DEBUG_OUTPUT table
It executes successfully and any error messages get recorded in the DEBUG_OUTPUT table.
It gives an error because PRAGMA AUTONOMOUS_TRANSACTION can be used only in packaged procedures.
It gives an error because procedures containing PRAGMA AUTONOMOUS_TRANSACTION cannot be called from the exception section.

Examine the following block of code;

DECLARE
 
    status            VARCHAR2(10) NOT NULL DEFAULT 'TRUE';
    
    net_value         NUMBER := 555;

    done              BOOLEAN;

    valid_id          BOOLEAN := TRUE;

BEGIN
   
    done := (net_value > 100);
  
    status := valid_id;


END;

/

which line in the above code would result in errors upon execution?

Examine the following block of code;

DECLARE
 
    status            VARCHAR2(10) NOT NULL DEFAULT 'TRUE';
    
    net_value         NUMBER := 555;

    done              BOOLEAN;

    valid_id          BOOLEAN := TRUE;

BEGIN
   
    done := (net_value > 100);
  
    status := valid_id;


END;

/

which line in the above code would result in errors upon execution?

1 Mark(s)

line 5
line 8
line 2
line 7

View the Exhibit and examine the structure of the EMP table.

SQL > DECLARE

          v_sal NUMBE;

      BEGIN

       SELECT sal INTO v_sal FROM emp WHERE empno = 130;

       INSERT INTO emp(empno,ename,sal) VALUES (185,'JONES',v_sal+1000);

      END;

/

Which stages are performed when the above block is executed ? Choose that to apply.

View the Exhibit and examine the structure of the EMP table.

SQL > DECLARE

          v_sal NUMBE;

      BEGIN

       SELECT sal INTO v_sal FROM emp WHERE empno = 130;

       INSERT INTO emp(empno,ename,sal) VALUES (185,'JONES',v_sal+1000);

      END;

/

Which stages are performed when the above block is executed ? Choose that to apply.

1 Mark(s)

Bind
Parse
Fetch
Execute

View the Exhibit and examine the structure of the EMP table.

SQL > desc emp

Name             Null?       Type
---------------  ----------  -----------
EMPNO            NOT NULL    NUMBER(4)

ENAME                        VARCHAR2(10)

JOB                          VARCHAR2(9)

MGR                          NUMBER(4)

HIREDATE                     DATE

SAL                          NUMBER(7,2)

COMM                         NUMBER(7,2)

DEPTNO                       NUMBER(2)

Which two rules should you apply to ensure that the overloading feature is used successfully? Choose that to apply.

View the Exhibit and examine the structure of the EMP table.

SQL > desc emp

Name             Null?       Type
---------------  ----------  -----------
EMPNO            NOT NULL    NUMBER(4)

ENAME                        VARCHAR2(10)

JOB                          VARCHAR2(9)

MGR                          NUMBER(4)

HIREDATE                     DATE

SAL                          NUMBER(7,2)

COMM                         NUMBER(7,2)

DEPTNO                       NUMBER(2)

Which two rules should you apply to ensure that the overloading feature is used successfully? Choose that to apply.

1 Mark(s)

The procedures can be either stand-alone or packaged.
The procedures should be created only as packaged subprograms.
The procedures should be created only as stand-alone subprograms.
Each subprograms formal parameters should differ in both name and data type.
The formal parameters of each subprogram should differ in data type but can use the same names

Examine the following code:

CREATE OR REPLACE FUNCTION f2 (p_pl NUMBER)

     RETURN NUMBER PARALLEL_ENABLE IS

     BEGIN

         RETURN p_pl * 2;

     END f2;

Which two statements are true about the above function? Choose that to apply.

Examine the following code:

CREATE OR REPLACE FUNCTION f2 (p_pl NUMBER)

     RETURN NUMBER PARALLEL_ENABLE IS

     BEGIN

         RETURN p_pl * 2;

     END f2;

Which two statements are true about the above function? Choose that to apply.

1 Mark(s)

It can be used only in a parallelized query.
It can be usedin both a parallelized query and a parallelized DML statement.
It can be used only in a parallelized data manipulation language (DML) statement.
It can have a separate copy run in each of the multiple processes when called from a SQL statement that is run in parallel.
It requires a PRAGMA RESTRICT_REFERENCES declaration with RNDS, WNDS, RNPS, and WNPS specified in order to use parallel optimization.

Examine the following command:

SQL > ALTER SESSION

SET plsql_warnings *

'enable: severe',

'enable: performance',

'ERROR: 05003';

What is the implication of the above command?

Examine the following command:

SQL > ALTER SESSION

SET plsql_warnings *

'enable: severe',

'enable: performance',

'ERROR: 05003';

What is the implication of the above command?

1 Mark(s)

It issues a warning whenever ERROR: 05003 occur during compilation.
It causes the compilation tofail whenever the warning ERROR.05003 occurs.
It issues warnings whenever the code causes an unexpected action or wrong results performance problems
It causes the compilation to fail whenever the code gives wrong results or contains statements that are never executed.

Which two statements are correct about the usage of parameters in functions? Choose that to apply.

1 Mark(s)

Functions can have only in mode parameters.
Functions called in SQL statements cannot haveout or in out mode parameters.
Functions having in, out, or in out parameters can be called only in named PL/SQL subprograms
Functions having in, out, or in out parameters can be called in PL/SQL procedures and anonymous blocks.

The STRING_TAB table has the following structure:

Name           Null?       Type
-------------  ---------   ---------------
STRING1                     VARCHAR2(100)

View the Exhibit and examine the code.

SQL >SET SERVEROUTPUT ON

SQL >DECALRE

       in_string  VARCHAR2(25) := 'This is my test string.';

       out_string VARCHAR2(25);

       PROCEDURE double (original IN VARCHAR2,new_string OUT VARCHAR2) IS

       BEGIN

            new_string := original || '+' || original;

       EXCEPTION 
        
           WHEN VALUE_ERROR THEN

                 DBMS_OUTPUT.PUT_LINE('ouput buffer not long enough.');
   
                 COMMIT;
      
       END;

       BEGIN

            double(in_string,out_string);

            DBMS_OUTPUT.PUT_LINE(in_string) || '-' || out_string);

       END;

       /

What is the outcome on execution?

The STRING_TAB table has the following structure:

Name           Null?       Type
-------------  ---------   ---------------
STRING1                     VARCHAR2(100)

View the Exhibit and examine the code.

SQL >SET SERVEROUTPUT ON

SQL >DECALRE

       in_string  VARCHAR2(25) := 'This is my test string.';

       out_string VARCHAR2(25);

       PROCEDURE double (original IN VARCHAR2,new_string OUT VARCHAR2) IS

       BEGIN

            new_string := original || '+' || original;

       EXCEPTION 
        
           WHEN VALUE_ERROR THEN

                 DBMS_OUTPUT.PUT_LINE('ouput buffer not long enough.');
   
                 COMMIT;
      
       END;

       BEGIN

            double(in_string,out_string);

            DBMS_OUTPUT.PUT_LINE(in_string) || '-' || out_string);

       END;

       /

What is the outcome on execution?

1 Mark(s)

It displays Output buffer not long enough. This is my test string.-.
It displays only Output buffer not long enough, and exits the anonymous block.
It displays only This is my test string. - Because EXCEPTION should have been defined in the anonymous block to getthe error message.
It does not display any of the MEMS_PUTPUT messages and gives an error because a transaction control statement cannot be used in the exception section of a procedure.

View the Exhibit and examine the structure of the customer table.

Name                    Null?           Type
---------------------   -------------   -------------
CUST_ID                 NOT NULL        NUMBER

CUST_LAST_NAME          NOT NULL        VARCHAR2(40)

CUST_CITY               NOT NULL        VARCHAR2(30)

CUST_CREDIT_LIMIT                        NUMBER

CUST_CATEGORY                            VARCHAR2(20)

Examine the following trigger code:

CREATE OR REPLACE TRIGGER max_credit_limit

    BEFORE INSERT OR UPDATE OF cust_category ON customer

    FOR EACH ROW

    WHEN (NEW/cust_category IS NULL)

 BEGIN

    IF INSERTING THEN

        :NEW.cust_category := 'C';

        :NEW.cust_creadit_limit := 8000;

    ELSEIF UPDATING THEN

        :NEW.cust_category := :OLD.cust_category;

        :NEW.cust_credit_limit := Old_cust_credit_limit

    END IF;

 END;

 /

What is the outcome when the above trigger is compiled?

View the Exhibit and examine the structure of the customer table.

Name                    Null?           Type
---------------------   -------------   -------------
CUST_ID                 NOT NULL        NUMBER

CUST_LAST_NAME          NOT NULL        VARCHAR2(40)

CUST_CITY               NOT NULL        VARCHAR2(30)

CUST_CREDIT_LIMIT                        NUMBER

CUST_CATEGORY                            VARCHAR2(20)

Examine the following trigger code:

CREATE OR REPLACE TRIGGER max_credit_limit

    BEFORE INSERT OR UPDATE OF cust_category ON customer

    FOR EACH ROW

    WHEN (NEW/cust_category IS NULL)

 BEGIN

    IF INSERTING THEN

        :NEW.cust_category := 'C';

        :NEW.cust_creadit_limit := 8000;

    ELSEIF UPDATING THEN

        :NEW.cust_category := :OLD.cust_category;

        :NEW.cust_credit_limit := Old_cust_credit_limit

    END IF;

 END;

 /

What is the outcome when the above trigger is compiled?

1 Mark(s)

It compiles successfully.
It gives an error because the when condition is not valid.
It gives an error because when cannot be used for row-level triggers.
It gives an error because the statements under updating are not valid.
It gives an error because the new qualifier in the when clause requires a colon prefix.

What is the correct definition of the persistent state of a packaged variable?

1 Mark(s)

It is a private variable defined in a procedure or function within apackage body whose value is consistent within a user session.
It is a public variable in a package specification whose value is consistent within a user session.
It is a private variable in a package body whose value is consistent across all currentactive sessions
It is a public variable in a package specification whose value is always consistent across all current active sessions.

View Exhibit 1 and examine the structure of the employees table.

NAME             NULL?             TYPE
--------------   -------------     --------------
EMPLOYEE_ID      NOT NULL          NUMBER(6)

FIRST_NAME                         VARCHAR2(20)

LAST_NAME        NOT NULL          VARCHAR2(25)

HIRE_DATE        NOT NULL          DATE

JOB_ID           NOT NULL          VARCHAR2(10)

SALARY                             NUMBER(8,2)

COMISSION_PCT                      NUMBER(2,2)

MANAGER_ID                         NUMBER(6)

DEPARTMENT_ID                      NUMBER(4)

View Exhibit 2 and examine the code

DECLARE

       emp_num NUMBER(6) := 120;
       
       sal NUMBER;

       FUNCTION increase (emp_num NUMBER)

          RETURN number IS

          inc_amt NUMBER;

          BEGIN
             
           SELECT salary INTO sal FROM employee WHERE employee_id = emp_num;
         
           inc_amt := sal * .10;
   
           RETURN inc_amt;
         
          END;
       
       PROCEDURE raise_salary (emp_id NUMBER) IS

         amt NUMBER;

         BEGIN
 
              amt :=  increase (emp_num);

              UPDATE employee SET salary = salary + amt 

                               WHERE employee_id = emp_id ;
        
         END raise_salary;

BEGIN

    raise_salary(emp_num)

    COMMIT;

END;

/

what would be the outcome when the code is executed?

View Exhibit 1 and examine the structure of the employees table.

NAME             NULL?             TYPE
--------------   -------------     --------------
EMPLOYEE_ID      NOT NULL          NUMBER(6)

FIRST_NAME                         VARCHAR2(20)

LAST_NAME        NOT NULL          VARCHAR2(25)

HIRE_DATE        NOT NULL          DATE

JOB_ID           NOT NULL          VARCHAR2(10)

SALARY                             NUMBER(8,2)

COMISSION_PCT                      NUMBER(2,2)

MANAGER_ID                         NUMBER(6)

DEPARTMENT_ID                      NUMBER(4)

View Exhibit 2 and examine the code

DECLARE

       emp_num NUMBER(6) := 120;
       
       sal NUMBER;

       FUNCTION increase (emp_num NUMBER)

          RETURN number IS

          inc_amt NUMBER;

          BEGIN
             
           SELECT salary INTO sal FROM employee WHERE employee_id = emp_num;
         
           inc_amt := sal * .10;
   
           RETURN inc_amt;
         
          END;
       
       PROCEDURE raise_salary (emp_id NUMBER) IS

         amt NUMBER;

         BEGIN
 
              amt :=  increase (emp_num);

              UPDATE employee SET salary = salary + amt 

                               WHERE employee_id = emp_id ;
        
         END raise_salary;

BEGIN

    raise_salary(emp_num)

    COMMIT;

END;

/

what would be the outcome when the code is executed?

1 Mark(s)

It executes successfully.
It gives an error because the SAL variable isnot visible in the increase function.
It gives an error because the increase function cannot be called from the RAISE_SALARY procedure
It gives an error because the increase function and the RAISE_SALARY procedure should be declared at the beginningof the declare section before all the other declarations.

/temp/my_files is an existing folder in the server, facultylist.txt is an existing text file in this folder.

Examine the following commands that are executed by the DBA:

SQL > CREATE DIRECTION my_dir AS '/temp/my_files';

SQL > GRANT READ ON DIRECTORY my_dir To public:

View the Exhibit and examine the procedure created by user SCOTT to read the list of faulty names from the text file:

CREATE OR REPLACE PROCEDURE read_files (dirname VARCHAR2,txtfile VARCHAR2) IS

       f_file UTL_FILE.FILE_TYPE;

       v_buffer VARCHAR2(200);

 BEGIN

       f_file := UTL_FILE.FOPEN (dirname,txtfile,'R');

LOOP
 
       UTL_FILE.GET_LINE(f_file,v_buffer);

       DBMS_OUTPUT.PUT_LINE(v_buffer);

END LOOP;

UTL_FILE.FCLOSE(f_file);

END read_file;

/

SCOTT executes the procedure as follows

SQL > SET SERVEROUTPUT ON

SQL > EXEC read_file('MY_DIR',FACULTYLIST.TXT')

What is the outcome?

/temp/my_files is an existing folder in the server, facultylist.txt is an existing text file in this folder.

Examine the following commands that are executed by the DBA:

SQL > CREATE DIRECTION my_dir AS '/temp/my_files';

SQL > GRANT READ ON DIRECTORY my_dir To public:

View the Exhibit and examine the procedure created by user SCOTT to read the list of faulty names from the text file:

CREATE OR REPLACE PROCEDURE read_files (dirname VARCHAR2,txtfile VARCHAR2) IS

       f_file UTL_FILE.FILE_TYPE;

       v_buffer VARCHAR2(200);

 BEGIN

       f_file := UTL_FILE.FOPEN (dirname,txtfile,'R');

LOOP
 
       UTL_FILE.GET_LINE(f_file,v_buffer);

       DBMS_OUTPUT.PUT_LINE(v_buffer);

END LOOP;

UTL_FILE.FCLOSE(f_file);

END read_file;

/

SCOTT executes the procedure as follows

SQL > SET SERVEROUTPUT ON

SQL > EXEC read_file('MY_DIR',FACULTYLIST.TXT')

What is the outcome?

1 Mark(s)

PRO - PL SQL Programming - 1 : Question 1 of 20