aix 上做rac的几个注意点
1.多路径软件是否支持asm一般ds8000使用的多路径软件是vpath,但是vpath不支持asm,所以需要换成mpio2.若是确定asm存储方式,请将hacmp软件卸载。3.emc的多路径软件是powerpath[@more@]
【转】 一次数据库不能归档问题的处理
一次数据库不能归档问题的处理:http://empo007.itpub.net/post/12076/300893版权归属于原作者。感谢原作者。 数据库不能归档,很多的时候是因为磁盘空间不够或者在线日志文件损坏导致。然而4月份的时候,我却遇到一个非常奇怪的归档不成功的问题:1、用户数据库不能登陆,查看警告日志,发现下面的错误:ORA-19510: failed to set size of 102395 blocks for file "/oradata/gpsdb/archive/1_9410.dbf" (blocksize=1024)ORA-27037: unable to obtain file statusHP-UX Error: 2: No such file or directoryAdditional inform
ORA-01031 While Connecting As Sysdba On Windows With A Domain User [ID 1071638.1]
Applies to: Oracle Server - Enterprise Edition - Version: 9.2.0.1 to 11.2.0.2.0 - Release: 9.2 to 11.2Information in this document applies to any platform. Symptoms While trying to connect to a database running on Windows using "/ as sysdba" from an OS session started as a domain user the following error occurs: sqlplus / as sysdbaSQL*Plus: Release 10.2.0.4.0 - Production on M Mar 8 17:22:36 2010Copyright (c) 1982, 2007, Oracle. All Rights Reserved.ERROR:ORA-1031: Insuf
Troubleshooting ORA-1031: Insufficient Privileges While Connecting As SYSDBA [ID 730067.1]
Troubleshooting ORA-1031: Insufficient Privileges While Connecting As SYSDBA [ID 730067.1] 修改时间 05-SEP-2011 类型 TROUBLESHOOTING 状态 PUBLISHED In this Document Purpose Last Review Date Instructions for the Reader Troubleshooting Details Generic Concepts SYSDBA OS Authentication SYSDBA Password File Authentication Troubleshooting ORA-1031 when connecting as SYSDBA using OS Authenticat
Bequeath Connection Generates Ora-12560: Tns:Protocol Adapter Error [ID 831007.1]
Applies to: Oracle Server - Enterprise Edition - Version: 6.0.0.0 to 11.2.0.2.0 - Release: 6.0 to 11.2Microsoft Windows (32-bit) Symptoms The local connection is failing when making a bequeath connection:Enter user-name: sys as sysdbaEnter password:ERROR:ORA-12560: TNS:proto adapter error Changes This is a newly duplicated database. Cause The Windows service name does not match the value for ORACLE_SID. Solution The ORACLE_SID environment variable is used to determine which se
RAC and Sequences [ID 853652.1]
RAC and Sequences [ID 853652.1] 修改时间 13-JUL-2011 类型 BULLETIN 状态 PUBLISHED In this Document Purpose Scope and Application RAC and Sequences 1. Sequence setup 2. Gap in sequences 3. Performance impact when using CACHE or NOCACHE Applies to: Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 11.2.0.2 - Release: 10.1 to 11.2Information in this document applies to any platform.
【原创】一对双引号引发的goldengate血案
一对双引号引发的goldengate血案:源是sql2005 ,目的是linux x64 下的db2 v9.7因为是测试环境,所以只同步了一个sql2005的表(注意,此时我并没有意识到sql2005是区分大小写的)源端和目的端配置完毕后,分别启动两端的mgr进程,状态是running。ok!extract 进程的状态是runningdatpump 进程的状态是runningreplicat进程的状态是runningok!在源端插入一条记录(此表已经被配置extract),马上就看到了源端trail文件的修改时间变了。马上就看到了目的端trail文件的修改时间也变了。然后replicat进程的状态是running然后去目的库查看此条记录
goldengate同步数据的同步速度测试记录
CREATE TABLE U_DS.TB_SMS_SENDSTATUS ( SMSSENDSTATUSID NUMBER NOT NULL, MSGID NUMBER(19) NULL, CHANNELID NUMBER NULL, MISDNTYPE NUMBER NULL, PRIORITY NUMBER NULL, SOURCETYPE NUMBER NULL, CUSTOMERID NUMBER NULL, ORGANID VARCHAR2(20) NULL, USERID NUMBER NULL, SENDADDRESS VARCHAR2(20) NULL, MOBILE VARCHAR2(20)
ORA-16047: DGID mismatch between destination setting and standby
本文转自:http://jzhil2004.blog.163.com/blog/static/275585042010112911625896/感谢原作者.ORA-16047: DGID mismatch between destination setting and standby一般是由于主库上log_archive_dest_?参数设置的db_unique_name和实际备库上设置的db_unique_name不一致引起 处理过程:1)由于之前的standby备机是可以应用日志的,后面由于机房停电,在关闭主从的时候,先关闭主,然后再关闭从,可是当时关闭了主以后,由于从库已经非法停了,类似于停电,后面进行主从库重新开启应用的时候,过程如下:从库:startup mount;alter database
sybase 的设备和数据库,是啥关系?
祈福的DBA (8819616) 21:50:21 一个数据库可以包含多个设备,一个设备也可以被多个数据库包含。祈福的DBA (8819616) 21:51:48 比如有数据库A和B,有设备甲乙丙丁,各100M 祈福的DBA (8819616) 21:52:00 A数据库可以包含甲乙100M以及丙的50M 祈福的DBA (8819616) 21:52:11 数据库B可以包含丙的50M和丁的100M 祈福的DBA (8819616) 21:53:01 A(甲-100M,乙-100M,丙-50M)B(丙-50M,丁-100M)[@more@]
rac2节点上配置iscsi 遇到iscsiadm: failing authentication, received incorrect username from target
在rac2节点上配置iscsi 连接共享存储(使用openfiler做共享存储)时遇到:注意:192.168.0.222是openfiler服务器ip[root@rac2 nodes]# iscsiadm -m discovery -t st -p 192.168.0.222iscsiadm: failing authentication, received incorrect username from target iscsiadm: Login authentication failed with target iscsiadm: discovery login to 192.168.0.222 failed, giving up最终发现是/etc/iscsi/iscsid.conf 配置文件的问题。[root@rac2 nodes]# cat /etc/iscsi/iscsid.conf ## Open-iSCSI default configuration.# Could be locate
查看selinux的状态以及关闭selinux
查看selinux的状态:[root@rac1 ~]# getenforceDisabled[root@rac1 ~]# sestatusSELinux status: disabled[root@rac1 ~]# 修改selinux为disabled(禁用),重启后此修改生效[root@rac1 ~]# cat /etc/selinux/config # This file controls the state of SELinux on the system.# SELINUX= can take one of these three values:# enforcing - SELinux security policy is enforced.# permissive - SELinux prints warnings instead of enforcing.# disabled - SELinux is fully disabled.SELINUX=disabled#
linux下的防火墙
1.检查linux防火墙是否处于开机自动启动状态: chkconfig --list |grep iptables2.检查linux防火墙当前是否处于运行状态:[root@rac1 ~]# service iptables statusFirewall is stopped.若是running的话, service iptables status的输出会有很多行。[@more@]
各种文件系统的允许的单个文件最大大小
fat32 单个文件最大大小? 4Gntfs 单个文件最大大小?ext2单个文件最大大小?ext3单个文件最大大小?ext4单个文件最大大小?[@more@]
检查dataguard有无报错信息的视图
主库:v$managed_standbyv$archive_dest_status备库:v$archived_log[@more@]
遇到ORA-01268: 用于变更永久性 TABLESPACE 的 TEMPFILE 子句无效 这样的错误,请问在么能解决
SQL> ALTER tablespace temp add tempfile '/dev/vgbill05/rlvbill05_4g_48' size 4000M;ALTER tablespace temp add tempfile '/dev/vgbill05/rlvbill05_4g_48' size 4000MORA-01268: 用于变更永久性 TABLESPACE 的 TEMPFILE 子句无效SQL> 白鳝1群里的凉面说:你把size设置成小于4G的就可以了,我也碰到过这个,是bug单个文件不能超过4G,上次我们那个8i的系统就挂了,因为涨到了4G先记录一下。[@more@]
[转]一次linux下的crontab中定义的任务计划无法执行的问题。
一般而言,crontab 定义的任务计划无法执行,无非几个原因:1.先看此linux系统中linux的 crontab进程是否在running 的状态。2.再看crontab中对应的脚本(假设此脚本名称为a.sql)是否有执行权限3.crontab中对应的脚本(假设此脚本名称为a.sql)中的内容是否包含如下的条目 a. ORACLE_BASE b. ORACLE_HOME C.ORACLE_SID D.PATH变量4. a.sql不要在windows下编辑好,然后ftp传到linux中。这样windows下有些不可见字符会导致linux无法运行此a.sql.此点是白鳝1群里一个哥们说的, [@more@][]
AIX: 'GGS ERROR 190 ... : Received Signal: OMVS Shutdown (33).' [ID 969596.1]
AIX: 'GGS ERROR 190 ... : Received Signal: OMVS Shutdown (33).' [ID 969596.1]Applies to: Oracle GoldenGate - Version: 4.0.0 - Release: 4.0.0Information in this document applies to any platform. Solution Issue: GoldenGate process on AIX stops with the following message: GGS ERROR 190 GoldenGate Collector: Received signal: OMVS Shutdown (33). Solution Overview: This message means that AIX had a system-wide paging problem, which it reported to the GoldenGate component, in this case the
不同bit数做dataguard的文章
Role Transitions for Data Guard Configurations Using Mixed Oracle Binaries [ID 414043.1][@more@]
Oracle ASM and Multi-Pathing Technologies [ID 294869.1]
Oracle ASM and Multi-Pathing Technologies [ID 294869.1] 内容不错,其实就是一个pdf文档。[@more@]