on 01-10-2011 1:09 PM
Hi,
we are recreating some triggers that have the function to write the changes in tables, like an audit table that compares if NEW.value is different from OLD.value then we insert that in some table.
something like:
VAR AGORA TIMESTAMP;
SET AGORA = NOW();
TRY
IF NEW.CFOP != OLD.CFOP THEN
INSERT INTO DBUSER.SYSHISTORICO (DATA_OCORRENCIA, OPERACAO, MY_OBJETO, ID_CLASSE, ID_CAMPO, INT_ANTIGO) VALUES (:AGORA, 2, :OLD.OID, 3001, 2, :OLD.CFOP);
CATCH
IF $RC != 100
THEN STOP ($RC, 'unexpected error');
then today, when we dropped all triggers and reacreated with some new attributes (more IFs sentences as we added new fields to application), we are getting the error:
: System error: bd_page_collision
I cant find anything about it inside documentation or on this forum, the MaxDB version is 7.6.06.10
any idea?
Best regards
Clóvis
Hi Clóvis,
this error means that there is a corruption in the internal page management of your database instance.
It has nothing to do with your procedure (well, let's say it really shouldn't have anything to do with it...).
Please run a CHECK DATA WITH UPDATE in ADMIN mode to fix this.
Afterwards the problem shouldn't be repdoducible.
regards,
Lars
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.