Intermediate
23-11. | Explain the output displayed in the following session in SQL*Plus: SQL> SET SERVEROUTPUT ON SQL> EXEC DBMS_OUTPUT.PUT_LINE ( ' Where oh where did my spaces go?'); Where oh where did my spaces go? |
23-12. | Enable DBMS_OUTPUT in your SQL*Plus session with a buffer size of 500,000 bytes, request that leading spaces and blank lines not be ignored, and also request that output from the package be wrapped at the SQL*Plus line length. |
23-13. | What variation of the SET SERVEROUTPUT statement allows you to display the DBMS_OUTPUT buffer within the SQL*Plus line length, but doesn’t break words? |
23-14. | What variation of the SET SERVEROUTPUT statement allows you to display the DBMS_OUTPUT buffer, but truncates any text that exceeds the SQL*Plus line length? |
23-15. | What do you see on the screen when you execute this block, and why do you see it? DECLARE oracle_consultant_egosize INTEGER := 10000000; ego_too_big BOOLEAN; BEGIN ego_too_big := oracle_consultant_egosize > 500; DBMS_OUTPUT.PUT_LINE (ego_too_big); END; |
23-16. | What do you see on the screen when you execute this block, and why do you see it? BEGIN
DBMS_OUTPUT.PUT_LINE (
RPAD (USER, 2000, ' is connected as ' || USER);
END; |
23-17. | Suppose you are working in an environment that does not automatically flush the DBMS_OUTPUT buffer to the screen. What DBMS_OUTPUT program can you use to extract that data into your own data structure? |
23-18. | Write a procedure that extends DBMS_OUTPUT.PUT_LINE functionality to the Boolean datatype. |
23-19. | Explain ... |
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access