Oracle9i RAC for aix 5.2 installation help go up in smoke. Two P550 : AIX hardware, EMC storage. AIX 5.2 operating system : Software : IBM HACMP 5.2, Oracle 9.2.0.0 Oracle RAC model for the installation, the installation of Oracle, it is not a "Cluster Node Selection" interface, what is the reason? HA installation of the nodes can take over and take over the volume group. Http://www.unixblog.net/index.php?blog=6&p=316 reference files : This appears and environmental variables, environment variables are set up to see Can PATH=/usr/bin:/etc:/usr/sbin:/usr/ucb:$HOME/bin:/usr/bin/X11:/sbin :. PATH=$PATH:/usr/ccs/bin:/usr/bin:/etc Export PATH=$PATH:/usr/bin/X11:/sbin:/usr/ccs/bin:/usr/bin Oracle is the client's environment variables? Just tried to choose the interface or can not have a mass assembly points. Oui hacmp must have started when opened. This problem and the environmental variables, the following are my aix install Oracle 5.2 5.2 hacmp use environment variables PATH=/usr/bin:/etc:/usr/sbin:/usr/ucb:$HOME/bin:/usr/bin/X11:/sbin :. PATH=$PATH:/usr/ccs/bin:/usr/bin:/etc Export PATH If [-s "$MAIL" Shell] # This is at startup. In normal Then echo "$MAILMSG" # operation, the Shell checks Fi # periodically. Export ORACLE_HOME=/oracle/product/9.2.0 Export ORA_NLS33=/oracle/product/9.2.0/ocommon/nls/admin/data Export DISPLAY=192.168.0.5:0.0 Export ORACLE_SID=orcl1 Export PATH=$PATH:/usr/bin/X11:/sbin:/usr/ccs/bin:/usr/bin Export PATH=$PATH:/etc:/u01/app/oracle/product/9.2.0/bin Export ORACLE_BASE=/u01/app/oracle Export DBCA_RAW_CONFIG=/home/oracle/rawconfig PGSD_SUBSYS=grpsvcs;export PGSD_SUBSYS Very grateful to your profile and it can copy the entire document. I used the wrong places that may result. RAC pattern emerged in the establishment of a database error PRKR-1005 Two P550 : AIX hardware, EMC storage. AIX 5.2 operating system : Software : IBM HACMP 5.2, Oracle 9.2.0.6 The authority has been given oracle:dba nude equipment. In the creation of a database error. From the set after losing phenomenon occurred nude equipment. Before creating a database : #cd /dev #ls L ro9* Oracle dba crw-rw---- 1 52 13 Dec 31 14:07 ro9_cntrl1_128m Oracle dba crw-rw---- 1 52 14 Dec 31 14:07 ro9_cntrl2_128m Oracle dba crw-rw---- 1 52 15 Dec 31 14:07 ro9_cntrl3_128m Oracle dba crw-rw---- 1 52 17 Dec 31 14:07 ro9_drsys_512m Oracle dba crw-rw---- 1 52 11 Dec 31 14:07 ro9_indx_512m Oracle dba crw-rw---- 1 52 7 Dec 31 14:07 ro9_log11_128m Oracle dba crw-rw---- 1 52 8 Dec 31 14:07 ro9_log12_128m Oracle dba crw-rw---- 1 52 9 Dec 31 14:07 ro9_log21_128m Oracle dba crw-rw---- 1 52 10 Dec 31 14:07 ro9_log22_128m Oracle dba crw-rw---- 1 52 12 Dec 31 14:07 ro9_spfile_128m Oracle dba crw-rw---- 1 52 18 Dec 31 14:07 ro9_srvcfg_128m Oracle dba crw-rw---- 1 52 1 Dec 31 14:07 ro9_system_1g Oracle dba crw-rw---- 1 52 4 Dec 31 14:07 ro9_temp_512m Oracle dba crw-rw---- 1 52 3 31 Dec 14:07 ro9_tools_512m Oracle dba crw-rw---- 1 52 5 Dec 31 14:07 ro9_undotbs1_1g Oracle dba crw-rw---- 1 52 6 Dec 31 14:07 ro9_undotbs2_1g Oracle dba crw-rw---- 1 52 2 Dec 31 14:07 ro9_users_512m Oracle dba crw-rw---- 1 52 16 Dec 31 14:07 ro9_xdb_512m When wrong, once again address : #ls L ro9* Oracle dba crw-rw---- 1 52 13 Jan 02 09:18 ro9_cntrl1_128m Oracle dba crw-rw---- 1 52 14 Jan 02 09:18 ro9_cntrl2_128m Oracle dba crw-rw---- 1 52 15 Jan 02 09:18 ro9_cntrl3_128m Oracle dba crw-rw---- 1 52 7 Jan 02 09:18 ro9_log11_128m Oracle dba 52 crw-rw---- 1, 8 Jan 02 09:18 ro9_log12_128m Oracle dba crw-rw---- 1 52 9 Jan 02 09:18 ro9_log21_128m Oracle dba crw-rw---- 1 52 10 Jan 02 09:18 ro9_log22_128m Oracle dba crw-rw---- 1 52 12 Jan 02 09:18 ro9_spfile_128m Oracle dba crw-rw---- 1 52 18 Jan 02 09:18 ro9_srvcfg_128m Oracle dba crw-rw---- 1 52 1 Jan 02 09:18 ro9_system_1g But there are pieces of equipment : # 1s l o9* Oracle dba brw-rw---- 1 52 13 Jan 02 10:04 o9_cntrl1_128m Oracle dba brw-rw---- 1 52 14 Jan 02 10:04 o9_cntrl2_128m Oracle dba brw-rw---- 1 52 15 Jan 02 10:04 o9_cntrl3_128m Oracle dba brw-rw---- 1 52 17 Jan 02 10:04 o9_drsys_512m Oracle dba brw-rw---- 1 52 11 Jan 02 10:04 o9_indx_512m Oracle dba brw-rw---- 1 52 7 Jan 02 10:04 o9_log11_128m Oracle dba 52 brw-rw---- 1, 8 Jan 02 10:04 o9_log12_128m Oracle dba brw-rw---- 1 52 9 Jan 02 10:04 o9_log21_128m Oracle dba brw-rw---- 1 52 10 Jan 02 10:04 o9_log22_128m Oracle dba brw-rw---- 1 52 12 Jan 02 10:04 o9_spfile_128m Oracle dba brw-rw---- 1 52 18 Jan 02 10:04 o9_srvcfg_128m Oracle dba brw-rw---- 1 52 1 Jan 02 10:04 o9_system_1g Oracle dba brw-rw---- 1 52 4 Jan 02 10:04 o9_temp_512m Oracle dba brw-rw---- 1 52 3 Jan 02 10:04 o9_tools_512m Oracle dba brw-rw---- 1 52 5 Jan 02 10:04 o9_undotbs1_1g Oracle dba brw-rw---- 1 52 6 Jan 02 10:04 o9_undotbs2_1g Oracle dba brw-rw---- 1 52 2 Jan 02 10:04 o9_users_512m Oracle dba brw-rw---- 1 52 16 Jan 02 10:04 o9_xdb_512m Oracle:dba piece of equipment here has the authority to the same problem was found. Will master guiding instructions. Thank you! Previous articles : Http://www.lslnet.com/linux/#viewthread.php?tid=678996&extra=page%3D2 Help out a top of Mt. 1 dbca database if there is a mistake in the process, dbca used to delete the data files, if the equipment used nude, nude equipment will be removed. These can be deleted district and then re-established, there has been a loss of nude equipment. In addition, according to determine if the use of the former may not kill orders to kill dbca deleted nude equipment. 2 dbca aix preferable not to use database (lessons of experience), the choice of database types to choose "New Database" can be used to create database generation script, the script for the whole or part of the operation can create a database. If this is established, there will not lead to more errors and failure to establish the database. Are likely to produce the same mistakes, but this time you can check, and then correct those mistakes, without re-running dbca, to build a database. Dbca the benefits of the use of database generation script is not only get rid of the manual database trouble, dbca action can be decomposed to facilitate acknowledged the problem. [ Closed window ]