Francesco
29th November 2005, 20:49
In all my years, I have never noticed this before. Some SOX compliance audit trail let me to this awkward discovery.
Apparently exchange attempts to create every table it imports to. Because in most cases the table already exists, it returns an Oracle code 955 and merrily polutes the audit log.
It leads me to believe that there is some very sloppy programming inside the tu module (at least in our backdated version). The code _always_ attempts to create the table and just lets the database handle the consequences if it already exists.
First line Baan support plays possum on this issue. Has anybody dealt with this? Are there tu updates available that will fix the problem? I didnt see any reference in the KB.
Apparently exchange attempts to create every table it imports to. Because in most cases the table already exists, it returns an Oracle code 955 and merrily polutes the audit log.
It leads me to believe that there is some very sloppy programming inside the tu module (at least in our backdated version). The code _always_ attempts to create the table and just lets the database handle the consequences if it already exists.
First line Baan support plays possum on this issue. Has anybody dealt with this? Are there tu updates available that will fix the problem? I didnt see any reference in the KB.