Skip to first unread message
Zhiming Su
Jan 23, 2019, 12:19:53 AM1/23/19
to schedulix
Hi all,
FATAL [main] 23 Jan 2019 05:17:04 GMT Fatal exception while loading Repository:
Duplicate id during load Object
FATAL [main] 23 Jan 2019 05:17:04 GMT ****************** Start Stacktrace *********************
FATAL [main] 23 Jan 2019 05:17:04 GMT de.independit.scheduler.server.util.SDMSThread.doTrace(SDMSThread.java:149)
FATAL [main] 23 Jan 2019 05:17:04 GMT de.independit.scheduler.server.Server.serverMain(Server.java:436)
FATAL [main] 23 Jan 2019 05:17:04 GMT de.independit.scheduler.BICServer.main(BICServer.java:144)
FATAL [main] 23 Jan 2019 05:17:04 GMT ****************** End Stacktrace *********************
INFO [Shutdown] 23 Jan 2019 05:17:04 GMT ***********************************************
INFO [Shutdown] 23 Jan 2019 05:17:04 GMT ** **
INFO [Shutdown] 23 Jan 2019 05:17:04 GMT ** U N G R A C E F U L S H U T D O W N ! ! **
INFO [Shutdown] 23 Jan 2019 05:17:04 GMT ** **
INFO [Shutdown] 23 Jan 2019 05:17:04 GMT ***********************************************
INFO [Shutdown] 23 Jan 2019 05:17:04 GMT Release repository lock from 1548220623320
INFO [Shutdown] 23 Jan 2019 05:17:04 GMT Shutdown completed
Thanks!
Dieter Stubler
Jan 23, 2019, 2:50:43 AM1/23/19
to schedulix
Hi,
When does this happen ?
During Install ?
During Install ?
The only case I've seen this before is during installation when set the install.sql script was run twice accidently.
To help you, we need a little bit more information.
A bit more context information and more of the logfile would help.
A bit more context information and more of the logfile would help.
Regards
Dieter
Dieter
Zhiming Su
Jan 24, 2019, 2:09:45 AM1/24/19
to schedulix
Hi Dieter,
INFO [main] 23 Jan 2019 05:17:03 GMT **************************************************************************
INFO [main] 23 Jan 2019 05:17:03 GMT Copyright : Copyright (c) 2002-2015 independIT Integrative Technologies GmbH
INFO [main] 23 Jan 2019 05:17:03 GMT Build-Date : 06.09.2016 23:21
INFO [main] 23 Jan 2019 05:17:03 GMT Level : OPEN
INFO [main] 23 Jan 2019 05:17:03 GMT Build :
INFO [main] 23 Jan 2019 05:17:03 GMT Company : independIT Integrative Technologies GmbH
INFO [main] 23 Jan 2019 05:17:03 GMT Program-Version : 2.7
INFO [main] 23 Jan 2019 05:17:03 GMT Created-By : 1.8.0_102 (Oracle Corporation)
INFO [main] 23 Jan 2019 05:17:03 GMT Manifest-Version : 1.1
INFO [main] 23 Jan 2019 05:17:03 GMT **************************************************************************
INFO [main] 23 Jan 2019 05:17:03 GMT ** BICsuite!Server
INFO [main] 23 Jan 2019 05:17:03 GMT ** Version 2.7
INFO [main] 23 Jan 2019 05:17:03 GMT ** Copyright (C) 2000-2002 topIT Informationstechnologie GmbH
INFO [main] 23 Jan 2019 05:17:03 GMT ** Copyright (C) 2003-2014 independIT Integrative Technologies GmbH
INFO [main] 23 Jan 2019 05:17:03 GMT **************************************************************************
INFO [main] 23 Jan 2019 05:17:03 GMT Commandline Start Options:
INFO [main] 23 Jan 2019 05:17:03 GMT /home/schedulix/etc/server.conf
INFO [main] 23 Jan 2019 05:17:03 GMT UserThreads=30
INFO [main] 23 Jan 2019 05:17:03 GMT JdbcDriver=com.mysql.jdbc.Driver
INFO [main] 23 Jan 2019 05:17:03 GMT ArchiveSMEColumns=ALL
INFO [main] 23 Jan 2019 05:17:03 GMT TrustStore=/home/bicsuite/etc/certs/srvkeystore
INFO [main] 23 Jan 2019 05:17:03 GMT TxRetryCount=3
INFO [main] 23 Jan 2019 05:17:03 GMT SingleServer=true
INFO [main] 23 Jan 2019 05:17:03 GMT CompatibilityLevel=BASIC
INFO [main] 23 Jan 2019 05:17:03 GMT History=14400
INFO [main] 23 Jan 2019 05:17:03 GMT ParameterHandling=liberal
INFO [main] 23 Jan 2019 05:17:03 GMT PriorityLowerBound=10
INFO [main] 23 Jan 2019 05:17:03 GMT ArchiveHierarchyColumns=ALL
INFO [main] 23 Jan 2019 05:17:03 GMT ServicePort=2505
INFO [main] 23 Jan 2019 05:17:03 GMT TimerWakeup=30
INFO [main] 23 Jan 2019 05:17:03 GMT PriorityDelay=1
INFO [main] 23 Jan 2019 05:17:03 GMT KeyStore=/home/bicsuite/etc/certs/srvkeystore
INFO [main] 23 Jan 2019 05:17:03 GMT ArchiveAuditColumns=ALL
INFO [main] 23 Jan 2019 05:17:03 GMT CodePage=latin1
INFO [main] 23 Jan 2019 05:17:03 GMT DbUrl=jdbc:mysql://172.31.3.254:3305/schedulixdb
INFO [main] 23 Jan 2019 05:17:03 GMT TimerTimeout=10
INFO [main] 23 Jan 2019 05:17:03 GMT ArchiveDependencyColumns=ALL
INFO [main] 23 Jan 2019 05:17:03 GMT ClientAuthorization=true
INFO [main] 23 Jan 2019 05:17:03 GMT DbLoaders=2
INFO [main] 23 Jan 2019 05:17:03 GMT RunMode=PRODUCTION
INFO [main] 23 Jan 2019 05:17:03 GMT Port=2506
INFO [main] 23 Jan 2019 05:17:03 GMT CalendarEntries=250
INFO [main] 23 Jan 2019 05:17:03 GMT TimerHorizon=2
INFO [main] 23 Jan 2019 05:17:03 GMT HistoryLimit=28800
INFO [main] 23 Jan 2019 05:17:03 GMT ScheduleWakeup=30
INFO [main] 23 Jan 2019 05:17:03 GMT DbUser=schedulix
INFO [main] 23 Jan 2019 05:17:03 GMT ArchiveVariableColumns=ALL
INFO [main] 23 Jan 2019 05:17:03 GMT MinHistoryCount=0
INFO [main] 23 Jan 2019 05:17:03 GMT CalendarHorizon=90
INFO [main] 23 Jan 2019 05:17:03 GMT TimerSuspendLimit=15
INFO [main] 23 Jan 2019 05:17:03 GMT Hostname=172.20.12.92
INFO [main] 23 Jan 2019 05:17:03 GMT WorkerThreads=2
INFO [main] 23 Jan 2019 05:17:03 GMT DbHistory=0
INFO [main] 23 Jan 2019 05:17:03 GMT Archive=false
INFO [main] 23 Jan 2019 05:17:03 GMT TriggerHardLimit=100
INFO [main] 23 Jan 2019 05:17:03 GMT TriggerSoftLimit=50
INFO [main] 23 Jan 2019 05:17:03 GMT MaxHistoryCount=0
INFO [main] 23 Jan 2019 05:17:03 GMT TraceLevel=1
INFO [main] 23 Jan 2019 05:17:03 GMT ArchiveKillJobColumns=ALL
INFO [main] 23 Jan 2019 05:17:03 GMT TimerRecalc=1
INFO [main] 23 Jan 2019 05:17:03 GMT GCWakeup=240
INFO [main] 23 Jan 2019 05:17:03 GMT SessionTimeout=0
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting ERRORLOG
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting EXPFINALTIME
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting EXPRUNTIME
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting FINISHTIME
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting ISRESTARTABLE
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting JOBID
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting JOBNAME
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting JOBSTATE
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting JOBTAG
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting KEY
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting LOGFILE
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting MASTERID
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting MERGEDSTATE
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting PARENTID
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting PID
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting RERUNSEQ
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting RESOURCETIME
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting RUNNABLETIME
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting SCOPENAME
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting SDMSHOST
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting SDMSPORT
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting SEID
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting STARTTIME
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting STATE
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting SUBMITTIME
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting SYNCTIME
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting SYSDATE
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting TRIGGERBASE
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting TRIGGERBASEID
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting TRIGGERBASEJOBID
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting TRIGGERNAME
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting TRIGGERNEWSTATE
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting TRIGGERORIGIN
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting TRIGGERORIGINID
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting TRIGGERORIGINJOBID
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting TRIGGEROLDSTATE
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting TRIGGERREASON
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting TRIGGERREASONID
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting TRIGGERREASONJOBID
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting TRIGGERSEQNO
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting TRIGGERTYPE
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting LAST_WARNING
INFO [main] 23 Jan 2019 05:17:03 GMT Exporting WORKDIR
INFO [main] 23 Jan 2019 05:17:03 GMT Acquire repository lock for 1548220623320
INFO [main] 23 Jan 2019 05:17:03 GMT Starting Renew Ticket Thread
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT TableLoader 0 started
INFO [Thread-1] 23 Jan 2019 05:17:04 GMT TableLoader 1 started
INFO [Thread-1] 23 Jan 2019 05:17:04 GMT Read 2, Loaded 2 rows for GROUPS
INFO [Thread-1] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for RESOURCE_REQUIREMENT
INFO [Thread-1] 23 Jan 2019 05:17:04 GMT Read 3, Loaded 3 rows for SCOPE
INFO [Thread-1] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for INTERVAL_SELECTION
INFO [Thread-1] 23 Jan 2019 05:17:04 GMT Read 1, Loaded 1 rows for RUNNABLE_QUEUE
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 123, Loaded 123 rows for SCHEDULING_HIERARCHY
INFO [Thread-1] 23 Jan 2019 05:17:04 GMT Read 1, Loaded 1 rows for EVENT
INFO [Thread-1] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for TRIGGER_QUEUE
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 1, Loaded 1 rows for SCHEDULED_EVENT
INFO [Thread-1] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for RESOURCE_STATE_PROFILE
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for KILL_JOB
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 1, Loaded 1 rows for PERSISTENT_VALUE
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for TRIGGER_DEFINITION
INFO [Thread-1] 23 Jan 2019 05:17:04 GMT Read 4, Loaded 4 rows for SCHEDULE
INFO [Thread-1] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for RESOURCE_STATE_MAP_PROF
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 1, Loaded 1 rows for GRANTS
INFO [Thread-1] 23 Jan 2019 05:17:04 GMT Read 13, Loaded 13 rows for FOLDER
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 60, Loaded 60 rows for DEPENDENCY_DEFINITION
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for RESOURCE_STATE
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 60, Loaded 60 rows for DEPENDENCY_STATE
INFO [Thread-1] 23 Jan 2019 05:17:04 GMT Read 150, Loaded 150 rows for SCHEDULING_ENTITY
INFO [Thread-1] 23 Jan 2019 05:17:04 GMT Read 692, Loaded 692 rows for SUBMITTED_ENTITY
INFO [Thread-1] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for TRIGGER_STATE
INFO [Thread-1] 23 Jan 2019 05:17:04 GMT Read 1, Loaded 1 rows for INTERVALL
ERROR [Thread-1] 23 Jan 2019 05:17:04 GMT Duplicate id during load Object
ERROR [Thread-1] 23 Jan 2019 05:17:04 GMT ****************** Start Stacktrace *********************
ERROR [Thread-1] 23 Jan 2019 05:17:04 GMT de.independit.scheduler.server.util.SDMSThread.doTrace(SDMSThread.java:149)
ERROR [Thread-1] 23 Jan 2019 05:17:04 GMT de.independit.scheduler.server.exception.FatalException.<init>(FatalException.java:52)
ERROR [Thread-1] 23 Jan 2019 05:17:04 GMT de.independit.scheduler.server.repository.SDMSTable.loadObject(SDMSTable.java:198)
ERROR [Thread-1] 23 Jan 2019 05:17:04 GMT de.independit.scheduler.server.repository.SDMSCalendarTableGeneric.loadTable(SDMSCalendarTableGeneric.java:210)
ERROR [Thread-1] 23 Jan 2019 05:17:04 GMT de.independit.scheduler.server.repository.TableLoader.SDMSrun(SDMSRepository.java:382)
ERROR [Thread-1] 23 Jan 2019 05:17:04 GMT de.independit.scheduler.server.util.SDMSThread.run(SDMSThread.java:207)
ERROR [Thread-1] 23 Jan 2019 05:17:04 GMT ****************** End Stacktrace *********************
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 449, Loaded 449 rows for HIERARCHY_INSTANCE
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 189, Loaded 189 rows for DEPENDENCY_INSTANCE
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 3, Loaded 3 rows for EXIT_STATE_MAPPING
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 1, Loaded 1 rows for EXIT_STATE_PROFILE
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 3, Loaded 3 rows for USERS
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for NICE_PROFILE_ENTRY
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 3, Loaded 3 rows for EXIT_STATE_DEFINITION
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 1, Loaded 1 rows for ENVIRONMENT
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for RESOURCE_REQ_STATES
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for NICE_PROFILE
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 1, Loaded 1 rows for EXIT_STATE_MAPPING_PROFILE
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 1, Loaded 1 rows for NAMED_ENVIRONMENT
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 143, Loaded 143 rows for PARAMETER_DEFINITION
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for INTERVAL_HIERARCHY
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 4, Loaded 4 rows for MEMBER
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for RESOURCE_STATE_MAPPING
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 3, Loaded 3 rows for NAMED_RESOURCE
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 48, Loaded 48 rows for ENTITY_VARIABLE
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for OBJECT_COMMENT
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 7, Loaded 7 rows for SCOPE_CONFIG
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for RESOURCE_VARIABLE
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for RESOURCE_ALLOCATION
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for IGNORED_DEPENDENCY
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for RESOURCE_STATE_DEFINITION
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 174, Loaded 174 rows for SME_COUNTER
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for SCOPE_CONFIG_ENVMAPPING
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 3, Loaded 3 rows for EXIT_STATE
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for FOOTPRINT
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 0, Loaded 0 rows for EVENT_PARAMETER
INFO [Thread-0] 23 Jan 2019 05:17:04 GMT Read 1, Loaded 1 rows for RESSOURCE
[scrolllog] Waiting for child (44) to terminate
[scrolllog] Child exited with state 1
[scrolllog] Try to restart child (child terminated with exit code <> 0)
I think it's a problem caused by virtual machine cloning because the IP address hasn't been changed to server boot failure.
How should I locate the problem?
Should I go to the database and delete duplicate data? Which table should I delete?
Regards
Suzm
Dieter Stubler
Jan 24, 2019, 2:42:29 AM1/24/19
to schedulix
Hello,
This is strange because there should be a unique index on ID of table CALENDAR.
Can please check with:
SELECT `ID` , COUNT(*) FROM CALENDAR GROUP BY ` ID`;
and post the result of this query here.
This way we can figure out whether the problem is associated with mysql or schedulix.
Regards
Dieter
Dieter
Zhiming Su
Jan 24, 2019, 3:16:15 AM1/24/19
to schedulix
mysql> SELECT `ID`, COUNT(*) FROM CALENDAR GROUP BY `ID`;
+--------+----------+
| ID | COUNT(*) |
+--------+----------+
| 665411 | 1 |
| 665416 | 1 |
| 665421 | 1 |
| 665427 | 1 |
| 665512 | 1 |
| 665517 | 1 |
| 665522 | 1 |
| 665527 | 1 |
| 665612 | 1 |
| 665617 | 1 |
| 665622 | 1 |
| 665627 | 1 |
| 665632 | 1 |
| 665637 | 1 |
| 665642 | 1 |
| 665647 | 1 |
| 665652 | 1 |
| 665657 | 1 |
| 665662 | 1 |
| 665667 | 1 |
| 665672 | 1 |
| 665677 | 1 |
| 665682 | 1 |
| 665687 | 1 |
| 665692 | 1 |
| 665697 | 1 |
| 665702 | 1 |
| 665708 | 1 |
| 665713 | 1 |
| 665718 | 1 |
| 665723 | 1 |
| 665728 | 1 |
| 665733 | 1 |
| 665738 | 1 |
| 665743 | 1 |
| 665748 | 1 |
| 665753 | 1 |
| 665758 | 1 |
| 665763 | 1 |
| 665768 | 1 |
| 665773 | 1 |
| 665778 | 1 |
| 665783 | 1 |
| 665788 | 1 |
| 665793 | 1 |
| 665798 | 1 |
| 665803 | 1 |
| 665808 | 1 |
| 665813 | 1 |
| 665818 | 1 |
| 665823 | 1 |
| 665829 | 1 |
| 665834 | 1 |
| 665839 | 1 |
| 665844 | 1 |
| 665849 | 1 |
| 665854 | 1 |
| 665859 | 1 |
| 665864 | 1 |
| 665869 | 1 |
| 665874 | 1 |
| 665879 | 1 |
| 665884 | 1 |
| 665889 | 1 |
| 665894 | 1 |
| 665899 | 1 |
| 665904 | 1 |
| 665909 | 1 |
| 665914 | 1 |
| 665919 | 1 |
| 665924 | 1 |
| 665929 | 1 |
| 665934 | 1 |
| 665939 | 1 |
| 665944 | 1 |
| 665950 | 1 |
| 665955 | 1 |
| 665960 | 1 |
| 665965 | 1 |
| 665970 | 1 |
| 665975 | 1 |
| 666020 | 1 |
| 666585 | 1 |
| 666609 | 1 |
| 666753 | 1 |
| 666758 | 1 |
| 666763 | 1 |
| 666768 | 1 |
| 666933 | 1 |
| 666938 | 1 |
| 666943 | 1 |
| 666948 | 1 |
| 666953 | 1 |
| 666958 | 1 |
| 666963 | 1 |
| 666968 | 1 |
| 666973 | 1 |
| 666978 | 1 |
| 666983 | 1 |
| 666989 | 1 |
| 666994 | 1 |
| 667117 | 1 |
| 667122 | 1 |
| 667245 | 1 |
| 667309 | 1 |
| 667373 | 1 |
| 667498 | 1 |
| 667543 | 1 |
| 667548 | 1 |
| 667553 | 1 |
| 667558 | 1 |
| 667643 | 1 |
| 667648 | 1 |
| 667653 | 1 |
| 667658 | 1 |
| 667663 | 1 |
| 667668 | 1 |
| 667673 | 1 |
| 667678 | 1 |
| 667683 | 1 |
| 667688 | 1 |
| 667693 | 1 |
| 667698 | 1 |
| 667744 | 1 |
| 667829 | 1 |
| 667834 | 1 |
| 667839 | 1 |
| 667844 | 1 |
| 667849 | 1 |
| 667854 | 1 |
| 667859 | 1 |
| 667864 | 1 |
| 667869 | 1 |
| 667874 | 1 |
| 667879 | 1 |
| 667922 | 1 |
| 667927 | 1 |
| 667932 | 1 |
| 667937 | 1 |
| 667942 | 1 |
| 667947 | 1 |
| 667952 | 1 |
| 667957 | 1 |
| 667962 | 1 |
| 667967 | 1 |
| 667972 | 1 |
| 667977 | 1 |
| 667983 | 1 |
| 667988 | 1 |
| 667993 | 1 |
| 667998 | 1 |
| 668003 | 1 |
| 668008 | 1 |
| 668013 | 1 |
| 668018 | 1 |
| 668023 | 1 |
| 668028 | 1 |
| 668033 | 1 |
| 668038 | 1 |
| 668043 | 1 |
| 668048 | 1 |
| 668053 | 1 |
| 668058 | 1 |
| 668063 | 1 |
| 668068 | 1 |
| 668073 | 1 |
| 668078 | 1 |
| 668083 | 1 |
| 668088 | 1 |
| 668093 | 1 |
| 668098 | 1 |
| 668104 | 1 |
| 668269 | 1 |
| 668331 | 1 |
| 668511 | 1 |
| 668516 | 1 |
| 668521 | 1 |
| 668526 | 1 |
| 668531 | 1 |
| 668536 | 1 |
| 668541 | 1 |
| 668546 | 1 |
| 668551 | 1 |
| 668556 | 1 |
| 668561 | 1 |
| 668566 | 1 |
| 668571 | 1 |
| 668576 | 1 |
| 668581 | 1 |
| 668586 | 1 |
| 668591 | 1 |
| 668596 | 1 |
| 668601 | 1 |
| 668606 | 1 |
| 668611 | 1 |
| 668617 | 1 |
| 668622 | 1 |
| 668627 | 1 |
| 668632 | 1 |
| 668637 | 1 |
| 668642 | 1 |
| 668647 | 1 |
| 668652 | 1 |
| 668657 | 1 |
| 668662 | 1 |
| 668667 | 1 |
| 668672 | 1 |
| 668677 | 1 |
| 668682 | 1 |
| 668687 | 1 |
| 668692 | 1 |
| 668697 | 1 |
| 668702 | 1 |
| 668707 | 1 |
| 668712 | 1 |
| 668717 | 1 |
| 668722 | 1 |
| 668727 | 1 |
| 668732 | 1 |
| 668738 | 1 |
| 668743 | 1 |
| 668748 | 1 |
| 668772 | 1 |
| 668777 | 1 |
| 668782 | 1 |
| 668787 | 1 |
| 668792 | 1 |
| 668797 | 1 |
| 668802 | 1 |
| 668807 | 1 |
| 668812 | 1 |
| 668817 | 1 |
| 668822 | 1 |
| 668827 | 1 |
| 668832 | 1 |
| 668837 | 1 |
| 668842 | 1 |
| 668847 | 1 |
| 668852 | 1 |
| 668857 | 1 |
| 668862 | 1 |
| 668867 | 1 |
| 668872 | 1 |
| 668878 | 1 |
| 668883 | 1 |
| 668888 | 1 |
| 705005 | 1 |
| 795005 | 1 |
| 885005 | 1 |
| 886005 | 1 |
+--------+----------+
250 rows in set (0.00 sec)
Dieter Stubler
Jan 24, 2019, 3:39:06 AM1/24/19
to schedulix
Hello,
Ok, the ID is not duplicate but checking the source, the error message can be missleading because also any other unique index violation will result in this error.
So please check with:
SELECT `ID`, `SCEV_ID` , COUNT(*) FROM CALENDAR GROUP BY ` ID` HAVING COUNT(*) > 1;
and post the result of this query here.
Regards
Dieter
Dieter
Zhiming Su
Jan 24, 2019, 3:43:47 AM1/24/19
to schedulix
mysql> SELECT `ID` ,`SCEV_ID`,COUNT(*) FROM CALENDAR GROUP BY `ID` HAVING COUNT(*)> 1;
Empty set (0.00 sec)
mysql>
Dieter Stubler
Jan 24, 2019, 3:59:59 AM1/24/19
to schedulix
Hello,
can please verify that the query was executed on the database repository the server tries to load ?
Please double check (DbUrl=jdbc:mysql://172.31.3.254:3305/schedulixdb)
Please double check (DbUrl=jdbc:mysql://172.31.3.254:3305/schedulixdb)
If not run last query on the database above (172.31.3.254:3305/schedulixdb) an send the result please.
Regards
Dieter
Zhiming Su
Jan 24, 2019, 4:08:18 AM1/24/19
to schedulix
Hi ,
mysql> use schedulixdb;
Database changed
mysql> SELECT `ID` ,`SCEV_ID`,COUNT(*) FROM CALENDAR GROUP BY `ID` HAVING COUNT(*)> 1;
Empty set (0.01 sec)
mysql>
I'm sure it's all right.！
Ronald Jeninga
Jan 24, 2019, 4:20:47 AM1/24/19
to schedulix
Hi Suzm,
_if_ you checked and double checked you're connecting to the correct database, you can do the following:
1. connect to the database
2. save the original calendar table, e.g.
create table save_calendar as select * from calendar;
3. Clean the Calendar table (that's not a critical table), e.g.
delete from calendar;
4. Try a new start of the server
If the server start works, you can recreate the calendar entries by saving again the only schedule you have within the system.
(set master inactive, save, set master active, save).
I don't know what happened, but duplicate ip addresses within a network can lead to weird effects.
And the query Dieter asked for is probably intended to be
SELECT `SCEV_ID`, `STARTTIME`, COUNT(*) from CALENDAR GROUP BY `SCEV_ID`, `STARTTIME` HAVING COUNT(*) > 1;
since we already know there are no duplicate IDs within the table and the other unique key is (SCEV_ID, STARTTIME).
Best regards,
Ronald
Dieter Stubler
Jan 24, 2019, 4:45:02 AM1/24/19
to sche...@googlegroups.com
Hi,
Yes, Ronald is right. I forgot to change the groupy by clause
Sry for that.
Sry for that.
Regards
Dieter
Dieter
Zhiming Su
Jan 24, 2019, 5:37:01 AM1/24/19
to schedulix
Hi ,
mysql> SELECT `SCEV_ID`, `STARTTIME`, COUNT(*) from CALENDAR GROUP BY `SCEV_ID`, `STARTTIME` HAVING COUNT(*) > 1;
+---------+------------------+----------+
| SCEV_ID | STARTTIME | COUNT(*) |
+---------+------------------+----------+
| 656398 | 1127448855442624 | 2 |
+---------+------------------+----------+
1 row in set (0.00 sec)
It may be that two servers link to the same MySQL and perform a timing job at the same time, which causes this problem.
Why is there no primary key in the table structure?
Thanks
Ronald Jeninga
Jan 24, 2019, 6:04:28 AM1/24/19
to schedulix
Hi Suzm,
there is a primary key defined at database level which ensures the uniqueness of the IDs.
The key (SCEV_ID, STARTTIME) is unique, which is ensured within the application.
If we'd add unique indexes for each candidate key, the DBMS wouldn't do much more than updating indexes.
If two servers use the same schema, at least one of them shouldn't be able to run.
This is where the REPOSITORY_LOCK table is for.
There is a flaw in the maintenance of the Calendar table.
The effects until now were basically missing entries (the next start to be precise).
But as it is with flaws, it is hard to estimate the total effect and this dup key is theoretically a consequence of the flaw.
Unfortunately, although I know there is a flaw somewhere, I haven't been able to find it yet.
Currently I'm fixing another flaw in the time scheduling engine, but this Calendar flaw is the next topic on my ToDo List.
The bottom line is: it is pretty unclear what caused the duplicate entry.
We know the duplicate entry though and if the server is shut down, you can do the following:
SELECT `ID`, `SCEV_ID`, `STARTTIME`
FROM CALENDAR
WHERE `SCEV_ID` = 656398
AND STARTTIME = 1127448855442624;
This should give 2 rows with two different IDs.
Say the lowest ID in the result is A and the higher ID is B (they are different, we know that, thus one of them is greater).
We can delete one of them to fix the table, e.g.
DELETE FROM CALENDAR WHERE ID = A; /* fill in the ID here */
After that, the server can be started.
Best regards,
Ronald
Zhiming Su
Jan 25, 2019, 1:23:17 AM1/25/19
to schedulix
Hi Ronald,
Thanks for your help.
Best regards,
Suzm
Reply all
Reply to author
Forward
0 new messages