SPONSORS:






User Tag List

Thanks Thanks:  0
Likes Likes:  0
Dislikes Dislikes:  0
Results 1 to 9 of 9
  1. #1
    SQA Council
    Join Date
    Mar 2001
    Posts
    14,438
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Rational v2001, General Datastore Errors

    User darth vader (vaderbreath@hotmail.com) posted:

    Hi Becky,

    I have encountered this on 2 occasions and have 2 methods to repair;

    (1) I repaired via Access 2000. The ODBC and MDAC versions of Access 97 are
    not a good mix with the 2001 projects.

    (2) I sent my project to tech support, and they rebuilt the tds.mdbs via the
    xml files. I suggest sending them your project file and asking them to see
    if they can repair it.

    Another option is for you to create a new project, but initiliaze it from
    assets from an existing one. Unfortunately, not everything will be copied
    (example test logs)

    Hope this helps !!

    &&&&&&&&&&&&&&&&&&&&&&&&&&&
    "Give yourself to the darkside"

    &&&&&&&&&&&&&&&&&&&&&&&&&&&
    __________________________________________________ _______________________
    Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.


    ---

  2. #2
    SQA Council
    Join Date
    Mar 2001
    Posts
    14,438
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Rational v2001, General Datastore Errors

    User Alex (atarlecky@vertical.net) posted:

    We also experienced the same problem with "General DataStore #3" in 2001
    and fixed it by simply creating a different username and login for each
    tester or testing box.

    BTW - if you have scripts you want to salvage simply copy the .REC (GUI)
    or .S (VU) files into the same location of a new project; also copy the VP
    folder to get you VP's to follow. Then just open robot and create a "New"
    file with the same exact names of the files you copied over. They will
    open (with VP's) and and you should be able to save them.

    Good luck.

    Alex Tarlecky
    Sr. QA Automation Engineer
    VerticalNet, LLC
    507 Prudential Road
    Horsham, PA 19044
    atarlecky@vertical.net

    ---

  3. #3
    SQA Council
    Join Date
    Mar 2001
    Posts
    14,438
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Rational v2001, General Datastore Errors

    User Becky Ellis (rjellis@primary.net) posted:

    Thanks for your responses -- they confirm what we are experiencing but
    unfortunately we aren't much farther along. We do think part of the
    problem was somehow connected with signons; we had been running tests on
    more than one workstation using the same Rational signon, and when we
    stopped doing that the General Datastore problems dropped by about 70%.
    So that was part, but not all, of the problem.

    We suspect but cannot confirm -- and Rational is working on it but has not
    come up with anything solid -- that the problem is that v2001 uses Access
    2000 internally but we are using Access 97 for the repositories where we
    build our test data. Rational says this should not be a problem, but what
    is breaking is in essence the Rational indexes -- this is what is
    addressed by rebuilding "the tds.mdbs via the xml files". We have had
    that done, but although it gets you out of the immediate crisis, it does
    not prevent the problem from recurring.

    We are generating extremely large test logs, and have concluded that
    either the Rational product is not very robust in handling the large logs
    (maybe in its Rational components, maybe in the workings of its Access
    2000 indexes), or perhaps there is a dll conflict between Rational's
    Access 2000 and our own Access 97. We are considering upgrading everyone
    to Office 2000 to see if that helps.

    We're running a second project in Rational that has not experienced any of
    these General Datastore problems -- it is not yet at a point to generate
    very large test logs and it has only 2 -3 people running tests at a time,
    so the scope is much smaller.

    This is all very frustrating because we are a new test team (for this
    company) and so under much skeptical scrutiny. Some of us have come from
    companies that attempted automated testing but unsuccessfully; it looked
    like in this case we came at it in the correct way and had found a
    situation where it would be an essential and valuable part of the test
    program. The datastore errors have nearly killed us, and at one point we
    were ready to throw all the time and money invested in this out the window
    and go back to manual testing (given the time frame, a very very ugly
    alternative). Datastore errors are still occurring, and still causing
    occasional but large amounts of damage to the schedule. The fact that
    they have decreased (after we quit doing multiple signons) mean we can go
    forward with the automated testing, but it continues to be a significant
    and frustrating problem.

    Any suggestions welcome.

    ---

  4. #4
    SQA Council
    Join Date
    Mar 2001
    Posts
    14,438
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Rational v2001, General Datastore Errors

    User Schoen, Torsten 3865 PPE-QA1 (Torsten.Schoen@de.heidelberg.com) posted:

    Hi Becky,

    not sure if any of the following will be a feasible solution, but I suppose
    anything with the faintest hope to work will be welcome.

    First off, how many concurrent users do you have on your repository server?
    There are some ugly limits in Windows itself, that cause much grief to one
    of my collegues that administers our clearcase servers. All windowed
    processes on a server can not allocate more than 48 MB of memory, no matter
    what amount of memory the server has. In that situation the only solution
    was to break the project into smaller chunks and distribute them across
    several servers.

    And that is basically my idea, to break down the repository into smaller
    chunks so the number of users per repository/project will decrease. Off
    course you'll run into problems with report generation and all that, but
    given the problems you have now, that might be less trouble.

    Another way to go would be to introduce a custom made logging system for
    your scripts and use the TT logging only once per script to generate the
    appropiate pass/fail flag for reports. Depending how you set your testing
    environment up, this might involve to much work though.

    Hope you find a solution,

    Torsten Schoen
    PPE-QA1
    Heidelberger Druckmaschinen AG

    Memory limit in NT: http://support.microsoft.com/support.../Q126/9/62.ASP

    ---

  5. #5
    SQA Council
    Join Date
    Mar 2001
    Posts
    14,438
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Rational v2001, General Datastore Errors

    User MArk B. (mkbutler@russellmellon.com) posted:

    Along that line, I was wondering what happens when logging is turned off?


    "Schoen, Torsten 3865 PPE-QA1" <Torsten.Schoen@de.heidelberg.com> wrote in
    message news:13361@sqa-suite-users...
    suppose
    server?
    matter

    ---

  6. #6
    SQA Council
    Join Date
    Mar 2001
    Posts
    14,438
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Rational v2001, General Datastore Errors

    User Becky Ellis (rjellis@primary.net) posted:

    Torsten,
    Thanks, this is probably the closest we will get to a real solution. We
    are now using solutions very close to what you suggest (see below).

    Rational has been able to duplicate our problem in their lab but not
    consistently. But we (and I think Rational) at this point believe that a
    large part of the problem occurs when there are multiple users (multiple
    workstations) doing I/O to the repository logs at the same time. To
    clarify that, the logs themselves are apparently generated as XML, and
    then when the suite is done the XML is converted and put into the Access
    repository. This last piece -- pushing the converted XML into the Access
    repository -- is where the problem occurs. The Access repository is
    slower at I/O than the server sending the info, and so if there are
    multiple suites ending at the same time, or overlapping in I/O (since the
    conversion from XML takes a while on larger logs) then you have problems.
    If you can get around my lack of technically precise language here, you've
    got the main idea. So we think the problem is made worse by any
    combination of large test logs and multiple suites/signons/users ending
    and thus generating I/O to the logs at the same time. The difference in
    speed between the data coming from the server into the Rational/Access
    repository and the ability of Rational/Access to translate the data from
    XML and to do the I/O to get it into the Access tables is the technical
    intersection of the problem, or so we think.

    This morning we ran 5 test suites on 5 separate PCs (all into the same
    project repository) -- the longest one takes almost 5 hrs to run, and
    altogether we have something like 600+ data scenarios that are involved in
    this. We didn't allow any of the rest of the test team to use Rational at
    all while this was going on. No datastore errors.

    So, so far so good. He have also in the past gotten general datastore
    errors while accessing test plans, not just while writing out test logs,
    so I don't think the problem is really solved but at least it is more
    controllable. We will also be modifying the scripts so that we can opt to
    generate full test logs, or just failed verification points -- that should
    cut down the size of the logs also.

    Rational actually suggested that we use separate repositories on separate
    PCs and then join them all together for reporting. I won't repeat what my
    manager said about that..... But Rational did agree to send a programmer
    here to help resolve the issue; the soonest they can do this is June 11.
    (I won't repeat what my manager said about that date either. Especially
    after the sizeable investment we've made in the tool and the licenses.)
    Rational also suggested running all the test suites on a single PC, single
    threaded (at this point over 10 hrs would be involved, which is not
    reasonable for the weekly regression tests given the number of other tasks
    that are on hold until these tests are done).

    So, we're not happy yet but not at a standstill. An automated tool should
    be robust enough to handle high volume like this -- if we didn't have so
    many tests that needed to be rerun quickly and reliably and so many times,
    we wouldn't really need an automated tool.... It doesn't help that the
    technical support from Rational has been less than sterling. (We don't
    know, uh, try this, no try that, well then try that.) I do think Rational
    is a great product, and it's a compliment to Rational that we can get a
    test process like this up and running gangbusters. They were really great
    about initial support -- helping us design the test suites etc. But part
    of the problem is that we are sort of an unwitting beta site for v2001, at
    least for such a large-scale test effort. The reluctant bleeding edge.
    The manual workarounds that other folks seem to be using -- rebuilding the
    project (which loses the test logs), breaking up the repository into
    separate pieces and then figuring out how to do the reporting -- are not
    an option when you have a dozen testers sitting on their hands every time
    you have to do this. What you end up with is nothing but a lot of very
    flat hands....

    The problems here will probably not affect sites with smaller volume.


    ---

  7. #7
    SQA Council
    Join Date
    Mar 2001
    Posts
    14,438
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Rational v2001, General Datastore Errors

    User Schoen, Torsten 3865 PPE-QA1 (Torsten.Schoen@de.heidelberg.com) posted:

    Hi Becky,

    after a long weekend and reading your mail my mind brought up another idea.
    As it seems your problem is basically a syncronisation problem occuring with
    simultaneous accesses to the Access DB *that sounds weird:-)*

    Anyhow, I would suggest that you create some text file on the repository
    server that will be monitored by all scripts prior to their termination. The
    file will only contain a single line with a time value that represents a
    delay.

    Each script/suite would have an indivual delay that you would set based on
    your experience and the amount of log data generated by that specific
    script. When the script/suite finishes it will write this delay to that file
    and exit.

    And here is the sketch-up of the process to avoid collisions:

    As last step in each suite you call a synchronize function that does the
    following:
    While (true)
    read the content of Delay.txt
    read the time stamp of Delay.txt
    if current time > time stamp + delay then
    write delay to file 'time stamp will be updated automatically
    exit
    else
    wait a minute 'Make that large enough to reduce chances that 2
    scripts collide here
    end if
    end while

    A potential problem is that script2's synchronize() reads the delay.txt
    after script1 read the file, but before script1 could write a new delay.txt.
    To avoid that risk you would have to take extra measures, like the
    following:

    Open Delay.txt for Write/Append 'Need error handling here -> File locking
    Append Scriptname
    Close Delay.txt
    While true
    read firstline/secondline of Delay.txt
    read timestamp
    if (secondline == scriptname) AND (timestamp + firstline > actual
    time) then
    ReOpen for Read/Write
    read lines 3 to n to buffer
    Write Delay
    Append lines 3 to n
    Exit
    Else
    Wait for a minute
    End if
    End while


    the second version will be more stable, but requires more effort. If the
    database can handle 2 concurrent logging activities I would stick with
    version 1, as it is very unlikely that serveral scripts will access
    Delay.txt at the same time.

    Hope this helps (before June 11th :-)),


    Torsten Schoen
    PPE-QA1
    Heidelberger Druckmaschinen AG
    ---

  8. #8
    Junior Member
    Join Date
    Mar 2003
    Posts
    1
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Rational v2001, General Datastore Errors

    Hello, all!
    I've recieved General Database Error today in Rational TestManager 2003.06. The last thing wich I've done was creating new suite (Likely it has successfully created). After this I've closed Testmanager and tryed to start it again. But it cannot start when I select that project which was opened earlier (say, "AAA"). If I select another (say, "BBB") project then Testmanager starts and it's ok. So some problems occured with "AAA" project. I've tryed to manualy remove in TMS_Suites directory last created suite but it isnot affected on running Testmanager.

    I'm using it under Access

    What can I do to force Testmanager to run project "AAA"?

    Is it possible to use instead MS SQL?



    Thanks.

    Regards.


    Polina Labinskaya
    Texuna Tech., Moscow
    +7-095-2588570

  9. #9
    Senior Member
    Join Date
    Jul 2002
    Location
    Palm Bay, FL USA
    Posts
    2,346
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Total Downloaded
    0

    Re: Rational v2001, General Datastore Errors

    I hate to do this to you, but call Tech Support. It is unlikely that the answer is simple and more unlikely that we'll manage to ask all the right questions in the right order to help you out correctly.

    Sorry.
    Scott Barber
    Chief Technologist, PerfTestPlus
    Executive Director, Association for Software Testing
    Co-Author, Performance Testing Guidance for Web Applications
    sbarber@perftestplus.com

    If you can see it in your mind...
    you will find it in your life.

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Search Engine Optimisation provided by DragonByte SEO v2.0.40 (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 11.54%
vBulletin Optimisation provided by vB Optimise v2.7.1 (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.3.0 (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2017 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 09:17 PM.

Copyright BetaSoft Inc.