Errors or warnings appear when importing Postgres database dump

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the server and data center platforms.


When importing a Postgres database dump from a Bamboo Cloud export, errors or warnings such as the following appear:

ERROR:  relation "public.plan_dependencies" does not exist
ERROR:  index "vrs_status_idx" does not exist
ERROR:  table "AO_C7F71E_OAUTH_SVC_PROV_TKNS" does not exist
ERROR:  sequence "AO_A0B856_WEB_HOOK_LISTENER_AO_ID_seq" does not exist
ERROR:  must be owner of language plpgsql
ERROR:  must be owner of schema public
ERROR:  schema "public" already exists
ERROR:  language "plpgsql" already exists
ERROR:  role "bamboo_ro"
WARNING:  no privileges could be revoked for "public"
WARNING:  no privileges were granted for "public"

Note: if you see the following errors (note the numbers after the user) instead, you've run into a different issue:

ERROR: role "bamboo_12345" does not exist
ERROR: role "bamboo_12345" does not exist
ERROR: role "bamboo_ro_12345_1" does not exist

(where 12345 may be any random string of numbers). If you see these errors, please instead follow the steps listed on  BAM-18060 - Getting issue details... STATUS


When importing a db dump into Postgres, it will try to remove any existing data from the destination database to ensure a clean import. If the destination database is empty, these errors and warnings will appear.


This is expected behaviour during an import of a database dump and can safely be ignored.

Note: If you see errors different from the examples listed above, you should contact Atlassian Support


Last modified on Dec 21, 2016

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.