Deleting SMS Users Fail with "Delete Unsuccessful :User Logged On" when User is not Logged On
(Doc ID 1959558.1)
Last updated on JULY 05, 2024
Applies to:
Oracle Communications Network Charging and Control - Version 5.0.0 and laterOracle Solaris on SPARC (64-bit)
Symptoms
In Network Charging and Control (NCC), when attempting to delete a System Management Server (SMS) user, the following error pops up:
This error may legitimately be logged if the SMS is actually logged on, but this KM article will cover cases where this is not the case.
Further (and more useful) errors can be found in the /IN/service_packages/SMS/tmp/smsTaskAgent.log on the SMS, specifically:
Dec 18 01:32:12 smsTaskAgent(16672) Oracle=-2292 oraUserMod.pc@131: delete : ORA-02292: integrity constraint (CCS_ADMIN.CCS_ADJUSER_USER_FK) violat
Dec 18 01:36:17 smsTaskAgent(16672) Oracle=-1918 oraUserMod.pc@129: drop user: ORA-01918: user 'TODELETE' does not exist
Dec 18 01:36:17 smsTaskAgent(16672) Oracle=-1918 oraUserMod.pc@129: drop user: ORA-01918: user 'TODELETE' does not exist
Changes
Attempting to delete an SMS user via the SMS screens.
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 |
| References |