Oracle Server issues/fixes
Most applications work without a hitch when set up in the Fresh Start machine on DaDesktop (DD). But a couple of them don’t function as expected after cloning and need a few extra steps to run normally.
System Details
-
Oracle Database 19c, (other versions will probably exhibit the same behaviour)
- Installed using Windows 10 template
Fresh Start Fix Notes
-
Please note this is a generic guide to fixing this application when using it in the Fresh Start machine. Steps may be different depending on your exact setup configuration.
-
Here’s a summary of the fix for Fresh Start: The Fresh Start machine’s hostname is used initially, but after cloning, the machine name changes, so the original hostname is no longer valid. Instead, we use 127.0.0.1 (localhost) rather than the original hostname. Extra database Listeners may also be present, which can confuse the configuration—these are best removed, as shown below.
Fix process
1. The screenshot below shows a database connection network failure when using the Oracle SQL Developer application.
2. Launch the Oracle Net Manager application.
The XE service details are shown, displaying the original host info (in this case alexei-uuae.vm).
3. The connection test fails (using userid=system and password).
4. In Oracle Net Manager, go to Listening Locations, then Listener.
The host details show the original hostname 'alexei-uue.vm', which will need to be changed.
5. No databases appear as configured to work with LISTENER1. Check for any Listeners that don’t have database services configured for them, and delete them if you find any.
6. Therefore, delete LISTENER1 and confirm. Note: This is an example of what happened in our setup, but it may not always be the case; it’s just provided here as an illustration.
7. For the DEFAULT SERVER LISTENER, check each Listener in turn; in this case, no listening location is available.
8. So, delete the DEFAULT SERVER LISTENER.
9. For LISTENER (the only one left now), you’ll see the existing VM hostname, which needs to be changed since it will differ after cloning.
10. Change the host from the one shown (in our case 'alexi.uuae.vm') to 127.0.0.1, leaving the port as before.
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 and restart the listener service.
Type ‘lsnrctl status’ and then 'lsnrctl stop'.
Type 'lsnrctl start'.
Launch Oracle Net Manager again.
14. Remove alexei-vm from the Service-naming -> xe section.
15. Change the host to 127.0.0.1.
16. Save the network connection.
17. Connection Test. Click the small button in the image below to run the Connection Test.
18. Change the login details: set the username to ‘system’ and enter the password.
Save the network connection if necessary.
19. Go back to the main Oracle SQL Developer app and run the Connection test again.
20. Assuming the connection succeeds, go to Connections on the left-hand side of the screen, expand Oracle Connections, and confirm that the database tables appear as expected.
21. Continue with the FreshStart machine configuration as needed, and clone the FreshStart machines to the Trainer’s and Participants’ machines.
The Oracle Database server should now run correctly on the Trainers’ and Participants’ machines.
If you still experience issues, please get in contact with DaDesktop Support via the chat app, and we’ll be happy to help.