RE: Unexpected XactState

Question

Hi,
We here have encountered the second message quite a lot in our environment.
It means that a cursor is somehow corrupted, that is, the content of the
cursor got overwritten. As explained by Forte consultant, this can happen
when an implicit cursor is being opened but the same DBSession was being
called for some other things. We are thus advised to use begin and end
transaction over all "FOR" loop on SQL statement, that is
BEGIN TRANSACTION
FOR ABC IN SQL SELECT ¡­
END TRANSACTION
Regards,
Peter Sham.
-----Original Message-----
From: KALLAMBELLA Ajith [SMTP:[email protected]]
Sent: Wednesday, July 22, 1998 3:11 AM
To: 'Forte'
Subject: Unexpected XactState
Hi all,
Does anyone out there know what this error means?
K12Windows_cl0:
[E92556D0-862B-11D1-811E-187EDF6BAA77:0x272c:0x3.033]
DBSession: :CloseCursor: Unexpected XactState in CloseCursor,
statementName = 0x3b95:K12DBServices.ReportStatusMgr.GetAllReports
Thanks in advance,
Ajith Kallambella M.
Forte Systems Engineer,
Internationational Business Corporation.
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive
<URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Answer 1

If your replacement battery is one of the cheapies sold for half or less than half what Apple charges, return it for a refund. Many such batteries are garbage.
Apple Hardware Test does not test the battery or any other part of the power system. Disk Utility and SMARTreporter don't either, and what they do test has no bearing on the problem.
The behavior you're seeing is typical of old batteries on their last legs. That was probably true of your first battery, and it may be true of your new one.