{"id":2144,"date":"2016-07-12T20:58:28","date_gmt":"2016-07-12T18:58:28","guid":{"rendered":"http:\/\/www.oradba.ch\/?p=2144"},"modified":"2016-07-12T20:58:28","modified_gmt":"2016-07-12T18:58:28","slug":"change-default-java_home-for-oud-instance","status":"publish","type":"post","link":"https:\/\/www.oradba.ch\/wordpress\/2016\/07\/change-default-java_home-for-oud-instance\/","title":{"rendered":"Change default JAVA_HOME for OUD Instance"},"content":{"rendered":"<p>I just had a situation where I had to change the JAVA_HOME for my <a href=\"https:\/\/www.oradba.ch\/wordpress\/category\/oud\/\">Oracle Unified Directory<\/a> (OUD) instance. Although this is quite simple, this blog post serves as my &#8220;sticky note&#8221;. <\/p>\n<p>During the setup of my OUD instance I&#8217;ve set the wrong JAVA_HOME. I&#8217;ve used JDK 1.8 instead recommended JRE 1.7. OUD does work well with Java 1.8, but it is just not a &#8220;certified configuration&#8221;. You never know which bug is coming next \ud83d\ude09 . Because my OUD Instance is used productive, I decided to change it back to JRE 1.7 Update 101. If you OUD server runs a couple of months, Java has to be updated regularly anyway due to vulnerabilities.<\/p>\n<p>The JVM and Java arguments for each command is specified in properties file, which is in the <code class=\"EnlighterJSRAW\" data-enlighter-language=\"bash\">INSTANCE_DIR\/OUD\/config\/java.properties<\/code>. To adjust the JVM settings, the OUD Instance must of course be stopped. New setting will then be applied with <em>dsjavaproperties<\/em>.<\/p>\n<p>First set the proper default Java Home. I will use JRE 1.7 Update 101.<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"bash\">\r\noracle@urania:~\/ [oud_eus] vi $ORACLE_HOME\/OUD\/config\/java.properties\r\n\r\n\r\ndefault.java-home=\/u00\/app\/oracle\/product\/java\/jre1.7.0_101\r\n<\/pre>\n<p>Stop the Directory Server using <em>stop-ds<\/em>.<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"bash\">oracle@urania:~\/ [oud_eus] stop-ds\r\nStopping Server...\r\n\r\n[12\/Jul\/2016:17:43:28 +0200] category=BACKEND severity=NOTICE msgID=9896306 msg=The backend cn=OIDCompatibility,cn=Workflow Elements,cn=config is now taken offline\r\n[12\/Jul\/2016:17:43:28 +0200] category=BACKEND severity=NOTICE msgID=9896306 msg=The backend cn=OracleContext0,cn=Workflow elements,cn=config is now taken offline\r\n[12\/Jul\/2016:17:43:29 +0200] category=BACKEND severity=NOTICE msgID=9896306 msg=The backend cn=userRoot,cn=Workflow Elements,cn=config is now taken offline\r\n[12\/Jul\/2016:17:43:29 +0200] category=BACKEND severity=NOTICE msgID=9896306 msg=The backend cn=virtualAcis,cn=Workflow Elements,cn=config is now taken offline\r\n[12\/Jul\/2016:17:43:29 +0200] category=CORE severity=NOTICE msgID=458955 msg=The Directory Server is now stopped<\/pre>\n<p>Apply new java configuration with <em>dsjavaproperties<\/em>.<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"bash\">oracle@urania:~\/ [oud_eus] dsjavaproperties \r\nThe operation was successful.  The server commands will use the java arguments\r\nand java home specified in the properties file located in\r\n\/u00\/app\/oracle\/product\/middleware\/oud_instances\/oud_eus\/OUD\/config\/java.properties<\/pre>\n<p>Start the Directory Server using <em>start-ds<\/em>.<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"bash\">oracle@urania:~\/ [oud_eus] start-ds\r\n[12\/Jul\/2016:17:44:09 +0200] category=CORE severity=INFORMATION msgID=132 msg=The Directory Server is beginning the configuration bootstrapping process\r\n[12\/Jul\/2016:17:44:11 +0200] category=CORE severity=NOTICE msgID=458886 msg=Oracle Unified Directory 11.1.2.3.160419 (build 20160315213404Z, R1603151302) starting up\r\n[12\/Jul\/2016:17:44:17 +0200] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381717 msg=Installation Directory:  \/u00\/app\/oracle\/product\/middleware\/oud_11.1.2.3.0\r\n[12\/Jul\/2016:17:44:17 +0200] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381719 msg=Instance Directory:      \/u00\/app\/oracle\/product\/middleware\/oud_instances\/oud_eus\/OUD\r\n[12\/Jul\/2016:17:44:17 +0200] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381713 msg=JVM Information: 1.7.0_101-b14 by Oracle Corporation, 64-bit architecture, 121634816 bytes heap size\r\n[12\/Jul\/2016:17:44:17 +0200] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381714 msg=JVM Host: urania.postgasse.org, running Linux 4.1.12-37.4.1.el6uek.x86_64 amd64, 3875069952 bytes physical memory size, number of processors available 2\r\n[12\/Jul\/2016:17:44:17 +0200] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381715 msg=JVM Arguments: &quot;-Xms130m&quot;, &quot;-Xmx130m&quot;, &quot;-Dorg.opends.server.scriptName=start-ds&quot;\r\n[12\/Jul\/2016:17:44:17 +0200] category=ACCESS_CONTROL severity=INFORMATION msgID=12582978 msg=Added 16 Global Access Control Instruction (ACI) attribute types to the access control evaluation engine\r\n[12\/Jul\/2016:17:44:18 +0200] category=BACKEND severity=INFORMATION msgID=9437595 msg=Local DB backend OracleContext0 does not specify the number of lock tables: defaulting to 97\r\n[12\/Jul\/2016:17:44:18 +0200] category=BACKEND severity=INFORMATION msgID=9437594 msg=Local DB backend OracleContext0 does not specify the number of cleaner threads: defaulting to 24 threads\r\n[12\/Jul\/2016:17:44:18 +0200] category=BACKEND severity=INFORMATION msgID=9437615 msg=Local DB backend OracleContext0 does not specify the percentage of the heap space to allocate to the database cache: defaulting to 35 percent\r\n[12\/Jul\/2016:17:44:18 +0200] category=BACKEND severity=INFORMATION msgID=9437613 msg=Local DB backend OracleContext0 does not specify the size of the file handle cache: sizing automatically to use 100 file descriptors\r\n[12\/Jul\/2016:17:44:19 +0200] category=JEB severity=NOTICE msgID=8847402 msg=The database backend cn=OracleContext0,cn=Workflow elements,cn=config containing 82 entries has started\r\n[12\/Jul\/2016:17:44:19 +0200] category=ACCESS_CONTROL severity=INFORMATION msgID=12582962 msg=Added 5 Access Control Instruction (ACI) attribute types found in context &quot;cn=OracleContext,dc=postgasse,dc=org&quot; to the access control evaluation engine\r\n[12\/Jul\/2016:17:44:19 +0200] category=BACKEND severity=INFORMATION msgID=9437595 msg=Local DB backend virtualAcis does not specify the number of lock tables: defaulting to 97\r\n[12\/Jul\/2016:17:44:19 +0200] category=JEB severity=NOTICE msgID=8847402 msg=The database backend cn=virtualAcis,cn=Workflow Elements,cn=config containing 0 entries has started\r\n[12\/Jul\/2016:17:44:20 +0200] category=BACKEND severity=INFORMATION msgID=9437595 msg=Local DB backend userRoot does not specify the number of lock tables: defaulting to 97\r\n[12\/Jul\/2016:17:44:20 +0200] category=BACKEND severity=INFORMATION msgID=9437594 msg=Local DB backend userRoot does not specify the number of cleaner threads: defaulting to 24 threads\r\n[12\/Jul\/2016:17:44:20 +0200] category=BACKEND severity=INFORMATION msgID=9437615 msg=Local DB backend userRoot does not specify the percentage of the heap space to allocate to the database cache: defaulting to 35 percent\r\n[12\/Jul\/2016:17:44:20 +0200] category=BACKEND severity=INFORMATION msgID=9437613 msg=Local DB backend userRoot does not specify the size of the file handle cache: sizing automatically to use 100 file descriptors\r\n[12\/Jul\/2016:17:44:20 +0200] category=JEB severity=NOTICE msgID=8847402 msg=The database backend cn=userRoot,cn=Workflow Elements,cn=config containing 141 entries has started\r\n[12\/Jul\/2016:17:44:21 +0200] category=BACKEND severity=INFORMATION msgID=9437595 msg=Local DB backend OIDCompatibility does not specify the number of lock tables: defaulting to 97\r\n[12\/Jul\/2016:17:44:21 +0200] category=BACKEND severity=INFORMATION msgID=9437594 msg=Local DB backend OIDCompatibility does not specify the number of cleaner threads: defaulting to 24 threads\r\n[12\/Jul\/2016:17:44:21 +0200] category=BACKEND severity=INFORMATION msgID=9437615 msg=Local DB backend OIDCompatibility does not specify the percentage of the heap space to allocate to the database cache: defaulting to 35 percent\r\n[12\/Jul\/2016:17:44:21 +0200] category=BACKEND severity=INFORMATION msgID=9437613 msg=Local DB backend OIDCompatibility does not specify the size of the file handle cache: sizing automatically to use 100 file descriptors\r\n[12\/Jul\/2016:17:44:22 +0200] category=JEB severity=NOTICE msgID=8847402 msg=The database backend cn=OIDCompatibility,cn=Workflow Elements,cn=config containing 29 entries has started\r\n[12\/Jul\/2016:17:44:22 +0200] category=ACCESS_CONTROL severity=INFORMATION msgID=12582962 msg=Added 10 Access Control Instruction (ACI) attribute types found in context &quot;cn=OracleContext&quot; to the access control evaluation engine\r\n[12\/Jul\/2016:17:44:22 +0200] category=ACCESS_CONTROL severity=INFORMATION msgID=12582962 msg=Added 1 Access Control Instruction (ACI) attribute types found in context &quot;cn=OracleSchemaVersion&quot; to the access control evaluation engine\r\n[12\/Jul\/2016:17:44:22 +0200] category=EXTENSIONS severity=INFORMATION msgID=1048797 msg=DIGEST-MD5 SASL mechanism using a server fully qualified domain name of: urania.postgasse.org\r\n[12\/Jul\/2016:17:44:22 +0200] category=CORE severity=INFORMATION msgID=731 msg=LDAP Connection Handler 0.0.0.0 port 1389 does not specify the number of request handler threads: sizing automatically to use 8 threads\r\n[12\/Jul\/2016:17:44:22 +0200] category=CORE severity=INFORMATION msgID=731 msg=LDAP Connection Handler 0.0.0.0 port 1636 does not specify the number of request handler threads: sizing automatically to use 8 threads\r\n[12\/Jul\/2016:17:44:22 +0200] category=CORE severity=INFORMATION msgID=720 msg=No worker queue thread pool size specified: sizing automatically to use 24 threads\r\n[12\/Jul\/2016:17:44:23 +0200] category=PROTOCOL severity=NOTICE msgID=2556180 msg=Started listening for new connections on Administration Connector 0.0.0.0 port 4444\r\n[12\/Jul\/2016:17:44:23 +0200] category=PROTOCOL severity=NOTICE msgID=2556180 msg=Started listening for new connections on LDAP Connection Handler 0.0.0.0 port 1389\r\n[12\/Jul\/2016:17:44:23 +0200] category=PROTOCOL severity=NOTICE msgID=2556180 msg=Started listening for new connections on LDAP Connection Handler 0.0.0.0 port 1636\r\n[12\/Jul\/2016:17:44:23 +0200] category=CORE severity=NOTICE msgID=458887 msg=The Directory Server has started successfully\r\n[12\/Jul\/2016:17:44:23 +0200] category=CORE severity=NOTICE msgID=458891 msg=The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerStarted, alert ID 458887):  The Directory Server has started successfully<\/pre>\n<p>Information on <em>dsjavaproperties<\/em> can be found in the Oracle\u00ae Fusion Middleware Administering Oracle Unified Directory 11g Release 2 (11.1.2) <a href=\"http:\/\/docs.oracle.com\/cd\/E52734_01\/oud\/OUDAG\/appendix_cli.htm#OUDAG01148\">A.2.5 dsjavaproperties<\/a>.<\/p>\n<p>More short blog posts are marked as <a href=\"https:\/\/www.oradba.ch\/wordpress\/tag\/sticky-notes\/\">sticky notes<\/a> in the future. I have enough Ideas for future short post or sticky notes. But time to write them is an other story&#8230;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I just had a situation where I had to change the JAVA_HOME for my Oracle Unified Directory (OUD) instance. Although this is quite simple, this blog post serves as my &#8220;sticky note&#8221;. During the setup of my OUD instance I&#8217;ve set the wrong JAVA_HOME. I&#8217;ve used JDK 1.8 instead recommended JRE 1.7. OUD does work [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"Change default JAVA_HOME for #OUD Instance #trivadis","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[142],"tags":[156,111],"class_list":["post-2144","post","type-post","status-publish","format-standard","hentry","category-oud","tag-sticky-notes","tag-tvdsecexpert"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p1aErb-yA","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":2609,"url":"https:\/\/www.oradba.ch\/wordpress\/2018\/05\/oracle-unified-directory-systemd-unit-file\/","url_meta":{"origin":2144,"position":0},"title":"Oracle Unified Directory systemd unit file","author":"Stefan","date":"16. May 2018","format":false,"excerpt":"About a year ago I explained in the blog post Start OUD Servers on Boot using systemd how to start Oracle Unified Directory automatically on system startup. In the meantime a lot has changed, so has my unit file. The simple unit file actually worked quite well. Until the time\u2026","rel":"","context":"In &quot;Linux&quot;","block_context":{"text":"Linux","link":"https:\/\/www.oradba.ch\/wordpress\/category\/linux-2\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2431,"url":"https:\/\/www.oradba.ch\/wordpress\/2017\/11\/install-oracle-unified-directory-12c-the-smart-way\/","url_meta":{"origin":2144,"position":1},"title":"Install Oracle Unified Directory 12c the smart way","author":"Stefan","date":"23. November 2017","format":false,"excerpt":"Installing Oracle Unified Directory has always been easy. The installation guide for OUD 11c as well OUD 12 is simple and straight forward. Additionally Oracle does provide a couple of MOS notes for different deployment scenarios. Nevertheless there is always room for improvement :-) During my work on OUD to\u2026","rel":"","context":"In &quot;Howto&quot;","block_context":{"text":"Howto","link":"https:\/\/www.oradba.ch\/wordpress\/category\/howto\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2280,"url":"https:\/\/www.oradba.ch\/wordpress\/2017\/05\/start-oud-servers-on-boot-using-systemd\/","url_meta":{"origin":2144,"position":2},"title":"Start OUD Servers on Boot using systemd","author":"Stefan","date":"16. May 2017","format":false,"excerpt":"Starting Oracle Unified Directory on system boot is essential for production environment. Unfortunately OUD just provides a script to create the init.d script. But newer system in general use systemd initialise and startup. Nevertheless, creating a custom unit file for OUD is simple and straightforward. First, let's create a regular\u2026","rel":"","context":"In &quot;Linux&quot;","block_context":{"text":"Linux","link":"https:\/\/www.oradba.ch\/wordpress\/category\/linux-2\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2693,"url":"https:\/\/www.oradba.ch\/wordpress\/2018\/07\/oudbase-environment-scripts-for-oracle-unified-directory-part-1\/","url_meta":{"origin":2144,"position":3},"title":"OUDbase environment scripts for Oracle Unified Directory Part 1","author":"Stefan","date":"16. July 2018","format":false,"excerpt":"Almost two years ago I started writing environment scripts for my Oracle Unified Directory installations. At the beginning there were only 2-3 scripts, from which at some point a small project on GitHub emerged. A lot has changed since my blog post Environment Scripts for OUD. The current version of\u2026","rel":"","context":"In &quot;Oracle Unified Directory&quot;","block_context":{"text":"Oracle Unified Directory","link":"https:\/\/www.oradba.ch\/wordpress\/category\/oud\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.oradba.ch\/wordpress\/wp-content\/uploads\/Screen-Shot-2018-07-16-at-23.43.18-300x95.png?resize=350%2C200&ssl=1","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.oradba.ch\/wordpress\/wp-content\/uploads\/Screen-Shot-2018-07-16-at-23.43.18-300x95.png?resize=350%2C200&ssl=1 1x, https:\/\/i0.wp.com\/www.oradba.ch\/wordpress\/wp-content\/uploads\/Screen-Shot-2018-07-16-at-23.43.18-300x95.png?resize=525%2C300&ssl=1 1.5x"},"classes":[]},{"id":2456,"url":"https:\/\/www.oradba.ch\/wordpress\/2017\/12\/oracle-unified-directory-on-docker\/","url_meta":{"origin":2144,"position":4},"title":"Oracle Unified Directory on Docker","author":"Stefan","date":"13. December 2017","format":false,"excerpt":"A bit a while ago I've started to use Docker for miscellaneous purposes. Not really an early adopter, but I still hope I caught the train just in time. :-) In one of my customer project, I did have to set up a couple of OUD instance to develop and\u2026","rel":"","context":"In &quot;Docker&quot;","block_context":{"text":"Docker","link":"https:\/\/www.oradba.ch\/wordpress\/category\/docker\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.oradba.ch\/wordpress\/wp-content\/uploads\/OUD_Moby-300x209.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":2205,"url":"https:\/\/www.oradba.ch\/wordpress\/2016\/11\/environment-scripts-for-oud\/","url_meta":{"origin":2144,"position":5},"title":"Environment Scripts for OUD","author":"Stefan","date":"18. November 2016","format":false,"excerpt":"At Trivadis we do have the TVD-BasEnv\u2122 to standardizes and simplifies the handling of environments for Oracle database and application server landscapes. This inspired me to create something similar for Oracle Unified Directory environments. Although current versions of TVD-BasEnv\u2122 already support OUD and OID environment. I've had the situation, where\u2026","rel":"","context":"In &quot;Oracle Unified Directory&quot;","block_context":{"text":"Oracle Unified Directory","link":"https:\/\/www.oradba.ch\/wordpress\/category\/oud\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/posts\/2144","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/comments?post=2144"}],"version-history":[{"count":5,"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/posts\/2144\/revisions"}],"predecessor-version":[{"id":2152,"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/posts\/2144\/revisions\/2152"}],"wp:attachment":[{"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/media?parent=2144"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/categories?post=2144"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/tags?post=2144"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}