Skip to Content
avatar image
Former Member

Change Tracking in MDM showing table empty from Portal

Hi Experts,

While accessing MDM change tracking history from portal, table that it is showing is empty.

As per note 1336601 checked all is okay.

While checking to the logs from portal

lication_Thread[impl:3]_58##0#0#Error##Plain###[jcc][t4][10335][10366][3.53.95] Invalid operation: Connection is closed. ERRORCODE=-4470, SQLSTATE=08003#

#1.#A6E5C754D50200800000082D00CB00980004ED693E3CBB07#1386936178359#com.sap.mdm.ChangeTrackingBean#sap.com/tc~wd~dispwda#com.sap.mdm.ChangeTrackingBean.SQLException in getConnection()# #374369##7D48A8FC63EE11E3A10800001EF2F9D6#7d48a8fc63ee11e3a10800001ef2f9d6-0#7d48a8fc63ee11e3a10800001ef2f9d6#SAPEngine_Application_Thread[impl:3]_58##0#0#Error##Plain###[jcc][t4][10335][10366][3.53.95] Invalid operation: Connection is closed. ERRORCODE=-4470, SQLSTATE=08003#

#1.#A6E5C754D50200800000082E00CB00980004ED693E3CBB82#1386936178359#com.sap.mdm.ChangeTrackingBean#sap.com/tc~wd~dispwda#com.sap.mdm.ChangeTrackingBean.SQLException in getLookupRecords()# #374369##7D48A8FC63EE11E3A10800001EF2F9D6#7d48a8fc63ee11e3a10800001ef2f9d6-0#7d48a8fc63ee11e3a10800001ef2f9d6#SAPEngine_Application_Thread[impl:3]_58##0#0#Error##Plain###[jcc][t4][10335][10366][3.53.95] Invalid operation: Connection is closed. ERRORCODE=-4470, SQLSTATE=08003#

Please suggest on it,what can be the issue.

Thanks,

Vaibhav

CaptureMDM.PNG (27.6 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Dec 13, 2013 at 04:05 PM

    Hi Vaibhav,

    Perhaps this might help you -

    http://scn.sap.com/thread/1995803

    Thanks,

    Ravi

    Add comment
    10|10000 characters needed characters exceeded

  • Dec 17, 2013 at 11:25 AM

    HI Vaibhav,

    Kindly Configure the JDBC connections.

    Regards,

    Vag Vignesh Shenoy

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Vaibhav,

      this could also happen due to millions of records existing in the change tracking table. It is advised to do a regular purge on change tracking table so that you dont face db connection issues or in general mdm performance issues as every update in change tracked field need to get updated in mdm tables as well as change tracker tables.