-
Allen Lai authored
Previously, we use server uuid to compose the master key name, and we didn't store the server uuid to data file of tablespace. So, if server uuid is changed or slave server need to use a different uuid, the encrypted tablespace will not get the correct master key, since the key name in key file is still composed by old server uuid. The solution is: we need to store the uuid into page 0 of tablespace data file. And we need to keep it to Encryption object. Reviewed-by:
Jimmy <Yang<jimmy.yang@oracle.com> Kevin<kevin.lewis@oracle.com> Maheehar<maheedhar.panchalamarri.venka@oracle.com> RB:12145
Allen Lai authoredPreviously, we use server uuid to compose the master key name, and we didn't store the server uuid to data file of tablespace. So, if server uuid is changed or slave server need to use a different uuid, the encrypted tablespace will not get the correct master key, since the key name in key file is still composed by old server uuid. The solution is: we need to store the uuid into page 0 of tablespace data file. And we need to keep it to Encryption object. Reviewed-by:
Jimmy <Yang<jimmy.yang@oracle.com> Kevin<kevin.lewis@oracle.com> Maheehar<maheedhar.panchalamarri.venka@oracle.com> RB:12145
Loading