ASM剖析(7)-Active Change Directory
文章转载链接:http://www.killdb.com/2013/01/16/oracle-asm剖析系列7-active-change-directory.html
ASM剖析(1)-disk header
文章转载链接:http://www.killdb.com/2013/01/07/oracle-asm-剖析系列1.html
oracle 10.2.0.5 版本之后 asm disk header 自动备份机制
在10.2.0.5 版本之前 ASM disk header没有自动备份,需要手动执行kfed read或者dd来备份,从10.2.0.5 之后 开始ASM disk header会自动备份到第一个AU#1的倒数第二个block。AU size是1MB的DISKGROUP,每个AU包括block数量=1024KB/4KB=256个,因此备份信息位于AU#1的第254号blockAU size是2MB的DISKGROUP,每...
oracle 12c R2 new feature dataguard 密码会自动同步
在oracle 12cR2 版本 dataguard中,如果你修改了主库的密码,备库的密码会自动同步 不像12cR2 以前版本,需要手工拷贝
RHEL6配置本地yum源
进入yum配置目录# cd /etc/yum.repos.d/添加如下内容# vim rhel-local.repo---[rhel-local]name=Red Hat Enterprise Linux $releasever - $basearch - Source #自定义名称baseurl=file:///mnt/cdrom/ #本地光盘挂载路径 enabled=1 #检查GPG-KEY,0为不检查,1为检查gpgcheck=0 #启用yu...
ASM AMDU工具使用
AMDU是ORACLE针对ASM开发的源数据转储工具,其全称为ASM Metadata Dump Utility(AMDU) AMDU具体以下三个主要功能: 1. 将ASM DISK上的元数据转储到文件系统上以便分析 2. 将ASM文件的内容抽取出来并写入到OS文件系统,Diskgroup是否mount均可 3. 打印出块的元数据,以块中C语言结构或16进制的形...
Datauard 实施架构-metalink介绍的两种方案
单实例MAA方案 MOS上的文档MAA - Creating a Single Instance Physical Standby for a RAC Primary (文档 ID 387339.1)RACMAA方案 MAA - Creating a RAC Physical Standby for a RAC Primary [文章 ID 380449.1][@more@]
RDBMS 数据库补丁集补丁号码快速参考
RDBMS 数据库补丁集补丁号码快速参考 (需要注意的是,一下的补丁集属于RDBMS,即DATABASE的补丁集,没有包括GI的补丁集)[@more@]补丁集/PSU补丁号码描述11.2.0.3.716619892DATABASE PATCH SET UPDATE 11.2.0.3.7 (INCLUDES CPUJUL2013)11.2.0.3.616056266DATABASE PATCH SET UPDATE 11.2.0.3.6 (INCLUDES CPUAPR2013) 11.2.0.3.514727310DATABASE PATCH SET UPDATE 11.2.0.3.5 (INCLUDES CPUJAN2013):11.2.0.3.414275605DATABASE PATCH SET UPDATE 11.2.0.3.4 (INCLUDES CPUOCT2012)11.2.0.3.313923374DATABASE PATCH SET UPDATE 11.2.0.3.
Buffer Cache Hit Ratio Is Not Everything
Buffer Cache Hit Ratio Is Not Everything[@more@]For example, suppose two applications (A and B) return the same result set. Application Ahas a cache hit ratio of 99%, whereas Application B has a hit ratio of 60 %. Whichapplication has the best performance? On further investigation you notice that ApplicationA requires 100,000 logical reads and 1,000 physical reads, whereas Application B has 100logical reads and 40 physical reads. Which application is better tuned now? With theadditional informat
SQL Tuning Advisor
SQL Tuning Advisor 数据库环境:oracle11gr2 数据库用户OE下面的表prootab数据量150万条记录数,执行全表扫描。 [@more@]1. 要访问SQL tuning advisor API,必须给一个用户授予 ADVISOR权限。 CONN sys/password AS SYSDBA GRANT ADVISOR TO dbmaintain; CONN dbmaintain/dbmaintain 2. 使用dbms_sqltune.create_tunning_task创建优化任务 SET SERVEROUTPUT ON -- Tuning task created for specific a statement from the AWR. --从AWR指定一个语句(SQL_ID)为了创建调优任务. DECLARE l_sql_tune_task_id VARCHAR2(100); BEGIN l_sql_tun
OGG-COLMAP-列映射
演示OGG 使用COLMAP进行列的映射功能[@more@]COLMAP--列映射源端表结构如下:SQL> desc gis_test.baobao14;Name Type Nullable Default Comments ----- ------------ -------- ------- -------- PXID NUMBER FANG VARCHAR2(10) Y TDD VARCHAR2(20) Y AWR VARCHAR2(15) Y TNAME VARCHAR2(20) Y 目标端表结构如下:SQL> desc gis_test.baobao14;Name Type Nullable Default Comments ----- -----
defgen
在业务上,对golendgate有这样的需求,源端的表的结构与目标端的结构不相同,表名称相同,但是表的字段不一样.我这里的举例是源端表的字段个数与目标端的字段个数不相同,目标端的表的字段个数是源端表的字段的子集.比如,源端表的字段为30个字段,而目标端的字段为源端的子集,有10个字段,只同步这10个字段的数据。其实,就是对某些敏感的数据不进行同步而已。今天因为业务上有这个需求,就翻照golendgate文档进程操作,操作成功,满足了业务的需求。我这里分享一下这个案例,创建一个表进行举例:[@more@]defgen源端:1.表结构SQL>
decode
写了一个抓取造成等待事件的SQL,里面应用到DECODE.记录一下。[@more@]select /*+ ORDERED */ sql_text, hash_value, address from v$sqltext c, (select sql_hash_value, sql_address from (select DECODE(sql_hash_value, 0, prev_hash_value, sql_hash_value) sql_hash_value, DECODE(sql_hash_value, 0, prev_sql_addr, sql_address) sql_address from v$session --
小知识:所谓“重构CR块”的含义
数据库在进行一致性读取的时候,有时候需要重构CR块,到底这个重构CR块是什么意思,以下是我个人的理解:[@more@]所谓“重构CR块”的含义:众所周知,undo段里存储DML数据是这样的:对于insert语句,undo段保存的是其rowid;对于delete语句,undo段里是保存的是整行删除记录;对于update语句,undo里保存的是更新前该字段的旧数据.那么,在进行一致性读取数据的时候,如果需要重构CR块:对于insert,使用删除rowid重构CR块数据;对于delete,使用插入重构CR块数据;对于update,使用更新把旧数据重构CR块数据。
ORACLE数据库主键与外键的三种关系
1. No action on deletion or update(在删除或更新时候,没有任何动作.)2.Cascading deletions(级联删除)3. Deletions that set null(删除设置为空值)[@more@]1. No action on deletion or update(在删除或更新时候,没有任何动作.)create table t3 (id int primary key,mname varchar2(20));create table t4 (xid number,id int,text varchar2(20),constraint pk_xid primary key (xid),constraint fk_id_t4 foreign key (id) references test.t3(id));select owner,constraint_name,constraint_type,r_owner,r_constraint_name,
Recompilation occurs automatically when the invalid dependent object is referenced.
在阅读oracle administartor 的时候,在读到依赖对象的时候,发现一段话比较绕口,“Recompilation occurs automatically when the invalid dependent object is referenced.”[@more@]我是这样理解的:当无效的依赖对象是被引用的时候,重编译将自动发生。过程如下: A对象依赖于B对象,A对象成为依赖对象;B对象成为引用对象。 当B对象发生改变的时候,A对象失效(比方说,修改字段,将数据类型从number修改为varchar2类型等),但是A对象被C对象引用的时候,A对象将自动变成有效,因为数据库内部跟踪对象的依赖关系的进程自动对A对象
ORA-00600: internal error code, arguments: [kkslrpl1], [8], [], [], [], [], [], []
ORA-600: [kkslrpl1], [8] [ID 987963.1][@more@] In this Document Symptoms Changes Cause Solution ReferencesApplies to: Oracle Server - Enterprise Edition - Version: 9.2.0.1 to 9.2.0.8 - Release: 9.2 to 9.2Information in this document applies to any platform.SymptomsAlert log reports ORA-600 [kkslrpl1] when literal replacement (cursor_sharing ) is being used.ALERT LOG---------Errors in file oracle/admin/testdb/udump/testdb_ora_4659.trc:ORA-00600: internal error code, arguments: [kkslrpl1], [8
OGG错误:ERROR: opening port for MGR MGR (Network is unreachable).
GGSCI (oggmiddle) 3> stop mgrManager process is required by other GGS processes.Are you sure you want to stop it (y/n)? ySending STOP request to MANAGER ...ERROR: opening port for MGR MGR (Network is unreachable).[@more@]这个错误是/etc/hosts IP与HOSTNAME不匹配造成的。
ORA-19502: write error on file "/u01/app/oracle/oradata/slog3.rdo", block
ERROR at line 1:ORA-19502: write error on file "/u01/app/oracle/oradata/slog3.rdo", blocknumber 34817 (block size=512)ORA-27072: File I/O errorAdditional information: 4Additional information: 34817Additional information: 1023488[@more@]出现这样的错误,一般是磁盘空间不足了.
ORACLE11G Snapshot Standby Database
ORACLE11G Snapshot Standby Database[@more@]A snapshot standby database is a fully updatable standby database.(snapshot standby database是一个可读写数据库)1. Like a physical or logical standby database, a snapshot standby database receives and archives redo data from a primary database.(类似于普通物理standby数据库,接受主库传送过来的归档)2. Unlike a physical or logical standby database, a snapshot standby database does not apply the redo data that it receives. The redo data received by a snapsh