Release information

Product Adobe Experience Manager
Version 6.2
Release Oak Cumulative Fix Packs

Oak Cumulative Fix Packs

Fixes for the Oak repository are delivered via Oak Cumulative Fix Packs (OCFP) which are fully supported, similarly to standard Cumulative Fix Packs. An Oak Cumulative Fix Pack is self-dependant (no dependencies). You need not worry about finding/resolving dependencies.

Install the latest cumulative fix pack for your AEM version to keep your deployment up-to-date.

If necessary, a diagnostic build on top of the latest OCFP can be made available for validation purpose before the official availability of the next OCFP. The precondition is that you have the latest OCFP running. A diagnostic build only provide the same level quality assurance as a hot fix, therefore it doesn't provide the same level of quality assurance as a cumulative fix pack, service pack, or product release. All official Oak fixes will be released as OCFP which come the with full support.

For more information on CFP and other types of releases, see Maintenance Release Vehicle.

Installation instructions

Pre-deployment Procedure for Oak 1.4.8 and higher versions

The Oak Cumulative Fix Pack 1.4.8 (and beyond) contains index definitions. Before deploying the Oak 1.4.8+ CFP, we recommend to follow the below pre-deployment procedure for preparing the corresponding index during a maintenance window, as indexing can be resource intensive. This is a one-off procedure (no need to apply it again if you've already done it when applying a previous Oak CFP having a version >= 1.4.8).

Important: for building indices, Oak setting -Dupdate.limit should be set to a higher value, e.g. 200000. This will also require enough heap. 

  1. Install the index definition package NPR-14064, which contains index definitions with async re-index (it should not build new index right away)
  2. For Mongo: stop all AEM instances except for 1
  3. Visit this url:
    /system/console/jmx/org.apache.jackrabbit.oak%3Aname%3Dasync%2Ctype%3DPropertyIndexAsyncReindex
  4. Invoke startPropertyIndexAsyncReindex() to start indexing
  5. Monitor the log files for this log message:
    22.02.2017 11:34:32.602 *INFO* [aysnc-index-update-async-reindex] org.apache.jackrabbit.oak.plugins.index.AsyncIndexUpdate [async-reindex] Reindexing completed for indexes: [/oak:index/externalId*(0), /oak:index/externalPrincipalNames*(0), /oak:index/repMembers*(51)] in 1.085 s
  6. Verify that indices have been built successfully by checking following properties updated
    • reindexCount=1
    • async="async-reindex" would be deleted (with this the index would  switch back to synchronous indexing)
  7. This should be checked for these 3 indices (can also check that following query has no results: //element(*, oak:QueryIndexDefinition)[@async = "async-reindex"]
    • /oak:index/repMembers
    • /oak:index/externalPrincipalNames

    • /oak:index/externalId

  8. Note: index build can be stopped.  Go to this url:
    /system/console/jmx/org.apache.jackrabbit.oak%3Aname%3Dasync%2Ctype%3DIndexStats

During the process of async reindexing, a repository checkpoint is created. Once the indexing task has completed, it must be released as described below, to ensure smooth Revision Garbage Collection later on :

  1. First, open the CheckpointManager MBean:
    MongoMK -
    /system/console/jmx/org.apache.jackrabbit.oak%3Aname%3DDocument+node+store+checkpoint+management%2Ctype%3DCheckpointManger
    TarMK -
    /system/console/jmx/org.apache.jackrabbit.oak%3Aname%3DSegment+node+store+checkpoint+management%2Ctype%3DCheckpointManger
  2. Invoke the listCheckpoints() operation,
  3. Find the checkpoint row with the "name=async-reindex" property,
  4. Copy its id value to the clipboard
    On MongoMK it will look similar to this: r1234567aaaa-0-1
    On TarMK it will look similar to this: 6eac07d0-fe27-4d16-82f8-6d5da4cefd67
  5. Then open the releaseCheckpoint() operation,
  6. Paste the copied id as p1 and click "Invoke",
  7. This step will release the checkpoint.

Oak Cumulative Fix Pack installation

0. Make sure you have a backup of the data
1. Go to 'Tools' and doubleclick on 'Packages' to open the CQ Package Manager
2. Upload and Install the hotfix package
3. Restart AEM
 
In case this patch needs to be deployed in context of an upgrade to AEM 6.2 use the following steps:
0. Make sure you have a backup of the data
1. Prepare the source instance as documented and shut down
2. Unpack the AEM 6.2 Quickstart (java -jar quickstart.jar -unpack)
3. Unpack the Hotfix Package to a temporary location
4. Move /jcr_root/libs/system/install/* to /crx-quickstart/install
5. Move /jcr_root/libs/system/install/crx3/* to /crx-quickstart/install/15
6. Move on with the upgrade as documented
 

Megjegyzés:

If you are using LDAP integration then see the Known Issues section below.

Megjegyzés:

Uninstalling an OCFP is not supported.

Available Oak Cumulative Fix Packs

Oak 1.4.22

Date Name Fixes Release Notes
July 27, 2018 OCFP 23303 2 bugs Oak 1.4.22

Oak 1.4.21

Date Name Fixes Release Notes
May 11, 2018 OCFP 22306 2 bugs Oak 1.4.21

Oak 1.4.20

Date Name Fixes Release Notes
March 19th, 2018 OCFP 21560 3 bugs Oak 1.4.20

Oak 1.4.19

Date Name Fixes Release Notes
February 14th, 2018 OCFP 19228 19 bugs Oak 1.4.19

Oak 1.4.18

Date Name Fixes Release Notes
September 23rd, 2017 OCFP 18453 2 bugs Oak 1.4.18

Oak 1.4.17

Date Name Fixes Release Notes
August 9th, 2017 OCFP 17578 5 bugs Oak 1.4.17

Oak 1.4.16

Date Name Fixes Release Notes
June 20th, 2017 OCFP 16981 10 bugs Oak 1.4.16

Oak 1.4.15

Date Name Fixes Release Notes
April 28th, 2017 OCFP 15607 8 bugs Oak 1.4.15

Oak 1.4.14

Date Name Fixes Release Notes
April 20th, 2017 OCFP 15527 9 bugs Oak 1.4.14

Oak 1.4.13

Date Name Fixes Release Notes
March 7th, 2017 OCFP 14822 4 bugs Oak 1.4.13

Oak 1.4.12

Date Name Fixes Release Notes
Feb 27th, 2017 OCFP 14698 10 bugs Oak 1.4.12

Oak 1.4.11

Date Name Fixes Release Notes
Jan 4th, 2017 OCFP 14163 11 bugs Oak 1.4.11

Oak 1.4.10

Date Name Fixes Release Notes
Nov 29th, 2016 OCFP 13878 8 bugs Oak 1.4.10

Oak 1.4.9

Date Name Fixes Release Notes
Nov 9th, 2016 OCFP 13547 7 bugs Oak 1.4.9

Oak 1.4.8

Date Name Fixes Release Notes
Oct 21st, 2016 OCFP 1319 11 bugs Oak 1.4.8

Oak 1.4.7

Date Name Fixes Release Notes
Oct 11th, 2016 OCFP 12395 16 bugs Oak 1.4.7

Important Note

Oak 1.4.7 introduces a change in synchronization behavior of external group memberships (e.g. from LDAP):

Mapping an external group to an existing local group is no longer possible. The local group needs to be created by the IDP sync process and also cannotbe shared with other external IDPs anymore.

This is required to ensure boundaries between locally establishedgroup memberships and external ones, as well as to ensure boundariesbetween multiple IDPs.

The tie to an IDP is done via the now fully protected "rep:externalId" property on groups and users. For details and migration solutions see: https://issues.apache.org/jira/browse/OAK-4397

Oak 1.4.6

Date Name Fixes Release Notes
Oct 5th, 2016 OCFP 11905 6 bugs Oak 1.4.6

Known issues

  • For versions prior to Oak 1.4.5, due to a known issue (OAK-4538, addressed in Oak 1.4.5), it may happen that AEM cannot be gracefully stopped and in this case the termination of the jvm process needs to be forced.
  • If you are using Oak LDAP integration, then after applying the latest Oak hotfix, LDAP user sync will not longer work.  To fix this, go to /system/console/configMgr and update your "LDAP Identity Provider" configuration's "Custom Attributes" property.  Update the property with all LDAP attributes used in the Sync configuration.  For example, these properties might be: cn, sn, givenName, mail

Helpful resources

Ez a munka a Creative Commons Nevezd meg!-Ne add el!-Így add tovább! 3.0 Unported licenc alatt lett közzétéve.  A Twitter™ és Facebook közzétételeket a Creative Commons jogi feltételei nem szabályozzák.

Jogi közlemények   |   Online adatvédelmi nyilatkozat