Inserting a Duplicate Entries in ZTABLE

  Hi,
I have Created a ZTABLE in that ztable having company code, sales org, employee no, from date , to date  and amount fields
ZTABLE PRIMARY KEY FIELDS IS COMPANY CODE AND SALES ORG.
now my requirement is to add 2 entries in a z table  same( employee company code and sales org).
i have developed a module pool program to  enter the data by using table control.
my logic is to insert the data from program to ztable
loop at it_emp into wa_emp.
insert zemp from wa_emp.
endloop.
Please give some suggestions to insert duplicate entries.

The primary key are defined as UNIQUE and NOT NULL. So you cannot have two records with same keys, you MUST add another key so I suggest add a flag for "Employee to Bill" and "Employee Mobile Bill", you can define a domain with those two values to define a data element and add that data element in your table, defining this "Employee type" field as the last key of the primary keys of the table (and do not forget to set the client as the fist key)
K
Field
Data Element
Check table
K
MANDT
MANDT
T000
K
BUKRS
BUKRS
T001
K
VKORG
VKORG
TVKO
K
Z-name
Z-name
Regards,
Raymond

Similar Messages

  • Insert - Ignore Duplicate Entry Error

    Hello
    I would like to use an insert statement which also contains a select statement in it and returns a set of records and gets inserted in to a particular table.
    But, when I tried to run the sql, it throws error as some of the records are duplicate entry insertions. Is it possible to modify the sql to ignore any duplicate entries and insert the new ones.
    Illustration:
    TABLE_A
    STUDENT_ID GROUP_ID
    101 200
    101 201
    103 200
    107 201
    and so on.
    Here, when I try to insert a set of records like
    101 200
    108 200
    101 300
    103 200
    103 201
    I would like the exact duplicate entries like (101,200), (103,200) to be ignored with out producing any error but insert the other records in to the TABLE_A table.
    Thr sql used is similar to this
    Insert into TABLE_A (student_id, group_id)
    select distinct person.studentid, groups.groupid from person, groups where
    Did any one know how to handle this?
    Thanks
    Shiv

    If I include 'NOT EXISTS' after insert and before
    select statement, it throws the error
    missing VALUES keyword
    The NOT EXISTS goes in the WHERE clause.
    Insert into Table_A (student_id, group_id)
    select distinct p.studentid, g.groupid
    from person p, group g
    where NOT EXISTS (select 1
                     from table_A a
                     where a.student_id = p.studentid
                     and a.group_id = g.groupid)or you could do
    Insert into Table_A (student_id, group_id)
    select distinct p.studentid, g.groupid
    from person p, group g
    MINUS
    select student_id, group_id
    from Table_A

  • Insert into duplicate entries--exception in crm 2007 webclient

    Hi All,
      I am facing small problem..
    1. I have property field in service ticket component ICCMP_BTSHEAD.
    2.I put some validations based on property .
    3.when user clicks on create service ticket it will create service ticket with PROPERTY field filled up with some value.
      if user clear that value and clicks enter
      again if user enters the some value in field and click on save  it leads to exceptions that is of type insert duplicates array..like that..
        when i checked in debug....for the above procedure the service ticket guid is there in some internal table twice..
      if i did nt dne the steps like above,..i.e with out making property field blank..then no duplicates..
    can any body through some light on this?

    Actully for the same guid there are several entries of the PROPERTY Field , i think you are trying to fill the property field  through manually.  Actually u are clearing the values from the UI layer ( input field )  but not the underlying BOL contexts, so whenever u are clearing and adding the new value it is trying to add the newly added value along with the odl values also. So  make sure that whenever u are clearing the field, the corresponding field should be cleared in the BOL level.
    Regards
    Vikranth

  • Insert into duplicate entries--exception in service ticket scenario

    Hi All,
      I am facing small problem..
    1. I have property field in service ticket component ICCMP_BTSHEAD.
    2.I put some validations based on property .
    3.when user clicks on create service ticket it will create service ticket with PROPERTY field filled up with some value.
      if user clear that value and clicks enter
      again if user enters the some value in field and click on save  it leads to exceptions that is of type insert duplicates array..like that..
        when i checked in debug....for the above procedure the service ticket guid is there in some internal table twice..
      if i did nt dne the steps like above,..i.e with out making property field blank..then no duplicates..
    can any body through some light on this?

    OSS note resolved it

  • Duplicate entries in table & email count

    hi,,
    In my selection screen i have 3 fields-
    billing doc--vbeln
    customer no--kunnr
    email id -
    when i give inputs in this selection screen fields and execute it mail is sent and
    the inputs given for the fields are stored in a ZTABLE.
    my requirement is if user is entering 90073336,66789 and daniel
    once it gets stored in the ztable. if once again i am giving the
    same input, it doesnot get stored in my ztable.
    can i get duplicate entries in my ztable. if yes how?
    and if my receiver mail id is daniel
    no of times email count should be one.if again daniel then two.
    if harry.the one.
    thnx..

    Hi,
    please help me in that counter loop code..how to do this!!
    and how to code for duplicate entries.
    DATA:  ITAB21 TYPE hashed TABLE OF zmailhist WITH UNIQUE key mandt vbeln kunnr,
           WA LIKE LINE OF ITAB21.
    WA-VBELN = P_VBELN.
          INSERT WA INTO TABLE ITAB21.
          WA-KUNNR = P_KUNNR.
          INSERT WA INTO TABLE ITAB21.
          TRANSLATE V_ID TO LOWER CASE.
          CONCATENATE V_ID '@cadence.com'  INTO CHAR1.
          WA-UNAME = CHAR1.
          INSERT WA INTO TABLE ITAB21.
          WA-VSURA = SY-UZEIT.
          INSERT WA INTO TABLE ITAB21.
          WA-ERDAT = SY-DATUM.
          INSERT WA INTO TABLE ITAB21.
              IF SY-SUBRC = 0.
                 V_VSTAT = '0'.
              ELSE.
                 V_VSTAT = '1'.
              ENDIF.
          WA-VSTAT = V_VSTAT.
          INSERT WA INTO TABLE ITAB21.
          WA-NAME1 = I_TAB1-EMAIL.
          INSERT WA INTO TABLE ITAB21.
    INSERT zmailhist FROM TABLE ITAB21 ACCEPTING DUPLICATE KEYS.
    its not picking the duplicate entries..pls help

  • Akonadi database error code: 1062 Duplicate entry for key

    Since my email provider migrated their webmail platform, I keep getting an error each time kmail attempts to get emails from their imap server: could not create collection INBOX resourceid: 17
    I double checked the provided imap settings have not changed and are correct : imap.laposte.net port 993 using SSL/TLS
    As you can see in the pasted akonadi self-test report below, I have a few errors related to innodb, the absence of mysql tables in local/share/akonadi/db_data/ and the table performance_schema having the wrong structure. Those have been there for several months but I've been unable to fix them and I didn't care because my email was working. I suppose they are unrelated to my current issues.
    Any help I can get is much welcome.
    Akonadi Server Self-Test Report
    ===============================
    Test 1: SUCCESS
    Database driver found.
    Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system.
    File content of '/home/the_user/.config/akonadi/akonadiserverrc':
    [%General]
    Driver=QMYSQL
    [QMYSQL]
    Name=akonadi
    Host=
    Options="UNIX_SOCKET=/tmp/akonadi-the_user.kKTLSR/mysql.socket"
    ServerPath=/usr/bin/mysqld
    StartServer=true
    User=
    Password=
    [Debug]
    Tracer=null
    [QPSQL]
    StartServer=true
    Name=akonadi
    Host=
    User=
    Password=
    Port=5432
    [SQLITE]
    Name=akonadi
    Test 2: SUCCESS
    Akonadi is not running as root
    Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.
    Test 3: SUCCESS
    MySQL server found.
    Details: You have currently configured Akonadi to use the MySQL server '/usr/bin/mysqld'.
    Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld'; its location varies depending on the distribution.
    Test 4: SUCCESS
    MySQL server is executable.
    Details: MySQL server found: /usr/bin/mysqld Ver 10.0.14-MariaDB-log for Linux on x86_64 (MariaDB Server)
    Test 5: ERROR
    MySQL server log contains errors.
    Details: The MySQL server error log file &apos;<a href='/home/the_user/.local/share/akonadi/db_data/mysql.err'>/home/the_user/.local/share/akonadi/db_data/mysql.err</a>&apos; contains errors.
    File content of '/home/the_user/.local/share/akonadi/db_data/mysql.err':
    141129 9:34:33 [Warning] You need to use --log-bin to make --binlog-format work.
    2014-11-29 09:34:33 7f5b81d0b780 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
    141129 9:34:33 [Note] InnoDB: Using mutexes to ref count buffer pool pages
    141129 9:34:33 [Note] InnoDB: The InnoDB memory heap is disabled
    141129 9:34:33 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
    141129 9:34:33 [Note] InnoDB: Memory barrier is not used
    141129 9:34:33 [Note] InnoDB: Compressed tables use zlib 1.2.8
    141129 9:34:33 [Note] InnoDB: Using Linux native AIO
    141129 9:34:33 [Note] InnoDB: Using CPU crc32 instructions
    141129 9:34:33 [Note] InnoDB: Initializing buffer pool, size = 80.0M
    141129 9:34:33 [Note] InnoDB: Completed initialization of buffer pool
    141129 9:34:33 [Note] InnoDB: Highest supported file format is Barracuda.
    141129 9:34:33 [Note] InnoDB: The log sequence numbers 66340678877 and 66340678877 in ibdata files do not match the log sequence number 66344113222 in the ib_logfiles!
    141129 9:34:33 [Note] InnoDB: Database was not shutdown normally!
    141129 9:34:33 [Note] InnoDB: Starting crash recovery.
    141129 9:34:33 [Note] InnoDB: Reading tablespace information from the .ibd files...
    141129 9:34:33 [Note] InnoDB: Restoring possible half-written data pages
    141129 9:34:33 [Note] InnoDB: from the doublewrite buffer...
    141129 9:34:34 [Note] InnoDB: 128 rollback segment(s) are active.
    141129 9:34:34 [Note] InnoDB: Waiting for purge to start
    141129 9:34:34 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.20-68.0 started; log sequence number 66344113222
    141129 9:34:34 [Note] Plugin 'FEEDBACK' is disabled.
    141129 9:34:34 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
    141129 9:34:34 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
    141129 9:34:34 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
    141129 9:34:34 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist
    141129 9:34:34 [Note] Reading of all Master_info entries succeded
    141129 9:34:34 [Note] Added new Master_info '' to hash table
    141129 9:34:34 [Note] /usr/bin/mysqld: ready for connections.
    Version: '10.0.14-MariaDB' socket: '/tmp/akonadi-the_user.kKTLSR/mysql.socket' port: 0 MariaDB Server
    2014-11-29 09:34:34 7f5b81c77700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
    141129 15:14:56 [Warning] Aborted connection 58 to db: 'akonadi' user: 'the_user' host: '' (Unknown error)
    Test 6: SUCCESS
    MySQL server default configuration found.
    Details: The default configuration for the MySQL server was found and is readable at <a href='/usr/share/config/akonadi/mysql-global.conf'>/usr/share/config/akonadi/mysql-global.conf</a>.
    File content of '/usr/share/config/akonadi/mysql-global.conf':
    # Global Akonadi MySQL server settings,
    # These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
    # Based on advice by Kris Köhntopp <[email protected]>
    [mysqld]
    # strict query parsing/interpretation
    # TODO: make Akonadi work with those settings enabled
    # sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
    # sql_mode=strict_trans_tables
    # DEBUGGING:
    # log all queries, useful for debugging but generates an enormous amount of data
    # log=mysql.full
    # log queries slower than n seconds, log file name relative to datadir (for debugging only)
    # log_slow_queries=mysql.slow
    # long_query_time=1
    # log queries not using indices, debug only, disable for production use
    # log_queries_not_using_indexes=1
    # mesure database size and adjust innodb_buffer_pool_size
    # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
    # NOTES:
    # Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
    #expire_logs_days=3
    #sync_bin_log=0
    # Use UTF-8 encoding for tables
    character_set_server=utf8
    collation_server=utf8_general_ci
    # use InnoDB for transactions and better crash recovery
    default_storage_engine=innodb
    # memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
    # Deprecated in MySQL >= 5.6.3
    innodb_additional_mem_pool_size=1M
    # memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
    # Larger values means less I/O
    innodb_buffer_pool_size=80M
    # Create a .ibd file for each table (default:0)
    innodb_file_per_table=1
    # Write out the log buffer to the log file at each commit (default:1)
    innodb_flush_log_at_trx_commit=2
    # Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
    # larger values means less I/O
    innodb_log_buffer_size=1M
    # Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
    innodb_log_file_size=64M
    # # error log file name, relative to datadir (default:hostname.err)
    log_error=mysql.err
    # print warnings and connection errors (default:1)
    log_warnings=2
    # Convert table named to lowercase
    lower_case_table_names=1
    # Maximum size of one packet or any generated/intermediate string. (default:1M)
    max_allowed_packet=32M
    # Maximum simultaneous connections allowed (default:100)
    max_connections=256
    # The two options below make no sense with prepared statements and/or transactions
    # (make sense when having the same query multiple times)
    # Memory allocated for caching query results (default:0 (disabled))
    query_cache_size=0
    # Do not cache results (default:1)
    query_cache_type=0
    # Do not use the privileges mechanisms
    skip_grant_tables
    # Do not listen for TCP/IP connections at all
    skip_networking
    # The number of open tables for all threads. (default:64)
    table_open_cache=200
    # How many threads the server should cache for reuse (default:0)
    thread_cache_size=3
    # wait 365d before dropping the DB connection (default:8h)
    wait_timeout=31536000
    # We use InnoDB, so don't let MyISAM eat up memory
    key_buffer_size=16K
    [client]
    default-character-set=utf8
    Test 7: SUCCESS
    MySQL server custom configuration found.
    Details: The custom configuration for the MySQL server was found and is readable at <a href='/home/the_user/.config/akonadi/mysql-local.conf'>/home/the_user/.config/akonadi/mysql-local.conf</a>
    File content of '/home/the_user/.config/akonadi/mysql-local.conf':
    # workaround fix for akonadi db error after server upgrade
    # http://forum.kde.org/viewtopic.php?f=215&t=101004
    [mysqld]
    binlog_format=row
    Test 8: SUCCESS
    MySQL server configuration is usable.
    Details: The MySQL server configuration was found at <a href='/home/the_user/.local/share/akonadi/mysql.conf'>/home/the_user/.local/share/akonadi/mysql.conf</a> and is readable.
    File content of '/home/the_user/.local/share/akonadi/mysql.conf':
    # Global Akonadi MySQL server settings,
    # These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
    # Based on advice by Kris Köhntopp <[email protected]>
    [mysqld]
    # strict query parsing/interpretation
    # TODO: make Akonadi work with those settings enabled
    # sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
    # sql_mode=strict_trans_tables
    # DEBUGGING:
    # log all queries, useful for debugging but generates an enormous amount of data
    # log=mysql.full
    # log queries slower than n seconds, log file name relative to datadir (for debugging only)
    # log_slow_queries=mysql.slow
    # long_query_time=1
    # log queries not using indices, debug only, disable for production use
    # log_queries_not_using_indexes=1
    # mesure database size and adjust innodb_buffer_pool_size
    # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
    # NOTES:
    # Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
    #expire_logs_days=3
    #sync_bin_log=0
    # Use UTF-8 encoding for tables
    character_set_server=utf8
    collation_server=utf8_general_ci
    # use InnoDB for transactions and better crash recovery
    default_storage_engine=innodb
    # memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
    # Deprecated in MySQL >= 5.6.3
    innodb_additional_mem_pool_size=1M
    # memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
    # Larger values means less I/O
    innodb_buffer_pool_size=80M
    # Create a .ibd file for each table (default:0)
    innodb_file_per_table=1
    # Write out the log buffer to the log file at each commit (default:1)
    innodb_flush_log_at_trx_commit=2
    # Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
    # larger values means less I/O
    innodb_log_buffer_size=1M
    # Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
    innodb_log_file_size=64M
    # # error log file name, relative to datadir (default:hostname.err)
    log_error=mysql.err
    # print warnings and connection errors (default:1)
    log_warnings=2
    # Convert table named to lowercase
    lower_case_table_names=1
    # Maximum size of one packet or any generated/intermediate string. (default:1M)
    max_allowed_packet=32M
    # Maximum simultaneous connections allowed (default:100)
    max_connections=256
    # The two options below make no sense with prepared statements and/or transactions
    # (make sense when having the same query multiple times)
    # Memory allocated for caching query results (default:0 (disabled))
    query_cache_size=0
    # Do not cache results (default:1)
    query_cache_type=0
    # Do not use the privileges mechanisms
    skip_grant_tables
    # Do not listen for TCP/IP connections at all
    skip_networking
    # The number of open tables for all threads. (default:64)
    table_open_cache=200
    # How many threads the server should cache for reuse (default:0)
    thread_cache_size=3
    # wait 365d before dropping the DB connection (default:8h)
    wait_timeout=31536000
    # We use InnoDB, so don't let MyISAM eat up memory
    key_buffer_size=16K
    [client]
    default-character-set=utf8
    # workaround fix for akonadi db error after server upgrade
    # http://forum.kde.org/viewtopic.php?f=215&t=101004
    [mysqld]
    binlog_format=row
    Test 9: SUCCESS
    akonadictl found and usable
    Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
    Result:
    Akonadi 1.13.0
    Test 10: SUCCESS
    Akonadi control process registered at D-Bus.
    Details: The Akonadi control process is registered at D-Bus which typically indicates it is operational.
    Test 11: SUCCESS
    Akonadi server process registered at D-Bus.
    Details: The Akonadi server process is registered at D-Bus which typically indicates it is operational.
    Test 12: SKIP
    Protocol version check not possible.
    Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements.
    Test 13: SUCCESS
    Resource agents found.
    Details: At least one resource agent has been found.
    Directory listing of '/usr/share/akonadi/agents':
    akonadibalooindexingagent.desktop
    akonadinepomukfeederagent.desktop
    akonotesresource.desktop
    archivemailagent.desktop
    birthdaysresource.desktop
    contactsresource.desktop
    davgroupwareresource.desktop
    facebookresource.desktop
    followupreminder.desktop
    googlecalendarresource.desktop
    googlecontactsresource.desktop
    icaldirresource.desktop
    icalresource.desktop
    imapresource.desktop
    invitationsagent.desktop
    kabcresource.desktop
    kalarmdirresource.desktop
    kalarmresource.desktop
    kcalresource.desktop
    kdeaccountsresource.desktop
    knutresource.desktop
    kolabproxyresource.desktop
    kolabresource.desktop
    localbookmarksresource.desktop
    maildirresource.desktop
    maildispatcheragent.desktop
    mailfilteragent.desktop
    mboxresource.desktop
    migrationagent.desktop
    mixedmaildirresource.desktop
    mtdummyresource.desktop
    newmailnotifieragent.desktop
    nntpresource.desktop
    notesresource.desktop
    openxchangeresource.desktop
    pop3resource.desktop
    sendlateragent.desktop
    vcarddirresource.desktop
    vcardresource.desktop
    Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/share:/usr/local/share'
    Test 14: ERROR
    Current Akonadi server error log found.
    Details: The Akonadi server reported errors during its current startup. The log can be found in <a href='/home/the_user/.local/share/akonadi/akonadiserver.error'>/home/the_user/.local/share/akonadi/akonadiserver.error</a>.
    File content of '/home/the_user/.local/share/akonadi/akonadiserver.error':
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    Test 15: ERROR
    Previous Akonadi server error log found.
    Details: The Akonadi server reported errors during its previous startup. The log can be found in <a href='/home/the_user/.local/share/akonadi/akonadiserver.error.old'>/home/the_user/.local/share/akonadi/akonadiserver.error.old</a>.
    File content of '/home/the_user/.local/share/akonadi/akonadiserver.error.old':
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    DATABASE ERROR:
    Error code: 1062
    DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
    Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
    Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
    Control process died, committing suicide!
    Test 16: ERROR
    Current Akonadi control error log found.
    Details: The Akonadi control process reported errors during its current startup. The log can be found in <a href='/home/the_user/.local/share/akonadi/akonadi_control.error'>/home/the_user/.local/share/akonadi/akonadi_control.error</a>.
    File content of '/home/the_user/.local/share/akonadi/akonadi_control.error':
    Executable "akonadi_nepomuk_feeder" for agent "akonadi_nepomuk_feeder" could not be found!
    Test 17: ERROR
    Previous Akonadi control error log found.
    Details: The Akonadi control process reported errors during its previous startup. The log can be found in <a href='/home/the_user/.local/share/akonadi/akonadi_control.error.old'>/home/the_user/.local/share/akonadi/akonadi_control.error.old</a>.
    File content of '/home/the_user/.local/share/akonadi/akonadi_control.error.old':
    Executable "akonadi_nepomuk_feeder" for agent "akonadi_nepomuk_feeder" could not be found!

    After Upload you can delete the Duplicates comparing the employee Id.
    It Will be Possible only when you use OLE and read the file records line by Line. I am not sure of the error Handling with OLE control. It may lead to some performance issues..

  • DUplicate entries in DB table

    Hi everyone
    I am a little confused by a situtation I have come across in one of our bespoke tables.  I was under the impression that all fields in a table that are marked as Key form a Primary Key and therefore it is <b>impossible</b> to create records where these key fields contain duplciate data.  However, I have found a bespoke table that is used for logging exception messages that appears to hold records with duplicates in the Key fields.  Has anyone else come across this or have any idea how it might be happening?  When creating a table is possible to specify a non-unique key in the same way you might for an internal table?! If it is relevant, the table is updated from a program that locks and unlocks the table before and afer the insert takes place and can be caused by both batch and manual changes.
    Thanks
    Andy

    Thanks Roopesh
    I understood the [ACCEPTING DUPLICATE KEYS] flag to mean that a a 'bulk' insert would not fail if a duplicate entry was identified but instead would set subrc to 4, skip the record in question and continue with subsequent records.  If this is the case it still should not actually create duplciate entries - surely in doing so referential integrity is being violated...
    Here is the section of code that performs the insert if that helps at all:
    *lock table and insert processing log details
    CALL FUNCTION 'ENQUEUE_EZLG_T024E'
    EXPORTING
       MODE_ZLG_T024           = 'E'
       MANDT                   = SY-MANDT
       EMPLOYER_REG_NO         = zlg_t024-EMPLOYER_REG_NO
       GRANT_CLAIM_NO          = zlg_t024-GRANT_CLAIM_NO
       ITEM                    = zlg_t024-ITEM
    EXCEPTIONS
       FOREIGN_LOCK            = 1
       SYSTEM_FAILURE          = 2
       OTHERS                  = 3.
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
             WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    insert zlg_t024.
    * unlock table.
    CALL FUNCTION 'DEQUEUE_EZLG_T024E'
    EXPORTING
       MODE_ZLG_T024           = 'E'
       MANDT                   = SY-MANDT
       EMPLOYER_REG_NO         = zlg_t024-EMPLOYER_REG_NO
       GRANT_CLAIM_NO          = zlg_t024-GRANT_CLAIM_NO
       ITEM                    = zlg_t024-ITEM
    Kind regards
    Andy

  • Trick to remove duplicate entries from tables ?

    hi.
    i have 53tables which are having duplicate entries and names of all 53 tables r listed in top_t table ?
    can any1 provide me solution to show and if possible ask for remove of those duplicates entries from each table if required ?
    daily i am removing duplicates manually ....its too tedious now !
    can any1 help me out ?

    Well, I suppose if the duplication is such that
    SELECT DISTINCT * FROM tablename;gives you the required result, then you could have a procedure that made a copy of the table, deleted/truncated the original, then inserted the distinct values back into it.
    In 10g you could even use flashback to avoid the temp copy - but it also means you can't use TRUNCATE so whether it's any more efficient I'm not sure. But just for fun and since it's urgent:
    CREATE OR REPLACE PROCEDURE dedupe_table
        ( p_table_name user_tables.table_name%TYPE )
    IS
        k_start_timestamp TIMESTAMP := SYSTIMESTAMP;
    BEGIN
        SAVEPOINT start_of_dedupe;
        BEGIN
            EXECUTE IMMEDIATE 'DELETE ' || p_table_name;
        EXCEPTION
            WHEN OTHERS THEN
                ROLLBACK TO start_of_dedupe;
                RAISE_APPLICATION_ERROR
                ( -20000
                , 'Error deleting ' || UPPER(p_table_name) ||
                   CHR(10) || DBMS_UTILITY.FORMAT_ERROR_BACKTRACE
                , TRUE );
        END;
        BEGIN
            EXECUTE IMMEDIATE
            'INSERT INTO ' || p_table_name ||
            ' SELECT DISTINCT * FROM ' || p_table_name || ' AS OF TIMESTAMP :b1'
            USING k_start_timestamp;
        EXCEPTION
            WHEN OTHERS THEN
                ROLLBACK TO start_of_dedupe;
                RAISE_APPLICATION_ERROR
                ( -20000
                , 'Error repopulating ' || UPPER(p_table_name) ||
                   CHR(10) || DBMS_UTILITY.FORMAT_ERROR_BACKTRACE
                , TRUE );
        END;
    END dedupe_table;
    SQL> select * from wr_test;
          COL1 C C
             1 A B
             1 A B
             2 C D
             2 C D
    4 rows selected.
    SQL> BEGIN
      2      dedupe_table('WR_TEST');
      3  END;
      4  /
    PL/SQL procedure successfully completed.
    SQL> select * from wr_test;
          COL1 C C
             1 A B
             2 C D
    2 rows selected.I make no claims for robustness, efficiency or human safety.
    Edited by: William Robertson on Sep 24, 2009 7:12 PM

  • Deleting duplicate entries

    I have two tables (Accounts, and Accounts_LOAD). The _Load table is a daily feed.
    For my first step, I need to delete all the duplicates from _Load that exist in Accounts. 
    How can I delete duplicate entries which exist in two tables..?

    I think that the Merge will suffice. My apologies.
    But, now (again, sorry) I have a couple questions on the merge.
    Below is similar to what I would use and a few Q's on it....
    line4: can u use multiple "on" ?
    line5:For 'when matched' i only want to update fields from "_load" to "Accounts" that need to be updated. If they are the same, they would be ignored... is that possible...?
    1 MERGE INTO accounts acc
    2 USING (SELECT **ALLFIELDS**
    3 WHERE SOMESTUFF=STUFFS) STF
    4 ON (ACC.ID_USER = STF.ID_USER) AND (ACC.SYSTEM_ID = STF.SYSTEM_ID)
    5 WHEN MATCHED THEN UPDATE SET acc.bonus = D.bonus + S.salary*.01
    6 DELETE WHERE (S.salary > 8000)
    7 WHEN NOT MATCHED THEN INSERT (D.employee_id, D.bonus)
    8 VALUES (S.employee_id, S.salary*0.1)
    9 WHERE (S.salary <= 8000);

  • Validating  duplicate entries in form level

    Hi I want to validate records whether its duplicate here i am inserting to a table and want to check whether its existing in another table and if not i need to enter the data.I return the following code but its returning error.I already removed the duplicate rows but still getting same error.I need to validate the duplicate entries.If i enter any refno its showing following error.
    frm 40735 When Validate Item Trigger raised unhandled exception Ora -01422
    declare
         refno number(10);
    begin
         select ref_no into refno from      Emp_ref_arch;
         if refno = :EMP.REF_NO then
              message ('Duplicate Entry Pls enter again');
              else
              go_item(:EMP.Edet);
         end if;
    end;
    rgds
    jyothi
    Edited by: user11243021 on Aug 16, 2009 11:48 PM

    jyothi,
    If you are using select into statements to check whether the data exists or not, then you have to use cursor because, when there is no data, it will return error. And you didn't specified the where condition also.
    So try this.
    DECLARE
         Num_RefNo NUMBER(10);
         CURSOR Cur_Check IS SELECT REF_NO FROM EMP_REF_ARCH WHERE <your condition>;
    BEGIN
         OPEN Cur_Check;
         FETCH Cur_Check INTO Num_RefNo;
         CLOSE Cur_Check;
         IF NVL(Num_RefNo, 0) = :EMP.REF_NO THEN
              MESSAGE ('Duplicate Entry Pls enter again');
         ELSE
              GO_ITEM(:EMP.EDET);
         END IF;
    END;Regards,
    Manu.
    If this answer is helpful or correct, please mark it. Thanks.

  • Exception :java.sql.SQLException: Duplicate entry '1-0' for key 1

    Help me in fixing this error
    Exception :java.sql.SQLException: Duplicate entry '1-0' for key 1
    1>>User_ID is primary key and unique and
    2>>User_ID is also auto Incremented
    3>>User_ID is the First coloumn in the table
    PreparedStatement ps=con.prepareStatement("insert into User(user_name,user_email,user_password) values (?,?,?)");
    ps.setString(1,s11);
    ps.setString(2,s22);
    ps.setString(3,s33);
    int i= ps.executeUpdate();

    A growing trend it appears. Must be some new high school and/or college curriculum regarding moral relativism.

  • MySQL duplicate entry deletion in 5.5.9

    Hey all,
    I've noticed that in the newest MySQL, I can no longer do:
    ALTER TABLE test ADD UNIQUE INDEX unique_index (id);
    ALTER TABLE test DROP INDEX unique_index;
    to remove duplicates. I get the following error:
    ERROR 1062 (23000): Duplicate entry '3' for key 'unique_index']
    This worked fine before the major SQL upgrade. It also works fine on version 5.1.52 on my web host.  I searched through the 5.5.9 release notes and I didn't see anything that should have changed this, but I'm no MySQL guru! Is this a feature or a bug? Any alternate suggestions for deleting duplicates that will work on this version and older versions of MySQL?
    Thanks!
    Scott
    Edit: Just for clarity, the table I'm working on has a single primary key column (UNIQUE_KEY) (with 80+ other data columns) and I'm only detecting the duplicate row based on the value of the primary key column.
    Last edited by firecat53 (2011-02-25 03:33:30)

    Alright, since I was apparently sucked in by this particular method the first time I googled the answer, care to enlighten me on the 'more practical' non-joke methods, as there appears to be more than one option.
    Also, why is that a joke of a feature? Like I said, I'm no MySQL guru so I'm ready to learn!
    Thanks,
    Scott
    edit: is this a 'more practical' method? It's hard when you're learning on your own to sort out the good from the bad sometimes
    edit2: using the above method with this table:
    +------+------+-------+
    | id | data | data1 |
    +------+------+-------+
    | 1 | 10 | 100 |
    | 2 | 100 | 1000 |
    | 3 | 1000 | 500 |
    | 3 | 1000 | 500 |
    +------+------+-------+
    and this query:
    delete test from test left outer join (select min(id) as RowID, id from test group by id) as KeepRows on test.id=KeepRows.RowID where KeepRows.RowID is null;
    I can't quite get it to work...it doesn't delete any rows. What am I missing there?
    edit3: This method works -- is it a 'good' method or should I be looking at something different? Again, I'm just matching on duplicates in the primary key column (before the primary key is assigned):
    create table test1 like test;
    insert into test1 select * from test group by id;
    drop table test;
    rename table test1 to test;
    Last edited by firecat53 (2011-02-25 03:55:10)

  • ORA-13223: duplicate entry for string in SDO_GEOM_METADATA table and

    I got the above error while trying to insert a record into the table SDO_GEOM_METADATA. However, when querying this table I did find any duplicate table_name, column_name pair that match with the error.
    Here are the steps that I worked on:
    1. Add a geometry column into an existing table.
    ALTER TABLE GEO_MAP ADD (ORG_GEOM mdsys.sdo_geometry);
    2. Register the new column into mdsys
    insert into USER_SDO_GEOM_METADATA
    values ('GEO_MAP','ORG_GEOM',
    mdsys.sdo_dim_array(
    mdsys.sdo_dim_element('LONG',-180,180,0.00005),
    mdsys.sdo_dim_element('LAT',-90,90,0.00005)
    8307)
    I got the error ORA-13223: duplicate entry for string in SDO_GEOM_METADATA table even there was no such record in there.
    3. I inserted values in the column ORG_GEOM fine.
    4. However, when I tried to create the index for this column I got the error:
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-13203: failed to read USER_SDO_GEOM_METADATA view
    ORA-13203: failed to read
    Please help.
    Thanks.

    SQL> select * from mdsys.sdo_geom_metadata_table;
    SDO_OWNER SDO_TABLE_NAME
    SDO_COLUMN_NAME
    SDO_DIMINFO(SDO_DIMNAME, SDO_LB, SDO_UB, SDO_TOLERANCE)
    SDO_SRID
    QW_USER1 GEO_REF
    LOC_GEOM
    SDO_DIM_ARRAY(SDO_DIM_ELEMENT('LONG', -180, 180, .00005), SDO_DIM_ELEMENT('LAT',
    -90, 90, .00005))
    SDO_OWNER SDO_TABLE_NAME
    SDO_COLUMN_NAME
    SDO_DIMINFO(SDO_DIMNAME, SDO_LB, SDO_UB, SDO_TOLERANCE)
    SDO_SRID
    8307
    MDSYS SDO_CMT_CBK_RTREE_TAB
    GEOM
    SDO_DIM_ARRAY(SDO_DIM_ELEMENT('X', -180, 180, .000000005), SDO_DIM_ELEMENT('Y',
    SDO_OWNER SDO_TABLE_NAME
    SDO_COLUMN_NAME
    SDO_DIMINFO(SDO_DIMNAME, SDO_LB, SDO_UB, SDO_TOLERANCE)
    SDO_SRID
    -90, 90, .000000005))
    The situation is we have 2 tables (GEO_MAP, and GEO_REF) that have spatial columns. Everything worked fine until when one of the queries that searched through the table GEO_MAP ran so slow, we decided to rebuild the related spatial index by dropping and recreating it. However, after I dropped it I could not recreated. Keep getting the error:
    ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
    ORA-13203: failed to read USER_SDO_GEOM_METADATA view
    ORA-13203: failed to read
    Any help is very much appreciated.

  • Short dumop in J2I5 (provide duplicate entry in Standard table)

    Hello Expert ,
                              We have a problem in  T.Code J2I5  ( Excise Register Extraction) input entry is lelect Excise group 20 . and a date   from 04.08.09 onwards. and select the register RG23D . it shows the run time error  ( Eg The ABAP/4 Open SQL array insert results in duplicate database record ) .  but in the standard Tcode is there possible to provide duplicate entry in Standard table
    Thaks & regards
    Aditya Kr Tripathi

    Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
    Except.                CX_SY_OPEN_SQL_DB
    Date and Time          29.01.2010 10:57:09
    <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
    problem occurs in this code :
       assign I_RG23D_TAB-I_RG23D_TYP to <x_rg23dtyp> casting.
       <x_extrctdata> = <x_rg23dtyp>.
        class CL_ABAP_CONTAINER_UTILITIES definition load.
        call method CL_ABAP_CONTAINER_UTILITIES=>FILL_CONTAINER_C
          EXPORTING
            IM_VALUE               = i_rg23d_tab-i_rg23d_typ
          IMPORTING
            EX_CONTAINER           = i_report_tab-extrctdata
          EXCEPTIONS
            ILLEGAL_PARAMETER_TYPE = 1
            others                 = 2.
       I_REPORT_TAB-EXTRCTDATA = I_RG23D_TAB-I_RG23D_TYP.
        COMPUTE I_REPORT_TAB-EXTRCTLNGT = STRLEN( I_REPORT_TAB-EXTRCTDATA ).
        APPEND I_REPORT_TAB.
      ENDLOOP.
      IF M_EXTRACTED = 'X'.
        LOOP AT I_RG23D_KEY.
          DELETE
          FROM  J_2IEXTRCT
          WHERE BUDAT    = I_RG23D_KEY-BUDAT
          AND   SERIALNO = I_RG23D_KEY-SERIALNO
          AND   REGISTER = I_RG23D_KEY-REGISTER
          AND   EXGRP    = I_RG23D_KEY-EXGRP.
        ENDLOOP.
      ENDIF.
    Control table check here for data Extraction
      INSERT J_2IEXTRCT FROM TABLE I_REPORT_TAB.
    If the insertion of the extract table is successfull then the table
    for Extraction is Inserted
      IF SY-SUBRC EQ 0.
        PERFORM FILL_EXTDT USING C_RG23D M_EXTRACTED.
      ENDIF.
    ENDFORM.                                                    " RG23D
    *&      Form  RG23CPART1
    Purpose : RG23C Part I extraction logic
    FORM RG23CPART1.
      DATA: $PART1      TYPE PART1_TYP,
            $LINCNT     LIKE SY-LINCT,
            M_EXTRACTED VALUE '',
            $RC         LIKE SY-SUBRC.
    *********************************************************************************************8

  • To avoid duplicate entries in multi row

    Hi i need to avoid duplicate entries in multi record form.In the master block i have AGENCY CODE.These are the fields, RATING_CODE(composite primary key alng with AGENCY_CODE in the detail block,but set as hidden) and DESCRIPTION
    in the detail block.If AGENCY_CODE is CRISIL,then for that i should not enter duplicate RATING CODES.I have written
    DECLARE
         L_COUNT2 NUMBER;
         l_ret varchar2(20);
    BEGIN
         SELECT COUNT(*) INTO L_COUNT2 FROM CSTM_AGENCY_CODE_DETAIL
    WHERE AGENCY_CODE=:BLK_CSTM_AGENCY_CODE_DETAIL.AGENCY_CODE
    AND RATING_CODE=:BLK_CSTM_AGENCY_CODE_DETAIL.RATING_CODE;
    IF L_COUNT2 > 0 THEN
              l_ret := ovpkcs.fn_dispmsg('AGYCOD-03;',';',';');
    Raise Form_Trigger_Failure;
    END IF;
    END;
    in WHEN_VALIDATE_ITEM.
    Now when i press the TAB to move next time it gives the message,DUPLICATE RATING CODE.The
    problem is when i move back to the previous record by clicking mouse and change it to the already existing value,and while i save the validation is not happening and the message is not shown.Kindly tell me where i should code.
    Thank you

    hy,
    you can check whan commit( an save button)
    for i = 1 to n-1
    check condition (item = item +1)
    next_record
    end
    or by stored insert whit exception return to form program when duplicate key is found
    ...

Maybe you are looking for