none
Oracle EBS adapter polling error RRS feed

  • Question


  • Hi All,
     
    i am trying to poll the data from oracle database (R12) using biztalk 2009 and LOB adapter pack 2.0, this is the error message

    The adapter "WCF-Custom" raised an error message. Details "Microsoft.ServiceModel.Channels.Common.TargetSystemException: ORA-02049: timeout: distributed transaction waiting for lock -


    any help ???


    praveen
    Friday, June 5, 2009 5:50 PM

Answers

  • We are also using the BizTalk Adapter Pack 2 in our environment and encountered this issue. This typically occurs when 2 processes are attempting to access the same resource (db page, extent etc). To resolve it, you can try the following:

    1. Reduce the amount of updates/inserts against the data you are trying to access through your polling action/statement.
    2. Reduce the number of connections attempting to access the same resource by reducing the max pool size.
    2. Add an extension to the receive location to change the isolation level from seriazible to read committed. This will reduce the chances of contention which create the timeout.

    Hope you get it right...
    Wednesday, June 10, 2009 6:42 PM

All replies



  •  Use Oracle administration tools to check which process that acutally has a lock on the data which your polling.

     - SHR
    Friday, June 5, 2009 6:17 PM
  • Are you locking rows as part of the polling statement? Then the 'SKIP LOCKED' statement could prove very useful to you to avoid such conditions. It is decribed in the documentation on this page: http://msdn.microsoft.com/en-us/library/dd788472.aspx

    Hope this helps.

    Thanks,
    Manas
    Sunday, June 7, 2009 7:51 PM
  • We are also using the BizTalk Adapter Pack 2 in our environment and encountered this issue. This typically occurs when 2 processes are attempting to access the same resource (db page, extent etc). To resolve it, you can try the following:

    1. Reduce the amount of updates/inserts against the data you are trying to access through your polling action/statement.
    2. Reduce the number of connections attempting to access the same resource by reducing the max pool size.
    2. Add an extension to the receive location to change the isolation level from seriazible to read committed. This will reduce the chances of contention which create the timeout.

    Hope you get it right...
    Wednesday, June 10, 2009 6:42 PM