Hi all,
I think it’s not DB-Query problem.
After analyzing the mysl log file it appear that the query is not
constructed and sent to the database.
Checks in 3 steps in QueryBuilder :
1- Add the desired queue → It work fine, query is constructed and
sent to the DB
QueryBuilder displays :
Queue = ‘adi.applications’
2- Add a first desired CF value → It work fine, query is constructed
and sent to the DB
QueryBuilder displays :
Queue = ‘my_queue_name’
AND ‘CF.{Impact Continuité}’ LIKE ‘Oui’
3- Add a second desired CF value → QueryBuilder froze, nothing is not
sent to the DB (request is not logged)
Horst
Horst,
Depending on how much SQL you want to see, you can see most of the
select and display SQL when you click “Advanced” at the top.
Kenn
Hi Kenn,
thanks for your answer.
How can I see the QueryBuilder’s executed query ?
Regards,
Horst
Hi Horst,
Is the query hitting the DB the same with the CLI versus
QueryBuilder? Maybe you are hitting a resource limit when
the request goes through the web server. Try checking the
system and web server logs to see if there is any more
information. If it is not generating the same query, then
that will give you a place to look for a problem. Good
luck. At least, there is a good consulting group available
should you need some expert assistance.
Regards,
Ken
I’ve tried in CLI mode and have no problem.
The execution of request is quick.
Horst
Le Lundi, 5. Juillet 2010 ?? 08:58, “Horst Kriegers”
Horst.Kriegers@loro.ch a ??crit :
Hi and tanks Kenn for your answer.
RT_Config : Identical (not modified)
RT_SiteConfig - Differences are minimal :
- $rtname
- $DatabasePort
- $DatabaseUser
- $DatabaseName
- $ParseNewMessageForTicketCcs
- $LogToFileNamed
- $WebPort
And log files contains nothings special
This behavior seem to appear by inserting Custom Fields in the
query.
Any idea where can I investigate to resolve this problem ?
Horst
Le Mercredi, 30. Juin 2010 ?? 16:53, Kenneth Crocker
kfcrocker@lbl.gov a ??crit :
Horst,
What are the differences in you RT_Config and RT_SiteConfig.pm
files?
Kenn
LBNL
Hi,
Suze Linux 2.6.16
RT 3.6.6
Apache 2.2.6
MySQL 5.1.45
We have 2 instances of RT:
- DEV for development
- PRD for production
A query created in RT’s Query Builder on the DEV environment works
fine.
By creating the same query on the PRD environment froze until
timeout
appear.
I’ve tried to connect the RT DEV to MySQL PRD, all works fine.
I’ve tried to connect the RT PRD to MySQL DEV, it froze.
I’ve tried to compare the both RT’s directory content, all seems to
be
identical.
How can I solve this probl??m ?
Many thanks in advance.
Horst
Le contenu de ce courriel est uniquement r??serv?? ?? la personne ou
l’organisme ?? qui il est destin??. Si vous n’??tes pas le
destinataire
pr??vu, veuillez nous en informer au plus vite et d??truire le
pr??sent
courriel. Dans ce cas, il ne vous est pas permis de copier ce
courriel,
de le distribuer ou de l’utiliser de quelque mani??re que ce soit.
The content of this e-mail is intended only and solely for the use
of
the named recipient or organisation. If you are not the named
recipient,
please inform us immediately and delete the present e-mail. In this
case, you are nor allowed to copy, distribute or use this e-mail in
any
way.
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
Le contenu de ce courriel est uniquement r??serv?? ?? la personne ou
l’organisme ?? qui il est destin??. Si vous n’??tes pas le
destinataire
pr??vu, veuillez nous en informer au plus vite et d??truire le
pr??sent
courriel. Dans ce cas, il ne vous est pas permis de copier ce
courriel,
de le distribuer ou de l’utiliser de quelque mani??re que ce soit.
The content of this e-mail is intended only and solely for the use
of
the named recipient or organisation. If you are not the named
recipient,
please inform us immediately and delete the present e-mail. In this
case, you are nor allowed to copy, distribute or use this e-mail in
any
way.
Le contenu de ce courriel est uniquement r??serv?? ?? la personne ou
l’organisme ?? qui il est destin??. Si vous n’??tes pas le
destinataire
pr??vu, veuillez nous en informer au plus vite et d??truire le
pr??sent
courriel. Dans ce cas, il ne vous est pas permis de copier ce
courriel,
de le distribuer ou de l’utiliser de quelque mani??re que ce soit.
The content of this e-mail is intended only and solely for the use
of the named recipient or organisation. If you are not the named
recipient, please inform us immediately and delete the present
e-mail.
In this case, you are nor allowed to copy, distribute or use this
e-mail in any way.
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
Le contenu de ce courriel est uniquement réservé à la personne ou
l’organisme à qui il est destiné. Si vous n’êtes pas le destinataire
prévu, veuillez nous en informer au plus vite et détruire le présent
courriel. Dans ce cas, il ne vous est pas permis de copier ce courriel,
de le distribuer ou de l’utiliser de quelque manière que ce soit.
The content of this e-mail is intended only and solely for the use of
the named recipient or organisation. If you are not the named recipient,
please inform us immediately and delete the present e-mail. In this
case, you are nor allowed to copy, distribute or use this e-mail in any
way.
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
Le contenu de ce courriel est uniquement réservé à la personne ou
l’organisme à qui il est destiné. Si vous n’êtes pas le destinataire
prévu, veuillez nous en informer au plus vite et détruire le présent
courriel. Dans ce cas, il ne vous est pas permis de copier ce courriel,
de le distribuer ou de l’utiliser de quelque manière que ce soit.
The content of this e-mail is intended only and solely for the use
of the named recipient or organisation. If you are not the named
recipient, please inform us immediately and delete the present e-mail.
In this case, you are nor allowed to copy, distribute or use this
e-mail in any way.