Hi

While running the session ticpr2260m000, i am getting an error

PRODUCTION CTF - Erreur fatale: Error 254 (Commit transaction has failed in the audit server) on ticpr170600 in commit_trans

While checking the logs i found out this message

2010-04-08[11:22:21]:E:bsp: Log_mesg: Reached maximum audit records/table per
2010-04-08[11:22:21]:E:bsp: transaction. Session ticpr2260m000, table ticpr17060
0 Limit = 32767. ABORT !!!

I have checked for AUDIT_MAX_ROWS in $BSE/lib/defaults/all but could not find it.


Anybody with an insight.

Regards
Shinoj

Hi

While running the session ticpr2260m000, i am getting an error

PRODUCTION CTF - Erreur fatale: Error 254 (Commit transaction has failed in the audit server) on ticpr170600 in commit_trans

While checking the logs i found out this message

2010-04-08[11:22:21]:E:bsp: Log_mesg: Reached maximum audit records/table per
2010-04-08[11:22:21]:E:bsp: transaction. Session ticpr2260m000, table ticpr17060
0 Limit = 32767. ABORT !!!

I have checked for AUDIT_MAX_ROWS in $BSE/lib/defaults/all but could not find it.


Anybody with an insight.

Regards
Shinoj

Hello,

check entry in $BSE/lib/audit_spec

Purge old sequences may help.

Regards

This is the entry

*:*:TOSEQ 999 SECURITY 28 MAXSEQSIZE 2048K

Purging didnt help.

Hi

Should i alter the sequence to some value or any other solution

Regards

This is part of session help in ERP LN:
The audit data is stored per transaction. If a single transaction generates too much data to be stored in a sequence file, the transaction is aborted. Therefore, the sequence file size must enable you to store transactions that involve many changes in a table, for example, an update of all fields in several columns.
So, I think you can solve your problem if you change MAXSEQSIZE. Don't edit file audit_spec, use session ttaud3135m000 in ERP LN or ttaad4160m000 ii Baan IV.

Hi

I have tried increasing the sequence in the Audit_spec file to more than 10 times but still getting the same error.

2010-07-21[11:00:24]:E:bsp: Log_mesg: Reached maximum audit records/table per
2010-07-21[11:00:24]:E:bsp: transaction. Session ticpr2260m000, table ticpr17060
0 Limit = 32767. ABORT !!!

Looks like the limit which is being considered is still not being updated.

Regards

Just a thought....

Could it be that your change won't become effective until all users disconnect/server is restarted?

Ed:confused:

Nothing works really . :rolleyes:

Hello,
If purge the old audit files not work, and you can´t change the file size, then rename the $BSE/audit directory to audit.old

Then when a new sequence comes, the directory will be created and the audit files will start to grow.

Good luck.

Finally its concluded that it is because of Porting Sets that the value is set and it AUDIT_MAX doesn't exist as a parameter anywhere. And the value is hardcoded. And the hardcoded value is because of the existing version of Porting Sets and if an enhancement occurs the value would be changed.

And that value was hardcoded as a signed 2 byte entity. hence it the maximum value which could have been set was 32767.

Thanks for everybody who has contributed.