Starting Stopping Names Servers

Question: Within the context of "Oracle Directory Naming", does the "Names" server have to be started and stopped?
In the context of Oracle Directory Naming, the "Names" server doesn't explicitly need to be started or stopped. However, the processes and services associated with Oracle Directory Naming are managed through the opmnctl utility, which requires starting and stopping individual components.
Here's how it works:

1. Oracle Directory Naming Components:
   Oracle Directory Naming consists of several components, each with its own functionality:
   • Oracle Directory Server (ODS):Stores directory data and provides directory services.
   • Oracle Internet Directory (OID):Provides LDAP directory services.
   • Oracle Directory Integration Platform (DIP):Integrates directory data with other applications and systems.
   • Oracle Unified Directory (OUD):Combines the features of ODS and OID into a single directory server.
2. Oracle Process Manager and Control (OPMNCTL):
   OPMNCTL is a command-line tool used to manage Oracle processes and services. It allows you to:
   • Start and stop individual components of Oracle Directory Naming, such as ODS, OID, and DIP.
   • Monitor the status of running components.
   • View detailed information about running processes.
3. Starting and Stopping Oracle Directory Naming:
   There are two ways to start and stop Oracle Directory Naming:
   
   • Using opmnctl:
     

     opmnctl startall -l
     

     
     This command starts all components of Oracle Directory Naming that are registered with OPMNCTL.
     

     opmnctl stopall -l
     

     
     This command stops all components of Oracle Directory Naming that are registered with OPMNCTL.
     
   • Using individual scripts:
   
   Some components may have their own scripts for starting and stopping them, such as:
   • startWebLogic.sh for Oracle WebLogic Server
   • dsctl for Oracle Unified Directory

Therefore, while the "Names" server itself doesn't require explicit starting and stopping, you can manage the underlying processes and services through opmnctl or individual scripts depending on your environment.

The startup command for the Names server is very similar to the start command for an Oracle listener. At startup time, Net Services displays all of the relevant parameter settings. From your server prompt, simply enter namesctl start.
View the Code below to see the output of this command.

The output from the namesctl start command is very similar to the namesctl stat command: both display all of the current configuration parameters.

Dilbert > namesctl Stop
Confirm [yes or no]: yes
Server shut down

The rules for starting and stopping the Names server are identical to the rules for starting and stopping the Oracle Listener. The Names server should be started after the Oracle databases are started. At shutdown time, the Names server should be stopped prior to stopping the Oracle databases. The next lesson concludes this module.