Moving QC projects into tn ENCRYPTED Oracle tablespace?

  • Questions
  • Moving QC projects into tn ENCRYPTED Oracle tablespace?
Question ID: 108392
0
0

We successfully created a few new projects using a Oracle tablespace that is not encrypted.

Now we plan on moving these projects to oracle database/tablespace that is ENCRYPTED. Would this database change be ok? Are you aware of any possible issues?

Marked as spam
Posted by (Questions: 76, Answers: 4)
Asked on May 10, 2018 3:33 pm
3 views
Answers (1)
0
Private answer

Your change is okay. You can enable Oracle encryption (sometimes called TDE) support in the following way.

Encryption on ORACLE requires an additional clause in Database connect string:

Example without:
jdbc:mercury:oracle:TNSNamesFile=C:Oracletnsnames.ora;TNSServerName=QC.world

Example with encryption:
jdbc:mercury:oracle:TNSNamesFile=C:Oracletnsnames.ora;TNSServerName=QC.world;EncryptionLevel=required

This will need to change EVERYWHERE -- each ''encrypted'' project will need to be ''fixed'' to point to the schema this way as well (remove edit DBID to change connect string,
restore). It has to change on the DB-Servers tab, AND it has to change in Siteadmin.xml as well.

This is as big of a change as changing Database Servers, so be careful!

Marked as spam
Posted by (Questions: 0, Answers: 15)
Answered on May 10, 2018 3:36 pm