This content has been marked as final. Show 3 replies
1. YES. You can absolutely use SAME DB to have multiple Versions of SOA Schemas.
2. Any SOA/BPM will need basically 4/5 schemas like SOAINFRA, MDS, ORABAM, ORASDPM etc. based on what you choose. And each of these Schemas can be Prefixed. Default prefix is like DEV, so schemas are like DEV_SOAINFRA, DEV_MDS etc
3. Very Simple. When you Run RCU 11.6 and give the same old db details, in next screen it will automatically show the new Prefix for the schemas it will create. If DEV is used, it will show DEV1 like that. So just choose a Different Prefix and you are good to go.
I have the same thing on my side. Single Database. Multiple RCU for SOA 11.5 and SOA 11.6 with different Prefixes:
SOA 11.5 -> DEV115_SOAINFRA, DEV115_MDS, DEV115_ORABAM etc
SOA 11.6 -> DEV116_SOAINFRA, DEV116_MDS, DEV116_ORABAM etc
I Used the Prefixes like DEV115, DEV116 so that I know exactly which version of RCU schema they refer to.
For QC, UAT, PROD we used prefixes like QC_*, UAT_*, PROD_* etc.
NOTE: When you drop the schemas for some reason, make sure to give the appropriate prefixes so that only they are dropped and not others.
When you create the schemas using RCU you are able to select a unique prefix for the schema.
For instance, DEV_SOAINFRA.
I use a prefix convention that's a bit more descriptive for my test box, which currently has five 11g SOA/OSB installs all using the same database for the schemas.
Since my installs are purely for testing on specific versions and install types - this convention works for me.
In a similar way, you could choose unique prefixes for your schemas which would allow you to have multiple SOA installs using the same database for the schemas.