No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

OceanStor BCManager 6.5.0 eReplication User Guide 02

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Starting Oracle Database Listeners

Starting Oracle Database Listeners

During an Oracle database test, if the database listeners are not started after the database is started, the database becomes inaccessible. In this case, you must start the database listeners.

Multiple listeners may be configured in listener.ora of an Oracle database. Whether to start all listeners or which listeners should be started are determined by actual service scenarios. Therefore, database listeners are not started by default.

Modifying the Script to Start Database Listeners

Add the postscript for starting database listeners after the database startup procedure in the recovery process based on actual service scenarios. The following procedure uses Linux as an example to describe how to modify the script to start database listeners:

  1. Copy the sample.sh script to the thirdparty directory.

    The path to sample.sh is as follows:

    • Windows

      %OceanStor BCManager Agent install path%\bin\thirdparty\sample

    • Non-Windows

      /home/rdadmin/Agent/bin/thirdparty/sample

    NOTE:

    You are advised to change the script name after copying the script.

  2. Modify the script by referring to the following example:

    
    ########Begin########
    echo "Begin to do something." >> ${LOGFILE}
    su -grid -c "lsnrctl start" >> ${LOGFILE}                      
    #Start the default listener. Whether the startup account grid or oracle is used is determined by the onsite environment.
    su -grid -c "lsnrctl start LISTENER1" >> ${LOGFILE}            
    #Start a non-default listener. LISTENER1 indicates the name of the non-default listener. 
    #If no non-default listener exists, you do not need to run this command.
    echo "Finish doing something." >> ${LOGFILE}
    ########End#######
    

  3. Add a listener startup script in the recovery process. For details, see Self-defining Execution Steps in a Recovery Plan.

Manually Starting Database Listeners

The following procedure uses Oracle 11R2 as an example to describe how to manually start database listeners:

  1. Determine whether the listener startup account is oracle or grid.
  2. Run the su -grid or su -oracle command to switch to the listener startup account.
  3. Run the lsnrctl start command to start the default listener.

    If there are multiple listeners, specify their names. Run the lsnrctl start LISTENER1 command to start non-default listeners. In this command, LISTENER1 indicates the name of a non-default listener.

  4. Run the lsnrctl status command to view the status of the default listener.

    If there are multiple listeners, specify their names. Run the lsnrctl status LISTENER1 command to view the status of non-default listeners. In this command, LISTENER1 indicates the name of a non-default listener.

Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 10614

Downloads: 55

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next