Pivotal Knowledge Base

Follow

GPCRONDUMP Error: "StatusFileError" with "Schema with <OID> does not Exist"

Environment

 Product  Version
 Pivotal Greenplum    4.3.x, 4.2.x

Symptom

gpcrondump generates an error message as shown below:

20140826:16:16:18:064177 gpcrondump:mdw:gpadmin-[ERROR]:-
Traceback (most recent call last):
File "/usr/local/greenplum-db/lib/python/gppylib/commands/base.py", line 202, in run
self.cmd.run()
File "/usr/local/greenplum-db/lib/python/gppylib/operations/__init__.py", line 49, in run
self.ret = self.execute()
File "/usr/local/greenplum-db/lib/python/gppylib/operations/utils.py", line 52, in execute
raise ret
StatusFileError
20140826:16:16:18:064177 gpcrondump:mdw:gpadmin-[DEBUG]:-[worker3] finished cmd with exception: Remote(PostDumpSegment)
20140826:16:16:18:064177 gpcrondump:mdw:gpadmin-[DEBUG]:-cgppylib.operations.dump
StatusFileError

Cause

There are catalog data errors at the segment instance. The pg_class is referring to a relation under a schema which doesn't exist on the pg_namespace table:

20140826:16:16:02|gp_dump_agent-[INFO]:-Starting monitor thread
20140826:16:16:03|gp_dump_agent-[INFO]:-Dumping database "eds"...
20140826:16:16:03|gp_dump_agent-[INFO]:-reading schemas
20140826:16:16:03|gp_dump_agent-[INFO]:-reading user-defined functions
20140826:16:16:03|gp_dump_agent-[INFO]:-reading user-defined types
20140826:16:16:04|gp_dump_agent-[INFO]:-TASK_SET_SERIALIZABLE
20140826:16:16:08|gp_dump_agent-[ERROR]:-schema with OID 35310820 does not exist
20140826:16:16:08|gp_dump_agent-[ERROR]:-*** aborted because of error:
20140826:16:16:08|gp_dump_agent-[ERROR]:-*** aborted because of error:

Resolution

Find a maintenance window, run gpcheckcat, and then fix catalog errors one-by-one. gpcrondump would then complete successfully.

Comments

Powered by Zendesk