[
https://issues.apache.org/jira/browse/OOZIE-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17423344#comment-17423344
]
meitingli commented on OOZIE-3638:
----------------------------------
When I installed Oozie, it used Derby database automatically, could I change
the database it used?
Besides, there is no process using the derby database before I start Oozie. The
*.lck files are created after Oozie starting. I find if I remove the *.lck
files, I can use other command such like ooziedb.sh version successed. Why
oozie would create the *.lck files, I'm not sure if these files cause the
locking.
> Execute command failed after oozie started
> ------------------------------------------
>
> Key: OOZIE-3638
> URL: https://issues.apache.org/jira/browse/OOZIE-3638
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 5.2.0
> Reporter: meitingli
> Priority: Major
> Attachments: image-2021-09-30-19-39-53-160.png,
> image-2021-09-30-19-40-00-109.png, image-2021-09-30-19-40-08-394.png,
> image-2021-09-30-19-41-18-290.png
>
>
> The version of oozie and the kernel version of OS as below:
> !image-2021-09-30-19-41-18-290.png!
> # Set the java path
> export JAVA_HOME=/usr/lib/jvm/$java11_version
> export PATH=$JAVA_HOME/bin:$PATH
> export CLASSPATH=.:$JAVA_HOME/lib/dt.jar:$JAVA_HOME/lib/tools.jar
> # Execute below command to start oozie
> oozie-start.sh
> # Check the path /var/cache/oozie/data/oozie-db， there were *.lck files
> created. !image-2021-09-30-19-40-08-394.png!
> # Executed other command line, such like ooziedb.sh version, it would pop up
> error that the database failed to start.
> !image-2021-09-30-19-39-53-160.png!!image-2021-09-30-19-40-00-109.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
