21-10-22 07:55 AM
We wanted to delete all logs in the test system (is an older copy from the production system)
Interestingly enough, fragments still remain in the database afterwards.
In the table BPASessionLog_NonUnicode there are 170 entries belonging to 2 session numbers
In the table BPASessionLog_NonUnicode_pre65 there are 14000 entries belonging to 12 session numbers.
(Another question, what is the pre65 table, what does it mean?)
In any case, there are 14 entries in the session table BPASession, all of which have the same status ID. Statusid = 5 (debugging).
Our guess is that Blue Prism probably crashed here while debugging.
Why is this data still available and can it also be deleted?
When I do a delete command on the session table:
delete from BPASession;
I get an error in SQL:
DELETE failed because the following SET options have incorrect settings: 'ANSI_NULLS, QUOTED_IDENTIFIER, CONCAT_NULL_YIELDS_NULL, ANSI_WARNINGS, ANSI_PADDING'. Verify that SET options are correct for use with
21-10-22 02:56 PM
24-10-22 09:51 AM