My Oracle Support Banner

IP2017 - SMC Login Failure After The Backend Database Host Or Instance Is Changed (Doc ID 2371577.1)

Last updated on DECEMBER 05, 2018

Applies to:

Siebel CRM - Version 17.0 [IP2017] and later
Siebel CRM Call Center - Version 18.9 to 18.9 [Release V17]
Information in this document applies to any platform.

Symptoms

On : 17.4 [IP2017] version, Upgrade

ACTUAL BEHAVIOR
---------------
IP2017 migrated installation was working fine, but after the database instance name on the database server side was changed SMC is not authenticating the user sadmin, although the connection to the database is working fine through sqlplus.


EXPECTED BEHAVIOR
-----------------------
The login through SMC should work fine.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot to SMC and perform management tasks

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.