Oracle ACE Pro
Oracle Solution Architect
Oracle E-Business Suite
Oracle Cloud Infrastructure
Oracle Fusion Middleware
Oracle Database Administration
Oracle Weblogic Administration
Oracle ACE Pro
Oracle Solution Architect
Oracle E-Business Suite
Oracle Cloud Infrastructure
Oracle Fusion Middleware
Oracle Database Administration
Oracle Weblogic Administration
ROWID is the physical address (location) of the row on the disk. This is the fastest way to access a row in a table.
There are 6 types of SQL statements.
Data Definition Language (DDL): The DDL statements define and maintain objects and drop objects.
Data Manipulation Language (DML): The DML statements manipulate database data.
Transaction Control Statements: Manage change by DML.
Session Control: Used to control the properties of current session enabling and disabling roles.
System Control Statements: Change Properties of Oracle Instance.
Embedded SQL: Incorporate DDL, DML and T.C.S in Programming Language.
There are Three Integrity Rules as follows:
Entity Integrity Rule: The Entity Integrity Rule enforces that the Primary key cannot be Null.
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.
Business Integrity Rules: The Third Integrity rule is about the complex business processes which cannot be implemented by the above 2 rules.
We can implement the if statement in the select statement by using the Decode statement.
e.g select DECODE (EMP_CAT,’1′,’First’,’2′,’Second’Null);
Here, the Null is the else statement where null is done .
We can delete the duplicate rows in the table by using the Rowid
Example: DELETE FROM table_name a Where rowid>(select min(rowid) from table_name b where a.table_no=b.table_no);
Yes we can disable database triggers through following issuing statement
ALTER TABLE TABLE [DISABLE all_trigger ]
14.Is space acquired in blocks or extents?
No, Only one of them should be used at a time.
FCF is now deprecated along with the Implicit Connection Caching in favor of using the Universal Connection Pool (UCP) for JDBC.
The default parameter settings work perfectly for ASM. The only parameters needed for 11g ASM:
No, RDBMS does I/O directly to the raw disk devices, the FILESYSTEMIO_OPTIONS parameter is only for filesystems.
Oracle recommends two diskgroups to provide a balance of manageability, utilization, and performance.
In most cases the storage team will dictate to you based on their standardized LUN size. The ASM administrator merely has to communicate the ASM Best Practices and application characteristics to storage:
Yes, disk sizes can be varied, Oracle ASM will manage data efficiently and intelligent by placing the extents proportional to the size of the disk in the disk group, bigger diskgroups have more extents than lesser ones.
Well, there is not much difference between 10g and 11g (Release-1) RAC.
But there is a significant difference in 11gR2.
Prior to 11gR1(10g) RAC, the following were managed by Oracle CRS
From 11gR2 its completed HA stack managing and providing the following resources as like the other cluster software like VCS etc.
Grid Naming service (GNS) is alternative service to Domain Naming Service (DNS) , which will act as a sub domain in your DNS but managed by Oracle, with GNS the connection is routed to the cluster IP and manages internally.
Control files |
Flashback logs | Data Pump dump sets |
Data files | DB SPFILE | Data Guard configuration |
Temporary data files | RMAN backup sets | Change tracking bitmaps |
Online redo logs | RMAN data file copies | OCR files |
Archive logs | Transport data files |
ASM SPFILE |
Process |
Description |
RBAL | Opens all device files as part of discovery and coordinates the rebalance activity |
ARBn | One or more slave processes that do the rebalance activity |
GMON | Responsible for managing the disk-level activities such as drop or offline and advancing the ASM disk group compatibility |
MARK | Marks ASM allocation units as stale when needed |
Onnn | One or more ASM slave processes forming a pool of connections to the ASM instance for exchanging messages |
PZ9n | One or more parallel slave processes used in fetching data on clustered ASM installation from GV$ views |
In 11gr2 the listeners will run from Grid Infrastructure software home
crsctl manages clusterware-related operations:
srvctl manages Oracle resource–related operations:
To determine the location of the voting disk write the following command on Linux terminal as Root User:
# crsctl query css votedisk
Disk Group Type | Supported MirroringLevels | Default Mirroring Level |
External redundancy | Unprotected (None) | Unprotected (None) |
Normal redundancy | Two-wayThree-way
Unprotected (None) |
Two-way |
High redundancy | Three-way | Three-way |
ASM can use variable size data extents to support larger files, reduce memory requirements, and improve performance.
Each data extent resides on an individual disk.
Data extents consist of one or more allocation units.
The data extent size is:
ASM stripes files using extents with a coarse method for load balancing or a fine method to reduce latency.
ASM imposes the following limits:
To determine the list of interfaces available to the cluster:
$ oifcfg iflist –p -n
To determine the public and private interfaces that have been configured:
$ oifcfg getif
To determine the Virtual IP (VIP) host name, VIP address, VIP subnet mask, and VIP interface name:
$ srvctl config nodeapps -a
To add a SCAN VIP resource:
$ srvctl add scan -n cluster01-scan
To remove Clusterware resources from SCAN VIPs:
$ srvctl remove scan [-f]
To add a SCAN listener resource:
$ srvctl add scan_listener
$ srvctl add scan_listener -p 1521
To remove Clusterware resources from all SCAN listeners:
$ srvctl remove scan_listener [-f]
Rebalance time is heavily driven by the three items:
Given that the new and old storage are both visible to ASM, simply add the new disks to the ASM disk group and drop the old disks. ASM rebalance will migrate data online.
Note 428681.1 covers how to move OCR/Voting disks to the new storage array
No, Cross-platform disk group migration not supported. To move datafiles between endian-ness platforms, you need to use XTTS, Datapump or Streams.
It works great! Multipathing software is at a layer lower than ASM, and thus is transparent.
You may need to adjust ASM_DISKSTRING to specify only the path to the multipathing pseudo devices.
http://dev.oraclesolutions.pk/real-application-clusterrac-interview-questions-part-4/
http://dev.oraclesolutions.pk/real-application-clusterrac-interview-questions-part-3/
http://dev.oraclesolutions.pk/real-application-clusterrac-interview-questions-part-2/
http://dev.oraclesolutions.pk/real-application-clusterrac-interview-questions-part-2/
http://dev.oraclesolutions.pk/real-application-clusterrac-interview-questions-part-1/
‘crsctl’ command from Root or Oracle user can be used to check the clusterware health ,while for starting or stopping we have to use Root user or any privilege user.
$ crsctl check crs
To change the VIP (virtual IP) on a RAC node, use the command:
$ srvctl modify nodeapps -A new_address
ACMS stands for Atomic Controlfile Memory Service.
In an Oracle RAC environment ACMS is an agent that ensures a distributed SGA memory update, (i.e.) SGA updates are globally committed on success or globally aborted in event of a failure.
No, crossover cables are not supported with Oracle Clusterware interconnects.
No,it can be used only for Oracle database 11g releases(from 11.1).
We need to stop and delete the instance in the node first in interactive or silent mode. After that ASM can be removed using srvctl tool as follows:
srvctl stop asm -n node_name
srvctl remove asm -n node_name
We can verify if ASM has been removed by issuing the following command:
srvctl config asm -n node_name
All Rights Reserved