Explore topic-wise InterviewSolutions in .

You can USE the dbms_redefinition.can_redef_table PROCEDURE to DETERMINE if a table can be REDEFINED.

You can use the dbms_redefinition.can_redef_table procedure to determine if a table can be redefined.

YES, you can USE the dbms_redefinition PACKAGE to REDEFINE a table ONLINE.

Yes, you can use the dbms_redefinition package to redefine a table online.

The information is USEFUL for TRACING. You can set client information, MODULE, or action information from different module of the application. At runtime, you can query different performance views to find out the action performed by application at that SPECIFIC TIME.

The information is useful for tracing. You can set client information, module, or action information from different module of the application. At runtime, you can query different performance views to find out the action performed by application at that specific time.

ORACLE PROVIDES a package called dbms_application_info. This package can be used to SET INFORMATION about current SESSION.

Oracle provides a package called dbms_application_info. This package can be used to set information about current session.

A DML behaves on RAC in a similar manner as on a single node instance except a small change.
Each node on RAC has its own buffer cache. In CASE of DML, it looks for the data block in a local cache. If the current COPY of block is not PRESENT, cache FUSION is applied to get the latest copy from the local cache of other blocks. If this is not possible then the block is read into the local cache from disk and updated similar to a single node instance. The buffer cache of other blocks is fused with the current block later as required.

A DML behaves on RAC in a similar manner as on a single node instance except a small change.
Each node on RAC has its own buffer cache. In case of DML, it looks for the data block in a local cache. If the current copy of block is not present, cache fusion is applied to get the latest copy from the local cache of other blocks. If this is not possible then the block is read into the local cache from disk and updated similar to a single node instance. The buffer cache of other blocks is fused with the current block later as required.

GSD RUNS on each NODE and is not an Oracle background process. This process performs administrative tasks, such as STARTUP and shut down, based on the requests from different CLIENTS, such as DBCA and enterprise manager.

GSD runs on each node and is not an Oracle background process. This process performs administrative tasks, such as startup and shut down, based on the requests from different clients, such as DBCA and enterprise manager.

The CONFIGURATION information for CRS resources is stored in OCR. The Clusterware USES that information to manage CRS resources.

The configuration information for CRS resources is stored in OCR. The Clusterware uses that information to manage CRS resources.

RAC CLUSTER is a DATABASE with a shared cache architecture that overcomes the limitations of traditional shared-nothing and shared-disk APPROACHES. It is a key COMPONENT of Oracle's private cloud architecture.

RAC cluster is a database with a shared cache architecture that overcomes the limitations of traditional shared-nothing and shared-disk approaches. It is a key component of Oracle's private cloud architecture.

You can USE the tnsnames.ora configuration FILE to ENSURE that you have the INSTANCE_NAME parameter SPECIFIED in it.

You can use the tnsnames.ora configuration file to ensure that you have the INSTANCE_NAME parameter specified in it.

Following is the procedure of RESTORING RMAN for the recovery:

•  Bring all the NODES down
•  Start a node
•  Restore all the DATA files and archive LOGS
•  Recover the node
•  Open the DATABASE
•  Bring other nodes up
•  Confirm that all nodes are operational

Following is the procedure of restoring RMAN for the recovery:

TAF is a MAJOR advantage of RAC. It ensures that application failover to another node of RAC when one node fails without any VISIBLE change from application. It also ensures that application servers are USING PROPER failover in TNSNAMES.ORA FILES.

TAF is a major advantage of RAC. It ensures that application failover to another node of RAC when one node fails without any visible change from application. It also ensures that application servers are using proper failover in TNSNAMES.ORA files.

Following are the steps to install and configure RAC:
1. Install operating SYSTEM drivers
2. Configure ASM
3. CREATE ASM disks
4. Install grid infrastructure
5. Create additional disk groups as NEEDED
6. Setup automatic RELOAD of ASM Cluster File System (ACFS) drivers on reboot
7. Setup ACFS disk group
8. Install software
9. Create database
10. Perform sanity checks

Following are the steps to install and configure RAC:
1. Install operating system drivers
2. Configure ASM
3. Create ASM disks
4. Install grid infrastructure
5. Create additional disk groups as needed
6. Setup automatic reload of ASM Cluster File System (ACFS) drivers on reboot
7. Setup ACFS disk group
8. Install software
9. Create database
10. Perform sanity checks

Following are the TWO TYPES of CONNECTION load BALANCING:

•  Server-side load balancing
•  Client-side load balancing

Following are the two types of connection load balancing:

You can DELETE the instances USING either the SILENT mode or the interactive mode using DBCA.

You can delete the instances using either the silent mode or the interactive mode using DBCA.

OCR stores INFORMATION about CLUSTER RESOURCES and their CONFIGURATION. The CRS process uses that information to manage resources.

OCR stores information about cluster resources and their configuration. The CRS process uses that information to manage resources.

CRS is the main PROGRAM that manages high availability operations. The RESOURCE managed by CRS PROCESS is called CRS or cluster resource, such as database, instance, service, listener, VIP address, or application process.

CRS is the main program that manages high availability operations. The resource managed by CRS process is called CRS or cluster resource, such as database, instance, service, listener, VIP address, or application process.

The components of Oracle Clusterware are GIVEN as FOLLOWS:

•  Oracle Process MONITOR Daemon
•  RACG Process
•  Oracle Notification Service
•  Event Manager
•  CLUSTER Ready Service (CRS)
•  Cluster Synchronization Services (CSS)

The components of Oracle Clusterware are given as follows:

You NEED to SET the CLUSTER_DATABASE and INSTANCE_TYPE PARAMETERS while starting up the ASM INSTANCE.

You need to set the CLUSTER_DATABASE and INSTANCE_TYPE parameters while starting up the ASM instance.

If you set the value of RESULT_CACHE_MAX_SIZE PARAMETER to zero, it will disable result CACHE. You cannot disable result cache on one NODE in a RAC; therefore, if you set this parameter to zero on one node, then you have to set this parameter to zero for rest of the NODES in RAC.

If you set the value of RESULT_CACHE_MAX_SIZE parameter to zero, it will disable result cache. You cannot disable result cache on one node in a RAC; therefore, if you set this parameter to zero on one node, then you have to set this parameter to zero for rest of the nodes in RAC.

No, it can only be USED for ORACLE DATABASE 11G RELEASES.

No, it can only be used for Oracle database 11g releases.

Applications can receive FAN event NOTIFICATION in the FOLLOWING situations:

•  RAC SERVICE up
•  RAC service down
•  Node down
•  Load balancing ADVISORY

Applications can receive FAN event notification in the following situations:

RAC can be managed USING Oracle Enterprise MANAGER (OEM), SERVER Control Utility (srvctl), and Database Configuration Assistant (DBCA).

RAC can be managed using Oracle Enterprise Manager (OEM), Server Control Utility (srvctl), and Database Configuration Assistant (DBCA).

A VIP ESSENTIALLY POINTS to another host. VIP ADDRESS failover happens WHENEVER the host pointed by the VIP fails.

A VIP essentially points to another host. VIP address failover happens whenever the host pointed by the VIP fails.

The three network COMPONENTS of RAC are public, PRIVATE, and VIP.

The three network components of RAC are public, private, and VIP.

VIP is an IP ADDRESS, which is not directly CONNECTED to any host. It is a spare address, which can be mapped to another host in the same subnet. It can be easily mapped to another host in case of a failure.

VIP is an IP address, which is not directly connected to any host. It is a spare address, which can be mapped to another host in the same subnet. It can be easily mapped to another host in case of a failure.

ORACLE NET SERVICES enables the load BALANCING of APPLICATIONS in RAC.

Oracle Net Services enables the load balancing of applications in RAC.

An Oracle SERVICE must have a UNIQUE name. It OFFERS WORKLOAD BALANCING and failover options.

An Oracle service must have a unique name. It offers workload balancing and failover options.

A RAC SETUP SHARES datafiles, CONTROL files, SP Files, redo log files; THEREFORE, these files MUST be stored in the cluster-aware shared storage.

A RAC setup shares datafiles, control files, SP Files, redo log files; therefore, these files must be stored in the cluster-aware shared storage.

RSMN stands for REMOTE Slave MONITOR process. It creates slave processes on remote instance on behalf of master coordinating process running on ANOTHER instance.

RSMN stands for Remote Slave Monitor process. It creates slave processes on remote instance on behalf of master coordinating process running on another instance.

RMSn are RAC Management PROCESSES. These processes manage RAC and create more resources WHENEVER NEW INSTANCES are added to RAC.

RMSn are RAC Management processes. These processes manage RAC and create more resources whenever new instances are added to RAC.

LCKO is LOCK process, which is used to manage requests for SHARED RESOURCES.

LCKO is lock process, which is used to manage requests for shared resources.

LMS stands for Lock Monitor Service. The primary JOB of this process is to transfer data blocks between cache of DIFFERENT nodes using high-speed interconnect. It is the most IMPORTANT and critical process for cache fusion. Each NODE has at least two LMS processes.

LMS stands for Lock Monitor Service. The primary job of this process is to transfer data blocks between cache of different nodes using high-speed interconnect. It is the most important and critical process for cache fusion. Each node has at least two LMS processes.

LMD STANDS for Lock Monitor DAEMON process. This process is used for deadlock DETECTION. It also manages remote resource and enqueue requests.

LMD stands for Lock Monitor Daemon process. This process is used for deadlock detection. It also manages remote resource and enqueue requests.

It MANAGES global resources and locks. It configures locks and resources WHENEVER an instance JOINS or leaves the CLUSTER. It is also called Global Enqueue Service MONITOR.

It manages global resources and locks. It configures locks and resources whenever an instance joins or leaves the cluster. It is also called Global Enqueue Service Monitor.

GTX is a Global TRANSACTION PROCESS, which provides transparent support for XA global transactions. The number of these processes is DECIDED AUTOMATICALLY based on the REQUIREMENTS.

GTX is a Global Transaction process, which provides transparent support for XA global transactions. The number of these processes is decided automatically based on the requirements.

In a RAC setup, each node has its own memory; however, they SHARE physical datafiles. As we know that data blocks are read into memory for updates or query in a single instance database. Similarly, in a RAC set up, a node reads a block from datafile when the node NEEDS it. However, in RAC setting, the required block may be already available in the memory of another node and it is FASTER to read block from the memory of another block than from a datafile. Therefore, RAC provides a mechanism to read block from memory of one node to the memory of another node. This mechanism is called cache fusion.
ORACLE uses high-speed interconnect to communicate between nodes. GES monitors and the Instance Enqueue process MANAGES the cache fusion.

In a RAC setup, each node has its own memory; however, they share physical datafiles. As we know that data blocks are read into memory for updates or query in a single instance database. Similarly, in a RAC set up, a node reads a block from datafile when the node needs it. However, in RAC setting, the required block may be already available in the memory of another node and it is faster to read block from the memory of another block than from a datafile. Therefore, RAC provides a mechanism to read block from memory of one node to the memory of another node. This mechanism is called cache fusion.
Oracle uses high-speed interconnect to communicate between nodes. GES monitors and the Instance Enqueue process manages the cache fusion.

RAC ENSURES data CONSISTENCY between two NODES through CACHE FUSION.

RAC ensures data consistency between two nodes through cache fusion.

ACMS ENSURES global updates to System Global Area (SGA) in a RAC SET up.

ACMS ensures global updates to System Global Area (SGA) in a RAC set up.

Whenever an APPLICATION uses VIP to connect to a database, it can failover to ANOTHER available node in case of a failure of one node. You need to use VIP as the HOST NAME in the Transparent Network Substrate (TNS) ENTRY to use VIP.

Whenever an application uses VIP to connect to a database, it can failover to another available node in case of a failure of one node. You need to use VIP as the host name in the Transparent Network Substrate (TNS) entry to use VIP.

GRD is used by GES and GCS to MAINTAIN status of datafiles and CACHED blocks. This PROCESS provides required information for cache fusion and maintains data integrity.

GRD is used by GES and GCS to maintain status of datafiles and cached blocks. This process provides required information for cache fusion and maintains data integrity.

Following statements can be used to START or STOP an instance on RAC:

Following statements can be used to start or stop an instance on RAC:

A non-RAC database has a SINGLE NODE while a RAC database has MULTIPLE (at LEAST two) nodes. The nodes in a RAC set up share storage. RAC offers failover option while a non-RAC database does not offer failover option because it is based on a single node.

A non-RAC database has a single node while a RAC database has multiple (at least two) nodes. The nodes in a RAC set up share storage. RAC offers failover option while a non-RAC database does not offer failover option because it is based on a single node.

DML HANDLER can be set by using the FOLLOWING STATEMENT:
Dbms_apply_adm.set_dml_handler(object_name/object_type, operation_name/error_handler,user_procedure,apply_db_link).

DML handler can be set by using the following statement:
Dbms_apply_adm.set_dml_handler(object_name/object_type, operation_name/error_handler,user_procedure,apply_db_link).

FOLLOWING are some IMPORTANT STREAMS VIEWS:

•  DBA_STREAMS_TABLE_RULES
•  DBA_APPLY_CONFLICT_COLUMNS
•  GV$STREAMS_CAPTURE

Following are some important Streams views:

You can FIND the SETUP of lob_assembly by USING the DBA_APPLY_DML_HANDLER VIEW.

You can find the setup of lob_assembly by using the DBA_APPLY_DML_HANDLER view.

Generally, capture process functions at source DATABASE. However, if you WANT to save RESOURCES at the source database, you can set up another database for the capture process only. The feature, which allows you to move capture process to another database, is CALLED downstream capture.

Generally, capture process functions at source database. However, if you want to save resources at the source database, you can set up another database for the capture process only. The feature, which allows you to move capture process to another database, is called downstream capture.

SYS.AnyData is a QUEUE that can capture messages of TYPE AnyData. This is a STANDARD USED in the Streams replication for storing LCRs. The reason for using this queue is that messages are WRAPPED into type AnyData before queuing.

SYS.AnyData is a queue that can capture messages of type AnyData. This is a standard used in the Streams replication for storing LCRs. The reason for using this queue is that messages are wrapped into type AnyData before queuing.

The APPLY PROCESS is a background process that runs on target database. It dequeues messages (LCR) and applies those to the target database EITHER directly or through HANDLER.

The apply process is a background process that runs on target database. It dequeues messages (LCR) and applies those to the target database either directly or through handler.

Capture PROCESS extracts database CHANGES from redo LOG files at source. It Is a BACKGROUND process.

Capture process extracts database changes from redo log files at source. It Is a background process.

LCR contains database change. Streams require the changes to be CAPTURED in SPECIFIC format. LCR KEEPS the changes in that format.

LCR contains database change. Streams require the changes to be captured in specific format. LCR keeps the changes in that format.