Von: Nils Petter Bjørge [mailto:[EMAIL PROTECTED] > > This error didn't appear in the beginning, and I suspect the > growing numbers of backup medias to be the reason. > > When I list the Backup history, I get the list up and all > backups have run and new backup mediums are created > continiually(scheduled script). So that is OK and everything > runs fine like in Jan-Hendrik Lendholt's case, but... > > When I try to open Backup Medium in DBMGUI, I get Error > -24987 (packet_size to small) > When I tried to change _PACKET_SIZE value in DBMGUI, ...
Hello Nils, the communication packet between the DBMServer and a DBMClient has a limit. For DBMServer commands which may produce a large amount of data (like sql_execute or backup_history_list) we have implemented a "fetch" command (sql_fetch, backup_history_listnext). For the command medium_getall unfortunately no "fetch" command exists. If the amount of data (the number of media definitions) exeeds the size of the communication packet the error "-24987, ERR_TOOSMALL: packet size too small for answer" will occur. Please decrease your number of media definitions with the DBMServer command medium_delete or edit the file <rundirectory>/dbm.mmm. Also you should change your backup strategy to avoid the growth of the media definitions. Regards Bernd PS: The database parameter _PACKET_SIZE does not matter in this area. -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
