DATA MASKING on EBS with Enterprise Manager

Transcription

1 DATA MASKING on EBS with Enterprise Manager DBA

2 Oracle E-Business Suite Data Masking Pack, Release with Oracle Enterprise Manager 12.1 (Doc ID ) We have followed the above document to perform data masking in EBS with EM 12c in cloned environment. You should read and understand all content described in document before you begin. EBS version : DB version : Note : if DB version is then upgrade the database to or higher version. To find exempt user for masking SQL> select fu.user_id, fu.user_name from applsys.fnd_user fu where fu.user_id < 1000 order by fu.user_id; USER_ID USER_NAME ANONYMOUS 0 SYSADMIN 1 AUTOINSTALL 2 INITIAL SETUP 3 FEEDER SYSTEM 4 CONCURRENT MANAGER 5 APPSMGR 6 GUEST 7 WIZARD 8 INDUSTRY DATA 120 ORACLE12.0.0

3 USER_ID USER_NAME ORACLE ORACLE ORACLE ORACLE ORACLE ORACLE ORACLE ORACLE ORACLE rows selected. The Oracle E-Business Suite Template for the Data Masking Pack is delivered as an XML template and some PL/SQL initialization scripts. These files are delivered via a zip file as Oracle E-Business Suite Patch SQL> select OWNER from all_tables where TABLE_NAME = 'JE_ES_MODELO_190_ALL'; OWNER JE Enterprise manager installation You can read the below document before proceeding the EM installation. Before Enterprise manager installation, you should install database software and create the repository database with preconfigured template for EM

4 2

5

6

7

8

9

10 Weblogic pwd : weblogic123 Nodemanager pwd : AceGroup123

11

12

13

14

15

16 URL :

17 Grid Agent Installation Grid Agent installation on the server where in Database to be monitored. Login into Enterprise manager console. Click Add

18 Click Deploy Agent

19

20 Prepare the Database SQL> GRANT INHERIT PRIVILEGES ON USER system TO apps; Grant succeeded. DATA MASKING preparation Pre Generate for Data masking : SQL> select count(*) "ninvalidbefore", to_char(sysdate,'yyyy-mm-dd HH24:MI:SS') "TimeStamp" from DBA_OBJECTS where STATUS = 'INVALID' / 2 3

21 ninvalidbefore TimeStamp :23:45 SQL> exec sys.utl_recomp.recomp_parallel; PL/SQL procedure successfully completed. SQL> select count(*) "ninvalidafter", to_char(sysdate,'yyyy-mm-dd HH24:MI:SS') "TimeStamp" from DBA_OBJECTS where STATUS = 'INVALID' / 2 3 ninvalidafter TimeStamp :23:58 Rerun these two SQL statements until the results from the first statement, which selects the count of invalids, remains the same. Unzip the patch [orauat@hrms-10-1-xxx-xx EBSMaskingPack1.1.4]$ pwd /u01/ebsmask/datamasking/patches/ebsmaskingpack1.1.4 [orauat@hrms-10-1-xxx-x EBSMaskingPack1.1.4]$ ls -ltr total rw-r--r-- 1 orauat oinstall 1275 Apr fndusmaexcr.sql -rw-r--r-- 1 orauat oinstall 1486 Apr ebs_post_generate.sql -rw-r--r-- 1 orauat oinstall 3822 May fndusmaexpo.sql -rw-r--r-- 1 orauat oinstall 751 Oct ebs_populate_synonyms.sql -rw-r--r-- 1 orauat oinstall Apr ebs_pre_generate.sql -rw-r--r-- 1 orauat oinstall 401 Mar README.txt -rw-r--r-- 1 orauat oinstall Mar ADM_EBS12.1.3_JG_V1.1.4_EM_12.1_Template.xml

22 -rw-r--r-- 1 orauat oinstall Mar ADM_EBS12.1.3_V1.1.4_EM_12.1_Template.xml -rw-r--r-- 1 orauat oinstall Mar Mask_EBS12.1.3_V1.1.4_EM_12.1_Template.xml -rw-r--r-- 1 orauat oinstall Mar Mask_EBS12.1.3_JG_V1.1.4_EM_12.1_Template.xml SQL> select count(*) "ninvalidbefore", to_char(sysdate,'yyyy-mm-dd HH24:MI:SS') "TimeStamp" from DBA_OBJECTS where STATUS = 'INVALID' / 2 3 ninvalidbefore TimeStamp :23:45 SQL> exec sys.utl_recomp.recomp_parallel; PL/SQL procedure successfully completed. SQL> select count(*) "ninvalidafter", to_char(sysdate,'yyyy-mm-dd HH24:MI:SS') "TimeStamp" from DBA_OBJECTS where STATUS = 'INVALID' / 2 3 ninvalidafter TimeStamp :23:58 SQL> show user USER is "SYSTEM" EBS drop table - FND_USER_MASKING_EXEMPTIONS Table or view does not exist, continuing PL/SQL procedure successfully completed. 20 rows created. Commit complete.

23 SQL> select user_id,current_name from FND_USER_MASKING_EXEMPTIONS; USER_ID CURRENT_NAME ANONYMOUS 5 APPSMGR 1 AUTOINSTALL 4 CONCURRENT MANAGER 3 FEEDER SYSTEM 6 GUEST 8 INDUSTRY DATA 2 INITIAL SETUP 120 ORACLE ORACLE ORACLE USER_ID CURRENT_NAME ORACLE ORACLE ORACLE ORACLE ORACLE ORACLE ORACLE SYSADMIN 7 WIZARD 20 rows selected.

24 Procedure created. EBS drop table - map_scl_dk Table or view does not exist, continuing EBS drop table - map_scl_nl_1 Table or view does not exist, continuing EBS drop table - map_scl_nl_2 Table or view does not exist, continuing EBS drop table - map_scl_nl_3 Table or view does not exist, continuing EBS drop table - map_scl_nl_4 Table or view does not exist, continuing EBS drop table - map_scl_nl_5 Table or view does not exist, continuing EBS drop table - map_scl_fi Table or view does not exist, continuing EBS drop table - map_pea_gb Table or view does not exist, continuing EBS drop table - map_pea_za Table or view does not exist, continuing EBS drop table - ni_mask Table or view does not exist, continuing EBS drop table - PER_ALL_PEOPLE_F_BKUP Table or view does not exist, continuing EBS drop table - HR_SOFT_CODING_BKUP Table or view does not exist, continuing EBS drop table - PAY_EXTRAL_ACCOUNTS_BKUP Table or view does not exist, continuing EBS drop table - PER_ADDRESSES_BKUP

25 Table or view does not exist, continuing EBS drop table - BEN_TRANSACTION_BKUP Table or view does not exist, continuing PL/SQL procedure successfully completed. Index created. Function created. Generate Masking Import XML ADM template. (goto Action tab and import) Template : ADM_EBS12.1.3_V1.1.4_EM_12.1_Template.xml (template file chosen from the patch )

26 Make verify ADM with source database Execute from sys user. SQL> grant Create Any Procedure to apps; Grant succeeded. SQL> grant Grant Any Object Privilege to apps; Grant succeeded. SQL> grant Execute Any Procedure to apps; Grant succeeded.

27 Import xml masking template. (template file chosen from the patch ) Template : Mask_EBS12.1.3_V1.1.4_EM_12.1_Template.xml

28 Generate the script as system user. It may take few hours to complete generation script. Once finish verify the log and save the masking script. (Action save script) Using the Data Masking Template (Not mandatory, Advised by Oracle support) Oracle recommends to change the credentials in the cloned database. Here I have not changed credentials because if require we can change later on. Appendix C of the "Secure Configuration Guide for Oracle E-Business Suite Release 12", Document

29 Execute Masking - Ensure system and temp tablespace having sufficient space. - Installing dm_fmtlib package as system user. Refer the below link. CA73D htm - Run the fndusmaexcr.sql script as the SYSTEM user. SQL> show user USER is "SYSTEM" EBS drop table - FND_USER_MASKING_EXEMPTIONS PL/SQL procedure successfully completed. 20 rows created. Commit complete. SQL> select count(1) from FND_USER_MASKING_EXEMPTIONS; COUNT(1) 20 - Execute below from sys user. SQL> grant execute on DBMS_CRYPTO to SYSTEM; Grant succeeded. Shutdown the Application. Within the data masking console in Oracle Enterprise Manager, run the mask for the script generated above using the SYSTEM user. Check "The selected target is not a production database" option on the schedule masking job page. ( correction : host user with normal and not with sudo privileges)

30

31 Compile the objects. select count(*) "ninvalidbefore", to_char(sysdate,'yyyy-mm-dd HH24:MI:SS') "TimeStamp" from DBA_OBJECTS where STATUS = 'INVALID' / exec sys.utl_recomp.recomp_parallel; select count(*) "ninvalidafter", to_char(sysdate,'yyyy-mm-dd HH24:MI:SS') "TimeStamp" from DBA_OBJECTS where STATUS = 'INVALID' /

32 Start the Applications. The data is changed after data masking over. SQL> select user_name, _address from fnd_user; USER_NAME _ADDRESS NZMBWDVQAK EEMXBAWEIS AWCMBCRXBQ MKDLKZJAKT WNEDLOSWDS MTGZXNDQGU PIWOYGGKRW JSFKVWAPCR OJSHDVVGIU MKVWJLFLCE RGWRPRPCJD USER_NAME _ADDRESS AMPGTKJALR OFUXGKEZAE GJWNCLZAHN

33 WTTGLKCBEV PRNCRLUROM YONBAIXPEW VSXEYWFLVG