Highlighted
HPSMdeployer Absent Member.
Absent Member.
2928 views

RTE I dbInsert: The record being added contains a duplicate key

Jump to solution

Hi Team, We have migrated HPSM from production DB to test DB. Test DB is the replica of production DB. After migration HPSM was working fine for 2 days, but from yesterday it started showing errors for duplication key:

 Please see the logs below, thanks in advance for the help...

 

 

7668(  7524) 07/31/2014 12:22:15  RTE E Error: SQL code=1 message=ORA-00001: unique constraint (SMADMIN.PROBSUMMARYM124431162) violated

  7668(  7524) 07/31/2014 12:22:15  RTE E API=OCIStmtExecute [in _insertOrUpdate], Statement=INSERT INTO PROBSUMMARYM1 ("NUMBER","CATEGORY","OPEN_TIME","OPENED_BY","PRIORITY_CODE","SEVERITY","UPDATE_TIME","ASSIGNMENT","REFERRAL_TIME","REFERRED_TO","ALERT_TIME","STATUS","CLOSE_TIME","CLOSED_BY","ELAPSED_TIME","VENDOR","REFERENCE_NO","CONTACT_TIME","REFERRAL_TO_CONTACT","ONSITE_TIME","CONTACT_TO_RESPOND","REPAIR_TIME","ONSITE_TO_REPAIR","BACKUP_START","BACKUP_TIME","BACKUP_END","DOWNTIME","CAUSE_CODE","RESOLUTION_CODE","LOGICAL_NAME","GROUP","JOB_NAME","LOCATION","VERSION","TYPE","ABEND_CODE","MODEL","ACTION","RESOLUTION","AFFECTED","KEY_WORDS","XREFERENCE","ALERT1","ALERT2","ALERT3","DEADLINE","REASSIGNED","ID","LOOKUP_TIME","TOTAL_PAGES","FLAG","DOWNTIME_END","DOWNTIME_START","ASSIGNEE_NAME","RESPOND_TIME","CONTACT_NAME","SECONDS","CALLER_ID","CONTACT_PHONE","UPDATE_ACTION","ACTOR","FORMAT","COUNT","RESPOND_TO_ONSITE","NETWORK_NAME","FINAL_CLOSE","OPEN_GROUP","ALERT_STATUS","DEADLINE_GROUP","DEADLINE_ALERT","PENDING_DATE","REFERRAL_COUNT","PENDING_REASON","NETWORK_ADDRESS","OUTAGE_TYPE","PARENT","DOMAIN","CALLBACK_LIST","CLOSING_COMMENTS","CS_CODE","CHANGE_NO","LAST_NAME","FIRST_NAME","COMPANY","START_TIME","TITLE","BRIEF_DESCRIPTION","DOCUMENT_ID","FOREIGN","FOREIGN_ID","DEPT","SERIAL_NO_","BUILDING","FLOOR","QUOTE_NO","TICKET_OWNER","INCIDENT_ID","SYSORGSITE","SYSHOMESITE","SYSMODTIME","UPDATED_BY","PROBLEM_STATUS","SLA_CONTACT","SLA_VENDOR","COMPANY_SLA","SUBCATEGORY","HOT_TIC","APPLICATION_NAME","SOLUTION_CANDIDATE","AGREEMENT_ID","PLANNED_START","PLANNED_END","Y2K_RELATED","OPERATIONAL_DEVICE","JUNK","CONTRACT_ID","SYSMODCOUNT","SYSMODUSER","KNOWNERROR","KPF_ID","CI_DATE_TIME","FLOW","SERVER_ID","UNITS","VALUE","PORT_INDEX","SYSTEM_STATE","PAYROLL_NO","CRITICAL_USER","ROOM_FLOOR_REF","USER_TYPE","SITE_CATEGORY","TOTAL_LOSS","PRODUCT_TYPE","PROBLEM_TYPE","FIX_TYPE","NO_SDU_FIX","RESOLVED_BY","COST_CENTRE","CUSTOMER_NO","UNSUSPEND_TIME","CRITICAL_DEVICE","UNUSED","FAILING_SERIAL_NO","THIRD_PARTY_NAME","THIRD_PARTY_REFERENCE","THIRD_PARTY_REFERRED","THIRD_PARTY_REFERRED_BY","CLASS","ALTERNATE_CONTACT","SITE_VISIT_DATE","SITE_VISIT_TECHNICIAN","OPERATING_SYSTEM","OS_RELEASE_LEVEL","OS_MAINT_LEVEL","MANUFACTURER","FAILING_COMPONENT","COUNTRY","CUSTOMER_REFERENCE","EXPD_RESPONSE_TIME","OTI_ORIGINATOR","OTI_ORIGINATOR_REFERENCE","OTI_ORIGINATOR_VERSION","OTI_TOSC_CONSUMER","OTI_TOSC_CONSUMER_REFERENCE","OTI_TOSC_PROVIDER","OTI_TOSC_PROVIDER_REFERENCE","OTI_MESSAGE_TYPE","OTI_FROMSC_CONSUMER","OTI_FROMSC_PROVIDER","OTI_FROMSC_CONSUMER_REFERENCE","OTI_FROMSC_PROVIDER_REFERENCE","PENDING_CHANGE","MANDATORY_ASSET","REG_ERROR","CUS_ERROR","VARIABLE1","VARIABLE2","VARIABLE3","CALL_ORIGIN","SOURCE","FIRST_TIME_FIX","RESOLVED_GROUP","RESOLVED_TIME","CLOSED_GROUP","SLA_ALERT_TIME","CONTACT_LOCATION","SRVC_MANAGER","SRVC_DEL_MANAGER","DIFFERENT_FROM_CONTACT","ALTERNATE_FAX","ALTERNATE_EXTENSION","ALTERNATE_PHONE","USER_PRIORITY","SLA_EXPIRE","CORP_STRUCTURE","RES_ANAL_CODE","LAST_ACTIVITY","MOBILE_CHECKOUT","LOCATION_FULL_NAME","PREV_UPDATE_TIME","MOBILE_UPDATE_TIME","REOPEN_TIME","REOPENED_BY","BILLTO","BILLTYPE","GL_NUMBER","TIME_SPENT","EXPLANATION","ADDRESS_1","ADDRESS_2","ADDRESS_3","ASSET_STATUS","CITY","CONTACT_EMAIL","COUNTY","EXTENSION","FAX","PARTS","LABOR","CONTRACT_CONSUMED","SITE","DUMP","DEADLINE_ALERT_FLAG","PAGE","SLA_STARTED","SLA_ENDED","ADJ_RESOLUTION_BY","ADJ_RESOLUTION_TIME","POSTCODE","ROOM","COMPONENT_CATEGORY","NDTHREAD","SLA_BREACH","ESS_ENTRY","PROB_MGMT_CANDIDATE","CUST_VISIBLE","INITIAL_IMPACT","KPF_FILE","FOLDER","AFFECTED_SERVICES","AGREEMENT_IDS","KPI_STATUS","KPI_VALUE","CI","AFFECTED_ITEM","MOD_EVENT","NO_AUTOCLOSE","EXTERNAL_PROCESS_REFERENCE","UPDATE_TYPE","AFFECTED_OBJECT","MANAGED_OBJECT_CLASS","ISSUE_TXT","PRIORITY_CODE_D","PROBLEM_STATUS_D","NAME","TOTAL_WORK_TIME") VALUES(:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X) RETURNING "ACTION","RESOLUTION","UPDATE_ACTION","CLOSING_COMMENTS","AGREEMENT_IDS" INTO :L37,:L38,:L59,:L78,:L241

  7668(  7524) 07/31/2014 12:22:15  RTE I dbInsert: The record being added contains a duplicate key

  7668(  7524) 07/31/2014 12:22:15  RTE I dbInsert: file:(probsummary) key:(number=IM68739)

  7668(  1860) 07/31/2014 12:22:19  RTE I Using "utalloc" memory manager

7668(  5152) 07/31/2014 12:24:18  RTE I sql total 0.063  call#:182 -->sqociDisconnect:OCIServerDetach

  7668(  5152) 07/31/2014 12:24:18  RTE I Thread termination cleanup complete

  7668(  6548) 07/31/2014 12:24:26  RTE A SUMMARY-1 The following event has been reported 3 times in the last hour

  7668(  6548) 07/31/2014 12:24:26  RTE A Performance-6-operator, Hit Ratio not achieved on file operator and query (assignment.groups="IT CRM"):  Of 171 records checked so far, 166 did not match the query

  7668(  6548) 07/31/2014 12:24:26  RTE A SUMMARY-1 The following event has been reported 3 times in the last hour

  7668(  6548) 07/31/2014 12:24:26  RTE A Performance-6-operator, Hit Ratio not achieved on file operator and query (assignment.groups="IT CRM"):  Of 5106 records checked, 5083 did not match the query

  7668(  6548) 07/31/2014 12:24:26  RTE E Error: SQL code=1 message=ORA-00001: unique constraint (SMADMIN.KMKNOWLEDGE1M1BCC9006C) violated

  7668(  6548) 07/31/2014 12:24:26  RTE E API=OCIStmtExecute [in _insertOrUpdate], Statement=INSERT INTO KMKNOWLEDGE1M1 ("DOCID","COLLECTIONNAME","ACTION","SYSMODTIME","SYSMODUSER","SYSMODCOUNT","ID","SEDOCID","RECDATA") VALUES(:X,:X,:X,:X,:X,:X,:X,:X,:X)

  7668(  6548) 07/31/2014 12:24:26  RTE I dbInsert: The record being added contains a duplicate key

  7668(  6548) 07/31/2014 12:24:26  RTE I dbInsert: file:(kmknowledgebaseupdates) key:(id=KMU0000136492)

  7668(  6548) 07/31/2014 12:24:26   JS W Please provide queryhashcode parameter to avoid an invalid hash code

  7668(  6548) 07/31/2014 12:24:26   JS W Please provide queryhashcode parameter to avoid an invalid hash code

  7668(  6548) 07/31/2014 12:24:26  RTE E Error: SQL code=1 message=ORA-00001: unique constraint (SMADMIN.ACTSVCMGTM15AA4189C) violated

  7668(  6548) 07/31/2014 12:24:26  RTE E API=OCIStmtExecute [in _insertOrUpdate], Statement=INSERT INTO ACTSVCMGTM1 ("THENUMBER","NUMBER","TYPE","DATESTAMP","OPERATOR","DESCRIPTION","NEGDATESTAMP","SYSMODTIME","SYSMODCOUNT","SYSMODUSER","SYSHOMESITE","CUST_VISIBLE") VALUES(:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X) RETURNING "DESCRIPTION" INTO :L5

  7668(  6548) 07/31/2014 12:24:26  RTE I dbInsert: The record being added contains a duplicate key

  7668(  6548) 07/31/2014 12:24:26  RTE I dbInsert: file:(activityservicemgt) key:(number=SD107503,negdatestamp=67724 04:35:34,thenumber=001A184017)

  7668(  6548) 07/31/2014 12:24:27  RTE E Error: SQL code=1 message=ORA-00001: unique constraint (SMADMIN.PROBSUMMARYM124431162) violated

  7668(  6548) 07/31/2014 12:24:27  RTE E API=OCIStmtExecute [in _insertOrUpdate], Statement=INSERT INTO PROBSUMMARYM1 ("NUMBER","CATEGORY","OPEN_TIME","OPENED_BY","PRIORITY_CODE","SEVERITY","UPDATE_TIME","ASSIGNMENT","REFERRAL_TIME","REFERRED_TO","ALERT_TIME","STATUS","CLOSE_TIME","CLOSED_BY","ELAPSED_TIME","VENDOR","REFERENCE_NO","CONTACT_TIME","REFERRAL_TO_CONTACT","ONSITE_TIME","CONTACT_TO_RESPOND","REPAIR_TIME","ONSITE_TO_REPAIR","BACKUP_START","BACKUP_TIME","BACKUP_END","DOWNTIME","CAUSE_CODE","RESOLUTION_CODE","LOGICAL_NAME","GROUP","JOB_NAME","LOCATION","VERSION","TYPE","ABEND_CODE","MODEL","ACTION","RESOLUTION","AFFECTED","KEY_WORDS","XREFERENCE","ALERT1","ALERT2","ALERT3","DEADLINE","REASSIGNED","ID","LOOKUP_TIME","TOTAL_PAGES","FLAG","DOWNTIME_END","DOWNTIME_START","ASSIGNEE_NAME","RESPOND_TIME","CONTACT_NAME","SECONDS","CALLER_ID","CONTACT_PHONE","UPDATE_ACTION","ACTOR","FORMAT","COUNT","RESPOND_TO_ONSITE","NETWORK_NAME","FINAL_CLOSE","OPEN_GROUP","ALERT_STATUS","DEADLINE_GROUP","DEADLINE_ALERT","PENDING_DATE","REFERRAL_COUNT","PENDING_REASON","NETWORK_ADDRESS","OUTAGE_TYPE","PARENT","DOMAIN","CALLBACK_LIST","CLOSING_COMMENTS","CS_CODE","CHANGE_NO","LAST_NAME","FIRST_NAME","COMPANY","START_TIME","TITLE","BRIEF_DESCRIPTION","DOCUMENT_ID","FOREIGN","FOREIGN_ID","DEPT","SERIAL_NO_","BUILDING","FLOOR","QUOTE_NO","TICKET_OWNER","INCIDENT_ID","SYSORGSITE","SYSHOMESITE","SYSMODTIME","UPDATED_BY","PROBLEM_STATUS","SLA_CONTACT","SLA_VENDOR","COMPANY_SLA","SUBCATEGORY","HOT_TIC","APPLICATION_NAME","SOLUTION_CANDIDATE","AGREEMENT_ID","PLANNED_START","PLANNED_END","Y2K_RELATED","OPERATIONAL_DEVICE","JUNK","CONTRACT_ID","SYSMODCOUNT","SYSMODUSER","KNOWNERROR","KPF_ID","CI_DATE_TIME","FLOW","SERVER_ID","UNITS","VALUE","PORT_INDEX","SYSTEM_STATE","PAYROLL_NO","CRITICAL_USER","ROOM_FLOOR_REF","USER_TYPE","SITE_CATEGORY","TOTAL_LOSS","PRODUCT_TYPE","PROBLEM_TYPE","FIX_TYPE","NO_SDU_FIX","RESOLVED_BY","COST_CENTRE","CUSTOMER_NO","UNSUSPEND_TIME","CRITICAL_DEVICE","UNUSED","FAILING_SERIAL_NO","THIRD_PARTY_NAME","THIRD_PARTY_REFERENCE","THIRD_PARTY_REFERRED","THIRD_PARTY_REFERRED_BY","CLASS","ALTERNATE_CONTACT","SITE_VISIT_DATE","SITE_VISIT_TECHNICIAN","OPERATING_SYSTEM","OS_RELEASE_LEVEL","OS_MAINT_LEVEL","MANUFACTURER","FAILING_COMPONENT","COUNTRY","CUSTOMER_REFERENCE","EXPD_RESPONSE_TIME","OTI_ORIGINATOR","OTI_ORIGINATOR_REFERENCE","OTI_ORIGINATOR_VERSION","OTI_TOSC_CONSUMER","OTI_TOSC_CONSUMER_REFERENCE","OTI_TOSC_PROVIDER","OTI_TOSC_PROVIDER_REFERENCE","OTI_MESSAGE_TYPE","OTI_FROMSC_CONSUMER","OTI_FROMSC_PROVIDER","OTI_FROMSC_CONSUMER_REFERENCE","OTI_FROMSC_PROVIDER_REFERENCE","PENDING_CHANGE","MANDATORY_ASSET","REG_ERROR","CUS_ERROR","VARIABLE1","VARIABLE2","VARIABLE3","CALL_ORIGIN","SOURCE","FIRST_TIME_FIX","RESOLVED_GROUP","RESOLVED_TIME","CLOSED_GROUP","SLA_ALERT_TIME","CONTACT_LOCATION","SRVC_MANAGER","SRVC_DEL_MANAGER","DIFFERENT_FROM_CONTACT","ALTERNATE_FAX","ALTERNATE_EXTENSION","ALTERNATE_PHONE","USER_PRIORITY","SLA_EXPIRE","CORP_STRUCTURE","RES_ANAL_CODE","LAST_ACTIVITY","MOBILE_CHECKOUT","LOCATION_FULL_NAME","PREV_UPDATE_TIME","MOBILE_UPDATE_TIME","REOPEN_TIME","REOPENED_BY","BILLTO","BILLTYPE","GL_NUMBER","TIME_SPENT","EXPLANATION","ADDRESS_1","ADDRESS_2","ADDRESS_3","ASSET_STATUS","CITY","CONTACT_EMAIL","COUNTY","EXTENSION","FAX","PARTS","LABOR","CONTRACT_CONSUMED","SITE","DUMP","DEADLINE_ALERT_FLAG","PAGE","SLA_STARTED","SLA_ENDED","ADJ_RESOLUTION_BY","ADJ_RESOLUTION_TIME","POSTCODE","ROOM","COMPONENT_CATEGORY","NDTHREAD","SLA_BREACH","ESS_ENTRY","PROB_MGMT_CANDIDATE","CUST_VISIBLE","INITIAL_IMPACT","KPF_FILE","FOLDER","AFFECTED_SERVICES","AGREEMENT_IDS","KPI_STATUS","KPI_VALUE","CI","AFFECTED_ITEM","MOD_EVENT","NO_AUTOCLOSE","EXTERNAL_PROCESS_REFERENCE","UPDATE_TYPE","AFFECTED_OBJECT","MANAGED_OBJECT_CLASS","ISSUE_TXT","PRIORITY_CODE_D","PROBLEM_STATUS_D","NAME","TOTAL_WORK_TIME") VALUES(:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X) RETURNING "ACTION","AGREEMENT_IDS" INTO :L37,:L241

  7668(  6548) 07/31/2014 12:24:27  RTE I dbInsert: The record being added contains a duplicate key

  7668(  6548) 07/31/2014 12:24:27  RTE I dbInsert: file:(probsummary) key:(number=IM68740)

  7668(  6548) 07/31/2014 12:24:27   JS W Please provide queryhashcode parameter to avoid an invalid hash code

  7668(  6548) 07/31/2014 12:24:27   JS W Please provide queryhashcode parameter to avoid an invalid hash code

  1920(  1676) 07/31/2014 12:24:39  RAD I Email has been sent to yomi.kasali@etisalat.com.ng.

  2728(  8488) 07/31/2014 12:24:46  RTE I Using "utalloc" memory manager

  2728(  8488) 07/31/2014 12:24:46  RTE I Process sm 9.31.2004 (2004) System: 13080 (0x784DFB00) on PC (x64 64-bit) running Windows Server 2008 R2 (6.1 Build 7600) from NMS1

  2728(  8488) 07/31/2014 12:24:46  RTE I Connected to SOAP client at 10.160.174.194

  2728(  8488) 07/31/2014 12:24:46  RTE I Thread attaching to resources with key 0x784DFB00

  2728(  8488) 07/31/2014 12:24:46  RTE I Thread DDF5C18DBD63D325DDC3D6DCA1909C2B initialization done.

  2728(  6876) 07/31/2014 12:24:46 JRTE I Webservice API session - Thread ID: DDF5C18DBD63D325DDC3D6DCA1909C2B; session timeout: 1800 seconds

  2728(  8488) 07/31/2014 12:24:46  RTE I Connection to dbtype 'oracle10' Oracle server 'smdbtest' as user 'smadmin' successful

  2728(  8488) 07/31/2014 12:24:46  RTE I Connected to Oracle Version 11.2.0.1.0

  2728(  8488) 07/31/2014 12:24:46  RTE I Oracle Client version: 11.2.0.1.0

  2728(  8488) 07/31/2014 12:24:46  RTE I Oracle server settings for language, territory and character set: AMERICAN_AMERICA.WE8MSWIN1252 (AL16UTF16)

  2728(  8488) 07/31/2014 12:24:46  RTE I OCI Client settings for language, territory and character set: AMERICAN_AMERICA.AL32UTF8 (UTF16)

  2728(  8488) 07/31/2014 12:24:46  RTE W Oracle instance setting for NLS_SORT could not be determined. Default to BINARY

  2728(  8488) 07/31/2014 12:24:46  RTE I Oracle instance setting for NLS_COMP is set to BINARY

  2728(  8488) 07/31/2014 12:24:46  RTE I Oracle session is set up in BINARY mode

  2728(  8488) 07/31/2014 12:24:46  RTE I LDAP: Server '10.150.140.10' supports LDAP Protocol Version 3.

  2728(  8488) 07/31/2014 12:24:46  RTE I LDAP: Directory Server is an Active Directory

  2728(  8488) 07/31/2014 12:24:46  RTE E _getLicenseInfoEntityForUpdate(): Error getting license info from database

  2728(  8488) 07/31/2014 12:24:46  RTE E User falcon login failed.

  2728(  8488) 07/31/2014 12:24:46  RTE E Error: SQL code=1 message=ORA-00001: unique constraint (SMADMIN.SCHEDULEM1244FEC3F) violated

  2728(  8488) 07/31/2014 12:24:46  RTE E API=OCIStmtExecute [in _insertOrUpdate], Statement=INSERT INTO SCHEDULEM1 ("DESCRIPTOR","CLASS","EXPIRATION","NUMBER","NAME","APPLICATION","STATUS","SCHED_CLASS","PM_STATUS","PM_NUMBER","SCHEDULE_ID","OBJECT","TYPE") VALUES(:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X) RETURNING "DESCRIPTOR" INTO :L0

  2728(  8488) 07/31/2014 12:24:46  RTE I dbInsert: The record being added contains a duplicate key

  2728(  8488) 07/31/2014 12:24:46  RTE I dbInsert: file:(schedule) key:(schedule.id=8325096)

  2728(  8488) 07/31/2014 12:24:46  RTE W Exception occurred for method RetrieveKeysList and XML request <?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><RetrieveEventOutKeysListRequest xmlns="http://servicecenter.peregrine.com/PWS"><model><keys xsi:nil="true"/><instance><evtype>ossjpm</evtype></instance></model></RetrieveEventOutKeysListRequest></soapenv:Body></soapenv:Envelope>

 

0 Likes
1 Solution

Accepted Solutions
Acclaimed Contributor.. Vadim Gorda Acclaimed Contributor..
Acclaimed Contributor..

Re: RTE I dbInsert: The record being added contains a duplicate key

Jump to solution

hello,

"Then if i am correct, I have to update the NUMBER table with "68858" or even higher than this. Right?" - Correct

 

In class field check the last numbers for 

incident management

incidents

cm3r

cm3t

device

activity

activitycm3r

activitycm3t

activityproblem

activityproblemtasks

activityservicemgt

activitySubscription

 

 

You might need something else as I am not aware of everything in your system. 

 

First of all start with the objects on which you were getting errors and check if they will still pop uo after that. Maybe problem is not in number records.

0 Likes
17 Replies
Acclaimed Contributor.. Vadim Gorda Acclaimed Contributor..
Acclaimed Contributor..

Re: RTE I dbInsert: The record being added contains a duplicate key

Jump to solution

What do you call under migration from dev to production? Have you pulled data like incidents, actions and other staff? Counters? have you checked if in the system are present records with the specified ids?

0 Likes
HPSMdeployer Absent Member.
Absent Member.

Re: RTE I dbInsert: The record being added contains a duplicate key

Jump to solution
Few more Logs:

4924( 8712) 07/31/2014 14:12:16 RTE I -Memory : S(4100576) O(1144220) MAX(5244796) - MALLOC's Total(361570)
4924( 7428) 07/31/2014 14:12:18 RTE E Error: SQL code=1 message=ORA-00001: unique constraint (SMADMIN.INCIDENTSM1BCDE1A6A) violated
4924( 7428) 07/31/2014 14:12:18 RTE E API=OCIStmtExecute [in _insertOrUpdate], Statement=INSERT INTO INCIDENTSM1 ("INCIDENT_ID","PROBLEM_ID","CONTACT_NAME","SEVERITY","OPEN_TIME","UPDATE_TIME","OPENED_BY","UPDATED_BY","DESCRIPTION","AFFECTED_ITEM","OWNER_NAME","OPEN","CALLBACK_TYPE","CALLBACK_REASON","UNUSED_FIELD","RESOLUTION","UNASSIGNED","CATEGORY","HANDLE_TIME","MODEL","TYPE","DEPT","LOCATION","CLOSE_TIME","CLOSED_BY","SOLUTION_CANDIDATE","AGREEMENT_ID","PRIORITY_CODE","FIRST_CALL","CONTRACT_ID","CONTRACT_CONSUMED","WORKED_TIME","SYSMODCOUNT","SYSMODUSER","SYSMODTIME","KPF_ID","PAYROLL_NO","CRITICAL_USER","ROOM","USER_TYPE","SITE_CATEGORY","TOTAL_LOSS","TEMP_UPDATE","SUBCATEGORY","PRODUCT_TYPE","PROBLEM_TYPE","FAILED_ENTITLEMENT","COST_CENTRE","CONTACT_LOCATION","PHONE","EXTENSION","CRITICAL_DEVICE","CAUSE_CODE","RESOLUTION_CODE","COMPANY","COMPANY_ID","VENDOR","CLASS","COUNTRY","ALTERNATE_CONTACT","ENGINEER","DIFFERENT_FROM_CONTACT","ALTERNATE_PHONE","ALTERNATE_EXTENSION","CUSTOMER_REFERENCE","FAX","ALTERNATE_FAX","PENDING_CHANGE","MANDATORY_ASSET","FLOOR","BUILDING","VARIABLE1","VARIABLE2","VARIABLE3","CORP_STRUCTURE","CORP_LEVEL1","CORP_LEVEL2","CORP_LEVEL3","CONTACT_EMAIL","LOCATION_FULL_NAME","CONTACT_FIRST","CONTACT_LAST","BILLTO","BILLTYPE","GL_NUMBER","ENTITLEMENT_REF","CONTACT_TZ","ESS_ENTRY","SLA_BREACH","NEXT_BREACH","OTHER","CALLBACK_CONTACT","CALLBACK_PHONE","CALLBACK_EMAIL","CALLBACK_BEEPER","FIRST_TOUCH","UPDATE_ACTION","UPDATE_ACTION_ESS","CUST_VISIBLE","INITIAL_IMPACT","NEEDED_BY_TIME","REQUESTTYPE","SVC_OPTIONS","ONE_CLICK","APPROVAL_STATUS","RESET_APPROVALS","SVC_COST","KPF_FILE","FOLDER","SUBSCRIPTIONITEM","AGREEMENT_IDS","EXPECTEDRESOLUTION","CONTACT_FULLNAME","CALLBACK_CONTACT_FULLNAME","CARTID","LOGICAL_NAME","TITLE","ESSUPDATED","BREQUESTONBEHALF","SOURCE_SERVICE","ISSUE_TXT","PRIORITY_CODE_D") VALUES(:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X) RETURNING "DESCRIPTION","AGREEMENT_IDS" INTO :L8,:L110
4924( 7428) 07/31/2014 14:12:18 RTE I dbInsert: The record being added contains a duplicate key
4924( 7428) 07/31/2014 14:12:18 RTE I dbInsert: file:(incidents) key:(incident.id=SD107590)
4924( 5168) 07/31/2014 14:12:24 RTE E Error: SQL code=1 message=ORA-00001: unique constraint (SMADMIN.INCIDENTSM1BCDE1A6A) violated
4924( 5168) 07/31/2014 14:12:24 RTE E API=OCIStmtExecute [in _insertOrUpdate], Statement=INSERT INTO INCIDENTSM1 ("INCIDENT_ID","PROBLEM_ID","CONTACT_NAME","SEVERITY","OPEN_TIME","UPDATE_TIME","OPENED_BY","UPDATED_BY","DESCRIPTION","AFFECTED_ITEM","OWNER_NAME","OPEN","CALLBACK_TYPE","CALLBACK_REASON","UNUSED_FIELD","RESOLUTION","UNASSIGNED","CATEGORY","HANDLE_TIME","MODEL","TYPE","DEPT","LOCATION","CLOSE_TIME","CLOSED_BY","SOLUTION_CANDIDATE","AGREEMENT_ID","PRIORITY_CODE","FIRST_CALL","CONTRACT_ID","CONTRACT_CONSUMED","WORKED_TIME","SYSMODCOUNT","SYSMODUSER","SYSMODTIME","KPF_ID","PAYROLL_NO","CRITICAL_USER","ROOM","USER_TYPE","SITE_CATEGORY","TOTAL_LOSS","TEMP_UPDATE","SUBCATEGORY","PRODUCT_TYPE","PROBLEM_TYPE","FAILED_ENTITLEMENT","COST_CENTRE","CONTACT_LOCATION","PHONE","EXTENSION","CRITICAL_DEVICE","CAUSE_CODE","RESOLUTION_CODE","COMPANY","COMPANY_ID","VENDOR","CLASS","COUNTRY","ALTERNATE_CONTACT","ENGINEER","DIFFERENT_FROM_CONTACT","ALTERNATE_PHONE","ALTERNATE_EXTENSION","CUSTOMER_REFERENCE","FAX","ALTERNATE_FAX","PENDING_CHANGE","MANDATORY_ASSET","FLOOR","BUILDING","VARIABLE1","VARIABLE2","VARIABLE3","CORP_STRUCTURE","CORP_LEVEL1","CORP_LEVEL2","CORP_LEVEL3","CONTACT_EMAIL","LOCATION_FULL_NAME","CONTACT_FIRST","CONTACT_LAST","BILLTO","BILLTYPE","GL_NUMBER","ENTITLEMENT_REF","CONTACT_TZ","ESS_ENTRY","SLA_BREACH","NEXT_BREACH","OTHER","CALLBACK_CONTACT","CALLBACK_PHONE","CALLBACK_EMAIL","CALLBACK_BEEPER","FIRST_TOUCH","UPDATE_ACTION","UPDATE_ACTION_ESS","CUST_VISIBLE","INITIAL_IMPACT","NEEDED_BY_TIME","REQUESTTYPE","SVC_OPTIONS","ONE_CLICK","APPROVAL_STATUS","RESET_APPROVALS","SVC_COST","KPF_FILE","FOLDER","SUBSCRIPTIONITEM","AGREEMENT_IDS","EXPECTEDRESOLUTION","CONTACT_FULLNAME","CALLBACK_CONTACT_FULLNAME","CARTID","LOGICAL_NAME","TITLE","ESSUPDATED","BREQUESTONBEHALF","SOURCE_SERVICE","ISSUE_TXT","PRIORITY_CODE_D") VALUES(:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X,:X) RETURNING "DESCRIPTION","AGREEMENT_IDS" INTO :L8,:L110
4924( 5168) 07/31/2014 14:12:24 RTE I dbInsert: The record being added contains a duplicate key
4924( 5168) 07/31/2014 14:12:24 RTE I dbInsert: file:(incidents) key:(incident.id=SD107593)
0 Likes
HPSMdeployer Absent Member.
Absent Member.

Re: RTE I dbInsert: The record being added contains a duplicate key

Jump to solution

we have took the DB dump from one database and imported it to the Test Database. then pointed the HPSM from SM.ini file to the new database. both are Oracle DB

 

Also as you asked about the present records, i want to tell you that, few people are complaining that they are not able to login. Also if service desk people are trying to Assign the ticket to Resolver, they are getting the error message of invalid contact.

0 Likes
Piku Absent Member.
Absent Member.

Re: RTE I dbInsert: The record being added contains a duplicate key

Jump to solution
Hi,

As told above it is because of some record with same unique already exists in system.
However it should not be case as number files auto update after assigning id to ticket.
But this also may be due to index corruption at DB end.

Do some one has did some tailoring or change in system before the error starts coming ?

You may try to restart the SM services or SM db too.


Regards,
____________________________________
Assign Kudo, if found post useful and mark it accepted if solves the issue.
0 Likes
Piku Absent Member.
Absent Member.

Re: RTE I dbInsert: The record being added contains a duplicate key

Jump to solution
For safe side, run command
“sm –unlockdatabase” form RUN directory after stopping SM services.

regards,
____________________________________
Assign Kudo, if found post useful and mark it accepted if solves the issue.
0 Likes
HPSMdeployer Absent Member.
Absent Member.

Re: RTE I dbInsert: The record being added contains a duplicate key

Jump to solution
After migration there was no tailoring done. Also i restarted the SM services. I also doubt that it is related to indexing and already asked to DBA to restart the DB. Can you help me with any other suggestion? if requires to do some configuration change in HPSM application level?
0 Likes
Acclaimed Contributor.. Vadim Gorda Acclaimed Contributor..
Acclaimed Contributor..

Re: RTE I dbInsert: The record being added contains a duplicate key

Jump to solution

How do you manage to not lose data when pushed db from dev to production? Your production was stopped for the time period of moving db from Production to Development for modifications?

 

If you were not stopping the production server then you would have lost all records which ere created after taking db to development server.

 

Have you checked that persons which does not have contact records and are bind to records in the system?

0 Likes
HPSMdeployer Absent Member.
Absent Member.

Re: RTE I dbInsert: The record being added contains a duplicate key

Jump to solution
Yes, I checked with the person. Looks like we had the maintenance window of 3 hours to take the DP dump and import into the another, and in meantime few people created the interactions, since our sysadmin team forgot to stop SM services.

as per the above suggestion, I stopped the SM Services and run “sm –unlockdatabase” commnad. but still no luck.

can somebody please help to resolve it, since the issue is became very critical.
0 Likes
Acclaimed Contributor.. Vadim Gorda Acclaimed Contributor..
Acclaimed Contributor..

Re: RTE I dbInsert: The record being added contains a duplicate key

Jump to solution

I don't understan how you any action of the persons on prod were affecting your backup if you have moved the whole dump to production.

 

Anyway check what is the last number of Interaction, incident, problem, change .... and then check what is set in the Number records for respective tables . if the last number in the Number table is lower then your last Interaction, Incident .... number then change it to higher then the last one and save. this will start increment of the number again nd there should not be collision of the id's.

 

Regarding contacts - just create them again in new system and use the names as in objects which dropped the links to the contacts.

0 Likes
HPSMdeployer Absent Member.
Absent Member.

Re: RTE I dbInsert: The record being added contains a duplicate key

Jump to solution

Thanks Vadim,

 

I'll try this tomorrow and update the outcome here.

0 Likes
HPSMdeployer Absent Member.
Absent Member.

Re: RTE I dbInsert: The record being added contains a duplicate key

Jump to solution

Hi Vadim,

 

As you said the highest number, say for Incident. we have IM68857. So is "68857" number to be considered as highest?

Then if i am correct, I have to update the NUMBER table with "68858" or even higher than this. Right?

 

Request you to explain the steps with the exact table names, if i am not right above and have to follow the different approach.

 

Thanks in advance for the kind support.

0 Likes
Acclaimed Contributor.. Vadim Gorda Acclaimed Contributor..
Acclaimed Contributor..

Re: RTE I dbInsert: The record being added contains a duplicate key

Jump to solution

hello,

"Then if i am correct, I have to update the NUMBER table with "68858" or even higher than this. Right?" - Correct

 

In class field check the last numbers for 

incident management

incidents

cm3r

cm3t

device

activity

activitycm3r

activitycm3t

activityproblem

activityproblemtasks

activityservicemgt

activitySubscription

 

 

You might need something else as I am not aware of everything in your system. 

 

First of all start with the objects on which you were getting errors and check if they will still pop uo after that. Maybe problem is not in number records.

0 Likes
Piku Absent Member.
Absent Member.

Re: RTE I dbInsert: The record being added contains a duplicate key

Jump to solution
Hi,

Here since you are getting unique constraint error in almost all of the SM tables so feels issue should be of DB side as conflict in each unique id is rare as of sudden.

Did you tried to restart the SM db? Asked dba to check errors.

Would suggest to recreate the replica as you will surely having the DB dump.

You may try to update each table from sm interface by just click on 'ok' button on each erroneous dbdict and datadict.
Restart the SM service before and after the activity.

Regards,
____________________________________
Assign Kudo, if found post useful and mark it accepted if solves the issue.
0 Likes
HPSMdeployer Absent Member.
Absent Member.

Re: RTE I dbInsert: The record being added contains a duplicate key

Jump to solution
Thanks for the great help, I followed Vadim's solution and it started working fine. But now after assigning the incident to resolver, it gives below error: "Process panel display.go in RAD display encountered error in line 6 (display,display.go)"

The error doesnt affect the incident assignment but its annoying the service desk agents. Can I get some help to override on this error.

Thanks in advance, this is such nice forum to get help on the issues. Keep it up guys!!!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.