Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2139894.1
Update Date:2016-05-23
Keywords:

Solution Type  Problem Resolution Sure

Solution  2139894.1 :   Diameter Signaling Router (DSR) Server Upgrade Fails If SG Name and Server Name Are Identical: ERROR 1022 (23000) at line 8: Can't write; duplicate key in table 'ResourceAudit_000'  


Related Items
  • Oracle Communications Diameter Signaling Router (DSR)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
  •  




In this Document
Symptoms
Changes
Cause
Solution
References


Created from <SR 3-12720089381>

Applies to:

Oracle Communications Diameter Signaling Router (DSR) - Version DSR 7.0 and later
Information in this document applies to any platform.

Symptoms

During a software upgrade, an individual server encounters an error and its upgrade fails.

Looking through the upgrade.log, the following messages can be seen [loader filename may vary]:

aa10_appworks_schema_upgrade.sh: Running upgrade loader file 'load.appworks.upgrade.60.29.0'
ERROR 1022 (23000) at line 8: Can't write; duplicate key in table 'ResourceAudit_000'

Changes

Occurs only during upgrade activity.

Cause

Cause of issue was identified as an upgrade Bug triggered by improper [but allowed by Graphical User Interface (GUI)] naming conventions in use:  Server Group name is identical to the Server name.

Example:

  • Server Group Name:  IPFE
  • Server Name:  IPFE

Solution

Upon this failure, the sever will revert back to the original software release.  The database backup taken prior to the upgrade event may need to be applied to restore the server.  All upgraded servers will need to be backed out to the original release. Thereafter, one of the two following remedies may be applied:

  1. If (a) the server is NOT a Site OAM (SOAM) or Network OAM (NOAM) and (b) the server does NOT have any server-group scoped routes, then when all are on uniform software release, rename Server Groups via the GUI so that they are not identical to any Server Name, and begin upgrade again.
  2. Upgrade to a release that will not have this Bug or related issues for renaming Server Group as indicated in the restrictions for (1) above.
    Bug should be resolved in DSR 7.3 and later releases, however not yet Generally Available (GA) so not yet confirmed.

References

<BUG:22917310> - IPFE UPGRADE TO DSR 7.,2 FAILED

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback