"Some
people are so afraid to die that they never begin to
live."
-Henry
Vandyke (1852-1933)
|
How
to start and stop the Oracle Internet Application Server?
Starting
an Stopping The Application Server
Starting
an Infrastructure
Using
Oracle Enterprise Manager on UNIX and Windows
This
section describes how to start an infrastructure using Oracle
Enterprise Manager on UNIX and Windows.
-
Start the metadata
repository.
-
Start the metadata
repository listener:
(UNIX)
ORACLE_HOME/bin/lsnrctl
start
(Windows)
ORACLE_HOME\bin\lsnrctl
start
-
Launch Oracle
Enterprise Manager in standalone mode:
(UNIX)
ORACLE_HOME/bin/oemapp dbastudio
(Windows)
ORACLE_HOME\bin\oemapp dbastudio
Select
Launch Standalone and click OK.
c.
Expand the Databases entry in the System Objects frame by
clicking the plus sign (+) next to it.
d.
Select the metadata repository entry.
e.
In the toolbar, select Object -> Connect. Connect as a user
with SYSDBA privileges.
f.
In the toolbar, select Object -> Startup.
2.
Start Oracle Internet Directory.
a.
Set the ORACLE_SID
is set to the metadata repository system identifier (default is iasdb).
b.
Start the Oracle Internet Directory monitor:
(UNIX)
ORACLE_HOME/bin/oidmon start
(Windows)
ORACLE_HOME\bin\oidmon start
c.
Start the Oracle Internet Directory server:
(UNIX)
ORACLE_HOME/bin/oidctl server=oidldapd configset=0 instance=n
start
(Windows)
ORACLE_HOME\bin\oidctl server=oidldapd configset=0 instance=n
start
where
n is any instance number (1,
2,
3...)
that is not in use. For example:
(UNIX)
ORACLE_HOME/bin/oidctl server=oidldapd configset=0 instance=1
start
(Windows)
ORACLE_HOME\bin\oidctl server=oidldapd configset=0 instance=1
start
3.
Start the Enterprise Manager Web site. The Web site must be
started after every system boot.
(UNIX)
You can run the following commands in the Oracle home of the primary
installation (the first installation on the host) to get status and
start the Web site:
ORACLE_HOME/bin/emctl
status
ORACLE_HOME/bin/emctl
start
(Windows)
You can check the status and start the Enterprise Manager Web site
using the Services control panel. The name of the service is in the
following format:
OracleORACLE_HOMEEMwebsite
4.
Access the Infrastructure Instance Page on the Enterprise
Manager Web site.
Point
your browser to the Enterprise Manager Web site on your host using the
following URL:
http://hostname:1810
Log
in as ias_admin.
This opens the Farm Page. Select the infrastructure instance in the
Name column in the Standalone Instances section. This opens the
Infrastructure Instance Page.
Note
that you should not click Start All. This will start OC4J instances
(OC4J_home and OC4J_Demos) that are not required and incur unnecessary
overhead. Instead, follow the rest of these steps to start only the
required components.
5.
Start Oracle HTTP Server.
a.
On the Infrastructure Instance Page, in the System Components
section, click the radio button in the Select column for HTTP Server.
b.
Click the Start button on the top right of the System
Components section.
Note
that starting Oracle HTTP Server also makes Oracle9iAS Single Sign-On
available.
6.
Start the OC4J_DAS instance.
a.
On the Infrastructure Instance Page, in the System Components
section, click the radio button in the Select column for OC4J_DAS.
b.
Click the Start button on the top right of the System
Components section.
Note
that the infrastructure instance contains other OC4J instances, such
as OC4J_home and OC4J_Demos, but these do not need to be started;
their services are not required and incur unnecessary overhead.
7.
Start Web Cache (optional).
Web
Cache is not configured in the infrastructure by default, but if you
have configured it, start it as follows:
-
On the Infrastructure
Instance Page, in the System Components section, click the radio
button in the Select column for Web Cache.
-
Click the Start
button on the top right of the System Components section.
-
Start Oracle Management
Server and Intelligent Agent (optional).
Perform
these steps only if you have configured Oracle Management Server.
-
Start Oracle
Management Server:
(UNIX)
ORACLE_HOME/bin/oemctl start oms
(Windows)
ORACLE_HOME\bin\oemctl start oms
-
Start the Intelligent
Agent.
In
order for Oracle Management Server to detect the infrastructure and
any other application server installations on this host, you must make
sure the Intelligent Agent is started. Note that one Intelligent Agent
is started per host and must be started after every reboot.
(UNIX)
You can run the following commands in the Oracle home of the primary
installation (the first installation on the host) to get status and
start the Intelligent Agent:
ORACLE_HOME/bin/agentctl
status agent
ORACLE_HOME/bin/agentctl
start agent
(Windows)
You can check the status and start the Intelligent Agent using the
Services control panel. The name of the service is in the following
format:
OracleORACLE_HOMEAgent
Starting
an Infrastructure Using Commands on UNIX
This
section describes how to start an infrastructure using command-line
tools on UNIX. Except where noted, all commands should be run in the
Oracle home of the infrastructure.
-
Start the metadata
repository.
-
Start the metadata
repository listener:
ORACLE_HOME/bin/lsnrctl
start
-
Set the ORACLE_SID
environment variable to the metadata repository system
identifier. The default ORACLE_SID
is iasdb
(Bourne
or Korn shell) ORACLE_SID=iasdb; export ORACLE_SID
(C
shell) setenv ORACLE_SID iasdb
-
Start the metadata
repository instance using SQL*Plus:
ORACLE_HOME/bin/sqlplus
/nolog
sql>
connect sys/password_for_sys
as sysdba
sql>
startup
sql>
quit
-
Start Oracle Internet
Directory.
-
Make sure the ORACLE_SID
is set to the metadata repository system identifier (refer to
previous step).
-
Start the Oracle
Internet Directory monitor:
ORACLE_HOME/bin/oidmon
start
-
Start the Oracle
Internet Directory server:
ORACLE_HOME/bin/oidctl
server=oidldapd configset=0 instance=n start
where
n is any instance number (1,
2,
3...)
that is not in use. For example:
ORACLE_HOME/bin/oidctl
server=oidldapd configset=0 instance=1 start
-
Start the Enterprise
Manager Web site.
Even
though you are using command-line, the Web site is required because it
provides underlying support for the command-line tools. The Web site
must be started after every system boot.
You
can run the following commands in the Oracle home of the primary
installation (the first installation on the host) to get status and
start the Web site:
ORACLE_HOME/bin/emctl
status
ORACLE_HOME/bin/emctl
start
-
Start Oracle HTTP
Server.
ORACLE_HOME/dcm/bin/dcmctl
start -ct ohs
Note
that starting Oracle HTTP Server also makes Oracle9iAS Single Sign-On
available.
-
Start the OC4J_DAS
instance.
ORACLE_HOME/dcm/bin/dcmctl
start -co OC4J_DAS
Note
that the infrastructure instance contains other OC4J instances, such
as OC4J_home and OC4J_Demos, but these do not need to be started;
their services are not required and incur unnecessary overhead.
-
Start Web Cache
(optional).
Web
Cache is not configured in the infrastructure by default, but if you
have configured it, start it as follows:
ORACLE_HOME/bin/webcachectl
start
-
Start Oracle Management
Server and Intelligent Agent (optional).
Perform
these steps only if you have configured Oracle Management Server.
-
Start Oracle
Management Server:
ORACLE_HOME/bin/oemctl
start oms
-
Start the Intelligent
Agent.
In
order for Oracle Management Server to detect the infrastructure and
any other application server installations on this host, you must make
sure the Intelligent Agent is started. Note that one Intelligent Agent
is started per host and must be started after every reboot.
You
can run the following commands in the Oracle home of the primary
installation (the first installation on the host) to get status and
start the Intelligent Agent:
ORACLE_HOME/bin/agentctl
status agent
ORACLE_HOME/bin/agentctl
start agent
Starting
an Infrastructure Using Commands on Windows
This
section describes how to start an infrastructure using command-line
tools on Windows. Except where noted, all commands should be run in
the Oracle home of the infrastructure.
-
Start the metadata
repository.
-
Start the metadata
repository listener:
ORACLE_HOME\bin\lsnrctl
start
-
Set the ORACLE_SID
environment variable to the metadata repository system
identifier (default is iasdb).
You
can set the ORACLE_SID system variable using the System Properties
control panel.
-
Start the metadata
repository instance using SQL*Plus:
ORACLE_HOME\bin\sqlplus
/nolog
sql>
connect sys/password_for_sys
as sysdba
sql>
startup
sql>
quit
-
Start Oracle Internet
Directory.
-
Make sure the ORACLE_SID
is set to the metadata repository system identifier (refer to
previous step).
-
Start the Oracle
Internet Directory monitor:
ORACLE_HOME\bin\oidmon
start
-
Start the Oracle
Internet Directory server:
ORACLE_HOME\bin\oidctl
server=oidldapd configset=0 instance=n start
where
n is any instance number (1,
2,
3...)
that is not in use. For example:
ORACLE_HOME\bin\oidctl
server=oidldapd configset=0 instance=1 start
-
Start the Enterprise
Manager Web site.
Even
though you are using command-line, the Web site is required because it
provides underlying support for the command-line tools. The Web site
must be started after every system boot.
You
can check the status and start the Enterprise Manager Web site using
the Services control panel. The name of the service is in the
following format:
OracleORACLE_HOMEEMwebsite
You
can also start the service using the following command line:
net
start WEB_SITE_SERVICE_NAME
-
Start Oracle HTTP
Server.
ORACLE_HOME\dcm\bin\dcmctl
start -ct ohs
Note
that starting Oracle HTTP Server also makes Oracle9iAS Single Sign-On
available.
-
Start the OC4J_DAS
instance.
ORACLE_HOME\dcm\bin\dcmctl
start -co OC4J_DAS
Note
that the infrastructure instance contains other OC4J instances, such
as OC4J_home and OC4J_Demos, but these do not need to be started;
their services are not required and incur unnecessary overhead.
-
Start Web Cache
(optional).
Web
Cache is not configured in the infrastructure by default, but if you
have configured it, start it as follows:
ORACLE_HOME\bin\webcachectl
start
-
Start Oracle Management
Server and Intelligent Agent (optional).
Perform
these steps only if you have configured Oracle Management Server.
-
Start Oracle
Management Server:
ORACLE_HOME\bin\oemctl
start oms
-
Start the Intelligent
Agent.
In
order for Oracle Management Server to detect the infrastructure and
any other application server installations on this host, you must make
sure the Intelligent Agent is started. Note that one Intelligent Agent
is started per host and must be started after every reboot.
You
can check the status and start the Intelligent Agent using the
Services control panel. The name of the service is in the following
format:
OracleORACLE_HOMEAgent
Stopping
an Infrastructure
This
section contains the following procedures for stopping an
infrastructure:
·
Stopping
an Infrastructure Using Oracle Enterprise Manager
on UNIX and Windows
·
Stopping
an Infrastructure Using Commands on UNIX
·
Stopping
an Infrastructure Using Commands on Windows
No matter
which procedure you use, stopping an infrastructure involves
performing the following steps in order:
-
Stop all middle-tier
application server instances that use the infrastructure.
-
Stop Oracle Management
Server and Intelligent Agent (optional)
-
Stop Web Cache
(optional)
-
Stop OC4J instances
-
Stop Oracle HTTP Server
-
Stop Oracle Internet
Directory
-
Stop the Metadata
Repository
Stopping
an Infrastructure Using Oracle Enterprise Manager on UNIX and Windows
This
section describes how to stop an infrastructure using Oracle
Enterprise Manager on UNIX and Windows.
-
Stop all middle-tier
application server instances that use the infrastructure.
-
Stop Oracle Management
Server and Intelligent Agent (optional).
Perform
these steps only if you have configured Oracle Management Server.
-
Stop Oracle
Management Server:
(UNIX)
ORACLE_HOME/bin/oemctl stop oms
(Windows)
ORACLE_HOME\bin\oemctl stop oms
-
Stop the Intelligent
Agent (for system shutdown only).
If
you are preparing to shut down your system, stop the Intelligent Agent
on this host.
(UNIX)
You can run the following commands in the Oracle home of the primary
installation (the first installation on the host) to get status and
stop the Intelligent Agent:
ORACLE_HOME/bin/agentctl
status agent
ORACLE_HOME/bin/agentctl
stop agent
(Windows)
You can check the status and start the Intelligent Agent using the
Services control panel. The name of the service is in the following
format:
OracleORACLE_HOMEAgent
-
Access the
Infrastructure Instance Page on the Enterprise Manager Web site.
Point
your browser to the Enterprise Manager Web site on your host using the
following URL:
http://hostname:1810
Log
in as ias_admin.
This opens the Farm Page. Select the infrastructure instance in the
Name column in the Standalone Instances section. This opens the
Infrastructure Instance Page.
Note
that you should not click Stop All. Instead, follow the rest of these
steps to stop components in the proper order.
-
Stop Web Cache
(optional).
Web
Cache is not configured in the infrastructure by default, but if you
have configured it, stop it as follows:
-
On the Infrastructure
Instance Page, in the System Components section, click the radio
button in the Select column for Web Cache.
-
Click the Stop button
on the top right of the System Components section.
-
Stop the OC4J
instances.
Stop
all running OC4J instances (OC4J_DAS, OC4J_home, OC4J_Demos) by
performing these steps on each one.
-
On the Infrastructure
Instance Page, in the System Components section, click the radio
button in the Select column for the OC4J instance.
-
Click the Stop button
on the top right of the System Components section.
-
Stop Oracle HTTP
Server.
-
On the Infrastructure
Instance Page, in the System Components section, click the radio
button in the Select column for HTTP Server.
-
Click the Stop button
on the top right of the System Components section.
Note
that stopping Oracle HTTP Server also makes Oracle9iAS Single Sign-On
unavailable.
-
Stop Oracle Internet
Directory.
-
On the Infrastructure
Instance Page, in the System Components section, click the radio
button in the Select column for Internet Directory.
-
Click the Stop button
on the top right of the System Components section.
-
Stop the metadata
repository.
-
Launch Oracle
Enterprise Manager in standalone mode:
(UNIX)
ORACLE_HOME/bin/oemapp dbastudio
(Windows)
ORACLE_HOME\bin\oemapp dbastudio
Select
Launch Standalone and click OK.
-
Expand the Databases
entry in the System Objects frame by clicking the plus sign (+)
next to it.
-
Select the metadata
repository entry.
-
In the toolbar,
select Object -> Connect. Connect as a user with SYSDBA
privileges.
-
In the toolbar,
select Object -> Shutdown.
-
Stop the metadata
repository listener:
(UNIX)
ORACLE_HOME/bin/lsnrctl
stop
(Windows)
ORACLE_HOME\bin\lsnrctl
stop
-
Stop the Enterprise
Manager Web site (system shutdown only).
If
you are preparing to shut down your system, stop the Enterprise
Manager Web site.
(UNIX)
You can run the following commands in the Oracle home of the primary
installation (the first installation on the host) to get status and
stop the Web site:
ORACLE_HOME/bin/emctl
status
ORACLE_HOME/bin/emctl
stop
(Windows)
You can check the status and stop the Enterprise Manager Web site
using the Services control panel. The name of the service is in the
following format:
OracleORACLE_HOMEEMwebsite
Stopping
an Infrastructure Using Commands on UNIX
This
section describes how to stop an infrastructure using command-line
tools on UNIX. Except where noted, all commands should be run in the
Oracle home of the infrastructure.
-
Stop all middle-tier
application server instances that use the infrastructure.
-
Stop Oracle Management
Server and Intelligent Agent (optional).
Perform
these steps only if you have configured Oracle Management Server.
-
Stop Oracle
Management Server:
If
you have configured Oracle Management Server, stop it as follows:
ORACLE_HOME/bin/oemctl
stop oms
-
Stop the Intelligent
Agent (for system shutdown only).
If
you are preparing to shut down your system, stop the Intelligent Agent
on this host.
You
can run the following commands in the Oracle home of the primary
installation (the first installation on the host) to get status and
stop the Intelligent Agent:
ORACLE_HOME/bin/agentctl
status agent
ORACLE_HOME/bin/agentctl
stop agent
-
Stop the Enterprise
Manager Web site (for system shutdown only).
If
you are preparing to shut down your system, stop the Enterprise
Manager Web site by running the following command in the Oracle home
of the primary installation (the first installation on the host):
ORACLE_HOME/bin/emctl
stop
-
Stop Web Cache
(optional).
Web
Cache is not configured in the infrastructure by default, but if you
have configured it, stop it as follows:
ORACLE_HOME/bin/webcachectl
stop
-
Stop OC4J instances and
Oracle HTTP Server.
If
you are preparing to shutdown your system, stop all running OC4J
instances, Oracle HTTP Server, and OPMN as follows:
ORACLE_HOME/dcm/bin/dcmctl
shutdown
Otherwise,
if you are not preparing to shut down your system, stop all running
OC4J instances and Oracle HTTP Server (leave OPMN running):
ORACLE_HOME/dcm/bin/dcmctl
stop
Note
that stopping Oracle HTTP Server also makes Oracle9iAS Single Sign-On
unavailable.
-
Stop Oracle Internet
Directory.
-
Make sure the ORACLE_SID
is set to the metadata repository system identifier (refer to
the next step).
-
Stop the Oracle
Internet Directory server:
ORACLE_HOME/bin/oidctl
server=oidldapd configset=0 instance=n stop
where
n is the instance number that was used to start the server (1,
2,
3...).
For example:
ORACLE_HOME\bin\oidctl
server=oidldapd configset=0 instance=1 stop
-
Stop the Oracle
Internet Directory monitor:
ORACLE_HOME/bin/oidmon
stop
-
Stop the metadata
repository.
-
Set the ORACLE_SID
environment variable to the metadata repository system
identifier. The default ORACLE_SID
is iasdb
(Bourne
or Korn shell) ORACLE_SID=iasdb; export ORACLE_SID
(C
shell) setenv ORACLE_SID iasdb
-
Stop the metadata
repository instance using SQL*Plus:
ORACLE_HOME/bin/sqlplus
/nolog
sql>
connect sys/password_for_sys
as sysdba
sql>
shutdown
sql>
quit
-
Stop the metadata
repository listener:
ORACLE_HOME/bin/lsnrctl
sto
Stopping
an Infrastructure Using Commands on Windows
This
section describes how to stop an infrastructure using command-line
tools on Windows. Except where noted, all commands should be run in
the Oracle home of the infrastructure.
-
Stop all middle-tier
application server instances that use the infrastructure.
-
Stop Oracle Management
Server and Intelligent Agent (optional).
Perform
these steps only if you have configured Oracle Management Server.
-
Stop Oracle
Management Server.
ORACLE_HOME\bin\oemctl
stop oms
-
Stop the Intelligent
Agent (for system shutdown only).
If
you are preparing to shut down your system, stop the Intelligent Agent
on this host.
The
name of the service is in the following format:
OracleORACLE_HOMEAgent
For
example:
OracleOraHome902Agent
The
Services control panel shows you the status of the service and
indicates the method used to stop the service. You can then select the
service name and use the controls on the Services window to stop the
service.
-
Stop the Enterprise
Manager Web site (for system shutdown only).
If
you are preparing to shut down your system, stop the Enterprise
Manager Web site.
You
can check the status and stop the Enterprise Manager Web site using
the Services control panel. The name of the service is in the
following format:
OracleORACLE_HOMEEMwebsite
For
example, if the name of the Oracle home is OraHome902,
the service name is:
OracleOraHome902EMWebsite
-
Stop Web Cache
(optional).
Web
Cache is not configured in the infrastructure by default, but if you
have configured it, stop it as follows:
ORACLE_HOME\bin\webcachectl
stop
-
Stop OC4J instances and
Oracle HTTP Server
If
you are preparing to shutdown your system, stop all running OC4J
instances, Oracle HTTP Server, and OPMN as follows:
ORACLE_HOME\dcm\bin\dcmctl
shutdown
Otherwise,
if you are not preparing to shut down your system, stop all running
OC4J instances and Oracle HTTP Server (leave OPMN running):
ORACLE_HOME\dcm\bin\dcmctl
stop
Note
that stopping Oracle HTTP Server also makes Oracle9iAS Single Sign-On
unavailable.
-
Stop Oracle Internet
Directory.
-
Make sure the ORACLE_SID
is set to the metadata repository system identifier (refer to
next step).
-
Stop the Oracle
Internet Directory server:
ORACLE_HOME\bin\oidctl
server=oidldapd configset=0 instance=n stop
where
n is the instance number that was used to start the server (1,
2,
3...).
For example:
ORACLE_HOME\bin\oidctl
server=oidldapd configset=0 instance=1 stop
-
Stop the Oracle
Internet Directory monitor:
ORACLE_HOME\bin\oidmon
stop
-
Stop the metadata
repository.
-
Set the ORACLE_SID
environment variable to the metadata repository system
identifier. The default ORACLE_SID
is iasdb
You
can set the ORACLE_SID
system variable using the System Properties control panel.
-
Stop the metadata
repository instance using SQL*Plus:
ORACLE_HOME\bin\sqlplus
/nolog
sql>
connect sys/password_for_sys
as sysdba
sql>
shutdown
sql>
quit
-
Stop the metadata
repository listener:
ORACLE_HOME\bin\lsnrctl
stop
|