>>>>> On Wed, 28 Dec 2005 11:39:20 -0500, Brian Keifer <[EMAIL PROTECTED]> said:

  Brian> We have a client that requires lower_case_table_names=1 in their mysqld
  Brian> configuration.  When I try to run a job, I get the following output:

  Brian> *run
  Brian> A job name must be specified.
  Brian> The defined Job resources are:
  Brian>      1: clientdb1
  Brian>      2: BackupCatalog
  Brian>      3: Monitoring
  Brian>      4: RestoreFiles
  Brian> Select Job resource (1-4): 1
  Brian> Run Backup job
  Brian> JobName:  clientdb1
  Brian> FileSet:  Full Set
  Brian> Level:    Incremental
  Brian> Client:   clientdb1-fd
  Brian> Storage:  File
  Brian> Pool:     Default
  Brian> When:     2005-12-28 11:17:57
  Brian> Priority: 10
  Brian> OK to run? (yes/mod/no): yes
  Brian> Job failed.
  Brian> You have messages.
  Brian> *m
  Brian> 28-Dec 11:17 clientdb1-dir: clientdb1.2005-12-28_11.17.58 Fatal error:
  Brian> sql_create.c:91 sql_create.c:91 insert INSERT INTO Job
  Brian> (Job,Name,Type,Level,JobStatus,SchedTime,JobTDate) VALUES
  Brian> ('clientdb1.2005-12-28_11.17.58','clientdb1','B','I','C','2005-12-28
  Brian> 11:17:57',1135786677) failed:
  Brian> Field 'ClientId' doesn't have a default value
  Brian> 28-Dec 11:17 clientdb1-dir: sql_create.c:91 INSERT INTO Job
  Brian> (Job,Name,Type,Level,JobStatus,SchedTime,JobTDate) VALUES
  Brian> ('clientdb1.2005-12-28_11.17.58','clientdb1','B','I','C','2005-12-28
  Brian> 11:17:57',1135786677)
  Brian> 28-Dec 11:17 clientdb1-dir: clientdb1.2005-12-28_11.17.58 Fatal error:
  Brian> sql_create.c:93 Create DB Job record INSERT INTO Job
  Brian> (Job,Name,Type,Level,JobStatus,SchedTime,JobTDate) VALUES
  Brian> ('clientdb1.2005-12-28_11.17.58','clientdb1','B','I','C','2005-12-28
  Brian> 11:17:57',1135786677) failed. ERR=Field 'ClientId' doesn't have a 
default value

  Brian> The errors don't necessarily point directly to the case difference, 
but it's the
  Brian> only thing that's different on this machine from all our other 
directors.  Is
  Brian> this MySQL setting just something that Bacula can't deal with, or is 
there a
  Brian> config option I'm missing that would let us work around this?

I think the setting of "strict mode" in the MySQL config is a possible reason
for this error.

__Martin


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to