1. You need to modify the $ CRS_HOME/bin/racgvip script before running the root. sh script in the last step of crs installation. Otherwise, the vip cannot be started. The modification method is as follows:
# Cd $ CRS_HOME/bin
# Cp racgvip. old
# Vi racgvip
Change $5 from the three rows of 221,231,371 to $6.
2. Run root at the second point. sh reported Oracle cluster verification utility from VIPCA finally reported crs-0223 manual view crs_stat status, found that a resource is not up, an error occurred while trying to manually start and operate the oracle cluster verification utility is normal after the "Retry" button is clicked in the pop-up window
3. Upgrade crs to 10.2.0.4. After running root02.sh, the vip becomes unable to start again. In this case, you need to modify $ CRS_HOME/bin/racgvip again by the following method:
Note that you need to modify it after running root02.sh.
# Cd $ CRS_HOME/bin
# Cp racgvip racgvip.10204.old
# Vi racgvip
Change $5 from row 263,275 to $6.
4. During the process of upgrading rdbms to 10.2.0.4, a window will pop up to report that the java Process is running and upgrade is not allowed. This is another bug. The modification method is as follows:
# Mv/usr/sbin/fuser. old
# Touch/usr/sbin/fuser
Then, click "Retry" in the pop-up window to complete the rdbms upgrade.
5. Because the fuser command was deleted in Step 4, an error was reported when the host was restarted and HA was started. If the fuser. old command was restored or an error was reported, it was found that the related permissions were incorrect.