Explore topic-wise InterviewSolutions in .

Heterogeneity of the system results in reduced reliablity, it MAY not be SUITABLE for all applications. MANAGING and tuning networks BECOMES difficult.

Heterogeneity of the system results in reduced reliablity, it May not be suitable for all applications. Managing and tuning networks becomes difficult.

• STAR,
• BUS,
• RING.

A CLIENT PROCESS at FIRST ESTABLISHES connection with the SERVER.

A client process at first establishes connection with the Server.

1.  Manage RESOURCES optimally across multiple clients.
2. Controlling database access and security.
3. Protecting the databse and recovering it from CRASHES.
4.  Enforcing INTEGRITY rules GLOBALLY.

The application can be CONNECTED to any BACK END SERVER that is supported by the API.

The application can be connected to any back end server that is supported by the API.

The APPLICATION cannot use any SPECIAL features of the backend SERVER.

The application cannot use any special features of the backend server.

Because an event DRIVEN PROGRAM is ALWAYS waiting for SOMETHING to happen before processing.

Because an event driven program is always waiting for something to happen before processing.

1. SYSTEM EVENTS,
2. CONTROL Events,
3. USER Events,
4. Other Events.

A file server just TRANSFERS all the data requested by all its client and the client PROCESSES the data while a database server RUNS the QUERY and SENDS only the query output.

A file server just transfers all the data requested by all its client and the client processes the data while a database server runs the query and sends only the query output.

Inheritance is a method by which properties and METHODS of an existing object are automatically PASSED to any object DERIVED from it.

Inheritance is a method by which properties and methods of an existing object are automatically passed to any object derived from it.

1. An ODBC manager/administrator and
2. ODBC DRIVER.

1. An ODBC manager/administrator and
2. ODBC driver.

The ODBC Manager MANAGES all the DATA sources that EXISTS in the SYSTEM.

The ODBC Manager manages all the data sources that exists in the system.

The ODBC DRIVER ALLOWS the developer to talk to the back END database.

The ODBC Driver allows the developer to talk to the back end database.

• The NAME of the DBMS,
• the LOCATION of the SOURCE and
• the database DEPENDENT information.

ODBC uses the description of the datasource available in the ODBC.INI file to load the required drivers to access that PARTICULAR back end DATABASE.

ODBC uses the description of the datasource available in the ODBC.INI file to load the required drivers to access that particular back end database.

This 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.

This 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.

%ROWTYPE allows you to ASSOCIATE a VARIABLE with an entire table row. The %TYPE associates a variable with a single COLUMN type.

%ROWTYPE allows you to associate a variable with an entire table row. The %TYPE associates a variable with a single column type.

PL/SQL tables are SCALAR arrays that can be REFERENCED by a binary integer. They can be used to hold VALUES for use in LATER queries or calculations. In Oracle 8 they will be able to be of the %ROWTYPE designation, or RECORD.

PL/SQL tables are scalar arrays that can be referenced by a binary integer. They can be used to hold values for use in later queries or calculations. In Oracle 8 they will be able to be of the %ROWTYPE designation, or RECORD.

The DECLARE statement is USED in PL/SQL anonymous blocks such as with STAND alone, nonstored PL/SQL procedures. It MUST come FIRST in a PL/SQL stand alone file if it is used.

The DECLARE statement is used in PL/SQL anonymous blocks such as with stand alone, nonstored PL/SQL procedures. It must come first in a PL/SQL stand alone file if it is used.

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.

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.

USE the %ISOPEN CURSOR STATUS VARIABLE.

Use the %ISOPEN cursor status variable.

Use the DBMS_OUTPUT PACKAGE. ANOTHER possible method is to just use the SHOW ERROR command, but this only shows errors. The DBMS_OUTPUT package can be used to show intermediate results from LOOPS and the STATUS of VARIABLES as the procedure is executed. The new package UTL_FILE can also be used.

Use the DBMS_OUTPUT package. Another possible method is to just use the SHOW ERROR command, but this only shows errors. The DBMS_OUTPUT package can be used to show intermediate results from loops and the status of variables as the procedure is executed. The new package UTL_FILE can also be used.

There are 12 types of TRIGGERS in PL/SQL that CONSIST of COMBINATIONS of the BEFORE, AFTER, ROW, TABLE, INSERT, UPDATE, DELETE and ALL key WORDS:

• BEFORE ALL ROW INSERT,
• AFTER ALL ROW INSERT,
• BEFORE INSERT,
• AFTER INSERT etc.

There are 12 types of triggers in PL/SQL that consist of combinations of the BEFORE, AFTER, ROW, TABLE, INSERT, UPDATE, DELETE and ALL key words:

The best method is to USE the CHR() function (CHR(10) is a return/linefeed) and the concatenation function "||". ANOTHER method, although it is hard to document and isn't always portable is to use the return/linefeed as a PART of a quoted string.

The best method is to use the CHR() function (CHR(10) is a return/linefeed) and the concatenation function "||". Another method, although it is hard to document and isn't always portable is to use the return/linefeed as a part of a quoted string.

By USE of the EXECUTE (short form EXEC) COMMAND.

By use of the EXECUTE (short form EXEC) command.

By USE of the exclamation POINT "!" (in UNIX and some other OS) or the HOST (HO) command.

By use of the exclamation point "!" (in UNIX and some other OS) or the HOST (HO) command.

This is BEST DONE with the COLUMN COMMAND.

This is best done with the COLUMN command.

MAX(sum_of_cost), min(sum_of_cost), count(item_no), item_no. The only COLUMN that can be grouped on is the "item_no" column, the REST have aggregate FUNCTIONS ASSOCIATED with them.

Max(sum_of_cost), min(sum_of_cost), count(item_no), item_no. The only column that can be grouped on is the "item_no" column, the rest have aggregate functions associated with them.

The COST BASED system allows the use of HINTs to control the optimizer PATH selection. If they can GIVE some example hints such as FIRST ROWS, ALL ROWS, USING INDEX, STAR, even better.

The COST based system allows the use of HINTs to control the optimizer path selection. If they can give some example hints such as FIRST ROWS, ALL ROWS, USING INDEX, STAR, even better.

CARTESIAN product is the RESULT of an unrestricted join 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.

Cartesian product is the result of an unrestricted join 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.

Ascending.

Ascending.

The tkprof tool is a TUNING tool USED to DETERMINE cpu and EXECUTION TIMES for SQL statements.

The tkprof tool is a tuning tool used to determine cpu and execution times for SQL statements.

The EXPLAIN PLAN command is a tool to TUNE SQL statements. To use it you must have an explain_table generated in the user you are RUNNING the explain plan for. This is created using the utlxplan.sql script. Once the explain plan table exists you run the explain plan command giving as its argument the SQL STATEMENT to be explained. The explain_plan table is then queried to see the EXECUTION plan of the statement. Explain plans can also be run using tkprof.

The EXPLAIN PLAN command is a tool to tune SQL statements. To use it you must have an explain_table generated in the user you are running the explain plan for. This is created using the utlxplan.sql script. Once the explain plan table exists you run the explain plan command giving as its argument the SQL statement to be explained. The explain_plan table is then queried to see the execution plan of the statement. Explain plans can also be run using tkprof.

The SET option TERMOUT controls OUTPUT to the SCREEN. Setting TERMOUT OFF TURNS off screen output. This option can be shortened to TERM.

The SET option TERMOUT controls output to the screen. Setting TERMOUT OFF turns off screen output. This option can be shortened to TERM.

The SET OPTIONS FEEDBACK and VERIFY can be set to OFF.

The SET options FEEDBACK and VERIFY can be set to OFF.

By USE of the SPOOL COMMAND.

By use of the SPOOL command.

Enterprise Backup Utility (EBU) is a functionally rich, HIGH PERFORMANCE interface for backing up Oracle7 DATABASES. It is sometimes referred to as OEBU for Oracle Enterprise Backup Utility. The Oracle Recovery Manager (RMAN) utility that SHIPS with Oracle8 and above is similar to Oracle7's EBU utility. However, there is no direct upgrade path from EBU to RMAN.

Enterprise Backup Utility (EBU) is a functionally rich, high performance interface for backing up Oracle7 databases. It is sometimes referred to as OEBU for Oracle Enterprise Backup Utility. The Oracle Recovery Manager (RMAN) utility that ships with Oracle8 and above is similar to Oracle7's EBU utility. However, there is no direct upgrade path from EBU to RMAN.

A PHYSICAL PAGE is a SIZE of a page. That is output by the printer. The logical page is the size of ONE page of the actual report as seen in the Previewer.

A physical page is a size of a page. That is output by the printer. The logical page is the size of one page of the actual report as seen in the Previewer.

A PROPERTY clause is a named object that contains a list of properties and their settings. Once you CREATE a property clause you can base other object on it. An object based on a property can INHERIT the setting of any property in the clause that makes SENSE for that object.

A property clause is a named object that contains a list of properties and their settings. Once you create a property clause you can base other object on it. An object based on a property can inherit the setting of any property in the clause that makes sense for that object.

A RECORD group is an internal Oracle Forms that structure that has a column/row framework similar to a database table. HOWEVER, UNLIKE database tables, record groups are separate objects that belong to the form module which they are DEFINED.

A record group is an internal Oracle Forms that structure that has a column/row framework similar to a database table. However, unlike database tables, record groups are separate objects that belong to the form module which they are defined.

A static record GROUP is not associated with a QUERY, RATHER, you DEFINE its STRUCTURE and row values at design time, and they remain fixed at runtime.

A static record group is not associated with a query, rather, you define its structure and row values at design time, and they remain fixed at runtime.

A user named editor has the same text EDITING functionality as the default editor, but, because it is a named OBJECT, you can specify editor ATTRIBUTES such as WINDOWS display size, position, and title.

A user named editor has the same text editing functionality as the default editor, but, because it is a named object, you can specify editor attributes such as windows display size, position, and title.

A way in which to PASS CONTROL (and possibly arguments ) form Oracle REPORT to another Oracle products of 3GL and then return control ( and ) back to Oracle REPORTS.

A way in which to pass control (and possibly arguments ) form Oracle report to another Oracle products of 3GL and then return control ( and ) back to Oracle reports.

• ADD-GROUP_COLUMN (FUNCTION),
• ADD_GROUP_ROW (PROCEDURE),
• DELETE_GROUP_ROW(procedure).

After the QUERY is EXECUTED but before the REPORT is executed and the RECORDS are DISPLAYED.

After the query is executed but before the report is executed and the records are displayed.

An LOV is a SCROLLABLE POPUP window that PROVIDES the operator with either a SINGLE or MULTI column selection list.

An LOV is a scrollable popup window that provides the operator with either a single or multi column selection list.

An object group is a CONTAINER for a group of OBJECTS; you DEFINE an object group when you want to PACKAGE related objects, so that you copy or reference them in other MODULES.

An object group is a container for a group of objects; you define an object group when you want to package related objects, so that you copy or reference them in other modules.

An Ole server application creates ole OBJECTS that are embedded or LINKED in ole CONTAINERS, ex. Ole servers are ms_word & ms_excel. OLE containers provide a place to store, DISPLAY and manipulate objects that are created by ole server applications. Ex. ORACLE forms is an example of an ole Container.

An Ole server application creates ole Objects that are embedded or linked in ole Containers, ex. Ole servers are ms_word & ms_excel. OLE containers provide a place to store, display and manipulate objects that are created by ole server applications. Ex. oracle forms is an example of an ole Container.

Any EVENT that makes a DIFFERENT record in the master block the CURRENT record is a coordination CAUSING event.

Any event that makes a different record in the master block the current record is a coordination causing event.

At the CLIENT.

At the client.