RyanRussell
Member
Registered:1467280638 Posts: 12
Posted 1566383886
· Edited
Reply with quote
#1
We already know that orphaned (or ghost) folders in the EFOLDER table are a thing and we know what causes them but does anyone know what the cause of the same thing in the process tables is? It was just highlighted to me the other day by a colleague when he was exploring the database via some new analytics tools we have access to. One of our processes is called the AFA process and looking into the AFA table reveals a fair amount of records that don't have a matching record in the EFOLDER table. I was pretty surprised when he pointed them out so went and checked another process and it was happening there too. Other than the EFOLDERID and the default values for non-null fields the records are completely blank. Anyone else saw this and know the cause? It doesn't appear to be the same cause as the ones in the EFOLDER table (caused by users raising and not submitting). Here is the query I'm using to check the tables in case it is of use to anyone (or wrong!):SELECT * FROM METASTORM . AFA WHERE EFOLDERID NOT IN (SELECT EFOLDERID FROM METASTORM . EFOLDER );
BMellert
Guru
Registered:1225130168 Posts: 688
Posted 1566910565
Reply with quote
#2
Presuming someone isn't deleting eFolder records outside of the Admin tool (or related stored procedure), and that AFA is a process table (which you state is), I've never seen this before, and I'm not quite sure how it would be created. Do any errors show in eLog or the Windows server logs that may shed some light?
RyanRussell
Member
Registered:1467280638 Posts: 12
Posted 1569333110
Reply with quote
#3
Hey BMellert, Sorry for the late reply. I'll have a look when I've a little down time, it isn't causing any issues and was just a curiosity I was wondering if anyone else had saw, not really something I want to actively investigate.