The problem doesn't occur in MaxDB version Linux 64bits 7.8.02.35
It only occurs in MaxDB version Linux 64bits 7.8.02.37
How can i report the bug, so that it can be corrected in next MaxDb release ?
Thanks for answer
The problem doesn't occur in MaxDB version Linux 64bits 7.8.02.35
It only occurs in MaxDB version Linux 64bits 7.8.02.37
How can i report the bug, so that it can be corrected in next MaxDb release ?
Thanks for answer