Import LDIF file to WindchillDS fails with error "Import task XXXXXXXXXXXXXXXXX did not complete successfully" in Windchill PDMLink

• Import LDIF file to WindchillDS fails with error "Import task XXXXXXXXXXXXXXXXX did not complete successfully" in Windchill PDMLink
• WindchillDS\logs\errors contains below error message :

severity="NOTICE" msgCount=5 msgID=20381713 message="JVM Information: 1.8.0_202-b08 by Oracle Corporation, 64-bit architecture, 2863661056 bytes heap size"
severity="NOTICE" msgCount=6 msgID=20381714 message="JVM Host: <Hostname>, running Windows Server 2016 10.0 amd64, 12884430848 bytes physical memory size, number of processors available 4"
severity="NOTICE" msgCount=7 msgID=20381715 message="JVM Arguments: "-Xrs", "-Dorg.opends.server.scriptName=start-ds"
severity="NOTICE" msgCount=8 msgID=8847546 message="The amount of free memory available to the import task is 969171314 bytes. The number of phase one buffers required is 480 buffers"
severity="NOTICE" msgCount=9 msgID=8847568 message="The amount memory available to the temporary DN cache environment is 319745432 bytes"
severity="NOTICE" msgCount=10 msgID=8847545 message="Setting DB cache size to 319745432 bytes and phase one buffer size to to 549057 bytes"
severity="NOTICE" msgCount=11 msgID=8847533 message="PTC Windchill Directory Server 2.6.0-Build_007 starting import (build 20150813161048Z, R9086)"
severity="NOTICE" msgCount=12 msgID=8847449 message="Import Thread Count: 8 threads"
severity="SEVERE_ERROR" msgCount=13 msgID=10748000 message="An error occurred while attempting to process the LDIF import: Setting indexes trusted failed for the following reason: (JE 18.3.12) Disk usage is not within je.maxDisk or je.freeDisk limits and write operations are prohibited: maxDiskLimit=0 freeDiskLimit=5 368 709 120 adjustedMaxDiskLimit=0 maxDiskOverage=0 freeDiskShortage=4 610 842 624 diskFreeSpace=757 866 496 availableLogSize=-4 610 842 624 totalLogSize=6 180 768 activeLogSize=6 180 768 reservedLogSize=0 protectedLogSize=0 protectedLogSizeMap={}"
severity="INFORMATION" msgCount=14 msgID=9437595 message="Local DB backend userRoot does not specify the number of lock tables: defaulting to 97"
severity="INFORMATION" msgCount=15 msgID=9437595 message="Local DB backend userRoot does not specify the number of lock tables: defaulting to 97"
severity="SEVERE_ERROR" msgCount=16 msgID=3408518 message="org.opends.server.admin.server.ConfigChangeListenerAdaptor.applyConfigurationChange failed for entry ds-cfg-backend-id=userRoot,cn=Backends,cn=config: result code=Other, admin action required=false, messages="An error occurred while trying to initialize a backend loaded from class org.opends.server.backends.jeb.BackendImpl with the information in configuration entry ds-cfg-backend-id=userRoot,cn=Backends,cn=config: je.lock.nLockTables is set to 97 in the config parameter which is incompatible with the value of null in the underlying environment (EnvironmentMutableConfig.java:626 DbInternal.java:622 EnvironmentImpl.java:2607 DbEnvPool.java:171 Environment.java:278 Environment.java:258 Environment.java:228 RootContainer.java:218 BackendImpl.java:1746 BackendImpl.java:319 BackendConfigManager.java:1298 BackendConfigManager.java:751 BackendConfigManager.java:69 ServerManagedObjectChangeListenerAdaptor.java:74 ConfigChangeListenerAdaptor.java:342 ConfigFileHandler.java:1759 LocalBackendModifyOperation.java:607 LocalBackendWorkflowElement.java:551 WorkflowImpl.java:197 WorkflowTopologyNode.java:100 ModifyOperationBasis.java:520 ...). This backend will be disabled""
severity="INFORMATION" msgCount=17 msgID=9437595 message="Local DB backend userRoot does not specify the number of lock tables: defaulting to 97"
severity="SEVERE_WARNING" msgCount=18 msgID=3277447 message="org.opends.server.admin.server.ConfigChangeListenerAdaptor.applyConfigurationChange indicated that administrative action is required for entry ds-cfg-backend-id=userRoot,cn=Backends,cn=config: messages="The change to the ds-cfg-db-num-lock-tables attribute will not take effect until the backend is restarted The change to the je.env.isTransactional attribute will not take effect until the backend is restarted The change to the je.log.faultReadSize attribute will not take effect until the backend is restarted The change to the je.txn.timeout attribute will not take effect until the backend is restarted The change to the je.log.iteratorReadSize attribute will not take effect until the backend