RE: Problem with external backup ID's
"Heinrich, Tilo" <[email protected]>
| Newsgroups | gmane.comp.db.maxdb |
|---|---|
| Message-ID | <[email protected]> |
Hello Spiker, You have to set the parameter NSR_SAVETIMEFORMAT in your configuration file for NetWorker to "dd.mm.yyyy HH:MM:SS". See also http://dev.mysql.com/doc/maxdb/en/62/aba9ac444311d5992400508b6b8b11/frameset.htm for a detailed description. You do not have to restart the database or even the DBM Server after the change. Best regards, Tilo Heinrich SAP Labs Berlin -----Original Message----- From: [email protected] Sent: Mittwoch, 7. Februar 2007 09:06 To: [email protected] Subject: Problem with external backup ID's Hello, we are using the external backup tool networker. Since an upgrade of the networker client to version 7 the MaxDB (7.6.00.12) can't get the external backup id's. In dbm.ebp are entries as below: ______________________________________ The line 'MAXDB:MAXDB03_on_php02 0 4 01.02.2007 19:00:03 23796068 1170352803' is ignored, as it does not have a date/time of the format yyyy/mm/dd HH:MM:SS AM. The line 'MAXDB:MAXDB03_on_php02 0 4 02.02.2007 19:00:03 29105456 1170439203' is ignored, as it does not have a date/time of the format yyyy/mm/dd HH:MM:SS AM. The line 'MAXDB:MAXDB03_on_php02 0 3 03.02.2007 14:00:02 2301457372 1170507602' is ignored, as it does not have a date/time of the format yyyy/mm/dd HH:MM:SS AM. ______________________________________ In dbm.ebf the backup's are documented correctly. Changing the extended parameter DATE_TIME_FORMAT to other possibilities (with database restart) doesn't fix the problem. The currently value is INTERNAL. Regards, Spiker -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[email protected]