Oracle Server issues/fixes
Most applications run perfectly fine when set up on a Fresh Start machine with DaDesktop (DD). But a couple of apps don’t behave as expected after cloning, so they need a few extra steps to get them working properly.
System Details
-
Oracle Database 19c (other versions will likely show the same behaviour)
- Installed using a Windows 10 template
Fresh Start Fix Notes
-
Keep in mind this is a general guide to sorting out this application inside Fresh Start. The exact steps might vary depending on your specific setup.
-
In a nutshell, here’s the fix for Fresh Start. The Fresh Start machine has a hostname, but after cloning, the machine name changes, so that original hostname no longer makes sense. Instead, we use 127.0.0.1 (localhost). On top of that, there are extra database Listeners tacked on that muddy the configuration — it’s best to remove them as shown below.
Fix process
1. The picture below shows the database connection network failure you’ll see when using Oracle SQL Developer.
2. Launch the Oracle Net Manager application.
xe service details are listed, with the original host info (in this case alexei-uuae.vm).
3. The connection test fails (after entering userid=system and password).
4. In Oracle Net Manager, under Listening Locations, go to Listener.
The host details show the original hostname ‘alexei-uue.vm’ — this will be changed.
5. No databases appear configured to work with LISTENER1. Check for any Listeners that may not have database services set up for them. If you find one, delete that Listener.
6. So, go ahead and delete LISTENER1 and confirm. Just a heads-up: this is what happened in our setup, but it might not always be the case; it’s shown here as an example.
7. DEFAULT SERVER LISTENER — Check each Listener one at a time. In this situation, there’s no listening location set up.
8. So, delete the DEFAULT SERVER LISTENER.
9. Now only LISTENER remains. You can see the existing VM hostname, which needs changing since it will be different after cloning.
10. Change the host from what’s shown (in our case ‘alexi.uuae.vm’) to 127.0.0.1, keeping the port the same.
Next, configure the existing database.
11. Change the SID to XE, and the Global Database Name to xe.local.
12. Save the network configuration and close the application.
13. Open a Command prompt; we’ll restart the listener service.
Type ‘lsnrctl status’, then ‘lsnrctl stop’
Type ‘lsnrctl start’
Launch Oracle Net Manager again.
14. Remove alexei-vm from Service-naming > xe section.
15. Change the host to 127.0.0.1.
16. Save the network connection.
17. Connection Test. Click the little button shown below to run the Connection Test.
18. Change the login. Set the username to ‘system’ and enter the password.
Save the network connection if needed.
19. Go back to the main Oracle SQL Developer app. Run the Connection test again.
20. Assuming the connection is successful, go to Connections on the left-hand screen, expand Oracle Connections, and confirm that the database tables are showing up as you’d expect.
21. Continue with the FreshStart machine setup as needed, then clone the FreshStart machines to the Trainer and Participant machines.
The Oracle Database server should now run properly on the Trainers’ and Participants’ machines.
If you still run into trouble, please reach out to DaDesktop Support through the chat app and we’ll be happy to lend a hand.