Skip to main content

How to apply DAC patch 12381656

By


It is mandatory to apply DAC patch 12381656 while using Oracle Business Intelligence Data Warehouse Administration Console 10.1.3.4.1 (DAC).



DAWSystem.jar - DAC Build # 10.1.3.4.1.patch.20111228.1556
infa_command.xml (see note 1 at the end)
siebproc.sql (see note 2 at the end)
automationUtils.bat (see note 3 at the end)


Fixes for the following bugs:
1.  Unique constraint (W_ETL_SYSPROP_U1) violated when importing DAC metadata in incremental way without truncate flag (8723317)

2.  Can't override DAC Email notification port, always uses port 25. SSL support added. (8570833)

3.  DAC Server couldn't start on 64-bit AIX. (8584709)

4.  DAC Server hanging at the end of ETL process (8743856)

5. Allowing DAC parameters in commands for full and incremental mode (8760212)

6. Index creation in DAC reported as noticeably longer then on database

7. DAC doesn't connect to SQL Server 2008 properly (9179169)

8. Various problems importing column definitions from database

9. DAC Server intermittent hang/crash (9015527)

10. DAC Task Group 'Execute Serially' option not working as desired (9252632)

Fixed in 10.1.3.4.1.patch.20100901.0520

11. DAC metadata import/export hangs with Java 1.6.0_18 (9532623)

12. Prevent inadvertent DAC repository upgrade (9538183)

13. RFA: 3-1474029951 - Change Capture tasks does not complete (9449388)

14. DAC upgrade from 7.8.4 to 10.1.3.4.1 – execution type and phases (9682840)

15. Import dac repository failed with java.lang.NullPointerException error (8702384)

16. Query indexes not created after table truncated (9907892)

17. Setting null as a ref date for one of the primary src tables does not force full load (10014476)

18. Incorrect script for stored procedure "siebdbx" creation, used for ETL run (9486873)

19. Oracle index failures messages are not captured by DAC client 10.1.3.4.1 (9977568)

20. Unable to create a DAC repository on a unicode DB2 database (8476448)

Fixed in 10.1.3.4.1.patch.20110427.0538

21. 10248767 DAC: FAILURE CONNECTING MSSQL DRIVER NOT AVAILABLE

22. 10435916 GENERATE UPGRADE SCRIPTS FOR TERADATA DW FAILS

23. 10368123 DAC 10.1.3.4.1 NVARCHAR DATATYPE NOT SUPPORTED

24. 9363341 DAC IMPORT SETS PHYSICAL CONNECTIONS URL FIELD BLANK

25. 11722188 DAC TASK ACTION - FAILURE ACTION NOT WORKING

26. 11793451 ISSUE IN UPGRADE-REGULAR.SQL FILE IN TERADATA OLAP

27. 11876706 UPGRADE 7961- 7962:UPGRADE-QUESTIONABLE.SQL FILE HAS TABLE LENGTH > 30 CHARS

28. 11892723 DAC EXPORT IMPORT DOES NOT MIGRATE TASK ACTIONS

29. 12382199 AUTOMATIONUTILS IMPORT WITHOUT TRUNCATE REQUIRED

30. 11930205 WRONG BIND VARIABLE DATATYPE PASSED BY DAC

Fixed in 10.1.3.4.1.patch.20110908.1744

31. 12559167 SOURCE SYSTEM FOLDERS NOT GETTING PROCESSED IN REPLACE BASE

32. 12679355 DAC ETL FAILING WITH ERROR ORA-01000: MAXIMUM OPEN CURSORS EXCEEDE

33. 12686915 DAC EMAIL NOTIFICATIONS ARE NOT BEING SENT AT TASK LEVEL

34. 12553329 TRUNCATE TABLE AND ANALYZE TABLE ISSUED ON FLAT FILE  TARGETS 

35. 12866726 ERROR IMPORTING INDEX FROM DATABASE TO DAC

Fixed in 10.1.3.4.1.patch.20111228.1556

36. 13403439 DAC REPOSITORY UPGRADE - "REPLACE BASE" OPTION LEAVES DAC IN INCOMPLETE STATE

37. 13400680 - UNABLE TO GET INFORMATICA WORKFLOW RETURN CODE ERROR

Fixed in 10.1.3.4.1.patch.20120711.0516

38. 13680270 ERROR WHILE REBUILDING A DAC EXECUTION PLAN

39. 13709324 ETL FAILS SINCE INDEX ALREADY EXISTS

40. 13987080 VIEW CREATION FOR CHANGE CAPTURE FAILS ON COLUMN NAMES WITH SPECIAL CHARACTERS

41. 14306733 LOOSING THE TIMESTAMP PART WHILE DOING CHANGE CAPTURE FOR SIEBEL

42. 14171067 SIMPLIFIED REFRESH FROM BASE INTRODUCES DUPLICATES

43. 14305802 SQL FORMAT DB SPECIFIC DOES NOT GIVE CORRECT SYNTAX FOR DB2-390


How to apply?
-------------
Terminate or stop all DAC clients and server(s).
Rename DAWSystem.jar file in the current DAC environment.
Copy the DAWSystem.jar file from the patch into the DAC home directory on all client and server machines.
You should NOT connect to the repository using different versions of DAC client/servers.

Restart the client.

If you have 7.9.x DAC platform you will be prompted to upgrade the repository. Choose 'Yes' if prompted.
There is no repository upgrade necessary for DAC 10.1.3.4.1.

Repeat the process for all environemtns, e.g. development, test, production. 


Please follow this screen shot to apply DAC patch





Labels:

Comments

Post a Comment

Popular posts from this blog

Contact Me

By
Do You have any queries ?                   If you are having any query or wishing to get any type of help related Datawarehouse, OBIEE, OBIA, OAC then please e-email on below. I will reply to your email within 24 hrs. If I didn’t reply to you within 24 Hrs., Please be patience, I must be busy in some work. kashif7222@gmail.com
3 comments
Read more

Top 130 SQL Interview Questions And Answers

By
1. Display the dept information from department table.   Select   *   from   dept; 2. Display the details of all employees   Select * from emp; 3. Display the name and job for all employees    Select ename ,job from emp; 4. Display name and salary for all employees.   Select ename   , sal   from emp;   5. Display employee number and total salary   for each employee. Select empno, sal+comm from emp; 6. Display employee name and annual salary for all employees.   Select empno,empname,12*sal+nvl(comm,0) annualsal from emp; 7. Display the names of all employees who are working in department number 10   Select ename from emp where deptno=10; 8. Display the names of all employees working as   clerks and drawing a salary more than 3000   Select ename from emp where job=’clerk’and sal>3000; 9. Display employee number and names for employees who earn commission   Select empno,ename from emp where comm is not null and comm>0. 10
32 comments
Read more

Informatica sample project

By
Informatica sample project - 1 CareFirst – Blue Cross Blue Shield, Maryland (April 2009 – Current) Senior ETL Developer/Lead Model Office DWH Implementation (April 2009 – Current) CareFirst Blue Cross Blue Shield is one of the leading health care insurance provided in Atlantic region of United States covering Maryland, Delaware and Washington DC. Model Office project was built to create data warehouse for multiple subject areas including Members, Claims, and Revenue etc. The project was to provide data into EDM and to third party vendor (Verisk) to develop cubes based on data provided into EDM. I was responsible for analyzing source systems data, designing and developing ETL mappings. I was also responsible for coordinating testing with analysts and users. Responsibilities: ·          Interacted with Data Modelers and Business Analysts to understand the requirements and the impact of the ETL on the business. ·          Understood the requirement and develope
Post a Comment
Read more