<?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>topic Backing up and restoring geodatabases in PostgreSQL in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/backing-up-and-restoring-geodatabases-in/m-p/528519#M29974</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I try to establish a workflow to backup und restore geodatabases in postgreSQL.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The instructions in the article &lt;/SPAN&gt;&lt;A href="http://support.esri.com/en/knowledgebase/techarticles/detail/36522" rel="nofollow noopener noreferrer" target="_blank"&gt;http://support.esri.com/en/knowledgebase/techarticles/detail/36522&lt;/A&gt;&lt;SPAN&gt; are unapplicable for SDE 10 and postgres 8.4 . pg_restore throws a lot of errors while importing.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So far dumping the public schema seperatly from the rest of the database works.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;PRE class="lia-code-sample line-numbers language-none"&gt;pg_dump -n public -Fc &amp;gt; sde_public.dump
pg_dump -N public -Fc &amp;gt; sde_etc.dump
dropdb sde
ceatedb sde
echo "alter database sde set search_path = E'\$user',public,sde;" | psql
pg_restore --disable-triggers sde_public.dump
pg_restore --disable-triggers sde_etc.dump&lt;/PRE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;while importing the dump following error occurs for each featrue class in the user schema:&lt;/SPAN&gt;&lt;BR /&gt;&lt;PRE class="lia-code-sample line-numbers language-none"&gt;pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 2432; 1259 59311 INDEX a2_ix1_a brdt
pg_restore: [archiver (db)] could not execute query: ERROR:&amp;nbsp; permission denied for schema sde
LINE 1: SELECT srid FROM SDE.ST_GEOMETRY_COLUMNS WHERE&amp;nbsp; lower(OWNER_...
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ^
QUERY:&amp;nbsp; SELECT srid FROM SDE.ST_GEOMETRY_COLUMNS WHERE&amp;nbsp; lower(OWNER_NAME) = lower('brdt') AND&amp;nbsp; lower(DATABASE_NAME) = lower('sde') AND&amp;nbsp; lower(SCHEMA_NAME) =e')
&amp;nbsp;&amp;nbsp;&amp;nbsp; Command was: CREATE INDEX a2_ix1_a ON a7 USING gist (shape);&lt;/PRE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Access the sde in arccatalog / arcmap works, but i think the missing indexes have an impact on the performace of the sde instance. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;After some investigation i found that the broken sql is hard coded in the st_geometry.so used by the postgres binary. Of course, there are some dirty workarounds for that problem but for a clean backupworkflow they are not acceptable.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any suggestions would help.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thomas&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 11 Dec 2021 23:01:03 GMT</pubDate>
    <dc:creator>ThomasJurk</dc:creator>
    <dc:date>2021-12-11T23:01:03Z</dc:date>
    <item>
      <title>Backing up and restoring geodatabases in PostgreSQL</title>
      <link>https://community.esri.com/t5/data-management-questions/backing-up-and-restoring-geodatabases-in/m-p/528519#M29974</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I try to establish a workflow to backup und restore geodatabases in postgreSQL.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The instructions in the article &lt;/SPAN&gt;&lt;A href="http://support.esri.com/en/knowledgebase/techarticles/detail/36522" rel="nofollow noopener noreferrer" target="_blank"&gt;http://support.esri.com/en/knowledgebase/techarticles/detail/36522&lt;/A&gt;&lt;SPAN&gt; are unapplicable for SDE 10 and postgres 8.4 . pg_restore throws a lot of errors while importing.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So far dumping the public schema seperatly from the rest of the database works.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;PRE class="lia-code-sample line-numbers language-none"&gt;pg_dump -n public -Fc &amp;gt; sde_public.dump
pg_dump -N public -Fc &amp;gt; sde_etc.dump
dropdb sde
ceatedb sde
echo "alter database sde set search_path = E'\$user',public,sde;" | psql
pg_restore --disable-triggers sde_public.dump
pg_restore --disable-triggers sde_etc.dump&lt;/PRE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;while importing the dump following error occurs for each featrue class in the user schema:&lt;/SPAN&gt;&lt;BR /&gt;&lt;PRE class="lia-code-sample line-numbers language-none"&gt;pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 2432; 1259 59311 INDEX a2_ix1_a brdt
pg_restore: [archiver (db)] could not execute query: ERROR:&amp;nbsp; permission denied for schema sde
LINE 1: SELECT srid FROM SDE.ST_GEOMETRY_COLUMNS WHERE&amp;nbsp; lower(OWNER_...
&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; ^
QUERY:&amp;nbsp; SELECT srid FROM SDE.ST_GEOMETRY_COLUMNS WHERE&amp;nbsp; lower(OWNER_NAME) = lower('brdt') AND&amp;nbsp; lower(DATABASE_NAME) = lower('sde') AND&amp;nbsp; lower(SCHEMA_NAME) =e')
&amp;nbsp;&amp;nbsp;&amp;nbsp; Command was: CREATE INDEX a2_ix1_a ON a7 USING gist (shape);&lt;/PRE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Access the sde in arccatalog / arcmap works, but i think the missing indexes have an impact on the performace of the sde instance. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;After some investigation i found that the broken sql is hard coded in the st_geometry.so used by the postgres binary. Of course, there are some dirty workarounds for that problem but for a clean backupworkflow they are not acceptable.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any suggestions would help.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thomas&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Dec 2021 23:01:03 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/backing-up-and-restoring-geodatabases-in/m-p/528519#M29974</guid>
      <dc:creator>ThomasJurk</dc:creator>
      <dc:date>2021-12-11T23:01:03Z</dc:date>
    </item>
    <item>
      <title>Re: Backing up and restoring geodatabases in PostgreSQL</title>
      <link>https://community.esri.com/t5/data-management-questions/backing-up-and-restoring-geodatabases-in/m-p/528520#M29975</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try granting following permission to public from pgadmin:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="font-size: small; font-family: Arial;"&gt;GRANT USAGE ON SCHEMA sde TO public;&lt;BR clear="none" /&gt;&lt;BR clear="none" /&gt;&lt;/STRONG&gt;&lt;SPAN style="font-family: Arial;"&gt;&lt;SPAN style="font-size: small;"&gt; and&lt;BR clear="none" /&gt;&lt;BR clear="none" /&gt;&lt;/SPAN&gt;&lt;SPAN style="font-size: small;"&gt; restore the user_schema once again.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: small; font-family: Arial;"&gt;Hope this helps!&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Nov 2017 00:44:07 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/backing-up-and-restoring-geodatabases-in/m-p/528520#M29975</guid>
      <dc:creator>ManviLather1</dc:creator>
      <dc:date>2017-11-17T00:44:07Z</dc:date>
    </item>
  </channel>
</rss>

