Explore topic-wise InterviewSolutions in .

• SYSTEM.cordination_operation
• System Date_threshold
• System.effective_Date
• System.event_window
• System.suppress_working.

• TEXT item.
• Chart item.
• Check BOX.
• DISPLAY item.
• Image item.
• List item.
• Radio GROUP.
• USER Area item.

The LAYOUT EDITOR is a graphical design facility for creating and arranging items and boilerplate text and graphics OBJECTS in your application's INTERFACE.

The Layout Editor is a graphical design facility for creating and arranging items and boilerplate text and graphics objects in your application's interface.

To pass ONE or more PARAMETERS to a called form, the calling form must perform the following steps in a trigger or user named routine execute the create_parameter_list built-in function to programmatically. Create a parameter list to execute the ADD parameter built-in procedure to add one or more parameters list. Execute the call_form, New_form or run_product built_in procedure and include the NAME or id of the parameter list to be PASSED to the called form.

To pass one or more parameters to a called form, the calling form must perform the following steps in a trigger or user named routine execute the create_parameter_list built-in function to programmatically. Create a parameter list to execute the add parameter built-in procedure to add one or more parameters list. Execute the call_form, New_form or run_product built_in procedure and include the name or id of the parameter list to be passed to the called form.

UNLIMITED no of RADIO BUTTONS can be ASSIGNED to a radio GROUP.

Unlimited no of radio buttons can be assigned to a radio group.

Visual Attributes are the FONT, COLOR and pattern characteristics of OBJECTS that OPERATORS see and intract with in our application.

Visual Attributes are the font, color and pattern characteristics of objects that operators see and intract with in our application.

• When-Image-activated(FIRES when the OPERATOR DOUBLE CLICKS on an image Items).
• When-image-pressed(fires when the operator selects or deselects the image item).

• When-window-activated,
• when-window-closed,
• when-window-deactivated,
• when-window-resized.

Yes.

Yes.

Yes.

Yes.

YES. Set_item_proprety.

Yes. Set_item_proprety.

1. NAVIGATIONAL TRIGGERS.
2. TRANSACTION Triggers.

1. Navigational Triggers.
2. Transaction Triggers.

1. Restricted PACKAGE procedure.
2. UNRESTRICTED package procedure.

1. Restricted package procedure.
2. Unrestricted package procedure.

1. System.block_status
2. System.current_block
3. System.current_field
4. System.current_value
5. System.cursor_block
6. System.cursor_field
7. System.field_status.

1. System.current_field GIVES NAME of the FIELD.
2. System.cursor_field gives name of the field with BLOCK name.

1. System.current_field gives name of the field.
2. System.cursor_field gives name of the field with block name.

255 CHARACTER WIDTH and 255 CHARACTERS LENGTH.

255 character width and 255 characters Length.

A PACKAGE PROCEDURE is BUILT in PL/SQL procedure.

A Package procedure is built in PL/SQL procedure.

A PIECE of logic that is executed at or triggered by a SQL *FORMS EVENT.

A piece of logic that is executed at or triggered by a SQL *forms event.

A USER exit is a subroutine which are WRITTEN in programming languages using PRO*C pro *Cobol , ETC., that link into the SQL * forms executable.

A user exit is a subroutine which are written in programming languages using pro*C pro *Cobol , etc., that link into the SQL * forms executable.

An ALERT is window that appears in the MIDDLE of the screen OVERLAYING a PORTION of the current display.

An alert is window that appears in the middle of the screen overlaying a portion of the current display.

• Anchor-VIEW
• RESIZE -View
• Move-View.

You can run the 'ANALYZE INDEX VALIDATE STRUCTURE' command on the affected indexes - each invocation of this command creates a single row in the INDEX_STATS view. This row is OVERWRITTEN by the next ANALYZE INDEX command, so COPY the contents of the view into a local table after each ANALYZE. The 'badness' of the index can then be JUDGED by the ratio of 'DEL_LF_ROWS' to 'LF_ROWS'.

You can run the 'ANALYZE INDEX VALIDATE STRUCTURE' command on the affected indexes - each invocation of this command creates a single row in the INDEX_STATS view. This row is overwritten by the next ANALYZE INDEX command, so copy the contents of the view into a local table after each ANALYZE. The 'badness' of the index can then be judged by the ratio of 'DEL_LF_ROWS' to 'LF_ROWS'.

The likely cause of this is because the execution plan has CHANGED. Generate a current explain plan of the offending query and compare it to a previous one that was TAKEN when the query was performing WELL. Usually the previous plan is not AVAILABLE.

Some factors that can cause a plan to change are:

• Which tables are currently analyzed? Were they previously analyzed? (ie. Was the query using RBO and now CBO?)
• Has OPTIMIZER_MODE been changed in INIT.ORA?
• Has the DEGREE of parallelism been defined/changed on any table?
• Have the tables been re-analyzed? Were the tables analyzed using estimate or compute? If estimate, what percentage was used?
• Have the statistics changed?
• Has the INIT.ORA parameter DB_FILE_MULTIBLOCK_READ_COUNT been changed?
• Has the INIT.ORA parameter SORT_AREA_SIZE been changed?
• Have any other INIT.ORA parameters been changed?
• What do you think the plan should be? Run the query with hints to SEE if this produces the required performance.

The likely cause of this is because the execution plan has changed. Generate a current explain plan of the offending query and compare it to a previous one that was taken when the query was performing well. Usually the previous plan is not available.

Some factors that can cause a plan to change are:

The UTLESTAT REPORT shows I/O per tablespace but ONE cannot see what tables in the tablespace has the most I/O. The $ORACLE_HOME/rdbms/admin/catio.sql script CREATES a sample_io procedure and table to GATHER the required information. After executing the procedure, one can do a simple SELECT * FROM io_per_object; to extract the required information. For more DETAILS, look at the header comments in the $ORACLE_ HOME/ rdbms/admin/catio.sql script.

The UTLESTAT report shows I/O per tablespace but one cannot see what tables in the tablespace has the most I/O. The $ORACLE_HOME/rdbms/admin/catio.sql script creates a sample_io procedure and table to gather the required information. After executing the procedure, one can do a simple SELECT * FROM io_per_object; to extract the required information. For more details, look at the header comments in the $ORACLE_ HOME/ rdbms/admin/catio.sql script.

ENTER Validate-data in the CURRENT VALIDATION UNIT.

Enter Validate-data in the current validation unit.

It is possible to improve %XYZ% QUERIES by forcing the OPTIMIZER to scan all the entries from the index INSTEAD of the table. This can be done by specifying HINTS. If the index is physically smaller than the table (which is USUALLY the case) it will take less time to scan the entire index than to scan the entire table.

It is possible to improve %XYZ% queries by forcing the optimizer to scan all the entries from the index instead of the table. This can be done by specifying hints. If the index is physically smaller than the table (which is usually the case) it will take less time to scan the entire index than to scan the entire table.

It's IMPORTANT to have statistics on all tables for the CBO (Cost Based Optimizer) to work correctly. If one table involved in a STATEMENT does not have statistics, Oracle has to revert to rule-based optimization for that statement. So you really want for all tables to have statistics right away; it won't help MUCH to just have the larger tables analyzed.

Generally, the CBO can change the execution PLAN when you:

1. Change statistics of objects by doing an ANALYZE;
2. Change some initialization PARAMETERS (for example: hash_join_enabled, sort_area_size, db_ file_ multi block_ read_count).

It's important to have statistics on all tables for the CBO (Cost Based Optimizer) to work correctly. If one table involved in a statement does not have statistics, Oracle has to revert to rule-based optimization for that statement. So you really want for all tables to have statistics right away; it won't help much to just have the larger tables analyzed.

Generally, the CBO can change the execution plan when you:

False.

False.

FUNCTION key triggers are ASSOCIATED with individual SQL*FORMS function keys You can attach Key function triggers to 10 keys or key sequences that normally do not perform any SQL * FORMS OPERATIONS. These keys referred as key F0 through key F9.

Function key triggers are associated with individual SQL*FORMS function keys You can attach Key function triggers to 10 keys or key sequences that normally do not perform any SQL * FORMS operations. These keys referred as key F0 through key F9.

• FUNCTION KEY
• Key-function
• Key-others
• Key-startup.

HIDE the FIELDS for INTERNAL CALCULATION.

Hide the fields for internal calculation.

HOST (E.g. Host (SQLPLUS)).

Host (E.g. Host (sqlplus)).

• INP (SOURCE FILE).
• FRM (EXECUTABLE File).

It FIRES just before SQL * FORMS the CURRENT BLOCK.

It fires just before SQL * forms the current block.

No.

No.

No.

No.

No.

No.

No.

No.

On-validate-FIELD trigger FIRES, when the field Validation status New or changed. Post-field-trigger WHENEVER the control leaving FORM the field, it will fire.

On-validate-field trigger fires, when the field Validation status New or changed. Post-field-trigger whenever the control leaving form the field, it will fire.

Pages are COLLECTION of DISPLAY INFORMATION, such as constant TEXT and graphics.

Pages are collection of display information, such as constant text and graphics.

PAUSE suspends processing until the OPERATOR presses a FUNCTION key.

Pause suspends processing until the operator presses a function key.

• ON-INSERT
• POST-INSERT
• PRE-INSERT

• PRE-QUERY FIRES once.
• POST-QUERY fires 10 TIMES.

Restricted package procedure that AFFECTS the basic functions of SQL * FORMS. It cannot used in all triggers except KEY triggers. Unrestricted package procedure that does not INTERFERE with the basic functions of SQL * Forms it can be used in any triggers.

Restricted package procedure that affects the basic functions of SQL * Forms. It cannot used in all triggers except key triggers. Unrestricted package procedure that does not interfere with the basic functions of SQL * Forms it can be used in any triggers.

Select the use CONSTRAINT PROPERTY is ON BLOCK DEFINITION screen. 

Select the use constraint property is ON Block definition screen. 

SQL *forms is 4GL tool for developing and executing; Oracle based INTERACTIVE APPLICATION.

SQL *forms is 4GL tool for developing and executing; Oracle based interactive application.

These triggers are executes when INSERTING, deleting and updating operations are performed and can be used to CHANGE the default function of INSERT, DELETE or update respectively. For Eg, INSTEAD of inserting a row in a table an existing row can be updated in the same table.

These triggers are executes when inserting, deleting and updating operations are performed and can be used to change the default function of insert, delete or update respectively. For Eg, instead of inserting a row in a table an existing row can be updated in the same table.

Unlimited.

Unlimited.

USING On-Message or On-Error TRIGGERS.

using On-Message or On-Error triggers.

When Execute-query or count-query PACKAGE PROCEDURES are INVOKED.

When Execute-query or count-query Package procedures are invoked.