客户10.2.0.4 RAC for Solaris 10环境突然出现了实例重启的现象。 数据库正常运行到下午3点左右,随后两个节点分别重启,其中一个节点上的实例无法自动启动。检查两个实例的告警日志发现,在节点重启前,两个节点都出现了明显的ORA-27504错误: Wed Apr 10 1
客户10.2.0.4 RAC for Solaris 10环境突然出现了实例重启的现象。
数据库正常运行到下午3点左右,随后两个节点分别重启,其中一个节点上的实例无法自动启动。检查两个实例的告警日志发现,在节点重启前,两个节点都出现了明显的ORA-27504错误:
Wed Apr 10 15:00:05 2013 Errors IN file /oracle/admin/orcl/udump/orcl1_ora_10997.trc: ORA-00603: ORACLE server SESSION TERMINATED BY fatal error ORA-27504: IPC error creating OSD context ORA-27300: OS system dependent operation:if_not_found failed WITH STATUS: 0 ORA-27301: OS failure message: Error 0 ORA-27302: failure occurred at: skgxpvaddr9 ORA-27303: additional information: requested interface 192.168.168.3 NOT found. CHECK output FROM ifconfig command Wed Apr 10 15:00:06 2013 Errors IN file /oracle/admin/orcl/udump/orcl1_ora_11007.trc: ORA-00603: ORACLE server SESSION TERMINATED BY fatal error ORA-27504: IPC error creating OSD context ORA-27300: OS system dependent operation:if_not_found failed WITH STATUS: 0 ORA-27301: OS failure message: Error 0 ORA-27302: failure occurred at: skgxpvaddr9 ORA-27303: additional information: requested interface 192.168.168.3 NOT found. CHECK output FROM ifconfig command Wed Apr 10 15:00:06 2013 Errors IN file /oracle/admin/orcl/udump/orcl1_ora_11009.trc: ORA-00603: ORACLE server SESSION TERMINATED BY fatal error ORA-27504: IPC error creating OSD context ORA-27300: OS system dependent operation:if_not_found failed WITH STATUS: 0 ORA-27301: OS failure message: Error 0 ORA-27302: failure occurred at: skgxpvaddr9 ORA-27303: additional information: requested interface 192.168.168.3 NOT found. CHECK output FROM ifconfig command Wed Apr 10 15:00:06 2013 Errors IN file /oracle/admin/orcl/udump/orcl1_ora_11011.trc: ORA-00603: ORACLE server SESSION TERMINATED BY fatal error ORA-27504: IPC error creating OSD context ORA-27300: OS system dependent operation:if_not_found failed WITH STATUS: 0 ORA-27301: OS failure message: Error 0 ORA-27302: failure occurred at: skgxpvaddr9 ORA-27303: additional information: requested interface 192.168.168.3 NOT found. CHECK output FROM ifconfig command . . . Wed Apr 10 15:07:08 2013 IPC Send timeout detected.Sender: ospid 25688 Receiver: inst 2 binc 427282 ospid 11838 Wed Apr 10 15:07:08 2013 IPC Send timeout detected.Sender: ospid 25724 Wed Apr 10 15:07:08 2013 IPC Send timeout detected.Sender: ospid 25680 Receiver: inst 2 binc 431591 ospid 11822 Receiver: inst 2 binc 431795 ospid 11874 Wed Apr 10 15:07:08 2013 IPC Send timeout detected.Sender: ospid 25684 Receiver: inst 2 binc 428985 ospid 11826 Wed Apr 10 15:07:08 2013 IPC Send timeout detected.Sender: ospid 25708 Receiver: inst 2 binc 430048 ospid 11858 Wed Apr 10 15:07:09 2013 ospid 25678: network interface WITH IP address 192.168.168.3 no longer operational requested interface 192.168.168.3 NOT found. CHECK output FROM ifconfig command Wed Apr 10 15:07:35 2013 IPC Send timeout TO 1.1 inc 4 FOR msg TYPE 44 FROM opid 7 Wed Apr 10 15:07:35 2013 IPC Send timeout TO 1.12 inc 4 FOR msg TYPE 44 FROM opid 21 Wed Apr 10 15:07:35 2013 IPC Send timeout TO 1.2 inc 4 FOR msg TYPE 44 FROM opid 8 Wed Apr 10 15:07:35 2013 IPC Send timeout TO 1.3 inc 4 FOR msg TYPE 44 FROM opid 10 Wed Apr 10 15:07:35 2013 IPC Send timeout TO 1.8 inc 4 FOR msg TYPE 44 FROM opid 15 Wed Apr 10 15:08:13 2013 ospid 25678: network interface WITH IP address 192.168.168.3 no longer operational requested interface 192.168.168.3 NOT found. CHECK output FROM ifconfig command Wed Apr 10 15:08:16 2013 IPC Send timeout detected.Sender: ospid 25748 Receiver: inst 2 binc 430164 ospid 11890 . . . Wed Apr 10 15:08:53 2013 IPC Send timeout TO 1.13 inc 4 FOR msg TYPE 36 FROM opid 176 Wed Apr 10 15:08:53 2013 IPC Send timeout TO 1.15 inc 4 FOR msg TYPE 36 FROM opid 167 Wed Apr 10 15:08:57 2013 IPC Send timeout TO 1.4 inc 4 FOR msg TYPE 32 FROM opid 180 . . . Wed Apr 10 15:15:51 2013 Evicting instance 2 FROM cluster Wed Apr 10 15:16:09 2013 ospid 25678: network interface WITH IP address 192.168.168.3 no longer operational requested interface 192.168.168.3 NOT found. CHECK output FROM ifconfig command Wed Apr 10 15:16:40 2013 Waiting FOR instances TO leave: Wed Apr 10 15:17:00 2013 Waiting FOR instances TO leave: Wed Apr 10 15:17:09 2013 ospid 25678: network interface WITH IP address 192.168.168.3 no longer operational requested interface 192.168.168.3 NOT found. CHECK output FROM ifconfig command Wed Apr 10 15:17:20 2013 Waiting FOR instances TO leave:
节点2上的错误信息与之类似:
. . . Wed Apr 10 15:19:07 2013 Errors IN file /oracle/admin/orcl/udump/orcl2_ora_14065.trc: ORA-00603: ORACLE server SESSION TERMINATED BY fatal error ORA-27504: IPC error creating OSD context ORA-27300: OS system dependent operation:if_not_found failed WITH STATUS: 0 ORA-27301: OS failure message: Error 0 ORA-27302: failure occurred at: skgxpvaddr9 ORA-27303: additional information: requested interface 192.168.168.4 NOT found. CHECK output FROM ifconfig command Wed Apr 10 15:19:08 2013 Errors IN file /oracle/admin/orcl/udump/orcl2_ora_14057.trc: ORA-00603: ORACLE server SESSION TERMINATED BY fatal error ORA-27504: IPC error creating OSD context ORA-27300: OS system dependent operation:if_not_found failed WITH STATUS: 0 ORA-27301: OS failure message: Error 0 ORA-27302: failure occurred at: skgxpvaddr9 ORA-27303: additional information: requested interface 192.168.168.4 NOT found. CHECK output FROM ifconfig command Wed Apr 10 15:19:46 2013 ospid 11820: network interface WITH IP address 192.168.168.4 no longer operational requested interface 192.168.168.4 NOT found. CHECK output FROM ifconfig command Wed Apr 10 15:20:46 2013 ospid 11820: network interface WITH IP address 192.168.168.4 no longer operational requested interface 192.168.168.4 NOT found. CHECK output FROM ifconfig command Wed Apr 10 15:20:55 2013 Errors IN file /oracle/admin/orcl/bdump/orcl2_lmon_11818.trc: ORA-29740: evicted BY member 0, GROUP incarnation 6 Wed Apr 10 15:20:55 2013 LMON: terminating instance due TO error 29740 Wed Apr 10 15:20:55 2013 Errors IN file /oracle/admin/orcl/bdump/orcl2_smon_11924.trc: ORA-29740: evicted BY member , GROUP incarnation Wed Apr 10 15:20:55 2013 Errors IN file /oracle/admin/orcl/bdump/orcl2_lmse_11886.trc: ORA-29740: evicted BY member , GROUP incarnation Wed Apr 10 16:11:37 2013 Starting ORACLE instance (normal) Wed Apr 10 16:11:45 2013 sculkget: failed TO LOCK /oracle/products/10.2/db_1/dbs/lkinstorcl2 exclusive Wed Apr 10 16:11:45 2013 sculkget: LOCK held BY PID: 6912 Wed Apr 10 16:11:45 2013 Oracle Instance Startup operation failed. Another process may be attempting TO startup OR shutdown this Instance. Wed Apr 10 16:11:45 2013 Failed TO acquire instance startup/shutdown serialization primitive Wed Apr 10 16:11:50 2013 sculkget: failed TO LOCK /oracle/products/10.2/db_1/dbs/lkinstorcl2 exclusive Wed Apr 10 16:11:50 2013 sculkget: LOCK held BY PID: 6912 Wed Apr 10 16:11:50 2013 Oracle Instance Startup operation failed. Another process may be attempting TO startup OR shutdown this Instance. Wed Apr 10 16:11:50 2013 Failed TO acquire instance startup/shutdown serialization primitive Wed Apr 10 16:11:54 2013 sculkget: failed TO LOCK /oracle/products/10.2/db_1/dbs/lkinstorcl2 exclusive Wed Apr 10 16:11:54 2013 sculkget: LOCK held BY PID: 6912 Wed Apr 10 16:11:54 2013 Oracle Instance Startup operation failed. Another process may be attempting TO startup OR shutdown this Instance. Wed Apr 10 16:11:54 2013 Failed TO acquire instance startup/shutdown serialization primitive Wed Apr 10 16:12:29 2013 sculkget: failed TO LOCK /oracle/products/10.2/db_1/dbs/lkinstorcl2 exclusive Wed Apr 10 16:12:29 2013 sculkget: LOCK held BY PID: 6912 Wed Apr 10 16:12:29 2013 Oracle Instance Startup operation failed. Another process may be attempting TO startup OR shutdown this Instance. Wed Apr 10 16:12:29 2013 Failed TO acquire instance startup/shutdown serialization primitive Wed Apr 10 16:12:47 2013 sculkget: failed TO LOCK /oracle/products/10.2/db_1/dbs/lkinstorcl2 exclusive Wed Apr 10 16:12:47 2013 sculkget: LOCK held BY PID: 6912 Wed Apr 10 16:12:47 2013 Oracle Instance Startup operation failed. Another process may be attempting TO startup OR shutdown this Instance. Wed Apr 10 16:12:47 2013 Failed TO acquire instance startup/shutdown serialization primitive Wed Apr 10 16:12:52 2013 sculkget: failed TO LOCK /oracle/products/10.2/db_1/dbs/lkinstorcl2 exclusive Wed Apr 10 16:12:52 2013 sculkget: LOCK held BY PID: 6912 Wed Apr 10 16:12:52 2013 Oracle Instance Startup operation failed. Another process may be attempting TO startup OR shutdown this Instance. Wed Apr 10 16:12:52 2013 Failed TO acquire instance startup/shutdown serialization primitive Wed Apr 10 16:12:56 2013 sculkget: failed TO LOCK /oracle/products/10.2/db_1/dbs/lkinstorcl2 exclusive Wed Apr 10 16:12:56 2013 sculkget: LOCK held BY PID: 6912 Wed Apr 10 16:12:56 2013 Oracle Instance Startup operation failed. Another process may be attempting TO startup OR shutdown this Instance. Wed Apr 10 16:12:56 2013 Failed TO acquire instance startup/shutdown serialization primitive
导致问题的原因根据错误信息很容易分析出来,节点2上的IP地址被修改,导致心跳通信出现了异常,而节点1试图将节点2踢出集群,但是由于无法和节点2之间进行通信,因此只有等待节点2重启。
检查节点2的操作系统日志:
Apr 10 15:00:04 bj-sst-xhm-3f2-m5k-02 ip: [ID 482227 kern.notice] ip_arp_done: init failed Apr 10 15:07:37 bj-sst-xhm-3f2-m5k-02 Had[4135]: [ID 702911 daemon.notice] VCS CRITICAL V-16-1-50086 CPU usage ON bj-sst-xhm-3f2-m5k-02 IS 92% Apr 10 15:18:41 bj-sst-xhm-3f2-m5k-02 sshd[13485]: [ID 800047 auth.error] error: Failed TO allocate internet-DOMAIN X11 display socket.
在15点04秒时出现的ip_arp_done: init failed信息,说明设置网卡接口时使用了主机名信息,且主机的IP地址被在线修改。
最后根据HISTORY确认,发现有人通过root登录系统,执行ifconfig –a6来检查IPV6的地址,但是命令敲错,执行了ifconfig –a 6,在a和6之间多了一个空格,导致主机所有的IP地址被设置成0.0.0.0,于是导致了上面的错误。
这再次说明,对于root这种权限用户而言,任何的不小心都可能会导致非常严重的后果。
原文地址:IP地址被清空导致实例重启, 感谢原作者分享。

MySQLoffersvariousstorageengines,eachsuitedfordifferentusecases:1)InnoDBisidealforapplicationsneedingACIDcomplianceandhighconcurrency,supportingtransactionsandforeignkeys.2)MyISAMisbestforread-heavyworkloads,lackingtransactionsupport.3)Memoryengineis

Common security vulnerabilities in MySQL include SQL injection, weak passwords, improper permission configuration, and unupdated software. 1. SQL injection can be prevented by using preprocessing statements. 2. Weak passwords can be avoided by forcibly using strong password strategies. 3. Improper permission configuration can be resolved through regular review and adjustment of user permissions. 4. Unupdated software can be patched by regularly checking and updating the MySQL version.

Identifying slow queries in MySQL can be achieved by enabling slow query logs and setting thresholds. 1. Enable slow query logs and set thresholds. 2. View and analyze slow query log files, and use tools such as mysqldumpslow or pt-query-digest for in-depth analysis. 3. Optimizing slow queries can be achieved through index optimization, query rewriting and avoiding the use of SELECT*.

To monitor the health and performance of MySQL servers, you should pay attention to system health, performance metrics and query execution. 1) Monitor system health: Use top, htop or SHOWGLOBALSTATUS commands to view CPU, memory, disk I/O and network activities. 2) Track performance indicators: monitor key indicators such as query number per second, average query time and cache hit rate. 3) Ensure query execution optimization: Enable slow query logs, record and optimize queries whose execution time exceeds the set threshold.

The main difference between MySQL and MariaDB is performance, functionality and license: 1. MySQL is developed by Oracle, and MariaDB is its fork. 2. MariaDB may perform better in high load environments. 3.MariaDB provides more storage engines and functions. 4.MySQL adopts a dual license, and MariaDB is completely open source. The existing infrastructure, performance requirements, functional requirements and license costs should be taken into account when choosing.

MySQL uses a GPL license. 1) The GPL license allows the free use, modification and distribution of MySQL, but the modified distribution must comply with GPL. 2) Commercial licenses can avoid public modifications and are suitable for commercial applications that require confidentiality.

The situations when choosing InnoDB instead of MyISAM include: 1) transaction support, 2) high concurrency environment, 3) high data consistency; conversely, the situation when choosing MyISAM includes: 1) mainly read operations, 2) no transaction support is required. InnoDB is suitable for applications that require high data consistency and transaction processing, such as e-commerce platforms, while MyISAM is suitable for read-intensive and transaction-free applications such as blog systems.

In MySQL, the function of foreign keys is to establish the relationship between tables and ensure the consistency and integrity of the data. Foreign keys maintain the effectiveness of data through reference integrity checks and cascading operations. Pay attention to performance optimization and avoid common errors when using them.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

WebStorm Mac version
Useful JavaScript development tools

mPDF
mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

EditPlus Chinese cracked version
Small size, syntax highlighting, does not support code prompt function

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software

SublimeText3 English version
Recommended: Win version, supports code prompts!
