A question posted on behalf of a partner: Limitations on DB_UNIQUE_NAME for Oracle VDBs

  • 0
  • 1
  • Question
  • Updated 7 months ago
  • Answered
A question posted on behalf of a partner...

In our production environment we may want to deploy an Oracle VDB as ORCL and in the development environment as ORCL in dSource.

However, the current Delphix Engine does not allow duplication of DBNAME etc within Engine.

Can you eliminate this limitation?
Photo of Tim Gorman

Tim Gorman, Field Services

  • 2,824 Points 2k badge 2x thumb

Posted 7 months ago

  • 0
  • 1
Photo of Tim Gorman

Tim Gorman, Field Services

  • 2,824 Points 2k badge 2x thumb
So, seemingly answering my own question... but really just posting the question here so that it might benefit others...  :)

In the "Provision VDB" wizard, there are three similar fields to requiring values when creating an Oracle VDB:

  1. the Oracle initialization parameter DB_UNIQUE_NAME
  2. the Oracle initialization parameter DB_NAME
  3. the UNIX/Linux environment variable ORACLE_SID

It is only the value of the initialization parameter DB_UNIQUE_NAME upon which Delphix enforces uniqueness;  Delphix does not actually qualify or limit DB_NAME or ORACLE_SID in any way.

So, to answer the question directly, my advice for that VDB would be to set the DB_UNIQUE_NAME value to "ORCL_DEV" (or perhaps "ORCL01" or "ORCLDEV01" or something similarly unique) while leaving the VDB's values for DB_NAME and ORACLE_SID at the desired value of "ORCL".

That way, the DB_UNIQUE_NAME value of the VDB will not conflict with the DB_UNIQUE_NAME value of the dSource, which is probably why you are receiving the error message?

Again, Delphix does not make restrictions on DB_NAME or ORACLE_SID, just on DB_UNIQUE_NAME.

Does that answer your question?

Please let me know, and if you have trouble answer through this portal, please feel free to send me email at "tim.gorman@delphix.com"?

Thank you,

-Tim