Database Error : Key violation.
Dear all,
I facing this problem while i'm trying to add user in the DB.
Database Error : Key violation.
Ora-00001 : unique constraint(PRD.PK_DRIVER_007) violated.
Could someone know how to solve this problem?
Thanks
Herewith the error log:
ORA-00001: unique constraint (PK_DRIVER_007) violated dataObj.cpp SQL = INSERT INTO PRD.driver (resourceId, driverName, companyIssuedId, displayInd, driverLicNo, identificationNo, homebaseLocId, contactPhoneNo, contactFaxNo, contactPagerNo, contactMobileNo, contactEmail, contactPreference, passNo, driverLinkLoginId, linkType, companyId, paymtSchemeCode, deptCode, subcontractedBy, remarks, activationKey, deletedInd, lastModifyBy, saveTime) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, TO_CHAR(F_GETCURRENTDATETIME, 'YYYY/MM/DD hh24:MI:SS'))
It this info useful?
Similar Messages
-
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.. -
Issue with INSERT INTO, throws primary key violation error even if the target table is empty
Hi,
I am running a simple
INSERT INTO Table 1 (column 1, column 2, ....., column n)
SELECT column 1, column 2, ....., column n FROM Table 2
Table 1 and Table 2 have same definition(schema).
Table 1 is empty and Table 2 has all the data. Column 1 is primary key and there is NO identity column.
This statement still throws Primary key violation error. Am clueless about this?
How can this happen when the target table is totally empty?
ChintuNope thats not true
Either you're not inserting to the right table or in the background some other trigger code is getting fired which is inserting into some table which causes a PK violation.
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page -
Hi all...
I hace created a Master table and a detail table. the detail table can have multiple records corresponding to a code in master table.this is the case which i want but its giving error of violation of primary key in detail table due to bydefault field Code in the table
Thanks in advanceHi
Good way are creating of UDO using these tables:
- Master = MASTER_DATA;
- Details = MASTER_DATA_ROWS.
If you import data you need to give values to saome SAP attributes.
Look this link [Thread: How to import data from excel to UserDefined Fields|How to import data from excel to UserDefined Fields;. May be it can help you.
Regards
Sierdna S. -
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,
TomHi,
" 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,
ManishHi 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,
KumarHi,
Check SAP Note 864267 (Code page conversion error after WP has left reconnect state). It might help .
Regards,
Neel -
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 RebolledoHi 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 -
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 JindalHi 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
RamHello 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 -
Standard DSO - Write Optimized DSO, key violation, same semantic key
Hello everybody,
I'm trying to load a Write-Optimized DSO from another Standard DSO and then is raised the "famous" error:
During loading, there was a key violation. You tried to save more than
one data record with the same semantic key.
The problematic (newly loaded) data record has the following properties:
o DataStore object: ZSD_O09
o Request: DTPR_D7YTSFRQ9F7JFINY43QSH1FJ1
o Data package: 000001
o Data record number: 28474
I've seen many different previous posts regarding the same issue but not quite equal as mine:
[During loading, there was a key violation. You tried to save more than]
[Duplicate data records at dtp]
...each of them suggests to make some changes in the Semantic Key. Here's my particular context:
Dataflow goes: ZSD_o08 (Standard DSO) -> ZSD_o09 (Write-Optimized DSO)
ZSD_o08 Semantic Keys:
SK1
SK2
SK3
ZSD_o09 Semantic Keys:
SK1
SK2
SK3
SK4 (value is taken in a routine as SY-DATUM-1)
As far as I can see there are no repeated records for semantic keys into ZSD_o08 this is confirmed by querying at active data table for ZSD_o08 ODS. Looking for the Temporary Storage for the crashed DTP at the specific package for the error I can't neither see any "weird" thing.
Let's suppose that the Semantic Key is crucial as is currently set.
Could you please advice?. I look forward for your quick response. Thank you and best regards,
BernardoHi Bernardo:
By maintaining the settings on your DTP you can indicate wether data should be extracted from the Active Table or Change Log Table as described below.
>-Double click on the DTP that transfers the data from the Standard DSO to the Write Optimized DSO and click on the "Extraction" Tab, on the group at the bottom select one of the 4 options:
>Active Table (With Archive)
>Active Table (Without Archive)
>Active Table (Full Extraction Only)
>Change Log
>Hit the F1 key to access the documentation
>
>===================================================================
>Indicator: Extract from Online Database
>The settings in the group frame Extraction From... or Delta Extraction From... of the Data Transfer Process maintenance specify the source from which the data of the DTP is extracted. For a full DTP, these settings apply to all requests started by the DTP. For a delta DTP, the settings only apply to the first request (delta initialization), since because of the delta logic, the following requests must all be extracted from the change log.
>For Extraction from the DataStore Object, you have the following options:
>Active Table (with Archive)
>The data is read from the active table and from the archive or from a near-line storage if one exists. You can choose this option even if there is no active data archiving process yet for the DataStore object.
>Active Table (Without Archive)
>The data is only read from the active table. If there is data in the archive or in a near-line storage at the time of extraction, this data is not extracted.
>Archive (Only Full Extraction)
>The data is only read from the archive or from a near-line storage. Data is not extracted from the active table.
>Change Log
>The data is read from the change log of the DataStore object.
>For Extraction from the InfoCube, you have the following options:
>InfoCube Tables
>Data is only extracted from the database (E table and F table and aggregates).
>Archive (Only Full Extraction)
>The data is only read from the archive or from a near-line storage.
Have you modified the default settings on the DTP? How is the DTP configured right now? (or how was configured before your testing?)
Hope this helps,
Francisco Milán. -
Database error when creating a new ADDM
Hi Guys,
In my dbconsole 10.1.0.4 i got this error when trying to create a snapshot:
Database Error
Task TASK_38223 has been created, but following error occurs during the execution time : ORA-13707: Either the start snapshot 19110 or the end snapshot 19111 is incomplete or missing
key statistics. ORA-06512: at "SYS.PRVT_ADVISOR", line 1283 ORA-06512: at "SYS.DBMS_ADVISOR",
line 190 ORA-06512: at line 1
everything else is OK.
Please advise,
Regards,
FirasHi,
I checked the trace files in BDUMP and found this:
Oracle process number: 13
Unix process pid: 21443, image: oracle@xxxxx (m000)
*** ACTION NAME:(Auto-Flush Slave Action) 2008-04-15 12:00:22.103
*** MODULE NAME:(MMON_SLAVE) 2008-04-15 12:00:22.103
*** SERVICE NAME:(SYS$BACKGROUND) 2008-04-15 12:00:22.103
*** SESSION ID:(156.413) 2008-04-15 12:00:22.103
*** KEWROCISTMTEXEC - encountered error:
( ORA-00001: unique constraint (SYS.WRH$_SQLTEXT_PK) violated )
*** SQLSTR: total-len=632, dump-len=240,
STR={INSERT INTO wrh$_sqltext (sql_id, dbid, sql_text, command_type, snap_id, ref_count) SELECT /*+ ord
ered use_nl(s1) index(s1) */ sie.sqlid_kewrsie, :dbid, s1.sql_fulltext, }
*** KEWRAFM1: Error=13509 encountered by kewrfteh
Please advise,
Cheers,
Firas -
Hi ,
anyone can help me check wat's the following error means? my program can query and update movies & movie reviews to/from the database. When i tried to query either the movie or the movie reviews, the program works fine but when i try to update review also no problem . However, when i try to update new movies to the database, this error appears(the database already had data inside and i had make sure tat the table name n etc is correct):
Database Error
An Operation on the Movie Database Failed!
org.apache.jasper.JasperException: Cannot find any information on property 'movie' in a bean of type 'db.UpdateMovies'
at org.apache.jasper.runtime.JspRuntimeLibrary.internalIntrospecthelper(JspRuntimeLibrary.java:363)
at org.apache.jasper.runtime.JspRuntimeLibrary.introspecthelper(JspRuntimeLibrary.java:306)
at org.apache.jsp.jdbc2_jsp._jspService(jdbc2_jsp.java:76)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Unknown Source)
Anyone have any idea wat's went wrong? Please advice .......& Thanks alot for yr help
Regards,
huiqinfrom what you're saying, it would sound like a duplicate entry of key constraint violation
your stack trace is simply saying that there is a problem with the bean being null or not initialized, and this is likely due to the database failing
you need to get the database specific error and/or error code, this JSP error won't help in debugging the problem -
BO 4.0 - Database error: Unable to connect to SAP BW Incomplete logon data
Hello Experts,
I have enabled a 'SSO to database' between SAP BW and Business objects by referencing to the documents related to below link.
[http://wiki.sdn.sap.com/wiki/display/BOBJ/HowtosetupSSOagainstSAPBWinSBOBI4.0forLDAPusers]
I have created a universe connection with option 'use single sign on when refreshing reports at view time' and have created a universe on top of my BEx query by log-in to the universe designer tools using my LDAP account.
Now when I run the report with either SAP account or LDAP - I am able to run a adhoc webi report on this universe and get data either through the webi rich client or via BO 4.0 Info-view/Launch Pad.
But the issue is that when other users are trying to run webi queries on this universe either through Info-view/launch pad or rich client by log-in via LDAP Authentication - they get the below error: I have given SAP_ALL to this user for time being and also have done the necessary configuration for 'simple user format' in CMC so these user has 1 account with 3 alias definitions: Enterprise, SAP, R/3.
Database error: Unable to connect to SAP BW server Incomplete logon data -
If the user logs on into the BO 4.0 Info-view/launch pad or webi rich client using his SAP authentication than he is able to run and retrieve data.
I also get a dump in the SAP BW system - I analyzed the dump in SAP BW using st22 tcode and it gives the error short text as - Incomplete logon data and run-time error - CALL_FUNCTION_SIGNON_INCOMPL
Desired outcome:
I want the users to log-in to webi rich client or BO 4.0 Launch pad/Info-view using their 'LDAP' authentication and run reports against the universe on SAP BW/BEx query without any errors or additional username/password requirements.
Can someone please tell me if I am missing any steps/configuration and guide me to achieve the above mentioned desired result ?
Any help in this matter would be greatly appreciated.
Thanks & regards,
CD.Hi Simone,
Thank you for the reply.
Here are the things done by me.
1. Generated the keystore file and imported it in BI 4.0 CMC on SAP Authentication Option tab
([http://wiki.sdn.sap.com/wiki/display/BOBJ/GeneratekeystoreandcertificateforSAPBO+BI4.0])
([http://wiki.sdn.sap.com/wiki/display/BOBJ/SetupofSAPSSOServiceinSAPBOBI4.0+CMC])
2. Generate the certificate file cert.der and this cert is imported in SAP BW with STRUSTSSO2 transaction.
([http://wiki.sdn.sap.com/wiki/display/BOBJ/ImportSAPBOBI4.0certificateintoSAP+BW])
3. BW Roles/Users have been imported into CMC.
4. SAP Users and LDAP users are mapped/aliased with each other using the registry key method
([http://wiki.sdn.sap.com/wiki/display/BOBJ/HowtomapSAPusersandLDAPusersinSBOBI4.0+CMC])
I haven't explicitly configured STS (Security token service) as STS is a part of Adaptive processing server (APS) and I have verified that by going to servers in CMC and then to analysis services.
I have searched for SAP OSS notes related to my issue but couldn't find any note related to SAP BW SSO with Business objects 4.0. Most of the notes are relevant for BO XI 3.1 environments.
Thanks & regards,
CD. -
Hello guys,
I am facing the error " Database error for <ADDR_PERS_COMP_COMM_GET> <0> " as a pop-up message.
below is my program.
types: BEGIN OF t_p0002,
pernr type PERSNO, "Personnel number
nachn TYPE PAD_NACHN, "Last Name
VORNA TYPE PAD_VORNA, "First Name
gbdat TYPE gbdat, "Date of Birth
END OF t_p0002.
*******************Data of an object which can be changed**************************************
data S_maildata type SODOCCHGI1.
*******************Text field length 255: texts***********************************************
data : IT_MAILTXT1 type table of SOLISTI1 , "Internal table will contain texts of mail header
WA_MAILTXT1 TYPE SOLISTI1,
IT_MAILTXT2 type table of SOLISTI1 , "Internal table will contain texts of contents in the mail
WA_MAILTXT2 TYPE SOLISTI1.
*******************Structure of the API Recipient List*****************************************
data : IT_MAILREC type table of SOMLRECI1,
WA_MAILREC TYPE SOMLRECI1.
DATA : it_pa0002 TYPE TABLE OF t_p0002,
wa_pa0002 type t_p0002.
data Header_text type c LENGTH 15.
CONSTANTS content_text type c LENGTH 35 VALUE 'Tomorrow is the birthday of'.
*******************Event start of selection***************************************************
start-of-selection.
PERFORM get_birthdate. " will give birthday details
PERFORM document_details. " will give text and mail details
*& Form get_birthdate
text : subroutine to get employee birthdate details
form get_birthdate.
data : l_date like sy-datum.
refresh it_pa0002.
l_date = sy-datum + 1.
SELECT pernr nachn vorna gbdat
from pa0002
INTO TABLE it_pa0002
where gbdat = '19650302'.
ENDFORM. "get_birthdate
*& Form document_details
text : subroutine to get texts and mail details.
FORM document_details.
CLEAR: Header_text,
wa_MAILREC.
REFRESH IT_MAILREC.
S_maildata-obj_name = 'Birthday Reminder'.
s_maildata-obj_descr = 'Birthday Reminder'.
s_maildata-obj_langu = sy-langu.
READ TABLE IT_MAILTXT1 INTO WA_MAILTXT1
WITH KEY WA_MAILTXT1-line .
WA_MAILTXT1-line = 'Birthday Reminder'.
append WA_MAILTXT1 TO IT_MAILTXT1.
CLEAR WA_MAILTXT1.
LOOP at it_pa0002 INTO wa_pa0002.
READ TABLE IT_MAILTXT2 INTO WA_MAILTXT2
WITH KEY WA_MAILTXT2-line .
CONCATENATE content_text ' ( ' wa_pa0002-pernr ' ) ' wa_pa0002-nachn wa_pa0002-vorna
INTO WA_MAILTXT2 SEPARATED BY ' '.
append WA_MAILTXT2 TO IT_MAILTXT2.
CLEAR WA_MAILTXT2.
CLEAR wa_pa0002.
ENDLOOP.
LOOP AT IT_MAILREC INTO WA_MAILREC.
WA_MAILREC-RECEIVER = 'Any mail id'.
WA_MAILREC-rec_type = 'U'.
append WA_MAILREC TO IT_MAILREC.
ENDLOOP.
********************Function Mofule:To Send new Document*****************************************
CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
EXPORTING
document_data = S_maildata
DOCUMENT_TYPE = 'RAW'
PUT_IN_OUTBOX = ' '
COMMIT_WORK = 'X'
IMPORTING
SENT_TO_ALL =
NEW_OBJECT_ID =
tables
OBJECT_HEADER = IT_MAILTXT1
OBJECT_CONTENT = IT_MAILTXT2
CONTENTS_HEX =
OBJECT_PARA =
OBJECT_PARB =
receivers = IT_MAILREC
EXCEPTIONS
TOO_MANY_RECEIVERS = 1
DOCUMENT_NOT_SENT = 2
DOCUMENT_TYPE_NOT_EXIST = 3
OPERATION_NO_AUTHORIZATION = 4
PARAMETER_ERROR = 5
X_ERROR = 6
ENQUEUE_ERROR = 7
OTHERS = 8
IF sy-subrc = 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. "document_details
After I pressed the exit button the program is getting terminated but still this mail is comming to sost transaction code.
If I will comment the message code which is after sy-subrc the popup will not come and program will work without any interruption.
Can anybody please solve this problem?Resolved
Maybe you are looking for
-
VPN connected - how do I access my office mac?
VPN - I am connected remotely on my MacBook Air via a VPN connection to my office Mac. How do I actually "see" the files, folders, etc. on my office Mac?
-
My sister bought an ipod nano about a month ago. She tried to install itunes to no avail. Something about it trying to install to a drive that wasn't there. So I told to her to install vpod instead. It worked like a charm. Then yesterday she tells ev
-
Really interesting bizarre bug in TreePath, I'm confused beyond belief
Inside a large program, in which I use custom TreeModel instead of DefaultMutableTreeNode's etc, I have a following method which needs to recurse up a TreePath. This seems to be a MAJOR bug, because if you look in the following ten lines, I verify se
-
I updated Firefox but now it says it will not work b/c the application may be damaged or incomplete. What can I do. It worked perfectly before I updated the app.
-
Leading account assignment mandatory
Hi For the account assignment Cost Center we have Cost Center as leading field and ORDER_NO as a second field for statistical internal orders. It is today possible to enter an order without the leading cost center without getting an error when orderi