Interview Question for PL/SQL Oracle Consultant

1.

Diff b/w Package Spec & Body Packages provide a method of encapsulating and storing related procedures, functions and other package constructs as a unit in the database. They offer increased functionality (for example, global package variables can be declared and used by any procedure in the package). They also improve performance (for example, all objects of the package are parsed, compiled, and loaded into memory once). Package specification contains declarations of public constructs where as the package body contains definitions of all those public constructs and declarations & definitions of private constructs. P/L SQL Tables / Arrays PL/SQL tables are declared in the declaration portion of the block. A table is a composite datatype in PL/SQL. PL/SQL tables can have one column and a primary key neither of which can be named. The column can be any scalar type but primary key should be a BINARY_INTEGER datatype. Various Cursor Attributes SQL%ROWCOUNT: Number of rows affected by most recent SQL statement. SQL%FOUND: Boolean attribute that evaluates to TRUE if most recent SQL statement affects one or more rows. SQL%NOTFOUND: Boolean attribute that evaluates to TRUE if most recent SQL statement does not affect any row. SQL%ISOPEN: Always evaluates to FALSE because P/L SQL closes implicit cursors immediately after they are executed. Different Database Triggers Database triggers are PL/SQL, Java, or C procedures that run implicitly whenever a table or view is modified or when some user actions or database system actions occur. Database triggers can be used in a variety of ways for managing your database. For example, they can automate data generation, audit data modifications, enforce complex integrity constraints, and customize complex security authorizations. Row Triggers A row trigger is fired each time the table is affected by the triggering statement. For example, if an UPDATE statement updates multiple rows of a table, a row trigger is fired once for each row affected by the UPDATE statement. If a triggering statement affects no rows, a row trigger is not executed at all. Row triggers are useful if the code in the trigger action depends on data provided by the triggering statement or rows that are affected. Statement Triggers A statement trigger is fired once on behalf of the triggering statement, regardless of the number of rows in the table that the triggering statement affects (even if no rows are affected). For example, if a DELETE statement deletes several rows from a table, a statement-level DELETE trigger is fired only once, regardless of how many rows are deleted from the table. Statement triggers are useful if the code in the trigger action does not depend on the data provided by the triggering statement or the rows affected. For example, if a trigger makes a complex security check on the current time or user, or if a trigger generates a single audit record based on the type of triggering statement, a statement trigger is used. BEFORE vs. AFTER Triggers When defining a trigger, you can specify the trigger timing. That is, you can specify whether the trigger action is to be executed before or after the triggering statement. BEFORE and AFTER apply to both statement and row triggers. BEFORE Triggers BEFORE triggers execute the trigger action before the triggering statement. This type of trigger is commonly used in the following situations: BEFORE triggers are used when the trigger action should determine whether the triggering statement should be allowed to complete. By using a BEFORE trigger for this purpose, you can eliminate unnecessary processing of the triggering statement and its eventual rollback in cases where an exception is raised in the trigger action. BEFORE triggers are used to derive specific column values before completing a triggering INSERT or UPDATE statement. AFTER Triggers AFTER triggers execute the trigger action after the triggering statement is executed. AFTER triggers are used in the following situations:

2.

3.

4.

Interview Question for PL/SQL Oracle Consultant AFTER triggers are used when you want the triggering statement to complete before executing the trigger action. If a BEFORE trigger is already present, an AFTER trigger can perform different actions on the same triggering statement. Combinations Using the options listed in the previous two sections, you can create four types of triggers: BEFORE statement trigger Before executing the triggering statement, the trigger action is executed. BEFORE row trigger Before modifying each row affected by the triggering statement and before checking appropriate integrity constraints, the trigger action is executed provided that the trigger restriction was not violated. AFTER statement trigger After executing the triggering statement and applying any deferred integrity constraints, the trigger action is executed. AFTER row trigger After modifying each row affected by the triggering statement and possibly applying appropriate integrity constraints, the trigger action is executed for the current row provided the trigger restriction was not violated. Unlike BEFORE row triggers, AFTER row triggers lock rows. New Database Triggers Startup, Shutdown, Logon, Logoff, Alter, Create, Drop Inline Views & Top N Analysis The Inline view: It is a construct in Oracle SQL where you can place a query in the SQL FROM, clause, just as if the query was a table name. A common use for in-line views in Oracle SQL is to simplify complex queries by removing join operations and condensing several separate queries into a single query. Top N Analysis: The task of retrieving the top or bottom N rows from a database table. You can do so either by using the ROWNUM pseudocolumn available in several versions of Oracle or by utilizing new analytic functions available in Oracle 8i: RANK () and DENSE_RANK (). Using the ROWNUM Pseudocolumn One-Way to solve this problem is by using the Oracle pseudocolumn ROWNUM. For each row returned by a query, the ROWNUM pseudocolumn returns a number indicating the order in which Oracle selects the row from a table or set of joined rows. E.g. To select top 5 rows SELECT Empno, Ename, Job, Mgr, Hiredate, Sal FROM (SELECT Empno, Ename, Job, Mgr, Hiredate, Sal FROM Emp ORDER BY NVL (Sal, 0) DESC) WHERE ROWNUM < 6; Utilizing Oracle 8i's Ranking Functions Another way to perform a top-N query uses the new Oracle 8i feature called "analytic functions. SELECT Empno, Ename, Job, Mgr, Sal, RANK () OVER (ORDER BY SAL Desc NULLS LAST) AS Rank, DENSE_RANK () OVER (ORDER BY SAL Desc NULLS LAST) AS Drank FROM Emp ORDER BY SAL Desc NULLS LAST; The difference between RANK () and DENSE_RANK () is that RANK () leaves gaps in the ranking sequence when there are ties. In our case, Scott and Ford tie for second place with a $3,000 salary; Jones' $2,975 salary brings him in third place using DENSE_RANK () but only fourth place using RANK (). The NULLS FIRST | NULLS LAST clause determines the position of rows with NULL values in the ordered query. Normalization / De-Normalization Normalization: It's the process of efficiently organizing data in a database. There are two goals of the normalization process: eliminate redundant data (for example, storing the same data in more than one table) and ensure data dependencies make sense (only storing related data in a table). Both of these are worthy goals as they reduce the amount of space a database consumes and ensure that data is logically stored. 1. Eliminate Repeating Groups - Make a separate table for each set of related attributes,

5.

6.

Interview Question for PL/SQL Oracle Consultant and give each table a primary key. 2. Eliminate Redundant Data - If an attribute depends on only part of a multi-valued key, remove it to a separate table. 3. Eliminate Columns Not Dependent On Key - If attributes do not contribute to a description of the key, remove them to a separate table. 4. Isolate Independent Multiple Relationships - No table may contain two or more 1:n or n:m relationships that are not directly related. 5. Isolate Semantically Related Multiple Relationships - There may be practical constrains on information that justify separating logically related many-to-many relationships. 1st Normal Form (1NF) Def: A table (relation) is in 1NF if 1. There are no duplicated rows in the table. 2. Each cell is single-valued (i.e., there are no repeating groups or arrays). 3. Entries in a column (attribute, field) are of the same kind. Note: The order of the rows is immaterial; the order of the columns is immaterial. Note: The requirement that there be no duplicated rows in the table means that the table has a key (although the key might be made up of more than one columneven, possibly, of all the columns). 2nd Normal Form (2NF) Def: A table is in 2NF if it is in 1NF and if all non-key attributes are dependent on all of the key. Note: Since a partial dependency occurs when a non-key attribute is dependent on only a part of the (composite) key, the definition of 2NF is sometimes phrased as, "A table is in 2NF if it is in 1NF and if it has no partial dependencies." 3rd Normal Form (3NF) Def: A table is in 3NF if it is in 2NF and if it has no transitive dependencies. Boyce-Codd Normal Form (BCNF) Def: A table is in BCNF if it is in 3NF and if every determinant is a candidate key. 4th Normal Form (4NF) Def: A table is in 4NF if it is in BCNF and if it has no multi-valued dependencies. 5th Normal Form (5NF) Def: A table is in 5NF, also called "Projection-Join Normal Form" (PJNF), if it is in 4NF and if every join dependency in the table is a consequence of the candidate keys of the table. Domain-Key Normal Form (DKNF) Def: A table is in DKNF if every constraint on the table is a logical consequence of the definition of keys and domains. De-Normalization: Denormalization is a technique to move from higher to lower normal forms of database modeling in order to speed up database access. You may apply Denormalization in the process of deriving a physical data model from a logical form. Autonomous Transactions Autonomous Transaction is a new feature in ORACLE. It allows setting up independent transactions that can be called from within other transactions. It lets you suspend the main transaction (without committing or rolling back), perform some DML operations, commit or roll back those operations (without any effect on the main transaction), and then return to the main transaction. Being independent of the main transaction (almost like a separate session), an autonomous transaction does not see the uncommitted changes from the main transaction. It also does not share locks with the main transaction. As a result, it can get into a deadlock with its parent something the application developer should watch out for. As expected, changes committed by an autonomous transaction are visible to other sessions/transactions immediately, regardless of whether the main transaction is committed or not. These changes also become visible to the main transaction when it resumes, provided its isolation level is set to READ COMMITTED (which is the default). Any of the routines can be marked as autonomous simply by using the following syntax anywhere in the declarative section of the routine (putting it at the top is recommended for better readability): E.g. PRAGMA AUTONOMOUS_TRANSACTION; Here is an example of defining a stored procedure as autonomous: CREATE PROCEDURE process_ord_line_shipment (p_order_no number, p_line_no number) AS PRAGMA AUTONOMOUS_TRANSACTION; l_char_1 varchar2(100);

7.

Interview Question for PL/SQL Oracle Consultant BEGIN ... END; Bitmap/B-Tree Index (Difference, Advantages) A traditional B-Tree (balanced tree) index stores the key values and pointers in an inverted tree structure. The key to good B-Tree index performance is to build the index on columns having a lot of different values. Oracle describes this as "good selectivity" Oracle is able to quickly bypass rows that do not meet the search criteria when searching through indexes built on columns having a high degree of selectivity. Conversely, bitmapped indexes perform better when the selectivity of an index is poor. The fewer different values a bitmapped index contains, the better it will perform. Bitmap indexes, in certain situations, can provide impressive performance benefits. Bitmapped indexes are most appropriate for complex and ad-hoc queries that contain lengthy WHERE clauses on columns that have a limited number of different values (poor selectivity). Standard B-tree indexes are most effective for columns containing a high number of different values (good selectivity) and bitmapped indexes are most appropriate for columns with a limited number (poor selectivity) of possible values. SQL Loader (Different Types of Files/Contents) SQL*Loader is a bulk loader utility used for moving data from external files into the Oracle database. Its syntax is similar to that of the DB2 Load utility, but comes with more options. SQL*Loader supports various load formats, selective loading, and multi-table loads. When we speak of the SQL*Loader environment, we are referring to the database, the SQL*Loader executable, and all the different files that you need to be concerned with when using SQL*Loader. These are shown in Figure The SQL*Loader environment The SQL*Loader Control File The SQL*Loader control file is the key to any load process. The control file provides the following information to SQL*Loader: The name and location of the input data file The format of the records in the input data file The name of the table or tables to be loaded The correspondence between the fields in the input record and the columns in the database tables being loaded Selection criteria defining which records from the input file contain data to be inserted into the destination database tables. The names and locations of the bad file and the discard file The Log File The log file is a record of SQL*Loader's activities during a load session. It contains information such as the following: The names of the control file, log file, bad file, discard file, and data file The values of several command-line parameters A detailed breakdown of the fields and data types in the data file that was loaded Error messages for records that cause errors Messages indicating when records have been discarded A summary of the load that includes the number of logical records read from the data file, the number of rows rejected because of errors, the number of rows discarded because of selection criteria, and the elapsed time of the load Always review the log file after a load to be sure that no errors occurred, or at least that no unexpected errors occurred. This type of information is written to the log file, but is not displayed on the terminal screen. The Bad File and the Discard File Whenever you insert data into a database, you run the risk of that insert failing because of some type of error. Integrity constraint violations undoubtedly represent the most common type of error. However, other problems, such as the lack of free space in a tablespace, can also cause insert operations to fail. Whenever SQL*Loader encounters a database error while trying to load

8.

9.

Interview Question for PL/SQL Oracle Consultant a record, it writes that record to a file known as the bad file. Discard files, on the other hand, are used to hold records that do not meet selection criteria specified in the SQL*Loader control file. By default, SQL*Loader will attempt to load all the records contained in the input file. Procedure/Function (Difference) Procedure A procedure is a subprogram that performs a specific action Procedure Does and Does not return the Value. Procedure we can use (In, Out, InOut Parameter) You cannot use the procedure in select Statement. Execute as a PL/SQL statement No RETURN clause in the header Can return none, one, or many values Function A function is a subprogram that computes a value Invoke as part of an expression Must contain a RETURN clause in the header Must return a single value Must contain at least one RETURN statement Always return the Value. Function you cannot use the (In, Out, InOut Parameter) You can use the Function the in select Statement. Pragma A pragma is a directive to the PL/SQL compiler. Pragmas pass information to the compiler; they are processed at compile time but do not execute. If you include a call to a built-in package in a SQL statement, you must include a RESTRICT REFERENCES pragma in your code. This pragma tells the compiler the purity level (freedom from side effects) of a packaged program. Pragma keyword is used to give instructions to the compiler. There are 4 types of Pragmas: A) Exception_Init: - Tells the compiler to associate the specified error number with an identifier that has been declared an Exception in your current program or an accessible package. B) Restrict_References: - Tells the compiler the purity level of packaged program. The purity level is the degree to which a program does not read/write database tables and/or packaged variables. C) Serially_Reusable: - Tells the runtime engine that package data should not persist between references. This is used to reduce per-user memory requirements when the package data is only needed for duration of call and not the duration of session. D) Autonomous_Transactions: - Tells the compiler that the function, procedure, toplevel anonymous P/L SQL block, object method, or database trigger executes in its own transaction space. Purity Levels Prior to Oracle8i Release 8.1, it was necessary to assert the purity level of a packaged procedure or function when using it directly or indirectly in a SQL statement. Beginning with Oracle8i Release 8.1, the PL/SQL runtime engine determines a program's purity level automatically if no assertion exists. The RESTRICT_REFERENCES pragma asserts a purity level. The syntax for the RESTRICT_REFERENCES pragma is: PRAGMA RESTRICT_REFERENCES (program_name | DEFAULT, purity_level); The keyword DEFAULT applies to all methods of an object type or all programs in a package. There can be from one to five purity levels, in any order, in a comma-delimited list. The purity level describes to what extent the program or method is free of side effects. Side effects are listed in the following table with the purity levels they address. Purity Level Description Restriction WNDS Write No Database State Executes no INSERT, UPDATE, or DELETE statements. RNDS Read No Database State Executes no SELECT statements.

10.

11.

12.

Interview Question for PL/SQL Oracle Consultant WNPS Write No Package State Does not modify any package variables. RNPS Read No Package State Does not read any package variables. TRUST (Oracle8i) Does not enforce the restrictions declared but allows the compiler to trust they are true. The purity level requirements for packaged functions are different depending on where in the SQL statement the stored functions are used: To be called from SQL, all stored functions must assert WNDS. All functions not used in a SELECT, VALUES, or SET clause must assert WNPS. To be executed remotely, the function must assert WNPS and RNPS. To be executed in parallel, the function must assert all four purity levels or, in Oracle8i, use PARALLEL_ENABLED in the declaration. These functions must not call any other program that does not also assert the minimum purity level. If a package has an initialization section, it too must assert purity in Oracle7. If a function is overloaded, each overloading must assert its own purity level, and the levels don't have to be the same. To do this, place the pragma immediately after each overloaded declaration. Many of the built-in packages, including DBMS_OUTPUT, DBMS_PIPE, and DBMS_SQL, do not assert WNPS or RNPS, so their use in SQL stored functions is necessarily limited. Early Binding/Late Binding Early and Late Binding When you generate RPCs (remote procedure calls) using SQL*Module, you have a choice of early binding or late binding. Your choice of early or late binding is controlled by the BINDING option. When you choose early binding, SQL*Module generates a call to the procedure stored in the database, and also uses a time stamp that is associated with the call. The time stamp records the date and time (to the nearest second) that the stored procedure was last compiled. The time stamp is created by the Oracle database. If a host application calls the stored procedure through the interface procedure, and the time stamp recorded with the interface procedure is earlier than the time stamp on the stored procedure recorded in the database, an error is returned to the host application in the SQLCODE and/or SQLSTATE status parameter. The SQLCODE error is 4062 "time stamp of name has been changed". The late binding option, on the other hand, does not use a time stamp. If your application calls a stored procedure that has been recompiled since SQL*Module generated the interface procedure, no error is returned to the application. The advantages of late binding are Greater flexibility Changes in the stored procedure(s) are transparent to the user Gives behavior similar to interactive SQL (for example, SQL*PLus) The disadvantages of late binding are There might be additional performance overhead at runtime, due to the necessity of compiling the PL/SQL anonymous block. It is difficult to detect runtime PL/SQL compilation errors in the host application. For example, if the anonymous block that calls the late-bound procedure fails at runtime, there is no convenient way for the host application to determine the cause of the error. The lack of time-stamp capability means that changes, perhaps radical changes, in the stored procedure could be made after the host application was built, and the application would have no way of detecting this. Hot & Cold Backup A cold backup is a physical backup. During a cold backup the database is closed and not available to users. All files of the database are copied (image copy). The datafiles do not change during the copy so the database is in sync upon restore. Used when: Service level allows for some down time for backup A hot backup is a physical backup. In a hot backup the database remains open and available to users. All files of the database are copied (image copy). There may be changes to the database as the copy is made and so all log files of changes being made during the backup must be saved too. Upon a restore, the changes in the log files are reapplied to bring the database in sync. Used when:

13.

14.

Interview Question for PL/SQL Oracle Consultant A full backup of a database is needed Service level allows no down time for the backup A logical backup is an extract of the database. All SQL statements to create the objects and all SQL statements to populate the objects are included in the extract. Oracle provides a utility export, to create the extract. A partner utility, import, is used to bring the data back into the database. A logical backup can be done at the table, schema (or proxy owner), or database level. That is, we can extract only a list of specified tables, a list of specified schemas or the full database. Used to: Move or archive a database Move or archive a table(s) Move or archive a schema(s) Verify the structures in the database Background Processes in Oracle Background Process: Database writer (DBWR): Writes modified blocks from database buffer cache to the datafile. Log Writer (LGWR): Writes redo log entries to disk. Check Point: At specific times all modified databases buffers in the SGA are written to the data files by DBWR. This event is called Checkpoint. System Monitor (SMON): Performs instance recovery at instance startup Process Monitor (PMON): Performs process recovery when user process fails Archiver (ARCH): Copies on line redo log files to archival storage when they are full Dispatcher: For multi threaded server for each request one dispatcher process Lock: For parallel server mode for inter instance locking Types of SQL Statements There are basically 6 types of sql statments. They are a) Data Definition Language (DDL): The DDL statements define and maintain objects and drop objects. b) Data Manipulation Language (DML): The DML statements manipulate database data. c) Transaction Control Statements: Manage change by DML d) Session Control: Used to control the properties of current session enabling and disabling roles and changing .e.g: Alter Statements, Set Role e) System Control Statements: Change Properties of Oracle Instance. e.g.: Alter System f) Embedded Sql: Incorporate DDL, DML and T.C.S in Programming Language.e.g: Using the Sql Statements in languages such as 'C', Open, Fetch, execute and close What is Transaction (Its ACID Property) A transaction is a Logical unit of work that compromises one or more SQL Statements executed by a single User. According to ANSI, a transaction begins with first executable statement and ends when it is explicitly committed or rolled back. A transaction is an atomic unit of work that either fails or succeeds. There is no such thing as a partial completion of a transaction. Since a transaction can be made up of many steps, each step in the transaction must succeed for the transaction to be successful. If any one part of the transaction fails, then the entire transaction fails. When a transaction fails, the system needs to return to the state that it was in before the transaction was started. This is known as rollback. When a transaction fails, then the changes that had been made are said to be "rolled back." In effect, this is acting similar to the way the Undo command works in most word processors. When you select undo, the change that you just may have made is reversed. The transaction processing system is responsible for carrying out this undo. When a transaction processing system creates a transaction, it will ensure that the transaction will have certain characteristics. ACID is an acronym for atomicity, consistency, isolation, and durability. An atomic transaction is either fully completed, or is not begun at all. A transaction enforces consistency in the system state by ensuring that at the end of any transaction the system is in a valid state. When a transaction runs in isolation, it appears to be the only action that the system is carrying out at one time. A transaction is durable in that once it has been successfully completed, all of the changes it made to the system are permanent. Exceptions (User-Defined/Oracle Defined) Oracle includes about 20 predefined exceptions (errors) - we can allow Oracle to raise these

15.

16.

17.

18.

Interview Question for PL/SQL Oracle Consultant implicitly. For errors that don't fall into the predefined categories - declare in advance and allow oracle to raise an exception. For problems that are not recognized as an error by Oracle - but still cause some difficulty within your application - declare a User Defined Error and raise it explicitly Trap non-predefined errors by declaring them. You can also associate the error no. with a name so that you can write a specific handler. This is done with the PRAGMA EXCEPION_INIT pragma. PRAGMA (pseudoinstructions) indicates that an item is a 'compiler directive' running this has no immediate effect but causes all subsequent references to the exception name to be interpreted as the associated Oracle Error. When an exception occurs you can identify the associated error code/message with two supplied functions SQLCODE and SQLERRM. Trapping user-defined exceptions DECLARE the exception RAISE the exception Handle the raised exception Propagation of Exception handling in sub blocks If a sub block does not have a handler for a particular error it will propagate to the enclosing block - where it can be caught by more general exception handlers. RAISE_APPLICATION_ERROR (error_no, message [, {TRUE|FALSE}]); This procedure allows user defined error messages from stored sub programs - call only from stored sub prog. Error_no = a user defined no (between -20000 and -20999) TRUE = stack errors FALSE = keep just last This can either be used in the executable section of code or the exception section SGA (System Global Area) The SGA is a shared memory region allocated by the Oracle that contains Data and control information for one Oracle Instance. Oracle allocates the SGA when an instance starts and deallocates it when the instance shuts down. Each instance has its own SGA. Users currently connected to an Oracle server share the data in the SGA. For optimal performance, the entire SGA should be as large as possible (while still fitting in real memory) to store as much data in memory as possible and to minimize disk I/O. It consists of Database Buffer Cache and Redo log Buffer. The PGA (Program Global Area) is a memory buffer that contains data and control information for server process. A PGA is created by Oracle when a server process is started. The information in a PGA depends on the Oracle configuration. Candidate, Artificial (Derived) Primary Key, Unique & Primary Key Integrity Constraint An integrity constraint is a declarative way to define a business rule for a column of a table. An integrity constraint is a statement about a table's data that is always true and that follows these rules: If an integrity constraint is created for a table and some existing table data does not satisfy the constraint, then the constraint cannot be enforced. After a constraint is defined, if any of the results of a DML statement violate the integrity constraint, then the statement is rolled back, and an error is returned. Integrity constraints are defined with a table and are stored as part of the table's definition in the data dictionary, so that all database applications adhere to the same set of rules. When a rule changes, it only needs be changed once at the database level and not many times for each application. Candidate key: A relation (table) may contain more than one key. In this case, one of the keys is selected as the primary key and the remaining keys are called candidate keys. The candidate key constraint indicates that the table cannot contain two different rows with the same values under candidate key columns. Artificial (Derived) Primary Key A derived key comes from a sequence. Usually it is used when a concatenated key becomes too cumbersome to use as a foreign key.

19.

20.

Interview Question for PL/SQL Oracle Consultant

UNIQUE Constraints You can use UNIQUE constraints to ensure that no duplicate values are entered in specific columns that do not participate in a primary key. Although both a UNIQUE constraint and a PRIMARY KEY constraint enforce uniqueness, use a UNIQUE constraint instead of a PRIMARY KEY constraint when you want to enforce the uniqueness of a column, or combination of columns, that is not the primary key. Multiple UNIQUE constraints can be defined on a table, whereas only one PRIMARY KEY constraint can be defined on a table. FOREIGN KEY Constraints A foreign key (FK) is a column or combination of columns used to establish and enforce a link between the data in two tables. A link is created between two tables by adding the column or columns that hold one table's primary key values to the other table. This column becomes a foreign key in the second table. PRIMARY KEY Constraints A table usually has a column or combination of columns whose values uniquely identify each row in the table. This column (or columns) is called the primary key of the table and enforces the entity integrity of the table. A table can have only one PRIMARY KEY constraint, and a column that participates in the PRIMARY KEY constraint cannot accept null values. PCT Free & PCT Used PCT Free: This parameter tells oracle how much space to leave in each oracle block for future updates. This defaults to 10. If table will have large number of updates, a larger value is needed. If the table will be static, small value can be used. PCT Used: This parameter tells oracle the minimum level of space in a block to maintain. Default is 40. A block becomes a candidate for updates if its storage falls below PCTUSED. PCTUSED + PCTFREE should not exceed 100. A high PCTUSED value results in more efficient space utilization but higher overhead, as oracle must work harder to maintain the free block list. 2 Phase Commit Two Phase Commit: Oracle provides the same assurance of data consistency in a distributed environment as in a non-distributed environment. There is two phases: Prepare Phase initiating node called global co-ordinator notifies all sites involved in transaction to be ready to either commit or rollback the transaction. Commit Phase If there is no problem in prepare phase, then all sites commit their transactions. If network or node failure occurs then all sites rollback their transactions.

21.

22.

23.

Delete & Truncate Table If you want to delete all the rows in a table, TRUNCATE TABLE is faster than DELETE. DELETE physically removes rows one at a time and records each deleted row in the transaction log. TRUNCATE TABLE deallocates all pages associated with the table. For this reason, TRUNCATE TABLE is faster and requires less transaction log space than DELETE. TRUNCATE TABLE is functionally equivalent to DELETE with no WHERE clause, but TRUNCATE TABLE cannot be used with tables referenced by foreign keys. Both DELETE and TRUNCATE TABLE make the space occupied by the deleted rows available for the storage of new data. Truncate just resets the high-water mark. It does not delete any rows. If you delete rows, then whatever you have specified regarding the referential integrity will be done (ON DELETE SET NULL, or ON DELETE CASCADE, or the default which is to return ORA-02292 if the referential integrity constraint would be violated) whereas TRUNCATE just returns ORA-02266 if you have any enabled foreign key constraints referencing the table, even if the tables are empty. schema is the schema to contain the trigger. If you omit schema, Oracle creates the trigger in your own schema. TABLE specifies the schema and name of the table to be truncated. You can truncate indexorganized tables. This table cannot be part of a cluster. When you truncate a table, Oracle also automatically deletes all data in the table's indexes. SNAPSHOT LOG specifies whether a snapshot log defined on the table is to be preserved or

Interview Question for PL/SQL Oracle Consultant purged when the table is truncated. This clause allows snapshot master tables to be reorganized through export/import without affecting the ability of primary-key snapshots defined on the master to be fast refreshed. To support continued fast refresh of primary-key snapshots the snapshot log must record primary-key information. For more information about snapshot logs and the TRUNCATE command, see Oracle8 Replication. PRESERVE specifies that any snapshot log should be preserved when the master table is truncated. This is the default. PURGE specifies that any snapshot log should be purged when the master table is truncated. CLUSTER specifies the schema and name of the cluster to be truncated. You can only truncate an indexed cluster, not a hash cluster. When you truncate a cluster, Oracle also automatically deletes all data in the cluster's tables' indexes. DROP STORAGE deallocates the space from the deleted rows from the table or cluster. This space can subsequently be used by other objects in the tablespace. This is the default. The DROP STORAGE option deallocates all but the space specified by the table's MINEXTENTS parameter. REUSE STORAGE retains the space from the deleted rows allocated to the table or cluster. Storage values are not reset to the values when the table or cluster was created. This space can subsequently be used only by new data in the table or cluster resulting from inserts or updates. The DROP STORAGE and REUSE STORAGE options also apply to the space freed by the data deleted from associated indexes. Deleting rows with the TRUNCATE command is also more convenient than dropping and recreating a table because dropping and re-creating: invalidates the table's dependent objects, while truncating does not requires you to regrant object privileges on the table, while truncating does not requires you to re-create the table's indexes, integrity constraints, and triggers and respecify its STORAGE parameters, while truncating does not Note: When you truncate a table, the storage parameter NEXT is changed to be the size of the last extent deleted from the segment in the process of truncation. Restrictions When you truncate a table, NEXT is automatically reset to the last extent deleted. You cannot individually truncate a table that is part of a cluster. You must either truncate the cluster, delete all rows from the table, or drop and re-create the table. You cannot truncate the parent table of an enabled referential integrity constraint. You must disable the constraint before truncating the table. (An exception is that you may truncate the table if the integrity constraint is self-referential.) You cannot roll back a TRUNCATE statement. Mutating Table/Constraining Table "Mutating" means "changing". A mutating table is a table that is currently being modified by an update, delete, or insert statement. When a trigger tries to reference a table that is in state of flux (being changed), it is considered "mutating" and raises an error since Oracle should not return data that has not yet reached its final state. Another way this error can occur is if the trigger has statements to change the primary, foreign or unique key columns of the table off which it fires. If you must have triggers on tables that have referential constraints, the workaround is to enforce the referential integrity through triggers as well. A constraining table is a table that a triggering statement might need to read either directly, for a SQL statement, or indirectly, for a declarative referential integrity constraint. There are several restrictions in Oracle regarding triggers: A row-level trigger cannot query or modify a mutating table. (Of course, NEW and OLD still can be accessed by the trigger). A statement-level trigger cannot query or modify a mutating table if the trigger is fired as the result of a CASCADE delete. Etc. Mutating Table error happens with triggers. It occurs because the trigger is trying to update a row it is currently using. The usual fix involves either use of views or temporary tables so the database is selecting from one while updating the other. For all row triggers, or for statement triggers that were fired as the result of a DELETE CASCADE, there are two important restrictions regarding mutating and constraining tables. These restrictions prevent a trigger from seeing an inconsistent set of data.

24.

10

Interview Question for PL/SQL Oracle Consultant The SQL statements of a trigger cannot read from (query) or modify a mutating table of the triggering statement. The statements of a trigger cannot change the PRIMARY, FOREIGN, or UNIQUE KEY columns of a constraining table of the triggering statement. If you need to update a mutating or constraining table, you could use a temporary table, a PL/SQL table, or a package variable to bypass these restrictions.

25. 26.

Pseudo Columns Key-Mode & Locking Mode Properties Key Mode: Specifies how oracle forms uniquely identifies rows in the database. This is property includes for application that will run against NON-ORACLE datasources. By default, the ORACLE database uses unique ROWID values to identify each row. Non-ORACLE databases do not include the ROWID construct, but instead rely solely on unique primary key values to identify unique rows. If you are creating a form to run against a non-ORACLE data source, you must use primary keys, and set the Key Mode block property accordingly. Automatic (default) Specifies that Form Builder should use ROWID constructs to identify unique rows in the datasource but only if the datasource supports ROWID. Non-Updateable Specifies that Form Builder should not include primary key columns in any UPDATE statements. Use this setting if your database does not allow primary key values to be updated. Unique Instructs Form Builder to use ROWID constructs to identify unique rows in an ORACLE database. Updateable: Specifies that Form Builder should issue UPDATE statements that include primary key values. Use this setting if your database allows primary key columns to be updated and you intend for the application to update primary key values. Locking mode: Specifies when Oracle Forms should attempt to obtain database locks on rows that correspond to queried records in the form. Automatic (default) Identical to Immediate if the datasource is an Oracle database. For other datasources, Form Builder determines the available locking facilities and behaves as much like Immediate as possible. Immediate Form Builder locks the corresponding row as soon as the end user presses a key to enter or edit the value in a text item. Delayed Form Builder locks the row only while it posts the transaction to the database, not while the end user is editing the record. Form Builder prevents the commit action from processing if values of the fields in the block have changed when the user causes a commit action. How many Integrity Rules are there and what are they There are Three Integrity Rules. They are as follows: a) Entity Integrity Rule: The Entity Integrity Rule enforces that the Primary key cannot be Null b) Foreign Key Integrity Rule: The FKIR denotes that the relationship between the foreign key and the primary key has to be enforced. When there is data in Child Tables the Master tables cannot be deleted. c) Business Integrity Rules: The Third Integrity rule is about the complex business processes which cannot be implemented by the above 2 rules. Cascading Triggers When a statement in a trigger body causes another trigger to be fired, the triggers are said to be cascading. Forward Declaration P/L SQL does not allow forward declaration. Identifier must be declared before using it. Therefore, subprogram must be declared before calling it. PL/SQL requires that every identifier must be declared before use. There are occasions where such declaration is not possible. For instance, 2 mutually recursive procedures will need to refer to each other before anyone such procedure can be declared. The solution is by Forward Declaration in which function or procedure's specifications are declared at the declaration. Another way to do forward declaration is to set up a package, which can be separated into specification part and body part. Forward Declaration can be used to do the following: Define Subprograms in logical or alphabetical order. Define mutually recursive subprograms. Group subprograms in a package. Packages provided by Oracle

27.

28.

29.

11

Interview Question for PL/SQL Oracle Consultant

30.

Oracle provides the DBMS_ series of packages. There are many which developers should be aware of such as DBMS_SQL, DBMS_PIPE, DBMS_TRANSACTION, DBMS_LOCK, DBMS_ALERT, DBMS_OUTPUT, DBMS_JOB, DBMS_UTILITY, DBMS_DDL, UTL_FILE. SQL Code & SQLERRM SQLCODE returns the value of the error number for the last error encountered. The SQLERRM returns the actual error message for the last error encountered. They can be used in exception handling to report, or, store in an error log table, the error that occurred in the code. These are especially useful for the WHEN OTHERS exception. How can variables be passed to SQL Runtime Using Ampersand (&) Cartesian Product A Cartesian product is the result of an unrestricted joins of two or more tables. The result set of a three table Cartesian product will have x * y * z number of rows where x, y, z correspond to the number of rows in each table involved in the join. How to prevent output coming to screen The SET option TERMOUT controls output to the screen. Setting TERMOUT OFF turns off screen output. This option can be shortened to TERM. How to prevent from giving information messages during SQL Execution The SET options FEEDBACK and VERIFY can be set to OFF. Row Chaining Row chaining occurs when a VARCHAR2 value is updated and the length of the new value is longer than the old value and wont fit in the remaining block space. This results in the row chaining to another block. It can be reduced by setting the storage parameters on the table to appropriate values. It can be corrected by export and import of the effected table. ERD (Relations) An ERD is an Entity-Relationship-Diagram. It is used to show the entities and relationships for a database logical model. The entity-relationship model is a tool for analyzing the semantic features of an application that are independent of events. Entity-relationship modeling helps reduce data redundancy. Type of Relationship One-One Relationship - For each entity in one class there is at most one associated entity in the other class. For example, for each husband there is at most one current legal wife (in this country at least). A wife has at most one current legal husband. Many-One Relationships - One entity in class E2 is associated with zero or more entities in class E1, but each entity in E1 is associated with at most one entity in E2. For example, a woman may have many children but a child has only one birth mother. Many-Many Relationships - There are no restrictions on how many entities in either class are associated with a single entity in the other. An example of a many-to-many relationship would be students taking classes. Each student takes many classes. Each class has many students. A relational database is a set of relations. It can be thought of as a set of related tables. Each table has a specific form. Attributes can be thought of as column headings. Entity-Relationship Diagram Symbols used in entity-relationship diagrams include: Rectangles represent ENTITY CLASSES Circles represent ATTRIBUTES Diamonds represent RELATIONSHIPS Arcs - Arcs connect entities to relationships. Arcs are also used to connect attributes to entities. Some styles of entity-relationship diagrams use arrows and double arrows to indicate the one and the many in relationships. Some use forks etc. Underline - Key attributes of entities are underlined. Snapshots Oracle provides an automatic method for table replication and update called snapshots. Snapshots are read-only copies of a master table located on a remote node. A snapshot can only be queried, not updated. A snapshot is periodically refreshed to reflect changes made to the master table. Snapshots are local; copies (also known as replicas) of remote data, based upon queries. The refreshes of the replicated data can be done automatically by the database, at time intervals you specify.

31.

32.

33.

34.

35.

36.

37.

12

Interview Question for PL/SQL Oracle Consultant 38. Materialized Views Introduced with Oracle8i, a materialized view is designed to improve performance of the database by doing some intensive work in advance of the results of that work being needed. In the case of a materialized view, the data for the view is assembled when the view is created or refreshed. Later queries that need this data automatically use the materialized view, thus saving the overhead of performing the work already done by the view. The work avoided by a materialized view is essentially twofold: A materialized view can be used to pre-collect aggregate values. A materialized view can be used to assemble data that would come from many different tables, which would in turn require many different joins to be performed. A materialized view is like a view in that it represents data that is contained in other database tables and views; yet it is unlike a view in that it contains actual data. A materialized view is like an index in that the data it contains is derived from the data in database tables and views; yet unlike an index in that its data must be explicitly refreshed. Finally, a materialized view is very much like a snapshot in that an administrator can specify when the data is to be refreshed; but it is unlike a snapshot in that a materialized view should either include summary data or data from many different joined tables. CREATE MATERIALIZED VIEW are required keywords name is the qualified name of the materialized view Physical attributes clause allows you to specify the physical attributes, such the tablespace name, for the materialized view BUILD clause The BUILD clause allows you to specify when you want to build the actual data in the table. Your options are BUILD IMMEDIATE, which calls for the view to be immediately built, BUILD DEFERRED, which calls for the view to be built when it is first refreshed (see explanation of REFRESH clause below) or ON PREBUILT TABLE, which indicates that you are identifying a table that is already built as a materialized view. REFRESH clause Since the materialized view is built on underlying data that is periodically changed, you must specify how and when you want to refresh the data in the view. You can specify that you want a FAST refresh, which will only update the values in the materialized view, assuming that some preconditions are met, COMPLETE, which recreates the view completely, or FORCE, which will do a FAST refresh if possible and a COMPLETE refresh if the preconditions for a FAST refresh are not available. The REFRESH clause also contains either the keywords ON COMMIT, which will cause a refresh to occur whenever the underlying data is changed and the change is committed, or ON DEMAND, which will only perform a refresh when it is scheduled or explicitly called. You can also use keywords in the REFRESH clause to create a schedule for recurring refresh operations. AS subquery The last clause of the CREATE MATERIALIZED VIEW command contains the sub-query that will be used to retrieve the data that will compose the materialized view. Oracle uses materialized views (also known as snapshots in prior releases) to replicate data to non-master sites in a replication environment and to cache expensive queries in a data warehouse environment. You can use materialized views to achieve one or more of the following goals: Ease Network Loads Create a Mass Deployment Environment Enable Data Subsetting Enable Disconnected Computing A materialized view can be either read-only, updatable, or writeable. Users cannot perform data manipulation language (DML) statements on read-only materialized views, but they can perform DML on updatable and writeable materialized views. More Explanation A materialized view is a database object that contains the results of a query. They are local copies of data located remotely, or are used to create summary tables based on aggregations of a table's data. Materialized views, which store data based on remote tables are also, know as snapshots. A materialized view can query tables, views, and other materialized views. Collectively these are called master tables (a replication term) or detail tables (a data warehouse term). For replication purposes, materialized views allow you to maintain copies of remote data on your local node. These copies are read-only. If you want to update the local copies, you have to use the Advanced Replication feature. You can select data from a materialized view as you would from a table or view. For data warehousing purposes, the materialized views commonly created are aggregate views, single-table aggregate views, and join views.

13

Interview Question for PL/SQL Oracle Consultant In replication environments, the materialized views commonly created are primary key, rowid, and subquery materialized views Primary Key Materialized Views The following statement creates the primary-key materialized view on the table emp located on a remote database. SQL> CREATE MATERIALIZED VIEW mv_emp_pk REFRESH FAST START WITH SYSDATE NEXT SYSDATE + 1/48 WITH PRIMARY KEY AS SELECT * FROM emp@remote_db; Materialized view created. Note: When you create a materialized view using the FAST option you will need to create a view log on the master tables(s) as shown below: SQL> CREATE MATERIALIZED VIEW LOG ON emp; Materialized view log created. Rowid Materialized Views The following statement creates the rowid materialized view on table emp located on a remote database: SQL> CREATE M ATERIALIZED VIEW mv_emp_rowid REFRESH WITH ROWID AS SELECT * FROM emp@remote_db; Materialized view log created. Subquery Materialized Views The following statement creates a subquery materialized view based on the emp and dept tables located on the remote database: SQL> CREATE MATERIALIZED VIEW mv_empdept AS SELECT * FROM emp@remote_db e WHERE EXISTS (SELECT * FROM dept@remote_db d WHERE e.dept_no = d.dept_no) Refresh Clause in Materialized Views REFRESH CLAUSE [refresh [fast|complete|force] [on demand | commit] [start with date] [next date] [with {primary key|rowid}]] The refresh option specifies: The refresh method used by Oracle to refresh data in materialized view Whether the view is primary key based or row-id based The time and interval at which the view is to be refreshed Refresh Method - FAST Clause The FAST refreshes use the materialized view logs (as seen above) to send the rows that have changed from master tables to the materialized view. You should create a materialized view log for the master tables if you specify the REFRESH FAST clause. SQL> CREATE MATERIALIZED VIEW LOG ON emp; Materialized view log created. Materialized views are not eligible for fast refresh if the defined subquery contains an analytic function. Refresh Method - COMPLETE Clause The complete refresh re-creates the entire materialized view. If you request a complete refresh, Oracle performs a complete refresh even if a fast refresh is possible. Refresh Method - FORCE Clause When you specify a FORCE clause, Oracle will perform a fast refresh if one is possible or a complete refresh otherwise. If you do not specify a refresh method (FAST, COMPLETE, or FORCE), FORCE is the default. PRIMARY KEY and ROWID Clause WITH PRIMARY KEY is used to create a primary key materialized view i.e. the materialized view is based on the primary key of the master table instead of ROWID (for ROWID clause). PRIMARY KEY is the default option. To use the PRIMARY KEY clause you should have defined PRIMARY

14

Interview Question for PL/SQL Oracle Consultant KEY on the master table or else you should use ROWID based materialized views. Primary key materialized views allow materialized view master tables to be reorganized without affecting the eligibility of the materialized view for fast refresh. Rowid materialized views should have a single master table and cannot contain any of the following: Distinct or aggregate functions GROUP BY Subqueries , Joins & Set operations Timing the refresh The START WITH clause tells the database when to perform the first replication from the master table to the local base table. It should evaluate to a future point in time. The NEXT clause specifies the interval between refreshes SQL> CREATE MATERIALIZED VIEW mv_emp_pk REFRESH FAST START WITH SYSDATE NEXT SYSDATE + 2 WITH PRIMARY KEY AS SELECT * FROM emp@remote_db; Materialized view created. In the above example, the first copy of the materialized view is made at SYSDATE and the interval at which the refresh has to be performed is every two days. Summary Materialized Views thus offer us flexibility of basing a view on Primary key or ROWID, specifying refresh methods and specifying time of automatic refreshes. Scenario for Using Multi-tier Materialized Views Consider a multinational company that maintains all employee information at headquarters, which is in the in the United States. The company uses the tables in the hr schema to maintain the employee information. This company has one main office in 14 countries and many regional offices for cities in these countries. For example, the company has one main office for all of the United Kingdom, but it also has an office in the city of London. The United Kingdom office maintains employee information for all of the employees in the United Kingdom, while the London office only maintains employee information for the employees at the London office. In this scenario, the hr.employees master table is at headquarters in the United States and each regional office has a an hr.employees materialized view that only contains the necessary employee information. The following statement creates the hr.employees materialized view for the United Kingdom office. The statement queries the master table in the database at headquarters, which is orc1.world. Notice that the statement uses subqueries so that the materialized view only contains employees whose country_id is UK. CREATE MATERIALIZED VIEW hr.employees REFRESH FAST FOR UPDATE AS SELECT * FROM [email protected] e WHERE EXISTS (SELECT * FROM [email protected] d WHERE e.department_id = d.department_id AND EXISTS (SELECT * FROM [email protected] l WHERE l.country_id = 'UK' AND d.location_id = l.location_id)); Note: To create this hr.employees materialized view, the following columns must be logged: The department_id column must be logged in the materialized view log for the hr.employees master table at orc1.world. The country_id must be logged in the materialized view log for the hr.locations master table at orc1.world. The following statement creates the hr.employees materialized view for the London office based on the level 1 materialized view at the United Kingdom office. The statement queries the materialized view in the database at the United Kingdom office, which is reg_uk.world. Notice that the statement uses subqueries so that the materialized view only contains employees whose city is London. CREATE MATERIALIZED VIEW hr.employees REFRESH FAST FOR UPDATE AS SELECT * FROM hr.employees@reg_uk.world e WHERE EXISTS (SELECT * FROM hr.departments@reg_uk.world d WHERE e.department_id = d.department_id AND EXISTS (SELECT * FROM hr.locations@reg_uk.world l

15

Interview Question for PL/SQL Oracle Consultant WHERE l.city = 'London' AND d.location_id = l.location_id)); Note: To create this hr.employees materialized view, the following columns must be logged: The department_id column must be logged in the materialized view log for the hr.employees master materialized view at reg_uk.world. The country_id must be logged in the materialized view log for the hr.locations master materialized view at reg_uk.world DDL Statements/Dynamic SQL from P/L Sql (Execute Immediate) EXECUTE IMMEDIATE is the replacement for DBMS_SQL package from Oracle 8i onwards. It parses and immediately executes a dynamic SQL statement or a PL/SQL block created on the fly. Dynamically created and executed SQL statements are performance overhead; EXECUTE IMMEDIATE aims at reducing the overhead and give better performance. It is also easier to code as compared to earlier means. The error messages generated when using this feature are more user friendly. Though DBMS_SQL is still available, it is advisable to use EXECUTE IMMEDIATE calls because of its benefits over the package. Usage tips 1. EXECUTE IMMEDIATE will not commit a DML transaction carried out and an explicit commit should be done. If the DML command is processed via EXECUTE IMMEDIATE, one needs to explicitly commit any changes that may have been done before or as part of the EXECUTE IMMEDIATE itself. If the DDL command is processed via EXECUTE IMMEDIATE, it will commit all previously changed data. 2. Multi-row queries are not supported for returning values, the alternative is to use a temporary table to store the records (see example below) or make use of REF cursors. 3. Do not use a semi-colon when executing SQL statements, and use semi-colon at the end when executing a PL/SQL block. 4. This feature is not covered at large in the Oracle Manuals. Below are examples of all possible ways of using Execute immediate. Hope it is handy. 6. For Forms Developers, this feature will not work in Forms 6i front-end as it is on PL/SQL 8.0.6.3. Example declare l_depnam varchar2(20) := 'testing'; l_loc varchar2(10) := 'Dubai'; begin execute immediate 'insert into dept values (:1, :2, :3)' using 50, l_depnam, l_loc; commit; end; EXECUTE IMMEDIATE is a much easier and more efficient method of processing dynamic statements than could have been possible before. As the intention is to execute dynamic statements, proper handling of exceptions becomes all the more important. Care should be taken to trap all possible exceptions. % Type & % Row Type The %TYPE and %ROWTYPE constructs provide data independence, reduces maintenance costs, and allows programs to adapt as the database changes to meet new business needs. %ROWTYPE is used to declare a record with the same types as found in the specified database table, view or cursor. Example: DECLARE v_EmpRecord emp%ROWTYPE; %TYPE is used to declare a field with the same type as that of a specified table's column. Example: DECLARE v_EmpNo emp.empno%TYPE; Instead of Triggers Views are commonly used to separate the logical database schema from the physical schema. Unfortunately the desired transparency often falls short in the case of UPDATE, DELETE or INSERT operations, since all but the simplest views are not updatable. Instead Of Trigger execute the trigger body instead of the triggering statement. This is used for

39.

40.

41.

16

Interview Question for PL/SQL Oracle Consultant views that are not otherwise modifiable. Instead of Trigger cant be written at Statement Level. Tables/Views (Difference) Views are customized presentations of data in one or more tables or other views. A view can also be considered a stored query. Views do not actually contain data. Rather, they derive their data from the tables on which they are based, referred to as the base tables of the views. Like tables, views can be queried, updated, inserted into, and deleted from, with some restrictions. All operations performed on a view actually affect the base tables of the view. Views provide an additional level of table security by restricting access to a predetermined set of rows and columns of a table. They also hide data complexity and store complex queries. This is the whole list of reasons to use views: 1) to provide an additional level of table security by restricting access to a predetermined set of rows and/or columns of a table 2) to hide data complexity For example, a single view might be defined with a join, which is a collection of related columns or rows in multiple tables. However, the view hides the fact that this information actually originates from several tables. to simplify commands for the user For example, views allow users to select information from multiple tables without actually knowing how to perform a join. 3) to present the data in a different perspective from that of the base table For example, the columns of a view can be renamed without affecting the tables on which the view is based. 4) to isolate applications from changes in definitions of base tables For example, if a view's defining query references three columns of a four column table and a fifth column is added to the table, the view's definition is not affected and all applications using the view are not affected. 5) to express a query that cannot be expressed without using a view For example, a view can be defined that joins a GROUP BY view with a table, or a view can be defined that joins a UNION view with a table. For information about GROUP BY or UNION, see the Oracle8 Server SQL Reference. 6) to save complex queries For example, a query could perform extensive calculations with table information. By saving this query as a view, the calculations can be performed each time the view is queried. 7) to achieve improvements in availability and performance For example, a database administrator can divide a large table into smaller tables (partitions) for many reasons, including partition level load, purge, backup, restore, reorganization, and index building. Once partition views are defined, users can query partitions, rather than very large tables. This ability to prune unneeded partitions from queries increases performance and availability. Dbms_SQL You can write stored procedures and anonymous PL/SQL blocks that use dynamic SQL. Dynamic SQL statements are not embedded in your source program; rather, they are stored in character strings that are input to, or built by, the program at runtime. This permits you to create procedures that are more general purpose. For example, using dynamic SQL allows you to create a procedure that operates on a table whose name is not known until runtime. Additionally, you can parse any data manipulation language (DML) or data definition language (DDL) statement using the DBMS_SQL package. This helps solve the problem of not being able to parse data definition language statements directly using PL/SQL. For example, you might now choose to issue a DROP TABLE statement from within a stored procedure by using the PARSE procedure supplied with the DBMS_SQL package. Table provides a brief description of each of the procedures and functions associated with the DBMS_SQL package, which are described in detail later in this chapter. An example of how these functions can be used begins. DBMS_SQL Package Functions and Procedures Function/Procedure Description

42.

43.

17

Interview Question for PL/SQL Oracle Consultant OPEN_CURSOR Return cursor ID number of new cursor. PARSE Parse given statement. BIND_VARIABLE Bind a given value to a given variable. DEFINE_COLUMN Define a column to be selected from the given cursor, used only with SELECT statements. DEFINE_COLUMN_LONG Define a LONG column to be selected from the given cursor, used only with SELECT statements. EXECUTE Execute a given cursor. EXECUTE_AND_FETCH Execute a given cursor and fetch rows. FETCH_ROWS Fetch a row from a given cursor. COLUMN_VALUE Returns value of the cursor element for a given position in a cursor. COLUMN_VALUE_LONG Returns a selected part of a LONG column, that has been defined using DEFINE_COLUMN_LONG. VARIABLE_VALUE Returns value of named variable for given cursor. IS_OPEN Returns TRUE if given cursor is open. CLOSE_CURSOR Closes given cursor and frees memory. LAST_ERROR_POSITION Returns byte offset in the SQL statement text where the error occurred. LAST_ROW_COUNT Returns cumulative count of the number of rows fetched. LAST_ROW_ID Returns ROWID of last row processed. LAST_SQL_ FUNCTION_CODE Returns SQL function code for statement. Eliminate duplicate rows from table Delete from EMP a Where a.rowid <> (select min (b.rowid) from emp b where a.empno = b.empno); OR Delete from EMP a Where a.rowid <> (select max (b.rowid) from emp b where a.empno = b.empno); Tree-Structured Queries Tree-structured queries are definitely non-relational (enough to kill Codd and make him roll in his grave). Also, this feature is not often found in other database offerings. The SCOTT/TIGER database schema contains a table EMP with a self-referencing relation (EMPNO and MGR columns). This table is perfect for tesing and demonstrating tree-structured queries as the MGR column contains the employee number of the "current" employee's boss. The LEVEL pseudo-column is an indication of how deep in the tree one is. Oracle can handle queries with a depth of up to 255 levels. Look at this example: Select LEVEL, EMPNO, ENAME, MGR From EMP Connect by prior EMPNO = MGR Start with MGR is NULL; One can produce an indented report by using the level number to substring or lpad() a series of spaces, and concatenate that to the string. Look at this example: Select lpad(' ', LEVEL * 2) || ENAME ........ One uses the "start with" clause to specify the start of the tree. More than one record can match the starting condition. One disadvantage of having a "connect by prior" clause is that you cannot perform a join to other tables. The "connect by prior" clause is rarely implemented in the other database offerings. Trying to do this programmatically is difficult, as one has to do the top-level query first, then, for each of the records open a cursor to look for child nodes. One way of working around this is to use PL/SQL, open the driving cursor with the "connect by prior" statement, and the select matching records from other tables on a row-by-row basis, inserting the results into a temporary table for later retrieval. Locking in Oracle Locks are mechanisms that prevent destructive interaction between transactions accessing the same resource - either user objects (such as tables and rows) or system objects not visible to users (such as shared data structures in memory and data dictionary rows). In all cases, Oracle automatically obtains necessary locks when executing SQL statements, so users need not be concerned with such details. Oracle automatically uses the lowest applicable level of restrictiveness to provide the highest degree of data concurrency yet also provide fail-safe data integrity. Oracle also allows the user to lock data manually.

44.

45.

46.

18

Interview Question for PL/SQL Oracle Consultant Oracle uses two modes of locking in a multi-user database: Exclusive lock mode: Prevents the associates resource from being shared. This lock mode is obtained to modify data. The first transaction to lock a resource exclusively is the only transaction that can alter the resource until the exclusive lock is released. Share lock mode: Allows the associated resource to be shared, depending on the operations involved. Multiple users reading data can share the data, holding share locks to prevent concurrent access by a writer (who needs an exclusive lock). Several transactions can acquire share locks on the same resource. Types of Locks Oracle automatically uses different types of locks to control concurrent access to data and to prevent destructive interaction between users. Oracle automatically locks a resource on behalf of a transaction to prevent other transactions from doing something also requiring exclusive access to the same resource. The lock is released automatically when some event occurs so that the transaction no longer requires the resource. DML locks (data locks): DML locks protect data. For example, table locks lock entire tables, row locks lock-selected rows. DDL locks (dictionary locks): DDL locks protect the structure of schema objects - for example, the definitions of tables and views. Internal locks and latches: Internal locks and latches protect internal database structures such as datafiles. Internal locks and latches are entirely automatic. Distributed locks: Distributed locks ensure that the data and other resources distributed among the various instances of an Oracle Parallel Server remain consistent. Distributed locks are held by instances rather than transactions. They communicate the current status of a resource among the instances of an Oracle Parallel Server. Parallel cache management (PCM) locks: Parallel cache management locks are distributed locks that cover one or more data blocks (table or index blocks) in the buffer cache. PCM locks do not lock any rows on behalf of transactions. 47. Joins Join is the process of combining data from two or more tables using matching columns. This relational computing feature consolidates multiple data tables for use in a single report. The SQL JOIN statement is used to combine the data contained in two relational database tables based upon a common attribute. Different Joins Equi-Join A join statement that uses an equivalency operation (i.e: colA = colB). The converse of an equijoin is a nonequijoin operation. In the Equi-Join two (or more) tables are linked via a common domain attribute. This is the most common form of joining used in relational data manipulation. Outer Join The Outer-Join is the opposite of an Equi-Join. It searches for records that exist outside of the specified Join condition. The (+) symbol is the Outer Join operator which causes the join condition to be inverted. Self Join A join in which a table is joined with itself. Sometimes we need to join a table to itself in order to search for the correct data. Nonequijoin A join statement that does not use an equality operation (i.e: colA <> colB). The converse of a nonequijoin is a equijoin. Types of Cursors There are two types of cursors (i) Implicit Implicit cursor will made automatically by oracle system it open fetch and close it automatically (ii) Explicit In explicit cursors you have make it forcefully like: Cursor C1 is select ename from emp; When Where Current of clause is used. This clause refers to the latest row processed by the FETCH statement associated with the cursor identified by cursor_name. The cursor must be FOR UPDATE and must be open and positioned on a row. If the cursor is not open, the CURRENT OF clause causes an error. If the cursor is open, but no rows have been fetched or the last fetch returned no rows, PL/SQL raises the predefined

48.

49.

19

Interview Question for PL/SQL Oracle Consultant exception NO_DATA_FOUND. WHERE CURRENT is used as a reference to the current row when using a cursor to UPDATE or DELETE the current row. Different ways in which block can be built Table Views Procedure Ref cursors Transactional triggers. From clause of a query What is Concurrency Concurrency is allowing simultaneous access of same data by different users. Locks useful for accessing the database are a) Exclusive The exclusive lock is useful for locking the row when an insert, update or delete is being done. This lock should not be applied when we do only select from the row. b) Share lock We can do the table as Share_Lock as many share_locks can be put on the same resource. Deadlock A deadlock is a situation in which two computer programs sharing the same resource are effectively preventing each other from accessing the resource, resulting in both programs ceasing to function. A deadlock can arise when two or more users wait for data locked by each other. The oracle server automatically detects and resolves deadlocks by rolling back the statement that detected the deadlock. Deadlocks most often occur when transactions explicitly override the default locking of the oracle server. A deadlock situation is recorded in a trace file in the USER_DUMP_DEST directory. One has to monitor the trace files for deadlock errors to determine if there are problems with the application. The trace file contains the row IDs of the locking rows. Varray/Nested Table (Difference) Varrays An array is an ordered set of data elements. All elements of a given array are of the same datatype. Each element has an index, which is a number corresponding to the element's position in the array. The number of elements in an array is the size of the array. Oracle allows arrays to be of variable size, which is why they are called VARRAYs. You must specify a maximum size when you declare the array type. Creating an array type does not allocate space. It defines a datatype, which you can use as The data type of a column of a relational table. An object type attribute A PL/SQL variable, parameter, or function return type. A VARRAY is normally stored in line, that is, in the same tablespace as the other data in its row. Nested Tables A nested table is an unordered set of data elements, all of the same datatype. It has a single column, and the type of that column is a built-in type or an object type. If an object type, the table can also be viewed as a multi-column table, with a column for each attribute of the object type. A table type definition does not allocate space. It defines a type, which you can use as The datatype of a column of a relational table. An object type attribute. A PL/SQL variable, parameter, or function return type When a table type appears as the type of a column in a relational table or as an attribute of the underlying object type of an object table, Oracle stores all of the nested table data in a single table, which it associates with the enclosing relational or object table. Differences between Nested Tables and Varrays Nested tables differ from varrays in the following ways: Varrays have a maximum size, but nested tables do not.

50.

51.

52.

53.

54.

20

Interview Question for PL/SQL Oracle Consultant Varrays are always dense, but nested tables can be sparse. So, you can delete individual elements from a nested table but not from a varray. Oracle stores varray data in-line (in the same tablespace). But, Oracle stores nested table data out-of-line in a store table, which is a system-generated database table associated with the nested table. When stored in the database, varrays retain their ordering and subscripts, but nested tables do not. 2 modes of isolation for form module Specifies whether or not transactions in a session will be serializable. If Isolation Mode has the value Serializable, the end user sees a consistent view of the database for the entire length of the transaction, regardless of updates committed by other users from other sessions. If the end user queries and changes a row, and a second user updates and commits the same row from another session, the first user sees Oracle error (ORA-08177: Cannot serialize access.). Read committed (default) Serialize The serialize works in conjunction with the block's locking property set as delayed. The basic idea behind serialize is that the user sees a consistent set of rows throughout the entire runtime session, inspite of any row being changed by another user of different session. This is mainly useful when the application access a very large databases and very few users use the appln so that the chances of users waiting for locked records is less. What is Ref Cursor A Ref Cursor is a pointer to a server side cursor variable. The stored procedure returns a reference to a cursor that is open and populated by a select statement to be used as a block Datasource REF cursors hold cursors in the same way that VARCHAR2 variables hold strings. This is an added feature that comes with PL/SQL v2.2. A REF cursor allows a cursor to be opened on the server and passed to the client as a unit rather than one row at a time. One can use a Ref cursor as a target of assignments and can be passed as parameters to the Program Units. Ref cursors are opened with an OPEN FOR statement and in all other ways, they are the same as regular cursors. Different States/Attributes of Constraints A constraint is deferred if the system checks that it is satisfied only on commit. If a deferred constraint is violated, then commit causes the transaction to roll back. If a constraint is immediate (not deferred), then it is checked at the end of each statement. If it is violated, the statement is rolled back immediately. Constraints can be defined as either deferrable or not deferrable, and either initially deferred or initially immediate. These attributes can be different for each constraint. Constraints can be added, dropped, enabled, disabled, or validated. You can also modify a constraint's attributes. Constraint States ENABLE ensures that all incoming data conforms to the constraint DISABLE allows incoming data, regardless of whether it conforms to the constraint VALIDATE ensures that existing data conforms to the constraint NOVALIDATE means that some existing data may not conform to the constraint ENABLE VALIDATE is the same as ENABLE. The constraint is checked and is guaranteed to hold for all rows. If a constraint is in this state, then all data in the table is guaranteed to adhere to the constraint. In addition, this state prevents any invalid data from being entered. This is the normal state of operation of a constraint for online transaction processing. ENABLE NOVALIDATE means that the constraint is checked, but it does not have to be true for all rows. This allows existing rows to violate the constraint, while ensuring that all new or modified rows are valid. If a constraint is in this state, the new data that violates the constraint cannot be entered. However the table can contain data that is invalid - that is, data that violates the constraint. This is usually an intermediate stage that ensures that all new data is checked before being accepted into the table. DISABLE NOVALIDATE is the same as DISABLE. The constraint is not checked and is not necessarily true. A constraint that is disabled novalidate is not checked, even though the constraint definition is still stored in the data dictionary. Data in the table, as well as the new data that is entered or updated, may not conform to the rules defined by the constraint. This is the normal state of operation of a constraint for online transaction processing. DISABLE VALIDATE disables the constraint, drops the index on the constraint, and disallows any modification of the constrained columns. If the constraint is in this state, them any modification of the constrained columns is not allowed. In addition, the index on the

55.

56.

57.

21

Interview Question for PL/SQL Oracle Consultant constraint is dropped and the constraint is disabled. Different Actions of Constraints Update and Delete No Action The No Action (default) option specifies that referenced key values cannot be updated or deleted if the resulting data would violate a referential integrity constraint. For example, if a primary key value is referenced by a value in the foreign key, then the referenced primary key value cannot be deleted because of the dependent data. Delete Cascade A delete cascades when rows containing referenced key values are deleted, causing all rows in child tables with dependent foreign key values to also be deleted. For example, if a row in a parent table is deleted, and this row's primary key value is referenced by one or more foreign key values in a child table, then the rows in the child table that reference the primary key value are also deleted from the child table. Delete Set Null A delete sets null when rows containing referenced key values are deleted, causing all rows in child tables with dependent foreign key values to set those values to null. For example, if employee_id references manager_id in the TMP table, then deleting a manager causes the rows for all employees working for that manager to have their manager_id value set to null. What is Savepoint Save Point: For long transactions that contain many SQL statements, intermediate markers or save points can be declared. Save points can be used to divide a transaction into smaller parts. You can rollback or commit up to that save point. When to use Procedure/Function/Package/PLL These different forms of procedures will produce different performance results depending on what you are trying to achieve. The database procedure will be invoked on the server side and will perform all of the processing there. This may help reduce network traffic, but may overload the server if many clients are doing this. Local form and library procedures are quite similar in that they are both stored and run on the client with any SQL statements being passed to the server. The local procedures are typically faster on execution because they are actually part of the .fmx file, but may use more memory and have a longer startup time when the .fmx file is initially invoked. Library procedures may be better in terms of overall memory as procedures are only loaded into memory in 4K chunks when they are required. However, once loaded they are read from memory. They have the additional advantage that the library can be attached to a number of forms and the code within the library is then available to the forms. If the code within the library procedures is altered, the form does not require re-generation. That can be a *big* advantage. What is Check option/Force View. FORCE: creates the view regardless of whether the view's base tables exist or the owner of the schema containing the view has privileges on them. Note that both of these conditions must be true before any SELECT, INSERT, UPDATE, or DELETE statements can be issued against the view. WITH CHECK OPTION: specifies that inserts and updates performed through the view must result in rows that the view query can select. The CHECK OPTION cannot make this guarantee if there is a subquery in the query of this view or any view on which this view is based. Different Optimization Techniques Optimizer: Optimization is the process of choosing the most efficient way to execute an SQL statement. When tuning SQL, its very important to understand WHY and WHEN a particular type of optimization should be used. When a SQL Select, Update, Insert or Delete statement is processed, Oracle must access the data referenced by the statement. The Optimizer portion of Oracle is used to determine an efficient path to reference data so that minimal I/O and Processing time is required. For statement execution the Optimizer formulates execution plans and chooses the most efficient plan before executing a statement. The Optimizer uses one of two techniques: Rule Based Approach: Using the rule-based approach, the optimizer chooses an execution plan based on the access paths available and the ranks of these access paths. If there is more than

58.

59.

60.

61.

62.

22

Interview Question for PL/SQL Oracle Consultant one way to execute an SQL statement, the rule-based approach always uses the operation with the lower rank. Usually, operations of lower rank execute faster than those associated with constructs of higher rank. The rule-based optimizer is no longer being enhanced by Oracle. The rule-based optimizer (RBO) Uses a fixed ranking, therefore, its essential to list the correct Table Order in the FROM clause. Normally, the (LAST or Right Most) Table listed in the FROM clause is the driving table. The data distribution and number of records is not taken into account. The RBO execution plan cant be changed by hints. Cost Based Approach: Using the cost-based approach, the optimizer determines which execution plan is most efficient by considering available access paths and factoring in information based on statistics in the data dictionary for the schema objects (tables, clusters or indexes) accessed by the statement. The cost-based approach also considers hints, or optimization suggestions placed in a Comment in the statement. By default, the goal of the cost-based approach is the best throughput, or minimal resource use necessary to process all rows accessed by the statement. The cost-based approach uses statistics to estimate the cost of each execution plan. These statistics quantify the data distribution and storage characteristics of tables, columns, indexes, and partitions. These statistics are generated by using the ANALYZE command. The cost-based optimizer was built to make tuning easier by choosing the best paths for poorly written queries. Normally, the (FIRST or Left Most) Table listed in the FROM clause is the driving table. Just opposite of RBO. The CBO decisions are only as good as the type and frequency of analyzes made on the Table and associated Indexes. To Tune SQL Queries using CBO you must also have an understanding of Table Access Methods, Table Join Methods and Hints. The DRIVING Table In Oracle the cost-based approach uses various factors in determining which table should be the Driving Table (the table that has the most restricted rows). It is the table that drives the query in a multi-table join query. The Driving Table should be listed First in Cost Based and listed Last in Rule Based Optimization. The best thing to remember is that you have control over which table will drive a query through the effective use of the ORDERED hint when using the CBO. The easiest way to determine if your query is using the correct Driving Table is to set the SQL Select to find Zero records. If the return is slow you know the Driving Table is incorrect! Difference b/w Dbms_Alert & Dbms_Pipe. The DBMS_ALERT package provides support for the asynchronous notification of database events (alerts). By appropriate use of this package and database triggers, an application can cause itself to be notified whenever values of interest in the database are changed. Alerts are transaction-based. This means that the waiting session does not get alerted until the transaction signalling the alert commits.There can be any number of concurrent signallers of a given alert, and there can be any number of concurrent waiters on a given alert. The DBMS_PIPE package lets two or more sessions in the same instance communicate. Oracle pipes are similar in concept to the pipes used in UNIX, but Oracle pipes are not implemented using the operating system pipe mechanisms. Information sent through Oracle pipes is buffered in the system global area (SGA). All information in pipes is lost when the instance is shut down. Depending upon your security requirements, you may choose to use either a public or a private pipe. Different types of Data types. Composite Data type Each literal or column value has a data type. The value's data types associate a fixed set of properties with the value. Varchar2 (size), number (p, s), char (size), long, raw, long raw, Boolean, smallint, binary_integer, double, decimal, dec, etc., The data types are scalar (all the above) Composite: tables and record HINTS Hints are suggestions that you give the optimizer for optimizing a SQL statement. Hints allow you to make decisions usually made by the optimizer. You can use hints to specify: Optimization approach for a SQL statement Goal of the cost-based approach for a SQL statement Access path for a table accessed by the statement Join order for a join statement A join operation in a join statement If you incorrectly specify a hint in any way, it will become a comment, and will be ignored. You can also use more than one hint at a time, although this may cause some or all of the hints to be ignored. When you use an alias on a table that you want to use in a hint, you must specify the alias - NOT the table name in the hint. Two MOST Used Hints

63.

64.

23

Interview Question for PL/SQL Oracle Consultant The Ordered Hint The ORDERED hint causes tables to be accessed in a particular order, based on the order of the tables in the FROM clause. The ORDERED hint guarantees the Driving Order of the Table Joins. The ORDERED hint is one of the most powerful hints available. When a multi-table join is slow and you dont know what to do this should be the first hint you should try! The RULE Hint The RULE Hint will force the optimizer to use Rule-Based Optimization. Hints NOT to Use Don't HINT to a specific INDEX-Index names can and do change frequently. DBA's restructure Indexes and change index names. Never use the CACHE Hint- Tables and Indexes have been assigned to specific storage areas. Please don't cache anything - leave that up to the DBA's. Never use the APPEND Hint- unless, the database uses parallel processing. This Hint will cause the table to be appended in Parallel Write Mode. If your Database is not in Parallel Mode - It will Trash the table Privileges/Grants Previleges are the right to execute a particular type of SQL statements. e.g.: Right to Connect, Right to create, Right to resource Grants are given to the objects so that the object might be accessed accordingly. The grant has to be given by the owner of the object.

65.

66.

Clusters Clusters are an optional method of storing table data. Clusters are groups of one or more tables physically stored together because they share common columns and are often used together. Because related rows are physically stored together, disk access time improves. Like indexes, clusters do not affect application design. Whether or not a table is part of a cluster is transparent to users and to applications. Data stored in a clustered table is accessed by SQL in the same way as data stored in a non-clustered table. Benefits: Disk I/O is reduced for joins of clustered tables. Access time improves for joins of clustered tables. In a cluster, a cluster key value is the value of the cluster key columns for a particular row. Each cluster key value is stored only once each in the cluster and the cluster index, no matter how many rows of different tables contain the value. Therefore, less storage is required to store related table and index data in a cluster than is necessary in non-clustered table format. Parallel Query Without the parallel query feature, the processing of a SQL statement is always performed by a single server process. With the parallel query feature, multiple processes can work together simultaneously to process a single SQL statement. This capability is called parallel query processing. By dividing the work necessary to process a statement among multiple server processes, the Oracle Server can process the statement more quickly than if only a single server process processed it. The parallel query feature can dramatically improve performance for data-intensive operations associated with decision support applications or very large database environments. Symmetric multiprocessing (SMP), clustered, or massively parallel systems gain the largest performance benefits from the parallel query feature because query processing can be effectively split up among many CPUs on a single system. It is important to note that the query is parallelized dynamically at execution time. Thus, if the distribution or location of the data changes, Oracle automatically adapts to optimize the parallelization for each execution of a SQL statement. The parallel query feature helps systems scale in performance when adding hardware resources. If your system's CPUs and disk controllers are already heavily loaded, you need to alleviate the system's load before using the parallel query feature to improve performance. Chapter 18, "Parallel Query Tuning" describes how your system can achieve the best performance with the parallel query feature. The Oracle Server can use parallel query processing for any of these statements: SELECT statements Subqueries in UPDATE, INSERT, and DELETE statements CREATE TABLE ... AS SELECT statements CREATE INDEX When a statement is parsed, the optimizer determines the execution plan of a statement. After

67.

24

Interview Question for PL/SQL Oracle Consultant the optimizer determines the execution plan of a statement, the query coordinator process determines the parallelization method of the statement. Parallelization is the process by which the query coordinator determines which operations can be performed in parallel and then enlists query server processes to execute the statement. This section tells you how the query coordinator process decides to parallelize a statement and how the user can specify how many query server processes can be assigned to each operation in an execution plan (that is, the degree of parallelism). 3 Tier Architecture Two tier Architecture: A two-tier architecture is where a client talks directly to a server with no intervening server. It is typically used in small environments. Here you can add more users to the server. This approach will usually result in an ineffective system, as the server becomes overwhelmed to properly scale the users. Eg. Oracle Products SQL*NET is the middleware between the client/server systems. Three tier Architecture: A three tier architecture introduces a server or an agent between the client and server. The role of the agent is manifolds. It can provide translation services (as in adapting a legacy application on a mainframe to a client/server environment), metering services (as in acting as a transaction monitor to limit the number of simultaneous requests to a given server), or intelligent agent services (as in mapping a request to a number of different servers, collating the results and returning a single response to the client. E.g. The Application Programming Interface (API) like ODBC is the middleware between the client and server development in this architecture. The primary advantage of using API in client application is that the resulting application can then use any backend database servers rather than specific server. The disadvantage of using API is the Least common denominators of all tools and database servers that support the standard. Therefore, when you develop a client application, you might not be able to take advantage of all the unique and special features that any one database servers offers. Indexes An Index is database structure that is used by the server to find a row in a table quickly. It is composed of a key value (the column in a row) and the rowid. Indexes are used to improve the performance of queries. It provides a faster access route to table data. Properly used, indexes are the primary means to reduce disk I/O. Index a column only if you frequently want to retrieve less than 15 percent of the rows in a large table. Do not index small tables with few rows. If the column data contains many nulls and you frequently search for these nulls, do not create an index on this column. Likewise if the column contains very similar data, dont create an index on that column. 70. 71. 72. P/L Sql Library Vs Object Library Types of Parameters passing option to procedure & function Partitioning Partitioning addresses the key problem of supporting very large tables and indexes by allowing users to decompose them into smaller and more manageable pieces called partitions. All partitions of a table or index have the same logical attributes, although their physical attributes can be different. For example, all partitions in a table share the same column and constraint definitions; and all partitions in an index share the same index columns. However, storage specifications and other physical attributes such as PCTFREE, PCTUSED, INITRANS, and MAXTRANS can vary for different partitions of the same table or index. Each partition is stored in a separate segment. Optionally, you can store each partition in a separate tablespace, which has the following advantages: You can contain the impact of damaged data. You can back up and recover each partition independently. You can balance I/O load by mapping partitions to disk drives. SDLC Requirements: Functional Specification Document Gap Analysis Document. Design: Architectural Design Document Combined Design Document

68.

69.

73.

25

Interview Question for PL/SQL Oracle Consultant Detailed Design Document Impact Analysis Document Program Specifications Program Submission Code Header QCT Acceptance

Coding/Development:

Testing/QCT: Project Analysis Report QCT Weekly Progress Report Quality Control Test Plan System Test Plan Unit Test Plan Senior Management Review (QCT) Release: Configuration Item Release Customer Release Note Maintenance Annual Technical Support Maintenance Plan Progress Report Project Board Review (Support) Project Schedule (Support Projects) Documentation: User Manuals Various lifecycle models descriptions o Waterfall o Spiral o Prototyping (Evolutionary Prototyping) o Incremental Database Procedure/Form Procedure/Libraries These different forms of procedures will produce different performance results depending on what you are trying to achieve. The database procedure will be invoked on the server side and will perform all of the processing there. This may help reduce network traffic, but may overload the server if many clients are doing this. Local form and library procedures are quite similar in that they are both stored and run on the client with any SQL statements being passed to the server. The local procedures are typically faster on execution because they are actually part of the .fmx file, but may use more memory and have a longer startup time when the .fmx file is initially invoked. Library procedures may be better in terms of overall memory as procedures are only loaded into memory in 4K chunks when they are required. However, once loaded they are read from memory. They have the additional advantage that the library can be attached to a number of forms and the code within the library is then available to the forms. If the code within the library procedures is altered, the form does not require re-generation. That can be a *big* advantage. Overloading Enables you to use same name for different subprograms inside p/l sql block, a subprogram or a package. Requires formal parameters of subprogram to differ in number, order or datatype Enables you to build more flexibility because a user or application is not restricted by specific datatype or number of formal parameters. Only local or packaged subprograms can be overloaded. You cannot overload stand-alone subprograms. Tablespace, Datafiles Table Space: Tablespace is a logical area of data storage. It is made up of one or more datafiles. A table space is an area of disk, comprised of one or more disk files. A tablespace can contain many tables, indexes, or clusters. Because a table space has a fixed size, it can get full as rows are added to its tables. When this happens, the table space can be expanded by someone who has DBA authority. When a database is created two table spaces are created. a) System Table space: This data file stores all the tables related to the system and dba tables b) User Table space: This data file stores all the user related tables We should have separate table spaces for storing the tables and indexes so that the access is fast. A tablespace can be online (accessible) or offline (not accessible). A tablespace is generally online, so that users can access the information in the tablespace. However, sometimes a

74.

75.

76.

26

Interview Question for PL/SQL Oracle Consultant tablespace is taken offline to make a portion of the database unavailable while allowing normal access to the remainder of the database. This makes many administrative tasks easier to perform. Data file: Oracle database has one or more physical datafiles (a datafile is a unit of physical data storage). A database data i.e. tables, indexes, etc. are stored in datafiles. A datafile is associated with only one tablespace. Once created, a datafile cannot change in size, (in release 7.1 datafiles can be appended but existing datafile size cannot be altered, however, later versions support change in existing datafile size). Datafiles can have certain characteristics set to let them automatically extend when the database runs out of space. One or more datafiles form a logical unit of database storage called a tablespace Rollback Segments Use of Control File Control file: A control file records the physical structure of the database. It records database name, names and locations of a databases datafiles and redo log files, time stamps of database creation. Every time an instance of an Oracle database is started, its control file identifies the database and redo log files that must be opened for database operation to proceed. If the physical makeup of the database is altered (for example, if a new datafile or redo log file is created), then the control file is automatically modified by Oracle to reflect the change. A control file is also used in database recovery. Database Link A database link is a named object that describes a "path" from one database to another. Types are Private Database Link, Public Database Link & Network Database Link. Private database link is created on behalf of a specific user. A private database link can be used only when the owner of the link specifies a global object name in a SQL statement or in the definition of the owner's views or procedures. Public database link is created for the special user group PUBLIC. A public database link can be used when any user in the associated database specifies a global object name in a SQL statement or object definition. Network database link is created and managed by a network domain service. A network database link can be used when any user of any database in the network specifies a global object name in a SQL statement or object definition. High Water Mark High-water mark is an indicator or pointer up to which table or index has ever contained data. Bind Variables & Host Variables Bind variables are used in SQL and PL/SQL statements for holding data or result sets. They are commonly used in SQL statements to optimize statement performance. A statement with a bind variable may be re-executed multiple times without needing to be re-parsed. Their values can be set and referenced in PL/SQL blocks. They can be referenced in SQL statements e.g. SELECT. Except in the VARIABLE and PRINT commands, bind variable references should be prefixed with a colon. Host variables are the key to communication between your host program and Oracle. Typically, a precompiler program inputs data from a host variable to Oracle, and Oracle outputs data to a host variable in the program. Oracle stores input data in database columns, and stores output data in program host variables. A host variable can be any arbitrary C expression that resolves to a scalar type. But, a host variable must also be an lvalue. Host arrays of most host variables are also supported. Define & Accept Command Use the DEFINE command to explicitly create substitution variables. The DEFINE command can also be used to display the value of a known variable. It shows the variable name, value and type. Using DEFINE with no arguments lists all defined substitution variables. Any variable that DEFINE lists is said to be defined. A variable may be redefined by repeating the DEFINE command with a different value. The DEFINE command only ever creates variables with type CHAR. The ACCEPT command always prompts for a variable's value, creating a new variable or replacing an existing one. ACCEPT has advantages over a double ampersand (&&) variable reference that causes a prompt. ACCEPT allows the prompting text to be customized and allows a default value to be specified. ACCEPT does type and format checking. The ACCEPT command understands numbers, strings and dates. If a FORMAT clause is used, SQL*Plus validates the input against the given format. If the input is not valid, you are re-prompted for a value.

77. 78.

79.

80. 81.

82.

27

Interview Question for PL/SQL Oracle Consultant 83. Merge Command Merge Command can dynamically decide whether to insert data or update current data during a load, depending on whether a corresponding row already exists in a table. What is Cursor A Cursor is a handle (a name or pointer) for the memory associated with a specific statement. Index by table methods Object Type Object types are abstractions of the real-world entities An object type has a name, which serves to identify the object type uniquely within that schema. It has attributes, which model the structure and state of the real world entity. Attributes are built-in types or other user-defined types. It has methods, which are functions or procedures written in PL/SQL and stored in the database, or written in a language like C and stored externally. Methods implement operations the application can perform on the real world entity. An object type is a template. A structured data unit that matches the template is called an object. An object type has attributes, which reflect the entity's structure, and methods, which implement the operations on the entity. Attributes are defined using built-in types or other object types. Methods are functions or procedures written in PL/SQL or an external language like C and stored in the database. A typical use for an object type is to impose structure on some part of the data kept in the database. For example, an object type named DataStream could be used by a cartridge to store large amounts of data in a character LOB (a data type for large objects). This object type has attributes such as an identifier, a name, a date, and so on. A method is a procedure or function that is part of the object type definition and that can operate on the object type data attributes. Such methods are called member methods, and they take the keyword MEMBER when you specify them as a component of the object type. The DataStream type definition declares three methods. The first two, DataStreamMin and DataStreamMax, calculate the minimum and maximum values, respectively, in the data stream stored inside the character LOB. The system implicitly defines a constructor method for each object type that you define. The name of the constructor method is the same as the name of the object type. The parameters of the constructor method are exactly the data attributes of the object type, and they occur in the same order as the attribute definition for the object type. At present, only one constructor method can be defined, and thus you cannot define other constructor methods. Methods for passing parameters Named Lists value in order in which parameter is declared Positional List value in arbitrarily order by associating each one with parameter name using => Combination List first value positionally and remainder using special syntax of named method Difference in different version of oracle (7.3/8/8i) Some new pl/sql enhancements in oracle 8i and 8 EXECUTE IMMEDIATE Command New Pragmas-serially reusable, autonomous transactions New Database Triggers startup,shutdown,logon,logoff,alter,create,drop Expanded Oracle Supplied Packages dbms_profiles,dbms_trace,dbms_debug Extended Security Methodology Password expire Password reuse max Password grace time Locking user accounts, and unlocking What is synonym. Different types of synonyms. A synonym is a name assigned to a table or a view may thereafter be used to refer it. Creating a synonym does not grant any privileges on referenced objects it just provides at alternative name for objects. Synonyms can be either private or public. A public synonym is owned by the special user group PUBLIC; every user of a database can access it. A private synonym is in the schema of a specific user, who has control over its availability to others. Individual users can see only the public synonyms and their private synonyms. A view is a look on a table's data with restrictions or specific data - a subset of the table's data.

84.

85. 86.

87.

88.

89.

28

Interview Question for PL/SQL Oracle Consultant A synonym is a way to share any object from your scheme with other schemes. A synonym is created to avoid using the user.object standard while calling to other scheme objects. Any privilege you have on the object, will affect the synonym if you grant select only - no insert or update is allowed using synonym (a synonym is a pointer to an object). A view is just a stored query. So any user with the appropriate privileges can query, insert, update, delete the data. The synonym is a pointer to the base table itself. So any user with the appropriate privileges can query, insert, update, delete the data, and also perform DDL on the base table, such as adding/dropping columns. Of course, all that can be controlled by properly managing privileges anyway. Data Dependencies When you create a stored procedure or function, Oracle verifies that the operations it performs are possible based on the schema objects accessed. For example, if a stored procedure contains a SELECT statement that selects columns from a table, Oracle verifies that the table exists and contains the specified columns. If the table is subsequently redefined so that one of its columns does not exist, the stored procedure may not work properly. For this reason, the stored procedure is said to depend on the table. In cases such as this, Oracle automatically manages dependencies among schema objects. After a schema object is redefined, Oracle automatically recompiles all stored procedures and functions in your database that depend on the redefined object the next time they are called. This recompilation allows Oracle to verify that the procedures and functions can still execute properly based on the newly defined object. Runtime recompilation reduces runtime performance and the possible resulting runtime compilation errors can halt your applications. Follow these measures to avoid runtime recompilation: Do not redefine schema objects (such as tables, views, and stored procedures and functions) while your production applications are running. Redefining objects causes Oracle to recompile stored procedures and functions that depend on them. After redefining a schema object, manually recompile dependent procedures, functions, and packages. This measure not only eliminates the performance impact of runtime recompilation, but it also notifies you immediately of compilation errors, allowing you to fix them before production use. You can manually recompile a procedure, stored function, or package with the COMPILE option of the ALTER PROCEDURE, ALTER FUNCTION, or ALTER PACKAGE command. Store procedures and functions in packages whenever possible. If a procedure or function is stored in a package, you can modify its definition without causing Oracle to recompile other procedures and functions that call it. Packages are the most effective way of preventing unnecessary dependency checks from being performed. The %TYPE attribute provides the datatype of a variable, constant, or column. This attribute is particularly useful when declaring a variable or procedure argument that refers to a column in a database table. The %ROWTYPE attribute is useful if you want to declare a variable to be a record that has the same structure as a row in a table or view, or a row that is returned by a fetch from a cursor. Dependencies among PL/SQL library units (packages, stored procedures, and stored functions) can be handled either with timestamps or with signatures. In the timestamp method, the server sets a timestamp when each library unit is created or recompiled, and the compiled states of its dependent library units contain records of its timestamp. If the parent unit or a relevant schema object is altered, all of its dependent units are marked as invalid and must be recompiled before they can be executed. In the signature method, each compiled stored library unit is associated with a signature that identifies its name, the types and modes of its parameters, the number of parameters, and (for a function) the type of the return value. A dependent unit is marked as invalid if it calls a parent unit whose signature has been changed in an incompatible manner. Oracle dynamically recompiles an invalid view or PL/SQL program unit the next time it is used. Alternatively, you can force the compilation of an invalid view or program unit using the appropriate SQL command with the COMPILE parameter. Forced compilations are most often used to test for errors when it is known that a dependent view or program unit is invalid, but is not currently being used; therefore, automatic recompilation would not otherwise occur until the view or program unit is executed. Top Nth Salary Select min (sal) from EMP a Where &N > (select count (distinct sal) from emp b where a.sal < b.sal) Order by sal desc;

90.

91.

29

Interview Question for PL/SQL Oracle Consultant Select deptno, min (sal) from EMP a Where &n > (select count (distinct sal) from EMP b Where a.sal < b.sal and a.deptno = b.deptno) Group by deptno Order by deptno; Select empno,sal from (select empno,sal from emp order by sal desc) where rownum<4 Select empno,sal from EMP a Where 3 > (select count (distinct sal) from emp b where a.sal < b.sal) Order by sal desc Query to return Nth highest salary for each department ----------------------------------------------------Select deptno, sal from emp a Where &N > (select count (sal) from emp b where a.sal < b.sal and a.deptno = b.deptno) Minus Select deptno, sal From emp a Where &(N-1) > (select count (sal) from emp b where a.sal < b.sal and a.deptno = b.deptno) Order by deptno, sal desc; Logical and Physical Page A physical page (or panel) is the size of a page that will be output by your printer. A logical page is the size of one page of your actual report (it can be any number of physical pages wide or long). The Runtime Previewer displays the logical pages of your report output, one at a time. Bulk Binds The assigning of values to PL/SQL variables in SQL statements is called binding. The binding of an entire collection at once is called bulk binding. Bulk binds improve performance by minimizing the number of context switches between the PL/SQL and SQL engines. With bulk binds, entire collections, not just individual elements, are passed back and forth. The keyword FORALL instructs the PL/SQL engine to bulk-bind input collections before sending them to the SQL engine. Although the FORALL statement contains an iteration scheme, it is not a FOR loop. In a FORALL statement, if any execution of the SQL statement raises an unhandled exception, all database changes made during previous executions are rolled back. However, if a raised exception is caught and handled, changes are rolled back to an implicit savepoint marked before each execution of the SQL statement. Changes made during previous executions are not rolled back. The following restrictions apply to the FORALL statement: You can use the FORALL statement only in server-side programs (not in client-side programs). Otherwise, you get the error this feature is not supported in client-side programs. The INSERT, UPDATE, or DELETE statement must reference at least one collection The keywords BULK COLLECT tell the SQL engine to bulk-bind output collections before returning them to the PL/SQL engine. You can use these keywords in the SELECT INTO, FETCH INTO, and RETURNING INTO clauses. The FORALL statement is specifically used for processing DML (INSERT, DELETE, and UPDATE) statements to improve performance by reducing the overhead of SQL processing. The PL/SQL interpreter executes all procedural statements. However, all SQL statements in the PL/SQL block are sent to the SQL engine, which parses and executes them. The PL/SQL-to-SQL context switch adds some overhead, which could become significant when SQL statements are nested in loops. For instance, if it's repeated in a loopsay, 1,000,000 timesthat could slow down code execution substantially. The FORALL statement has a structure similar to FOR LOOP with a range. However, it doesn't contain an END LOOP statement and it cannot contain any statements other than the index, lower and upper bound, and actual SQL statement (which refers to the index). The range specified by lower and upper bounds (in my example, it's 1 to 10,000) must be contiguous and all the elements within that range must exist, otherwise an ORA-22160 exception will be raised. The FORALL clause is used for DML statements. The equivalent statement for a bulk fetch is the BULK COLLECT clause, which can be used as a part of SELECT INTO, FETCH INTO, or RETURNING INTO clauses The BULK COLLECT clause can be used for both explicit (FETCH INTO) and implicit (SELECT INTO) cursors. It fetches the data into the collection (PL/SQL table, varray) starting with element 1 and overwrites all consequent elements until it retrieves all the rows. If the collection is varray, it has to be declared large enough to accommodate all fetched rows, otherwise an ORA-22160 exception will be raised. The bulk binds features allow users to increase the performance and reduce the overhead of

92.

93.

30

Interview Question for PL/SQL Oracle Consultant SQL processing by operating on multiple rows in a single DML statement. The entire collectionnot just one collection element at a time-is passed back and forth between the PL/SQL and SQL engines. According to Oracle, during internal benchmark tests there was a 30 percent performance improvement as a result of using these new features. Index-Organized Table, Difference b/w Ordinary Table & Index-Organized Table An index-organized table has a storage organization that is a variant of a primary B-tree. Unlike an ordinary (heap-organized) table whose data is stored as an unordered collection (heap), data for an index-organized table is stored in a B-tree index structure in a primary key sorted manner. Besides storing the primary key column values of an index-organized table row, each index entry in the B-tree stores the nonkey column values as well. Ordinary Table Index-Organized Table Rowid uniquely identifies a row. Primary key can be optionally specified uniquely identifies a row. Primary key must be specified Physical rowid in ROWID pseudocolumn allows building secondary indexes ROWID pseudocolumn allows building secondary indexes Access is based on rowid Access is based on logical rowid Sequential scan returns all rows Full-index scan returns all rows Can be stored in a cluster with other tables Cannot be stored in a cluster Can contain a column of the LONG datatype and columns of LOB datatypes columns but not LONG columns Primary key Logical rowid in

94.

Can contain LOB

95.

Index-organized tables provide faster access to table rows by the primary key or any key that is a valid prefix of the primary key. Presence of nonkey columns of a row in the B-tree leaf block itself avoids an additional block access. Also, because rows are stored in primary key order, range access by the primary key (or a valid prefix) involves minimum block accesses. Because rows are stored in primary key order, a significant amount of additional storage space savings can be obtained through the use of key compression. Use of primary-key based logical rowids, as opposed to physical rowids, in secondary indexes on index-organized tables allows high availability. This is because, due to the logical nature of the rowids, secondary indexes do not become unusable even after a table reorganization operation that causes movement of the base table rows. At the same time, through the use of physical guess in the logical rowid, it is possible to get secondary index based index-organized table access performance that is comparable to performance for secondary index based access to an ordinary table. Package/Stored Procedure (Difference) A Package is a database object that groups logically related PL/SQL types, objects and subprograms. Packages usually have 2 parts - specification & body. The specification is the interface to your applications; it declares the types, variables, constants, exceptions, cursors and subprograms available for use. The Body fully defines cursors and subprograms, and so implements the Specification. Unlike subprograms, packages cannot be called, passed parameters, or nested. A Package might include a collection of procedures. Once written, your general-purpose package is compiled, and then stored in an ORACLE database, where, like a library unit, its contents can be shared by many applications. Advantages of Packages: Modularity Easier Application design: Initially once the Specification has been compiled, the Body need not be fully defined until one is ready to complete the application. Information hiding: Certain procedures can be made as Public (visible and accessible) and others as Private (hidden and inaccessible). Added Functionality: Packaged public variables and cursors persist for the duration of a session. So, they can be shared by all procedures that execute in the environment. Also, they allow you to maintain data across transactions without having to store it in the database. Better Performance: When you call a package for the first time, the whole package is loaded into memory. Therefore, subsequent calls to related procedures in the package require no disk I/O. Procedure: A Procedure is a subprogram that performs a specific action. It has 2 parts: Specification & Body. Global Temporary Table In Oracle 8i, the CREATE GLOBAL TEMPORARY TABLE command creates a temporary table, which can be transaction specific or session specific. For transaction-specific temporary tables, data exists for the duration of the transaction while for session-specific temporary tables, data exists for the duration of the session. Data in a temporary table is private to the session. Each session can only see and modify its own data. The table definition itself is not temporary.

96.

31

Interview Question for PL/SQL Oracle Consultant You can create indexes for temporary tables using the CREATE INDEX command. Indexes created on temporary tables are also temporary and the data in the index has the same session or transaction scope as the data in the temporary table. You can perform DDL commands (ALTER TABLE, DROP TABLE, CREATE INDEX, and so on) on a temporary table only when no session is currently bound to it. A session gets bound to a temporary table when an INSERT is performed on it. The session gets unbound by a TRUNCATE, at session termination, or by doing a COMMIT or ABORT for a transaction-specific temporary table. Temporary tables use temporary segments. Temporary segments are de-allocated at the end of the transaction for transaction-specific temporary tables. For session-specific temporary tables, they are de-allocated at the end of the session. Multi-session scenarios: 1-Two different users try to create a global temporary table with the same name Both tables get created. Each user sees his/her own table. 2-Two sessions by a single user try to create a global temporary table with the same name. Once the table has been created in one of the sessions, the table exists and an error is given to the second session when trying to create the table. This behavior occurs whether or not the table structure is defined to be the same in both sessions. 3-Two sessions by a single user insert rows into a global temporary table. Each session can insert rows into the table, no matter which session created the table. 4-Two sessions by the same user select from a global temporary table. A given session will only see the rows that it has inserted, as if the table was private to that session. 5-A session tries to alter a temporary table that another session is also using. Columns cannot be added/deleted/modified as long as the table is bound to a session. Renaming, however, can be done even when another session has rows in the table. 6-A session attempts to rename a global temporary table in which another session has inserted some rows The table gets renamed and rows are preserved. After the rename has taken place, both sessions must use the new name to refer to that table. Surrogate Keys A unique primary key generated by the RDBMS that is not derived from any data in the database and whose only significance is to act as the primary key. A surrogate key is frequently a sequential number (e.g. a Sybase "identity column") but doesn't have to be. Having the key independent of all other columns insulates the database relationships from changes in data values or database design and guarantees uniqueness. Some database designers use surrogate keys religiously regardless of the suitability of other candidate keys. However, if a good key already exists, the addition of a surrogate key will merely slow down access, particularly if it is indexed. DUAL table A tiny table with only one row and one column Implicit commit Using any of the following actions will force a commit to occur: quit, exit, create table, create view, drop table, drop view, grant, revoke, connect, disconnect, alert, audit and no audit. What is Rollback If a series of instructions are completed, but have not yet explicitly or implicitly committed them, and if a serious difficulty such as computer failure is experienced, Oracle automatically rollbacks any uncommitted work. Database Cache Database Cache is a caching service that resides on the middle-tier and provides caching services for data from the origin database. It provides caching of the data from the origin database so that the application of the middle-tier can fetch data. It can be created on either the application server or the web server. Explain Plain The EXPLAIN PLAN command displays the execution plan chosen by the Oracle optimizer for SELECT, UPDATE, INSERT, and DELETE statements at the current time, with the current set of initialization and session parameters. A statements execution plan is the sequence of operations that Oracle performs to execute the SQL statement. By examining the execution plan, you can see exactly how Oracle executes the SQL statement. Use EXPLAIN PLAN to determine the Table Access Order, Table Join Types, Index Access to test modifications to improve SQL performance. Its best if you dont blindly evaluate the plan for a statement, and decide to tune it based only on the execution plan. EXPLAIN PLAN results alone cannot tell you which statements will perform well, and which wont. For example, just because EXPLAIN PLAN

97.

98.

99.

100.

101.

32

Interview Question for PL/SQL Oracle Consultant indicates that a statement will use an Index doesn't mean that the statement will run quickly. The index might be very inefficient. Instead, you should examine the statement's actual RESOURCE CONSUMPTION and the statements ACTUAL RUN TIME. REMEMBER - A low COST doesn't GUARANTEE a FASTER RUN TIME The AUTOTRACE Command in SQLPlus can be used to generate EXPLAIN PLANS and Run Time Statistics. The EXPLAIN PLAN is generated after the SQL Statement is executed. Explain Plan (Optimization): To analyze for tuning the SQL statement Explain Plan is used. For that run the UTLXPLAN.SQL script to create table named PLAN_TABLE, for receiving the output of an Explain Plan statement. Eg. Explain Plan Set Statement_id My Customer Into Plan_table For Select lastname, firstname From customers Where state = NY

Output: Select statement_id,operation,options,cost from plan_table; Statement_id My Customer My Customer Operation Select Statement Table Access Options Full Access Cost 9 16

102.

The Explain Plan command of oracle7 uses the current statistics in the data dictionary to do its best to return an accurate execution plan and corresponding cost to executing a statement. However, if statistics are not up-to-date then of course the Explain Plan command might not return an accurate execution plan and cost. Parsing Parsing: Parsing a statement means breaking down the statement, so that it can be executed. When oracle server parses a SQL statement, it first checks for semantic and syntactical errors in statements. Oracle uses shared the SQL area for parsing (Parse tree). Programming standards: Using the standard template form. Naming conventions for blocks, buttons, record groups, etc. Proper Indentation. Naming and declaration of identifiers (local variables, global variables, cursors, etc.) Always use %Type and %RecType Exception handling and error messages Proper commenting Using performance standard code in Validation and data fetching 9I Features Features: 1. One can create or rebuild online index 2. Buffer cache & shared pool is resized dynamically 3. Data recovery is very fast due to 2 pass recovery algorithm 4. Flashback Query feature of oracle 9I 5. 2 million of users performing millions of transaction/H is possible (Scalability) 6. Multilingual server side debugging has been added 7. Rollback segments are managed own by Oracle 8. Oracle 9i introduces resumable statements, which allow to temporarily suspending batch process or data load. 9. Databases created with Multiple Block size 10. Execution history is maintained 11. Better integration with Windows 2000 12. Feature of intermedia text indexing for fast searches has been introduced 13. Long data types can be converted to LOB using alteration 14. Self tuning memory among processes hence query performance There are two tables namely EMP, SALGRADE Fields of SALGRADE are GRADE, LOSAL HISAL Fields of EMP table are as usual

103.

33

Interview Question for PL/SQL Oracle Consultant I want the output like this. GRADE LOSAL HISAL COUNT (*) --------- --------- --------- --------1 700 1200 4 2 1201 1400 5 3 1401 2000 4 4 2001 3000 8 5 3001 9999 2 Select grade, losal, hisal, count (*) from EMP, salgrade Where sal between losal and hisal Group by grade, losal, hisal Select even row from emp table Select * from EMP where rowid in (select decode (mod (rownum, 2), 0,rowid, null) from emp); Select odd row from emp table Select * from EMP where rowid in (select decode (mod (rownum, 2), 1,rowid, null) from emp); Select Nth row from emp table where N=10 Select * from EMP where rowid=(select rowid from EMP where ROWNUM <= 10 MINUS Select rowid from EMP where ROWNUM < 10) Select rows X to Y from emp table where X=5 and Y=7 Select * from EMP where rowid in (select rowid from EMP Where rowNUM <= 7 MINUS Select rowid from EMP where rownum < 5); All even, Odd, Nth rows from a table Select * from emp where (rowid, 0) in (select rowid, mod (rownum,&n) from emp); Select N rows from a table Select * from EMP a Where &n>(select count (distinct (sal)) from emp b where a. Sal >= b.sal) Order by sal desc; Please check this query for the correctness for n=1,2,3,4,5 Select Employee having maximum salary in department from emp table Select deptno, empno, sal from EMP a where (deptno, sal) in ( Select deptno, max (sal) from EMP b Where a.deptno = b.deptno Group by b.deptno) order by 1 External Tables External tables allow Oracle to query data that is stored outside the database in flat files. The ORACLE_LOADER driver can be used to access any data stored in any format that can be loaded by SQL*Loader. No DML can be performed on external tables but they can be used for query, join and sort operations. Views and synonyms can be created against external tables. They are useful in the ETL process of data warehouses since the data doesn't need to be staged and can be queried in parallel. They should not be used for frequently queried tables. Limitations on external tables Because external tables are new, Oracle has not yet perfected their use. In Oracle9i the feature has several limitations, including: No support for DML. External tables are read-only, but the base data can be edited in any text editor. Poor response for high-volume queries. External tables have a processing overhead and are not suitable for large tables. Example: The example below describes how to create external files, create external tables, query external tables and create views. Step I: Creating the flat files, which will be queried The file "emp_ext1.dat" contains the following sample data: 101,Andy,FINANCE,15-DEC-1995 102,Jack,HRD,01-MAY-1996 103,Rob,DEVELOPMENT,01-JUN-1996 104,Joe,DEVELOPMENT,01-JUN-1996

104.

105. 106.

107.

108. 109.

110.

111.

34

Interview Question for PL/SQL Oracle Consultant The file "emp_ext2.dat" contains the following sample data: 105,Maggie,FINANCE,15-DEC-1997 106,Russell,HRD,01-MAY-1998 107,Katie,DEVELOPMENT,01-JUN-1998 108,Jay,DEVELOPMENT,01-JUN-1998 Copy these files under "C:\EXT_TABLES" Step II: Create a Directory Object where the flat files will reside SQL> CREATE OR REPLACE DIRECTORY EXT_TABLES AS 'C:\EXT_TABLES'; Directory created. Step III: Create metadata for the external table SQL> CREATE TABLE emp_ext ( empcode NUMBER(4), empname VARCHAR2(25), deptname VARCHAR2(25), hiredate date ) ORGANIZATION EXTERNAL ( TYPE ORACLE_LOADER DEFAULT DIRECTORY ext_tables ACCESS PARAMETERS ( RECORDS DELIMITED BY NEWLINE FIELDS TERMINATED BY ',' MISSING FIELD VALUES ARE NULL ) LOCATION ('emp_ext1.dat','emp_ext2.dat') ) REJECT LIMIT UNLIMITED; Table created. The REJECT LIMIT clause specifies that there is no limit on the number of errors that can occur during a query of the external data. Step V: Creating Views SQL> CREATE VIEW v_empext_dev AS SELECT * FROM emp_ext WHERE deptname = 'DEVELOPMENT'; View created. Dropping External Tables For an external table, the DROP TABLE statement removes only the table metadata in the database. It has no affect on the actual data, which resides outside of the database. Multitable Insert in Oracle 9i Multitable inserts allow a single INSERT INTO.. SELECT statement to conditionally, or nonconditionally, insert into multiple tables. This statement reduces table scans and PL/SQL code necessary for performing multiple conditional inserts compared to previous versions. Its main use is for the ETL process in data warehouses where it can be parallelized and/or convert nonrelational data into a relational format: -- Unconditional insert into ALL tables INSERT ALL INTO sal_history VALUES (empid, hiredate, sal) INTO mgr_history VALUES (empid, mgr, sysdate) SELECT employee_id EMPID, hire_date HIREDATE, salary SAL, manager_id MGR FROM employees WHERE employee_id > 200; -- Pivoting insert to split non-relational data INSERT ALL NTO Sales_info VALUES (employee_id, week_id, sales_MON) INTO Sales_info VALUES (employee_id, week_id, sales_TUE) INTO Sales_info VALUES (employee_id, week_id, sales_WED) INTO Sales_info VALUES (employee_id, week_id, sales_THUR)

112.

35

Interview Question for PL/SQL Oracle Consultant NTO Sales_info VALUES (employee_id, week_id, sales_FRI) SELECT EMPLOYEE_ID, week_id, sales_MON, sales_TUE, Sales_WED, sales_THUR, sales_FRI FROM Sales_source_data; -- Conditionally insert into ALL tables INSERT ALL WHEN SAL>10000 THEN INTO sal_history VALUES (EMPID, HIREDATE, SAL) WHEN MGR>200 THEN INTO mgr_history VALUES (EMPID, MGR, SYSDATE) SELECT employee_id EMPID, hire_date HIREDATE, salary SAL, manager_id MGR FROM employees WHERE employee_id > 200; -- Insert into the FIRST table with a matching condition INSERT FIRST WHEN SAL > 25000 THEN INTO special_sal VALUES (DEPTID, SAL) WHEN HIREDATE like ('%00%') THEN INTO hiredate_history_00 VALUES (DEPTID, HIREDATE) WHEN HIREDATE like ('%99%') THEN INTO hiredate_history_99 VALUES (DEPTID, HIREDATE) ELSE INTO hiredate_history VALUES (DEPTID, HIREDATE) SELECT department_id DEPTID, SUM (salary) SAL, MAX (hire_date) HIREDATE FROM employees GROUP BY department_id; The restrictions on multitable Inserts are: Multitable inserts can only be performed on tables, not on views or materialized views. You cannot perform a multitable insert via a DB link. You cannot perform multitable inserts into nested tables. The sum of all the INTO columns cannot exceed 999. Sequences cannot be used in the subquery of the multitable insert statement. New Join Syntax This new join syntax uses the new keywords inner join, left outer join, right outer join, and full outer join, instead of the (+) operator. INNER Join: SQL> select p.part_id, s.supplier_name From part p inner join supplier s On p.supplier_id = s.supplier_id; PART SUPPLIER_NAME ---- -------------------P1 Supplier#1 P2 Supplier#2 Remember, if we want to retain all the parts in the result set, irrespective of whether any supplier supplies them or not, then we need to perform an outer join. The corresponding outer join query using the new syntax will be: OUTER JOIN SQL> select p.part_id, s.supplier_name from part p left outer join supplier s on p.supplier_id = s.supplier_id; PART SUPPLIER_NAME ---- -------------------P1 Supplier#1 P2 Supplier#2 P4 P3 This is called a "left outer join" because all the rows from the table on the left (PART) are retained in the result set. If we want to retain all the suppliers in the result set, irrespective of whether they supply any part or not, then we need to perform a "right outer join". That would look like: SQL> select p.part_id, s.supplier_name from part p right outer join supplier s on p.supplier_id =

113.

36

Interview Question for PL/SQL Oracle Consultant s.supplier_id; PART SUPPLIER_NAME ---- -------------------P1 Supplier#1 P2 Supplier#2 Supplier#3 However, the biggest advantage of the new join syntax is its support for full outer joins. Introduction of the ANSI standard join syntax in Oracle9i greatly simplifies the full outer join query. We are no longer limited by unidirectional outer join, and no longer need to use the UNION operation to perform the full outer join. FULL OUTER JOIN Oracle9i introduced the full outer join operation to carry out such operations, as in the following example: SQL> select p.part_id, s.supplier_name From part p full outer join supplier s On p.supplier_id = s.supplier_id; PART SUPPLIER_NAME ---- -------------------P1 Supplier#1 P2 Supplier#2 P4 P3 Supplier#3 The above SQL statement is not only smaller in size, it is much more elegant and intuitive as well. This ANSI join syntax is also more efficient than the UNION method of achieving a full outer join. NATURAL Joins. A natural join, as its name implies, can be invoked when two or more tables share exactly the same columns needed for a successful equijoin. For example, these queries will return all Region and Country information for all countries whose name that contains the string "united": Example: NATURAL Join Traditional Syntax ANSI SYNTAX SELECT r.region_id, r.region_name, c.country_id, c.country_name FROM Countries c, regions r WHERE c.region_id = r.region_id AND LOWER (c.country_name) LIKE '%united%'; SELECT region_id, r.region_name, c.country_id, c.country_name FROM countries c NATURAL JOIN regions r WHERE LOWER (c.country_name) LIKE '%united%'; 114. Multiple block sizes in the same database The BLOCKSIZE keyword has been added to the CREATE TABLESPACE command. Valid values are: 2K, 4K, 8K, 16K, 32K (operating system dependent). CREATE TABLESPACE MY_TBS ... BLOCKSIZE 16K; CREATE TABLESPACE MY_TBS ... BLOCKSIZE 8192; The field BLOCK_SIZE has been added to the DBA_TABLESPACES view. The DB_BLOCK_SIZE parameter is still needed in the init.ora during database creation. This value is the default blocksize for new tablespaces as well as the required size for the system tablespace, undo tablespace and all temporary tablespaces. As with previous releases, DB_BLOCK_SIZE cannot be changed without recreating the database. All partitions of a partitioned object must be in tablespaces with the same block size. Indexes can be in a tablespace with a different block size than its corresponding table.

37

Interview Question for PL/SQL Oracle Consultant 115. 9I SQL FEATURES NULL2 Function NVL2 lets you determine the value returned by a query based on whether a specified expression is null or not null. If expr1 is not null, then NVL2 returns expr2. If expr1 is null, then NVL2 returns expr3. The argument expr1 can have any datatype. The arguments expr2 and expr3 can have any datatypes except LONG. If the datatypes of expr2 and expr3 are different, then Oracle converts expr3 to the datatype of expr2 before comparing them unless expr3 is a null constant. In that case, a datatype conversion is not necessary. The datatype of the return value is always the same as the datatype of expr2, unless expr2 is character data, in which case the return value's datatype is VARCHAR2. NULLIF (expr1, expr2) Returns NULL if the first argument is equal to the second, otherwise returns the first argument. COALESCE (expr1, expr2, expr3, ...) Returns the first non-null argument. SELECT... FOR UPDATE Enhancements Selecting a record for update that is already locked causes the current session to hang indefinitely until the lock is released. If this situation is unacceptable the NOWAIT keyword can be used to instantly return an error if the record is locked. Oracle9i adds more flexibility by allowing the programmer to specify a maximum time limit to wait for a lock before returning an error. This gets round the problem of indefinite waits, but reduces the chances of lock errors being returned: SELECT * FROM employees WHERE empno = 20 FOR UPDATE WAIT 30;

Merge Statement The MERGE statement can be used to conditionally insert or update data depending on its presence. This method reduces table scans and can perform the operation in parallel. Consider the following example where data from the HR_RECORDS table is merged into the EMPLOYEES table: MERGE INTO employees e USING hr_records h ON (e.id = h.emp_id) WHEN MATCHED THEN UPDATE SET e.address = h.address WHEN NOT MATCHED THEN INSERT (id, address) VALUES (h.emp_id, h.address); Explicitly Named Indexes On Keys In Oracle9i the index used to support primary and unique keys can be defined independently of the constraint itself by using the CREATE INDEX syntax within the USING UNDEX clause of the CREATE TABLE statement: CREATE TABLE employees ( Empno NUMBER (6), Name VARCHAR2 (30), Deptno NUMBER (2), CONSTRAINT emp_pk primary key (empno) USING INDEX (CREATE INDEX emp_pk_idx ON employee (empno)) ); The constraint can subsequently be dropped without dropping the index using either syntax: ALTER TABLE employees DROP PRIMARY KEY KEEP INDEX; ALTER TABLE employees DROP CONSTRAINT empno_pk;

38

Interview Question for PL/SQL Oracle Consultant

Share Locks On Unindexed FKs In previous versions a share lock was issued on the entire child table while the parent table was being updated if the foreign key between them was unindexed. This had the affect of preventing DML operations on the child table until the parent table transaction was complete. In Oracle9i this situation has been altered such that a table level share lock is issued and instantly released. This action allows Oracle to check that there are no pending changes on the child table, but the instant release means that DML can resume almost instantly once the parent table update has initiated. If multiple keys are updated Oracle issues a share lock and release on the child table for each row. PK Lookup During FK Insertion During insertions foreign key values are checked against the primary keys of referenced tables. This process is optimized in Oracle9i by caching the first 256 PK values of the referenced table on insertion of the second record of a multiple insert. The process is done on the second record to prevent the overhead of managing the cache on a single insert. Function Based Index Enhancements Function Based Indexes are now capable of doing an index-only scan. In previous versions this was only possible if the index creation statement explicitly prevented NULL values. Since each built-in operator knows implicitly whether it can produce null values when all it's input parameters are not null, Oracle can deduce if nulls can be produced and therefore decide if index-only scans are possible based on the columns queried using the function based index. View Constraints Declarative primary key, unique key and foreign key constraints can now be defined against views. The NOT NULL constraint is inherited from the base table so it cannot be declared explicitly. The constraints are not validated so they must be defined with the DISABLE NOVALIDATE clause: CREATE VIEW Emp_view (Id PRIMARY KEY DISABLE NOVALIDATE, firstname) AS SELECT employee_id, first_name FROM employees WHERE department_id = 10; ALTER VIEW Emp_view ADD CONSTRAINT emp_view_unq UNIQUE (first_name) DISABLE NOVALIDATE; How to retrieve DDL from Database DBMS_METADATA package will work for tables, indexes, views, packages, functions, procedures, triggers, synonyms, and types. DBMS_METADATA.GET_DDL (object_type, name, schema) DBMS_METADATA.GET_XML (object_type, name, schema) SELECT DBMS_METADATA.GET_DDL (TABLE, EMP, SCOTT) from dual; How could you create six unique random numbers between 1 and 49 with one SQL statement? select r from (select r from (select rownum r from all_objects where rownum < 50) order by dbms_random.value) where rownum <= 6; R ---------10

116.

117

39

Interview Question for PL/SQL Oracle Consultant

2 19 34 12 21 That query works by generating the numbers 1 .. 49, using the inline view. We wrap that innermost query as an inline view and sort it by a random value, using DBMS_RANDOM.VALUE. We wrap that result set in yet another inline view and just take the first six rows. If we run that query over and over, we'll get a different set of six rows each time.

118.

Oracle Pipelined Table Functions

40