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.

PeopleTools and Lifecycle Management - PSFT (MOSC)

deploy FSCM PUM 25 failed with Error: Could not change the DB Access

Sep 15, 2017 9:50AM edited Nov 19, 2017 4:03AM in PeopleTools and Lifecycle Management - PSFT (MOSC) 2 commentsAnswered

Hi,

I'm deploying FSCM PUM 25. And it failed in the almost end with following message

PSDMTX Error: signon

Reason: Invalid user ID or password for database signon. (id=The)

Error: Could not change the DB Access

I'm wondering if other people run to this problem.

Yan

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