Monitoring SOA Infra- Dehydration Store
Performance- Single Data Source Configuration (Doc ID 1513585.1)
Dehydration Store Performance: "Failed connecting
to SOA repository." (Doc ID 1508559.1)
Enterprise
Manager for Fusion Middleware - Version 12.1.0.1.0 and later
Information in this document applies to any platform.
Information in this document applies to any platform.
The
purpose of this document is to provide troubleshooting steps to view
"Dehydration Store Performance" information in Cloud
Control. The Dehydration Store Diagnostics feature provides a dedicated
view that allows you to analyze the behavior of the SOA Dehydration database.
You can monitor SQL performance metrics and table growth specifically in the
context of the SOA Suite's use of the database. The view displays both
throughput and wait bottleneck data which allows you to monitor the general
health of the target database instance. Using Active Session History, you can track
usage data and display it as a table space chart, a growth rate chart, or an
execution chart.
In
order to enable Dehydration monitoring in Cloud Control, several configuration
steps should be performed.
The
database must be discovered and configured.
Document 1400463.1 Understanding Database Discovery in Enterprise Manager 12cCloud Control
The database target representing SOA Dehydration Store is discovered in EM. The target should be visible on the database homepage and its status should be UP
Document 1400463.1 Understanding Database Discovery in Enterprise Manager 12cCloud Control
The database target representing SOA Dehydration Store is discovered in EM. The target should be visible on the database homepage and its status should be UP
The
configuration must have been collected at least once for the targets SOA Infra
and Weblogic Server. It can be validated by visiting the latest configuration
page for the respective targets.
The configuration of
monitored targets in Cloud Control occurs every 24 hours.
If
there is no configuration yet available, the configuration can be triggered
from Cloud Control - "Last Collected" pages- "Actions" drop
down menu - "Refresh" option
One
configuration for the SOA Infra is mandatory. It can be validated by SOA Infra
target - SOA Infra Configuration Details pages.
One
configuration for the Weblogic target is mandatory. The JDBC DataSource can be
validated in JDBC DataSources pages.
On
the monitoring configuration for the SOA Infra target, the following fields
related to SOA Repository are required to be set:
a) SOA Repository Connection Descriptor
The connection URL string specified for JDBC datasource on the Weblogic server. This configuration is collected as part of the configuration collection mechanism for the SOA Server instance.
Example: jdbc:oracle:thin:@host:port/sid (or service_name )
b) SOA Repository Host Name
The db listener host for the SOA DB instance.
(This is optional when the connection string is already configured)
c) SOA Repository Port
The db listener port for the SOA DB instance.
(This is optional when the connection string is already configured)
d) SOA Repository Schema Name
The schema name configured for SOA dehydration store.
e) SOA Repository User Name
The schema name configured for SOA dehydration store. It’s the same value as above.
f) SOA Repository Password
Password for the SOA schema user.
g) SOA Repository SID
The SID for the SOA DB instance.
a) SOA Repository Connection Descriptor
The connection URL string specified for JDBC datasource on the Weblogic server. This configuration is collected as part of the configuration collection mechanism for the SOA Server instance.
Example: jdbc:oracle:thin:@host:port/sid (or service_name )
b) SOA Repository Host Name
The db listener host for the SOA DB instance.
(This is optional when the connection string is already configured)
c) SOA Repository Port
The db listener port for the SOA DB instance.
(This is optional when the connection string is already configured)
d) SOA Repository Schema Name
The schema name configured for SOA dehydration store.
e) SOA Repository User Name
The schema name configured for SOA dehydration store. It’s the same value as above.
f) SOA Repository Password
Password for the SOA schema user.
g) SOA Repository SID
The SID for the SOA DB instance.
With the above
configuration complete, in case the metric data is missing, it is recommended
to wait till the next collection interval (i.e 30 mins)
Otherwise,
collections can be run manually using command: emctl control agent
runCollection TARGETNAME:TARGETTYPE COLLECTIONITEM
If
the dehydration store page is still not displaying the details after
configuring the setup steps above, continue with the next troubleshooting
steps:
Validate whether the Database Host and SID value on the DB target property (Targets ->Databases -> Select specific DB. Select Target Information , Monitoring Configuration ) and compare with the value collected for Weblogic Server JDBC Datasource configuration.
Validate whether the Database Host and SID value on the DB target property (Targets ->Databases -> Select specific DB. Select Target Information , Monitoring Configuration ) and compare with the value collected for Weblogic Server JDBC Datasource configuration.
The host and SID value
should perfectly match. If the hostname is FQDN (Fully Qualified Domain Name)
in one place, it should be the same in the other place.
In case the Host or SID value is different, the mechanism to relate the targets in EM 12c will skip the association and dehydration store performance data will not be available.
In case the Host or SID value is different, the mechanism to relate the targets in EM 12c will skip the association and dehydration store performance data will not be available.
The
data source connection url string can be updated to keep the value as same from
the SOA Domain Weblogic Console.
WebLogic
Console-> Services - > DataSources - >
SOALocalTxDataSource->Connection Pool to update the connection pool .
In case of any change in
weblogic configuration performed from WebLogic Console, these changes should be
collected and in Last Collected configuration pages in Cloud Control.
Therefore, someone can wait for the collection to be collected or can manually
trigger the collection configuration.
growth monitoring is the regular measurement of a child's size Abstract.https://www.jainclinic.in/growth-monitoring.html BACKGROUND Growth monitoring consists of routine measurements to detect abnormal growth, combined with some
ReplyDeleteaction when this is detected. It aims to improve nutrition, reduce the risk of deathor inadequate nutrition, help educat
carers, and lead to early referral for conditions manifest by growth drjaineyeclinic.in order to document growth. The child's size measurementsmust then be plotted on a growth chart.