Need help to resolve archive, purge related issues deu to old indexing rule.

General
, ,
1

I enabled archive process (using 3 jobs first and then using pyPegaArchiverUsingPipeline job) and it was working fine at first. But now I can see some logs are generated due to an index rule we had. I think this issue started with pyPegaArchiverUsingPipeline job.

But now though I stopeed this and enabled 3 old jobs, still logs are getting generated.

Currently this index rule is withdrawn, index rule related database table also doesn’t have any record. I deleted this table after this error.

When I went through some data class instances related to archive process, we can see some records for this index rule under my work classes. (Data-ArchivalClassDependency class has these index related instances. I deleted them, but not deleting, again it is getting created automatically. )

How do we resolve this issue?

Data-ArchivalMetadata has so many records with Object Class as this index class.

Ex:

Data-ArchivalClassDependency

Class name Dependency Name
Org-ABC-MyApp-Work-Correspondence Index-Org-Data-Issues Org-ABC-MyApp-Work-Correspondence Index-Org-Data-Issues

Data-ArchivalMetadata

Object Class Ins Key of the instance Parent Ins Key of the instance Name
Index-Org-Data-Issues ORG-ABC-MYAPP-WORK COR-9003 ORG-ABC-MYAPP-WORK COR-9003 Org-ABC-MyApp-Work-Correspondence ORG-ABC-MYAPP-WORK COR-9003 Index-Org-Data-Issues
Index-Org-Data-Issues ORG-ABC-MYAPP-WORK COR-9002 ORG-ABC-MYAPP-WORK COR-9002 Org-ABC-MyApp-Work-Correspondence ORG-ABC-MYAPP-WORK COR-9002 Index-Org-Data-Issues

I would like to have a call regarding this from some Pega resource. Please let me know if I have to add this in company support portal.

2

@Dhanusha regarding your comments 'I would like to have a call regarding this from some Pega resource. Please let me know if I have to add this in company support portal. ’

→ Please familiarize yourself with the How to Get Support processes.

  1. You need to have an email that is affiliated to a recognized licensed company domain (My Support Portal FAQ)

  2. You need your Account Administrator to affiliate you. (Administering Support Accounts)

Details of what constitutes a valid support incident and timeframes of SLA are described in our MSP FAQ pages. Please make sure you follow the processes .

General information about your Pega Account can be found on the ‘About My Pega’ FAQ page.

3

@MarijeSchillern

I just trying to get some help without adding the details to support portal. It seems that is not possible. That is okay.

Anyway, I could fix this issue using below steps.

  1. Still declare index is withdrawn.
  2. But I created data table instance and table in DB to match with old table name. (In the logs I could find out which table is looking for in purge process).
  3. After that, purging was working as expected.

But still I m thinking why it is checking for this index class records when that is already withdrawn. That question is still open, but I resolved my blocker.