A command-line interface opmnctl for advanced users to control Oracle Fusion Middleware components. Automatic restart of processes when they become unresponsive or terminate unexpectedly. Command Description opmnctl status Shows the component names and the status of all system components opmnctl startall Starts OPMN and all Oracle Business Intelligence system components. A specific module or list of modules may be specified with modules module-ids.
Each subcomponent for ons and pm may be prefaced with the negation character,! By using all with negated sub-components, specific subcomponents can be easily eliminated from the display.
Components and subcomponents are set or negated in the order in which they are encountered. The attribute name of target must be specified along with an attribute value.
The value for target can be either log or debug , which refer to the opmn. Refer to Section B. The opmnctl help commands enable you to obtain additional information regarding OPMN. This section describes the help command options available with the opmnctl command.
Syntax: opmnctl help. The usage command displays help for any one specified opmnctl command. With no argument the opmnctl usage command displays the same information as opmnctl help. For example, enter the following command to receive the output shown in Example :. Example opmnctl usage stopall output. The opmnctl validate command validates the XML syntax of the opmn.
The location of the opmnctl script determines which opmnctl commands you can use. Do not use command line scripts or utilities from previous versions of Oracle Fusion Middleware for starting and stopping system components.
Table opmnctl Syntax Syntax Description verbose Prints detailed execution message, if available. It includes the following sections: Scope Attributes Verbose 4. Note: If Oracle Internet Directory is managed by OPMN and an Oracle Internet Directory dependency not a managed-process dependency for Oracle Internet Directory is encountered as part of the request, and the request is expected to start both Oracle Internet Directory processes such as an opmnctl startall request , the Oracle Internet Directory process will not start unless it has been configured in the opmn.
Otherwise, the request times out with an Oracle Internet Directory dependency failure. Server Control Commands on Microsoft Windows opmnctl start opmnctl startall opmnctl stopall opmnctl shutdown opmnctl reload Output is not generated for the successful execution of an opmnctl server control command. All system component processes are also started. Enter one of the following commands to obtain additional information: opmnctl usage stopall or opmnctl usage shutdown. The restart of the service is not equivalent to an opmnctl reload , however.
This action is equivalent to an opmnctl shutdown followed by an opmnctl startall. See Also: Section 4. It includes the following process control commands: opmnctl startproc, opmnctl restartproc and opmnctl stopproc Progressive Request Reports Sequential Requests Output is not generated for the successful execution of an opmnctl process control command.
The following attributes and values can be used with the startproc, stopproc, and restartproc commands: ias-component, process-type, and process-set: The values for these attributes should be the same as the id value specified in the opmn. You can obtain this value by entering the following command and obtaining the unique number for the system component in the uid column of the generated output: opmnctl status -l Attribute names other than those listed may be specified for some types of system processes managed by OPMN.
Note that dependencies are still honoured, and take part in the request sequentially as well. Use these commands to: Create and delete an Oracle instance or system component.
Update an Oracle instance or system component registration with the WebLogic domain. Name must be no more than 30 characters long. Name must be at least 4 characters long. The following provisioning commands are supported: createinstance createcomponent deleteinstance deletecomponent registerinstance unregisterinstance updateinstanceregistration updatecomponentregistration. Any opmnctl provisioning commands can be entered using either syntax.
The Adminserver arguments are: -adminHost : the Weblogic Adminserver host. The Oracle instance arguments are: -oracleInstance : the Oracle instance root directory.
For example: opmnctl usage createcomponent -componentType OHS. It includes the following sections: createinstance createcomponent deleteinstance deletecomponent registerinstance unregisterinstance updateinstanceregistration updatecomponentregistration 4.
The createcomponent command uses the following arguments: Adminserver Logging Oracle Instance Component Specific Arguments -componentType : the system component type -componentName : the system component name For example: opmnctl createcomponent -componentType OHS -componentName ohs1 -proxyPort It is important to note that different system components feature different sets of arguments that are available for configuration.
For example: opmnctl deleteinstance The deleteinstance command uses the following arguments: Adminserver Logging Oracle Instance -force : The -force argument forces the opmnctl deleteinstance command to proceed regardless of discrepancies in the Oracle instance. Force deleteinstance The deleteinstance command operates in a forced mode if the option -force true is included in the command.
For example: opmnctl deleteinstance -force true -instanceName instance1 -adminHost myadminserver -adminPort or opmnctl deleteinstance -force true -instanceName instance1. The deletecomponent command uses the following arguments: Adminserver Logging Oracle Instance -componentName : The system component name. For example: opmnctl deletecomponent -componentName ohs1.
The registerinstance command uses the following arguments: Adminserver Logging Oracle Instance For example: opmnctl registerinstance -adminHost myhostname -adminPort For example: opmnctl unregisterinstance The unregisterinstance command uses the following arguments: Adminserver Logging Oracle Instance -force : directs the opmnctl unregisterinstance command to proceed regardless of discrepancies in the Oracle instance.
An example is shown in section Forced unregisterinstance Forced unregisterinstance The unregisterinstance command can operate in a forced mode when the option -force true is included. For example: opmnctl unregisterinstance -force true -instanceName instance1 -adminHost myadminserver -adminPort The updateinstanceregistration command uses the following arguments: Adminserver Logging Oracle Instance For example: opmnctl updateinstanceregistration.
The updatecomponentregistration command uses the following arguments: Adminserver Logging Oracle Instance Component Specific Arguments -componentName : the system component name For example: opmnctl updatecomponentregistration -componentName ohs1 -proxyPort It includes the following sections: opmnctl status opmnctl metric opmnctl dmsdump opmnctl ping opmnctl set opmnctl query See Also: Section 4. The output is a text table. Each row in the table represents one system process. You can customize the status command in the following ways: Change the information displayed about each system process Remove the table headers from the output Change the field separator Change the record separator Change the width of individual columns Change the justification of the data in an individual column Enter the opmnctl usage status command to obtain full details on how to use the status command.
Default: width of each datum. Default: L. For example, the command: opmnctl status -port displays: For example, the following command, opmnctl ping 10 designates pinging of OPMN 10 times until the ping command succeeds. The following attribute names are required by OPMN for this command: target : the value for target can be either log or debug , which refer to the standard.
Note: Enable usage of the debug. The debug. Messages that are contained in the debug. The following values for comp specify the OPMN internal components and subcomponents: internal: specifies the common internal information for OPMN ons :specifies the ONS component information for OPMN pm : specifies the PM component information for OPMN Both the ons and pm components consist of subcomponents which may be specified using the component[subcomponents] syntax where component can be either ons or pm.
Table ONS Component Codes ONS element Definition all all subcomponents local local information listener listener information discover discover server or multicast information servers remote servers currently up and connected to the farm topology current farm wide server connection topology server remote server connection information client client connection information connect generic connection information subscribe client subscription information message notification receiving and processing information deliver notification delivery information special special notification processing internal internal resource information secure SSL operation information workers worker threads.
Table PM Component Codes PM element Definition all all subcomponents requests HTTP user requests remote remote HTTP requests scheduler scheduler thread and resource information monitor monitor thread information workers worker threads process managed processes depend dependency processing rmd RMD directives fos service failover information internal internal resources schedjobs periodic scheduled jobs procjobs for each process scheduled jobs fos service failover processing dms DMS processing modules process module information.
It includes the following sections: Section 4. Example shows the output from the opmnctl help command. This request first tries to stop all managed processes gracefully. Processes which will not stop gracefully will be forcefully shutdown. After stopping all managed processes, the opmn daemon will shutdown itself. For example, the following command, outputs debug information at an interval of 5 seconds 3 times. Contact your local Oracle support to assist you in using the opmnctl debug command to diagnose your OPMN problem.
Use the iHAT tool to provide a real time, graphical interface view of your enterprise. The snapshot of the system is updated continuously at a configurable interval. Application Server Control provides a graphical interface that enables diagnosis of Oracle Application Server components in your network and enterprise. Application Server Control features a log page. The log page enables you to view all of the Oracle Application Server log files in one place and trace problems across multiple log files.
You can use Application Server Control to enable or disable Oracle Application Server components: You can disable components so they do not start when you start an Oracle Application Server instance. You can create a script that records events prior to the start or stop of Oracle Application Server processes, as well as an unscheduled system crash. The following Example shows a pre-start event script:. This section describes some of the common problems encountered when using OPMN.
Review the standard out output log for the Oracle Application Server process. Verify the dependency requirements for the Oracle Application Server process you are attempting to start. For example, the Oracle Application Server process you want to start may require that the Oracle Application Server Metadata Repository be up and running. Verify the element values for the Oracle Application Server component in the opmn.
Value can either be sync or async. The default value is " sync , meaning that this request operates synchronously, and waits for the operation to complete before returning.
This can only be specified in sync mode. The value is in seconds. After this timeout expires, OPMN does not continue to perform the request for startproc operations. The request does continue for restartproc and stopproc operations.
This value is assigned by OPMN after starting up. You can use this value when you execute the opmnctl restartproc and opmnctl stopproc commands. Syntax: opmnctl verbose command. The opmnctl verbose option enables you to obtain detailed information about the command you are executing. For example, the following command outputs the information shown in Example :. The opmnctl start, startall, reload, stopall, and shutdown commands enable you to control the OPMN server.
Output is not generated for the successful execution of an opmnctl server control command. Syntax: opmnctl start. The startall is equivalent to the start command and the startproc command without arguments.
Oracle recommends using the start or startproc command. This command operates synchronously and waits for the operation to complete before returning. To set a timeout for the request, specify the timeout value in seconds.
Syntax: opmnctl stopall. This request operates synchronously; it waits for the operation to complete before returning. Shutting down the OPMN server is not necessary during normal operation. The opmnctl stopall command should only be executed prior to shutting down OPMN and your computer. This request first tries to stop all OPMN-managed processes gracefully.
Processes which will not stop gracefully will be forcefully shutdown. After stopping all managed processes, the OPMN daemon will shutdown itself. The opmnctl stopall command should only be used when it is necessary to stop the OPMN daemon. Once started, the OPMN daemon should remain up until it is necessary to restart the computer or some other unforeseen administrative event occurs.
The opmnctl reload command is the appropriate command to use when the only goal is to restart the opmn daemon with a new configuration. Use the opmnctl stopproc command if you want to stop all OPMN managed processes. Use the opmnctl reload if you want OPMN to reread its configuration. Syntax: opmnctl shutdown. The opmnctl shutdown command is similar to the opmnctl stopall command but waits less time before initiating a forceful termination of OPMN-managed processes.
The opmnctl shutdown command should only be performed when it is necessary to stop the OPMN daemon. The opmnctl reload command is the appropriate command to use when the objective is to restart the OPMN daemon with a new configuration.
Syntax: opmnctl [ scope ] reload. Use this command to trigger the OPMN to reread its configuration files in the requested scope. The opmnctl process control commands enable you to start, stop, or restart single or multiple Oracle Application Server components. This section describes the process control commands available with opmnctl.
It includes the following process control commands:. Section 4. Output is not generated for the successful execution of an opmnctl process control command. Use these commands to start, restart, or stop OPMN-managed processes in the requested scope.
The following attributes and values can be used with the startproc, stopproc, and restartproc commands:. If no attribute is supplied, the command is applied to all OPMN-managed processes other than those that are configured in the opmn.
The sync value for mode causes the opmnctl command to operate synchronously and wait for the command to be executed completely before a return prompt is displayed. The timeout element can only be specified when the value of mode is sync.
The value is specified in number of seconds. After the specified timeout expires, the operation is aborted for startproc but not for restartproc or stopproc. T he opmnctl command prompt returns, the OPMN server continues to perform the opmnctl restartproc or stopproc command request until the operation is finished. The async value for mode causes the return prompt to be displayed immediately, while the OPMN server continues to perform the opmnctl command request until the operation is finished.
You can use this value when you execute the restartproc and stopproc commands.
0コメント