SAP Knowledge Base Article - Preview

2495178 - Missing Column LASTUPDATED after SMP 3.0 SP13 upgrade

Symptom

After upgrading from SMP 3.0 SP12 PL2 to SMP 3.0 SP13, the following error is shown in the server log:

2017 06 19 13:56:05#+0200#ERROR#com.sap.mobile.platform.server.support.service.impl.MultiTenantLogLevelCache###s-log-settings-refresh-1########Failed to update log settings cache for tenant tenantId org.eclipse.persistence.exceptions.DatabaseException:Internal Exception: com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [260]: invalid column name: LASTUPDATED: line 1 col 35 (at pos 34)Error Code: 260Call: SELECT COMPONENT, ISTRACEENABLED, LASTUPDATED, SEVERITY FROM SMP_SERVER_TRACE_LOG_LEVELQuery: ReadAllQuery(referenceClass=ServerTraceLogLevel sql="SELECT COMPONENT, ISTRACEENABLED, LASTUPDATED, SEVERITY FROM SMP_SERVER_TRACE_LOG_LEVEL").

When we check the table SERVER_TRACE_LOG_LEVEL we can see that the table SERVER_TRACE_LOG_LEVEL exists of three columns: COMPONENT, ISTRACEENABLED and SEVERITY.  

While troubleshooting the installation the logs, there are no error entries that indicate any errors:
com. installshield. sybaseuep.event.dialog.silent.PanelLastSilentImpl, dbg, Upgrade to SAP Mobile Platform 3.0 SP13 has been completed successfully.


Read more...

Environment

  • SMP 3.0 SP12 PL2 or later
  • HANA 1 SP12 (1.00.122.05.1481577062)

Product

SAP Mobile Platform 3.0 ; SAP Mobile Platform 3.1

Keywords

SMP 3.0 SP13; Hana DB; LASTUPDATED; SMP_SERVER_TRACE_LOG_LEVEL; , KBA , MOB-ONP , SAP Mobile Platform on Premise , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.