使用sysbench测试Mysql性能
sysbench可以用来测试oracle,mysql,os的性能,比较方便实用[@more@]首先要安装mysql 5,因为mysql 4不支持sysbench 0.4.8安装完以后按照下面的步骤配置sysbench:tar zxvf sysbench-0.4.8.tar.gz./configure --with-mysql-includes=/usr/local/mysql/include --with-mysql-libs=/usr/local/mysql/lib && make && make install如果安装完毕后运行sysbench碰到下面的错误:sysbench: error while loading shared libraries: libmysqlclient_r.so.15: cannot open shared object file: No such file or directory运行 exp
Megaraid 必知必会
使用LSI的megaraid可以对raid进行有效监控。别的厂商比如HP,IBM也有自己的raid API[@more@]MegaCli -ldinfo -lall -aall查询raid级别,磁盘数量,容量,条带大小。MegaCli -cfgdsply -aALL |grep Policy查询控制器cache策略MegaCli -LDSetProp WB -L0 -a0设置write back功能MegaCli -LDSetProp CachedBadBBU -L0 -a0设置即使电池坏了还是保持WB功能MegaCli -AdpBbuCmd -BbuLearn a0手动充电MegaCli -FwTermLog -Dsply -aALL 查询日志显示适配器个数: MegaCli -adpCount显示所有适配器信息: MegaCli -AdpAllInfo -aAll Critical Disks
修改sqlplus的SQLPROMPT
记着备用[@more@]alter session set nls_date_format='hh24:mi:ss';col login_info_temp new_value login_infoselect UTL_INADDr.get_host_name login_info_temp from dual;SET SQLPROMPT "_USER'@'_CONNECT_IDENTIFIER _DATE &login_info SQL>"
老外的EXP&IMP总结
写的不错,方方面面都写的很认真,要是我也有这么认真就好了- -[@more@]Most DBAs know this old trick of using a named pipe in import or export on UNIX or Linux (not for Windows although it has the concept of named pipes). Most of the time you do this is when you need to export to or import from a compressed file. mknod tmppipe p #Create a named pipe, can also be: mkfifo tmppipe #export exp username/password file=tmppipe & cat tmppipe | gzip > expdat.dmp.gz #import cat expdat.dmp
使用SQL Developer 迁移异构数据库到Oracle
基本步骤基本如下:1.在oracle上创建资料库2.使用SQL Developer连接异构数据库,捕获对象3.生成oracle对象脚本4.执行脚本生成对象5.移动数据[@more@]第3步中,脚本中有date类型的话会发生ORA-01843: not a valid month,可以在脚本前加上2句:alter session set nls_date_language=AMERICAN;alter session set nls_date_format='DD-MON-YYYY';迁移数据时,如果数据有中文等非英语字符,那么要注意字符集的转换,被迁移数据库,SQL Developer,oracle数据库字符集一定要一致。以mysql为例:在my.cnf中加上default-character-set=gbk,重启o
dataguard故障处理一则
primary rac+single dataguard结构[@more@]主库2节点其中一台意外宕机,宕机后发生问题:节点1一切正常,归档可以正常归到standby端。节点2本地归档正常,但是没有归档到远程standby端。查询v$archived_log也没有记录,standby端的日志也均无记录,在主库端switch log触发无效。最后只能kill节点2的arch进程。恢复正常。