ORAMAN utility
- Last Updated: January 17, 2024
- 2 minute read
- OpenEdge
- Version 12.8
- Documentation
Use the ORAMAN utility to control the operation of a configured OpenEdge DataServer for Oracle. The utility allows you to start a broker, query its status, start and stop additional DataServer servers, and shut down the broker.
Syntax
| Operating System | Syntax |
|---|---|
| UNIX Windows |
|
Parameters
- -name DataServer-name
- Specifies the name of a DataServer. This parameter is required.
- -kill
- Stops and removes the DataServer from memory, no matter what it is doing.
- -start
- Starts the DataServer.
- -stop
- Tells the DataServer to stop itself.
- -query
- Queries the DataServer for its status.
- -host host-name
- Specifies the name of the machine where the AdminServer is running. If a host name is not specified, it defaults to the local host name.
- -user user-name
- Specifies a user name and prompts for a password. A user name
and password are required only when you use the
-hostparameter and specify a remote host name. If you specify a remote host name with the-hostparameter, but do not specify a user name with the-userparameter, you receive a prompt for a user name and password. - -port port-number
- Specifies the port number of the machine on which the AdminServer is running. If a port number is not specified, it defaults to 20931.
- -help
- Displays command-line help.
Notes
When you
specify a user name with the -user parameter, Windows
supports three different formats:
- A user name as a simple
text string, such as "
mary," implies a local user whose user account is defined on the local server machine, which is the same machine that runs the AdminServer. - A user name as an explicit local user name, in which the user
account is defined on the same machine that runs the AdminServer,
except the user name explicitly references the local machine domain,
for example "
.\mary". - A user name as a user account on a specific Windows domain. The general format is Domain\User, in which theUser is a valid user account defined within the domain and theDomain is any valid Windows Server, including the one where the AdminServer is running.