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 System Admin, Install and Upgrade (MOSC)

Siebel Administrator position dropped from SADMIN user after upgrade.

May 26, 2021 2:10PM edited May 26, 2021 2:13PM in Siebel System Admin, Install and Upgrade (MOSC) 1 commentAnswered

After Siebel Upgrade to 20.12, in all RR environments, position for SADMIN user is changed in Siebel.

In our environments, we have Siebel Administrator position with Default Organization division as primary position for SADMIN user.

But after the upgrade ,SADMIN user is updated with Siebel Administrator position with Siebel Administration division. This is set as primary as well.

So we had to manually update SADMIN with Siebel Administrator position having Default Organization division and marking it as Primary.

1) Please suggest which step of Upgrade process is updating the position for SADMIN user ?

2) Any changes required to keep the position of the SADMIN as same as prior to Upgrade ?

Tagged:

IT2SBL-SysAdmin

0

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