Legacy Knowledge Base
Published Sep. 10, 2025

For Oracle Database users, ORA-01795 appears while reindexing

Written By

Brian Suh

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • For Oracle Database users, an error indicating ORA-01795 appears while reindexing
    • ORA-01795: maximum number of expressions in a list is 1000

Environment

  • Liferay DXP 7.3

Resolution

  • Please try to adjust the value.object.finder.cache.list.threshold property (in portal-ext.properties). This property configures the list threshold for the maximum number of objects to cache with the same finder path and arguments. The default value is set at 10,000.
  • We have found that some subscribers who experience this behavior have benefited from setting the value of value.object.finder.cache.list.threshold to 1000.
    • For example, append value.object.finder.cache.list.threshold=1000 in portal-ext.properties.
    • Since we're lowering the value of this property to the maximum value that Oracle supports, there should be no apparent performance impact on the Liferay application. You may observe a slight increase in CPU load on the database due to the increase in successful queries.


Additional Information

 

Did this article resolve your issue ?

Legacy Knowledge Base