Oracle 1z0-144 Dumps

A package must have both specification and body.

A package body can exist without the package specification.

A package specification can exist without the package body.

When a packaged public variable is called for the first time in a session, the entire package is loaded into memory.

The program abruptly terminates and an exception is raised.

The program executes successfully and the output is No ROWS_FOUND.

The program executes successfully and the query fetches a null value in the V_LNAME variable.

Program executes successfully, fetches a NULL value in the V_LNAME variable and an exception is raised.

Reference tables indirectly by using views.

Reference tables directly avoid using views.

When adding new items to a package, add them to the end of the package.

When adding new items to a package, add them to the beginning of the package.

It executes successfully and all the rows are updated.

It gives an error but saves the inserted rows and the update to the first row.

It gives an error but saves the inserted rows; however, no rows are updated.

It gives an error and all the data manipulation language (DML) statements are rolled back

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.

A procedure can contain a return statement without a value.

A function can return multiple values using a single return clause.

A procedure can be executed as part of a SQL expression or as a PL/SQL statement,

A function can contain zero or more parameters that are transferred from the calling environment.

The PL/SQL block execution terminates immediately after the exit statement.

The loop completes immediately and control passes to the statement after end loop

The statements after the exit statement in the Iteration are not executed before terminating the LOOP.

The current iteration of the loop completes immediately and control passes to the next iteration of the loop.

Both Output statements show different values.

Both output statements show exactly the same values.

It gives an error because the nested blocks are not labeled.

It gives an error because the V_CUSTOMER variable have different types in the nested blocks

The PL/SQL wrapper detects and reports only syntax errors.

The PL/SQL wrapper detects and reports both syntax and semantic errors.

When wrapping a package or object type, both the body and specification should be wrapped.

When wrapping a package or object type, only the body should be wrapped, not the specification.

To change a wrapped object, the original source code needs to be modified and then wrapped again

To change a wrapped object, the wrapped code can be unwrapped, modified In a text file, and then wrapped again.

Line 2

Line 3

Line 4

Line 5

Line 6

It is a private variable defined in a procedure or function within a package 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 current active sessions.

It is a public variable in a package specification whose value is always consistent across all current active sessions.

It executes successfully and creates the report.

It gives an error because the text file should be opened in append mode.

It gives an error because the "no data found" condition is not handled to come out of the loop.

It gives an error because user SCOTT should be granted both read and write privileges to the directory alias.

It executes but no data is written to the text file because the FFLUSH subprogram is not used to write all the data buffered in memory to a file.

when you want to lock the rows fetched by the cursor

when you want to update or delete the result set without affecting the rows in the table

when you want the database not to wait if the requested rows are locked by another user

when you want to ensure that the current rows fetched by the cursor are updated or deleted

when you want to retrieve an entire row from a table and perform calculations

when you know the number of elements in advance and the elements are usually accessed sequentially

when you want to create a separate lookup table with multiple entries for each row of the main table, and access it through join queries

when you want to create a relatively small lookup table, where the collection can be constructed in memory each time a subprogram is invoked

The execution fails because of the misplaced else clause.

The execution is successful even if there is no employee with EMPLOYEE_ID 115.

The execution falls and throws exceptions if no employee with EMPLOYEE_ID us is found.

The execution is successful, but it displays an incorrect output if no employee with EMPLOYEE_ID 115 is found.