Oracle Server issues/fixes

Most applications work perfectly normally when prepared on a Fresh Start machine using DaDesktop (DD) in the UK. However, one or two applications may not function as expected after the cloning process, requiring a few extra steps to restore normal operation.

System Details

• Oracle Database 19c, (other versions will probably exhibit the same behaviour)

• Installed using a Windows 10 template

 

Fresh Start Fix Notes

1. Please note that this is a general guide to resolving this application's issues when using it within Fresh Start. The steps may differ depending on your exact setup configuration.

2. Summary – The fix for Fresh Start involves using the localhost IP 127.0.0.1 instead of the original hostname, as the machine’s hostname changes when cloned. Extra database listeners often get added, which can confuse the configuration; it is best to remove them as shown below.
   
    

Fix process

1. The image below shows a database connection network failure when using Oracle SQL Developer.

2. Launch Oracle Net Manager.

XE service details are displayed, with the original host information (in this case alexei-uuae.vm).

3. The connection test fails (enter userid=system and password).

4. Under Oracle Net Manager, go to Listening Locations, then Listener.
The host details show the original hostname 'alexei-uue.vm', which will be changed.

5. No databases appear configured for LISTENER1. Check for any listeners that lack database services configured, and delete them if found.

6. Therefore, delete LISTENER1 and confirm. Note: this is an example from our setup and may not always apply, but is shown here for illustration.

7. DEFAULT SERVER LISTENER – Check each listener in turn; in this case, no listening location is available.

8. Hence, delete DEFAULT SERVER LISTENER.

9. On LISTENER (the only one remaining), you'll see the existing virtual machine hostname, which needs changing as it will be altered during cloning.

10. Change the host from '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 Command Prompt; we will restart the listener service.

Type 'lsnrctl status', then 'lsnrctl stop', and finally 'lsnrctl start'.

Launch Oracle Net Manager once more.

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 shown in the image below to run the connection test.

18. Amend the login details. Set the username to 'system', and enter the appropriate password.

Save the network connection if prompted.

19. Return to the main Oracle SQL Developer application and run the connection test again.

20. Assuming a successful connection, go to the Connections pane on the left, expand Oracle Connections, and confirm that the database tables appear as expected.

21. Proceed with the FreshStart machine configuration as required, then clone the FreshStart machines to both trainer and participant machines.

The Oracle database server should now run correctly on both trainer and participant machines.

If you continue to experience issues, please contact DaDesktop Support via the chat app; we'll be happy to assist.