Hi
We are getting the following Error.
Error 254: Committ transaction has failed in audit server) on commit_trans.
I believe this is because there is no sufficient space in the Baan server.
I have purged the audit file by running the session Purge Audit files
(ttaad4161m000) by selecting all the companies in the range (except companies like 000.
However it has given us only a few MB of space.Previously when I ran the session(3 monts back) we got almost 1.2gb space.
Please help me in finding a solution. Presently Audit folder shows the space as 850mb.
Regards
Django

Hi there,


254 EAUDABORT

Commit transaction has failed in the audit server action: see log.audit file for more information


log.audit should be found at $BSE/log




I believe this is because there is no sufficient space in the Baan server.



Is there or isn't there space on your disk left?


However it has given us only a few MB of space.Previously when I ran the session(3 monts back) we got almost 1.2gb space.


As audit information are condensed to the maximum, this sounds reasonable. The 1,2 GB had been gathered for which time interval? (When did you delete last before these 3 month?)
Audit is turned on for which tables?

good luck

Norbert

Hi Norbert
3 months back when we purged audit files we got around 1.5GB, this was after an interval of perhaps 1 year,after that we have done this a couple of times.
1 week back we faced this problem & found that space had come down to just 3MB.
On purging the audit file we got just 150MB.
After 4 days the space again reduced to 2MB & we repeated the process, but this time we got just 60MB. I believe even if I purge the files now I would get only a few MB of space.
At present I have only around 90MB space.
Audit is turned ON for almost all tables. All standard tables have audit on.
Regards
Django

Hi django,

have a look at the max file size with ttaad4560m000. Audit information is added to sequential files per table upto the max file size value, then the next file will be created.
The current sequence cannot be deleted, so a large max file size has disadvantages.

For the file tiitm001 in company 777 you will find files like:
$BSE/audit/777/atiitm/aitm001777.000
$BSE/audit/777/atiitm/aitm001777.001
.
.
$BSE/audit/777/atiitm/aitm001777.nnn and
$BSE/audit/777/atiitm/aitm001777.inf,
nnn beeing the sequence actually in use and
the .inf file will have information about the file and current sequenc (I guess).

By taking a closer look on $BSE/audit and its subdirectories you can find out which tables consume the most space.

Anyway, if you delete audit files on a regular base, one has to ask why you audit in the first place.

It is rather unusual to audit "almost all files", especially the tf files are altered very often.
For the files like the item master I would strongly suggest to exclude certain fields from audit, like tiitm001.ltdt (last change of stock) and suchlike, as these fields are altered very very often and there is no gain in monitoring these changes.

To specify whether fields should be excluded from audit, use session ttadv4127s000, don't forget to convert to runtime.
Keep in mind that if you change the DD, another audit sequence will start too.


hth

Norbert