Yes, that's the SQL server side log.  Any application servers that are
going to be processing them should have it turned on to have a
comprehensive look.  You should also include API logging to help identify
what api calls are causing the sql to fire, and if possible, it would be
best to turn on Filter as well to identify what filters are causing the sql
to fire.....anything that the Remedy server sends to the db should be
logged in these logs.  The turning on of the query hint would prevent an
update to a form from stopping queries to the form from processing.

On Tue, Mar 27, 2018 at 10:20 AM, Dinesh Kumar <guru...@gmail.com> wrote:

> Hi Thad,
>
> We are using Oracle Database and the table row is getting locked by update
> query. Its not getting released after that.
>
> DB team is saying there is no commit from application.
>
> Is there any way we can find what are all the SQL's issued by ARS to DB.
>
> Thanks,
> Dinesh kumar.
>
>
> On Tue, Mar 27, 2018 at 4:28 PM, Thad Esser <thad.es...@gmail.com> wrote:
>
>> Dinesh,
>>
>> Look into the Select-Query-Hint setting, which might help.  Our issue
>> manifested as ridiculously slow reports, which our DBAs said were because
>> of row locking.  This setting fixed that issue for us.  I don't recall for
>> sure, but there may have a been database setting to go along with that.  We
>> are on ARS/SRM/ITSM 8.1, with a SQL Server database.
>>
>> -Thad
>>
>> BMC Docs:
>> ==============================
>> https://docs.bmc.com/docs/display/public/ars81/ar.cfg+or+ar.
>> conf+options+S-Z
>> Select-Query-Hint
>>
>> Text to use in a query hint in the WITH clause of a SELECT statement when
>> queries are supplied to Microsoft SQL Server databases. This option works
>> only for queries triggered by GLE,GLEWF, and GME API calls. If this option
>> is an empty string or is not present, no WITH clause is generated. To
>> determine the appropriateness of using this feature in your environment,
>> consult your SQL Server documentation. This option is commonly used with a
>> NOLOCK setting for allowing queries to execute without being blocked by
>> simultaneous updates, thereby improving performance. For example, to allow
>> SQL Server to read data being updated and avoid blocking, use this syntax:
>>
>> Select-Query-Hint: NOLOCK
>> ==============================
>>
>> On Mon, Mar 26, 2018 at 10:52 AM, Dinesh Kumar <guru...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> We are facing below issue in our environment which causes a higher
>>> impact and Business critical.
>>>
>>>
>>>
>>> SRM Fulfillment requests are not getting generated.
>>>
>>>
>>>
>>> The requests are getting struck in the *CAI Events* form in the Running
>>> status for all the events (SRM_OUT_RESTART_SR_SUBMIT, TMS_OUT_GET_DATA).
>>>
>>> We could see that PDT’s are also not getting connected to the Service
>>> Requests. (adding screenshot).
>>>
>>>
>>>
>>>
>>>
>>> We are getting time out errors in the plugin and ARERR logs for the
>>> certain requests.
>>>
>>>
>>>
>>> *Error-1:*
>>>
>>>
>>>
>>> 2018-02-14 09:12:55,772 ERROR [pool-2-thread-4]
>>> com.bmc.itsm.cai.filterapi.cai.worker.BaseEventWorker
>>> (BaseEventWorker.java:166) - CAI plugin failed to update error code of
>>> event:TMHAA5V0GJ3KKAPEER8HBGHK64BVRP. Failed with following exception.
>>> ERROR (94): Timeout during database query -- consider using more specific
>>> search criteria to narrow the results, and retry the operation;
>>> ATVIEUUSMS006:2000 ONC/RPC call timed out
>>>
>>>
>>>
>>> *Error-2:*
>>>
>>>
>>>
>>> Wed Feb 14 09:24:49 2018 390627 : The SQL database operation failed.
>>> (ARERR 552)
>>>
>>> Wed Feb 14 09:24:49 2018 ORA-03135: connection lost contact
>>>
>>> Process ID: 315236
>>>
>>> Session ID: 411 Serial number: 60447
>>>
>>> Wed Feb 14 09:24:49 2018 lastsql UPDATE T2457 SET
>>> C112=';1000000018;',C5='Remedy Application Service',C6=1518531886 WHERE C1
>>> = 'PDT000000005704'
>>>
>>> Wed Feb 14 09:24:53 2018 390627 : SQL database is now available (ARNOTE
>>> 592)
>>>
>>> SRM:ProcessDefinitionTemplate_Base(T2457) is getting locked and we are
>>> not able to create any request fulfillment after that.  Then we need to
>>> manually release.
>>>
>>>
>>>
>>> Has one faced this kind of issues.
>>>
>>>
>>> Thanks,
>>>
>>> Dinesh kumar.
>>>
>>> --
>>> ARSList mailing list
>>> ARSList@arslist.org
>>> https://mailman.rrr.se/cgi/listinfo/arslist
>>>
>>>
>>
>> --
>> ARSList mailing list
>> ARSList@arslist.org
>> https://mailman.rrr.se/cgi/listinfo/arslist
>>
>>
>
> --
> ARSList mailing list
> ARSList@arslist.org
> https://mailman.rrr.se/cgi/listinfo/arslist
>
>
-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

Reply via email to