Hi,
What's the big deal? Surely with those outdated versions and no sup****t
contract, this system can't be doing anything im****tant. Can it? What does
Nightspeed do? Do they have any customers or shareholders that read this
group :-(
Ok, sorry to be a pain and now I'll try to help. But it just drives me
nuts
how many other companies out there just like yours (and some of them are
VERY big and profitable) are too cheap to supply the resource levels
required. (And the number of Rdb bodies out on the street.) Insurance eh,
who needs it?
Anyway, you say nothing's changed so without much information to go on,
I'll
offer two guesses FWTW
1) You've started to get a lot of deadlocks (any other errors logged to
user
screens etc?) maybe a sorted index is looking a bit crappy after years of
neglect. If your error-handling code is rolling back the transaction so as
to recover from the deadlock then maybe the code is incorrectly proceeding
to the otherwise legitimate commit/rollback.
2) Some part of the database has grown and the number of rows has led to
an
internal array blowing up and if your transaction handles are in memory
after the array. Is the system written in Pascal, RDML, RDO? Do you
declare
your own transaction handles? Sadly, I have seen production systems where
people simply ignore this error :-( Often, they're using a specific
database
handle in one module but accepting the default rdb$dbhandle in the other.
Then they say "That module does what we want let's call that" and they end
up with two attaches to the database each with it's own transaction
context.
So a transaction could be started in one attach and you're trying to
commit
it in another. Are you using SQL Connections?
Any more information? How many times does RMU say each user is attached to
the database? Is it only one specific module/option?
Regards Richard Maher
"NightspeedIT" <derek.cowdrey@[EMAIL PROTECTED]
> wrote in message
news:1116430491.529600.205410@[EMAIL PROTECTED]
> HELP!!!
>
> I am the technical sup****t person for Nightspeed Services Ltd in
> Tipton, UK.
>
> We have been using RDB V6.1-14 under VMS 6.2 for several years with a
> major hitch but suddenly, two days ago we started to get large numbers
> of...
>
> %RDB-E-BAD_TRANS_HANDL, invalid transaction handle
>
> ... errors. There have been no changes made to the system as far as I
> am aware.
>
> I have very scant knowledge of RDB internals and Oracle don't seem to
> interested in helping me (I know we don't have a sup****t contract but I
> did offer to pay to speak to someone on the phone!)
>
> Is there anyone out there who might be able to help?
>
> Thanks
>
> Derek Cowdrey
>
|
