一、单实例升级先决条件:
1.表空间需求
确保system表空间至少有10M空间可用
2.系统参数:
确保参数SHARED_POOL_SIZE 和 JAVA_POOL_SIZE大于150MB以上,为加快升级速度,在系统内存可用的情况下,可临时调大这2个参数
SQL> SHOW PARAMETER SHARED_POOL_SIZE
SQL> SHOW PARAMETER JAVA_POOL_SIZE
SQL> ALTER SYSTEM SET SHARED_POOL_SIZE=’200M’ SCOPE=spfile;
SQL> ALTER SYSTEM SET JAVA_POOL_SIZE=’200M’ SCOPE=spfile;
二、实施升级
1.关闭需要升级的实例
停止实例
SQL> shutdown immediate
停止与该实例相关的所有后台进程
$ emctl stop dbconsole
$ isqlplusctl stop
$ lsnrctl stop
2.备份Oracle Home 目录及数据库
tar -cvf $ORACLE_BASE /orabak/ –确保Oracle相关的所有配置都位于$ORACLE_BASE目录,如监听等
cp *.dbf con*.ora redo*.log /orabak/ –对数据库实施冷备
3.升级软件
./runIstanller –>oracle 账户
root.sh –>root 账户
4.更新数据字典
SQL> startup upgrade
SQL> spool patch.log
SQL> @?/rdbms/admin/catupgrd.sql –注9i 使用catpatch.sql
SQL> spool off
SQL> !egrep “ORA-|Error” patch.log -i
5.重编译失效对象:
sql>shutdown immediate
sql>startup
SQL>@?/rdbms/admin/utlrp.sql
6.修改兼容性参数
SQL> alter system set compatible=’10.2.0.4.0′ scope=spfile;
7.如果使用了恢复目录,则执行下面的命令
$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;
8.如果升级回退:
SQL> STARTUP DOWNGRADE
SQL> SPOOL downgrade.log
SQL> @catdwgrd.sql(10.2.10运行的是这个,而10.1降级用的是d92000.sql,即dold_release.sql)
SQL>spool off
SQL>shutdown immediate
9.重新启动数据库:
SQL> SHUTDOWN
SQL> STARTUP
$ lsnrctl start
$ isqlplusctl start
$ emctl start dbconsole
10.检查升级后的情况
SQL> col comp_name for a35
SQL> col comp_name for a30
SQL> col version for a10
SQL> select comp_name,version,status from sys.dba_registry;
COMP_NAME VERSION STATUS
———————————– ———- ———————-
Oracle Database Catalog Views 10.2.0.4.0 VALID
Oracle Database Packages and Types 10.2.0.4.0 VALID
Oracle Workspace Manager 10.2.0.4.3 VALID
JServer JAVA Virtual Machine 10.2.0.4.0 VALID
Oracle XDK 10.2.0.4.0 VALID
Oracle Database Java Packages 10.2.0.4.0 VALID
Oracle Expression Filter 10.2.0.4.0 VALID
Oracle Data Mining 10.2.0.4.0 VALID
Oracle Text 10.2.0.4.0 VALID
Oracle XML Database 10.2.0.4.0 VALID
Oracle Rule Manager 10.2.0.4.0 VALID
COMP_NAME VERSION STATUS
———————————– ———- ———————-
Oracle interMedia 10.2.0.4.0 VALID
OLAP Analytic Workspace 10.2.0.4.0 VALID
Oracle OLAP API 10.2.0.4.0 VALID
OLAP Catalog 10.2.0.4.0 VALID
Spatial 10.2.0.4.0 VALID
Oracle Enterprise Manager 10.2.0.4.0 VALID
17 rows selected.
SQL> select * from utl_recomp_errors;
no rows selected
10g新增列方式指定HINT
在9i和以前的版本,索引提示的格式为/*+ index(table_alias) */或/*+ index(table_alias index_name) */,但是在10g中不仅可以通过索引名称来确定HINT的索引,还可以通过指定列名的方式,格式为/*+ index(table_alias (column_names)) */
SQL> create table test_hint 2 as 3 select * from dba_objects; Table created. SQL> create index ind_hint on test_hint(owner,object_type); Index created. SQL> exec dbms_stats.gather_table_stats(user, 'TEST_HINT', 2 method_opt => 'for all indexed columns size 100',cascade=>true); PL/SQL procedure successfully completed. SQL> set autot trace exp SQL> select * from test_hint where owner = 'SYS'; Execution Plan ---------------------------------------------------------- Plan hash value: 11101196 ------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | ------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 23272 | 2113K| 161 (1)| 00:00:02 | |* 1 | TABLE ACCESS FULL| TEST_HINT | 23272 | 2113K| 161 (1)| 00:00:02 | ------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 1 - filter("OWNER"='SYS') SQL> select /*+index(a)*/ * from test_hint a where owner = 'SYS'; Execution Plan ---------------------------------------------------------- Plan hash value: 890897193 ----------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | ----------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 23272 | 2113K| 1122 (1)| 00:00:14 | | 1 | TABLE ACCESS BY INDEX ROWID| TEST_HINT | 23272 | 2113K| 1122 (1)| 00:00:14 | |* 2 | INDEX RANGE SCAN | IND_HINT | 23272 | | 84 (0)| 00:00:02 | ----------------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 2 - access("OWNER"='SYS') SQL> select /*+index(a ind_hint)*/ * from test_hint a where owner = 'SYS'; Execution Plan ---------------------------------------------------------- Plan hash value: 890897193 ----------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | ----------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 23272 | 2113K| 1122 (1)| 00:00:14 | | 1 | TABLE ACCESS BY INDEX ROWID| TEST_HINT | 23272 | 2113K| 1122 (1)| 00:00:14 | |* 2 | INDEX RANGE SCAN | IND_HINT | 23272 | | 84 (0)| 00:00:02 | ----------------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 2 - access("OWNER"='SYS') SQL> select /*+index(a (owner,object_type))*/ * from test_hint a where owner = 'SYS'; Execution Plan ---------------------------------------------------------- Plan hash value: 890897193 ----------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | ----------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 23272 | 2113K| 1122 (1)| 00:00:14 | | 1 | TABLE ACCESS BY INDEX ROWID| TEST_HINT | 23272 | 2113K| 1122 (1)| 00:00:14 | |* 2 | INDEX RANGE SCAN | IND_HINT | 23272 | | 84 (0)| 00:00:02 | ----------------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 2 - access("OWNER"='SYS') --指定和index完全一致的列,走index SQL> select /*+index(a (owner))*/ * from test_hint a where owner = 'SYS'; Execution Plan ---------------------------------------------------------- Plan hash value: 890897193 ----------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | ----------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 23272 | 2113K| 1122 (1)| 00:00:14 | | 1 | TABLE ACCESS BY INDEX ROWID| TEST_HINT | 23272 | 2113K| 1122 (1)| 00:00:14 | |* 2 | INDEX RANGE SCAN | IND_HINT | 23272 | | 84 (0)| 00:00:02 | ----------------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 2 - access("OWNER"='SYS') --指定列和where条件一致,也可以使用该index SQL> select /*+index(a (object_id))*/ * from test_hint a where owner = 'SYS'; Execution Plan ---------------------------------------------------------- Plan hash value: 11101196 ------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | ------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 23272 | 2113K| 161 (1)| 00:00:02 | |* 1 | TABLE ACCESS FULL| TEST_HINT | 23272 | 2113K| 161 (1)| 00:00:02 | ------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 1 - filter("OWNER"='SYS') --虽然是index中的一个列,但是由于不是where条件中,所以不能被使用 SQL> select /*+index(a (owner))*/ * from test_hint a where object_type = 'TABLE'; Execution Plan ---------------------------------------------------------- Plan hash value: 1755360976 ----------------------------------------------------------------------------------------- | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | ----------------------------------------------------------------------------------------- | 0 | SELECT STATEMENT | | 1752 | 159K| 104 (0)| 00:00:02 | | 1 | TABLE ACCESS BY INDEX ROWID| TEST_HINT | 1752 | 159K| 104 (0)| 00:00:02 | |* 2 | INDEX SKIP SCAN | IND_HINT | 1752 | | 25 (0)| 00:00:01 | ----------------------------------------------------------------------------------------- Predicate Information (identified by operation id): --------------------------------------------------- 2 - access("OBJECT_TYPE"='TABLE') filter("OBJECT_TYPE"='TABLE') --指定index的第一列,虽然不在where中,但是还是会使用index --说明:使用/*+ index(table_alias (column_names)) */方式的hint,需要先测试,有可能不能达到预期效果
TOM的SHOW_SPACE过程使用
TOM写了个好工具SHOW_SPACE,这个工具对于Oracle来讲其实就是个存储过程,这个存储过程可以用来分析空间使用情况,有了此工具,就不用再通过写SQL语句来看每条记录或表占用表空间的大小了,使用起来很方便。
create or replace procedure show_space ( p_segname_1 in varchar2, p_owner_1 in varchar2 default user, p_type_1 in varchar2 default 'TABLE', p_space in varchar2 default 'AUTO', p_analyzed in varchar2 default 'Y' ) as p_segname varchar2(100); p_type varchar2(10); p_owner varchar2(30); l_unformatted_blocks number; l_unformatted_bytes number; l_fs1_blocks number; l_fs1_bytes number; l_fs2_blocks number; l_fs2_bytes number; l_fs3_blocks number; l_fs3_bytes number; l_fs4_blocks number; l_fs4_bytes number; l_full_blocks number; l_full_bytes number; l_free_blks number; l_total_blocks number; l_total_bytes number; l_unused_blocks number; l_unused_bytes number; l_LastUsedExtFileId number; l_LastUsedExtBlockId number; l_LAST_USED_BLOCK number; procedure p( p_label in varchar2, p_num in number ) is begin dbms_output.put_line( rpad(p_label,40,'.') || p_num ); end; begin p_segname := upper(p_segname_1); -- rainy changed p_owner := upper(p_owner_1); p_type := p_type_1; if (p_type_1 = 'i' or p_type_1 = 'I') then --rainy changed p_type := 'INDEX'; end if; if (p_type_1 = 't' or p_type_1 = 'T') then --rainy changed p_type := 'TABLE'; end if; if (p_type_1 = 'c' or p_type_1 = 'C') then --rainy changed p_type := 'CLUSTER'; end if; dbms_space.unused_space ( segment_owner => p_owner, segment_name => p_segname, segment_type => p_type, total_blocks => l_total_blocks, total_bytes => l_total_bytes, unused_blocks => l_unused_blocks, unused_bytes => l_unused_bytes, LAST_USED_EXTENT_FILE_ID => l_LastUsedExtFileId, LAST_USED_EXTENT_BLOCK_ID => l_LastUsedExtBlockId, LAST_USED_BLOCK => l_LAST_USED_BLOCK ); if p_space = 'MANUAL' or (p_space <> 'auto' and p_space <> 'AUTO') then dbms_space.free_blocks ( segment_owner => p_owner, segment_name => p_segname, segment_type => p_type, freelist_group_id => 0, free_blks => l_free_blks ); p( 'Free Blocks', l_free_blks ); end if; p( 'Total Blocks', l_total_blocks ); p( 'Total Bytes', l_total_bytes ); p( 'Unused Blocks', l_unused_blocks ); p( 'Unused Bytes', l_unused_bytes ); p( 'Last Used Ext FileId', l_LastUsedExtFileId ); p( 'Last Used Ext BlockId', l_LastUsedExtBlockId ); p( 'Last Used Block', l_LAST_USED_BLOCK ); /*IF the segment is analyzed */ if p_analyzed = 'Y' then dbms_space.space_usage(segment_owner => p_owner , segment_name => p_segname , segment_type => p_type , unformatted_blocks => l_unformatted_blocks , unformatted_bytes => l_unformatted_bytes, fs1_blocks => l_fs1_blocks, fs1_bytes => l_fs1_bytes , fs2_blocks => l_fs2_blocks, fs2_bytes => l_fs2_bytes, fs3_blocks => l_fs3_blocks , fs3_bytes => l_fs3_bytes, fs4_blocks => l_fs4_blocks, fs4_bytes => l_fs4_bytes, full_blocks => l_full_blocks, full_bytes => l_full_bytes); dbms_output.put_line(rpad(' ',50,'*')); dbms_output.put_line('The segment is analyzed'); p( '0% -- 25% free space blocks', l_fs1_blocks); p( '0% -- 25% free space bytes', l_fs1_bytes); p( '25% -- 50% free space blocks', l_fs2_blocks); p( '25% -- 50% free space bytes', l_fs2_bytes); p( '50% -- 75% free space blocks', l_fs3_blocks); p( '50% -- 75% free space bytes', l_fs3_bytes); p( '75% -- 100% free space blocks', l_fs4_blocks); p( '75% -- 100% free space bytes', l_fs4_bytes); p( 'Unused Blocks', l_unformatted_blocks ); p( 'Unused Bytes', l_unformatted_bytes ); p( 'Total Blocks', l_full_blocks); p( 'Total bytes', l_full_bytes); end if; end; /
用法
SQL> create table t 2 as 3 select * from dba_objects; Table created. SQL> set serverout on SQL> exec show_space('T','TEST'); Total Blocks............................768 Total Bytes.............................6291456 Unused Blocks...........................52 Unused Bytes............................425984 Last Used Ext FileId....................4 Last Used Ext BlockId...................1033 Last Used Block.........................76 ************************************************* The segment is analyzed 0% -- 25% free space blocks.............0 0% -- 25% free space bytes..............0 25% -- 50% free space blocks............0 25% -- 50% free space bytes.............0 50% -- 75% free space blocks............0 50% -- 75% free space bytes.............0 75% -- 100% free space blocks...........0 75% -- 100% free space bytes............0 Unused Blocks...........................0 Unused Bytes............................0 Total Blocks............................696 Total bytes.............................5701632 PL/SQL procedure successfully completed. SQL> delete from t; 50602 rows deleted. SQL> exec show_space('T','TEST'); Total Blocks............................768 Total Bytes.............................6291456 Unused Blocks...........................52 Unused Bytes............................425984 Last Used Ext FileId....................4 Last Used Ext BlockId...................1033 Last Used Block.........................76 ************************************************* The segment is analyzed 0% -- 25% free space blocks.............0 0% -- 25% free space bytes..............0 25% -- 50% free space blocks............0 25% -- 50% free space bytes.............0 50% -- 75% free space blocks............0 50% -- 75% free space bytes.............0 75% -- 100% free space blocks...........696 75% -- 100% free space bytes............5701632 Unused Blocks...........................0 Unused Bytes............................0 Total Blocks............................0 Total bytes.............................0 PL/SQL procedure successfully completed. SQL> alter table t move; Table altered. SQL> exec show_space('T','TEST'); Total Blocks............................8 Total Bytes.............................65536 Unused Blocks...........................5 Unused Bytes............................40960 Last Used Ext FileId....................4 Last Used Ext BlockId...................401 Last Used Block.........................3 ************************************************* The segment is analyzed 0% -- 25% free space blocks.............0 0% -- 25% free space bytes..............0 25% -- 50% free space blocks............0 25% -- 50% free space bytes.............0 50% -- 75% free space blocks............0 50% -- 75% free space bytes.............0 75% -- 100% free space blocks...........0 75% -- 100% free space bytes............0 Unused Blocks...........................0 Unused Bytes............................0 Total Blocks............................0 Total bytes.............................0 PL/SQL procedure successfully completed.
ORA-02266: unique/primary keys in table referenced by enabled foreign keys
truncate清空一张表记录发现ORA-02266,进行模拟测试
SQL> truncate table p; truncate table p * ERROR at line 1: ORA-02266: unique/primary keys in table referenced by enabled foreign keys --错误原因 SQL> !oerr ora 02266 02266, 00000, "unique/primary keys in table referenced by enabled foreign keys" // *Cause: An attempt was made to truncate a table with unique or // primary keys referenced by foreign keys enabled in another table. // Other operations not allowed are dropping/truncating a partition of a // partitioned table or an ALTER TABLE EXCHANGE PARTITION. // *Action: Before performing the above operations the table, disable the // foreign key constraints in other tables. You can see what // constraints are referencing a table by issuing the following // command: // SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = "tabnam"; --查询是否有主键或者唯一index SET SERVEROUTPUT ON SET LINESIZE 1000 SET FEEDBACK OFF SET LONG 999999 SET PAGESIZE 1000 EXEC DBMS_METADATA.SET_TRANSFORM_PARAM(DBMS_METADATA.SESSION_TRANSFORM,'STORAGE',false);--不显示存储信息 SQL> SELECT DBMS_METADATA.GET_DDL('TABLE','P') FROM DUAL; DBMS_METADATA.GET_DDL('TABLE','P') -------------------------------------------------------------------------------- CREATE TABLE "CHF"."P" ( "X" NUMBER(*,0), PRIMARY KEY ("X") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 TABLESPACE "USERS" ENABLE ) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING TABLESPACE "USERS --查询主外键关系 SQL> col 主键表名 for a20 SQL> col 主键列名 for a20 SQL> col 外键表名 for a20 SQL> col 外键列名 for a20 SQL> select b.table_name 主键表名, b.column_name 主键列名, a.table_name 外键表名, a.column_name 外键列名 from (select a.constraint_name, b.table_name, b.column_name, a.r_constraint_name from dba_constraints a, dba_cons_columns b WHERE a.constraint_type = 'R' and a.constraint_name = b.constraint_name) a, (select distinct a.r_constraint_name, b.table_name, b.column_name from dba_constraints a, dba_cons_columns b WHERE a.constraint_type = 'R' and a.r_constraint_name = b.constraint_name) b where a.r_constraint_name = b.r_constraint_name and b.table_name='P'; 主键表名 主键列名 外键表名 外键列名 -------------------- -------------------- -------------------- -------------------- P X C X 1 row selected. --处理方法一 SQL> alter table p disable primary key cascade; Table altered. SQL> truncate table p; Table truncated. SQL> alter table p enable primary key; Table altered. --处理方法二 SQL> delete from t; 1 row deleted. SQL> commit; Commit complete.
自治事件引起死锁
今天遇到一个比较特殊的死锁现象,记录下来
DEADLOCK DETECTED ( ORA-00060 ) [Transaction Deadlock] The following deadlock is not an ORACLE error. It is a deadlock due to user error in the design of an application or from issuing incorrect ad-hoc SQL. The following information may aid in determining the deadlock: Deadlock graph: ---------Blocker(s)-------- ---------Waiter(s)--------- Resource Name process session holds waits process session holds waits TX-00090022-000002ba 15 145 X 15 145 X session 145: DID 0001-000F-00000019 session 145: DID 0001-000F-00000019 Rows waited on: Session 145: obj - rowid = 0000E0A3 - AAAOCjAAFAAAAA8AAA (dictionary objn - 57507, file - 5, block - 60, slot - 0) Information on the OTHER waiting sessions: End of information on OTHER waiting sessions. Current SQL statement for this session: UPDATE T SET Y = Y WHERE X = :B1 ----- PL/SQL Call Stack ----- object line object handle number name 0x67987910 4 CHF.T ===================================================
问题原因:自治事件导致(重现)
drop table t; create table t ( x int, y int ); create or replace trigger t before update on t for each row declare pragma autonomous_transaction; begin update t set y = y where x = :new.x; commit; end; / insert into t values ( 1, 1 ); commit; update t set y = y where x = 1;
DUMPING ORACLE BLOCKS
我见识过的,讲的最好的关于dump相关的文章,这个里面关于dump block,dump index,dump controlfile说的比较详细,看了收获不小,现在贡献出来和大家分享
如何阅读oracle数据块的dump文件
http://www.xifenfei.com/wp-content/uploads/2011/09/read_oracle_dump.pdf
假坏块引起恐慌
alert文件出现如下日志
Fri Sep 16 02:58:25 2011
Hex dump of (file 19, block 1444767) in trace file /opt/oracle/admin/ora9i/udump/ora9i_ora_24702.trc
Corrupt block relative dba: 0x04d60b9f (file 19, block 1444767)
Fractured block found during backing up datafile
Data in bad block:
type: 6 format: 2 rdba: 0x04d60b9f
last change scn: 0x0abf.56961827 seq: 0x1 flg: 0x04
spare1: 0x0 spare2: 0x0 spare3: 0x0
consistency value in tail: 0x7c340601
check value in block header: 0xba17
computed block checksum: 0x6413
Reread of blocknum=1444767, file=/opt/oracle/oradata/ora9i/TS_INDX_Base.005.dbf. found valid data
因为这个是我们比较重要的业务服务器,如果出现坏块,不能及时处理,后果将不堪设想,因此我马上检查
先查看是什么对象:(结果是一个分区表的index,担心减少一半,index大不了重建,无大事)
SELECT OWNER, SEGMENT_NAME, SEGMENT_TYPE, TABLESPACE_NAME, A.PARTITION_NAME FROM DBA_EXTENTS A WHERE FILE_ID = &FILE_ID AND &BLOCK_ID BETWEEN BLOCK_ID AND BLOCK_ID + BLOCKS - 1;
然后检查是否真的坏块
方法一:dbv
[oracle@DB1 bdump]$ dbv file=/opt/oracle/oradata/ora9i/TS_INDX_Base.005.dbf blocksize=8192 DBVERIFY: Release 10.2.0.4.0 - Production on Fri Sep 16 09:15:11 2011 Copyright (c) 1982, 2007, Oracle. All rights reserved. DBVERIFY - Verification starting : FILE = /opt/oracle/oradata/ora9i/TS_INDX_Base.005.dbf DBVERIFY - Verification complete Total Pages Examined : 2207744 Total Pages Processed (Data) : 0 Total Pages Failing (Data) : 0 Total Pages Processed (Index): 2201581 Total Pages Failing (Index): 0 Total Pages Processed (Other): 3271 Total Pages Processed (Seg) : 0 Total Pages Failing (Seg) : 0 Total Pages Empty : 2892 Total Pages Marked Corrupt : 0 Total Pages Influx : 0 Highest block SCN : 1454468581 (2751.1454468581)
结论无坏块
方法二:bbed
[oracle@DB1 lib]$ bbed Password: BBED: Release 2.0.0.0.0 - Limited Production on Fri Sep 16 10:01:26 2011 Copyright (c) 1982, 2007, Oracle. All rights reserved. ************* !!! For Oracle Internal Use only !!! *************** BBED> set filename '/opt/oracle/oradata/ora9i/TS_INDX_Base.005.dbf' FILENAME /opt/oracle/oradata/ora9i/TS_INDX_Base.005.dbf BBED> set block 1444767 BLOCK# 1444767 BBED> VERIFY DBVERIFY - Verification starting FILE = /opt/oracle/oradata/ora9i/TS_INDX_Base.005.dbf BLOCK = 1444767 DBVERIFY - Verification complete Total Blocks Examined : 1 Total Blocks Processed (Data) : 0 Total Blocks Failing (Data) : 0 Total Blocks Processed (Index): 1 Total Blocks Failing (Index): 0 Total Blocks Empty : 0 Total Blocks Marked Corrupt : 0 Total Blocks Influx : 0
再次证明无坏块
方法三:rman
RMAN> backup validate datafile 19;
结果查询V$BACKUP_CORRUPTION也无坏块
方法四:使用index查询
结果也正常,没报错,alert中无错误记录
发现alert报错,但是实际没有错误,查询相关资料发现
从日志中可以看到,提示Corrupt的block对应的dba为0x04d60b9f (file 19, block 1444767),data block的类型为6(6为trans data,所有的data和index blocks都是该类型)。Oracle发现block有可能corrupt后,进行了reread,结果为found valid data,说明数据块未损坏。Fractured block found,表示rman发现这个数据块正在被使用,这时rman会进行重新读取,如果再次失败,才认为是坏块。如果第二次尝试读取时成功,则表示数据完好,不会产生影响。此类信息在IO负载较高的情况下进行rman备份时比较容易出现。
查询系统发现,正好该时间段是系统io负载最高的时候
ORA-00600 [ktbdchk1: bad dscn] 解决
启动数据库报错 SQL> startup ORACLE instance started. Total System Global Area 167772160 bytes Fixed Size 1260720 bytes Variable Size 150995792 bytes Database Buffers 8388608 bytes Redo Buffers 7127040 bytes Database mounted. ORA-01092: ORACLE instance terminated. Disconnection forced alert.log导错 Wed Aug 10 12:31:11 2011 Errors in file /u01/admin/xienfei/udump/xff_ora_8568.trc: ORA-00600: internal error code, arguments: [ktbdchk1: bad dscn], [], [], [], [], [], [], [] xff_ora_8568.trc内容 [ktbdchk] -- readers_dsz -- bad dscn scn: 0x0000.b1e60c00scn: 0x0000.0011fca1 *** 2011-08-10 12:31:11.998 ksedmp: internal or fatal error ORA-00600: internal error code, arguments: [ktbdchk1: bad dscn], [], [], [], [], [], [], [] Current SQL statement for this session: select ctime, mtime, stime from obj$ where obj# = :1 根据上面错误判断,错误的scn为b1e60c00,不是整个数据文件的scn错误 而应该是一个对象的scn错误,所以继续在xff_ora_8568.trc文件中查找b1e60c00 找到结果如下: Block header dump: 0x0040007a Object id on Block? Y seg/obj: 0x12 csc: 0x00.b1e60c00 itc: 1 flg: - typ: 1 - DATA fsl: 0 fnx: 0x0 ver: 0x01 Itl Xid Uba Flag Lck Scn/Fsc 0x01 0x0008.02a.000001d9 0x00802341.01bb.04 ---- 1 fsc 0x0000.0011ae7c data_block_dump,data header at 0x20fd6044 =============== tsiz: 0x1fb8 hsiz: 0xea pbl: 0x20fd6044 bdba: 0x0040007a 76543210 flag=-------- ntab=1 nrow=108 frre=-1 fsbo=0xea fseo=0x453 avsp=0x369 tosp=0x369 0xe:pti[0] nrow=108 offs=0 根据这个提示,发现dba为:0040007a的对象异常,查找对应的file_id,block SQL> SELECT DBMS_UTILITY.data_block_address_file (TO_NUMBER ('40007a', 'XXXXXXXX')) file_id, 2 DBMS_UTILITY.data_block_address_block (TO_NUMBER ('40007a', 'XXXXXXXX')) block_id 3 FROM DUAL; FILE_ID BLOCK_ID ---------- ---------- 1 122 使用bbed查看file=1,block=122的scn情况 BBED> p ktbbh struct ktbbh, 48 bytes @20 ub1 ktbbhtyp @20 0x01 (KDDBTDATA) union ktbbhsid, 4 bytes @24 ub4 ktbbhsg1 @24 0x00000012 ub4 ktbbhod1 @24 0x00000012 struct ktbbhcsc, 8 bytes @28 ub4 kscnbas @28 0xb1e60c00 ub2 kscnwrp @32 0x0000 b2 ktbbhict @36 1 ub1 ktbbhflg @38 0x02 (NONE) ub1 ktbbhfsl @39 0x00 ub4 ktbbhfnx @40 0x00000000 struct ktbbhitl[0], 24 bytes @44 struct ktbitxid, 8 bytes @44 ub2 kxidusn @44 0x0008 ub2 kxidslt @46 0x002a ub4 kxidsqn @48 0x000001d9 struct ktbituba, 8 bytes @52 ub4 kubadba @52 0x00802341 ub2 kubaseq @56 0x01bb ub1 kubarec @58 0x04 ub2 ktbitflg @60 0x0001 (NONE) union _ktbitun, 2 bytes @62 b2 _ktbitfsc @62 0 ub2 _ktbitwrp @62 0x0000 ub4 ktbitbas @64 0x0011ae7c 果然发现scn为0xb1e60c00,现在把其修改为:0x00124ac6(注意规则,一般linux下都是倒序) BBED> set offset 28 OFFSET 28 BBED> m /x c64a1200 BBED-00209: invalid number (c64a1200) 小技巧,一次性修改报错,尝试一次修改一点 BBED> m /x c64a File: /u01/oradata/xienfei/system01.dbf (0) Block: 122 Offsets: 28 to 43 Dba:0x00000000 ------------------------------------------------------------------------ c64ae6b1 00000000 01000200 00000000 <32 bytes per line> BBED> set offset +2 OFFSET 30 BBED> m /x 1200 File: /u01/oradata/xienfei/system01.dbf (0) Block: 122 Offsets: 30 to 45 Dba:0x00000000 ------------------------------------------------------------------------ 12000000 00000100 02000000 00000800 <32 bytes per line> BBED> set offset -2 OFFSET 28 BBED> dump File: /u01/oradata/xienfei/system01.dbf (0) Block: 122 Offsets: 28 to 43 Dba:0x00000000 ------------------------------------------------------------------------ c64a1200 00000000 01000200 00000000 <32 bytes per line> BBED> sum apply Check value for File 0, Block 122: current = 0x3a4e, required = 0x3a4e SQL> startup ORACLE instance started. Total System Global Area 167772160 bytes Fixed Size 1260720 bytes Variable Size 150995792 bytes Database Buffers 8388608 bytes Redo Buffers 7127040 bytes Database mounted. Database opened.
cursor: pin S事件
A session waits for “cursor: pin S” when it wants a specific mutex in S (share) mode on a specific cursor and there is no concurrent X holder but it could not acquire that mutex immediately. This may seem a little strange as one might question why there should be any form of wait to get a mutex which has no session holding it in an incompatible mode. The reason for the wait is that in order to acquire the mutex in S mode (or release it) the session has to increment (or decrement) the mutex reference count and this requires an exclusive atomic update to the mutex structure itself. If there are concurrent sessions trying to make such an update to the mutex then only one session can actually increment (or decrement) the reference count at a time. A wait on “cursor: pin S” thus occurs if a session cannot make that atomic change immediately due to other concurrent requests.
Mutexes are local to the current instance in RAC environments.
Oracle10g中引用的mutexes机制一定程度的替代了library cache pin,其结构更简单,get&set的原子操作更快捷。
它相当于,每个child cursor下面都有一个mutexes这样的简单内存结构,当有session要执行该SQL而需要pin cursor操作的时候,session只需要以shared模式set这个内存位+1,表示session获得该mutex的shared mode lock.可以有很多session同时具有这个mutex的shared mode lock;但在同一时间,只能有一个session在操作这个mutext +1或者-1。+1 -1的操作是排它性的原子操作。如果因为session并行太多,而导致某个session在等待其他session的mutext +1/-1操作,则该session要等待cursor: pin S等待事件。
当看到系统有很多session等待cursor: pin S事件的时候,要么是CPU不够快,要么是某个SQL的并行执行次数太多了而导致在child cursor上的mutex操作争用。如果是Capacity的问题,则可以升级硬件。如果是因为SQL的并行太多,则要么想办法降低该SQL执行次数,要么将该SQL复制成N个其它的SQL。
select /*SQL 1*/object_name from t where object_id=?
select /*SQL 2*/object_name from t where object_id=?
select /*SQL …*/object_name from t where object_id=?
select /*SQL N*/object_name from t where object_id=?
这样就有了N个SQL Cursor,N个Mutex内存结构,就将争用分散开来,类似partition的作用了
Oracle常用诊断事件清单
事件 | 说明 | 例子 |
Event 10013 – Monitor Transaction Recovery | 在Startup时跟踪事务恢复 | ALTER SESSION SET EVENTS ’10013 trace name context forever, level 1′; |
Event 10015 – Dump Undo Segment Headers- | 在事务恢复后做Dump回退段头信息 | ALTER SESSION SET EVENTS ’10015 trace name context forever, level 1′; |
Event 10032 – Dump Sort Statistics | Dump排序的统计信息 | ALTER SESSION SET EVENTS ’10032 trace name context forever, level 10′; |
Event 10033 – Dump Sort Intermediate Run Statistics | 排序过程中,内存排序区和临时表空间的交互情况 | ALTER SESSION SET EVENTS ’10033 trace name context forever, level 10′; |
Event 10045 – Trace Free List Management Operations | FREELIST的管理操作 | ALTER SESSION SET EVENTS ’10045 trace name context forever, level 1′; |
Event 10046 – Enable SQL Statement Trace | 跟踪SQL,有执行计划,邦定变量和等待的统计信息,level 12最详细。 | ALTER SESSION SET EVENTS ’10046 trace name context forever, level 12′; LEVEL定义如下: 1:SQL 语句,执行计划和执行状态 4:1的内容加上绑定变量信息 8:1的信息加上等待事件信息 12:1+4+8 |
Event 10053 – Dump Optimizer Decisions | 在分析SQL语句时,Dump出优化器所做的选择,级别level 1最详细 | ALTER SESSION SET EVENTS ’10053 trace name context forever, level 1′; LEVEL定义如下: 1:状态和估算信息 2:只显示估算信息 |
Event 10060 – Dump Predicates | DUMP SQL语句中的断语信息。需要在需要DUMP的用户下创建以下表 CREATE TABLE kkoipt_table (c1 INTEGER, c2 VARCHAR2(80)); 断语信息会写入该表 |
ALTER SESSION SET EVENTS ’10060 trace name context forever, level 1′; |
Event 10065 – Restrict Library Cache Dump Output for State Object Dumps | 限制对象状态DUMP的时候LIBRARY CACHE信息的详细程度 1 Address of library object only 2 As level 1 plus library object lock details 3 As level 2 plus library object handle and library object 缺省是LEVEL 3 |
ALTER SESSION SET EVENTS ’10065 trace name context forever, level level’; |
Event 10079 – Dump SQL*Net Statistics- | Dump SQL*NeT的统计信息 | ALTER SESSION SET EVENTS ’10079 trace name context forever, level 2′; |
Event 10081 – Trace High Water Mark Changes | HWM的改变 | ALTER SESSION SET EVENTS ’10081 trace name context forever, level 1′; |
Event 10104 – Dump Hash Join Statistics | HASH JOIN的统计信息 | ALTER SESSION SET EVENTS ’10104 trace name context forever, level 10′; |
Event 10128 – Dump Partition Pruning Information | 分区表调整信息 | ALTER SESSION SET EVENTS ’10128 trace name context forever, level level’; Level取值: 1 Dump pruning descriptor for each partitioned object 0×0002 Dump partition iterators 0×0004 Dump optimizer decisions about partition-wise joins 0×0008 Dump ROWID range scan pruning information 在9.0.1或者后面的版本,在level 2后还需要建立如下的表: CREATE TABLE kkpap_pruning ( partition_count NUMBER, iterator VARCHAR2(32), partition_level VARCHAR2(32), order_pt VARCHAR2(12), call_time VARCHAR2(12), part# NUMBER, subp# NUMBER, abs# NUMBER ); |
事件 | 说明 | 例子 |
Event 10200 – Dump Consistent Reads | DUMP一致读的信息 | ALTER SESSION SET EVENTS ’10200 trace name context forever, level 1′; |
Event 10201 – Dump Consistent Read Undo Application | DUMP一致性读涉及UNDO信息的内容 | ALTER SESSION SET EVENTS ’10201 trace name context forever, level 1′; |
Event 10220 – Dump Changes to Undo Header | Dump出Undo头信息的改变 | ALTER SESSION SET EVENTS ’10220 trace name context forever, level 1′; |
Event 10221 – Dump Undo Changes | Dump Undo的改变 | ALTER SESSION SET EVENTS ’10221 trace name context forever, level 7′; |
Event 10224 – Dump Index Block Splits / Deletes | 索引块的分裂和D删除信息 | ALTER SESSION SET EVENTS ’10224 trace name context forever, level 1′; |
Event 10225 – Dump Changes to Dictionary Managed Extents | DUMP字段管理的扩展变化 | ALTER SESSION SET EVENTS ’10225 trace name context forever, level 1′; |
Event 10231 | 全表扫描时跳过坏块,在有坏块的情况下做数据拯救时很有用 | ALTER SYSTEM SET EVENTS ’10231 trace name context forever,level 10′; |
Event 10241 – Dump Remote SQL Execution | 远程SQL语句的执行信息 | ALTER SESSION SET EVENTS ’10241 trace name context forever, level 1′; |
Event 10246 – Trace PMON Process | 跟踪PMON进程 | 只能修改参数,不能用ALTER SYSTEM event = “10246 trace name context forever, level 1″ |
Event 10248 – Trace Dispatcher Processes | 跟踪DISPATCHER的工作情况 | event = “10248 trace name context forever, level 10″ |
Event 10249 – Trace Shared Server (MTS) Processes- | 跟踪共享服务器的工作情况 | event = “10249 trace name context forever, level 10″ |
Event 10270 – Debug Shared Cursors | 跟踪共享CURSORS的情况 | event = “10270 trace name context forever, level 10″ |
Event 10299 – Debug Prefetching | 跟踪表数据块和索引数据块的PREFETCHING | event = “10299 trace name context forever, level 1″ |
Event 10357 – Debug Direct Path | ALTER SESSION SET EVENTS ’10357 trace name context forever, level 1′; | |
Event 10390 – Dump Parallel Execution Slave Statistics | 跟踪并行操作中的SLAVE的状态 | ALTER SESSION SET EVENTS ’10390 trace name context forever, level 1; |
Event 10391-Dump Parallel Execution Granule Allocation | 跟踪并行操作的粒度 | ALTER SESSION SET EVENTS ’10391 trace name context forever, level 2′; |
Event 10393 – Dump Parallel Execution Statistics | 跟踪并行操作的状态(每个SLAVE单独列出状态) | ALTER SESSION SET EVENTS ’10393 trace name context forever, level 1′; |
Event 10500 – Trace SMON Process | 跟踪SMON进程 | event = “10500 trace name context forever, level 1″ |
Event 10608 – Trace Bitmap Index Creation | 跟踪BITMAP索引创建的详细过程 | ALTER SESSION SET EVENTS ’10608 trace name context forever, level 10′; |
Event 10704 – Trace Enqueues | 跟踪锁的使用情况 | ALTER SESSION SET EVENTS ’10704 trace name context forever, level 1′; |
Event 10706 – Trace Global Enqueue Manipulation | 跟踪全局锁的使用情况 | ALTER SESSION SET EVENTS ’10706 trace name context forever, level 1′; |
Event 10708 – Trace RAC Buffer Cache | 跟踪RAC环境下的BUFFER CACHE | ALTER SESSION SET EVENTS ’10708 trace name context forever, level 10′; |
事件 | 说明 | 例子 |
Event 10710 – Trace Bitmap Index Access | 跟踪位图索引的访问情况 | ALTER SESSION SET EVENTS ’10710 trace name context forever, level 1′; |
Event 10711 – Trace Bitmap Index Merge Operation | 跟踪位图索引合并操作 | ALTER SESSION SET EVENTS ’10711 trace name context forever, level 1′; |
Event 10712 – Trace Bitmap Index OR Operation | 跟踪位图索引或操作情况 | ALTER SESSION SET EVENTS ’10712 trace name context forever, level 1′; |
Event 10713 – Trace Bitmap Index AND Operation | 跟踪位图索引与操作 | ALTER SESSION SET EVENTS ’10713 trace name context forever, level 1′; |
Event 10714 – Trace Bitmap Index MINUS Operation | 跟踪位图索引minus操作 | ALTER SESSION SET EVENTS ’10714 trace name context forever, level 1′; |
Event 10715 – Trace Bitmap Index Conversion to ROWIDs Operation | 跟踪位图索引转换ROWID操作 | ALTER SESSION SET EVENTS ’10715 trace name context forever, level 1′; |
Event 10716 – Trace Bitmap Index Compress/Decompress | 跟踪位图索引压缩和解压缩情况 | ALTER SESSION SET EVENTS ’10716 trace name context forever, level 1′; |
Event 10717 – Trace Bitmap Index Compaction | ALTER SESSION SET EVENTS ’10717 trace name context forever, level 1′; | |
Event 10719 – Trace Bitmap Index DML | 跟踪位图索引列的DML操作(引起位图索引改变的DML操作) | ALTER SESSION SET EVENTS ’10719 trace name context forever, level 1′; |
Event 10730 – Trace Fine Grained Access Predicates | 跟踪细粒度审计的断语 | ALTER SESSION SET EVENTS ’10730 trace name context forever, level 1′; |
Event 10731 – Trace CURSOR Statements | 跟踪CURSOR的语句情况 | ALTER SESSION SET EVENTS ’10731 trace name context forever, level level’; LEVEL定义 1 Print parent query and subquery 2 Print subquery only |
Event 10928 – Trace PL/SQL Execution | 跟踪PL/SQL执行情况 | ALTER SESSION SET EVENTS ’10928 trace name context forever, level 1′; |
Event 10938 – Dump PL/SQL Execution Statistics | 跟踪PL/SQL执行状态。使用前需要执行rdbms/admin下的tracetab.sql | ALTER SESSION SET EVENTS ’10938 trace name context forever, level 1′; |
flush_cache | 刷新BUFFER CACHE | ALTER SESSION SET EVENTS ‘immediate trace name flush_cache’; |
DROP_SEGMENTS | 手工删除临时段。当这些临时段无法自动清除的时候可以手工清除 | alter session set events ‘immediate trace name DROP_SEGMENTS level ts#+1′; ts#是指要删除临时段的表空间的ts# |