Start and Stop OID: Hands-on Exersizes

In the hands-on examples below, you will learn how to Stop and Start OID.

Before you begin make sure you have set your $ORACLE_HOME environment parameter to the instance location where OID is installed.

For instance if OID is installed in the directory /u01/app/oracle/product/902 you should run the following command to set your $ORACLE_HOME environment parameter:

Example Unix C shell: setenv ORACLE_HOME /u01/app/oracle/product/902

Example Window: set ORACLE_HOME /u01/app/oracle/product/902

Stopping OID

Prerequisites

OID must be installed

Stop the oidldapd server processes

Example: oidctl connect=iasdb server=oidldapd instance=1 stop

This is an example of how to stop the OID default configuration set. The minimum parameters that need to be passed to OID are "connect", "server", and "instance".

The "connect" parameter passes the database SID value. In this case "iasdb".

The "server" parameter passes the OID server type value that is to be stopped. In this case "oidldapd". If you were stopping a replication server you would pass the value of "oidrepld". If you were stopping a DIP server you would pass the value "odisrv". We will discuss these other server parameter values later in this section.

The "instance" parameter passes the instance number value. OID can run multiple instance of the same server process. Being able to start multiple instance of your server process is what gives OID the ability to scale the number of users accessing OID. We will talk about this parameter im more detail later in this exercise.

Note: It is very important that you make sure the oidldapd server processes have stopped before stopping the oidmon process in the next step.

In Unix, run the command "ps -ef|grep oidldapd. If you see any oidldapd server processes still running you should wait till they are gone before continuing.

In Windows you can check this by looking at the process tab in the Task Manager. When all of the oidldapd server processes are gone you can proceed to the next step.

Stopping the "oidmon" process

The "oidmon" server process is a gardian process that keep track of all the server processes and listener threads that are running and restarts them if any of them terminate abmormally.

Example: oidmon stop

Stopping the Database

Example Unix: sqlplus '/as sysdba'

Example Windows: sqlplus "/as sysdba"

SQL> shutdown

SQL > exit

Stopping the Database listener

Example: lsnrctl stop

Heres how its done

Starting OID

Prerequisites

OID must be installed

Start the Database listener

Example: lsnrctl start

Start the Database

Example Unix: sqlplus '/as sysdba'

Example Windows: sqlplus "/as sysdba"

SQL> startup

SQL> exit

Starting the "oidmon" process

The "oidmon" server process is a gardian process that keep track of all the server processes that are running and restarts them if any of them terminate abmormally. It must be started before you start the oidldapd server processes.

Example: oidmon start

Start the oidldapd server processes

Example: oidctl connect=iasdb server=oidldapd instance=1 start

This is an example of how to start the OID default configuration set. The minimum parameters that need to be passed to OID are "connect", "server", and "instance".

The "connect" parameter passes the database sid value. In this case "iasdb".

The "server" parameter passes the OID server type value that is to be started. In this case "oidldapd". If you were starting a replication server you would pass the value of "oidrepld". If you were starting a DIP server you would pass the value "odisrv". We will discuss these other server parameter values later in this section.

The "instance" parameter passes the instance number value. OID can run multiple instance of the same server process. If you decide to start two oidldapd server processes they must have different instance number values.

Heres how its done