查询Oracle RAC Cache Fusion通信的私有网络-Mysql Tutorial-php.cn

Home

Database

Mysql Tutorial

查询Oracle RAC Cache Fusion通信的私有网络

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB

Jun 07, 2016 pm 05:26 PM

oracle rac

查询Oracle RAC Cache Fusion通信的私有网络

[Oracle@zhongwc1 ~]$ cat /etc/RedHat-release
Red Hat Enterprise Linux Server release 5.7 (Tikanga)
[oracle@zhongwc1 ~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.3.0 Production on Tue Jan 22 15:12:35 2013

Copyright (c) 1982, 2011, Oracle. All rights reserved.

Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options

SQL> oradebug setmypid
Statement processed.
SQL> oradebug ipc
Information written to trace file.
SQL> oradebug tracefile_name
/u01/app/oracle/diag/rdbms/zhongwc/zhongwc1/trace/zhongwc1_ora_31553.trc
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options

Oracle版本是11.2.0.3,从11.2.0.2开始引入了HAIP规则为169.254.xxx.xxx;RAC Cache Fusion通信的IP为169.254.218.13

SKGXP:[7f31b7724c68.96]{ctx}:SSKGXPT 0x7f31b772e848 flags 0x0 sockno 13 IP 169.254.218.13 UDP 30898 lerr 0
SKGXP:[7f31b7724c68.97]{ctx}: SKGXPGPID Internet address 169.254.218.13 UDP port number 30898

[oracle@zhongwc1 ~]$ cat /u01/app/oracle/diag/rdbms/zhongwc/zhongwc1/trace/zhongwc1_ora_31553.trc
Trace file /u01/app/oracle/diag/rdbms/zhongwc/zhongwc1/trace/zhongwc1_ora_31553.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1
System name: Linux
Node name: zhongwc1.oracle.com
Release: 2.6.32-200.13.1.el5uek
Version: #1 SMP Wed Jul 27 21:02:33 EDT 2011
Machine: x86_64
Instance name: zhongwc1
Redo thread mounted by this instance: 1
Oracle process number: 38
Unix process pid: 31553, image: oracle@zhongwc1.oracle.com (TNS V1-V3)

*** 2013-01-22 15:12:37.782
*** SESSION ID:(56.143) 2013-01-22 15:12:37.782
*** CLIENT ID:() 2013-01-22 15:12:37.782
*** SERVICE NAME:(SYS$USERS) 2013-01-22 15:12:37.782
*** MODULE NAME:(sqlplus@zhongwc1.oracle.com (TNS V1-V3)) 2013-01-22 15:12:37.782
*** ACTION NAME:() 2013-01-22 15:12:37.782

Processing Oradebug command 'setmypid'

*** 2013-01-22 15:12:37.782
Oradebug command 'setmypid' console output:

*** 2013-01-22 15:12:39.777
Processing Oradebug command 'ipc'
Dump of unix-generic skgm context
areaflags 000000f7
realmflags 0000001f
mapsize 00000800
protectsize 00001000
lcmsize 00001000
seglen 00200000
largestsize 0000040000000000
smallestsize 0000000001000000
stacklimit 0x7fffafa932a0
stackdir -1
mode 640
magic acc01ade
Handle: 0x7f31b77150f0 `/u01/app/oracle/product/11.2.0/dbhome_1zhongwc1'
Dump of unix-generic realm handle `/u01/app/oracle/product/11.2.0/dbhome_1zhongwc1', flags = 00000000
Area #0 `Fixed Size' containing Subareas 0-0
Total size 000000000021ff10 Minimum Subarea size 00000000
Area Subarea Shmid Stable Addr Actual Addr
0 0 3735560 0x00000060000000 0x00000060000000
Subarea size Segment size
0000000000220000 0000000001000000
Area #1 `Variable Size' containing Subareas 4-4
Total size 000000004b000000 Minimum Subarea size 01000000
Area Subarea Shmid Stable Addr Actual Addr
1 4 3768329 0x00000061000000 0x00000061000000
Subarea size Segment size
000000004b000000 000000004b000000
Area #2 `Redo Buffers' containing Subareas 1-1
Total size 0000000000870000 Minimum Subarea size 00000000
Area Subarea Shmid Stable Addr Actual Addr
2 1 3735560 0x00000060220000 0x00000060220000
Subarea size Segment size
0000000000870000 0000000001000000
Area #3 `Base Allocator Control' containing Subareas 3-3
Total size 0000000000002000 Minimum Subarea size 00000000
Area Subarea Shmid Stable Addr Actual Addr
3 3 3735560 0x00000060ffe000 0x00000060ffe000
Subarea size Segment size
0000000000002000 0000000001000000
Area #4 `Slab Allocator Control' containing Subareas 2-2
Total size 000000000056e000 Minimum Subarea size 00000000
Area Subarea Shmid Stable Addr Actual Addr
4 2 3735560 0x00000060a90000 0x00000060a90000
Subarea size Segment size
000000000056e000 0000000001000000
Area #5 `skgm overhead' containing Subareas 5-5
Total size 0000000000002000 Minimum Subarea size 00000000
Area Subarea Shmid Stable Addr Actual Addr
5 5 3801098 0x000000ac000000 0x000000ac000000
Subarea size Segment size
0000000000002000 0000000000200000
Dump of Linux-specific skgm context
sharedmmu 00000001
shareddec 0
used region 0: start 0000000060000000 length 000000004d000000
used region 1: start 0000003e61000000 length 0000000003000000
used region 2: start 0000003e66000000 length 0000000001000000
Maximum processes: = 800
Number of semaphores per set: = 201
Semaphores key overhead per set: = 4
User Semaphores per set: = 197
Number of semaphore sets: = 5
Semaphore identifiers: = 5
Semaphore List=
2097154
2129923
2162692
2195461
2228230
-------------- system semaphore information -------------
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x00000000 2031617 root 644 80 2
0x00000000 2064386 root 644 16384 2
0x00000000 2097155 root 644 280 2
0x00000000 2359301 grid 640 4096 0
0x00000000 2392070 grid 640 4096 0
0xed304ac0 2424839 grid 640 4096 0
0x00000000 3735560 oracle 640 4096 0
0x00000000 3768329 oracle 640 4096 0
0x62385348 3801098 oracle 640 4096 0
------ Semaphore Arrays --------
key semid owner perms nsems
0x869d3e0c 262145 grid 640 124
0xb5514170 2097154 oracle 640 201
0xb5514171 2129923 oracle 640 201
0xb5514172 2162692 oracle 640 201
0xb5514173 2195461 oracle 640 201
0xb5514174 2228230 oracle 640 201
------ Message Queues --------
key msqid owner perms used-bytes messages
ksxpdmp: facility 0 (?) (0x0, (nil)) counts 0, 0
Dumping the osd state
Dumping the osd context (brief)
SKGXP:[7f31b7724c68.0]{ctx}: SKGXPCTX: 0x0x7f31b7724c68 ctx
SKGXP:[7f31b7724c68.1]{ctx}: Compatible: 0 0.0 0
SKGXP:[7f31b7724c68.2]{ctx}: SKGXP Versions: 3.3.4.2.2.c0.4(3.2.4.1)
SKGXP:[7f31b7724c68.3]{ctx}: DBG flags1: 0
SKGXP:[7f31b7724c68.4]{ctx}: DBG post_type: 0
SKGXP:[7f31b7724c68.5]{ctx}: DBG post_sig: 0
SKGXP:[7f31b7724c68.6]{ctx}: DBG post_send_thresh: 0
SKGXP:[7f31b7724c68.7]{ctx}: DBG post_timing: 0
SKGXP:[7f31b7724c68.8]{ctx}: DBG post_trace_all: 0
SKGXP:[7f31b7724c68.9]{ctx}: DBG dev_poll: 0
SKGXP:[7f31b7724c68.10]{ctx}:
SKGXP:[7f31b7724c68.11]{ctx}: WAIT HISTORY
SKGXP:[7f31b7724c68.12]{ctx}: Wait Time Time since Fast reaps Wait Type Return Code
SKGXP:[7f31b7724c68.13]{ctx}: (ms) prev wait(ms) before
SKGXP:[7f31b7724c68.14]{ctx}: --------- -------------- ----------- --------- -----------
SKGXP:[7f31b7724c68.15]{ctx}: 0 0 0 NORMAL invalid status code
SKGXP:[7f31b7724c68.16]{ctx}: 0 0 0 NORMAL invalid status code
SKGXP:[7f31b7724c68.17]{ctx}: 0 0 0 NORMAL invalid status code
SKGXP:[7f31b7724c68.18]{ctx}: 0 0 0 NORMAL invalid status code
SKGXP:[7f31b7724c68.19]{ctx}: 0 0 0 NORMAL invalid status code
SKGXP:[7f31b7724c68.20]{ctx}: 0 0 0 NORMAL invalid status code
SKGXP:[7f31b7724c68.21]{ctx}: 0 0 0 NORMAL invalid status code
SKGXP:[7f31b7724c68.22]{ctx}: 0 0 0 NORMAL invalid status code
SKGXP:[7f31b7724c68.23]{ctx}: 0 0 0 NORMAL invalid status code
SKGXP:[7f31b7724c68.24]{ctx}: 0 0 0 NORMAL invalid status code
SKGXP:[7f31b7724c68.25]{ctx}: 0 0 0 NORMAL invalid status code
SKGXP:[7f31b7724c68.26]{ctx}: 0 0 0 NORMAL invalid status code
SKGXP:[7f31b7724c68.27]{ctx}: 0 0 0 NORMAL invalid status code
SKGXP:[7f31b7724c68.28]{ctx}: 0 0 0 NORMAL invalid status code
SKGXP:[7f31b7724c68.29]{ctx}: 0 0 0 NORMAL invalid status code
SKGXP:[7f31b7724c68.30]{ctx}: 0 0 0 NORMAL invalid status code
SKGXP:[7f31b7724c68.31]{ctx}: wait delta 3 sec (3883 msec) ctx ts 0x0 last ts 0x0
SKGXP:[7f31b7724c68.32]{ctx}: user cpu time since last wait 0 sec 140733193388032 ticks
SKGXP:[7f31b7724c68.33]{ctx}: system cpu time since last wait 0 sec 140733193388032 ticks
SKGXP:[7f31b7724c68.34]{ctx}: locked 2
SKGXP:[7f31b7724c68.35]{ctx}: blocked 0
SKGXP:[7f31b7724c68.36]{ctx}: timed wait receives 0
SKGXP:[7f31b7724c68.37]{ctx}: fast reaps since last wait 0
SKGXP:[7f31b7724c68.38]{ctx}: context timestamp 0
SKGXP:[7f31b7724c68.39]{ctx}: flags=1 flags1=30 zcpyflg=5824 iflags=820 aflags=80 trcflags=0 trclevel=3
SKGXP:[7f31b7724c68.40]{ctx}: rcvbuf=131072 sndbuf=262144
SKGXP:[7f31b7724c68.41]{ctx}:
SKGXP:[7f31b7724c68.42]{ctx}: admno 0x5c339b5a admport:
SKGXP:[7f31b7724c68.43]{ctx}: SSKGXPT 0x7f31b7726390 flags 0x5 { READPENDING } sockno 5 IP 169.254.218.13 UDP 49793 lerr 0
SKGXP:[7f31b7724c68.44]{ctx}:
SKGXP:[7f31b7724c68.45]{ctx}: post port:
SKGXP:[7f31b7724c68.46]{ctx}: SSKGXPT 0x7f31b77267e8 flags 0x0 sockno 8 IP 127.0.0.1 UDP 26916 lerr 0
SKGXP:[7f31b7724c68.47]{ctx}:
SKGXP:[7f31b7724c68.48]{ctx}: sconno [693611d6, 693611d6]=0 aconno [507a7b6d, 507a7b6d]=0
SKGXP:[7f31b7724c68.49]{ctx}:
SKGXP:[7f31b7724c68.50]{ctx}:
SKGXP:[7f31b7724c68.51]{ctx}: memory (native) allocs 5 free 1 lost 0 out 5712 max 32768
SKGXP:[7f31b7724c68.52]{ctx}:
SKGXP:[7f31b7724c68.53]{ctx}: ctx(10296) sctx(1920) rqh(1040) cid(24)
SKGXP:[7f31b7724c68.54]{ctx}: prt(464) cnh(1936/15040) ach(1544/14648) rpc(2400) pid(64)
SKGXP:[7f31b7724c68.55]{ctx}: rgnst(472) rgnpt(248) rgn(8056) rbd(120) bid(64) mcph(7872/20976) mupdh(1144/14248)
SKGXP:[7f31b7724c68.56]{ctx}: mcb(852008) smap(4184) nsm(2084) me(1040) mcbe(48) mcbi(24) epid(40)
SKGXP:[7f31b7724c68.57]{ctx}: mhdr(76) fhdr(28) madm(272) aggpid(32)
SKGXP:[7f31b7724c68.58]{ctx}: sta msc(448) cnh(344) prt(216) ep(48)
SKGXP:[7f31b7724c68.59]{ctx}: aggpt(192) swin(384) finfo(176) segf(200)
SKGXP:[7f31b7724c68.60]{ctx}:
SKGXP:[7f31b7724c68.61]{ctx}: done Queue
SKGXP:[7f31b7724c68.62]{ctx}: no completed requests
SKGXP:[7f31b7724c68.63]{ctx}:
SKGXP:[7f31b7724c68.64]{ctx}: connection Queue
SKGXP:[7f31b7724c68.65]{ctx}: no pending connect disconnect operations
SKGXP:[7f31b7724c68.66]{ctx}:
SKGXP:[7f31b7724c68.67]{ctx}: sends waiting to be transmitted
SKGXP:[7f31b7724c68.68]{ctx}: no sends waiting to be transmitted
SKGXP:[7f31b7724c68.69]{ctx}:
SKGXP:[7f31b7724c68.70]{ctx}: pending ack Queue
SKGXP:[7f31b7724c68.71]{ctx}: no send requests pending ack
SKGXP:[7f31b7724c68.72]{ctx}:
SKGXP:[7f31b7724c68.73]{ctx}: Vrpc requests pending reply
SKGXP:[7f31b7724c68.74]{ctx}:
SKGXP:[7f31b7724c68.75]{ctx}: Port queue
SKGXP:[7f31b7724c68.76]{ctx}:
SKGXP:[7f31b7724c68.77]{ctx}: Region queue
SKGXP:[7f31b7724c68.78]{ctx}: SKGXPRGN: 0x7f31b6efdd30
SKGXP:[7f31b7724c68.79]{ctx}: region id 0xcf2f rgn idx: 0 rgn key: 127980261
SKGXP:[7f31b7724c68.80]{ctx}: base address 0x61000000 size: 1258291200
SKGXP:[7f31b7724c68.81]{ctx}: flags 0x0 state: 0x2 largest buffer: 0
SKGXP:[7f31b7724c68.82]{ctx}: num bids prepared: 0
SKGXP:[7f31b7724c68.83]{ctx}: SKGXPRGNSTATE: 0x7f31b77261a0
SKGXP:[7f31b7724c68.84]{ctx}: rgns mapped: 1 num shared: 1 max: 1
SKGXP:[7f31b7724c68.85]{ctx}: flags: 0 bseqno: 19445 nxtrgnno: 53039
SKGXP:[7f31b7724c68.86]{ctx}: shared ports open: 1 limits (1,16)
SKGXP:[7f31b7724c68.87]{ctx}: shared bids prepared: 0 hiwat: 0
SKGXP:[7f31b7724c68.88]{ctx}: space - used: 0 max possible: 4194304 sock limit: 524288
SKGXP:[7f31b7724c68.89]{ctx}: rgnarr[0x7f31b772e718(32)] rgnpts[0]=0x7f31b772e838
SKGXP:[7f31b7724c68.90]{ctx}: REGION ARRAY
SKGXP:[7f31b7724c68.91]{ctx}: rgn mapped[0] = 0x7f31b6efdd30
SKGXP:[7f31b7724c68.92]{ctx}: SHARED PORT ARRAY
SKGXP:[7f31b7724c68.93]{ctx}: rgn port[0]=0x7f31b772e838
SKGXP:[7f31b7724c68.94]{ctx}: SKGXPRGNPORT: 0x7f31b772e838
SKGXP:[7f31b7724c68.95]{ctx}: nbids: 0 space: 0 used: 0
SKGXP:[7f31b7724c68.96]{ctx}: SSKGXPT 0x7f31b772e848 flags 0x0 sockno 13 IP 169.254.218.13 UDP 30898 lerr 0
SKGXP:[7f31b7724c68.97]{ctx}: SKGXPGPID Internet address 169.254.218.13 UDP port number 30898
SKGXP:[7f31b7724c68.98]{ctx}:
SKGXP:[7f31b7724c68.99]{ctx}: Dumping Connection Handle Table
SKGXP:[7f31b7724c68.100]{ctx}: hdl sconno aconno admno RmtPid state seq# msgs rtrans credits rtt last ack id ip
SKGXP:[7f31b7724c68.101]{ctx}:
SKGXP:[7f31b7724c68.102]{ctx}: Dumping Accept Handle Table
SKGXP:[7f31b7724c68.103]{ctx}:
Done dumping the osd state
Dumping ksxp state
ksxppg=0x7f31b71e47a8 ksxpsg=0xa7584ed8 ksxpsg_a=0xa7584ed8ksxpssg=0xa7584c20 rm=0xa7584b98
proc state: (pid: 38) [flg: 1 sg: 1]
curts 1358838759 wtctr 0
Dumping ksxp contexts
Context[2] 0x7f31b6f06430 GES state 1
Dumping region queue
region count: 0
Dumping connection queue
connection count: 0
Dumping done requests queue
done requests count: 0
Dumping mupq requests queue
mupq requests count: 0
Dumping zombie requests queue
zombie requests count: 0
Dumping delayed callback requests queue
delayed callback requests count: 0
Context[1] 0x7f31b6effcc0 gc ksxp component context state 1
Dumping region queue
region count: 1
Dumping connection queue
connection count: 0
Dumping done requests queue
done requests count: 0
Dumping mupq requests queue
mupq requests count: 0
Dumping zombie requests queue
zombie requests count: 0
Dumping delayed callback requests queue
delayed callback requests count: 0
Dumping pending request queue
pending request count: 0

*** 2013-01-22 15:12:39.785
Oradebug command 'ipc' console output:
Information written to trace file.

*** 2013-01-22 15:12:43.443
Processing Oradebug command 'tracefile_name'

*** 2013-01-22 15:12:43.443
Oradebug command 'tracefile_name' console output:
/u01/app/oracle/diag/rdbms/zhongwc/zhongwc1/trace/zhongwc1_ora_31553.trc

linux

，

Statement

The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

What are stored procedures in MySQL?May 01, 2025 am 12:27 AM

Stored procedures are precompiled SQL statements in MySQL for improving performance and simplifying complex operations. 1. Improve performance: After the first compilation, subsequent calls do not need to be recompiled. 2. Improve security: Restrict data table access through permission control. 3. Simplify complex operations: combine multiple SQL statements to simplify application layer logic.

How does query caching work in MySQL?May 01, 2025 am 12:26 AM

The working principle of MySQL query cache is to store the results of SELECT query, and when the same query is executed again, the cached results are directly returned. 1) Query cache improves database reading performance and finds cached results through hash values. 2) Simple configuration, set query_cache_type and query_cache_size in MySQL configuration file. 3) Use the SQL_NO_CACHE keyword to disable the cache of specific queries. 4) In high-frequency update environments, query cache may cause performance bottlenecks and needs to be optimized for use through monitoring and adjustment of parameters.

What are the advantages of using MySQL over other relational databases?May 01, 2025 am 12:18 AM

The reasons why MySQL is widely used in various projects include: 1. High performance and scalability, supporting multiple storage engines; 2. Easy to use and maintain, simple configuration and rich tools; 3. Rich ecosystem, attracting a large number of community and third-party tool support; 4. Cross-platform support, suitable for multiple operating systems.

How do you handle database upgrades in MySQL?Apr 30, 2025 am 12:28 AM

The steps for upgrading MySQL database include: 1. Backup the database, 2. Stop the current MySQL service, 3. Install the new version of MySQL, 4. Start the new version of MySQL service, 5. Recover the database. Compatibility issues are required during the upgrade process, and advanced tools such as PerconaToolkit can be used for testing and optimization.

What are the different backup strategies you can use for MySQL?Apr 30, 2025 am 12:28 AM

MySQL backup policies include logical backup, physical backup, incremental backup, replication-based backup, and cloud backup. 1. Logical backup uses mysqldump to export database structure and data, which is suitable for small databases and version migrations. 2. Physical backups are fast and comprehensive by copying data files, but require database consistency. 3. Incremental backup uses binary logging to record changes, which is suitable for large databases. 4. Replication-based backup reduces the impact on the production system by backing up from the server. 5. Cloud backups such as AmazonRDS provide automation solutions, but costs and control need to be considered. When selecting a policy, database size, downtime tolerance, recovery time, and recovery point goals should be considered.

What is MySQL clustering?Apr 30, 2025 am 12:28 AM

MySQLclusteringenhancesdatabaserobustnessandscalabilitybydistributingdataacrossmultiplenodes.ItusestheNDBenginefordatareplicationandfaulttolerance,ensuringhighavailability.Setupinvolvesconfiguringmanagement,data,andSQLnodes,withcarefulmonitoringandpe

How do you optimize database schema design for performance in MySQL?Apr 30, 2025 am 12:27 AM

Optimizing database schema design in MySQL can improve performance through the following steps: 1. Index optimization: Create indexes on common query columns, balancing the overhead of query and inserting updates. 2. Table structure optimization: Reduce data redundancy through normalization or anti-normalization and improve access efficiency. 3. Data type selection: Use appropriate data types, such as INT instead of VARCHAR, to reduce storage space. 4. Partitioning and sub-table: For large data volumes, use partitioning and sub-table to disperse data to improve query and maintenance efficiency.

How can you optimize MySQL performance?Apr 30, 2025 am 12:26 AM

TooptimizeMySQLperformance,followthesesteps:1)Implementproperindexingtospeedupqueries,2)UseEXPLAINtoanalyzeandoptimizequeryperformance,3)Adjustserverconfigurationsettingslikeinnodb_buffer_pool_sizeandmax_connections,4)Usepartitioningforlargetablestoi

See all articles