CALCPARALLEL VS FIXPARALLEL

Продолжаем изучать революционный 500 патч.

Я обратил внимание , что в некоторых случаях принудительное распараллеливание работает хуже, старого , по умолчанию.  На этот счет у меня есть соображения общего характера и мнения от GlennS

1)  Принудительный Fork затратен.  Если расчет укладывается в 2-3 команды, то нужно тестировать что быстрее.

2)  Если Расчет уже параллелится , то “улучшайзинг” принесет только вред

3)  Так же это верно и при агрегации с помощью AGG and IDescendants

Т.е.  как всегда , пока универсального ответа нет как и чем параллелить расчеты, все нужно тестировать и проверять.

EPM 11.1.2.3.500

it’s time to update
IMHO мир essbase сейчас разделится на две половинки ) Без изучения новых технологий в следующем году старички значительно проиграют в конкуретной борьбе.

p.s. В очередной раз радует Oracle Support. Если создать case по воспроизведению ошибки , то исправление будет готово в ближайшее время )

upd. Неожиданно процесс обновления оказался не таким уж легким и приятным. ниже инструкция по применению

1) загрузить 17529887 патч
2) распаковать патчи 16964825 и 18362693 из каталога
\Middleware\EPMSystem11R1\OPatch\17529887\files\OPatch
3) установить 16964825 и 18362693 в -oh \Middleware\oracle_common
( перенести все файлы из 18362693\oui в 18362693\)
4) установить 17529887
5) передеплоить все приложения

upd 2
Для обновления клиентской части и SV нужно использовать отдельный пакет.

upd 3
И да, теперь нужно перестать ограничивать себя в памяти . У меня на тестовой среде значения в 24Gb были съедены в течении двух дней.
Так что прод должен начинаться от 32Gb RAM.

upd 4
Чем больше я изучаю новую версию, тем больше понимаю насколько она архитектурно отличается от предыдущих релизов. IMHO либо при апгрейде вы отключаетет все новые фичи, либо заново проходите UAT существующей модели.

upd 5
Две недели – полет нормальный.
Cameron поделился с народом о своем опыте установке 500 патча.

Essbase revolution is her: AsoDynamicAggINBso

CL Hybrid Essbase has arrived
Evolution or Revolution: The New Hybrid Essbase

Announcing Essbase 11.1.2.3.500

A new Essbase configuration setting, ASODYNAMICAGGINBSO, controls whether block storage databases use hybrid aggregation mode. Hybrid aggregation for block storage databases means that wherever possible, block storage data calculation executes with efficiency similar to that of aggregate storage databases.

The following are some scenarios where hybrid aggregation is highly likely to improve calculation performance:

  • A block storage database has stored members that are not level 0, and are calculated according to hierarchy (rather than by calculation scripts).
  • A Dynamic Calc member has more than 100 children.
  • You are using a transparent partition between an empty aggregate storage target and a block storage source. If the formulas on the aggregate storage target are simple and translatable to block storage formula language, you can achieve fast results on block storage using hybrid aggregation.
  • You are using a transparent partition between two block storage databases, and calculation performance is a concern.

Syntax

ASODYNAMICAGGINBSO [appname [dbname]] NONE | PARTIAL | FULL

Parameter Description
appname Optional. If you specify only an application, all the databases in that application are affected. If you leave out the application and database name parameters, the setting applies to the entire server.
dbname Optional. If you specify an application and database, the database you specify is affected by the setting.
NONE Disable hybrid aggregation in block storage databases (the default).
PARTIAL Turn on hybrid aggregation only for simple outline aggregations based on the consolidation operators +, -, and ~, but excluding the operators *, /, and %. Leave formulas to be calculated in block storage mode.
FULL Turn on hybrid aggregation for simple aggregations and formula calculations. See Notes for formula limitations.

Outline Structure for Hybrid Aggregation

To use hybrid aggregation most effectively:

  • If there are non-level-0 stored members that are batch calculated based solely on their hierarchy, it’s recommended that you convert them to Dynamic Calc members.
  • If the conversion to Dynamic Calc members affects solve order for dependent formulas, you may also need to adjust the outline’s order of dimensions, and/or their dense or sparse configurations, to align the solve order with the previous batch calculation order.

Notes

During hybrid aggregation, Dynamic Calc and Store members are treated as stored members.

If enabled, hybrid aggregation is supported for member formulas using any of the following functions: @CHILDREN, @EXP, @INT, @ISMBR, @MIN, @MINSRANGE, @MOD, @MODE, @NOTEQUAL, @POWER, @RANGE, @REMAINDER, @ROUND, @VAR, @VARIANCEP, and @VARPER.

The following types of calculations are not supported for hybrid mode. Essbase detects when these conditions are present, and calculates them in block storage mode.

  • Time-balance tagged members
  • Attribute calculations
  • Formulas with cross-dimensional operators
  • Dynamic Calc members with formulas that are a target of transparent partitions
  • Queries which include both two-pass and one-pass dynamic calc members from the same dimension
  • XOLAP

If a query mixes supported and unsupported hybrid mode calculation types, Essbase defaults to block storage execution.

Formulas with dimension references can run in hybrid mode in the following cases:

  • Sparse-to-Sparse: The formula is set on a sparse dimension member, and the formula only references member combinations from sparse dimensions.
  • Dense-to-Dense: The formula is set on a dense dimension member, and the formula only references member combinations from dense dimensions.
  • Sparse-to-Dense/Sparse: The formula is set on a sparse dimension member, and the formula references member combinations from both dense and sparse dimensions. The dense dimension members must be stored.

Example: On a sparse Product dimension, a Dynamic Calc member [Stereo_HY1] has the formula @MINSRANGE(“Stereo”,”Qtr1″:”Qtr2″);.

The formula depends on the dense Year dimension for [Qtr1] and [Qtr2], and the sparse Product dimension for [Stereo].

Enabling In-Place Data Writing with Exalytics

Остаются только детские эмоции, когда в угоду продаж железок портят софт. Теперь даже не будет предприниматься и попытки использовать старое место блока для записи .

——————–

The INPLACEDATAWRITE setting in essbase.cfg enables or disables in-place data writing.

Prior to this release, each time a data block was updated, it was written to a new disk location. With this release, for Exalytics, Essbase enables in-place data writing.

In-place data writing means that when updates occur, the data block can be written to the same location, as long as the compressed size of the data block fits in its original location on the disk.

In-place data writing can help reduce data fragmentation and lower the need for frequent restructuring of database. It also reduces the need for frequent index updates, resulting in improved performance.

Syntax and Usage of INPLACEDATAWRITE

INPLACEDATAWRITE [appname [dbname]] TRUE | FALSE

Keyword Description
appname Optional. If provided, the setting applies only to the specified application; otherwise, the setting applies to the Essbase Server.
dbname Optional. If provided, specifies the database.
TRUE In-place data writing is enabled for Exalytics. This is the default.
FALSE In-place data writing is disabled.

Notes

  • This configuration setting applies only when the ORACLEHARDWAREACCELERATION configuration  setting is set to TRUE.
  • If you set INPLACEDATAWRITE to TRUE, there is a risk to data integrity if Essbase terminates abnormally.

Example

INPLACEDATAWRITE Sample Basic FALSE