Why a big .lar import, using SQL Server database makes the Liferay system unreachable?
Written By
Sebastian Madaras
How To articles are not official guidelines or officially
supporteddocumentation. They are community-contributed content and may
not alwaysreflect the latest updates to Liferay DXP. We welcome your
feedback toimprove How to articles!
While we make every effort to ensure this Knowledge Base is accurate,
itmay not always reflect the most recent updates or official
guidelines.We appreciate your understanding and encourage you to reach
out with anyfeedback or concerns.
Legacy Article
You are viewing an article from our legacy
"FastTrack"publication program, made available for
informational purposes. Articlesin this program were published without a
requirement for independentediting or verification and are provided
"as is" withoutguarantee.
Before using any information from this article, independently verify
itssuitability for your situation and project.
Issue
- The Customer has initiated a big .lar import, and during the actual import-process the system cannot be accessed.
Environment
- Liferay 6.2
- Liferay 7.0
- Liferay 7.1
- Liferay 7.2
- Liferay 7.3
Resolution
-
For SQL Server to function properly. SQL Server’s Read Committed Snapshot Isolation level must be turned on. While other databases enable this behavior out of the box, it is disabled by default for SQL Server.
Did this article resolve your issue ?