Oracle 11gR2 RAC添加新节点错误之--IP子网掩码
Oracle11gR2RAC添加新节点错误之--IP子网掩码系统环境:操作系统:RedHatEL5Cluster:OracleGI(GridInfrastructure)Oracle:Oracle11.2.0.1.0如图所示:RAC系统
Oracle 11gR2 RAC添加新节点错误之--IP子网掩码
系统环境:
操作系统:RedHat EL5
Cluster: Oracle GI(Grid Infrastructure)
Oracle: Oracle 11.2.0.1.0
如图所示:RAC 系统架构
对于Oracle 11G构建RAC首先需要构建GI(Grid Infrastructure)的架构
案例分析:
在Oracle 11gR2 RAC在添加新节点时,添加grid,在node3上执行root.sh时,出现以下错误:
[root@lxh3 ~]# /u01/11.2.0/grid/root.sh
Running Oracle 11g root.sh script... The following environment variables are set as: ORACLE_OWNER= grid ORACLE_HOME= /u01/11.2.0/grid Enter the full pathname of the local bin directory: [/usr/local/bin]: Copying dbhome to /usr/local/bin ... Copying oraenv to /usr/local/bin ... Copying coraenv to /usr/local/bin ... Creating /etc/oratab file... Entries will be added to the /etc/oratab file as needed by Database Configuration Assistant when a database is created Finished running generic part of root.sh script. Now product-specific root actions will be performed. 2014-07-10 15:00:36: Parsing the host name 2014-07-10 15:00:36: Checking for super user privileges 2014-07-10 15:00:36: User has super user privileges Using configuration parameter file: /u01/11.2.0/grid/crs/install/crsconfig_params Creating trace directory LOCAL ADD MODE Creating OCR keys for user 'root', privgrp 'root'.. Operation successful. Adding daemon to inittab CRS-4123: Oracle High Availability Services has been started. ohasd is starting CRS-4402: The CSS daemon was started in exclusive mode but found an active CSS daemon on node lxh1, number 1, and is terminating An active cluster was found during exclusive startup, restarting to join the cluster CRS-2672: Attempting to start 'ora.mdnsd' on 'lxh3' CRS-2676: Start of 'ora.mdnsd' on 'lxh3' succeeded CRS-2672: Attempting to start 'ora.gipcd' on 'lxh3' CRS-2676: Start of 'ora.gipcd' on 'lxh3' succeeded CRS-2672: Attempting to start 'ora.gpnpd' on 'lxh3' CRS-2676: Start of 'ora.gpnpd' on 'lxh3' succeeded CRS-2672: Attempting to start 'ora.cssdmonitor' on 'lxh3' CRS-2676: Start of 'ora.cssdmonitor' on 'lxh3' succeeded CRS-2672: Attempting to start 'ora.cssd' on 'lxh3' CRS-2672: Attempting to start 'ora.diskmon' on 'lxh3' CRS-2676: Start of 'ora.diskmon' on 'lxh3' succeeded CRS-2676: Start of 'ora.cssd' on 'lxh3' succeeded CRS-2672: Attempting to start 'ora.ctssd' on 'lxh3' CRS-2676: Start of 'ora.ctssd' on 'lxh3' succeeded CRS-2672: Attempting to start 'ora.drivers.acfs' on 'lxh3' CRS-2676: Start of 'ora.drivers.acfs' on 'lxh3' succeeded CRS-2672: Attempting to start 'ora.asm' on 'lxh3' CRS-2676: Start of 'ora.asm' on 'lxh3' succeeded CRS-2672: Attempting to start 'ora.crsd' on 'lxh3' CRS-2676: Start of 'ora.crsd' on 'lxh3' succeeded CRS-2672: Attempting to start 'ora.evmd' on 'lxh3' CRS-2676: Start of 'ora.evmd' on 'lxh3' succeeded Timed out waiting for the CRS stack to start.CRSD服务启动失败!
查看日志:
[root@lxh3 crsd]# more crsdOUT.log
2014-07-10 15:03:56
Changing directory to /u01/11.2.0/grid/log/lxh3/crsd 2014-07-10 15:03:56 CRSD REBOOT CRSD exiting: Could not init OCR, code: 442014-07-10 15:03:58 Changing directory to /u01/11.2.0/grid/log/lxh3/crsd 2014-07-10 15:03:58 CRSD REBOOT CRSD exiting: Could not init OCR, code: 442014-07-10 15:04:00 Changing directory to /u01/11.2.0/grid/log/lxh3/crsd 2014-07-10 15:04:00 CRSD REBOOT CRSD exiting: Could not init OCR, code: 442014-07-10 15:04:02 Changing directory to /u01/11.2.0/grid/log/lxh3/crsd 2014-07-10 15:04:02 CRSD REBOOT CRSD exiting: Could not init OCR, code: 442014-07-10 15:04:04 Changing directory to /u01/11.2.0/grid/log/lxh3/crsd 2014-07-10 15:04:04 CRSD REBOOT CRSD exiting: Could not init OCR, code: 442014-07-10 15:04:06 Changing directory to /u01/11.2.0/grid/log/lxh3/crsd 2014-07-10 15:04:06 CRSD REBOOT CRSD exiting: Could not init OCR, code: 442014-07-10 15:04:08 Changing directory to /u01/11.2.0/grid/log/lxh3/crsd 2014-07-10 15:04:08 CRSD REBOOT CRSD exiting: Could not init OCR, code: 442014-07-10 15:04:10 Changing directory to /u01/11.2.0/grid/log/lxh3/crsd 2014-07-10 15:04:10 CRSD REBOOT CRSD exiting: Could not init OCR, code: 442014-07-10 15:04:12 Changing directory to /u01/11.2.0/grid/log/lxh3/crsd 2014-07-10 15:04:12 CRSD REBOOT CRSD exiting: Could not init OCR, code: 442014-07-10 15:04:14 Changing directory to /u01/11.2.0/grid/log/lxh3/crsd 2014-07-10 15:04:14 CRSD REBOOT CRSD exiting: Could not init OCR, code: 442014-07-10 15:04:16 Changing directory to /u01/11.2.0/grid/log/lxh3/crsd 2014-07-10 15:04:16 CRSD REBOOT CRSD exiting: Could not init OCR, code: 44
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

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Table of Contents Solution 1 Solution 21. Delete the temporary files of Windows update 2. Repair damaged system files 3. View and modify registry entries 4. Turn off the network card IPv6 5. Run the WindowsUpdateTroubleshooter tool to repair 6. Turn off the firewall and other related anti-virus software. 7. Close the WidowsUpdate service. Solution 3 Solution 4 "0x8024401c" error occurs during Windows update on Huawei computers Symptom Problem Cause Solution Still not solved? Recently, the web server needs to be updated due to system vulnerabilities. After logging in to the server, the update prompts error code 0x8024401c. Solution 1

The retention period of Oracle database logs depends on the log type and configuration, including: Redo logs: determined by the maximum size configured with the "LOG_ARCHIVE_DEST" parameter. Archived redo logs: Determined by the maximum size configured by the "DB_RECOVERY_FILE_DEST_SIZE" parameter. Online redo logs: not archived, lost when the database is restarted, and the retention period is consistent with the instance running time. Audit log: Configured by the "AUDIT_TRAIL" parameter, retained for 30 days by default.

The Oracle database startup sequence is: 1. Check the preconditions; 2. Start the listener; 3. Start the database instance; 4. Wait for the database to open; 5. Connect to the database; 6. Verify the database status; 7. Enable the service (if necessary ); 8. Test the connection.

The amount of memory required by Oracle depends on database size, activity level, and required performance level: for storing data buffers, index buffers, executing SQL statements, and managing the data dictionary cache. The exact amount is affected by database size, activity level, and required performance level. Best practices include setting the appropriate SGA size, sizing SGA components, using AMM, and monitoring memory usage.

To find the number of occurrences of a character in Oracle, perform the following steps: Get the total length of a string; Get the length of the substring in which a character occurs; Count the number of occurrences of a character by subtracting the substring length from the total length.

Oracle database server hardware configuration requirements: Processor: multi-core, with a main frequency of at least 2.5 GHz. For large databases, 32 cores or more are recommended. Memory: At least 8GB for small databases, 16-64GB for medium sizes, up to 512GB or more for large databases or heavy workloads. Storage: SSD or NVMe disks, RAID arrays for redundancy and performance. Network: High-speed network (10GbE or higher), dedicated network card, low-latency network. Others: Stable power supply, redundant components, compatible operating system and software, heat dissipation and cooling system.

Oracle can read dbf files through the following steps: create an external table and reference the dbf file; query the external table to retrieve data; import the data into the Oracle table.

The amount of memory required for an Oracle database depends on the database size, workload type, and number of concurrent users. General recommendations: Small databases: 16-32 GB, Medium databases: 32-64 GB, Large databases: 64 GB or more. Other factors to consider include database version, memory optimization options, virtualization, and best practices (monitor memory usage, adjust allocations).
