Comments on: Oracle BI EE 10.1.3.4.1 – Persistent Connection Pool – Converting In-Memory BI Server Processing to Temporary Tables

By: Ash

Ash — Thu, 27 Aug 2009 10:22:32 +0000

I have a query regarding in memory stitch join. I have a report where OBI generates 4 separate queries and does an in memory stitch join for the actual result. This is resulting in some performance issue. Just wanted to check how can we avoid these in memory stitch joins in OBI so that it generates only a single query.

Thanks,
Ash

By: Venkatakrishnan J

Venkatakrishnan J — Fri, 21 Aug 2009 21:56:40 +0000

@Debu – Good point. One issue with your approach is that one cannot expect what report will create temporary tables. In my case above, i had to simulate a case wherein the temporary table was actually created. This will not be true in all the cases as it is at the discretion of the BI Server. Also the names are dynamic. So we cannot drop any specific temporary table. Of course we cannot drop all of them as some of them might be used by other queries.

By: Debu@S

Debu@S — Thu, 20 Aug 2009 23:52:43 +0000

Though I have not tried it but I believe for the connection pool, under ‘Connection Scripts’ a SQL script can be associated for ‘Execute on disconnect’ to drop these temporary tables.

By: Vinod jaganathan

Vinod jaganathan — Fri, 14 Aug 2009 02:40:56 +0000

Clear and good post . Some time back I noticed we have lot ot temporary tables only on production and now I knew how its created .Could you please help me how to configure drop table ddl after end of request . In my system temporary tables are physically present (user_tables) .

By: Nicolas GERARD

Nicolas GERARD — Tue, 11 Aug 2009 09:27:21 +0000

Thanks for this good and clear post.