crs_stat |
crsctl check cluster -allcrsctl stat res -t |
crs_register |
crsctl add resourcecrsctl add typecrsctl modify resourcecrsctl modify type |
crs_unregister |
crsctl stop resourcecrsctl modify resource resource_name -attr "AUTO_START=never" |
crs_start |
crsctl start resourcecrsctl start crscrsctl start cluster |
crs_stop |
crsctl stop resourcecrsctl stop crscrsctl stop cluster |
crs_getperm |
crsctl getperm resourcecrsctl getperm type |
crs_profile |
crsctl add resourcecrsctl add typecrsctl status resourcecrsctl status typecrsctl modify resourcecrsctl modify type |
crs_relocate |
crsctl relocate resource |
crs_setperm |
crsctl setperm resourcecrsctl setperm type |
crsctl check crsd |
crsctl check crs |
crsctl check cssd |
crsctl check css |
crsctl check evmd |
crsctl check evm |
crsctl debug res log resource_name:level |
crsctl set log |
crsctl set css votedisk |
crsctl add css votediskcrsctl delete css votediskcrsctl query css votediskcrsctl replace css votedisk |
crsctl start resources |
crsctl start resource -all |
crsctl stop resources |
crsctl stop resource -all
http://docs.oracle.com/cd/E11882_01/rac.112/e16794/crsref.htm#autoId61 |
Having 17 year of experince in variety of field including 14 year as IT and As a Oracle DBA Having 7 year of Experince With PT , Backup and Recovery , Database Migration (sql to ORACLE ),Creating Stand By Database. New Projects Installation. Have experice in any kind of Trouble shooting in Database. Knowledge of RAC and Dataguard. Financial prospective of projects and cost reduction
Friday, May 24, 2013
CRSCTL command for RAC Cluster Service
Friday, May 3, 2013
Thursday, May 2, 2013
query For No of sql_id execution ans Hash Value in Oracle
set lines 155
col execs for 999,999,999
col avg_etime for 999,999.999
col avg_lio for 999,999,999.9
col begin_interval_time for a30
col node for 99999
break on plan_hash_value on startup_time skip 1
select ss.snap_id, ss.instance_number node, begin_interval_time, sql_id, plan_hash_value,nvl(executions_delta,0) execs,
(elapsed_time_delta/decode(nvl(executions_delta,0),0,1,executions_delta))/1000000 avg_etime,
(buffer_gets_delta/decode(nvl(buffer_gets_delta,0),0,1,executions_delta)) avg_lio
from DBA_HIST_SQLSTAT S, DBA_HIST_SNAPSHOT SS
where sql_id = nvl('&sql_id','gzxwajs4zqpmb')
and ss.snap_id = S.snap_id
and ss.instance_number = S.instance_number
and executions_delta > 0
order by 1, 2, 3
/
select DBMS_SQLTUNE.REPORT_SQL_MONITOR(type=>'HTML',report_level=>'ALL',sql_id=>'gzxwajs4zqpmb') as report FROM dual;
col execs for 999,999,999
col avg_etime for 999,999.999
col avg_lio for 999,999,999.9
col begin_interval_time for a30
col node for 99999
break on plan_hash_value on startup_time skip 1
select ss.snap_id, ss.instance_number node, begin_interval_time, sql_id, plan_hash_value,nvl(executions_delta,0) execs,
(elapsed_time_delta/decode(nvl(executions_delta,0),0,1,executions_delta))/1000000 avg_etime,
(buffer_gets_delta/decode(nvl(buffer_gets_delta,0),0,1,executions_delta)) avg_lio
from DBA_HIST_SQLSTAT S, DBA_HIST_SNAPSHOT SS
where sql_id = nvl('&sql_id','gzxwajs4zqpmb')
and ss.snap_id = S.snap_id
and ss.instance_number = S.instance_number
and executions_delta > 0
order by 1, 2, 3
/
select DBMS_SQLTUNE.REPORT_SQL_MONITOR(type=>'HTML',report_level=>'ALL',sql_id=>'gzxwajs4zqpmb') as report FROM dual;
Wednesday, May 1, 2013
SRVCTL Command Help in Oracle
gdcbs320%%=====$CRS_HOME/bin/srvctl -h
Usage: srvctl [-V]
Usage: srvctl add database -d -o [-m ] [-p ] [-A ip>/netmask] [-r {PRIMARY
PHYSICAL_STANDBY
LOGICAL_STANDBY}] [-s] [-n ] [-y {AUTOMATIC
MANUAL}]
Usage: srvctl add instance -d -i -n
Usage: srvctl add service -d -s -r "" [-a ""] [-P ]
Usage: srvctl add service -d -s -u {-r ""
-a ""}
Usage: srvctl add nodeapps -n -o -A ip>/netmask[/if1[
if2
...]]
Usage: srvctl add asm -n -i -o [-p ]
Usage: srvctl config database
Usage: srvctl config database -d [-a] [-t]
Usage: srvctl config service -d [-s ] [-a] [-S ]
Usage: srvctl config nodeapps -n [-a] [-g] [-o] [-s] [-l]
Usage: srvctl config asm -n
Usage: srvctl config listener -n
Usage: srvctl disable database -d
Usage: srvctl disable instance -d -i ""
Usage: srvctl disable service -d -s "" [-i ]
Usage: srvctl disable asm -n [-i ]
Usage: srvctl enable database -d
Usage: srvctl enable instance -d -i ""
Usage: srvctl enable service -d -s "" [-i ]
Usage: srvctl enable asm -n [-i ]
Usage: srvctl getenv database -d [-t ""]
Usage: srvctl getenv instance -d -i [-t ""]
Usage: srvctl getenv service -d -s [-t ""]
Usage: srvctl getenv nodeapps -n [-t ""]
Usage: srvctl modify database -d [-n ] [-m ] [-p ] [-r {PRIMARY
PHYSICAL_STANDBY
LOGICAL_STANDBY}] [-s] [-y {AUTOMATIC
MANUAL}]
Usage: srvctl modify instance -d -i -n
Usage: srvctl modify instance -d -i {-s
-r}
Usage: srvctl modify service -d -s -i -t [-f]
Usage: srvctl modify service -d -s -i -r [-f]
Usage: srvctl modify service -d -s -n -i [-a ] [-f]
Usage: srvctl modify asm -n -i [-o ] [-p ]
Usage: srvctl relocate service -d -s -i -t [-f]
Usage: srvctl remove database -d [-f]
Usage: srvctl remove instance -d -i [-f]
Usage: srvctl remove service -d -s [-i ] [-f]
Usage: srvctl remove nodeapps -n "" [-f]
Usage: srvctl remove asm -n [-i ] [-f]
Usage: srvctl setenv database -d {-t =[,=,...]
-T=}
Usage: srvctl setenv instance -d [-i ] {-t "=[,=,...]"
-T "="}
Usage: srvctl setenv service -d [-s ] {-t "=[,=,...]"
-T "="}
Usage: srvctl setenv nodeapps -n {-t "=[,=,...]"
-T "="}
Usage: srvctl start database -d [-o ]
Usage: srvctl start instance -d -i "" [-o ]
Usage: srvctl start service -d [-s "" [-i ]] [-o ]
Usage: srvctl start nodeapps -n
Usage: srvctl start asm -n [-i ] [-o ]
Usage: srvctl start listener -n [-l ]
Usage: srvctl status database -d [-f] [-v] [-S ]
Usage: srvctl status instance -d -i "" [-f] [-v] [-S ]
Usage: srvctl status service -d [-s ""] [-f] [-v] [-S ]
Usage: srvctl status nodeapps -n
Usage: srvctl status asm -n
Usage: srvctl stop database -d [-o ]
Usage: srvctl stop instance -d -i "" [-o ]
Usage: srvctl stop service -d [-s "" [-i ]] [-f]
Usage: srvctl stop nodeapps -n [-r]
Usage: srvctl stop asm -n [-i ] [-o ]
Usage: srvctl stop listener -n [-l ]
Usage: srvctl unsetenv database -d -t ""
Usage: srvctl unsetenv instance -d [-i ] -t ""
Usage: srvctl unsetenv service -d [-s ] -t ""
Usage: srvctl unsetenv nodeapps -n -t ""
Usage: srvctl [-V]
Usage: srvctl add database -d
PHYSICAL_STANDBY
LOGICAL_STANDBY}] [-s
MANUAL}]
Usage: srvctl add instance -d
Usage: srvctl add service -d
Usage: srvctl add service -d
-a "
Usage: srvctl add nodeapps -n
if2
...]]
Usage: srvctl add asm -n
Usage: srvctl config database
Usage: srvctl config database -d
Usage: srvctl config service -d
Usage: srvctl config nodeapps -n
Usage: srvctl config asm -n
Usage: srvctl config listener -n
Usage: srvctl disable database -d
Usage: srvctl disable instance -d
Usage: srvctl disable service -d
Usage: srvctl disable asm -n
Usage: srvctl enable database -d
Usage: srvctl enable instance -d
Usage: srvctl enable service -d
Usage: srvctl enable asm -n
Usage: srvctl getenv database -d
Usage: srvctl getenv instance -d
Usage: srvctl getenv service -d
Usage: srvctl getenv nodeapps -n
Usage: srvctl modify database -d
PHYSICAL_STANDBY
LOGICAL_STANDBY}] [-s
MANUAL}]
Usage: srvctl modify instance -d
Usage: srvctl modify instance -d
-r}
Usage: srvctl modify service -d
Usage: srvctl modify service -d
Usage: srvctl modify service -d
Usage: srvctl modify asm -n
Usage: srvctl relocate service -d
Usage: srvctl remove database -d
Usage: srvctl remove instance -d
Usage: srvctl remove service -d
Usage: srvctl remove nodeapps -n "
Usage: srvctl remove asm -n
Usage: srvctl setenv database -d
-T
Usage: srvctl setenv instance -d
-T "
Usage: srvctl setenv service -d
-T "
Usage: srvctl setenv nodeapps -n
-T "
Usage: srvctl start database -d
Usage: srvctl start instance -d
Usage: srvctl start service -d
Usage: srvctl start nodeapps -n
Usage: srvctl start asm -n
Usage: srvctl start listener -n
Usage: srvctl status database -d
Usage: srvctl status instance -d
Usage: srvctl status service -d
Usage: srvctl status nodeapps -n
Usage: srvctl status asm -n
Usage: srvctl stop database -d
Usage: srvctl stop instance -d
Usage: srvctl stop service -d
Usage: srvctl stop nodeapps -n
Usage: srvctl stop asm -n
Usage: srvctl stop listener -n
Usage: srvctl unsetenv database -d
Usage: srvctl unsetenv instance -d
Usage: srvctl unsetenv service -d
Usage: srvctl unsetenv nodeapps -n
Find Session Generating a lot of REDO in Oracle
Archive logs [ID 167492.1]
To find sessions generating lots of redo, you can use either of the following
methods. Both methods examine the amount of undo generated. When a transaction
generates undo, it will automatically generate redo as well.
The methods are:
1) Query V$SESS_IO. This view contains the column BLOCK_CHANGES which indicates
how much blocks have been changed by the session. High values indicate a
session generating lots of redo.
The query you can use is:
SQL> SELECT s.sid, s.serial#, s.username, s.program,
2 i.block_changes
3 FROM v$session s, v$sess_io i
4 WHERE s.sid = i.sid
5 ORDER BY 5 desc, 1, 2, 3, 4;
Run the query multiple times and examine the delta between each occurrence
of BLOCK_CHANGES. Large deltas indicate high redo generation by the session.
2) Query V$TRANSACTION. This view contains information about the amount of
undo blocks and undo records accessed by the transaction (as found in the
USED_UBLK and USED_UREC columns).
The query you can use is:
SQL> SELECT s.sid, s.serial#, s.username, s.program,
2 t.used_ublk, t.used_urec
3 FROM v$session s, v$transaction t
4 WHERE s.taddr = t.addr
5 ORDER BY 5 desc, 6 desc, 1, 2, 3, 4;
Run the query multiple times and examine the delta between each occurrence
of USED_UBLK and USED_UREC. Large deltas indicate high redo generation by
the session.
You use the first query when you need to check for programs generating lots of
redo when these programs activate more than one transaction. The latter query
can be used to find out which particular transactions are generating redo.
To find sessions generating lots of redo, you can use either of the following
methods. Both methods examine the amount of undo generated. When a transaction
generates undo, it will automatically generate redo as well.
The methods are:
1) Query V$SESS_IO. This view contains the column BLOCK_CHANGES which indicates
how much blocks have been changed by the session. High values indicate a
session generating lots of redo.
The query you can use is:
SQL> SELECT s.sid, s.serial#, s.username, s.program,
2 i.block_changes
3 FROM v$session s, v$sess_io i
4 WHERE s.sid = i.sid
5 ORDER BY 5 desc, 1, 2, 3, 4;
Run the query multiple times and examine the delta between each occurrence
of BLOCK_CHANGES. Large deltas indicate high redo generation by the session.
2) Query V$TRANSACTION. This view contains information about the amount of
undo blocks and undo records accessed by the transaction (as found in the
USED_UBLK and USED_UREC columns).
The query you can use is:
SQL> SELECT s.sid, s.serial#, s.username, s.program,
2 t.used_ublk, t.used_urec
3 FROM v$session s, v$transaction t
4 WHERE s.taddr = t.addr
5 ORDER BY 5 desc, 6 desc, 1, 2, 3, 4;
Run the query multiple times and examine the delta between each occurrence
of USED_UBLK and USED_UREC. Large deltas indicate high redo generation by
the session.
You use the first query when you need to check for programs generating lots of
redo when these programs activate more than one transaction. The latter query
can be used to find out which particular transactions are generating redo.
Subscribe to:
Comments (Atom)