The parameter is optional and can be used to operate on a different Oracle home. Management Agent will wait for the reverse ping from the OMS so that Management Agent can confirm that the pingOMS is successful.Ĭonfigures the current time zone as set in the environment.ĭisplays the supported time zone based on the setting in the environment.Ĭonfigures the console based on the configuration entries mentioned in the file. Pings the OMS to check if the Management Agent is able to connect to the OMS. Recomputes the dynamic properties of a target and displays them. Note: Oracle does not support manual editing of the targets.xml files unless the procedure is explicitly documented or you are instructed to do so by Oracle Support.Įmctl reload agent dynamicproperties. For example, to change the upload interval, emd.properties can be modified, and emctl reload can then be run. This command can be used to apply the changes after you have manually modified the emd.properties file. Use this command instead of waiting until the next scheduled upload of the data. Use this command to force an immediate upload of the current management data from the managed host to the Management Service. xml files that are pending to the OMS under the upload directory. Lists the names of the metrics whose values are present in the metric cache. You can also provide a particular metric name in the emctl status agent command to get the status of a particular metric of a target. Lists the detailed status of the specified targets such as target name, target type, and so on. Lists the status of the jobs that are running at present on the Management Agent. Lists all the running, ready, and scheduled collection threads. It also lists the OMS security status and the port. Lists the secure status of the Mangement Agent and the secure mode port on which the Management Agent is running. Note: On a Windows system change the directory to the AGENT_INSTANCE_HOME directory before executing the command. If the Management Agent is running, this command displays status information about the Management Agent, including the Agent Home, the process ID, and the time and date of the last successful upload to the Management Repository (). The AIXTHREAD_SCOPE parameter changes AIX Threadscope context from the default Processwide 'P' to Systemwide 'S'. To prevent this issue, prior to starting the Management Agent, add the following parameters to the common environment LDR_CNTRL variable sets the data segment size and disables loading of run time libraries in kernel space. On IBM AIX environment with a large memory configuration where the Management Agent is monitoring a large number of targets, the Agent may not start. Table 27-3 EMCTL Commands for Management Agent EMCTL Command
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |