cancel

Database errors

Highlighted
isd15
Trusted Contributor.

Database errors

Running TRIM 6.25, build 2.5.1406 on Windows Server 2008

User's have also been reporting that when they do a simple word search it will occasionally display the error Database not responding and will hang up to 10 -15 seconds before completing the query (we currently have just over 42 million electronic records)

Checking the logs display the following error SQL TIMEOUT errors. "The SQL query failed. Errors were Query timeout" with "TRIM Connectivity Toolkit unique id = 1100061)"

C:\TRIM Context\ServerLocalData\TRIM\Log Example below from Trim logs

00:01:40 0 Error : B4 User: PARWNTC01 - The SQL query failed. Errors were Query timeout expired SQL was SELECT uri FROM TSRECORD WITH (NOLOCK) WHERE (URI IN (SELECT A0.uri FROM TSRECORD A0 WITH (NOLOCK) WHERE ((rcRecTypeUri IN (1,2,3,7,27,47,67,170,171,211,251,531,532,534,535) ) AND NOT EXISTS (SELECT * FROM TSEXFIELDV WHERE evObjectUri = A0.uri AND evFieldUri = 2 AND evFieldBobType = 6 AND evFieldValKey <> ' ')))) AND ( TSRECORD.rcSecLevel <= 10 AND TSRECORD.rc1CaveatKey = 1 AND TSRECORD.rc2CaveatKey = 1 AND TSRECORD.rc3CaveatKey = 1 AND TSRECORD.rc4CaveatKey = 1 AND TSRECORD.rc5CaveatKey = 1 ) AND ( (TSRECORD.rcAccessLoc = 0 OR EXISTS ( SELECT axLocUri FROM TSaccessCo WITH (NOLOCK) WHERE TSRECORD.uri = axObjectUri AND axObject = 6 AND axType = 2 AND (axLocUri IN (0,187327,177877,177908,177910,178919,178920,178921,178922,178923,178924,178925,178926,178927,178928,178929,178930,178931,178932,178933,178934,178935,178936,178937,178938,178939,178940,178941,178942,178943) OR axLocUri IN (178944,178945,178946,178947,178948,178949,178950,178951,178952,178953,178954,182771,187327,188669) ))) AND ( TSRECORD.rcAccessLoc > 0 OR TSRECORD.rcAccessIsCont = 'F' OR TSRECORD.rcContainerUri = 0 OR EXISTS (SELECT ContTest.uri FROM TSrecord ContTest WITH (NOLOCK) WHERE ContTest.uri = TSRECORD.rcContainerUri AND ( ContTest.rcSecLevel <= 10 AND ContTest.rc1CaveatKey = 1 AND ContTest.rc2CaveatKey = 1 AND ContTest.rc3CaveatKey = 1 AND ContTest.rc4CaveatKey = 1 AND ContTest.rc5CaveatKey = 1 ) AND ( (ContTest.rcAccessLoc = 0 OR EXISTS ( SELECT axLocUri FROM TSaccessCo WITH (NOLOCK) WHERE ContTest.uri = axObjectUri AND axObject = 6 AND axType = 2 AND (axLocUri IN (0,187327,177877,177908,177910,178919,178920,178921,178922,178923,178924,178925,178926,178927,178928,178929,178930,178931,178932,178933,178934,178935,178936,178937,178938,178939,178940,178941,178942,178943) OR axLocUri IN (178944,178945,178946,178947,178948,178949,178950,178951,178952,178953,178954,182771,187327,188669) ))) ) )) )

00:15:42 0 Error : B4 User: PARWNTC01 - The SQL query failed. Errors were Query timeout expired SQL was SELECT uri,regDateTime,fullRecordId FROM TSRECORD WITH (NOLOCK) WHERE (URI IN (SELECT A0.uri FROM TSRECORD A0 WITH (NOLOCK) WHERE ((rcRecTypeUri IN (1,2,3,7,27,47,67,251,532,534) ) AND NOT EXISTS (SELECT * FROM TSEXFIELDV WHERE evObjectUri = A0.uri AND evFieldUri = 5 AND evFieldBobType = 6 AND evFieldValKey <> '+000000000000')))) AND ( TSRECORD.rcSecLevel <= 10 AND TSRECORD.rc1CaveatKey = 1 AND TSRECORD.rc2CaveatKey = 1 AND TSRECORD.rc3CaveatKey = 1 AND TSRECORD.rc4CaveatKey = 1 AND TSRECORD.rc5CaveatKey = 1 ) ORDER BY regDateTime DESC , fullRecordId DESC

 

Our Application server is showing errors in the App events "TRIM Connectivity Toolkit unique id = 1100061)"

We have been advised that we should get our DBA's to run statistics and rebuild the indexes on the database, would this be a good place to start ?

Any advice or ideas would be greatly appreciated on where we should start in resolving these issues.

1 REPLY
Greg Fraser_1
HPE Expert

Re: Database errors

Looks like a fairly large search to me.

 

have you tried increasing the timeout in the TES and re-running the search. By default it is set to -1 you could set it to 300 and see if it goes through.

**Any opinions expressed in this forum are my own personal opinion and should not be interpreted as an official statement on behalf of Hewlett Packard Enterprise**