PEM: Error in REINDEX DATABASE PEM

Highlighted
Level 3 Adventurer

PEM: Error in REINDEX DATABASE PEM

Hi,

After fixing corrupted data in pem.alert and pem.alert_status(see previous post)

pem=# reindex (verbose) table  pem.alert;

ERROR:  failed to find parent tuple for heap-only tuple at (290,6) in table "alert"

pem=# delete from pem.alert where ctid = '(290,6)';

DELETE 1

pem=# reindex (verbose) table  pem.alert;

INFO:  index "alert_pkey" was reindexed

DETAIL:  CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s

INFO:  index "alert_name_object_type_uniq" was reindexed

DETAIL:  CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s

INFO:  index "pg_toast_19174_index" was reindexed

DETAIL:  CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s

Now I get another error in:

pem=# reindex (verbose) database pem;

I get this error:

ERROR:  could not create unique index "probe_schedule_pkey"
DETAIL:  Key (probe_id, parameter_value_list)=(19, {12,postgres}) is duplicated.

Kindly,

Polem

 

PS:

Turnoff 5432 port to block all agent during the REINDEX command to validate all data

Archived Discussions


Effective March 31st, we will no longer engage on PostgresRocks.


How to engage with us further?


  • Thought Leadership: EDB Blogs

  • Tips and Tricks: Postgres Tutorials

  • Customer Support: Create a Case Please note: Only customers with an active EDB support subscription and support portal authorization can create support ticket

  • Engage on Stackoverflow While engaging on Stackoverflow tag the question with EDB or EnterpriseDB.

2 REPLIES 2
Highlighted
Level 3 Adventurer

Re: PEM: Error in REINDEX DATABASE PEM

Hi,

I was able to delete the duplicate records but now I found errors in pemdata.index_statistics.

Can I truncate this table?

 

Kindly

Polem

Highlighted
EDB Team Member

Re: PEM: Error in REINDEX DATABASE PEM

Hi Paul,

 

As you are facing corruption in your PEM database which is mentioned via PostgresRocks another thread.

i.e. : https://postgresrocks.enterprisedb.com/t5/Postgres-Tools/Error-in-PEM-worker-on-PEM-server/m-p/2320#...

 

Where we have requested you re-setup the PEM instead of truncating alerts table. As it is not recommended.

 

Hope this answers your question.

Regards,
Dhananjay

© 2019 EnterpriseDB Corporation. All rights reserved.   |   Privacy Policy   |  Terms of Use   |   Trademarks