Is this with EMC SAN storage, LVM in use?
And at IQ side, do you have the Max_temp_Space_per_Connection setting ?
Or how big of the temp db space sizing?
On 2/9/2012 8:08 AM, Larry Gale wrote:
>> Hello,
>> I am curious too, you wrote "perfectly legal query",
>> does it mean it is one and the same ? If yes can you
>> reproduce it in another environment ? Regrds,
>> Peter
>>
> We have a development environment with the exact software
> and hardware configuration, but with only a small (10%)
> subset of our database from the production server.
>
> The queries in question sometimes fail on the development
> server, but others run successfully on the development
> system. For those, we suspect the size of the dataset may
> have an impact.
>
> But our main concern is: even "bad" queries shouldn't cause
> a production commercial database product to crash! At
> worst, it should say "can't parse that query", or "result
> set too large", or some similar warning, and then allow
> other users to continue processing.
>
> It's the apparent inability of Sybase Technical Support,
> after two months, to still be unable to provide us a
> solution to this problem. I'm hoping that by posting on
> this forum, somebody with similar experiences may be able to
> elucidate.
>
>>
>> On 2/8/2012 10:06 PM, IQRules wrote:
>>> Just curious, you have weekly checkDB here and Hardware
>>> side is confirmed no issue ??
>>>
>>>
>>> On 2/8/2012 2:54 PM, Larry Gale wrote:
>>>> Yes, we've uploaded those to Sybase with our trouble
>> tickets>> (actually, our systems integrator, Telus
>> Healthcare, has>> been handling the tickets with Sybase).
>> Multiple core>> files, stack traces, message files, log
>> files, etc., but>> still no answer on what the problem is
>> and why we continue>> to experience crashes.
>>>>
>>>> But we still haven't been able to get any definitive
>> answer>> on why a legal query crashes the server, rather
>> than saying>> "sorry, can't parse that", or some similar
>> message. We>> upgraded to 15.3 in December 2011, and
>> we've had multiple>> crashes since then. We'd had similar
>> problems on 15.1,>> before we upgraded to 15.3, and were
>> hoping the upgrade>> would solve the problem, but it
>> clearly has not.>>
>>>> As a comparison, our main clinical data repository runs
>> on>> Sybase ASE. As far as I know, they've NEVER had the
>> ASE>> server crash on them, so we're really curious why
>> IQ seems>> so fragile.
>>>>
>>>> The lack of stability is frustrating to us and to our
>> user>> community. IQ is an amazing product for reporting;
>> I've>> never seen anything like this kind of speed, but
>> it just>> crashes so often that our management may lose
>> confidence in>> the product and look at other options.
>>>>
>>>>
>>>>> Is there any error messages in msg or serverlog files
>> ?>>> any stack traces ?
>>>>>
>>>>> Manish Negandhi
>>>>> [TeamSybase]
>>>>>
>>>>> <Larry Gale> wrote in message
>>>>>> news:4f317c27.6444.1681692777@sybase.com... We are
>>>>>> running Sybase IQ 15.3 on Solaris 10. We have been
>>>>>> having problems for months with the IQ server core
>>>>> dumping when running a perfectly legal query.>
>>>>>> We upgraded from 15.1 to 15.3, since that's what
>> Sybase>>>> suggested when we had this problem under IQ
>> 15.1, but it>>>> still hasn't eliminated the problem.
>>>>>>
>>>>>> Has anybody else experienced issues with IQ core
>>>>>> dumping? This has been going on for months, and
>> Sybase>>>> tech support hasn't found a solution.
>>>>>>
>>>>>> Larry Gale
>>>>>> galel@musc.edu
>>>>>
>>>>>
>>>
>>
|