Re: OT: IDS 10 QPlan sanity failure problems
Davorin Kremenjas wrote:
> Just like Neil, we're preparing to migrate our v9.40 servers to v10.
> I already converted one test instance to v10UC3R1, using same dbspaces, the
> same onconfig, sqlhosts etc.
> Upgrade went fine, at least the log said so, but now we're constantly
> facing -640 QPlan sanity failure <line-number> exceptions.
> UPDATE STATISTICS doesn't help.> Any ideas?
> Thanks everyone.
>
> "Neil Truby" <neil.truby@ardenta.com> wrote in message
> news:3p6df9F8or2fU1@individual.net...
>
>>IDS 10.0FC3 on Solaris 2.9
>>
>>This is a brand new server which we are preparing to migrate a v9 system
>>to.
>>Over the past few weeks I have run multiple dbimports from more-or-less
>>the
>>same data source - certainly the same schema - but the import time varies
>>widely.
>
>
>
I think you would need to post a more "complete" description of the error.
If the database is relatively small, you could try :
"update statistics low drop distributions"
if the error is specific to a database.
There was something related to the sysmaster requiring update statistics
drop distributions after an upgrade - not in my head at the mo.
> I think you would need to post a more "complete" description of the error. OK, here is more complete description: this error ocurres only when invoking certain inserts/updates/... (which trigger corresponding triggers, which trigger some SPLs, ...) from Java application through JDBC driver so it seems like a driver error, possibly with PreparedStatement. > If the database is relatively small, you could try : > "update statistics low drop distributions" I'll try that and report the results. > There was something related to the sysmaster requiring update statistics > drop distributions after an upgrade - not in my head at the mo. Well, if you remember something, please contact me, since this is preventing me to upgrade my production environment to v10 (I upgraded my test instance, that's the one that's giving me a headache).
...if not a solution, I don't know yet.
This is what I did this time, following TBP's advice:
update statistics low drop distributions;
update statistics;
update statistics for procedure;
I'm not sure which one of them helped, but nevertheless :-)
The problematic insert I know of went fine this time.
I'll check with my colleagues about their problematic use cases and report
if this is a full solution or maybe just a partial one.
"Davorin Kremenjas" <davorin.kremenjas@srce.hr> wrote in message
news:dgrfvo$mfu$1@bagan.srce.hr...
>> I think you would need to post a more "complete" description of the
>> error.
>
> OK, here is more complete description: this error ocurres only when
> invoking certain inserts/updates/... (which trigger corresponding
> triggers, which trigger some SPLs, ...) from Java application through JDBC
> driver so it seems like a driver error, possibly with PreparedStatement.
>
>> If the database is relatively small, you could try :
>> "update statistics low drop distributions"
>
> I'll try that and report the results.
>
>> There was something related to the sysmaster requiring update statistics
>> drop distributions after an upgrade - not in my head at the mo.
>
> Well, if you remember something, please contact me, since this is
> preventing me to upgrade my production environment to v10 (I upgraded my
> test instance, that's the one that's giving me a headache).
>
update statistics drop distributions will not fix the stored procedurequery plans so have little if any impact on your problem
the reason I asked about replication was becasue of the sysmaster issue
as it appears to only be related to ER
If dropping the procedures and recreating them didn't resolve the
problem its time to contact your support provider