Duplicate queries
We have duplicate queries and plan to report ANALYZE_RSZ_TABLES to change the name in some and delete in others.
Part of our checks has referred to considerations that have been made in SAP Note 792779.
However, we have the following scenario:
We have a duplicate query that is shown in RSRT whilst the other appears in the Info Area Open Dialog box. We will be changing the name of the one that appears in RSRT. After the change will the other version of the query appear in RSRT if I run with COMPID and secondly will the changed query name appear in RSRT and the Info Area Open Dialog box with its new COMPID?
Thank you in advance for your help
Hi JC,
I think you can use Tcode RSZDELETE to delete the duplicate UIDs of elements or any query objects.
Test it in dev box / sandbox before using it in prod.
Thanks
Similar Messages
-
Duplicate Queries and Query Components in BI Production Box
Hi:
We have a situation where we have duplicate queries and query components in our Production BI box.
The problem was caused by transports. We have a development landscape and a support landscape where both are transporting separately up to the BI Production Box.
For example, query ABC was created in the development landscape and transported up to our production box.
The same query ABC was created in our support landscape and transported up to our production box.
Now in the production box we have 2 queries ABC with the same technical name and description but with different active ELTUIDs.
We have found the program ANALYZE_RSZ_TABLES and it does show us this problem in our production box with many queries and query components.
The question is how do we get rid of the duplicate ELTUIDs in our Production box and how do we stop this from happening during transport?
any suggestions would be helpful.Hi JC,
I think you can use Tcode RSZDELETE to delete the duplicate UIDs of elements or any query objects.
Test it in dev box / sandbox before using it in prod.
Thanks -
SQL Dev 2.1 - Session browser Active SQL showing duplicate queries
Haven't noticed this before in any other version but then hadn't realy been looking but when i use the session browser to check code running on the DB in the ACTIVE SQL tab i ocassionally see duplicate sql statments, which can be misleading, see below for an example.
SELECT SUM(AID.AMOUNT),
DECODE(APS.PAYMENT_STATUS_FLAG,'Y','Paid','P','Partially Paid','Not Paid')
FROM PO_LINE_LOCATIONS_ALL PLL,
PO_DISTRIBUTIONS_ALL PDA,
AP_INVOICE_DISTRIBUTIONS_ALL AID,
AP_INVOICES_ALL AIA,
AP_PAYMENT_SCHEDULES_ALL APS
WHERE PLL.PO_LINE_ID = :B1
AND PLL.LINE_LOCATION_ID = PDA.LINE_LOCATION_ID
AND PDA.PO_DISTRIBUTION_ID = AID.PO_DISTRIBUTION_ID
AND AIA.INVOICE_ID = AID.INVOICE_ID
AND APS.INVOICE_ID = AIA.INVOICE_ID
AND AIA.CANCELLED_BY IS NULL
GROUP BY DECODE(APS.PAYMENT_STATUS_FLAG,'Y','Paid','P','Partially Paid','Not Paid')
SELECT SUM(AID.AMOUNT),
DECODE(APS.PAYMENT_STATUS_FLAG,'Y','Paid','P','Partially Paid','Not Paid')
FROM PO_LINE_LOCATIONS_ALL PLL,
PO_DISTRIBUTIONS_ALL PDA,
AP_INVOICE_DISTRIBUTIONS_ALL AID,
AP_INVOICES_ALL AIA,
AP_PAYMENT_SCHEDULES_ALL APS
WHERE PLL.PO_LINE_ID = :B1
AND PLL.LINE_LOCATION_ID = PDA.LINE_LOCATION_ID
AND PDA.PO_DISTRIBUTION_ID = AID.PO_DISTRIBUTION_ID
AND AIA.INVOICE_ID = AID.INVOICE_ID
AND APS.INVOICE_ID = AIA.INVOICE_ID
AND AIA.CANCELLED_BY IS NULL
GROUP BY DECODE(APS.PAYMENT_STATUS_FLAG,'Y','Paid','P','Partially Paid','Not Paid')
SELECT SUM(AID.AMOUNT),
DECODE(APS.PAYMENT_STATUS_FLAG,'Y','Paid','P','Partially Paid','Not Paid')
FROM PO_LINE_LOCATIONS_ALL PLL,
PO_DISTRIBUTIONS_ALL PDA,
AP_INVOICE_DISTRIBUTIONS_ALL AID,
AP_INVOICES_ALL AIA,
AP_PAYMENT_SCHEDULES_ALL APS
WHERE PLL.PO_LINE_ID = :B1
AND PLL.LINE_LOCATION_ID = PDA.LINE_LOCATION_ID
AND PDA.PO_DISTRIBUTION_ID = AID.PO_DISTRIBUTION_ID
AND AIA.INVOICE_ID = AID.INVOICE_ID
AND APS.INVOICE_ID = AIA.INVOICE_ID
AND AIA.CANCELLED_BY IS NULL
GROUP BY DECODE(APS.PAYMENT_STATUS_FLAG,'Y','Paid','P','Partially Paid','Not Paid')
The reason seems to be that the Session Browser query:
SELECT REPLACE(q.sql_text,chr(0)) sql_text
FROM v$session s,
v$sql q
WHERE s.sql_address = q.address
AND s.sql_hash_value = q.hash_value
AND s.sid = :SID
is picking up all the different child number queries from v$sql, is there anyway to only pick up the child that you are using to avoid the strange query output?
Thanks in advance
TrottyHello All;
The front end is Oracle Forms/ Reports 6i Patch 16.
I will try TKprof.
I found here someone asking on the same case,
Database is too slow.....
He was advices to 1- Compute Statistics 2- reorganize tables 3- re-build indexes
I done it in the order a-Import Tables b-Rebuild indexes c-Compute Statistics.
Shall I do it in order 1 2 3 ? or 1 & 3 will be ok?
Can I issue
sql> Alter table <name> move tablespace <tablespace_name>;
on the original tablespace or I need to provide new tablespace?
Best Regards,
Naji Ghanim -
Hi All,
We have a scenario where we are developing and transporting a query from sandbox to production. If the same query with the same techincal name is developed and transported from another system to production will the query be duplicated.
Thanks in Advance.The query keys aren't the technical name, it is an internally assigned GUID. If you take a look at the RSZELTDIR table, the key is ELTID (Query Element ID) which is this internally assigned GUID. The MAPNAME column on this table is where the technical name of the query is stored.
So, if you create two queries with the same technical name, you can transport them both through your landscape and they will both coexist. If you're using the SAP BW Portal, updates to the published query will be affected. If you modify a query that has the same technical name, but isn't the query that was published (different Query Element ID), the query in the portal will not change. -
2 queries with same technical name
Hi,
I have just opened this <b>QA</b> system. I find that there are two queries with the same technical name. The query definition is also the same. But it shows twice when I search for them.
I thought the system only allows a single technical name to be created once.
Please help me understand how this may have happned? And also how I can delete one of them without effecting the web templates and workbooks where this query is used.
Thanks
NEWBWYou can use the ABAP Program RENAME_DUPLICATE_ELEMENTS to rename the duplicate queries.
The system tracks query objects using the 25 char UID and not the technical name of the query. In some cases you will end up with 2 queries with the same technical name usually with transports from multiple systems.
You can also use the report ANALYZE_RSZ_TABLES to proactiveley analyze these kinds of issues in the system.
Thanks -
when i wake up my computer the screen will come to life and then go blank. the computer is still on because i have to manually turn it off and restart. sometimes it takes a couple restarts to get it back. Once it faded out but most of the time it just goes black. Any clues as to what is going on? Anyone??
Does it only happen with Microsoft Office applications? Sometimes this can also be caused by a memory leak, occupying lots of system resources to the point that Microsoft Office needs to 'queue' the text up in the buffer for display, hence the partial blanking.
Check you task manager - does the Physical Memory Usage exceed 85%?
Rather than using System Update to check for the graphics driver update, go straight to Lenovo's support site to get the driver from there. There are some times where system update doesn't display updates when there's actually one. Compare the driver version on the support site against that in the device manager's display card properties page, and update if necessary.
If you are using Firefox Developer Edition without e10s (electrolysis mode) and running some flash based app memory leaks can be very common. There is currently no solution to this issue, there are workarounds however. Either don't run any flash-based apps, don't run Firefox Developer Edition at all, or downgrade to the stable release of Firefox.
Let me know if this helps, please mark the respective posts s a solution IF it has helped you to solve the problem. This will make it much, much easier for others encountering the same issue to get to their answer, avoiding any duplicate queries.
Thanks!
-it_geek -
Hi Experts,
Is transport of new variant (from development to production) for a query already available in production possible?
If yes, please guide on the same.
Regards,
RohitRohit,
There are some issues with transporting queries already available in Production.
1. If the query was created natively in the Production System - delete the query using RSZDELETE before transporting to Production.
If the query was however transported into Production and then changed in Production - you need not delete anything before transporting.
In case of case 1 - this leads to duplicate queries in the production system.
Arun -
Deleting query in production server
Hi,
Some of the duplicate queries are deleted in Development server, which are not transported to other servers by some mistakes.
Now we need to delete those duplicate queries in production server.
Plsease suggest immediately.
Regards,
ArchanaHi,
use the Tcode RSZDELETE.
If you dont have authorization use the program COMPONENT_REORG.
Regds,
Shashank -
Duplicated query due to parallel development environment
We have a rather unpleasant situation in our BW environment after our upgrade to BI 7.0 and use of a parallel BW development machine during the upgrade.
Some of the queries seems to have multiple copies with the same technical name in production and development. The queries would have the same technical name but there are diffrent COMPUID generated when I see the RSZCOMPDIR table.
The problem is that when I make changes to the query and transport it to production, the production query with the same technical name but a different COMPUID does not get over writen. So the users don't see the fix. Unfortunately, we have a very large number of users and deleting the original queryin production is not an option. They all have their bookmarks and views etc. In production, I do see a duplicated query with same tech name but a different COMPUID same as what we have in development but not included in the roles. The added problem is that when I try to open the query with the technical name in query designer in production, it opens up the modified one but when I try to execute it from the same query designer, it executes the old one that is active.
In my opinion, a back transport would fix the problem as we'll have the same GUID query back in development and then it can be fixed or modified and transported wherever. Has anyone seen such problem and is there a cleaner solution?
Thanks for the help.
Bilal
Edited by: Bilal Ghayur on Aug 11, 2008 2:17 PMHi,
Execute the report 'ANALYZE_RSZ_TABLES' in your system where there are duplicate queries selecting the tables 'RSRREPDIR, RSZCOMPDIR and RSZELTDIR and the version 'A. This report will display all the incosistency with the reporting components in your system and hence will take sometime to fdisplay the output: 1-2 mins. In the report result, click on the 'Display' icon against 'Components with duplicated technical names.' under the heading 'Table RSZCOMPDIR'. You will now see the queries which have the same technical name but different COMPID. You then identify the query that you do not want & rename it to a different technical name by changing the entry under 'Rename query components...'.
I have used this report in 3.0B & 3.5.
Regards,
Shilpa -
El programa me indica que no responde y se cuelga muchas veces
se queda colgado unos segundo y luego vuelve a responder. no puedo trabajar asi... me desespero
You have already asked this question only a few minutes after the first time. Please do not create duplicates queries for same question. Please keep all responses in the same question otherwise the continuity of the conversation can get confusing.
https://support.mozilla.org/en-US/questions/1029477
Usted ya ha hecho esta pregunta sólo unos minutos después de la primera vez . Por favor, no crear consultas duplicados para la misma pregunta . Por favor, mantenga todas las respuestas en la misma pregunta de otra manera la continuidad de la conversación puede ser confuso. -
Queries: duplicate info when executing a HR query
Hi.
Friends, i trying to do a query with info of two infotipes: 21 and 482 (aditional info of it21), when i execute the query the result it's a cartesian product (wrong result).
For example:
DATA
IT21
PERNR Subty Name
1 10 ssssss
2 11 dddddd
IT482
Pernr subty identity card
1 10 5
2 11 6
Result
Wrong Result with cartesian product of the query:
PERNR subty name it482-subty it482-identity card
1 10 ssssss 10 5
1 11 dddddd 10 5
1 10 ssssss 11 6
1 11 dddddd 11 6
The correct result must be:
PERNR subty name it482-subty it482-identity card
1 10 ssssss 10 5
1 11 dddddd 11 6
I think that the join of the PNPCE logical database it's performed using just personel number (pernr), how could i solve this issue?
Thanks in advance.
Albio.-
Solved in HCM Forum: Re: Queries: duplicate info when executing a HR query
Edited by: Albio Manuel Vivas on Aug 16, 2011 7:35 PMI found where to put the switch, but it doesn't work.
I did this:
1) in the infogroup (tx sq02): goto/ code / data. Then i typed:
*$HR$ [P0482]
*$HR$ PRIMARY_INFTY = 'P0021'
2) save
3) verify
4) generate
Then i use the transaction S_PH0_48000513 - Ad-hoc-Query , and create a query, i save it, and execute, then the result it's wrong. I check the program generated by the query, and search for this text: 'hr-log' where are supposed that the code must appears, and the code that i added doesn't exits.
Any idea?
Thanks in advance.
Albio.-
Edited by: Albio Manuel Vivas on Aug 16, 2011 6:14 PM -
Queries regarding Boleto and Duplicata
Hi All,
I am a new member of this site.We have got a requirement for developing sap scripts for Brazil. Did anyone happen to work on Boleto and duplicata?
The standard forms available are J_1b_boleto_itau and j_1b_duplicata.
Can anyone please explain the functinality of the driver program RFFOBR_D which is for both the forms mentioned above?
Please help me out.1) IS OMS 10g also going out of support in July. If yes, what is latest version availableTo know about support Life cycle you could review the below document :
www.oracle.com/us/support/.../057419.pdf
Or
MOS notes :FAQ for Products in Extended Support [ID 757445.1]
Latest version : 12c
2) Can we upgrade just repository DB (OEM DB) without upgrading OMS software (as oracle 10g is going out of support)yes
As view just to know :
http://learnwithme11g.wordpress.com/tag/upgrade-oem/
3) Steps involved in upgrading OMS from 10g to 11g.Review this :
Master Index for Grid Control OMS and Repository Installation, Patching and Upgrade [ID 1277921.1] -
Need Different Selection screen for different Queries in a Workbook
Hi,
I have created a workbook with Multiple tabs in BI 7.0. Each Tab has different Queries and each query has different Selection screens (Variable Selections).
When i open the workbook and refresh it, the selection screen is appearing only for one query. All the queries are refreshed by this single selection screen, though each query has different Variable selections. What i need is a seperate selection screen i.e seperate Variable selection appearing for each queries, when i refresh each one of them.
Is it possible to do this? If anybody has tried this, help me in solving this issue. Thanks for ur time.
Regards,
MuraliMurali,
If you un-check the 'Display Duplicate Variables Only Once' this WILL solve your problem.
When you Refresh, you should be presented with a single variable selection dialog box, but it should contain an area for each Query (DataProvider) that is embedded in the Workbook.
This is the case if the queries are all on the same tab, or on different tabs.
However, if you have multiple tabs each with a query on it, each query must have it's own DataProvider. If all queries are based on the same DataProvider, it will not work as the Workbook only 'sees' one Query for which it needs variable input.
If you REALLY want multiple variable selection dialog boxes, then maybe the best way to do this is to have the queries in separate Workbooks.
If you don't want the User to have to open 5 queries manually, you could use a Macro in each Workbook that runs on opening, to open the next Workbook in the sequence.
I hope this makes sense!
Regards
Steve -
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 '<a href='/home/the_user/.local/share/akonadi/db_data/mysql.err'>/home/the_user/.local/share/akonadi/db_data/mysql.err</a>' 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.. -
To find Queries by InfoObjects
Hi SDN Community
Here is a reversal of a post made by another developer
List of infoobjects used in a Query
This has the reverse logic... thanks for the tip.
*& Report ZBW_FIND_CHARACTERISTICS_QUERY
SAP Consulting BW Tools:
*& Find Characteristics in BEx Queries using ABAP
*& List of infoobjects used in a Query
*& Developer: WBHADS 07/06/2011
REPORT ZBW_FIND_CHARACTERISTICS_QUERY.
PARAMETER: CHARACT LIKE rszrange-IOBJNM.
DATA: s_characteristic LIKE rszrange-IOBJNM.
s_characteristic = CHARACT.
DATA: lv_count TYPE i.
DATA: lv_count1 TYPE i.
DATA: lv_count2 TYPE i.
Data Declaration
DATA: D_MSG_TEXT(50).
DATA: lc_DIRECTORY(30) TYPE c.
DATA: P_FILE(128).
DATA: FILENAME(128).
DATA: lc_query(60) TYPE c.
DATA: lc_date(30) TYPE c.
DATA: lc_time(30) TYPE c.
DATA: lc_start_time(60) TYPE c.
DATA: lc_syst(30) TYPE c.
DATA: lc_exception(120) TYPE c.
RSZELTDIR Directory of the reporting component elements
RSZELTTXT Texts of reporting component elements
RSZELTXREF Directory of query element references
RSRREPDIR Directory of all reports (Query GENUNIID)
RSZCOMPDIR Directory of reporting components
RSZRANGE Selection specification for an element
RSZSELECT Selection properties of an element
RSZELTDIR Directory of the reporting component elements
RSZCOMPIC Assignment reuseable component <-> InfoCube
RSZELTPRIO Priorities with element collisions
RSZELTPROP Element properties (settings)
RSZELTATTR Attribute selection per dimension element
RSZCALC Definition of a formula element
RSZCEL Query Designer: Directory of Cells
RSZGLOBV Global Variables in Reporting
data: gi_data like rszrange occurs 0 with header line.
Determine the queries
tables:
RSZELTTXT,
rszeltdir,
rszeltxref,
rszrange.
data: begin of lt_line occurs 0,
ELTUID like RSZELTDIR-ELTUID, "char 25
MAPNAME like RSZELTDIR-MAPNAME, "char 30
end of lt_line.
data: begin of lt_line1 occurs 0,
SELTUID like rszeltxref-SELTUID, "char 25
TELTUID like rszeltxref-TELTUID, "char 25
LAYTP like rszeltxref-LAYTP, "char 30
end of lt_line1.
data: begin of lt_line2 occurs 0,
ELTUID like rszrange-ELTUID, "char 25
IOBJNM like rszrange-IOBJNM, "char 25
end of lt_line2.
data: lt_tab like standard table of lt_line initial size 0.
data: lt_tab1 like standard table of lt_line initial size 0.
data: lt_tab2 like standard table of lt_line initial size 0.
data: lt_line20(128) TYPE c. " LIKE RSZELTXREF-SELTUID.
data: lt_line30(128) TYPE c. " LIKE RSZELTXREF-SELTUID.
clear lt_line.
lv_count = 0.
lv_count2 = 0.
Loop through all the queries
select * from RSZELTDIR
into corresponding fields of lt_line
where DEFTP = 'REP'
and OBJVERS = 'A'.
Filter by the Z Developed Queries
IF lt_line-MAPNAME CP 'Z*'.
clear lt_line20.
Get the Query Long Name
select single * from RSZELTTXT
into lt_line20
where eltuid = lt_line-eltuid "rszeltdir-eltuid
and objvers = 'A'
and langu = 'EN'.
Find all the query elements within the query
select * from rszeltxref
into corresponding fields of lt_line1
where seltuid = lt_line-eltuid "rszeltdir-eltuid
and objvers = 'A'.
IF lt_line1-laytp = 'FIX' OR lt_line1-laytp = 'COL' OR lt_line1-laytp = 'ROW'.
Determine if the Query Element is matching to the characteristic
select * from rszrange "appending table gi_data
into corresponding fields of lt_line2
where eltuid = lt_line1-teltuid "rszeltxref-teltuid
and objvers = 'A'
and enum = 1.
Populate tables
IF lt_line2-IOBJNM = s_characteristic.
append lt_line-MAPNAME to lt_tab.
lv_count = lv_count + 1.
ENDIF.
endselect.
ENDIF.
endselect.
ENDIF.
endselect.
sort lt_tab by MAPNAME.
delete adjacent duplicates from lt_tab comparing MAPNAME.
DIRECTORY represents path where file is stored .
lc_DIRECTORY = '/interfaces/EDW/data/CSM/'.
CONCATENATE 'EDW Queries by Characteristic -' SY-DATUM
'.txt' into P_FILE SEPARATED BY SPACE.
CONCATENATE lc_DIRECTORY P_FILE into FILENAME.
Opening the Log File
OPEN DATASET FILENAME FOR OUTPUT IN TEXT MODE
ENCODING DEFAULT.
IF SY-SUBRC NE 0.
WRITE: 'File cannot be opened. Reason:'. ", D_MSG_TEXT.
EXIT.
ENDIF.
CONCATENATE 'System Date -' SY-DATUM 'YYYYMMDD' into lc_date
SEPARATED BY SPACE.
CONCATENATE 'EDW System -' SY-SYSID into lc_syst
SEPARATED BY SPACE.
TRANSFER lc_date TO FILENAME.
TRANSFER lc_start_time TO FILENAME.
TRANSFER lc_syst TO FILENAME.
Queries for the parameters
loop at gi_data into lt_line.
loop at lt_tab into lt_line.
TRANSFER lt_line TO FILENAME.
endloop. "Query Loop
Closing the Log File
CLOSE DATASET FILENAME.We have successfully created an ABAP program to do this.
Thank you.
Simon
*& Report ZBW_FIND_CHARACTERISTICS_QUERY
SAP Consulting BW Tools:
*& Find Characteristics in BEx Queries using ABAP
*& List of infoobjects used in a Query
*& Developer: WBHADS 07/06/2011
REPORT ZBW_FIND_CHARACTERISTICS_QUERY.
PARAMETER: CHARACT LIKE rszrange-IOBJNM.
PARAMETER: VARIABN LIKE RSZGLOBV-VNAM.
DATA: query_name TYPE RSZCOMPID.
DATA: s_varname TYPE RSZGLOBV-VNAM,
s_varnameu TYPE RSZGLOBV-VARUNIID.
DATA: s_characteristic LIKE rszrange-IOBJNM.
DATA: lv_count TYPE i.
DATA: lv_count1 TYPE i.
DATA: lv_count2 TYPE i.
Data Declaration
DATA: D_MSG_TEXT(50).
DATA: lc_DIRECTORY(30) TYPE c.
DATA: P_FILE(128).
DATA: FILENAME(128).
DATA: lc_query(60) TYPE c.
DATA: lc_date(30) TYPE c.
DATA: lc_time(30) TYPE c.
DATA: lc_start_time(60) TYPE c.
DATA: lc_syst(30) TYPE c.
DATA: lc_exception(120) TYPE c.
RSZELTDIR Directory of the reporting component elements
RSZELTTXT Texts of reporting component elements
RSZELTXREF Directory of query element references
RSRREPDIR Directory of all reports (Query GENUNIID)
RSZCOMPDIR Directory of reporting components
RSZRANGE Selection specification for an element
RSZSELECT Selection properties of an element
RSZELTDIR Directory of the reporting component elements
RSZCOMPIC Assignment reuseable component <-> InfoCube
RSZELTPRIO Priorities with element collisions
RSZELTPROP Element properties (settings)
RSZELTATTR Attribute selection per dimension element
RSZCALC Definition of a formula element
RSZCEL Query Designer: Directory of Cells
RSZGLOBV Global Variables in Reporting
data: gi_data like rszrange occurs 0 with header line.
Determine the queries
tables:
RSZELTTXT,
rszeltdir,
rszeltxref,
rszrange.
data: begin of lt_line occurs 0,
ELTUID like RSZELTDIR-ELTUID, "char 25
MAPNAME like RSZELTDIR-MAPNAME, "char 30
TXTLG(60) TYPE c,
end of lt_line.
data: begin of lt_line1 occurs 0,
SELTUID like rszeltxref-SELTUID, "char 25
TELTUID like rszeltxref-TELTUID, "char 25
LAYTP like rszeltxref-LAYTP,
end of lt_line1.
data: begin of lt_line2 occurs 0,
ELTUID like rszrange-ELTUID, "char 25
IOBJNM like rszrange-IOBJNM,
LOW like rszrange-LOW,
LOWFLAG like rszrange-LOWFLAG,
end of lt_line2.
data: begin of lt_line3 occurs 0,
VARUNIID like RSZGLOBV-VARUNIID, "char 25
VNAM like RSZGLOBV-VNAM,
IOBJNM like RSZGLOBV-IOBJNM,
end of lt_line3.
data: lt_tab like standard table of lt_line initial size 0.
data: lt_tab1 like standard table of lt_line1 initial size 0.
data: lt_tab2 like standard table of lt_line2 initial size 0.
data: lt_tab3 like standard table of lt_line3 initial size 0.
data: lt_line20(128) TYPE c. " LIKE RSZELTXREF-SELTUID.
data: lt_line30(128) TYPE c. " LIKE RSZELTXREF-SELTUID.
type-pools:
rs, "BW global
rrms, "message server
rsz, "Qry definition global
rzx0, "Qry RFC interface
rzd1. "Qry definition database
DATA: l_target_compid TYPE rszcompdir-compid,
l_t_uid_server TYPE rzx0_t_uid_server,
l_s_uid_server TYPE rzx0_s_uid_server_x,
l_s_msg TYPE rs_s_msg,
l_s_compdir TYPE rzx0_s_compdir,
l_s_eltdir TYPE rzx0_s_eltdir,
l_s_elttxt TYPE rzx0_s_elttxt,
l_t_eltdir TYPE rzx0_t_eltdir,
l_t_eltprop TYPE rzx0_t_eltprop,
l_t_eltprio TYPE rzx0_t_eltprio,
l_t_eltattr TYPE rzx0_t_eltattr,
l_t_eltxref TYPE rzx0_t_eltxref,
l_t_compdir TYPE rzx0_t_compdir,
l_t_compic TYPE rzx0_t_compic,
l_t_select TYPE rzx0_t_select,
l_t_range TYPE rzx0_t_range,
l_t_calc TYPE rzx0_t_calc,
l_t_elttxt TYPE rzx0_t_elttxt,
l_t_cell TYPE rzx0_t_cel.
data: c_subrc LIKE sy-subrc.
data:
l_GENUNIID LIKE RSRREPDIR-GENUNIID,
l_COMPID LIKE RSZCOMPDIR-COMPID,
l_COMPUID LIKE RSZCOMPDIR-COMPUID,
I_OBJVERS LIKE RSZCOMPDIR-OBJVERS,
I_WITH_TEMPLATES LIKE RSGENERAL-BOOL,
I_BY_INFOCUBE LIKE RSZCOMPIC-INFOCUBE,
I_TEMPLATE_TYPE LIKE RSZELTDIR-DEFTP,
I_VARIABLE_TYPES LIKE RSZHELP-VARTYPES,
I_VARIABLE_INFOOBJECT LIKE RSZGLOBV-IOBJNM,
I_LANGUAGE LIKE SY-LANGU,
I_USE_BUFFER TYPE RS_BOOL.
FIELD-SYMBOLS:
<l_s_eltdir> TYPE rzx0_s_eltdir,
<l_s_compdir> TYPE rzx0_s_compdir,
<l_s_compic> TYPE rzx0_s_compic,
<l_s_eltxref> TYPE rzx0_s_eltxref.
DATA:
l_t_eltxref_seltuid LIKE rszeltxref-seltuid,
l_t_eltxref_teltuid LIKE rszeltxref-teltuid,
l_t_eltxref_laytp LIKE rszeltxref-laytp.
s_characteristic = CHARACT.
Find instances of the Forecast/Budget Variable in queries
s_varname = VARIABN. "'ZE_BFC01'.
SELECT SINGLE VARUNIID from RSZGLOBV
INTO s_varnameu where VNAM = s_varname.
clear lt_line.
lv_count = 0.
lv_count2 = 0.
Loop through all the queries
select * from RSZELTDIR
into corresponding fields of lt_line
where DEFTP = 'REP'
and OBJVERS = 'A'.
l_COMPUID = lt_line-ELTUID.
l_GENUNIID = lt_line-MAPNAME.
Filter by the Z Developed Queries
IF l_GENUNIID CP 'Z*'.
clear lt_line20.
Get the Query Long Name
select single * from RSZELTTXT
into lt_line20
where eltuid = lt_line-eltuid "rszeltdir-eltuid
and objvers = 'A'
and langu = 'EN'.
Find all the query elements within the query using function module
Get the tables of source query and its components
CALL FUNCTION 'RSZ_X_COMPONENT_GET'
EXPORTING
i_genuniid =
I_COMPID =
I_COMPUID = l_COMPUID
IMPORTING
e_subrc = c_subrc
TABLES
c_t_eltdir = l_t_eltdir
c_t_eltprop = l_t_eltprop
c_t_eltprio = l_t_eltprio
c_t_eltattr = l_t_eltattr
c_t_eltxref = l_t_eltxref.
c_t_compdir = l_t_compdir
c_t_compic = l_t_compic
c_t_select = l_t_select
c_t_range = l_t_range
c_t_calc = l_t_calc
c_t_elttxt = l_t_elttxt
c_t_cell = l_t_cell.
LOOP AT l_t_eltxref ASSIGNING <l_s_eltxref>.
l_t_eltxref_seltuid = <l_s_eltxref>-seltuid.
l_t_eltxref_teltuid = <l_s_eltxref>-teltuid.
l_t_eltxref_laytp = <l_s_eltxref>-laytp.
IF l_t_eltxref_laytp = 'FIX' OR l_t_eltxref_laytp = 'COL' OR l_t_eltxref_laytp = 'ROW' OR l_t_eltxref_laytp = 'AGG'.
Determine if the Query Element is matching to the characteristic
select * from rszrange
into corresponding fields of lt_line2
where eltuid = l_t_eltxref_teltuid "rszeltxref-teltuid
and objvers = 'A'.
Determine the variable name or master data value
IF lt_line2-LOWFLAG = 1.
Populate tables if match for Characterisic
IF lt_line2-IOBJNM = s_characteristic.
move lt_line-ELTUID to lt_line-ELTUID.
move lt_line-MAPNAME to lt_line-MAPNAME.
move lt_line2-LOW to lt_line-TXTLG.
append lt_line to lt_tab.
lv_count = lv_count + 1.
clear lt_line2-LOW.
ENDIF.
ELSE.
select * from RSZGLOBV
into corresponding fields of lt_line3
where VARUNIID = lt_line2-LOW
and objvers = 'A'.
Populate tables if match for Characterisic
IF lt_line2-IOBJNM = s_characteristic.
move lt_line-ELTUID to lt_line-ELTUID.
move lt_line-MAPNAME to lt_line-MAPNAME.
move lt_line3-VNAM to lt_line-TXTLG.
append lt_line to lt_tab.
lv_count = lv_count + 1.
clear lt_line3-VNAM.
ENDIF.
endselect.
ENDIF.
endselect.
ENDIF.
clear l_t_eltxref_seltuid.
clear l_t_eltxref_teltuid.
clear l_t_eltxref_laytp.
ENDLOOP.
ENDIF.
clear lt_line-ELTUID.
clear lt_line-MAPNAME.
clear lt_line-TXTLG.
endselect.
sort lt_tab by MAPNAME.
delete adjacent duplicates from lt_tab comparing ELTUID MAPNAME TXTLG.
DIRECTORY represents path where file is stored .
lc_DIRECTORY = '/interfaces/EDW/data/CSM/'.
CONCATENATE 'EDW Queries by Characteristic -' SY-DATUM
'.txt' into P_FILE SEPARATED BY SPACE.
CONCATENATE lc_DIRECTORY P_FILE into FILENAME.
Opening the Log File
OPEN DATASET FILENAME FOR OUTPUT IN TEXT MODE
ENCODING DEFAULT.
IF SY-SUBRC NE 0.
WRITE: 'File cannot be opened. Reason:'. ", D_MSG_TEXT.
EXIT.
ENDIF.
CONCATENATE 'System Date -' SY-DATUM 'YYYYMMDD' into lc_date
SEPARATED BY SPACE.
CONCATENATE 'EDW System -' SY-SYSID into lc_syst
SEPARATED BY SPACE.
TRANSFER lc_date TO FILENAME.
TRANSFER lc_start_time TO FILENAME.
TRANSFER lc_syst TO FILENAME.
Queries for the parameters
loop at lt_tab into lt_line.
TRANSFER lt_line TO FILENAME.
endloop. "Query Loop
Closing the Log File
CLOSE DATASET FILENAME.
Maybe you are looking for
-
After Effects crashes on Windows 7
Hello everybody, I installed After Effects on Windows 7. I have an Asus NVidia GTS 250 512MB graphic card. When I initialized AFX for the first time all went well. I could work normaly, see all the panels and stuff. Then I closed the program and star
-
Index bookmarks not appearing in correct place in PDF
This has happened to me on Frame 6, Frame 7, Frame 8, and Frame 9. It's happened with Acrobat 7, 9, and 10. Occasionally, when I print a book in FrameMaker, the Index bookmarks are out of sequence in the generated PDF. They appear as subheadings in t
-
Need help figuring how to track DVD drive usage
I work at a public library and need to track how often the DVD drives are used by our patrons. Is there some count somewhere of how many times the drive is accessed? The only other way I can think of to do this is to run a script that will check if
-
OS4 not letting me change wallpaper
Hey guys I had the same problem as most It took too long to back up so I did a restore and update and that worked but when I go to settings and then wallpaper all I see are my photo albums. When I select a pic the only time I can see it is when I am
-
An unknown error has occured [-50]
There was a problem downloading "Summer / Sunshine State Of Mind / We The Kings" An unknown error has occured [-50] Please check the connection to the network is active and try again. Connection is definalty active as I have brought another song toni