grep shm /etc/system
get Memory
prtconf | head -3 |grep Memget HW
uname -X
Display number of CPU’s: psrinfo -v|grep "Status of processor"|wc -l
RAM Size in Solaris: prtconf|grep -i mem
prtconf | head -3 |grep Memget HW
SQL >SELECT Table_A.letter, Table_B.letter
2 FROM Table_A, Table_B
3 WHERE Table_A.letter = Table_B.letter;
LETTER LETTER
---------- ----------
A A
SQL >SELECT Table_A.letter, Table_B.letter
2 FROM Table_A INNER JOIN Table_B
3 ON Table_A.letter = Table_B.letter;
LETTER LETTER
---------- ----------
A A
SQL >SELECT A1.letter, A2.letter
2 FROM Table_A A1, Table_A A2
3 WHERE A1.letter = A2.letter;
LETTER LETTER
---------- ----------
A A
B B
SQL >SELECT A1.letter, A2.letter
2 FROM Table_A A1 INNER JOIN Table_A A2
3 ON A1.letter = A2.letter;
LETTER LETTER
---------- ----------
A A
B B
SQL >SELECT Table_A.letter, Table_B.letter
2 FROM Table_A, Table_B
3 WHERE Table_A.letter = Table_B.letter(+);
LETTER LETTER
---------- ----------
A A
B
SQL >SELECT Table_A.letter, Table_B.letter
2 FROM Table_A LEFT OUTER JOIN Table_B
3 ON Table_A.letter = Table_B.letter;
LETTER LETTER
---------- ----------
A A
B
SQL >SELECT Table_A.letter, Table_B.letter
2 FROM Table_A, Table_B
3 WHERE Table_A.letter(+) = Table_B.letter;
LETTER LETTER
---------- ----------
A A
C
SQL >SELECT Table_A.letter, Table_B.letter 2 FROM Table_A RIGHT OUTER JOIN Table_B
3 ON Table_A.letter = Table_B.letter;
LETTER LETTER
---------- ----------
A A
C
SQL >SELECT Table_A.letter, Table_B.letter
2 FROM Table_A, Table_B
3 WHERE Table_A.letter = Table_B.letter(+)
4 UNION
5 SELECT Table_A.letter, Table_B.letter
6 FROM Table_A, Table_B
7 WHERE Table_A.letter(+) = Table_B.letter;
LETTER LETTER
---------- ----------
A A
B
C
SQL >SELECT Table_A.letter, Table_B.letter
2 FROM Table_A FULL OUTER JOIN Table_B
3 ON Table_A.letter = Table_B.letter;
LETTER LETTER
---------- ----------
A A
B
C
SQL >SELECT Table_A.letter, Table_B.letter
2 FROM Table_A, Table_B;
LETTER LETTER
---------- ----------
A A
A C
B A
B C
SQL >SELECT Table_A.letter, Table_B.letter
2 FROM Table_A CROSS JOIN Table_B;
LETTER LETTER
---------- ----------
A A
A C
B A
B C
Reference Document dbasupport.com
select * from dba_objects where object_name = 'AD_BUGS';
Oracle Clusterware enables servers in an Oracle database Real Application Cluster to coordinate simultaneous workload on the same database files. The crsctl command provides administrators many useful capabilities. For example, with crsctl, you can check Clusterware health disable/enable Oracle Clusterware startup on boot, find information on the voting disk and check the Clusterware version, and more.
1. Do you want to check the health of the Clusterware?
# crsctl check crs
CSS appears healthy
CRS appears healthy
EVM appears healthy
2. Do you want to reboot a node for maintenance without Clusterware coming up on boot?
## Disable clusterware on machine2 bootup:
# crsctl disable crs
## Stop the database then stop clusterware processes:
# srvctl stop instance –d db –i db2
# crsctl stop crs
# reboot
## Enable clusterware on machine bootup:
# crsctl enable crs
# crsctl start crs
# srvctl start instance –d db –i db2
3. Do you wonder where your voting disk is?
# crsctl query css votedisk
0. 0 /dev/raw/raw2
Stop all listeners and other processes running in the Oracle home directory, where you need to install the patch set.
Note: If you shut down ASM instances, you must first shut down all database instances that use ASM, even if these databases run from different Oracle homes. |
If you are upgrading a single instance installation, shut down the following Oracle Database 10g processes before installing the patch set:
Note: You must perform these steps in the order listed. |
Shut down all processes in the Oracle home that might be accessing a database, for example Oracle Enterprise Manager Database Control or iSQL*Plus.
Note: Before you shutdown all processes that are monitored by Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime rather than an unplanned system outage. |
Shut down all database instances running in the Oracle home directory, where you need to install the patch set.
Shut down the ASM instance, if the ASM instance is running in the Oracle home directory, where you need to install the patch set.
Shut down all listeners running in the Oracle home directory, where you need to install the patch set.
Shut down the Oracle Cluster Synchronization Services (CSS) daemon as the root
user:
# oracle_home/bin/crsctl stop crs
If you are upgrading an Oracle Clusterware installation, shut down the following Oracle Database 10g processes before installing the patch set:
Note: You must perform these steps in the order listed. |
Shut down all processes in the Oracle home on each node that might be accessing a database, for example Oracle Enterprise Manager Database Control.
Note: Before you shutdown all processes that are monitored by Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime rather than an unplanned system outage. |
Shut down all RAC instances on all nodes. To shut down all RAC instances for a database, enter the following command where db_name
is the name of the database:
$ oracle_home/bin/srvctl stop database -d db_name -i inst_name
Shut down all ASM instances on all nodes. To shut down an ASM instance, enter the following command where node
is the name of the node where the ASM instance is running:
$ oracle_home/bin/srvctl stop asm -n node
Stop all node applications on all nodes. To stop node applications running on a node, enter the following command where node
is the name of the node where the applications are running:
$ oracle_home/bin/srvctl stop nodeapps -n node
Shut down the Oracle Clusterware process by entering the following command on all nodes as the root
user:
# crs_home/bin/crsctl stop crs
Note: In these examples,crs_home is the Oracle Clusterware home directory where the Oracle Clusterware 10g installation that you want to upgrade is installed. |
Note: If the Oracle Clusterware installation is not on a shared Oracle home you can upgrade the Oracle Clusterware installation one node at a time. To do this, perform the preceding steps only on the first node that you are upgrading, then follow the instructions on the installer screen. |
If you are upgrading a RAC installation, shut down the following Oracle Database 10g processes before installing the patch set:
Note: You must perform these steps in the order listed. |
Shut down all processes in the Oracle home on each node that might be accessing a database, for example Oracle Enterprise Manager Database Control.
Note: Before you shutdown all processes that are monitored by Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime rather than an unplanned system outage. |
Shut down all RAC instances on the nodes, which run from the Oracle home on which you are going to apply the patch set. To shut down all RAC instances for a database, enter the following command where db_name
is the name of the database:
$ oracle_home/bin/srvctl stop database -d db_name
Shut down all ASM instances on all nodes. To shut down an ASM instance, enter the following command where node
is the name of the node where the ASM instance is running:
$ oracle_home/bin/srvctl stop asm -n node
Stop any listeners that are running from the Oracle home that you are patching on all nodes. To stop the listener running on a node, enter the following command, where node
is the name of the node where the listener is running:
$ oracle_home/bin/srvctl stop listener -n node [-l listenername]
select start_scnw, start_scnb from v$transaction;
alter system checkpoint;
select CONTROLFILE_CHANGE# from v$database;
select dbms_flashback.get_system_change_number flashback_scn from v$database;
SELECT dbms_flashback.get_system_change_number FROM dual;
alter system checkpoint;
alter system flush buffer_cache;
alter system flush buffer_pool;
alter system quiesce restricted;
alter system suspend|resume;
alter system switch logfile;