windows上也有os watcher:OSWFW。 目前支持的windows版本是: Windows XP (x86 & x64) Windows 7 (x86 & x64) Windows 8 (x86 & x64) Windows 2003 R1 & […]
mongodb添加arbiter节点
创建mongodb的replica set的时候,只是做成了1主2从,没有做成1主1从1仲裁。这我们将一个几点从replica set中删除,再以仲裁节点的身份加入到replica set中: 1.初始状态:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 |
shard1ReplSet:PRIMARY> rs.status();rs.status(); { "set" : "shard1ReplSet", "date" : ISODate("2017-02-21T07:48:03.058Z"), "myState" : 1, "term" : NumberLong(1), "heartbeatIntervalMillis" : NumberLong(2000), "optimes" : { "lastCommittedOpTime" : { "ts" : Timestamp(0, 0), "t" : NumberLong(-1) }, "appliedOpTime" : { "ts" : Timestamp(1487663274, 1), "t" : NumberLong(1) }, "durableOpTime" : { "ts" : Timestamp(1487587982, 1), "t" : NumberLong(-1) } }, "members" : [ { "_id" : 0, "name" : "10.13.0.130:22001", "health" : 1, "state" : 1, "stateStr" : "PRIMARY", "uptime" : 76672, "optime" : { "ts" : Timestamp(1487663274, 1), "t" : NumberLong(1) }, "optimeDate" : ISODate("2017-02-21T07:47:54Z"), "electionTime" : Timestamp(1487587993, 1), "electionDate" : ISODate("2017-02-20T10:53:13Z"), "configVersion" : 1, "self" : true }, { "_id" : 1, "name" : "10.13.0.131:22001", "health" : 1, "state" : 2, "stateStr" : "SECONDARY", "uptime" : 75300, "optime" : { "ts" : Timestamp(1487663274, 1), "t" : NumberLong(1) }, "optimeDurable" : { "ts" : Timestamp(1487587982, 1), "t" : NumberLong(-1) }, "optimeDate" : ISODate("2017-02-21T07:47:54Z"), "optimeDurableDate" : ISODate("2017-02-20T10:53:02Z"), "lastHeartbeat" : ISODate("2017-02-21T07:48:02.150Z"), "lastHeartbeatRecv" : ISODate("2017-02-21T07:48:02.215Z"), "pingMs" : NumberLong(0), "syncingTo" : "10.13.0.132:22001", "configVersion" : 1 }, { "_id" : 2, "name" : "10.13.0.132:22001", "health" : 1, "state" : 2, "stateStr" : "SECONDARY", "uptime" : 75300, "optime" : { "ts" : Timestamp(1487663274, 1), "t" : NumberLong(1) }, "optimeDurable" : { "ts" : Timestamp(1487587982, 1), "t" : NumberLong(-1) }, "optimeDate" : ISODate("2017-02-21T07:47:54Z"), "optimeDurableDate" : ISODate("2017-02-20T10:53:02Z"), "lastHeartbeat" : ISODate("2017-02-21T07:48:02.889Z"), "lastHeartbeatRecv" : ISODate("2017-02-21T07:48:01.503Z"), "pingMs" : NumberLong(0), "syncingTo" : "10.13.0.130:22001", "configVersion" : 1 } ], "ok" : 1 } shard1ReplSet:PRIMARY> shard1ReplSet:PRIMARY> shard1ReplSet:PRIMARY> shard1ReplSet:PRIMARY> |
2.删除节点: [cra […]
Oracle并发(CONCURREMT)收集统计信息
对于大表的统计信息收集,我们可以加degree参数,使得扫描大表的时候,进行并行扫描,加快扫描速度。 但是这在收集的时候,还是进行一个表一个表的扫描。并没有并发的扫描各个表。在oracle 11.2.0.2之后,就有了一个参数,可以并发扫描表(或者分区),这就是CONCURRENT参数。你可以通过 […]
Bug Issues Known to cause Wrong Results
LAST UPDATE:
1 |
Dec 15, 2016 |
APPLIES TO:
1 2 3 4 |
Oracle Database - Enterprise Edition - Version 7.0.16.0 and later Oracle Database - Standard Edition - Version 7.0.16.0 and later Oracle Database - Personal Edition - Version 7.1.4.0 and later Information in this document applies to any platform. |
PURPOSE:
1 2 |
This document provides information on bugs known to cause "wrong results". "Wrong results" in this context has quite a broad classification - it may be a performance monitoring view giving slightly misleading information, or may be completely wrong rows returned (or missing) from a query result set. These issues can be particularly difficult to match to a known bug as the symptom often depend on the query. The aim here is to provide a list of bugs known to cause wrong results and to provide both version affected and radio options to trim the list. |
KNOWN BUGS: NB Pr […]
Common X$ dictionary table queries for ORA-4031 investigation
LAST UPDATE:
1 |
Jun 15, 2011 |
APPLIES TO:
1 2 3 |
Oracle Server - Enterprise Edition - Version: 9.2.0.1 to 11.1.0.8 - Release: 9.2 to 11.1 Information in this document applies to any platform. Customers should have limited access to these scripts. There can be database hangs and impacts to performance running these too often. |
PURPOSE: There are a number of x$ queries in various notes […]
Documented Database Bugs With High “Solved SR” Count
APPLIES TO:
1 |
Oracle Database - Enterprise Edition - Version 9.2.0.8 and later |
PURPOSE:
1 2 3 4 5 6 7 |
This note lists "documented" database bugs that have been marked as the solution to a "high number of Service Requests". For the purpose of this listing: A "documented" bug means one with a bugno.8 KM document created from BugTag data. A "high number of Service Requests" means that there are more than 50 "Solved SR" entries for the bug - ie: all bugs in this doc have > 50 "Solved SR" entries from the SR closure data. It is suggested to restrict the list based on the version of interest, and then use the radio buttons to check on particular features / symptoms / facts linked to the bug descriptions. The list includes some bugs with a "D" in the "NB" column - this is used to denote a bug fix that is DISABLED by default and so a customer may encounter that issue in DB versions where the bug is marked as fixed. |
KNOWN BUGS: NB Prob Bug Fixed Description P IIII 7272646 Linux- […]
Known Issues for Database and Query Performance Reported in 12C
LAST UPDATE:
1 |
Dec 13, 2016 |
APPLIES TO:
1 2 |
Oracle Database - Enterprise Edition - Version 12.1.0.1 to 12.1.0.2 [Release 12.1] Information in this document applies to any platform. |
PURPOSE:
1 2 3 4 5 |
In recent quarters, during non-code closure bug review for Performance, it was found that more than 50% of duplicates (36,96) closed by Sustaining Engineering (SE) belonged to version 12.1. As a result this document was created to list most commonly reported and share this with Tier-1 engineers so that they could check this before logging any new bugs. Thus the Goal of this document is to provide a list of known bugs reported in 12C for database & SQL performance for support analysts to check before logging new bugs. In addition to the bugs listed in this article, there is also a useful list of Documented Database Bugs With High "Solved SR" Count where a high number of Service Requests means that there are more than 50 "Solved SR" entries for the bug - ie: all bugs in this doc have > 50 "Solved SR" entries.” : Document 2099231.1 Documented Database Bugs With High "Solved SR" Count |
DETAILS: Query Op […]
关于物理Dataguard切换导致索引坏块的问题
在11.2.0.2之后,有一个非常重要的dataguard的patch。在使用物理dataguard环境(包括ADG),进行switchover之后,存在导致index block上的invalid SCNs的坏块问题。 国内已经好几个行业的大客户,都遇到了这个问题。 在index block中的失 […]
swap不足导致ora-4030
客户一个测试环境,一个主机上面运行了很多数据库,某库的程序会时不时报错ora-4030。 加大了pga,然后还检查了ulimit的 data 和 stack都是ulimit。还是报错。 进而检查/var/adm/messages,发现有报错swap不足的情况。 所以,解决方法是加大物理内存,或者加大 […]
Solaris操作系统真的停止开发了吗?
Solaris系统将被停止开发,这个消息,据我所看到的,最初的来源是来自thelayoff网站的消息『Solaris being canned, at least 50% of teams to be RIF’d in short term』 All hands meetings bei […]
闰秒(Leap Second)问题
2017年的第一天,因为闰秒的关系,加上时差的原因,我国将在北京时间2017年1月1日的7时59分59秒和全球同步进行闰秒调整,届时会出现7:59:60的特殊现象。(国家授时中心闰秒公告) 那么闰秒对数据库有什么影响? (一)具体的说: 可以参考:Information Center: Leap S […]
解决主库报错HeartBeat failed to connect to standby Error 12154
有一个库自从上线之后,主库的alertlog中一直有如下报错:
1 2 3 |
Tue Dec 20 14:42:16 2016 Error 12154 received logging on to the standby PING[ARC2]: Heartbeat failed to connect to standby 'rmydb'. Error is 12154. |
1. 检查远端的standby库已经启动,且已经到了mount以上的状态(即在read only的模式下Real Time Apply)。 2. 检查主库到远端的tnsp […]