Uploaded image for project: 'PUBLIC - Liferay Documentation'
  1. PUBLIC - Liferay Documentation
  2. LRDOCS-332

Required settings for Oracle is not documented and thus users might experience ORA-01450 due to misconfiguration when indices are being created

    Details

    • Type: New Article
    • Status: Closed
    • Priority: Minor
    • Resolution: Reorganized
    • Fix Version/s: None
    • Component/s: Core Infrastructure
    • Labels:
    • Environment:
      LIFERAY VERSION: 6.x
      OPERATING SYSTEM: Any
      APPLICATION SERVER: Any
      JAVA VIRTUAL MACHINE: Any
      DATABASE: Oracle 10g/11g

      Description

      Background

      The documentation of Liferay 6.x is not detailed enough and does not contain those preliminary settings which need to be checked by DBAs in order to deploy Liferay properly.

      http://www.liferay.com/documentation/liferay-portal/6.0/administration/-/ai/installing-liferay-for-an-enterpri-4
      http://www.liferay.com/documentation/liferay-portal/6.1/user-guide/-/ai/installing-liferay-on-an-existing-application-serv-1

      Experienced phenomenon

      Having the NLS_LENGTH_SEMANTICS set to CHAR or creating the database with a block size less than 8K prevents Liferay to create some indices.

      • When NLS_LENGTH_SEMANTICS=CHAR
      2012-11-08 11:17:42,581 INFO  [STDOUT] 11:17:42,580 WARN  [BaseDB:382] ORA-01450: maximum key length (6398) exceeded: create unique index IX_DD635956 on Lock_ (className, key_, owner);
      2012-11-08 11:17:45,982 INFO  [STDOUT] 11:17:45,982 WARN  [BaseDB:382] ORA-01450: maximum key length (6398) exceeded: create index IX_88705859 on ResourcePermission (companyId, name, primKey, ownerId);
      2012-11-08 11:17:45,986 INFO  [STDOUT] 11:17:45,986 WARN  [BaseDB:382] ORA-01450: maximum key length (6398) exceeded: create index IX_C94C7708 on ResourcePermission (companyId, name, primKey, roleId, actionIds);
      2012-11-08 11:17:46,012 INFO  [STDOUT] 11:17:46,012 WARN  [BaseDB:382] ORA-01450: maximum key length (6398) exceeded: create index IX_2200AA69 on ResourcePermission (companyId, name, scope, primKey);
      2012-11-08 11:17:46,015 INFO  [STDOUT] 11:17:46,015 WARN  [BaseDB:382] ORA-01450: maximum key length (6398) exceeded: create index IX_8D83D0CE on ResourcePermission (companyId, name, scope, primKey, roleId);
      2012-11-08 11:17:46,020 INFO  [STDOUT] 11:17:46,018 WARN  [BaseDB:382] ORA-01450: maximum key length (6398) exceeded: create index IX_D2E2B644 on ResourcePermission (companyId, name, scope, primKey, roleId, actionIds);
      2012-11-08 11:17:46,024 INFO  [STDOUT] 11:17:46,024 WARN  [BaseDB:382] ORA-01450: maximum key length (6398) exceeded: create index IX_4A1F4402 on ResourcePermission (companyId, name, scope, primKey, roleId, ownerId, actionIds);
      
      • When DB_BLOCK_SIZE=4K
      11:45:24,549 WARN  [pool-2-thread-1][BaseDB:428] ORA-01450: maximum key length (3118) exceeded: create index IX_7020130F on SCProductVersion (directDownloadURL);
      11:45:25,706 WARN  [pool-2-thread-1][BaseDB:428] ORA-01450: maximum key length (3118) exceeded: create index IX_89509087 on User_ (companyId, openId);
      

      Solution

      Customers tend to ask about the recommended settings in terms of Oracle and it's a frequently recurring question as well. Of course we cannot foretell all the parameters which would make a certain installation to operate optimally, but at least those factors should be documented that hamper Liferay's deployment.

      Affected customer's so far

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Packages

                Version Package