Unsubscribe

Sent from my iPhone 6  > On 26 Mar 2018, at 19:28, Tauf Chowdhury wrote: > > Totally doing this from memory but I’m pretty sure the reason is that the > query is looking at the product catalog form and timing out. You can try to > be more specific in your query or do

Duplicate config component listings

Greetings, Listers! I was attempting to add a new configuration to the AREA LDAP section. When I submitted it, I got an error message stating that there were multiple matches for a filter condition and it threw an error. Turning on logging, I found out that there was a filter for the "AR

Re: SRM Fulfillment creation issue

Dinesh, I've never been too much on the application side of thingsa quick filter log should show you what workflow is pushing to that form which might give you a better idea of 'why' :) On Mon, Mar 26, 2018 at 1:56 PM, Dinesh Kumar wrote: > We are in ARS 8.1 SP1 and SRM

Re: SRM Fulfillment creation issue

We are in ARS 8.1 SP1 and SRM 8.1. Why we are updating the SRM:ProcessDefinitionTemplate_Base form for every service request creation ? Thanks, Dinesh kumar. On Mon, Mar 26, 2018 at 9:48 PM, LJ LongWing wrote: > You might try looking for an arexception.log fileif

Re: SRM Fulfillment creation issue

You might try looking for an arexception.log fileif you are of a sufficient version and have it enabled, you might find information on how some of the calls are being generated and maybe even who. On Mon, Mar 26, 2018 at 1:45 PM, Dinesh Kumar wrote: > Hi LJ, > > We are

Re: SRM Fulfillment creation issue

Hi LJ, We are not able to find that update statement in the logs, its getting captured in the AR Error logs only. Not sure from where its getting triggered . Thanks, Dinesh kumar. On Mon, Mar 26, 2018 at 9:25 PM, LJ LongWing wrote: > Dinesh, > Remedy does a 'BEGIN' at

Re: SRM Fulfillment creation issue

Dinesh, Remedy does a 'BEGIN' at the beginning of an API call and does a 'COMMIT' at the end of an API callyou'll need to run some API/SQL logs on your server to help identify what processes are causing the blocking to occur at the DB level... Now, that could easily describe why #1 is

Re: SRM Fulfillment creation issue

Hi LJ, DB team is saying this is boz of "TX - row lock contention". "enq: TX - row lock contention" waits are generally related to the application code being executed and do not indicate a problem with the DB itself. The reason to this could be as the commit is still not issued , thus the lock

Re: SRM Fulfillment creation issue

Totally doing this from memory but I’m pretty sure the reason is that the query is looking at the product catalog form and timing out. You can try to be more specific in your query or do some tuning on those tables. Sent from my iPhone > On Mar 26, 2018, at 2:03 PM, LJ LongWing

Re: SRM Fulfillment creation issue

Well, for #1, you are issuing a query to the db that's not returning in the 120 second timeoutfor #2 you are getting disconnected from the DBboth scenarios are pointing to a DB that is either overwhelmed, or under performing...I would highly recommend working with your DBA to figure out

SRM Fulfillment creation issue

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,