Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic System Architect (steve huntington)
Decrease font size
Increase font size
Topic Title: Running reports in multi-user environment
Topic Summary: Recently, we've been getting db error dialog boxes when running a report and other users are editting
Created On: 17-May-2007 22:42
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 17-May-2007 22:42
User is offline View Users Profile Print this message


Matt Tricomi

Posts: 19
Joined: 20-Jan-2006

Since 2003, we've been running reports mostly at night, but many times during the day while others are editting. It wasn't til recently that while running reports that we began to encounter:
  message box: database error: 7100, codes: 4, 1206, 137
  message box: database error: 7101, codes: 4, 4407, 137 - [ happens 8 times]

then repeats for each row it doesn't like when writing the report temp NDX files.

(((On 6/2006, we moved to SA 10.3 and have been on since then (looking to go to SA 10.7 soon) - it wasn't til recently this started happening. We've always been on SQL Server 2k and on windows OS)

Thoughts? (We have a ticket in, but we're struggling together trying to figure it out)
Report this to a Moderator Report this to a Moderator
 17-May-2007 22:46
User is offline View Users Profile Print this message


Matt Tricomi

Posts: 19
Joined: 20-Jan-2006

Worth adding, the old documentation on reporting engine for SA 8.x is the following, but we don't know how that is related to SA 10.3 and up on SQL Server 2000. We supposedly have plenty of free space in our MDF and LDF :

Errors in the 7000 range occur during reporting. Reporting goes through two
passes:
. Extraction Pass; it reads the Entity and Relationship databases,
using their indexes as appropriate, and, in response to the "WHERE" clauses of
the report specification, selects records and writes them to the extract
database. At the same time, it creates one or two indexes to that extract
database.
. Printing Pass; it reads the extract database sequentially through its
main index and prepares the report. If the report is a matrix type, it used
the secondary index. If the report is not a matrix type, the secondary index
is not created. Some errors can occur only in the Selection Pass, some only in
the Printing Pass, some only if a matrix is being produced and some can occur
regardless of the particular reporting activity taking place.

In v8.x if the code number is 4, a disk full error has occurred. Please check
your LDF file to see if it is maxed out or not. If you have not done so already
please make a backup of this encyclopedia and run basic maintenance.

Could it be disk space?

Report this to a Moderator Report this to a Moderator
 18-May-2007 00:35
User is offline View Users Profile Print this message


Matt Tricomi

Posts: 19
Joined: 20-Jan-2006

looks likely to be disk space as our c drive was dangerously low (our data drive had plenty of room which was confusing). Reports write temporary NDX/etc. files to the C drive based on the SA v8 architecture, and it couldn't write its NDXs so, for each remaining row it was attempting to write, it created the 9 errors.

Report this to a Moderator Report this to a Moderator
 18-May-2007 11:15
User is offline View Users Profile Print this message


SA Team

Posts: 148
Joined: 18-Nov-2005

Did freeing some space up fix the problem?

Thanks
Ian

-------------------------

Senior Software Developer
Telelogic UK Ltd.
Report this to a Moderator Report this to a Moderator
 13-Jun-2007 01:20
User is offline View Users Profile Print this message


Matt Tricomi

Posts: 19
Joined: 20-Jan-2006

Hi Ian

Yeah, this was part of it. There were several other issues that this caused and we created a checklist of things to check now on crashes. Turns out anti virus and backup jobs were causing a dump at night eating up the Hard drive space.

Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic System Architect forum.
There are currently 0 users logged in.
The most users ever online was 16 on 30-Oct-2008 at 14:46.
There are currently 0 guests browsing this forum, which makes a total of 0 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.