Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Suggested Answer
  • Replies replies
    2
  • Answers answer
    1
  • Subscribers subscribers
    178
  • Views views
    555
  • Users 0 members are here
Related
Options

RTSM error creating service model

Red John

Hello All,

I am triyng to make a simple service model and getting "Error saving Model" output on rtsm ui. when i check the ucmdb/runtime/log/error.log i see there are errors creating and inserting into tables like below : 

-- Caused by: com.mercury.topaz.cmdb.shared.base.CmdbException: com.mercury.topaz.cmdb.server.manage.dal.CmdbDalBatchException: [ErrorCode [-2147483648] undefined error code]
Can't execute BATCH prepared statement [INSERT INTO HDM_231110CI_COLLECTION_1 (ID, CMDB_ID, A_COUNTRY,A_CI_COLLECTION_ID,A_CITY,A_CI_LIFECYCLE_STATE,A_BITMAP_ID,A_DESCRIPTION,A_VULNERABILITY_STATUS,A_TENANTOWNER,A_ACK_CLEARED_TIME,A_DISPLAY_LABEL,A_DATA_ALLOW_AUT................

also like : 

Caused by: com.hp.ucmdb.reconciliation.datain.operation.DataInOperationException: Error while trying to [addStrict] on level [1]! appilog.framework.shared.manage.impl.MamResponseException: [ErrorCode [-2147483648] undefined error code]

database  side is up and running,does anyone knows the problem?

Thanks

Tags:

  • Suggested Answer

    0  

    This error means that you have an issue with your history tables.

    Run the following from the JMX console:

    1) alignHistoryForType:  customerID: 1 (I am assuming)  ciType:ci_collection alignIndexes: true

    2) executeBaselineForClass: customerID: 1 (I am assuming) classType: ci_collection

    You may need to execute a full baseline additionally.

    -- Hope this helps!

    Keith Paschal

    UCMDB Worldwide Support Lead

  • 0  

    Hello,

    To find what the actual issue on DB is you should provide the last Caused by reason from the stack trace.

    Running the methods mention by Keith should help and fix most of history related issues.

    Hope it helps.

    Best Regards,

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.