oracle 11g crs检测结果
+ASM1@testdb11a /oracle/media/grid$ ./runcluvfy.sh stage -pre crsinst -n testdb11a,testdb11b -verbose Performing pre-checks for cluster services setup Checking node reachability... Check: Node reachability from node "testdb11a"
Destination Node Reachable?
------------------------------------ ------------------------
testdb11b yes
testdb11a yes
Result: Node reachability check passed from node "testdb11a" Checking user equivalence... Check: User equivalence for user "grid"
Node Name Status
------------------------------------ ------------------------
testdb11b passed
testdb11a passed
Result: User equivalence check passed for user "grid" Checking node connectivity... Checking hosts config file...
Node Name Status
------------------------------------ ------------------------
testdb11b passed
testdb11a passed Verification of the hosts config file successful Interface information for node "testdb11b"
Name IP Address Subnet Gateway Def. Gateway HW Address MTU
------ --------------- --------------- --------------- --------------- ----------------- ------
eth0 192.168.1.21 192.168.1.0 0.0.0.0 192.168.1.1 :0C::B6::
eth0 192.168.1.24 192.168.1.0 0.0.0.0 192.168.1.1 :0C::B6::
eth0 192.168.1.23 192.168.1.0 0.0.0.0 192.168.1.1 :0C::B6::
eth1 192.168.2.21 192.168.2.0 0.0.0.0 192.168.1.1 :0C::B6::5E
eth1 169.254.164.12 169.254.0.0 0.0.0.0 192.168.1.1 :0C::B6::5E
eth2 192.168.1.115 192.168.1.0 0.0.0.0 192.168.1.1 :0C::B6:: Interface information for node "testdb11a"
Name IP Address Subnet Gateway Def. Gateway HW Address MTU
------ --------------- --------------- --------------- --------------- ----------------- ------
eth0 192.168.1.20 192.168.1.0 0.0.0.0 192.168.2.1 :0C::0B:FD:9E
eth0 192.168.1.22 192.168.1.0 0.0.0.0 192.168.2.1 :0C::0B:FD:9E
eth1 192.168.2.20 192.168.2.0 0.0.0.0 192.168.2.1 :0C::0B:FD:A8
eth1 169.254.209.140 169.254.0.0 0.0.0.0 192.168.2.1 :0C::0B:FD:A8 Check: Node connectivity of subnet "192.168.1.0"
Source Destination Connected?
------------------------------ ------------------------------ ----------------
testdb11b[192.168.1.21] testdb11b[192.168.1.24] yes
testdb11b[192.168.1.21] testdb11b[192.168.1.23] yes
testdb11b[192.168.1.21] testdb11b[192.168.1.115] yes
testdb11b[192.168.1.21] testdb11a[192.168.1.20] yes
testdb11b[192.168.1.21] testdb11a[192.168.1.22] yes
testdb11b[192.168.1.24] testdb11b[192.168.1.23] yes
testdb11b[192.168.1.24] testdb11b[192.168.1.115] yes
testdb11b[192.168.1.24] testdb11a[192.168.1.20] yes
testdb11b[192.168.1.24] testdb11a[192.168.1.22] yes
testdb11b[192.168.1.23] testdb11b[192.168.1.115] yes
testdb11b[192.168.1.23] testdb11a[192.168.1.20] yes
testdb11b[192.168.1.23] testdb11a[192.168.1.22] yes
testdb11b[192.168.1.115] testdb11a[192.168.1.20] yes
testdb11b[192.168.1.115] testdb11a[192.168.1.22] yes
testdb11a[192.168.1.20] testdb11a[192.168.1.22] yes
Result: Node connectivity passed for subnet "192.168.1.0" with node(s) testdb11b,testdb11a Check: TCP connectivity of subnet "192.168.1.0"
Source Destination Connected?
------------------------------ ------------------------------ ----------------
testdb11a:192.168.1.20 testdb11b:192.168.1.21 passed
testdb11a:192.168.1.20 testdb11b:192.168.1.24 passed
testdb11a:192.168.1.20 testdb11b:192.168.1.23 passed
testdb11a:192.168.1.20 testdb11b:192.168.1.115 passed
testdb11a:192.168.1.20 testdb11a:192.168.1.22 passed
Result: TCP connectivity check passed for subnet "192.168.1.0" Check: Node connectivity of subnet "192.168.2.0"
Source Destination Connected?
------------------------------ ------------------------------ ----------------
testdb11b[192.168.2.21] testdb11a[192.168.2.20] yes
Result: Node connectivity passed for subnet "192.168.2.0" with node(s) testdb11b,testdb11a Check: TCP connectivity of subnet "192.168.2.0"
Source Destination Connected?
------------------------------ ------------------------------ ----------------
testdb11a:192.168.2.20 testdb11b:192.168.2.21 passed
Result: TCP connectivity check passed for subnet "192.168.2.0" Check: Node connectivity of subnet "169.254.0.0"
Source Destination Connected?
------------------------------ ------------------------------ ----------------
testdb11b[169.254.164.12] testdb11a[169.254.209.140] yes
Result: Node connectivity passed for subnet "169.254.0.0" with node(s) testdb11b,testdb11a Check: TCP connectivity of subnet "169.254.0.0"
Source Destination Connected?
------------------------------ ------------------------------ ----------------
testdb11a:169.254.209.140 testdb11b:169.254.164.12 passed
Result: TCP connectivity check passed for subnet "169.254.0.0" Interfaces found on subnet "169.254.0.0" that are likely candidates for VIP are:
testdb11b eth1:169.254.164.12
testdb11a eth1:169.254.209.140 WARNING:
Could not find a suitable set of interfaces for the private interconnect
Checking subnet mask consistency...
Subnet mask consistency check passed for subnet "192.168.1.0".
Subnet mask consistency check passed for subnet "192.168.2.0".
Subnet mask consistency check passed for subnet "169.254.0.0".
Subnet mask consistency check passed. Result: Node connectivity check passed Checking multicast communication... Checking subnet "192.168.1.0" for multicast communication with multicast group "230.0.1.0"...
Check of subnet "192.168.1.0" for multicast communication with multicast group "230.0.1.0" passed. Checking subnet "192.168.2.0" for multicast communication with multicast group "230.0.1.0"...
Check of subnet "192.168.2.0" for multicast communication with multicast group "230.0.1.0" passed. Checking subnet "169.254.0.0" for multicast communication with multicast group "230.0.1.0"...
Check of subnet "169.254.0.0" for multicast communication with multicast group "230.0.1.0" passed. Check of multicast communication passed. Checking ASMLib configuration.
Node Name Status
------------------------------------ ------------------------
testdb11b passed
testdb11a passed
Result: Check for ASMLib configuration passed. Check: Total memory
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b .8672MB (.0KB) .5GB (.0KB) failed
testdb11a .8672MB (.0KB) .5GB (.0KB) failed
Result: Total memory check failed Check: Available memory
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b .4297MB (.0KB) 50MB (.0KB) passed
testdb11a .5391MB (.0KB) 50MB (.0KB) passed
Result: Available memory check passed Check: Swap space
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b .9687GB (.0KB) .5GB (.0KB) passed
testdb11a .9687GB (.0KB) .5GB (.0KB) passed
Result: Swap space check passed Check: Free disk space for "testdb11b:/u01/app/11.2.0/grid,testdb11b:/tmp"
Path Node Name Mount point Available Required Status
---------------- ------------ ------------ ------------ ------------ ------------
/u01/app/11.2./grid testdb11b / .9961GB .5GB passed
/tmp testdb11b / .9961GB .5GB passed
Result: Free disk space check passed for "testdb11b:/u01/app/11.2.0/grid,testdb11b:/tmp" Check: Free disk space for "testdb11a:/u01/app/11.2.0/grid,testdb11a:/tmp"
Path Node Name Mount point Available Required Status
---------------- ------------ ------------ ------------ ------------ ------------
/u01/app/11.2./grid testdb11a / .7471GB .5GB failed
/tmp testdb11a / .7471GB .5GB failed
Result: Free disk space check failed for "testdb11a:/u01/app/11.2.0/grid,testdb11a:/tmp" Check: User existence for "grid"
Node Name Status Comment
------------ ------------------------ ------------------------
testdb11b passed exists()
testdb11a passed exists() Checking for multiple users with UID value
Result: Check for multiple users with UID value passed
Result: User existence check passed for "grid" Check: Group existence for "oinstall"
Node Name Status Comment
------------ ------------------------ ------------------------
testdb11b passed exists
testdb11a passed exists
Result: Group existence check passed for "oinstall" Check: Group existence for "dba"
Node Name Status Comment
------------ ------------------------ ------------------------
testdb11b passed exists
testdb11a passed exists
Result: Group existence check passed for "dba" Check: Membership of user "grid" in group "oinstall" [as Primary]
Node Name User Exists Group Exists User in Group Primary Status
---------------- ------------ ------------ ------------ ------------ ------------
testdb11b yes yes yes yes passed
testdb11a yes yes yes yes passed
Result: Membership check for user "grid" in group "oinstall" [as Primary] passed Check: Membership of user "grid" in group "dba"
Node Name User Exists Group Exists User in Group Status
---------------- ------------ ------------ ------------ ----------------
testdb11b yes yes yes passed
testdb11a yes yes yes passed
Result: Membership check for user "grid" in group "dba" passed Check: Run level
Node Name run level Required Status
------------ ------------------------ ------------------------ ----------
testdb11b , passed
testdb11a , passed
Result: Run level check passed Check: Hard limits for "maximum open file descriptors"
Node Name Type Available Required Status
---------------- ------------ ------------ ------------ ----------------
testdb11b hard passed
testdb11a hard passed
Result: Hard limits check passed for "maximum open file descriptors" Check: Soft limits for "maximum open file descriptors"
Node Name Type Available Required Status
---------------- ------------ ------------ ------------ ----------------
testdb11b soft passed
testdb11a soft passed
Result: Soft limits check passed for "maximum open file descriptors" Check: Hard limits for "maximum user processes"
Node Name Type Available Required Status
---------------- ------------ ------------ ------------ ----------------
testdb11b hard passed
testdb11a hard passed
Result: Hard limits check passed for "maximum user processes" Check: Soft limits for "maximum user processes"
Node Name Type Available Required Status
---------------- ------------ ------------ ------------ ----------------
testdb11b soft passed
testdb11a soft passed
Result: Soft limits check passed for "maximum user processes" Check: System architecture
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b x86_64 x86_64 passed
testdb11a x86_64 x86_64 passed
Result: System architecture check passed Check: Kernel version
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b 2.6.-.el5 2.6. passed
testdb11a 2.6.-.el5 2.6. passed
Result: Kernel version check passed Check: Kernel parameter for "semmsl"
Node Name Current Configured Required Status Comment
---------------- ------------ ------------ ------------ ------------ ------------
testdb11b passed
testdb11a passed
Result: Kernel parameter check passed for "semmsl" Check: Kernel parameter for "semmns"
Node Name Current Configured Required Status Comment
---------------- ------------ ------------ ------------ ------------ ------------
testdb11b passed
testdb11a passed
Result: Kernel parameter check passed for "semmns" Check: Kernel parameter for "semopm"
Node Name Current Configured Required Status Comment
---------------- ------------ ------------ ------------ ------------ ------------
testdb11b passed
testdb11a passed
Result: Kernel parameter check passed for "semopm" Check: Kernel parameter for "semmni"
Node Name Current Configured Required Status Comment
---------------- ------------ ------------ ------------ ------------ ------------
testdb11b passed
testdb11a passed
Result: Kernel parameter check passed for "semmni" Check: Kernel parameter for "shmmax"
Node Name Current Configured Required Status Comment
---------------- ------------ ------------ ------------ ------------ ------------
testdb11b passed
testdb11a passed
Result: Kernel parameter check passed for "shmmax" Check: Kernel parameter for "shmmni"
Node Name Current Configured Required Status Comment
---------------- ------------ ------------ ------------ ------------ ------------
testdb11b passed
testdb11a passed
Result: Kernel parameter check passed for "shmmni" Check: Kernel parameter for "shmall"
Node Name Current Configured Required Status Comment
---------------- ------------ ------------ ------------ ------------ ------------
testdb11b passed
testdb11a passed
Result: Kernel parameter check passed for "shmall" Check: Kernel parameter for "file-max"
Node Name Current Configured Required Status Comment
---------------- ------------ ------------ ------------ ------------ ------------
testdb11b passed
testdb11a passed
Result: Kernel parameter check passed for "file-max" Check: Kernel parameter for "ip_local_port_range"
Node Name Current Configured Required Status Comment
---------------- ------------ ------------ ------------ ------------ ------------
testdb11b between 9000.0 & 65500.0 between 9000.0 & 65500.0 between 9000.0 & 65500.0 passed
testdb11a between 9000.0 & 65500.0 between 9000.0 & 65500.0 between 9000.0 & 65500.0 passed
Result: Kernel parameter check passed for "ip_local_port_range" Check: Kernel parameter for "rmem_default"
Node Name Current Configured Required Status Comment
---------------- ------------ ------------ ------------ ------------ ------------
testdb11b passed
testdb11a passed
Result: Kernel parameter check passed for "rmem_default" Check: Kernel parameter for "rmem_max"
Node Name Current Configured Required Status Comment
---------------- ------------ ------------ ------------ ------------ ------------
testdb11b passed
testdb11a passed
Result: Kernel parameter check passed for "rmem_max" Check: Kernel parameter for "wmem_default"
Node Name Current Configured Required Status Comment
---------------- ------------ ------------ ------------ ------------ ------------
testdb11b passed
testdb11a passed
Result: Kernel parameter check passed for "wmem_default" Check: Kernel parameter for "wmem_max"
Node Name Current Configured Required Status Comment
---------------- ------------ ------------ ------------ ------------ ------------
testdb11b passed
testdb11a passed
Result: Kernel parameter check passed for "wmem_max" Check: Kernel parameter for "aio-max-nr"
Node Name Current Configured Required Status Comment
---------------- ------------ ------------ ------------ ------------ ------------
testdb11b passed
testdb11a passed
Result: Kernel parameter check passed for "aio-max-nr" Check: Package existence for "make"
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b make-3.81-.el5 make-3.81 passed
testdb11a make-3.81-.el5 make-3.81 passed
Result: Package existence check passed for "make" Check: Package existence for "binutils"
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b binutils-2.17.50.0.-.el5 binutils-2.17.50.0. passed
testdb11a binutils-2.17.50.0.-.el5 binutils-2.17.50.0. passed
Result: Package existence check passed for "binutils" Check: Package existence for "gcc(x86_64)"
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b gcc(x86_64)-4.1.-.el5 gcc(x86_64)-4.1. passed
testdb11a gcc(x86_64)-4.1.-.el5 gcc(x86_64)-4.1. passed
Result: Package existence check passed for "gcc(x86_64)" Check: Package existence for "libaio(x86_64)"
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b libaio(x86_64)-0.3.- libaio(x86_64)-0.3. passed
testdb11a libaio(x86_64)-0.3.- libaio(x86_64)-0.3. passed
Result: Package existence check passed for "libaio(x86_64)" Check: Package existence for "glibc(x86_64)"
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b glibc(x86_64)-2.5- glibc(x86_64)-2.5- passed
testdb11a glibc(x86_64)-2.5- glibc(x86_64)-2.5- passed
Result: Package existence check passed for "glibc(x86_64)" Check: Package existence for "compat-libstdc++-33(x86_64)"
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b compat-libstdc++-(x86_64)-3.2.- compat-libstdc++-(x86_64)-3.2. passed
testdb11a compat-libstdc++-(x86_64)-3.2.- compat-libstdc++-(x86_64)-3.2. passed
Result: Package existence check passed for "compat-libstdc++-33(x86_64)" Check: Package existence for "elfutils-libelf(x86_64)"
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b elfutils-libelf(x86_64)-0.137-.el5 elfutils-libelf(x86_64)-0.125 passed
testdb11a elfutils-libelf(x86_64)-0.137-.el5 elfutils-libelf(x86_64)-0.125 passed
Result: Package existence check passed for "elfutils-libelf(x86_64)" Check: Package existence for "elfutils-libelf-devel"
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b elfutils-libelf-devel-0.137-.el5 elfutils-libelf-devel-0.125 passed
testdb11a elfutils-libelf-devel-0.137-.el5 elfutils-libelf-devel-0.125 passed WARNING:
PRVF- : Multiple versions of package "elfutils-libelf-devel" found on node testdb11b: elfutils-libelf-devel(i386)-0.137-.el5,elfutils-libelf-devel(x86_64)-0.137-.el5 WARNING:
PRVF- : Multiple versions of package "elfutils-libelf-devel" found on node testdb11a: elfutils-libelf-devel(i386)-0.137-.el5,elfutils-libelf-devel(x86_64)-0.137-.el5
Result: Package existence check passed for "elfutils-libelf-devel" Check: Package existence for "glibc-common"
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b glibc-common-2.5- glibc-common-2.5 passed
testdb11a glibc-common-2.5- glibc-common-2.5 passed
Result: Package existence check passed for "glibc-common" Check: Package existence for "glibc-devel(x86_64)"
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b glibc-devel(x86_64)-2.5- glibc-devel(x86_64)-2.5 passed
testdb11a glibc-devel(x86_64)-2.5- glibc-devel(x86_64)-2.5 passed
Result: Package existence check passed for "glibc-devel(x86_64)" Check: Package existence for "glibc-headers"
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b glibc-headers-2.5- glibc-headers-2.5 passed
testdb11a glibc-headers-2.5- glibc-headers-2.5 passed
Result: Package existence check passed for "glibc-headers" Check: Package existence for "gcc-c++(x86_64)"
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b gcc-c++(x86_64)-4.1.-.el5 gcc-c++(x86_64)-4.1. passed
testdb11a gcc-c++(x86_64)-4.1.-.el5 gcc-c++(x86_64)-4.1. passed
Result: Package existence check passed for "gcc-c++(x86_64)" Check: Package existence for "libaio-devel(x86_64)"
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b libaio-devel(x86_64)-0.3.- libaio-devel(x86_64)-0.3. passed
testdb11a libaio-devel(x86_64)-0.3.- libaio-devel(x86_64)-0.3. passed
Result: Package existence check passed for "libaio-devel(x86_64)" Check: Package existence for "libgcc(x86_64)"
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b libgcc(x86_64)-4.1.-.el5 libgcc(x86_64)-4.1. passed
testdb11a libgcc(x86_64)-4.1.-.el5 libgcc(x86_64)-4.1. passed
Result: Package existence check passed for "libgcc(x86_64)" Check: Package existence for "libstdc++(x86_64)"
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b libstdc++(x86_64)-4.1.-.el5 libstdc++(x86_64)-4.1. passed
testdb11a libstdc++(x86_64)-4.1.-.el5 libstdc++(x86_64)-4.1. passed
Result: Package existence check passed for "libstdc++(x86_64)" Check: Package existence for "libstdc++-devel(x86_64)"
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b libstdc++-devel(x86_64)-4.1.-.el5 libstdc++-devel(x86_64)-4.1. passed
testdb11a libstdc++-devel(x86_64)-4.1.-.el5 libstdc++-devel(x86_64)-4.1. passed
Result: Package existence check passed for "libstdc++-devel(x86_64)" Check: Package existence for "sysstat"
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b sysstat-7.0.-.el5 sysstat-7.0. passed
testdb11a sysstat-7.0.-.el5 sysstat-7.0. passed
Result: Package existence check passed for "sysstat" Check: Package existence for "ksh"
Node Name Available Required Status
------------ ------------------------ ------------------------ ----------
testdb11b ksh--.el5 ksh- passed
testdb11a ksh--.el5 ksh- passed
Result: Package existence check passed for "ksh" Checking for multiple users with UID value
Result: Check for multiple users with UID value passed Check: Current group ID
Result: Current group ID check passed Starting check for consistency of primary group of root user
Node Name Status
------------------------------------ ------------------------
testdb11b passed
testdb11a passed Check for consistency of root user's primary group passed Starting Clock synchronization checks using Network Time Protocol(NTP)... NTP Configuration file check started...
Network Time Protocol(NTP) configuration file not found on any of the nodes. Oracle Cluster Time Synchronization Service(CTSS) can be used instead of NTP for time synchronization on the cluster nodes
No NTP Daemons or Services were found to be running Result: Clock synchronization check using Network Time Protocol(NTP) passed Checking Core file name pattern consistency...
Core file name pattern consistency check passed. Checking to make sure user "grid" is not in "root" group
Node Name Status Comment
------------ ------------------------ ------------------------
testdb11b passed does not exist
testdb11a passed does not exist
Result: User "grid" is not part of "root" group. Check passed Check default user file creation mask
Node Name Available Required Comment
------------ ------------------------ ------------------------ ----------
testdb11b passed
testdb11a passed
Result: Default user file creation mask check passed
Checking consistency of file "/etc/resolv.conf" across nodes Checking the file "/etc/resolv.conf" to make sure only one of domain and search entries is defined
File "/etc/resolv.conf" does not have both domain and search entries defined
Checking if domain entry in file "/etc/resolv.conf" is consistent across the nodes...
domain entry in file "/etc/resolv.conf" is consistent across nodes
Checking if search entry in file "/etc/resolv.conf" is consistent across the nodes...
search entry in file "/etc/resolv.conf" is consistent across nodes
Checking file "/etc/resolv.conf" to make sure that only one search entry is defined
All nodes have one search entry defined in file "/etc/resolv.conf"
Checking all nodes to make sure that search entry is "localdomain" as found on node "testdb11b"
All nodes of the cluster have same value for 'search'
Checking DNS response time for an unreachable node
Node Name Status
------------------------------------ ------------------------
testdb11b passed
testdb11a passed
The DNS response time for an unreachable node is within acceptable limit on all nodes File "/etc/resolv.conf" is consistent across nodes Check: Time zone consistency
Result: Time zone consistency check passed Pre-check for cluster services setup was unsuccessful on all the nodes.
oracle 11g crs检测结果的更多相关文章
- Oracle 11g RAC 卸载CRS步骤
Oracle 11g之后提供了卸载grid和database的脚本,可以卸载的比较干净,不需要手动删除crs ##########如果要卸载RAC,需要先使用dbca删除数据库,在执行下面的操作### ...
- 【oracle 11G Grid 】Crsctl start cluster 和 crsctl start crs 有差别么？
[oracle 11G Grid ]Crsctl start cluster 和 crsctl start crs 有差别么? q:Crsctl start cluster 是 11.2新特性和 ...
- oracle 11g r1 RAC增加新节点
在一套两节点的rac上增加一个新的节点,详细的操作记录如下: 已有节点RAC1,RAC2 一,环境及版本: 公司环境:Vmware Esxi 5.5 操作系统:Redhat 5.8 x86_64 ...
- 转载：细说oracle 11g rac 的ip地址
本文转载自:细说oracle 11g rac 的ip地址 http://blog.sina.com.cn/s/blog_4fe6d4250102v5fa.html 以前搭建oracle rac的时候( ...
- Oracle 11g RAC for LINUX rhel 6.X silent install（静默安装）
一.前期规划 1.硬件环境 CPU: Intel(R) Xeon(R) CPU E7-4820 v4 @ 2.00GHz 8*10核 内存:512GB OCR:2147*5 MB DATA1:2TB ...
- CentOS6.8环境安装oracle 11G
本节所讲内容: oracle11g基础环境配置 数据库的三种安装方式(图形.静默.克隆) http://db-engines.com REDHAT6.5安装oracle11.2.4 ORACLE11G ...
- Oracle 11g RAC运维总结
转至:https://blog.csdn.net/qq_41944882/article/details/103560879 1 术语解释1.1 高可用(HA)什么是高可用?顾名思义我们能轻松地理解是 ...
- Linux平台oracle 11g单实例 + ASM存储 安装部署 快速参考
操作环境:Citrix虚拟化环境中申请一个Linux6.4主机(模板)目标:创建单机11g + ASM存储 数据库 1. 主机准备 2. 创建ORACLE 用户和组成员 3. 创建以下目录并赋予对应权 ...
- RHEL6.4 + Oracle 11g DG测试环境快速搭建参考
环境现状: 两台虚拟主机A和B: 1. A机器已安装ASM存储的Oracle 11g 实例 参考:http://www.cnblogs.com/jyzhao/p/4332410.html 2 ...
随机推荐
- php 如何解决“您访问的域名有误或网页不存在”
对一个域名访问,在家访问正常,到办公室就总是看到下面的页面. 清楚浏览器浏览数据是一个解决途径.这里通过Chrome浏览做示例.通过标记路径,进入清除界面. 也可以在浏览器地址中输入 chrome:/ ...
- cxf设置代理访问webservice接口
由于业务上的需要,需要访问第三方提供的webservice接口,但由于公司做了对外访问的限制,不设置代理是不能外网的,如果使用http设置代理访问外网还是比较容易的,但使用cxf有点不知道从哪里入手. ...
- 分布式服务框架dubbo原理解析（转）
libaba有好几个分布式框架,主要有:进行远程调用(类似于RMI的这种远程调用)的(dubbo.hsf),jms消息服务(napoli.notify),KV数据库(tair)等.这个框架/工具/产品 ...
- nginx中将POST数据写到日志里面的正确方式
http://www.cnblogs.com/meteorx/p/3188647.html
- Map工具系列-02-数据迁移工具使用说明
所有cs端工具集成了一个工具面板 -打开(IE) Map工具系列-01-Map代码生成工具说明 Map工具系列-02-数据迁移工具使用说明 Map工具系列-03-代码生成BySQl工具使用说明 Map ...
- sqlalchemy入门记录
前言 发现翻译全文时间比较久,所以先整个简单的使用说明吧 安装SQLAlchemy pip install sqlalchemy 查看SQLAlchemy版本 In [1]: import sqlal ...
- js 中关于this用变量存起来的原因
近来,不忙,总是在网上看大牛的博客,发现关于this指向的情况,有的说是4种,也对,有的就是总结一句话,也对,但是我发现一种特殊情况,例子如下 var show={ btn:$('.div1'), i ...
- .NET学习之路----我对P/Invoke技术的理解(一)
看了P/Invoke技术的介绍,于是想写下点东西,东西包含两个部分:知识的纪录和我的理解及疑问. r托管代码中调用非托管API函数的过程 1.定位包含API的DLL: 2.载入DLL 3.找到DLL中 ...
- tamtam-nuget-imageserver
https://bitbucket.org/tamtam-nl/tamtam-nuget-imageserver/src/eaddb1ac943fcaa9e7ef210ed5a5ccf630b8699 ...
- sql clear dblog
USE [master]GOALTER DATABASE ndFlightPolicy SET RECOVERY SIMPLE WITH NO_WAITGOALTER DATABASE ndFligh ...