PeopleTools and Lifecycle Management - PSFT (MOSC)

MOSC Banner

nVision ExcelAutomation versus OpenXML performance

edited Apr 24, 2018 10:17PM in PeopleTools and Lifecycle Management - PSFT (MOSC) 2 commentsAnswered

We have 60+ nVision layouts, some are matrix, some are tabular. Oracle have advised with the later tools releases like 8.54, 8.55, 8.56 that it is preferable to use OpenXML for generating nVision reports, but my personal experience with this thus far is that it is more complicated than what Oracle states, and from all my searching, I don't think I could find anything really of substance.

We have been converting layouts to run under OpenXML, but sometimes there is a significant performance issue. As an example of one report, it has 3 sheets which are tabular layouts. Each sheet might have a result set of 5,000 rows. Under ExcelAutomation, it takes 20 seconds to run, but when run in OpenXML, takes 25 minutes. The problem is definitely not the SQL, because this report has been used for years under ExcelAutomation, and always ran quite quickly. Another report took only a minute or two to run under ExcelAutomation, but 20 minutes in OpenXML. This one has 8

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

PSFT PeopleTools Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center