If use other x86 server for the target system,
then could not apply the patch to target system?
Exadata can be considered just a large x86 Linux system. A standalone or virtual x86 Linux system is equivalent for Oracle purposes, so you should be able to provision from Exadata source to any x86 Linux target. I'm not sure what patch you refer to, though. If you could give us some detail about that question, we could provide a complete answer.
HCC is something that oracle locked only on its own storage products (exadata, pillar, zs).
But you can still use Delphix with non of those storage appliances, the key point is just to uncompress the hcc tables using a hook at vdb configuration.
Or you can have one of those storages as a backend for Delphix and nothing should be done you can query the hcc tables
Typically for Exadata sources, Delphix uses either one (or more) of the Exadata compute nodes as target servers, or else completely separate Linux x86-64 servers as target servers.
Regardless of what server is used for compute, Delphix VDBs can be provisioned to these target servers from Exadata sources, whether HCC is in use or not.
HCC is usable only on Oracle-branded storage (i.e. Exa, ZFSSA, Pillar), so HCC tables are unreadable within Delphix VDBs unless appropriate "ALTER TABLE ... MOVE ..." commands are configured to rebuild the HCC tables (usually as COMPRESS BASIC) using Delphix "configure clone" hooks.
As for HJ's original question, applying patches to the target VDB system should be considered very carefully. Exadata patches are often comprehensive bundled patches, so they may include changes for storage nodes, compute nodes, and database.
If you are testing a database-only patch, then no problems; the patch will affect only the Delphix VDB.
If the patch is more comprehensive and bundled, and hits more than just database, then please exercise caution. Delphix can virtualize binaries and other file-systems as well as databases, allowing testing of patches to the RDBMS binaries, but comprehensive Exadata bundle patches might go beyond that and update the OS or firmware on the compute node, which Delphix can not and does not virtualize.
Hope this helps...
Thanks for the explanation.
I have one query with respect to the HCC tables in DSource.
Will there be any licensing factor if the HCC tables are present in the Dsource(Gold Copy).
When a VDB is created we are disabling the compression with the help of hooks, so we are good there.
Just wanted to get clarify on the DSource part.