Why does sca_entity table having entries for composite revisions which were undeployed in the past?
(Doc ID 3028042.1)
Last updated on JUNE 17, 2024
Applies to:
Oracle SOA Suite - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Goal
On : 12.2.1.3.0 version, Deployment
While executing the query below
SELECT sp.name folder
,se.composite
,se.revision
,se.*
FROM xxxxx_soainfra.sca_entity se
,xxxxx_soainfra.sca_partition sp
WHERE sp.id = se.sca_partition_id
AND se.state = 'active'
AND se.type = 'composite'
AND se.composite = 'xxxxxxxxxxx'
ORDER BY se.composite
,se.revision;
For example the query returns revisions 1.02 and 1.05 for a particular composite.
However when searching for this composite in EM console, only the latest revision 1.05 exists. The older revision (1.02) doesn’t exist and was undeployed in the past.
Why does the above query still return the older (undeployed) revision 1.02?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |