Explore topic-wise InterviewSolutions in .

VIEW by STRUCTURE and view by TYPE .

View by structure and view by type .

when one FORM invokes another form by EXECUTING open_form the first form remains DISPLAYED, and operators can navigate between the forms as desired. when one form invokes another form by executing call_form, the called form is MODAL with respect to the CALLING form. That is, any windows that belong to the calling form are disabled, and operators cannot navigate to them until they first exit the called form.

when one form invokes another form by executing open_form the first form remains displayed, and operators can navigate between the forms as desired. when one form invokes another form by executing call_form, the called form is modal with respect to the calling form. That is, any windows that belong to the calling form are disabled, and operators cannot navigate to them until they first exit the called form.

When-image-activated FIRES, when the OPERATORS double CLICKS on an image ITEM, when-image-pressed fires, when an OPERATOR clicks or double clicks on an image item.

When-image-activated fires, when the operators double clicks on an image item, when-image-pressed fires, when an operator clicks or double clicks on an image item.

While both reports 2.0 and 2.5 CREATE the parameter, report 2.5 GIVES a MESSAGE that a bind parameter has been CREATED.

While both reports 2.0 and 2.5 create the parameter, report 2.5 gives a message that a bind parameter has been created.

Yes.

Yes.

Yes.

Yes.

Yes. Each window you create must have atleast one content canvas view assigned to it. You can also create a window that has MANIPULATED content canvas view. At RUN TIME only one of the content canvas VIEWS assign to a window is displayed at a time.

Yes. Each window you create must have atleast one content canvas view assigned to it. You can also create a window that has manipulated content canvas view. At run time only one of the content canvas views assign to a window is displayed at a time.

You can pass PARAMETER values to a FORM when an application EXECUTES the call_form, New_form, Open_form or Run_product.

You can pass parameter values to a form when an application executes the call_form, New_form, Open_form or Run_product.

- A simple snapshot is BASED on a query that does not contains GROUP BY CLAUSES, CONNECT BY clauses, JOINS, sub-query or snashot of operations.
- A complex snapshots CONTAIN atleast any one of the above.

- A simple snapshot is based on a query that does not contains GROUP BY clauses, CONNECT BY clauses, JOINs, sub-query or snashot of operations.
- A complex snapshots contain atleast any one of the above.

- REPLICATION of data in DISTRIBUTED environment.
- Using snapshots to replicate data.
- Using REMOTE procedure calls.

- Replication of data in distributed environment.
- Using snapshots to replicate data.
- Using remote procedure calls.

A DISTRIBUTED DATABASE is a network of DATABASES managed by MULTIPLE database servers that appears to a user as single logical database. The data of all databases in the distributed database can be simultaneously accessed and modified.

A distributed database is a network of databases managed by multiple database servers that appears to a user as single logical database. The data of all databases in the distributed database can be simultaneously accessed and modified.

COMPLETE - Tables are COMPLETELY regenerated using the snapshots query and the master tables every time the snapshot referenced.
FAST - If simple snapshot used then a snapshot log can be used to send the changes to the snapshot tables.
FORCE - Default VALUE. If POSSIBLE it PERFORMS a FAST refresh; Otherwise it will perform a complete refresh.

COMPLETE - Tables are completely regenerated using the snapshots query and the master tables every time the snapshot referenced.
FAST - If simple snapshot used then a snapshot log can be used to send the changes to the snapshot tables.
FORCE - Default value. If possible it performs a FAST refresh; Otherwise it will perform a complete refresh.

Database on other servers can be UPDATED and those transactions can be GROUPED together with OTHERS in a logical unit.
Database uses a TWO phase commit.

Database on other servers can be updated and those transactions can be grouped together with others in a logical unit.
Database uses a two phase commit.

It is a table that MAINTAINS a record of MODIFICATIONS to the master table in a SNAPSHOT. It is stored in the same database as master table and is only available for SIMPLE SNAPSHOTS. It should be created before creating snapshots.

It is a table that maintains a record of modifications to the master table in a snapshot. It is stored in the same database as master table and is only available for simple snapshots. It should be created before creating snapshots.

Prepare phase - The global coordinator (initiating node) ask a PARTICIPANTS to prepare (to promise to commit or rollback the transaction, EVEN if there is a failure.
Commit Phase - If all participants respond to the coordinator that they are PREPARED, the coordinator asks all nodes to commit the transaction, if all participants cannot prepare, the coordinator asks all nodes to ROLL back the transaction.

Prepare phase - The global coordinator (initiating node) ask a participants to prepare (to promise to commit or rollback the transaction, even if there is a failure.
Commit Phase - If all participants respond to the coordinator that they are prepared, the coordinator asks all nodes to commit the transaction, if all participants cannot prepare, the coordinator asks all nodes to roll back the transaction.

SIMPLE and COMPLEX.

Simple and Complex.

SNAPSHOTS and SNAPSHOT LOGS.

Snapshots and SNAPSHOT LOGs.

SNAPSHOTS are read-only copies of a master table LOCATED on a remote node which is periodically REFRESHED to reflect CHANGES MADE to the master table.

Snapshots are read-only copies of a master table located on a remote node which is periodically refreshed to reflect changes made to the master table.

SQL *NET is ORACLE's MECHANISM for interfacing with the communication protocols USED by the NETWORKS that facilitate distributed processing and distributed databases. It is used in Clint-Server and Server-Server communications.

SQL *NET is ORACLE's mechanism for interfacing with the communication protocols used by the networks that facilitate distributed processing and distributed databases. It is used in Clint-Server and Server-Server communications.

Time the REFERENCES to OCCUR when master tables are not in USE. Peform the reference manually immediately LOCKING the master tables. We can join tables in SNAPSHOTS by creating a complex snapshots that will be based on the master tables.

Time the references to occur when master tables are not in use. Peform the reference manually immediately locking the master tables. We can join tables in snapshots by creating a complex snapshots that will be based on the master tables.

Two-phase COMMIT is MECHANISM that guarantees a distributed transaction either commits on all involved nodes or ROLLS back on all involved nodes to maintain DATA consistency across the global distributed database. It has two phase, a Prepare Phase and a Commit Phase.

Two-phase commit is mechanism that guarantees a distributed transaction either commits on all involved nodes or rolls back on all involved nodes to maintain data consistency across the global distributed database. It has two phase, a Prepare Phase and a Commit Phase.

• DBA_FREE_SPACE
• DBA_SEGMENTS
• DBA_DATA_FILES.

QUERY V$fixed_view_definition.
EXAMPLE: SELECT * FROM v$fixed_view_definition WHERE view_name='V$SESSION';

Query v$fixed_view_definition.
Example: SELECT * FROM v$fixed_view_definition WHERE view_name='V$SESSION';

Each database USER is assigned a PROFILE that specifies limitations on VARIOUS system RESOURCES available to the user.

Each database user is assigned a Profile that specifies limitations on various system resources available to the user.

Unlike normal tablespaces, true TEMPORARY tablespace INFORMATION is not listed in DBA_FREE_SPACE. Instead use the V$TEMP_SPACE_HEADER VIEW:

Unlike normal tablespaces, true temporary tablespace information is not listed in DBA_FREE_SPACE. Instead use the V$TEMP_SPACE_HEADER view:

TEMPFILES, UNLIKE normal DATAFILES, are not listed in v$datafile or dba_data_files. Instead query v$tempfile or dba_temp_files:

Tempfiles, unlike normal datafiles, are not listed in v$datafile or dba_data_files. Instead query v$tempfile or dba_temp_files:

MONITORING of USER access to AID in the INVESTIGATION of database use.

Monitoring of user access to aid in the investigation of database use.

OBJECT AUDITING is the auditing of accesses to SPECIFIC schema OBJECTS without regard to user.

Object auditing is the auditing of accesses to specific schema objects without regard to user.

Privilege AUDITING is the auditing of the USE of powerful system PRIVILEGES WITHOUT regard to specifically NAMED objects.

Privilege auditing is the auditing of the use of powerful system privileges without regard to specifically named objects.

• REDUCED GRANTING OF PRIVILEGES - Rather than explicitly granting the same set of privileges to many users a database ADMINISTRATOR can grant the privileges for a group of RELATED user's granted to a ROLE and then grant only the role to each member of the group.
• DYNAMIC PRIVILEGE MANAGEMENT - When the privileges of a group must change, only the privileges of the role need to be modified. The security domains of all users granted the group's role automatically reflect the changes made to the role.
• SELECTIVE AVAILABILITY OF PRIVILEGES - The roles granted to a user can be selectively enable (available for use) or disabled (not available for use). This allows specific control of a user's privileges in any given situation.
• APPLICATION AWARENESS - A database application can be designed to automatically enable and disable selective roles when a user attempts to use the application.

Roles are NAMED groups of RELATED PRIVILEGES that are GRANTED to USERS or other roles.

Roles are named groups of related privileges that are granted to users or other roles.

Roles are the easiest way to grant and manage common PRIVILEGES needed by DIFFERENT groups of DATABASE USERS. Creating roles and assigning provides to roles. Assign each role to group of users. This will SIMPLIFY the job of assigning privileges to individual users.

Roles are the easiest way to grant and manage common privileges needed by different groups of database users. Creating roles and assigning provides to roles. Assign each role to group of users. This will simplify the job of assigning privileges to individual users.

• SHUT the DATABASE
• BACKUP the database
• Modify/Include LOG_ARCHIVE_START_TRUE in init.ora FILE.
• START up the database.

SQL * DBA - This allows DBA to monitor and control an ORACLE database.
SQL * Loader - It LOADS data from standard operating SYSTEM files (Flat files) into ORACLE database TABLES. Export (EXP) and Import (imp) utilities allow you to move existing data in ORACLE format to and from ORACLE database.

SQL * DBA - This allows DBA to monitor and control an ORACLE database.
SQL * Loader - It loads data from standard operating system files (Flat files) into ORACLE database tables. Export (EXP) and Import (imp) utilities allow you to move existing data in ORACLE format to and from ORACLE database.

Statement auditing is the auditing of the powerful SYSTEM privileges WITHOUT regard to SPECIFICALLY NAMED OBJECTS.

Statement auditing is the auditing of the powerful system privileges without regard to specifically named objects.

STATEMENT AUDITING, PRIVILEGE Auditing and OBJECT Auditing.

Statement Auditing, Privilege Auditing and Object Auditing.

The collective amount of DISK space available to the OBJECTS in a schema on a particular TABLESPACE.

The collective amount of disk space available to the objects in a schema on a particular tablespace.

• The number of concurrent SESSIONS the user can establish the CPU processing time available to the user's session.
• The CPU processing time available to a SINGLE call to ORACLE made by a SQL statement.
• The amount of logical I/O available to the user's session.
• The AMOUT of logical I/O available to a single call to ORACLE made by a SQL statement.
• The allowed amount of idle time for the user's session.
• The allowed amount of connect time for the user's session.

The TABLESPACE to CONTAIN SCHEMA objects CREATED without specifying a tablespace name.

The Tablespace to contain schema objects created without specifying a tablespace name.

To perform ONE of these function on an index,table, or cluster:
- To collect statistics about object USED by the optimizer and STORE them in the data dictionary.
- To delete statistics about the object used by object from the data dictionary.
- To validate the STRUCTURE of the object.
- To identify migrated and chained rows of the table or cluster.

To perform one of these function on an index,table, or cluster:
- To collect statistics about object used by the optimizer and store them in the data dictionary.
- To delete statistics about the object used by object from the data dictionary.
- To validate the structure of the object.
- To identify migrated and chained rows of the table or cluster.

A database INSTANCE (Server) is a set of MEMORY structure and background processes that access a set of database files.The PROCESS can be shared by all users. The memory structure that are used to store most queried data from database. This helps up to improve database performance by decreasing the amount of I/O performed against data FILE.

A database instance (Server) is a set of memory structure and background processes that access a set of database files.The process can be shared by all users. The memory structure that are used to store most queried data from database. This helps up to improve database performance by decreasing the amount of I/O performed against data file.

An index is a database structure used by the SERVER to have direct access of a ROW in a table. An index is automatically created when a unique of primary key constraint clause is SPECIFIED in CREATE table comman (VER 7.0)

An index is a database structure used by the server to have direct access of a row in a table. An index is automatically created when a unique of primary key constraint clause is specified in create table comman (Ver 7.0)

GROUP of tables physically stored TOGETHER because they share common COLUMNS and are OFTEN used together is called CLUSTER.

Group of tables physically stored together because they share common columns and are often used together is called Cluster.

MULTIPLE INSTANCES ACCESSING the same DATABASE (Only In Multi-CPU ENVIRONMENTS).

Multiple instances accessing the same database (Only In Multi-CPU environments).

The related columns of the tables are CALLED the cluster KEY. The cluster key is indexed using a cluster INDEX and its VALUE is stored only once for multiple tables in the cluster.

The related columns of the tables are called the cluster key. The cluster key is indexed using a cluster index and its value is stored only once for multiple tables in the cluster.

The SET of objects owned by user account is CALLED the SCHEMA.

The set of objects owned by user account is called the schema.

TWO processes wating to update the rows of a table which are locked by the other process then deadlock ARISES. In a database environment this will often HAPPEN because of not issuing proper row lock commands. Poor design of front-end application MAY cause this SITUATION and the performance of server will reduce drastically.
These locks will be released automatically when a commit/rollback operation performed or any one of this processes being killed externally.

Two processes wating to update the rows of a table which are locked by the other process then deadlock arises. In a database environment this will often happen because of not issuing proper row lock commands. Poor design of front-end application may cause this situation and the performance of server will reduce drastically.
These locks will be released automatically when a commit/rollback operation performed or any one of this processes being killed externally.

A Read-Only transaction ENSURES that the results of each QUERY executed in the transaction are CONSISTENT with respect to the same POINT in TIME.

A Read-Only transaction ensures that the results of each query executed in the transaction are consistent with respect to the same point in time.

COMMIT makes permanent changes resulting from all SQL statements in the TRANSACTION. The changes made by the SQL statements of a transaction become visible to other user sessions transactions that START only after transaction is COMMITTED.

COMMIT makes permanent changes resulting from all SQL statements in the transaction. The changes made by the SQL statements of a transaction become visible to other user sessions transactions that start only after transaction is committed.

Considering available access paths and determining the most EFFICIENT execution PLAN based on statistics in the data DICTIONARY for the tables accessed by the statement and their ASSOCIATED clusters and INDEXES.

Considering available access paths and determining the most efficient execution plan based on statistics in the data dictionary for the tables accessed by the statement and their associated clusters and indexes.