Oracle CRM On Demand: (503) Server Unavailable Error

Issue

In Riva Cloud or Riva On-Premise, "(503) Server Unavailable" errors may sporadically appear throughout crmex-log files.

Cause

Oracle CRM On Demand imposes a set of "web services on demand limiters" that can limit

• the total number of concurrent requests for data,
• the maximum values for records, and
• the volume of data requested.

If the total volume of data being requested or synced during a Riva sync cycle exceeds the permitted threshold value, Oracle On Demand web services report that the server is unavailable.

Solution

• If this issue if a low occurrence error, it can be safely ignored.
• If the issue becomes pronounced, adjustments need to be made to reduce the number of requests and volume of data syncing.

Solution for Riva Cloud

• Contact the Riva Success Team.

Solution for Riva On-Premise

Reducing the number of requests and/or volume of data syncing can be accomplished in several ways, including:

• Reducing the number of concurrent execution threads that Riva is using. This will reduce the number of requests and volume of data. For more information, see Controlling concurrent Riva synchronization threads.
• If users are syncing large attachments, you could
  • go as far as disabling attachments on a per-module basis, or
  • (less radically) implement attachment size limits: for more information, see the "configure attachment options" section of
    • Create & configure a sync policy for Exchange and IBM Notes,
    • Create & configure a sync policy for Google's G Suite, or
    • Create & configure a sync policy for GroupWise (available soon).