Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Siebel Business Process & Functionality (MOSC)

SRProc reported Deadlock On S_SRM_REQUEST

Nov 4, 2014 4:08AM edited Nov 12, 2014 9:27PM in Siebel Business Process & Functionality (MOSC) 6 commentsAnswered

Hi, We are noticing from last week that SRProc is putting a lock on S_SRM_REQUEST and we found this error in the SRProc log file:

select R.ROW_ID, R.RPT_TYPE, A.NAME, A.ACTION_TYPE, A.FILE_LOC, R.PARAM_VAL,

R.ACTL_START_DT, R.ACTL_END_DT, R.SCHED_START_DT, R.LAST_UPD,

R.LAST_UPD_BY, R.SERVER_NAME, R.RPT_NUM, R.RPT_MAX, R.SRB_FLGS,

R.REQUESTED_BY, R.REQ_KEY, R.DESC_TEXT, R.CODE_PAGE, R.LANG_ID,

U.LOGIN, R.RETRY_ON_ERROR_FLG, R.NUM_RETRY

1

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month