<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Failed to Start SAM in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-SAM/m-p/211947#M63047</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I installed HDF3.0 on an existing HDP2.6.0 cluster using Ambari 2.5.1. Installation was succeed, but failed to start SAM. My configuration uses Postgresql for SAM. I got the below error. Does anyone happen to see this before?&lt;/P&gt;&lt;PRE&gt;Exception in thread "main" com.hortonworks.streamline.storage.exception.StorageException: org.postgresql.util.PSQLException: ERROR: syntax error at or near "ON"
  Position: 112
	at com.hortonworks.streamline.storage.impl.jdbc.provider.sql.factory.AbstractQueryExecutor$QueryExecution.executeUpdate(AbstractQueryExecutor.java:223)
	at com.hortonworks.streamline.storage.impl.jdbc.provider.sql.factory.AbstractQueryExecutor.executeUpdate(AbstractQueryExecutor.java:180)
	at com.hortonworks.streamline.storage.impl.jdbc.provider.postgresql.factory.PostgresqlExecutor.insertOrUpdateWithUniqueId(PostgresqlExecutor.java:150)
	at com.hortonworks.streamline.storage.impl.jdbc.provider.postgresql.factory.PostgresqlExecutor.insertOrUpdate(PostgresqlExecutor.java:69)
	at com.hortonworks.streamline.storage.impl.jdbc.JdbcStorageManager.addOrUpdate(JdbcStorageManager.java:81)
	at com.hortonworks.streamline.storage.cache.writer.StorageWriteThrough.addOrUpdate(StorageWriteThrough.java:37)
	at com.hortonworks.streamline.storage.CacheBackedStorageManager.addOrUpdate(CacheBackedStorageManager.java:68)
	at com.hortonworks.streamline.streams.catalog.service.StreamCatalogService.addOrUpdateTopologyVersionInfo(StreamCatalogService.java:262)
	at com.hortonworks.streamline.streams.service.StreamsModule.setupPlaceholderTopologyVersionInfo(StreamsModule.java:210)
	at com.hortonworks.streamline.streams.service.StreamsModule.setupPlaceholderEntities(StreamsModule.java:198)
	at com.hortonworks.streamline.streams.service.StreamsModule.getResources(StreamsModule.java:104)
	at com.hortonworks.streamline.webservice.StreamlineApplication.registerResources(StreamlineApplication.java:293)
	at com.hortonworks.streamline.webservice.StreamlineApplication.run(StreamlineApplication.java:100)
	at com.hortonworks.streamline.webservice.StreamlineApplication.run(StreamlineApplication.java:74)
	at io.dropwizard.cli.EnvironmentCommand.run(EnvironmentCommand.java:43)
	at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:85)
	at io.dropwizard.cli.Cli.run(Cli.java:75)
	at io.dropwizard.Application.run(Application.java:79)
	at com.hortonworks.streamline.webservice.StreamlineApplication.main(StreamlineApplication.java:78)
Caused by: org.postgresql.util.PSQLException: ERROR: syntax error at or near "ON"
  Position: 112
	at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2455)
	at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2155)
	at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:288)
	at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:430)
	at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:356)
	at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:168)
	at org.postgresql.jdbc.PgPreparedStatement.executeUpdate(PgPreparedStatement.java:135)
	at com.zaxxer.hikari.pool.ProxyPreparedStatement.executeUpdate(ProxyPreparedStatement.java:61)
	at com.zaxxer.hikari.pool.HikariProxyPreparedStatement.executeUpdate(HikariProxyPreparedStatement.java)
	at com.hortonworks.streamline.storage.impl.jdbc.provider.sql.factory.AbstractQueryExecutor$QueryExecution.executeUpdate(AbstractQueryExecutor.java:221)
	... 18 more
&lt;/PRE&gt;</description>
    <pubDate>Tue, 21 Apr 2026 12:22:47 GMT</pubDate>
    <dc:creator>yjiang</dc:creator>
    <dc:date>2026-04-21T12:22:47Z</dc:date>
    <item>
      <title>Failed to Start SAM</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-SAM/m-p/211947#M63047</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I installed HDF3.0 on an existing HDP2.6.0 cluster using Ambari 2.5.1. Installation was succeed, but failed to start SAM. My configuration uses Postgresql for SAM. I got the below error. Does anyone happen to see this before?&lt;/P&gt;&lt;PRE&gt;Exception in thread "main" com.hortonworks.streamline.storage.exception.StorageException: org.postgresql.util.PSQLException: ERROR: syntax error at or near "ON"
  Position: 112
	at com.hortonworks.streamline.storage.impl.jdbc.provider.sql.factory.AbstractQueryExecutor$QueryExecution.executeUpdate(AbstractQueryExecutor.java:223)
	at com.hortonworks.streamline.storage.impl.jdbc.provider.sql.factory.AbstractQueryExecutor.executeUpdate(AbstractQueryExecutor.java:180)
	at com.hortonworks.streamline.storage.impl.jdbc.provider.postgresql.factory.PostgresqlExecutor.insertOrUpdateWithUniqueId(PostgresqlExecutor.java:150)
	at com.hortonworks.streamline.storage.impl.jdbc.provider.postgresql.factory.PostgresqlExecutor.insertOrUpdate(PostgresqlExecutor.java:69)
	at com.hortonworks.streamline.storage.impl.jdbc.JdbcStorageManager.addOrUpdate(JdbcStorageManager.java:81)
	at com.hortonworks.streamline.storage.cache.writer.StorageWriteThrough.addOrUpdate(StorageWriteThrough.java:37)
	at com.hortonworks.streamline.storage.CacheBackedStorageManager.addOrUpdate(CacheBackedStorageManager.java:68)
	at com.hortonworks.streamline.streams.catalog.service.StreamCatalogService.addOrUpdateTopologyVersionInfo(StreamCatalogService.java:262)
	at com.hortonworks.streamline.streams.service.StreamsModule.setupPlaceholderTopologyVersionInfo(StreamsModule.java:210)
	at com.hortonworks.streamline.streams.service.StreamsModule.setupPlaceholderEntities(StreamsModule.java:198)
	at com.hortonworks.streamline.streams.service.StreamsModule.getResources(StreamsModule.java:104)
	at com.hortonworks.streamline.webservice.StreamlineApplication.registerResources(StreamlineApplication.java:293)
	at com.hortonworks.streamline.webservice.StreamlineApplication.run(StreamlineApplication.java:100)
	at com.hortonworks.streamline.webservice.StreamlineApplication.run(StreamlineApplication.java:74)
	at io.dropwizard.cli.EnvironmentCommand.run(EnvironmentCommand.java:43)
	at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:85)
	at io.dropwizard.cli.Cli.run(Cli.java:75)
	at io.dropwizard.Application.run(Application.java:79)
	at com.hortonworks.streamline.webservice.StreamlineApplication.main(StreamlineApplication.java:78)
Caused by: org.postgresql.util.PSQLException: ERROR: syntax error at or near "ON"
  Position: 112
	at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2455)
	at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2155)
	at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:288)
	at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:430)
	at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:356)
	at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:168)
	at org.postgresql.jdbc.PgPreparedStatement.executeUpdate(PgPreparedStatement.java:135)
	at com.zaxxer.hikari.pool.ProxyPreparedStatement.executeUpdate(ProxyPreparedStatement.java:61)
	at com.zaxxer.hikari.pool.HikariProxyPreparedStatement.executeUpdate(HikariProxyPreparedStatement.java)
	at com.hortonworks.streamline.storage.impl.jdbc.provider.sql.factory.AbstractQueryExecutor$QueryExecution.executeUpdate(AbstractQueryExecutor.java:221)
	... 18 more
&lt;/PRE&gt;</description>
      <pubDate>Tue, 21 Apr 2026 12:22:47 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-SAM/m-p/211947#M63047</guid>
      <dc:creator>yjiang</dc:creator>
      <dc:date>2026-04-21T12:22:47Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to Start SAM</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-SAM/m-p/211948#M63048</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have exactly the same situation. Haven't find the solution yet.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jun 2017 16:03:22 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-SAM/m-p/211948#M63048</guid>
      <dc:creator>andres_koitmae</dc:creator>
      <dc:date>2017-06-16T16:03:22Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to Start SAM</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-SAM/m-p/211949#M63049</link>
      <description>&lt;P&gt;Experiencing same issue on a completely new installation. We did notice that the postgres database did contain tables, so connection is working.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jun 2017 23:44:44 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-SAM/m-p/211949#M63049</guid>
      <dc:creator>jerry_johnson</dc:creator>
      <dc:date>2017-06-16T23:44:44Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to Start SAM</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-SAM/m-p/211950#M63050</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/274/yjiang.html" nodeid="274"&gt;@yjiang&lt;/A&gt; &lt;A rel="user" href="https://community.cloudera.com/users/15382/andreskoitmae.html" nodeid="15382"&gt;@Andres Koitmäe&lt;/A&gt;&lt;P&gt; &lt;A rel="user" href="https://community.cloudera.com/users/3482/jerryjohnson.html" nodeid="3482"&gt;@Jerry Johnson&lt;/A&gt;&lt;/P&gt;&lt;P&gt;This message is usually because you are using an unsupported database version, most commonly because you installed SAM against the Ambari Database - unfortunately at this time they do not support cross-compatible versions.  &lt;/P&gt;&lt;P&gt;
For your reference, the support matrices are here: &lt;A href="https://docs.hortonworks.com/HDPDocuments/HDF3/HDF-3.0.0/bk_support-matrices/content/ch_matrices-hdf.html" target="_blank"&gt;https://docs.hortonworks.com/HDPDocuments/HDF3/HDF-3.0.0/bk_support-matrices/content/ch_matrices-hdf.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jun 2017 23:50:58 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-SAM/m-p/211950#M63050</guid>
      <dc:creator>dchaffey</dc:creator>
      <dc:date>2017-06-16T23:50:58Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to Start SAM</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-SAM/m-p/211951#M63051</link>
      <description>&lt;P&gt;After re-configured SAM against Postgresql 9.6, this error is gone. However, I got another error while starting SAM.&lt;/P&gt;&lt;PRE&gt;Exception in thread "main" com.hortonworks.streamline.storage.exception.StorageException: com.google.common.util.concurrent.UncheckedExecutionException: com.hortonworks.streamline.storage.exception.StorageException: org.postgresql.util.PSQLException: ERROR: relation "topology_version" does not exist
  Position: 15
	at com.hortonworks.streamline.storage.cache.impl.GuavaCache.get(GuavaCache.java:72)
	at com.hortonworks.streamline.storage.cache.impl.GuavaCache.get(GuavaCache.java:41)
	at com.hortonworks.streamline.storage.CacheBackedStorageManager.get(CacheBackedStorageManager.java:74)
	at com.hortonworks.streamline.streams.catalog.service.StreamCatalogService.getTopologyVersionInfo(StreamCatalogService.java:245)
	at com.hortonworks.streamline.streams.service.StreamsModule.setupPlaceholderTopologyVersionInfo(StreamsModule.java:202)
	at com.hortonworks.streamline.streams.service.StreamsModule.setupPlaceholderEntities(StreamsModule.java:198)
	at com.hortonworks.streamline.streams.service.StreamsModule.getResources(StreamsModule.java:104)
	at com.hortonworks.streamline.webservice.StreamlineApplication.registerResources(StreamlineApplication.java:293)
	at com.hortonworks.streamline.webservice.StreamlineApplication.run(StreamlineApplication.java:100)
	at com.hortonworks.streamline.webservice.StreamlineApplication.run(StreamlineApplication.java:74)
	at io.dropwizard.cli.EnvironmentCommand.run(EnvironmentCommand.java:43)
	at io.dropwizard.cli.ConfiguredCommand.run(ConfiguredCommand.java:85)
	at io.dropwizard.cli.Cli.run(Cli.java:75)
	at io.dropwizard.Application.run(Application.java:79)
	at com.hortonworks.streamline.webservice.StreamlineApplication.main(StreamlineApplication.java:78)

&lt;/PRE&gt;</description>
      <pubDate>Mon, 19 Jun 2017 11:20:44 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-SAM/m-p/211951#M63051</guid>
      <dc:creator>yjiang</dc:creator>
      <dc:date>2017-06-19T11:20:44Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to Start SAM</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-SAM/m-p/211952#M63052</link>
      <description>&lt;P&gt;After manually executed /usr/hdf/current/streamline/bootstrap/sql/postgresql/create_tables.sql, I was able to start SAM successfully.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jun 2017 12:16:37 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-SAM/m-p/211952#M63052</guid>
      <dc:creator>yjiang</dc:creator>
      <dc:date>2017-06-19T12:16:37Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to Start SAM</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-SAM/m-p/211953#M63053</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/274/yjiang.html" nodeid="274"&gt;@yjiang&lt;/A&gt;&lt;P&gt;Glad to hear it's working - there should be a couple of bash scripts in /usr/hdf/current/streamline/bootstrap that are better to use than the sql directly - as it also creates the UDFs and roles and whatnot.  

I'd suggest you run ./bootstrap-storage.sh drop-create  and then ./bootstrap.sh   to ensure you have a clean install.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jun 2017 14:42:22 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-SAM/m-p/211953#M63053</guid>
      <dc:creator>dchaffey</dc:creator>
      <dc:date>2017-06-19T14:42:22Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to Start SAM</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-SAM/m-p/211954#M63054</link>
      <description>&lt;P&gt;Thanks &lt;A rel="user" href="https://community.cloudera.com/users/2662/dchaffey.html" nodeid="2662"&gt;@Dan Chaffelson&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Executed the scripts without error. Was able to start SAM and import an application. Cool!&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jun 2017 18:07:59 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Failed-to-Start-SAM/m-p/211954#M63054</guid>
      <dc:creator>yjiang</dc:creator>
      <dc:date>2017-06-19T18:07:59Z</dc:date>
    </item>
  </channel>
</rss>

