Database error: TemSe- XRTAB(2)- 1 for table TST01 key [400]JOBLGX13132201X

Hi
We are getting the next erros with the jobs:
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            F6H Database error: TemSe->XRTAB(2)->1 for table TST01 key                                  
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            GZZ > retry creation JOBLGX btctlgow216#                                                    
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            F6H Database error: TemSe->XRTAB(2)->1 for table TST01 key [400]JOBLGX13132201X28173,1      
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            GZZ > retry creation JOBLGX btctlgow216#                                                    
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            F6H Database error: TemSe->XRTAB(2)->1 for table TST01 key [400]JOBLGX13132201X28173,1      
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            GZZ > retry creation JOBLGX btctlgow216#                                                    
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            F6H Database error: TemSe->XRTAB(2)->1 for table TST01 key [400]JOBLGX13132201X28173,1      
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            ECF Failed to create log for job POLCASHWIN                                                 
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            EBC > Job POLCASHWIN                                                                        
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            EAY Failed to read status entry for job POLCASHWIN                                          
13:13:51 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            EBC > Job POLCASHWIN                                                                        
13:24:21 PRDAUNE2_PRD_02      BTC 22 000 SAPSYS            BYM SQL error 0 . Work processes in reconnect status                                        
We make a consistency check of spool and temse but nothing is wrong, but if we apply Check Status in  the SM37 some jobs change to Active and run but other are in same status Ready
We olny found the note 67055 but recommended the consistency check.
Best Regards
Reynaldo Rebolledo

Hi Reynaldo,
Check for Tablespace PSAPTEMP size for Oracle database when job is running.
If tablespace is full try adding datafile and run the job.
Award Points if Helpful

Similar Messages

  • Database error: TemSe- XRTAB(3)- 1 for table TST01 key

    Hi Sap Gurus,
    BZ  Y Unexpected return value 1 when calling up DbSlR
    BY  J Function ROLLBACK on connection R/3 failed
    R3  9 Error in DB rollback/SyFlush, return code 016384
    BY  4 Database error 0 at UPD access to table TST01
    BY  0 >
    F6  H Database error: TemSe->XRTAB(3)->1 for table TST01 key
    Q0  2 Stop Workp. 14, PID 4186340
    Q0  1 Start Workp. 14, 16 times since system startup. PID 9 646770
    F6  F TemSe object JOBLGX22303300X49850 was closed remotely
    F6  V Invalid address (NULL) was transferred
    EC  F Failed to create the log for job No joblog, 4C412205C6C80300E1008
    R4  7 Delete session 001 after error 023
    Q0  I Operating system call getaddrinfo failed (error no. 0 )
    Q0  I Operating system call getaddrinfo failed (error no. 0 )
    BZ  Y Unexpected return value 1 when calling up DbSlR
    BY  J Function ROLLBACK on connection R/3 failed
    R3  9 Error in DB rollback/SyFlush, return code 016384
    BY  4 Database error 0 at UPD access to table TST01
    BY  0 >
    F6  H Database error: TemSe->XRTAB(3)->1 for table TST01 key
    Any idea to avoid the system log entries.
    Regards
    Munish Jindal

    Hi Munish,
                   For TemSe error first point of resolution will be at T - Code : SP12. In there select,
    TemSe Data Storage --> Consistency Check. This will run for a while depending on the number of recored within the TSTO1 table. Once the execution is completed delete all the records displayed in red.
    Apart from above step, you can use T - Code: SPAD. In there, you will find two tabs
    a) Devices/servers
    b) Admin.
    within admin tab select "Delete Old Spool Request". You will see a popup. In there you can select "Request already printed" check box and Minimum Age in day <> depends on your requirement. I sugest for 7 days and execute. This also takes certain amount of time to get executed.
    In the same  T - Code: SPAD, Select Administration --> Check Consistency
    Make sure Spool re-organizing job is scheduled that will be executed daily at night to clear spool requrest that are older than 10 days in age.
    I guess this helps to some extent.
    Regards,
    Nani Chowdary

  • Database error: TemSe- XRTAB(4)- 64 for table TST01 key,

    Hi all,
    We are getting the following system logs regarding TEMSE,kindly suggest the solution.
    =============================================================
    Database error: TemSe->XRTAB(4)->64 for table TST01 key /usr/sap/RP1/SYS/global/400JOBLG/0001X00314003X87008
    Database error:  TemSe->&A(&B)->&C for table &D key &a
                             !  !    !            Table name
                             !  !    Error number
                             !  Function number
                             Database access module
    Possible database access modules
    RTAB
    Direct access with entire or partial primary key
    XRTAB
    direct access with entire or partial primary key for all clients
    INCLUDE 'RSTS_RTAB_FUNCTIONS' OBJECT DOKU ID TX
    INCLUDE 'RSTS_RTAB_ERRORS' OBJECT DOKU ID TX
    INCLUDE 'RSTS_TABLES' OBJECT DOKU ID TX
    =================================================================
    Error in TemSe Management
    Error in the C coding of the spooler.Message is no longer output.
    ==================================================================
    Spool: RT_DELETE Reports Error 64 for Table
    The RTAB interface has reported an unexpected error return code to the
    spool. The RTAB function used was 'RT_DELETE'. The error number used in
    the message can be translated using 'dbrtab.h' and 'dbglobal.h'.
    Check whether there has been a syslog entry from the RTAB interface
    before this.
    ===================================================================
    Regards
    Ram

    Hello Siobhan,
    There is an inconsistency in data .Check if you are able to find an entry for SPOOL0000028682 in table TST01.
    Check the OSS note 67055.
    TemSe->XRTAB(4)->64  means that SAP is not able to find a key entrySPOOL0000028682 in the tableTST01 for updating records. If you dont need. Check errors in Sm13 as well for this table.
    If you dont need 28682 go ahead and delete it and do a temse reorganization.
    Before this do a TEMSE check using report RSTS0020.
    regards.
    Ruchit.
    Message was edited by:
            Ruchit Khushu

  • Database error: TemSe- XRTAB(0)- 1 for table TST01

    Dear All
    following error is showing in system log from yesterday every 3 minute intreval
    SQL error 3114 . Work processes in reconnect status
    Database error: TemSe->XRTAB(0)->1 for table TST01 key
    [900]JOBLGX09372801X60922,1
    Failed to read status entry for job SWWERRE
    Failed to create log for job SWWERRE
    Failed to read status entry for job SWWERRE
    SQL error 3114 . Work processes in reconnect status
    Database error: TemSe->XRTAB(0)->1 for table TST01 key
    [900]JOBLGX09212801X09555,1
    Failed to read status entry for job SWWDHEX
    Failed to create log for job SWWDHEX
    Failed to read status entry for job SWWDHEX
    pl reply

    Hi Baikerikar,
    As per I see, the particular log getting appened in the log when a given workprocess trying to perform a 'WORKFLOW' related task. Both tasks SWWERRE and SWWDHEX are two reports; report SWWERRE  helps in clean-up error out workflow items and report SWWDHEX helps in monitoring the deadlines of workflow items.
    so please check the following
    - TempSec (SP12)  - consistence check -> Delete All (if systems lists any entries)
    - Printer Consistence (SPAD)->Administration->Check Consistence -> Delete All (if systems lists any entries)
    - SM12 for locks.- -> Delete All (if systems lists any entries)
    - And also check 'SAP_REORG_JOB' running fine in the system.
    You perhaps respond back if the above key tasks does not resolve the issue.
    Regards
    Sekhar

  • TemSe- XRTAB(4)- 64 for table TST01 key [200]SPOOL0000028682 ,1

    Hi
    Keep getting this error in SM21 Database error: TemSe->XRTAB(4)->64 for table TST01 key [200]SPOOL0000028682 ,1.
    I've run the consistency check in SPAD and SP12 and everything looks ok.
    Would any have any ideas where to go next?
    Thanks
    Siobhan

    Hello Siobhan,
    There is an inconsistency in data .Check if you are able to find an entry for SPOOL0000028682 in table TST01.
    Check the OSS note 67055.
    TemSe->XRTAB(4)->64  means that SAP is not able to find a key entrySPOOL0000028682 in the tableTST01 for updating records. If you dont need. Check errors in Sm13 as well for this table.
    If you dont need 28682 go ahead and delete it and do a temse reorganization.
    Before this do a TEMSE check using report RSTS0020.
    regards.
    Ruchit.
    Message was edited by:
            Ruchit Khushu

  • Database error: TemSe- RTAB-S/G(8)- 1 for table TCPSBUILD key

    I am having a two (2) node (Microsoft) cluster running on Oracle10g R.
    I have restarted both nodes, the cluster is on node #1, and I keep seeing the following errors (repeatedly) only in node #2:
    SQL error 12154 occured: work process in reconnect status
    Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key
    No Code Page Conversion '4103'->'1100' : CCC->CCC
    I have also run TemSe: Data Consistency Check (via SP12).
    Can I resolve this issue ?
    Best regards,
    Tom

    Hi,
    " Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key "
    This error is because codepage converter has no access to database. Hence the converter messages are aftereffects due to the fact that the work process has no connection to the database and can be ignored.
    See this SAP note for more details...
    Note 864267 - Code page conversion error after WP has left reconnect state
    Regards
    Bhuban

  • Database error: TemSe- RTAB-S/G(8)- 4 for table TCPSBUILD key

    Hi,
    I am checking in sm21, I getting continously this syslog Database error: TemSe->RTAB-S/G(8)->4 for table TCPSBUILD key.
    I deleted records of past 10 days from TST03 table.
    but still I am getting this error in SM21.
    Would anyone please suggest on this?
    MY sap Component is SAP ECC 6.0
    Thanks in advance.
    Regards,
    Manish

    Hi all,
    I have the same message but on the Windows event viewer.
    Because of this, backups are failing.
    When I try to make a consistensy check throught SP12 there is a dump:
    The program "RSTS0020" has exceeded the maximum permitted runtime without
    interruption and has therefore been terminated.
    I have tried to launch also the RSTS0030 program in dialog, no objects are found.
    Can someone help please?

  • Database error: TemSe- RTAB-S/G(8)- 1 for table TCPSBUILD key 1100T*

    Dear All,
    I am getting the below error in txsm21.Please suggest how to solve it
    we are using ecc6 , oracle 10g on windows.
    Database error 12518 at SEL access to table TCPSBUILD
    > ORA-12518: TNS:listener could not hand off client connection
    Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key 1100T*
    No Code Page Conversion '4103'->'1100' : CCC->CCC
    Database error 12518 at SEL access to table TCPSBUILD
    > ORA-12518: TNS:listener could not hand off client connection
    Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key 1100T*
    No Code Page Conversion '4103'->'1100' : CCC->CCC
    Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key 1100T*
    No Code Page Conversion '4103'->'1100' : CCC->CCC
    Database error 12518 at SEL access to table TCPSBUILD
    > ORA-12518: TNS:listener could not hand off client connection
    Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key 1100T*
    No Code Page Conversion '4103'->'1100' : CCC->CCC
    Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key 1100T*
    No Code Page Conversion '4103'->'1100' : CCC->CCC
    Database error 12518 at SEL access to table TCPSBUILD
    > ORA-12518: TNS:listener could not hand off client connection
    Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key
    No Code Page Conversion '4103'->'1100' : CCC->CCC
    Database error 12518 at SEL access to table TCPSBUILD
    > ORA-12518: TNS:listener could not hand off client connection
    Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key
    No Code Page Conversion '4103'->'1100' : CCC->CCC
    Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key
    No Code Page Conversion '4103'->'1100' : CCC->CCC
    Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key
    No Code Page Conversion '4103'->'1100' : CCC->CCC
    Operating system call recv failed (error no. 10054)
    Regards,
    Kumar

    Hi,
    Check  SAP Note 864267 (Code page conversion error after WP has left reconnect state). It might help .
    Regards,
    Neel

  • Database Error: RSR0009: Resource not available for pool. Wait-time expired

    i am occassionally receiving the following error during database connections in my servlet:
    Database Error: RSR0009: Resource not available for pool [webAdvisorTestPool]. Wait-time expired
    i understand that this is a result of a connection leak from improper closure of my Connection object, but i thought that i was properly closing my connection.
    i can get the error if i do the following steps:
    1) access my login page and enter login credentials.
    2) submit the login which then hits the Authentication servlet.
    3) Authentication servlet authenticates and takes me to home page.
    4) hit the back button to get back to the login page.
    5) repeat this process until i hit the Max Pool Size (from web server).
    6) then i get the error message
    here are some details:
    i have an Authentication servlet; here is the pertinent code from that servlet:
    try {     // retrieve the user and add the User object to the session     DAO dao = new DAO();     Person authenticUser = dao.getPerson(userID, password);     session.setAttribute("validUser", authenticUser);     redirectPage = mapping.findForward("success"); }
    i also have a DAO object that handles all of my DB transactions (and you can see from my code above that the Authentication servlet is using that object); here is the pertinant code from that servlet:
    public DAO() {     datasource = "java:comp/env/jdbc/webAdvisorTest"; } public Person getPerson(String userID, String password)     throws ObjectNotFoundException {     // JDBC variables     DataSource ds = null;     Connection conn = null;     PreparedStatement stmt = null;     ResultSet results = null;     // User variables     Person validUser = null;     try     {         // Retrieve the DataSource from JNDI         InitialContext ctx = new InitialContext();         // if this statement fails, NamingException is thrown         ds = (DataSource)ctx.lookup(datasource);         // get DB connection and perform SQL operations         conn = ds.getConnection();         // User variables         String validUserID = null;         String validFName = null;         String validLName = null;         String validEmail = null;         // get DB connection and perform SQL operations         conn = ds.getConnection();         stmt = conn.prepareStatement(PERSON_QUERY);         stmt.setString(1, userID);         stmt.setString(2, password);         results = stmt.executeQuery();         // iterate through the results         if (results.next())         {             validUserID = results.getString("id");             validFName = results.getString("first_name");             validLName = results.getString("last_name");             validUser = new Person(validUserID, validFName, validLName);         }     }     // handle SQL errors     catch(SQLException e)     {         e.printStackTrace(System.err);         throw new RuntimeException("Database Error: " + e.getMessage());     }     // handle JNDI errors     catch(NamingException e)     {         throw new RuntimeException("JNDI Error: " + e.getMessage());     }     // clean up resources     finally     {         doClosure(results, stmt, conn);     }     // if the user was not found, throw ObjectNotFoundException     if(validUser == null)     {         throw new ObjectNotFoundException();     }     return validUser; } protected void doClosure(ResultSet results, PreparedStatement stmt,     Connection conn) {     if (results != null)     {         try { results.close(); }         catch (SQLException e) { e.printStackTrace(System.err); }     }     if (stmt != null)     {         try { stmt.close(); }         catch (SQLException e) { e.printStackTrace(System.err); }     }     if (conn != null)     {         try         {             System.out.println("R18Resources.conn before close: " + conn);             conn.close();             System.out.println("R18Resources.conn after close: " + conn);             System.out.println("R18Resources.conn is closed? " +                 conn.isClosed());         }         catch (SQLException e)         {             System.out.println("R18Resource conn close error: " +                 e.getMessage());         }     } }
    as you can see, i've added some print statements in my connection closure block. based on my output log, each connection is being properly closed and i am not encountering any errors during that closing block.
    any ideas???
    Message was edited by:
    millerand

    Please try the following code in your doClosure method. Replace your code with the following code.
    public void doClosure(ResultSet pResultSet, Statement pStmt, Connection pConn) throws Exception {
    try {
                   if (pResultSet != null) {
                        pResultSet.close();
                        pResultSet = null;
              } catch (SQLException se) {
              logger.error( se );
              } finally {
                   try {
                        if (pStmt != null) {
                             pStmt.close();
                             pStmt = null;
                   } catch (SQLException se) {
                   logger.error(se);
                   } finally {
                        try {
                             if (pConn != null) {
                                  pConn.close();
                                  pConn = null;
                        } catch (SQLException se) {
                        logger.error(se);
    And let me know if you still face this issue. What is the application server you are using?

  • Getting database error while updating data to mysql table.

    user registration.jsp < jsp user view to get input >
    <?xml version="1.0" encoding ="UTF-8"?>
    <%@ taglib prefix="c"   uri="http://java.sun.com/jsp/jstl/core" %>
    <%@ taglib prefix="fmt" uri="http://java.sun.com/jsp/jstl/fmt" %>
    <%@ taglib prefix="sql" uri="http://java.sun.com/jsp/jstl/sql" %>
    <%@ taglib prefix="x"   uri="http://java.sun.com/jsp/jstl/xml" %>
    <%@ taglib prefix="fn"  uri="http://java.sun.com/jsp/jstl/functions" %>
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html>
    <head>
    <title>Registeres USers Login Page</title>
    <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
    <body>
    <%--debugging code--%>
    <%@ include file="debug.jsp" %>
    <table width="1049" cellpadding="5" align="center">
      <tr>
        <td width="2378"><div align="center">
          <h2 align="center"> User Registration</h2>
           <p>
         <c:url var="HmePgeURL"  value="/cw/router/home"  scope="page"/>
         <a href="${HmePgeURL}">Home</a>  <c:url var='BSPgeURL'  value='/cw/router/login'  scope='page'/>
         <a href="${BSPgeURL}">Buy or Sell</a>
         </p>
        </div></td>
      </tr>
    </table>
    <p align="center"> </p>
    <p>This website is only open to members of the De MontFort University.
    You will need a current @learner.dmu.ac.uk e-mail address in order to register.</p>
    <p> If you've already registered for one site you do not need to register again </p>
    <c:url value="/cw/router/userregistration" var="UregPgeURL" scope="page"/>
    <form name="frmregister" method="post" action="${UregPgeURL}">
      <div>
      <table width="726" height="285" border="0" align="left" cellpadding="2" cellspacing="0">
        <tr>
          <td width="157" align="right" >Name:</td>
          <td width="561" > <input name="txtname" type="text" value="${param.txtname}"/> </td>
        </tr>
          <c:if test="${!empty requestScope.reqInvalidUserName}">
          <c:out value="${requestScope.reqInvalidUserName}"/>
          </c:if>
        <tr>
          <td width="157" align="right" >Department</td>
          <td align="left" >
              <select name="txtdepartment" value="${param.txtdepartment}" >
                <option></option>
                <option value="Faculty of Art and Design">Faculty of Art and Design</option>
                <option value="Faculty of Business and Law">Faculty of Business and Law</option>
                <option value="Faculty of Computing Sciences and Engineering">Faculty of Computing Sciences and Engineering</option>
                <option value="Faculty of Health and Life Sciences">Faculty of Health and Life Sciences</option>
                <option value="Faculty of Humanities">Faculty of Humanities</option>
              </select>
          </td>
        </tr>
          <tr>
            <td align="right" >Programme</td>
            <td ><input type="text" name="txtprogramme"  value="${param.txtprogramme}" />
              (eg: BIS,SE) </td>
          </tr>
          <tr>
          <td align="right" >Telephone Number: </td>
          <td ><input name="txtphonenum" type="text" value="${param.txtphonenum}" /></td>
        </tr>
        <tr>
          <td align="right" >Date Of Birth: </td>
          <td ><input name="txtday" type="text" size="15" value="${param.txtdob}" />(of format YYYY-MM-DD)</td>
          </tr>
        <tr>
          <td align="right" >Username</td>
          <td align="left" >
              <input name="txtuserid" type="text"  size="15"  value="${param.txtuserid}" />
            (eg. p07269027 from [email protected])</td>
            <c:if test="${!empty requestScope.reqInvalidUserId}">
            <c:out value="${requestScope.reqInvalidUserId}"/>
            </c:if>
        </tr>
        <tr>
          <td align="right" >Password</td>
          <td align="left" >
              <input name="txtpassword" type="password"  size="15" value="${param.txtpassword}" />
          </td></tr>
         <c:if test="${!empty requestScope.reqInvalidPassword}">
          <c:out value="${requestScope.reqInvalidPassword}"/>
          </c:if>
        <tr>
          <td align="right" >Confirm Password </td>
          <td align="left" >
              <input name="txtpasswordconf" type="password" size="15"  />
          </td>
        </tr>
        <tr>
          <td colspan="2" align="center">
            <input name="frmsubmit" type="submit" value="Register User" />
            <input type="reset" name="Reset" value="Reset" />
          </td>
        </tr>
      </table>
         <c:if test="${!empty requestScope.reqQueryErrorMessage}">
          <c:out value="${requestScope.reqQueryErrorMessage}"/>
          </c:if>
         <c:if test="${!empty requestScope.reqInvalidUpdate}">
          <c:out value="${requestScope.reqInvalidUpdate}"/>
          </c:if>
    </div>     
    </form>
    </body>
    </html>
    proregistration.jsp ( registration process jsp)
    <?xml version="1.0" encoding ="UTF-8"?>
    <%@ taglib prefix="c"   uri="http://java.sun.com/jsp/jstl/core" %>
    <%@ taglib prefix="fmt" uri="http://java.sun.com/jsp/jstl/fmt" %>
    <%@ taglib prefix="sql" uri="http://java.sun.com/jsp/jstl/sql" %>
    <%@ taglib prefix="x"   uri="http://java.sun.com/jsp/jstl/xml" %>
    <%@ taglib prefix="fn"  uri="http://java.sun.com/jsp/jstl/functions" %>
    <%-- \WEB-INF\jsp\cwjsps\probooksforsale.jsp --%>
    <%-- Probookforsale --%>
    <%-- skip field validation and provide blankpage if first time in --%>
    <c:if test="${empty param.frmsubmit}">
    <c:set var="reqOutcome" scope="request" value=" "/>
    <jsp:forward page="/WEB-INF/jsp/cwjsps/userregistration.jsp"/> <%-- initial request --%>
    </c:if>
    <%-- validate txtname --%>
    <c:if test="${empty param.txtname}">
    <c:set var="reqInvalidUserName" scope="request" value= "User Name Cannot Be Empty"/>
    </c:if>
    <%-- validate txtuserid --%>
    <c:if test="${empty param.txtuserid}">
    <c:set var="reqInvalidUserId" scope="request" value= "User ID Cannot Be Empty"/>
    </c:if>
    <%-- validate txtpassword--%>
    <c:if test="${empty param.txtpassword}">
    <c:set var="reqInvalidPassword" scope="request" value= "Password Cannot Be Empty"/>
    </c:if>
    <%-- if userid invalid or username invalid  --%>
    <%-- redisplay form with originl typed-in data and with errors marked --%>
    <c:if test="${empty param.txtname or empty param.txtuserid}">
    <c:set var="reqOutcome" scope="request" value= "failure" />
    <jsp:forward page="/WEB-INF/jsp/cwjsps/userregistration.jsp"/> <%-- failure --%>
    </c:if>
    <c:catch var="pgeQueryError">
    <sql:update var="pgeRowCount" scope="page" >
    <%-- insert details to trader table --%>
    INSERT INTO trader(dbTraderName,dbTraderDepartment,dbTraderProgramme,dbTraderPhoneNum ,dbTraderDOB,dbTraderPNumber,dbTraderPwd)
    VALUES(?,?,?,?,?,?,?)
    <sql:param value="${param.txtname}"/>
    <sql:param value="${param.txtdepartment}"/>
    <sql:param value="${param.txtprogramme}"/>
    <sql:param value="${param.txtphonenum}"/>
    <sql:param value="${param.txtdob}"/>
    <sql:param value="${param.txtuserid}"/>
    <sql:param value="${param.txtpassword}"/>
    </sql:update>
    </c:catch>
    <%-- check For query Error --%>
    <c:if test="${not empty pgeQueryError}">
    <c:choose>
    <%-- check duplicate record --%>
    <c:when test="${pgeQueryError.rootCause.errorCode =='1062'}">
    <c:set var="reqQueryErrorMessage" scope="request" value="User already Registered - Duplicate Record" />
    <jsp:forward page="/WEB-INF/jsp/cwjsps/login.jsp"/>
    </c:when>
    <c:otherwise>
    <%-- database error --%>
    <c:set var="reqQueryErrorMessage" scope="request" value="Database Error" />
    <jsp:forward page="/WEB-INF/jsp/cwjsps/userregistration.jsp"/>
    </c:otherwise>
    </c:choose>
    <c:set var="reqOutcome" scope="request" value="failure" />
    <jsp:forward page="/WEB-INF/jsp/cwjsps/userregistration.jsp"/>
    </c:if>
    <%-- check For no rows returned --%>
    <c:if test="${pgeRowCount !=1}">
    <c:set var="reqInvalidUpdate" scope="request" value="*** rowCount not = 1"/>
    <c:set var="reqOutcome" scope="request" value="failure"/>
    <jsp:forward page="/WEB-INF/jsp/cwjsps/userregistration.jsp"/> <%-- failure --%>
    </c:if>
    <%-- Otherwise --%>
    <%-- Outcome is success --%>
    <c:if test="${pgeRowCount ==1}">
    <c:set var="reqOutcome" scope="request" value="success" />
    <jsp:forward page="/WEB-INF/jsp/cwjsps/login.jsp"/> <%-- success --%>
    </c:if>
    router.jsp  ( maps the jsp page based on success and failure)
    <?xml version="1.0" encoding ="iso-8859-1"?>
    <%-- /WEB-INF/jsp/cwjsps/router.jsp --%>
    <%@ taglib prefix="c"   uri="http://java.sun.com/jsp/jstl/core" %>
    <%@ taglib prefix="fmt" uri="http://java.sun.com/jsp/jstl/fmt" %>
    <%@ taglib prefix="sql" uri="http://java.sun.com/jsp/jstl/sql" %>
    <%@ taglib prefix="x"   uri="http://java.sun.com/jsp/jstl/xml" %>
    <%@ taglib prefix="fn"  uri="http://java.sun.com/jsp/jstl/functions" %>
    <%--  setup session if one does not exist --%>
    <%@ page session="true" %>
    <%-- set up debug variable --%>
    <c:set var="sessDebug" scope="session" value="true"/>
    <%-- get pathinfo information  from the request --%>
    <%-- this defines which use case has been requested --%>
    <c:set var="pgePathInfo" scope="page" value="${pageContext.request.pathInfo}" />
    <%-- uc02 : Login --%>
    <c:if test="${pageScope.pgePathInfo =='/home'}" >
    <jsp:forward page="/WEB-INF/jsp/cwjsps/home.jsp"/>
    </c:if>
    <c:if test="${pageScope.pgePathInfo =='/login'}" >
    <jsp:forward page="/WEB-INF/jsp/cwjsps/prologin.jsp"/>
    </c:if>
    <%-- uc01 : View Details Of Books For Sale --%>
    <c:if test="${pageScope.pgePathInfo =='/viewbooksforsale'}" >
    <jsp:forward page="/WEB-INF/jsp/cwjsps/probooksforsale.jsp"/>
    </c:if>
    <%-- uc01 : process User registration--%>
    <c:if test="${pageScope.pgePathInfo =='/userregistration'}" >
    <jsp:forward page="/WEB-INF/jsp/cwjsps/proregistration.jsp"/>
    </c:if>
    <%-- uc01 : debug --%>
    <c:if test="${pageScope.pgePathInfo =='/debug'}" >
    <jsp:forward page="/WEB-INF/jsp/cwjsps/debug.jsp"/>
    </c:if>
    <%-- uc01 : view Traders Own View  --%>
    <c:if test="${pageScope.pgePathInfo =='/Traderhomepage'}" >
    <jsp:forward page="/WEB-INF/jsp/cwjsps/Traderhomepage.jsp"/>
    </c:if>
    <%-- otherwise --%>
    <jsp:forward page="/WEB-INF/jsp/cwjsps/home.jsp"/>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          &nb

    Hi..
    Correcting the record from PSA is temporary solution depends on u r criticality....
    Only Solution is to correct the record at source system level... Generally Material master data record is imp so just try to fix temporarily so that it vl not affect u r loads until it is corrected at Source System level..
    Note: inform the problem to u r co-ordinator and try to correct it ASAP... and explain the temp solution(PSA correction)...
    cheers..

  • 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..

  • Database error says connect by clause for Oracle10g

    Hi All,
    I am trying to select details from anodestable where error says SQLException connect by clause is required in this query block.
    Please respond if you know how to resolve this error.
    Thanks in advance.
    Bye

    Katheresh wrote:
    Hi All,
    I am trying to select details from anodestable where error says SQLException connect by clause is required in this query block.
    Please respond if you know how to resolve this error.
    Thanks in advance.
    ByeCould you post the SQL code and the error you got?

  • Getting error message when passing data into table: Primary Key

    Getting an error in a process that is feeding the invoice creation in SAP, violation of PRIMARY KEY constraint 'INV1_Primary', cannot insert duplicate key in object 'INV1'. I assume this is due to duplicate key values being passed into the table INV1, however I get this error even when I am passing unique record combinations of the key fields docentry and linenum. This is on 2005A SP01.
    Thanks

    Hi Peter,
    Could you provide a code sample of the routine that is causing the error please?
    It sounds like a data corruption issue (though it could possibly be a bug in the DI API). I recommend you speak to SAP support. There is a utility that can validate the document numbering but you'll need to speak to SAP support before you run this as it can have other negative effects, depending on the state of your data. They may ask for a copy of your database to test.
    Kind Regards,
    Owen

  • F7N Spool: RT_DELETE Reports Error 64 for Table

    Hello All,
    In our PRD system in SM21, we are getting below errors daily
    ERROR:
    F71 Error in TemSe Management
    F7N Spool: RT_DELETE Reports Error 64 for Table
    F6H Database error: TemSe->XRTAB(4)->64 for table TST01 key
        [100]SPOOL0000003637 ,1
    F6H Database error: TemSe->XRTAB(4)->64 for table TST01 key
        [100]SPOOL0000003637 ,1
    1) F71 Error in TemSe Management
        Documentation for system log message F7 1 :
        Error in the C coding of the spooler.
        Message is no longer output.
    2) F7N Spool: RT_DELETE Reports Error 64 for Table
         Documentation for system log message F7 N :
        The RTAB interface has reported an unexpected error return code to the
        spooler. The RTAB function used was 'RT_DELETE'. The error number used
         in the message can be translated using 'dbrtab.h' and 'dbglobal.h'.
         Check whether there has been a syslog entry from the RTAB interface
         before this.
    3) F6H Database error: TemSe->XRTAB(4)->64 for table TST01 key
        [100]SPOOL0000003637 ,1
    Documentation for system log message F6 H :
    Database error:  TemSe->&A(&B)->&C for table &D key &a
                              !  !    !            Table name
                              !  !    Error number
                              !  Function number
                              Database access module
    Possible database access modules
    RTAB
    Direct access with entire or partial primary key
    XRTAB
    direct access with entire or partial primary key for all clients
    INCLUDE 'RSTS_RTAB_FUNCTIONS' OBJECT DOKU ID TX
    INCLUDE 'RSTS_RTAB_ERRORS' OBJECT DOKU ID TX
    INCLUDE 'RSTS_TABLES' OBJECT DOKU ID TX
    Plese suggest on this.
    Thanks in advance.
    Regards,
    Pratyu

    Perform a Spool consistency check.
    Goto Tcode SP12. In the menu choose "Temse Data Storage" -> "Consistency check".
    In the output, delete all the inconsistencies.
    Edited by: Debi Prasad Goswami on May 10, 2010 7:11 AM

  • Database error found in SM21 logs

    Hi,
    we are facing problem with too many system logs as :
    Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUILD key.
    Found no information on google. If anyone might have come accross this problem or know the solution plz reply..
    00:17:39 DIA 000                       F6H Database error: TemSe->RTAB-S/G(8)->1 for table TCPSBUI
    Program name........
    Problem class....... K    SAP Web AS Problem
    Development class... STMS
    Further details for this message type
    Module name......... rscpgdio
    Location............  15
    Error text.......... RTAB-S/G&8&1&TCPSBUILD                     &
    Documentation for system log message F6 H :
    Database error:  TemSe->&A(&B)->&C for table &D key &a
                              !  !    !            Table name
                              !  !    Error number
                              !  Function number
                              Database access module
    Possible database access modules
    RTAB
    Direct access with entire or partial primary key
    XRTAB
    direct access with entire or partial primary key for all clients
    INCLUDE 'RSTS_RTAB_FUNCTIONS' OBJECT DOKU ID TX
    INCLUDE 'RSTS_RTAB_ERRORS' OBJECT DOKU ID TX
    INCLUDE 'RSTS_TABLES' OBJECT DOKU ID TX
    Thanks in advance.
    Tyson

    Hello,
    Please make sure you use the latest kernel and dbsl. ( see note 19466 to download the latest)
    Do you have any database errors in alert<SID>.log
    ($oraclehome\saptrace\background), listener.log ($oraclehome\network\log) and sqlnet.log?

Maybe you are looking for

  • Migrate from GUI to web based application

    what's the easy and the fast method to migrate java GUI application to a web based aplpication. thanks in advance for information

  • Can someone tell me how to delete EditRegion4.

    Can someone tell me how to delete an "exra" EditRegion4" i have in Dreamweaver CS4? I have 5 total edit regions on each page, but somehow I have 2 of the EditRegion4 on one of the poem pages. The one region4 is total empty so since I can't seem to de

  • Long time to sleep

    Hi, When I first got my mbp it would go into sleep within a few seconds of closing the lid. Recently it has started to take some time in going to sleep when I close the lid, or when I select sleep from the apple menu. I just timed it and it took 40 s

  • SQLite version - AIR 1.0 vs 1.5 vs 2.0

    I've come to understand that AIR uses its own built-in version of SQLite but it's been hard to grasp what version is being used in each AIR version? Has there been any upgrades to the SQLite version from 1.0 to 1.5 to 2.0beta? I did notice that Neste

  • How to compile forms in a UNIX CLI?

    Can anybody tell me how to compila a form in UNIX with Oracle 6 or 6i? I know I have to use the 'f60gen' or 'f60genm' commands, but I don't know witch arguments I have to use. Thanks in advance, Pablo.