The latest rollup patch for BIP 11.1.1.5 is available, 12954375. For your delight and delectation and to bulk out this post, I have reproduced the readme file below.
This patch contains fixes of following bugs for Oracle Business Intelligence Publisher 11.1.1.5.0.
10402890 - SETTINGS FROM "DELIVERY CONFIGURATION" PAGE NOT BEING HONORED WHEN REPORTS RUN 11725468 - ER: RTE HTML SUPPORT IN DATA XML 11828672 - QA: INCORRECT INACTIVE WARNING MESSAGE 11835845 - 11G SQL DATA SET CREATION ORA-01756 ERROR BECAUSE COLON IS READ AS BIND VARIABLE 12376386 - REMOVETEMPLATEFORREPORT API DOESN'T REMOVE TEMPLATE 12405904 - CANNOT DEPLOY BIP WHEN DEPLOYMENT PATH INCLUDES SPACE CHARACTERS 12406034 - CANNOT USE JAVA DB - DERBY - FOR SCHEDULER DATABASE 12595931 - WHEN PRINTING CHARTS TO PDF, NUMBERS BECOME ARABIC NUMBERS 12615821 - MISSING MEMBERS ON THE XML GENERATED BY BIP 12634030 - RE-PACKAGING MLR#11893189 TO XDOPARSER11G.JAR 12666066 - ER: EXCEL 2007 SUPPORT IN REST API 12705244 - JOINED MDX DATA SETS DO NOT PRODUCE CORRECT DATA - DATA MISSING 12726163 - NUMBER OF SESSIONS INCREASES AFTER RUNNING SCHEDULED JOBS 12737670 - GROUP BY FOR MDX DATA SET MISSING IN 11.1.1.5 - WAS PRESENT IN 11.1.1.3 12750192 - ER: GENERATE NATIVE COMBINATION DUAL Y GRAPH IN PPTX OUTPUT FROM RTF AND XPT 12766932 - VERTICAL DUAL Y COMBO CHART MISSING SETTINGS TO ASSIGN VALUES TO AXIS 12791282 - WS PROXY WIZARD CANNOT GENERATE PROXY WHEN SERVICE NAME HAS SPECIAL CHARACTERS 12828845 - ISSUE WITH XDO_USER_NAME PARAMETER ON BIP 11.1.1.5.0 12835431 - INTRANSIT VALUATION REPORT QUERY GIVING ERROR IN EDITOR 12847306 - BI PUBLISHER DATA SET - WON'T SAVE 12872831 - EXCEL TEMPLATES GENERATING INCORRECT RESULTS FROM NESTED GROUPS 12879801 - ALLOW SAVING DATA MODEL WITH SPECIAL CHARACTER 12945367 - NOT ABLE TO EDIT DATA MODEL WHEN LINKS EXIT AMONG DATA SETS 12945475 - IE: NOT ABLE TO EDIT DATA MODEL WITH MANY DATA SET AND LINKS 12956901 - IN SQL SERVER CLOB IN DATA MODEL UI MARKED AS STRING DATA TYPE 12956915 - INCORRECT DATA WHEN PROCESSING OF CLOB COLUMNS FOR SQLSERVER 12956934 - DATA MODEL SHOULD RESPECT CASE SENSITIVITY FOR COLUMN AND TABLE NAMES 12972852 - DYNAMIC IMAGES BROKEN FOR FO/PDF 12989467 - NEED TO CONVERT DOCUMENT FORMAT "EXCEL" TO "EXCEL2000"
----------------------------- INSTALLATION FOR ENTERPRISE -----------------------------
1. Login to BI Domain Weblogic Administration Console.
2. Find the location of the "bipublisher".
3. Stop the bipublisher application.
4. Open a terminal and go to the directory.
5. Back up the existing xmlpserver.ear to xmlpserver.ear.org.
6. Copy new xmlpserver.ear from this patch.
7. In Admin Console, select "Lock & Edit".
8. Select the application "bipublisher" and "Update".
9. Leave all options same and proceed to Finish.
10. Select "Activate Changes".
11. Start the bipublisher application.
------------------------- MDX Query Limitation -------------------------
Joins of two MDX queries on a dimension that uses a MDX function in the Select Clause that requires the stipulation of the same dimension, such as Intersect, MemberRange, Union are not supported. Example
SELECT NON EMPTY Hierarchize([Product].Generations(3).Members) ON Axis(0), Hierarchize(Union([Market].Generations(3).Members, [Market].Generations(4).Members, ALL)) ON Axis(1) FROM Demo.BasicIt should be written using a With Set member:
with set [UnionMarket] as '{Union([Market].Generations(3).Members, [Market].Generations(4).Members, ALL)}'
SELECT
NON EMPTY Hierarchize([Product].Generations(3).Members) ON Axis(0),
Hierarchize(([UnionMarket]) ON Axis(1)
FROM Demo.Basic
This MDX set is recreated for the Join clause to:
with set [UnionMarket] as '{Union([Market].Generations(3).Members, [Market].Generations(4).Members, ALL)}'
SELECT
NON EMPTY Hierarchize([Product].Generations(3).Members) ON Axis(0),
Hierarchize(Filter([UnionMarket], [Market].CurrentMember.Member_Name = "Boston")) ON Axis(1)
FROM Demo.Basic Plus you have the new XHTML formatter included in the patch too, more on that here.