Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

(2 Ratings)
facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

FAQ: What are the limitations of the Aggregator sorted input option?
Answer

The PowerCenter sorted input option in an Aggregator transformation is ignored if any of the following conditions are true:

  • The aggregate expression uses nested aggregate functions.
  • The session uses incremental aggregation.

When any of these conditions are true, the Integration Service processes the transformation as if you do not use sorted input.

Nested aggregate functions

An aggregate expression can include one aggregate function nested within another aggregate function, such as:

MAX(COUNT( ITEM ))

Incremental aggregation

Using incremental aggregation, you can apply captured changes in the source to aggregate calculations in a session. If the source changes incrementally and you can capture changes, you can configure the session to process those changes.
This allows the Integration Service to update the target incrementally, rather than forcing it to process the entire source and recalculate the same data each time you run the session.


More Information

Applies To
Product: PowerCenter
Problem Type:
User Type: Administrator
Project Phase:
Product Version: PowerCenter
Database:
Operating System:
Other Software:

Reference

"Aggregate Expressions" and "Using Sorted Input" in "Aggregator Transformation" chapter of the PowerCenter Transformation Guide

http://technet.oracle.com/products/discoverer/pdf/calcul.pdf


Attachments

Last Modified Date:1/6/2012 7:14 AMID:20369
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)