[ https://issues.apache.org/jira/browse/SYNCOPE-903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370584#comment-15370584 ]
Jeffrey Everling commented on SYNCOPE-903: ------------------------------------------ Hello Fabio, Thank you for your quick reply. I think you are right. I can find 2 provisioning.properties and they both are containing postgresql configuration. Do I need to adjust both? /opt/syncope-2.0.0-M2/identitybox/core/src/main/resources/provisioning.properties /opt/syncope-2.0.0-M2/identitybox/core/target/classes/provisioning.properties I am having a hard time finding the documentation on the Syncope configuration. Where can I find this information? I have found the following sources, but they are rather limited: https://syncope.apache.org/docs/getting-started.html https://syncope.apache.org/docs/reference-guide.html https://cwiki.apache.org/confluence/display/SYNCOPE/Index;jsessionid=B78878E91F067D6BFDA75B12D249CDBF > Scheduler not operational due to lowercase MySQL tables > ------------------------------------------------------- > > Key: SYNCOPE-903 > URL: https://issues.apache.org/jira/browse/SYNCOPE-903 > Project: Syncope > Issue Type: Bug > Components: archetype, core > Affects Versions: 2.0.0-M4 > Environment: MySQL Database > Reporter: Jeffrey Everling > > Hello, > After deploying the latest version of Syncope, I noticed that I could not > create any pull tasks. When I took a look at the error and compared this to > the database structure it has generated, I noticed that Syncope is searching > for an uppercase name where my database tables are lower case. > Error: > 17:40:22.279 ERROR org.apache.syncope.client.console.wizards.AjaxWizard - > Wizard error on finish > org.apache.syncope.common.lib.SyncopeClientException: Scheduling [Failure > obtaining db row lock: Table 'syncope.QRTZ_LOCKS' doesn't exist {prepstmnt > 1156556661 SELECT * FROM QRTZ_LOCKS WHERE SCHED_NAME = > 'scheduler' AND LOCK_NAME = ? FOR UPDATE} [code=1146, state=42S02]] > SQL table view: > +--------------------------------+ > | Tables_in_syncope | > +--------------------------------+ > | ACT_EVT_LOG | > | ACT_GE_BYTEARRAY | > | ACT_GE_PROPERTY | > | ACT_HI_ACTINST | > | ACT_HI_ATTACHMENT | > | ACT_HI_COMMENT | > | ACT_HI_DETAIL | > | ACT_HI_IDENTITYLINK | > | ACT_HI_PROCINST | > | ACT_HI_TASKINST | > | ACT_HI_VARINST | > | ACT_ID_GROUP | > | ACT_ID_INFO | > | ACT_ID_MEMBERSHIP | > | ACT_ID_USER | > | ACT_PROCDEF_INFO | > | ACT_RE_DEPLOYMENT | > | ACT_RE_MODEL | > | ACT_RE_PROCDEF | > | ACT_RU_EVENT_SUBSCR | > | ACT_RU_EXECUTION | > | ACT_RU_IDENTITYLINK | > | ACT_RU_JOB | > | ACT_RU_TASK | > | ACT_RU_VARIABLE | > | ADynGroupMembership | > | ADynGroupMembership_AnyObject | > | AMembership | > | APlainAttr | > | APlainAttrUniqueValue | > | APlainAttrValue | > | ARelationship | > | AccountPolicy | > | AccountPolicy_ExternalResource | > | AccountRuleConfInstance | > | AnyAbout | > | AnyObject | > | AnyObject_AnyTypeClass | > | AnyObject_ExternalResource | > | AnyTemplatePullTask | > | AnyTemplateRealm | > | AnyType | > | AnyTypeClass | > | AnyType_AnyTypeClass | > | CPlainAttr | > | CPlainAttrUniqueValue | > | CPlainAttrValue | > | ConnInstance | > | ConnInstance_capabilities | > | DerSchema | > | DynRoleMembership | > | DynRoleMembership_User | > | ExternalResource | > | ExternalResource_PropActions | > | ExternalResource_capOverride | > | GPlainAttr | > | GPlainAttrUniqueValue | > | GPlainAttrValue | > | MailTemplate | > | Mapping | > | MappingItem | > | MappingItem_Transformer | > | Notification | > | NotificationTask_recipients | > | Notification_events | > | Notification_staticRecipients | > | OPENJPA_SEQUENCES_TABLE | > | PasswordPolicy | > | PasswordRuleConfInstance | > | PlainSchema | > | Provision | > | PullPolicy | > | PullTask_actionsClassNames | > | PushPolicy | > | PushTaskAnyFilter | > | PushTask_actionsClassNames | > | Realm | > | Realm_actionsClassNames | > | RelationshipType | > | Report | > | ReportExec | > | ReportTemplate | > | ReportletConfInstance | > | SYNCOPEAUDIT | > | SecurityQuestion | > | SyncopeConf | > | SyncopeDomain | > | SyncopeGroup | > | SyncopeGroup_AnyTypeClass | > | SyncopeGroup_ExternalResource | > | SyncopeLogger | > | SyncopeRole | > | SyncopeRole_Realm | > | SyncopeRole_entitlements | > | SyncopeUser | > | SyncopeUser_AnyTypeClass | > | SyncopeUser_ExternalResource | > | SyncopeUser_SyncopeRole | > | SyncopeUser_passwordHistory | > | Task | > | TaskExec | > | TypeExtension | > | TypeExtension_AnyTypeClass | > | UDynGroupMembership | > | UDynGroupMembership_User | > | UMembership | > | UPlainAttr | > | UPlainAttrUniqueValue | > | UPlainAttrValue | > | URelationship | > | VirSchema | > | anyObject_search | > | anyObject_search_adyngmemb | > | anyObject_search_amembership | > | anyObject_search_arelationship | > | anyObject_search_attr | > | anyObject_search_group_res | > | anyObject_search_null_attr | > | anyObject_search_resource | > | anyObject_search_unique_attr | > | group_search | > | group_search_attr | > | group_search_null_attr | > | group_search_resource | > | group_search_unique_attr | > | qrtz_fired_triggers | > | qrtz_locks | > | qrtz_paused_trigger_grps | > | qrtz_scheduler_state | > | user_search | > | user_search_attr | > | user_search_dynrmemb | > | user_search_group_res | > | user_search_null_attr | > | user_search_resource | > | user_search_role | > | user_search_udyngmemb | > | user_search_umembership | > | user_search_unique_attr | > | user_search_urelationship | > +--------------------------------+ > I discussed this issue over IRC and as per advice I have tried upgrading the > database (Current MySQL version: 5.5). The JDBC connector was already the > latest version. > But still MySQL is operating in a case sensitive way as far as I can check by > performing the following queries: > mysql> select * from QRTZ_LOCKS; > ERROR 1146 (42S02): Table 'syncope.QRTZ_LOCKS' doesn't exist > mysql> select * from qrtz_locks; > Empty set (0.00 sec) > Can you please advise about this matter? I would like to continue building > the demo, but I would like to hear first if I can simply rename the database > tables, or that I should proceed in another way. > Kind regards, > Jeffrey Everling -- This message was sent by Atlassian JIRA (v6.3.4#6332)