Waiting 10 minutes for filesystem containing /u01/app/11.2.0****** during server reboot

If by any chance, your server reboot is blocked or delayed due to "waiting 10 minutes for file system" then in this case, you need to either rename /etc/init.d/ohasd to another name or open the file and comment the loop in order to skip the infinite loop during start.

the loop section is below

# Wait until it is safe to start CRS daemons.

  # Wait for 10 minutes for filesystem to mount

  # Print message to syslog and console

  works=true

  for minutes in 10 9 8 7 6 5 4 3 2 1

  do

    if [ ! -r $CRSCTL ]

    then

      works=false

      log_console "Waiting $minutes minutes for filesystem containing $CRSCTL."

      $SLEEP $DEP_CHECK_WAIT

    else

      works=true

      break

    fi

  done







AutoConfig Encounters ORA- errors in a fresh physical standby database for EBS 12.2.7

For the past few days, i was making my hands dirty on setting up a physical standby database for EBS 12.2.7. Once i had created the context file in the physical standby database and cleaned up the FND nodes, it was time for me to run autoconfig for the first time.

The first error encountered was

Encounters A ORA-1804 Error: Failure To Initialize Timezone Information

This issue was caused by the current AutoConfig template file that points to the wrong file. Issue was resolved by editing the template ad8idbux.env in location .../oracle/db/tech_st/11.2.0/appsutil/template changing:

From:
set ORA_TZFILE=%s_db_oh%\oracore\zoneinfo\timezlrg.dat

To:
set ORA_TZFILE=%s_db_oh%\oracore\zoneinfo\timezlrg_18.dat

Again i ran autoconfig and encountered the next error which was ORA-12705: Cannot Access NLS Data Files Or Invalid Environment Specified.

The solution is to run perl $ORACLE_HOME/nls/data/old/cr9idata.pl 

So at the end of the day, we should always stick on following the Oracle supported docs line by line. Hope this will help someone.