This page (revision-5) was last changed on 26-Nov-2021 10:22 by rforbes

This page was created on 26-Nov-2021 10:22 by rforbes

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
5 26-Nov-2021 10:22 2 KB rforbes to previous
4 26-Nov-2021 10:22 2 KB rforbes to previous | to last
3 26-Nov-2021 10:22 2 KB rforbes to previous | to last
2 26-Nov-2021 10:22 2 KB rforbes to previous | to last
1 26-Nov-2021 10:22 2 KB rforbes to last

Page References

Incoming links Outgoing links
MOVING AN ENCRYPTED DATABASE
MOVING AN ENCRYPTED DATABASE

Version management

Difference between version and

At line 1 changed one line
Steps to follow to export/import a database with encryption enabled, after the dump file has been imported into the new database:
!Importing to a new database
At line 3 added 2 lines
If you are exporting a database that has already had encryption enabled (even if no fields have been encrypted), you must follow these steps __after__ you have imported the dump file into the new database, that has not had encryption enabled.
At line 13 changed one line
{{{ALTER ROLE p2k_dba NOT IDENTIFIED;}}}
{{{
ALTER ROLE p2k_dba NOT IDENTIFIED;
}}}
At line 29 changed one line
Test getting the encryption values using something with encryption on such as:
{{{
At line 31 removed 7 lines
rca.CANDIDATE_CODE,
rca.DRIVERS_LICENSE,
rca.RAW_DRIVERS_LICENSE,
p2k_pmsec.decrypt(rca.RAW_DRIVERS_LICENSE) d_lic,
rca.GOVERNMENT_CODE,
rca.RAW_GOVERNMENT_CODE,
p2k_pmsec.decrypt(rca.RAW_GOVERNMENT_CODE) GC,
At line 40 changed 2 lines
p2k_pmsec.decrypt(rca.RAW_BIRTH_DATE) BD
FROM
p2k_pmsec.decrypt(rca.RAW_BIRTH_DATE) decryption
FROM
At line 43 changed 2 lines
WHERE
rca.CANDIDATE_CODE IN( '0000', '0000000908')
where rownum < 30;
}}}
At line 46 changed 5 lines
There are many errors that can happen at this point.
If you get that no key was supplied then other actions have set the Context to say no key found. Use this to force read the key from the disk and then try again:
BEGIN
p2k_pmsec.getkeyfromdisk;
END;
9. Execute the DB_RECOMPILE.sql script and rectify any compile errors.
At line 52 changed 9 lines
If you get this then the key is corrupt and likely not transfered in a binary mode.
ORA-28817: PL/SQL function returned an error.
ORA-06512: at "SYS.DBMS_CRYPTO_FFI", line 67
ORA-06512: at "SYS.DBMS_CRYPTO", line 44
ORA-06512: at "P2K.P2K_PMSEC", line 753
ORA-06512: at "P2K.P2K_PMSEC", line 723
28817. 00000 - "PL/SQL function returned an error."
*Cause: A PL/SQL function returned an error unexpectedly.
*Action: This is an internal error. Contact Oracle customer support.
10. Execute the DB_UMRS.sql script to set the users/roles at the DB properly. This will put any role passwords in step 5 back.
At line 62 changed one line
Execute the DB_RECOMPILE.sql script and rectify any compile errors.
!Importing to a database that previously had encryption
At line 64 changed one line
Execute the DB_UMRS.sql script to set the users/roles at the DB properly.
If your target database previously had encryption enabled (even if no fields were encrypted), you must follow these steps after the dump file has been imported:
1. Copy the key files (from the source database) into them, use a binary transfer method so that bad characters do not get added to the end.
This page (revision-5) was last changed on 26-Nov-2021 10:22 by rforbesTop