Manage The Manager: Tips On How To Best Manage Oracle Enterprise .
Manage the Manager: Tips on How toBest Manage Oracle EnterpriseManager 12cAngeline Janet Dhanarani,Product Management,OracleLap Nguyen,ChevronAndrei Dumitru,CERNCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Total Cloud ControlExpanded Cloud StackManagementComplete Cloud LifecycleManagementAgile, Automated Optimized, EfficientSuperior Enterprise-GradeManagement Copyright 2014, Oracle and/or its affiliates. All rights reserved. Scalable, Secure
Safe Harbor StatementThe following is intended to outline our general product direction. It is intended forinformation purposes only, and may not be incorporated into any contract. It is not acommitment to deliver any material, code, or functionality, and should not be relied uponin making purchasing decisions. The development, release, and timing of any features orfunctionality described for Oracle’s products remains at the sole discretion of Oracle.Copyright 2014, Oracle and/or its affiliates. All rights reserved.
Program Agenda1Architecture Overview of Enterprise Manager2Critical Subsystems and its monitoring with Self-monitoringfeatures3High Availability and Disaster RecoveryCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Architecture OverviewOverall Architecture and ComponentsCopyright 2014, Oracle and/or its affiliates. All rights reserved.
CRITICAL SUBSYSTEMS AND ITSMONITORING WITH SELF-MONITORINGFEATURESCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Critical Subsystems1Loader Subsystem2Job Subsystem3Console Subsystem4Agent Subsystem5Notification SubsystemCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Loader SubsystemBacklog Responsible for processing the datacollected by the agent and uploading it tothe Repository Its efficiency greatly impactsperformance and health of overall system Does synchronous uploading of data Under heavy load, OMS prioritizesuploading of data Preference given to agents withhigher agent priorities like MissionCritical and Production Agents with lower priorities areasked to backoff by OMS for a specifictime period Backlog accumulates at the agentsOMSAgentsSynchronousUpload of dataRepositoryCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Loader Subsystem MonitoringChecking Loader Performance Monitor the Loader performance charts in Setup Manage Cloud Control Management ServersIndicates the loader processing timeLook for consistent increase over a time periodCurrent loader CPU utilizationLower value indicates loader throughput is efficient Contact oracle support if the loader consistently running at more than 85% utilizationcapacityCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Loader Subsytem MonitoringChecking Agent Backlog Monitor the Upload Backlog and Backoff charts in Setup Manage Cloud Control Health OverviewOverall Back-off Requests in the Last 10 MinsOverall Upload Backlog (MB) and (Files)Overall Upload Rate (MB/sec) Incase of consistent increase in Back-off requests / Backlog Check that load is evenly distributed across all OMS with Loader Statistics Report (Reports /Information Publisher)Copyright 2014, Oracle and/or its affiliates. All rights reserved.
Loader Subsystem MonitoringChecking Agent Backlog Uneven load on specific Management Server :Check if SLB configuration is set to Round-Robin algorithm Permitted deviation tolerance : 10 – 20 %Deviationtolerance10-20% General Advice It is normal to have some amount of Agent being backed off Keep an eye on consistently growing large number of agents backed offCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Job Subsystem AnythingUserOMSWORKER THREADSJOB DISPATCHERSTEP SCHEDULERRepositoryAgentsthat is scheduled andautomated uses the job subsystem.Eg: Scheduling Blackouts, Templateapply applications Very crucial sub-component Critical processes in the Job System Step Scheduler: Responsible for processing the jobsteps that are ready to run and marks it“Ready” Job Dispatcher: Picks the steps marked “ready” forexecution.Dispatches job steps to jobworker threads Workers threads: Take work from the Job Dispatcher andsend it to the appropriate agent Different thread pools for job typesCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Job Subsystem MonitoringSetup Manage Cloud Control Health Overview Monitor Jobs Backlog(Steps) Indicates number of Job steps past its scheduled execution time. If this number is high and has not decreased for long period, it indicates job system is notfunctioning normally. Indicates Job engine resources are unable to meet inflow or indicate abnormal processing ofspecific jobs because it is stuck for unusual periodsClick Rate of change of backlog is more important thanabsolute backlog numbers11Copyright 2014, Oracle and/or its affiliates. All rights reserved.
Job Subsystem MonitoringSetup Manage Cloud Control Health Overview Monitoring All Metrics Repository Job Scheduler Performance Problem Trend Analysis of ‘Job Step Backlog’ and ‘Overall Job Steps per Second’ metricIncreasing trend over a prolonged periodIncreasing trend over a prolonged periodDecreased /constant trend over a prolonged period If Job Step Backlog and Overall Jobs per Second shows increasing trend, indicates work load is high. Jobengine resources are not able to keep with inflow. Increase the resources If Job Step Backlog is increasing but Overall Jobs per Second is not,it indicates abnormal processing ofspecific jobCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Job Subsystem MonitoringSetup / Manage Cloud Control / Management Services Job System(More Details ) Job Dispatcher details Monitor Thread Pool Utilization if inflow of work is high, backlog is consistently high If the Avg. Steps Dispatched/Min is HIGH and Avg. Threads Available is less than 50% ofConfigured Threads for a specific pool, increase the thread pool size for each of the OMS If the Avg. Steps Dispatched/Min is LOW, Avg. Threads Available is also LOW, this typically means thateither a thread is stuck/hung Refer to Appendix forSizing RecommendationsWorkof thread pool sizeInflow Contact Support fortriaging stuck threadsCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Console Subsystem Monitoring Setup Manage Cloud Control Health Overview OMS and Repository Monitoring Page Performance Monitoring console performance General Advisories Proactively check that page access andsession load is evenly distributed across OMS Check SLB configuration if not Check the presence of Symptom AnalysisIcon in Overall Tab and use this feature tonarrow down the cause of slow performingpages Icon appears only when metric “PageProcessing Time (sec)” exceeds thethreshold Symptom analysis can be done on overallpage processing and individual pages Break-down of processing time by layershelps narrow down the issueCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Agent Subsystem Monitoring With Partner Agent Partner agent is an agent which in additionto all of its regular functions, monitors thestatus of its assigned Management Agent andits hostOMSOracle emd proxy statusHost statusPartnerAgentAgentoracle emd proxyHost1Agent PushMonitoring with Proprietary protocolSignals to partner agentMonitoredAgentHost2 Algorithm of automatic partner agentassignment by OMS Agent should be pingable from agent itis going to monitor Preference is given to agents belongingto the same subnet Agent should be a 12.1.0.4 Agent Agent should be monitoring less than 10(Configurable) agents One can change the partnership explicitlywith emcli “manage agent partnership”Copyright 2014, Oracle and/or its affiliates. All rights reserved.
Agent Subsystem Monitoring With Partner Agent Target statuses with partner agentmentioned in tableSCENARIOTARGETSSTATUS OF TARGETSAgent is shutdowngracefully and notunder blackoutAGENTHOST OMSDownMONITOREDTARGETAgent DownAGENTAgent UnreachableHOSTUp (Unmonitored)MONITOREDTARGETAgent UnreachableIf Partner Agent isAGENTnot available(Host orHOSTAgent is down)MONITOREDTARGETAgent UnreachableIf AGENT goes downunexpectedly andhost is up (and notunder blackout)Up (Unmonitored)Agent UnreachableAgent Unreachable Partner agent accesses the monitoredagent and host with a proprietaryprotocol Can convey to the OMS whether themonitored agent goes DOWN Can determine if the host of themonitored agent is UP or DOWN Agent status detection doneimmediately (few seconds). Host status change detection when theagent is down done every minuteCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Agent Subsystem-Agent Unreachable TroubleshootingSub status added to provide more diagnostic detailsCommonScenariosSub status DescriptionTroubleshooting TipsDownAgent DownAgent was brought down in error /brought down as part ofplanned maintenance.If agent was brought down in error, restart it from the agenthomepage.If agent was brought down as part of plannedmaintenance, consider creating a blackout on the agent.UpUnmonitoredCurrently this sub status is set only for host target with real timepartner agent deduction. Host is up but its agent is shutdown.If agent is down, do “emctl start agent”. To triage agent issue, goto its agent homepage and run the Symptom Analysis toollocated next to the Status field.Cannot Write toFile SystemAgent cannot write to file system due to permission issue.Check that OS user who owns the agent process has write accessto agent instance directory.CollectionsDisabledAgent Collections have been disabled. The Agent will no longercollect any metric for the managed targets.Check that Agent can upload to OMS with “emctl upload”. Checkloader statistics report for loader health.Disk FullAgent file system is full.Check that Agent can upload to OMS with “emctl upload”. Recheck the count of pending files using the command ‘emctlstatus agent’ to verify if they have reduced.Post BlackoutAgent is unreachable as its first severity has not yet come afterblackout end.To triage agent issue, go to its agent homepage and run theSymptom Analysis tool located next to the Status field.Copyright 2014, Oracle and/or its affiliates. All rights reserved.
Agent Subsystem-Agent Unreachable/Pending DiagnosisSub status added to provide more diagnostic detailsCommon ScenariosSub status DescriptionTroubleshooting TipsBlocked ManuallyAgent has been blocked manually.Unblock the Agent from console -Setup Manage CloudControl AgentsBlocked (Plug-inMismatch)Agent has been blocked for communication with OMS due toPlug-in mismatch.If Agent has been restored from a backup perform an AgentResync ‘emcli resyncAgent’.Blocked (BounceCounter Mismatch)Agent has been blocked for communication with OMS due toBounce Counter mismatch.If Agent has been restored from a backup perform an AgentResync ‘emcli resyncAgent’.Agent MisconfiguredAgent is configured for communication with another OMS orOMS Agent time skew is noticed or Consecutive metadata/severity upload failureCheck Agent configuration to ensure the Agent iscommunicating with the correct OMS.Re-secure the agentwith ‘emctl secure agent’CommunicationBrokenAgent is unreachable due to communication break betweenagent and the OMS.Address the network latency , port being blocked or proxyrelated issue.Under MigrationAgent is unreachable as it is under migration (2 systemupgrade) from pre 12 to 12C.Migrate the agent and then start the agent.Note: Refer to Appendix for General Troubleshooting steps for Agent UnreachableCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Notification Subsystem Monitoring Notification system allows you to notify Enterprise Manager administrators whenspecific incidents, events, or problems arise A backlog in notifications can cause a delay in alerts being sent, or a missing alert alltogether If notifications are not getting delivered Check your external systems that are configured to receive notifications For email/pager - Is the email gateway configured and working? For OS Command and PLSQL, check the external systems that they may connect to Contact Oracle Support if external systems are not working as expected. Find the specific events in Incident Manager console for non-informational events If it is not found, likely to be an event publishing issue. If found in Incident Manager, verify the rule definitionCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Notification Subsystem MonitoringSetup Manage Cloud Control Health Overview Check Notification delivery backlog Look for consistent increase Key Metrics to monitor Notifications Processed (Last Hour) Pending Notifications Count If Pending Notifications Count remains high over a period of time [such as an hour],check Notifications Processed (Last Hour) If it is making good progress, there could be temporary load and it will resolve itself soon If it is not making good progress, there could be stuck queues in notification system/ out-of-dateincident rules. Contact Oracle SupportCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Few Other Critical Subsystems(Appendix)1Events Subsystem2Repository Metrics Collection Jobs3Repository Health4Repository Scheduler Jobs5Metric Rollup JobsCopyright 2014, Oracle and/or its affiliates. All rights reserved.
HIGH AVAILABILITY AND DISASTERRECOVERYCopyright 2014, Oracle and/or its affiliates. All rights reserved.
High Availability Critical components in Enterprise Managerinfrastructure are:– Repository - Persistent store for all Enterprise Managerdata– OMS - Central application accessed by Agents and endusers– Software Library - Filesystem repository used to storesoftware entities All of the above should be configured for HighAvailability if availability of Enterprise Manager iscriticalCopyright 2014, Oracle and/or its affiliates. All rights reserved.
High AvailabilityRepository Oracle RAC provides a standard HA solution for the EM repository Best Practice: Configure RAC prior to EM installation Best Practice: Use SCAN and role –based DB Servicesfor OMS to Repository connect stringsOMSRepository Advantage of Role-based database services with Oracle RAC Can automatically control the startup of database services on databases by assigninga database role - PRIMARY / PHYSICAL STANDBY / LOGICAL STANDBY /SNAPSHOT STANDBY Refer whitepaper Best Practises for Highly Available Oracle Databases for detailsCopyright 2014, Oracle and/or its affiliates. All rights reserved.
High AvailabilityOMS Additional OMSs can bedeployed behind a Server LoadBalancer (SLB) for OMS HighAvailability Agents and Users communicatewith OMS via load balancerCopyright 2014, Oracle and/or its affiliates. All rights reserved.
High Availability End-To-End Topology All OMS, Repository and Software Librarycomponents are active within the same DataCenter Software Library must be accessibleRead/Write from all active OMSs Software library should be deployed onhighly available storage Not a Disaster Recovery (DR) solutionCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Disaster Recovery Protects applications from catastrophic failuresPrimarySite Keeps data on primary site synchronized with a standby Allows applications to failover to the standby siteCopyright 2014, Oracle and/or its affiliates. All rights reserved. StandbySite
Disaster RecoveryRepository Data Guard Physical Standby Database provides Disaster Recoverysolution for RepositoryPrimary Site(active) Use Data Guard Broker to manage switchover/ failover of database Best Practise: Configure OMS connect descriptor with scan namesand role-based services of primary and standby data centers (DESCRIPTION LIST (LOAD BALANCE off) (FAILOVER on)(DESCRIPTION (CONNECT TIMEOUT 5)(TRANSPORT CONNECT TIMEOUT 3)(RETRY COUNT 3)(ADDRESS LIST (LOAD BALANCE on)(ADDRESS (PROTOCOL TCP)(HOST PRIM SCAN)(PORT 1521)))(CONNECT DATA (SERVICE NAME DB ROLE SERVICE)))(DESCRIPTION (CONNECT TIMEOUT 5)(TRANSPORT CONNECT TIMEOUT 3)(RETRY COUNT 3)(ADDRESS LIST (LOAD BALANCE on)(ADDRESS (PROTOCOL TCP)(HOST STBY SCAN)(PORT 1521)))(CONNECT DATA (SERVICE NAME DB ROLE SERVICE))))Copyright 2014, Oracle and/or its affiliates. All rights reserved. Standby Site(passive)Data GuardPhysical Standby
Disaster RecoveryOMS Deploy Standby (Passive) OMSs on Standby Site Standby OMS using Standby WebLogic Domain Standby OMS using Storage ReplicationDeprecatedPrimary Site Use DNS / Global Traffic Manager to redirectAgent Best Practice: Storage Replication isrecommended method– No manual application of Plug-ins or OMSpatches at Standby Site– No rebuild of Standby site needed after upgradesDNS/GTMStandby SiteCopyright 2014, Oracle and/or its affiliates. All rights reserved. Console/EMCLI
Enterprise Manager High Availability Level 4 SolutionRecommended Solution for High Availability and Disaster Recovery with Storage er Load Balancer ofStandby data centerPrimaryOMSAdditionalOMS1StorageOMS ShareOMS1 ShareEMRepositoryPhysical StandbySwlib ShareSWITCHOVERServer Load Balancer ofPrimary data centerStoragePrimaryOMSAdditionalOMS1OMS ShareOMS1 ShareSwlib ShareStorage Continuous ReplicationDB Replication with Dataguard from Primary to StandbyCopyright 2014, Oracle and/or its affiliates. All rights reserved. EMRepositoryPhysical Standby
ACFS ReplicationAlternate to using External Storage Appliances ACFS storage replication requires GridInfrastructure to be installed for a Cluster ACFS Filesystem created for OMS installand software library on ACFS server and thisis exported using NFS Filesystem mounted on another node(OMSserver) and EM installed here Similar setup on second ACFS server withanother ACFS filesystem to be used as astandby Established ACFS replication between theprimary and standby ACFS servers Refer to Section 18.7 of AdvancedInstallation Guide for configuration detailsCopyright 2014, Oracle and/or its affiliates. All rights reserved.
BI Publisher High Availability With EM12c R4, BI Publisher is bundled and installed by default BIP needs to be configured using the ‘configureBIP’ script BIP supports Enterprise Manager HA scale out BIP can be configured on all OMS nodes to increase reporting capacity This does not provide failover, in case one of the BIP instances fails or is otherwise stopped [Fixedin future].Recommendations: Configure BIP on the first OMS node, before cloning it Always configure BIP on all OMS nodes, and ensure thatBIP is always UP, when that node's OMS is also up BI Publisher is supported only with storage replicationbased solution for Disaster Recovery. Not functional withStandby OMS with Weblogic Domain methodLoad BalancerOMS1BIP1BIP2OMS2WebLogicWebLogicServer 1Server 2Copyright 2014, Oracle and/or its affiliates. All rights reserved.
AppendixCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Architecture OverviewOracle Management Service (OMS)OMS Central Enterprise Manager Application Source of truth for all management Receives and processes data from Agents Uses repository as persistent store for informationConsolePBS Comprises 2 Weblogic Server application deployments Console – Provides UI and Target Specific Management Platform Background Services (PBS) – A set of background services critical for monitoringand management Verify status of Console and PBS is marked as UP for each Management Service in Setup Manage Cloud Control Management ServicesCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Architecture OverviewRepository Most critical part of EM system Deploy with performance and availability in mind Persistent store for data collected from the managed Targets Performance and Availability Metrics Configuration and Compliance InformationRepository Used to store a variety of Enterprise Manager configuration informationsuch as: users and privileges job definitionsCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Architecture OverviewAgents Collect monitoring and configuration data from the targets and store locallyin XML files Collected data uploaded at scheduled intervals to Management Service usingHTTP/HTTPS XML files are purged once data has been uploaded Execute tasks on behalf of Enterprise Manager users Real-time data collections Jobs Deployment ProceduresAgentsCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Job Subsystem MonitoringSizing Recommendations of thread pool size Sizing Recommendations of pool size for Large Configuration with 2 or 4 OMS nodes Default pool size configuration forSmall and Medium configuration Incase of major resource issues,contact Oracle Support for guidanceon adding additional e.conn.maxConnForJobWorkers144Copyright 2014, Oracle and/or its affiliates. All rights reserved.
Event Subsystem MonitoringSetup / Manage Cloud Control / Health Overview / OMS and Repository Menu /Monitoring –All Metrics Responsible for processing the events published by different components in the system Key Metrics to check event backlog -Total Events Pending and Total Events Processed(Last Hour) If Total Events Pending remains high [over an hour]. Check metrics Total Events Processed (Last Hour) If it is making good progress(count is high), there could be temporary load –ignore When pending count continues to be high, it should sustain a minimum processing of 1000events per every 10 minutes If it is not making good progress, there could be stuck queues in event system Check the queue statistics in “Event Status” metric group to detect problem in AQ Contact Support for triaging issues in AQ /queuesCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Repository Metric Collection Jobs Monitoring Repository metric jobs are sub divided into long and short running tasks Some collection workers (Default 1) process the short tasks and some (Default 1)process long tasks Key Indicators of its performance Repository Collection Performance Chart Repository collection performance metrics Key Metrics Average Collection Duration (seconds) Collections Processed Repository Collection Task Performance Run Duration (Seconds)Copyright 2014, Oracle and/or its affiliates. All rights reserved.
Repository Metric Collection Job Monitoring Average Collection Duration (seconds) - Indicator of the load on therepository collection subsystem Two possible reasons - Number of collections have increased Or some of the metricsare taking a long time to complete Check the Run Duration (Seconds) metric To identify which metric is taking more than 2 mins of time(default) to execute. Threshold-able If any metric is taking unusually long time, disable the specific metric to unblock. Check the Collections Processed metric Consistently high and backlog is continuous Enable Collection Manager for one-off cases Configure threads if backlogs are generally high Maximum workers is 5Copyright 2014, Oracle and/or its affiliates. All rights reserved.
Repository Health Monitoring General guidelines for MaximumAvailability to check in repository Regular Backups ARCHIVELOG mode ON FLASHBACK Mode ON Refer to Oracle Database High AvailabilityGuidelines Compliance to Repository DatabaseSetting as per Sizing guidelines.Copyright 2014, Oracle and/or its affiliates. All rights reserved.
Repository Scheduler Jobs MonitoringSetup Manage Cloud Control Repository Monitor Repository Scheduler Jobs status and processing time Tips to troubleshoot if the Status of these jobs are down For the repository jobs to run, the DBMS SCHEDULER must be enabled Start these jobs with pl/sql command ‘exec emd maintenance.submit em dbms jobs’Copyright 2014, Oracle and/or its affiliates. All rights reserved.
Repository Scheduler Jobs Monitoring If a specific job is down ie broken state, Query the mgmt performance names table as repository owner for thedbms jobname and fetch the job id from all jobs Look for ORA-12012 messages for this job id in the database alerts log and trace filesfor the problem to fix. Re-start the job from console Contact Oracle Support if fix cannot be easily identified Key Metrics to gauge its performance Throughput per second Processing Time(% of Last Hour) If Processing Time is largeand the Throughput is low Check for errors in database-alert.logCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Metric Rollup JobsSetup Manage Cloud Control Repository Aggregation mechanism: Both hourly and daily rollups are done from the raw datadirectly Look out for consistently growing backlogs or prolonged execution time span Configure additional rollup worker threads using configure option in Metric Rollup Performance ChartClick If the RAC is configured in the database,to avoid RAC contention negating gain ofadditional threads Create database service and set affinity to itfor the rollup job to only run on one RAC nodeCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Metric Rollup Jobs MonitoringSetting affinity with RAC Configuration Create database service and set affinity to it for the rollup job to only run on one RACnode Create database service “rollup” and set one of RAC instance as primary instance in “-r” srvctl add service -d dbname -s rollup -r primary instance -a the the other instances -yautomatic srvctl start service -d dbname -s rollupsrvctl status service -d dbname As sys user, execute DBMS SCHEDULER.create job class( job class name 'ROLLUP', service 'rollup') GRANT EXECUTE ON sys.ROLLUP TO sysman; As sysman user, execute DBMS SCHEDULER.SET ATTRIBUTE ( name 'EM ROLLUP SCHED JOB',attribute 'job class', value 'ROLLUP') As sysman user, execute GC SCHED JOB REGISTRAR.SET JOB CLASS('EM ROLLUP SCHED JOB', 'ROLLUP')Copyright 2014, Oracle and/or its affiliates. All rights reserved.
Agent Subsystem-New Agent Unreachable sub-statusesSub status added to provide more diagnostic detailsAgent Unreachable And Status Pending StatusesAgent UnreachablePost BlackoutDownBlocked (Plug-in Mismatch)Agent DownBlocked (Bounce Counter Mismatch)Up UnmonitoredAgent MisconfiguredUnder MigrationCommunication BrokenCannot Write to File SystemStatus PendingCollections DisabledTarget Addition in ProgressDisk FullStatus Pending (Post Blackout)Blocked ManuallyStatus Pending (Post Metric Error)Copyright 2014, Oracle and/or its affiliates. All rights reserved.
General Troubleshooting Steps for Agent UnreachableSetup Manage Cloud Control Agents Target Status Diagnostics Report: Agent-based targets (Information Publisher report) Check the Promote Status column and Broken Reason in Target Information Check for latest “Clean Heartbeat UTC” time in “Agent Ping Status” table in the Report Ensure OMS is reachable from agent host and agent from OMS hostCheck “emctl status” for various configurations. Eg: Agent communicating with correct OMSCheck agent upload with “emctl upload”Contact Oracle Supprt with these log gcagent.log from agent home emoms pbs .log, emoms.logCopyright 2014, Oracle and/or its affiliates. All rights reserved.
Safe Harbor StatementThe preceding is intended to outline our general product direction. It is intended forinformation purposes only, and may not be incorporated into any contract. It is not acommitment to deliver any material, code, or functionality, and should not be relied uponin making purchasing decisions. The development, release, and timing of any features orfunctionality described for Oracle’s products remains at the sole discretion of Oracle.Copyright 2014, Oracle and/or its affiliates. All rights reserved.
Copyright 2014, Oracle and/or its affiliates. All rights reserved.
status of its assigned Management Agent and its host Algorithm of automatic partner agent assignment by OMS Agent should be pingable from agent it is going to monitor Preference is given to agents belonging to the same subnet Agent should be a 12.1.0.4 Agent Agent should be monitoring less than 10 (Configurable) agents
May 02, 2018 · D. Program Evaluation ͟The organization has provided a description of the framework for how each program will be evaluated. The framework should include all the elements below: ͟The evaluation methods are cost-effective for the organization ͟Quantitative and qualitative data is being collected (at Basics tier, data collection must have begun)
Silat is a combative art of self-defense and survival rooted from Matay archipelago. It was traced at thé early of Langkasuka Kingdom (2nd century CE) till thé reign of Melaka (Malaysia) Sultanate era (13th century). Silat has now evolved to become part of social culture and tradition with thé appearance of a fine physical and spiritual .
On an exceptional basis, Member States may request UNESCO to provide thé candidates with access to thé platform so they can complète thé form by themselves. Thèse requests must be addressed to esd rize unesco. or by 15 A ril 2021 UNESCO will provide thé nomineewith accessto thé platform via their émail address.
̶The leading indicator of employee engagement is based on the quality of the relationship between employee and supervisor Empower your managers! ̶Help them understand the impact on the organization ̶Share important changes, plan options, tasks, and deadlines ̶Provide key messages and talking points ̶Prepare them to answer employee questions
Dr. Sunita Bharatwal** Dr. Pawan Garga*** Abstract Customer satisfaction is derived from thè functionalities and values, a product or Service can provide. The current study aims to segregate thè dimensions of ordine Service quality and gather insights on its impact on web shopping. The trends of purchases have
Chính Văn.- Còn đức Thế tôn thì tuệ giác cực kỳ trong sạch 8: hiện hành bất nhị 9, đạt đến vô tướng 10, đứng vào chỗ đứng của các đức Thế tôn 11, thể hiện tính bình đẳng của các Ngài, đến chỗ không còn chướng ngại 12, giáo pháp không thể khuynh đảo, tâm thức không bị cản trở, cái được
Le genou de Lucy. Odile Jacob. 1999. Coppens Y. Pré-textes. L’homme préhistorique en morceaux. Eds Odile Jacob. 2011. Costentin J., Delaveau P. Café, thé, chocolat, les bons effets sur le cerveau et pour le corps. Editions Odile Jacob. 2010. Crawford M., Marsh D. The driving force : food in human evolution and the future.
Le genou de Lucy. Odile Jacob. 1999. Coppens Y. Pré-textes. L’homme préhistorique en morceaux. Eds Odile Jacob. 2011. Costentin J., Delaveau P. Café, thé, chocolat, les bons effets sur le cerveau et pour le corps. Editions Odile Jacob. 2010. 3 Crawford M., Marsh D. The driving force : food in human evolution and the future.
