Those who handle Oracle SOA support will know how difficult to locate an instance using composite sensors in Enterprise Manager Console. This will eat our time and patience :)
But this can be avoided by using SOA infra tables.
We all know that the transactions are available in SOA Infra tables across multiple tables and if we leverage it with proper joins, then life of support person will be easy.
Below mentioned tables are the important ones that will be used to locate the instances.
CUBE_INSTANCE
COMPOSITE_INSTANCE
COMPOSITE_SENSOR_VALUE
Below mentioned tables are the important ones that will be used to locate the instances.
CUBE_INSTANCE
COMPOSITE_INSTANCE
COMPOSITE_SENSOR_VALUE
Composite Instance :
Below are the important columns in composite instance tables.
ECID: Unique values for one end to end transactions across several tables.
ID: Instance ID that is visible in Enterprise Manager Console
PARENT_ID: This will be null for initiator composite and child composite will have value of parent composite
COMPOSITE_DN: Composite name along with partition name
STATE: State of instance like completed, running etc which is explained in details
CREATED_TIME: Creation time of an instance
List of states and its description:
Below are the important columns in composite instance tables.
ECID: Unique values for one end to end transactions across several tables.
ID: Instance ID that is visible in Enterprise Manager Console
PARENT_ID: This will be null for initiator composite and child composite will have value of parent composite
COMPOSITE_DN: Composite name along with partition name
STATE: State of instance like completed, running etc which is explained in details
CREATED_TIME: Creation time of an instance
List of states and its description:
| State | Description |
|---|---|
| 0 | Running |
| 1 | Completed |
| 2 | Running with faults |
| 3 | Completed with faults |
| 4 | Running with recovery required |
| 5 | Completed with recovery required |
| 6 | Running with faults and recovery required |
| 7 | Completed with faults and recovery required |
| 8 | Running with suspended |
| 9 | Completed with suspended |
| 10 | Running with faults and suspended |
| 11 | Completed with faults and suspended |
| 12 | Running with recovery required and suspended |
| 13 | Completed with recovery required and suspended |
| 14 | Running with faults, recovery required, and suspended |
| 15 | Completed with faults, recovery required, and suspended |
| 16 | Running with terminated |
| 17 | Completed with terminated |
| 18 | Running with faults and terminated |
| 19 | Completed with faults and terminated |
| 20 | Running with recovery required and terminated |
| 21 | Completed with recovery required and terminated |
| 22 | Running with faults, recovery required, and terminated |
| 23 | Completed with faults, recovery required, and terminated |
| 24 | Running with suspended and terminated |
| 25 | Completed with suspended and terminated |
| 26 | Running with faulted, suspended, and terminated |
| 27 | Completed with faulted, suspended, and terminated |
| 28 | Running with recovery required, suspended, and terminated |
| 29 | Completed with recovery required, suspended, and terminated |
| 30 | Running with faulted, recovery required, suspended, and terminated |
| 31 | Completed with faulted, recovery required, suspended, and terminated |
| 32 | Unknown |
| 64 | - |
Any value in the range of 32 to 63 indicates that the composite instance state has not been enabled, but the instance state is updated for faults, aborts, etc.
Cube Instance:
CIKEY: Unique value for a instance
CREATION_DATE: Creation date
STATE: State of Instance
STATUS: Status of Instance
ECID: Unique hexa decimal id for end to end transaction
CMPST_ID: Instance ID that is visible in Enterprise Manager console or Value of ID column in Composite Instance table
COMPOSITE_NAME: Name of composite
DOMAIN_NAME: Partition Name
COMPONENT_NAME: Name of component
COMPOSITE_REVISION: Revision Number of composites
CIKEY: Unique value for a instance
CREATION_DATE: Creation date
STATE: State of Instance
STATUS: Status of Instance
ECID: Unique hexa decimal id for end to end transaction
CMPST_ID: Instance ID that is visible in Enterprise Manager console or Value of ID column in Composite Instance table
COMPOSITE_NAME: Name of composite
DOMAIN_NAME: Partition Name
COMPONENT_NAME: Name of component
COMPOSITE_REVISION: Revision Number of composites
CUBE_INSTANCE States
| State | Description |
|---|---|
| 0 | STATE_INITIATED |
| 1 | STATE_OPEN_RUNNING |
| 2 | STATE_OPEN_SUSPENDED |
| 3 | STATE_OPEN_FAULTED |
| 4 | STATE_CLOSED_PENDING_CANCEL |
| 5 | STATE_CLOSED_COMPLETED |
| 6 | STATE_CLOSED_FAULTED |
| 7 | STATE_CLOSED_CANCELLED |
| 8 | STATE_CLOSED_ABORTED |
| 9 | STATE_CLOSED_STALE |
| 10 | STATE_CLOSED_ROLLED_BACK |
Composite Sensor Values:
COMPOSITE_INSTANCE_ID: Instance ID that is visible in EM console or Value of ID in composite_instance table
COMPONENT_NAME: Name of the component
SENSOR_NAME: Name of the sensors
CPST_PARTITION_DATE: Creation date
STRING_VALUE: Sensor value in String datatype
NUMBER_VALUE: Sensor value in Number datatype
DATE_VALUE: Sensor value in Date datatype
CLOB_VALUE: Sensor value in Clob datatype
BLOB_VALUE: Sensor value in Blob datatype
In following post, we shall see different queries that we use day by day for support purpose.
No comments:
Post a Comment