[chrisplough]

Naveen,

First - there is a process in OTM to copy domain data called a Domain Copy. It was created for use by the G-Log QA department and can be very fragile. It often has issues, because of integrity constraints and other issues and I’m careful about recommending it. The process is covered in the OTM Data Management Guide ($OTM_HOME/docs/integration/datamanagement.pdf).

Copying a whole OTM instance is easy, though, as it just involves a straight DB copy. Or you can achieve it by exporting the DB, importing it into the target DB, and running the post-import scripts to setup VPD, recompile invalid objects, etc. It’s basically the same process we used when creating a new DB from the installer-provided export file.
If you do try this, I encourage you to:

1. Test it thoroughly before using it in production. Missing data can be very hard to identify.
2. Ensure your OTM instances are at the same patch level (i.e. both CU4). Being on different platforms doesn't matter.

Hope this helps,
Chris