![]() It bounces once or twice in the dock and then nothing. I learned that SQL Developer should ask the user where the JAVA_HOME is located when they first launch the app, but it never did for me. ![]() So, if my system didn't know where JAVA_HOME was, I didn't think SQL Developer probably knew, either. I tested this by opening my terminal app and typing echo $JAVA_HOME, which returned nothing. This happened after my upgrade to macOS Big Sur. It seems like, somewhere in the upgrade, SQL Developer (or a configuration file somewhere) lost the location of the Java JDK, typically expressed as the JAVA_HOME environmental variable. There are always some growing pains when upgrading to a new operating system, and one problem I ran into was not being able to launch Oracle SQL Developer.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |