dul 10g版本的使用
dul 10g版本的使用在自己的测试环境下(linux平台)测试下10g dul工具的使用数据库表空间使用的有ASM管理的磁盘组,也有一般的数据文件1)创建表空间create tablespace TBSDATA3 datafile '+DSKGRP1' size 100M;create table testdul (name varchar2(20)) tablespace TBSDATA3;select name,path,total_mb,free_mb,failgroup from v$asm_diskNAME PATH TOTAL_MB FREE_MB FAILGROUP-------------------- ---------------------------------------- ---------- ---------- --------
ORA-00845: MEMORY_TARGET not supported on this system
SQL> startup nomount;ORA-00845: MEMORY_TARGET not supported on this system[root@server ~]# df -k /dev/shmFilesystem 1K-blocks Used Available Use% Mounted onnone 517896 0 517896 0% /dev/shm[root@server ~]# umount /dev/shm[root@server ~]# mount -t tmpfs shmfs -o size=1024m /dev/shm[root@server ~]# df -k /dev/shmFilesystem 1K-blocks Used Available Use% Mounted onshmfs 1048576 0 1048576 0% /dev/shm[@more@]
听同事关于一个ASM的故事
最近同事去客户现场,一启动ASM,HP主机就重新启动后来检查ASM启动文件中的disk_string参数,发现该通过该参数扫描root盘disk_string=/dev/....修改该参数不扫描根盘,操作系统不在重新启动[@more@]
exp导出blob数据时报 ORA-22924: snapshot too old
针对该问题,参考metalink Doc ID: 452341.1Solution1. Run the following script against the LOB tables in order to check for corruption:set serverout onexec dbms_output.enable(100000);declare pag number; len number; c varchar2(10); charpp number := 8132/2;begin for r in (select rowid rid, dbms_lob.getlength (<your_clob_column>) len from <your_table_with_clcob_column>) loop if r.len is not null then for page in 0..r.len/charpp loop begin
linux 上 10g rac 升级到10.2.0.4
今天没什么事情,把笔记本上的10.2.0.3 rac升级到10.2.0.4,简单描述下升级过程第一步修改两个节点上的数据库启动方式把相关数据库及crs停掉$srvctl modify database -d orcl -y manual$srvctl stop asm -n server1$srvctl stop asm -n server2$srvctl stop instance -d orcl -i orcl1$srvctl stop instance -d orcl -i orcl2$srvctl stop nodeapps -n server1$srvctl stop nodeapps -n server2# crsctl stop crs第二步升级rac crs软件,10g的crs补丁和db补丁都在一个盘里,只是在升级的时候选不同的安装路径而已,注意安装界面选择对应的安
oracle 11g release 2 12g 不支持裸设备的声明
参考 metalink 754305.1,578455.1 两篇文章在11g release 2版本图形界面不再支持使用裸设备,在12g中,完全不支持使用裸设备oracle开始全面强迫推行ASM[@more@]
一个[kclchkblk_4]错误处理
今天早上一上班就有朋友在MSN上说,容灾库无法启动,昨天晚上容灾库和生产库同步后,容灾库打开频繁的出现下列错误ORA-00600: internal error code, arguments: [2662], [2156], [2993124414], [2156], [2997732192], [97803001], [], []ORA-00600: internal error code, arguments: [kclchkblk_4], [2156], [18446744072412316512], [2156], [18446744072407708733], [], [], []查看metalink文档275902.1解释该错误Cause 1) Error, ORA-600[KCLCHKBLK_4], is signaled because the SCN in a tempfile blockis too high. The same reason
10.2.0.3 crs bundle# 安装说明
Normal 0 7.8 磅 0 2 具体在安装crs过程中可能遇到的问题请详细阅读metalink文档(405820.1),下面描述整个工作步骤。注意在该文档中前缀提示为 Ø #表示为root用户执行该命令 Ø %表示为oracle用户执行该命令 设置权限 该步骤主要是参考metalink文档405820.1,在AIX平台上安装完10.2.0.3 crs bundle#3 patch后,crs无法正常启动,通过设置这些权限可以解决该问题。 #chuser capabilities=CAP_BYP
转载一个朋友的关于outline的使用
http://space.itpub.net/756652/viewspace-544642SQL> variable aa number;SQL> exec :aa:=90;PL/SQL 过程已成功完成。SQL> select * from tt where id=:aa; ID MC ---------- -------------------- 90 1 Execution Plan---------------------------------------------------------- 0 SELEC
10g统计信息的管理
禁用10自动统计分析特性: exec DBMS_SCHEDULER.DISABLE('GATHER_STATS_JOB');exec dbms_stats.gather_table_stats(username,tablename,method_opt => 'FOR ALL COLUMNS SIZE 1',cascade => TRUE,estimate_percent => 25,granularity=>'all',degree => 4,no_invalidate => false);[@more@]
10g关于统计信息自动收集的一些测试
oracle9i生产库上在导出表的统计信息时有部分索引的统计信息导不出来,开始认为是索引的统计列GLOBAL_STAT=NO导致索引统计信息无法导出,在这里做一个演示来说明导致这种问题的原因。 create table T1 (A NUMBER,B NUMBER); declare begin for i in 1..10000 loop insert into T1 (a) values (i); end loop; commi
一篇关于Cost Based Optimizer统计收集的文挡
Subject: Gathering Statistics for the Cost Based Optimizer Doc ID: 114671.1 Type: FAQ Modified Date : 11-JAN-2009 Status: PUBLISHED Checked for relevance June 2007PURPOSE-------Give the available methods for gathering statistics for the Cost Based Optimizer. SCOPE & APPLICATION-------------------Database Administrators and Oracle Support AnalystsGathering Statistics-------------------- The cost-based optimization approach uses these statistics to estimate
10046 event的使用
10046 EVENT levels: /* Style Definitions */ table.MsoNormalTable {mso-style-name:普通表格; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-languag
Heap size 2706K exceeds notification threshold (2048K)
Normal 0 7.8 磅 0 2 false false false MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:普通表格; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan;
转载ORA-01591错误故障处理
ORA-01591错误故障处理 摘要: 在访问某些表的特定行时报ORA-01591错误 select * from BF_INCOME_EXPENSES_T where account_id = 36816153 and user_id = 39964213 and city_code = '185' ORA-01591: 锁定已被有问题的分配事务处理72.0.1608712挂起 SQL> select count(*) from UNITELE.BI_MQSYNC_SOURCE_CONTROL_T1; ORA-01591: 锁定已被有问题的分配事务处理72.0.1608712挂起 由于该表是业务关键表,部分前台业务受到影响。 关键词:ORA-01591 DBA_2PC_PENDING 分布式事务 1.故障分析 首先,
查找holder的操作
Normal 0 7.8 磅 0 2 false false false MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:普通表格; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan;
关于RAC环境下锁查询的测试案例1-2
Normal 0 7.8 磅 0 2 false false false MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:普通表格; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan;
关于RAC环境下锁查询的测试案例1-1
Normal 0 7.8 磅 0 2 false false false MicrosoftInternetExplorer4 /* Style Definitions */ table.MsoNormalTable {mso-style-name:普通表格; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan;
关于ora_pz进程的一些讨论
在oracle10g数据库上经常看到一些ora_pz进程From Oracle 10g onwards you will find on every node slave processes like pz99. This are the processes that query the gv$ viewsselect * from gv$px_process; INST_ID SERV STATUS PID SPID SID SERIAL#---------- ---- --------- ---------- ------------ ---------- ---------- 2 PZ99 IN USE 35 24994 2562 53336 2 PZ98 AVAILABLE 109 3905 2 PZ97 AVAILABLE 1229 4260
utllockt.sql
运行oracle自己的工具就可以查询锁的信息You can also use the utllockt.sql script to display lock wait-for in a hierarchy. The script prints the sessions that are waiting for locks and the sessions that are blocking. You must run the catblock.sql script (found in $ORACLE_HOME/rdbms/admin folder) as a sysdba user before using utllockt.sql. The catblock.sql script creates the dba_locksand dba_blockers views along with others that will be used by utllockt.sql[@more@]