Datamart extractor throws exception "The query processor ran out of stack space".

0 Likes

Problem:

Datamart extractor throws exception "The query processor ran out of stack space".

Resolution:

  • Product Name: StarTeam
  • Product Version:2005
  • Product Component: Datamart
  • Platform/OS Version: All

Description:

Datamart extractor is trying to purge Audit records. A SQL statement gets generated that looks like

Delete from ST_AUDITS Where ViewID = 249 AND ID IN (1491087, 1491122, 1491130, 1491131, 1491132, 1491182, 1491183, 1491184, 1491185, 1491187, 1491189, 1491190, 1491191, 1491192, 1491193, 1491194, 1491196, 1491197, 1491198, 1491200, 1491201, 1491202, 1491203, 1491204, 1491206, 1491207, 1491208, 1491209, 1491210, 1491211, 1491212, 1491213, 1491214, 1491215, 1491216, 1491218, 1491219, 1491220, 1491221

.................. This statement goes on until the datamart logs shows following exception

EXCEPTION: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Internal Query Processor Error: The query processor ran out of stack space during query optimization. at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source) at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source) at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source) at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source) at com.microsoft.jdbc.sqlserver.tds.TDSExecuteRequest.processReplyToken(Unknown Source) at com.microsoft.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source) at com.microsoft.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown Source) at com.microsoft.jdbc.base.BaseStatement.commonTransitionToState(Unknown Source) at com.microsoft.jdbc.base.BaseStatement.postImplExecute(Unknown Source) at com.microsoft.jdbc.base.BaseStatement.commonExecute(Unknown Source) at com.microsoft.jdbc.base.BaseStatement.executeUpdateInternal(Unknown Source) at com.microsoft.jdbc.base.BaseStatement.executeUpdate(Unknown Source) at com.starbase.extractor.Database.executeQuery(Database.java:206) at com.starbase.extractor.TableExtractor.deleteRecords(TableExtractor.java:456) at com.starbase.extractor.TableExtractor.populateTable(TableExtractor.java:209) at com.starbase.extractor.AuditExtractor.populateTable(AuditExtractor.java:120) at com.starbase.extractor.FolderExtractor.populateItems(FolderExtractor.java:223) at com.starbase.extractor.FolderExtractor.populateTable(FolderExtractor.java:129) at com.starbase.extractor.ViewExtractor.populateChildItems(ViewExtractor.java:284) at com.starbase.extractor.ViewExtractor.populateTable(ViewExtractor.java:211) at com.starbase.extractor.ProjectExtractor.populateChildItems(ProjectExtractor.java:228) at com.starbase.extractor.ProjectExtractor.populateTable(ProjectExtractor.java:188) at com.starbase.extractor.Extractor.doExtract(Extractor.java:330) at com.starbase.extractor.Extractor.extract(Extractor.java:283) at com.starbase.extractor.Extractor.run(Extractor.java:84)



Answer/Solution:

This issue is fixed in Datamart Patch 4 for StarTeam2005R2.




Author:Swati Joshi

Old KB# 28083
Comment List
Related
Recommended