Oracle Server Troubleshooting and Fixes

When you set up applications on a Fresh Start machine in DaDesktop (DD), most work completely fine. However, a couple of them won’t behave as expected after cloning, and you’ll need to take a few additional steps to get them running smoothly.

System Details

• Oracle Database 19c – other versions are likely to behave the same way.

• Installed using Windows 10 template

 

Fixing Fresh Start: Key Notes

1. Keep in mind that this is a general guide for resolving issues with this application in Fresh Start. The exact steps might vary based on your specific setup.

2. In a nutshell: the fix on Fresh Start involves using 127.0.0.1 (localhost) instead of the original machine hostname, because after cloning the hostname changes and no longer matches. Also, any additional database Listeners that were set up can cause confusion and are best removed, as shown below.
   
    

The Fix Process

1. Here you can see a database connection failure using Oracle SQL Developer.

2. Open the Oracle Net Manager application.

The xe service details appear, showing the original host information (here, alexei-uuae.vm).

3. The connection test fails (after entering userid=system and the password).

4. In Oracle Net Manager, under Listening Locations, select Listener.
The host details show the original hostname 'alexei-uue.vm', which will be changed.

5. No databases appear as configured for LISTENER1. Look for any Listeners that lack database service configurations and delete them if found.

6. So delete LISTENER1 and confirm. Note: this happened in our setup but may not occur for everyone – it’s just an example.

7. DEFAULT SERVER LISTENER – go through each Listener. In this instance, there is no listening location available.

8. So, delete the DEFAULT SERVER LISTENER.

9. Now only LISTENER remains. Notice the existing VM hostname, which must be updated because it changes after cloning.

10. Change the host from the one shown (in our example, 'alexi.uuae.vm') to 127.0.0.1, leaving the port unchanged.

Next, configure the existing database. 

11. Set 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 to restart the listener service.

Run ‘lsnrctl status’, then ‘lsnrctl stop’.

Then ‘lsnrctl start’.

Open Oracle Net Manager once more.

14. Delete alexei-vm from Service-naming- > xe.

15. Change the host to 127.0.0.1. 

16. Save the network connection.

17. Run a Connection Test. Click the small button shown in the image below to trigger the test.

18. Update the login: set the username to ‘system’ and enter the password.

Save the network connection if prompted.

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

20. If the connection succeeds, navigate to the Connections panel on the left, expand Oracle Connections, and verify that the database tables appear as expected.

21. Proceed with any remaining FreshStart machine configuration, then clone the FreshStart machines to the trainer’s and participants’ systems. The Oracle Database server should now operate correctly on both trainer and participant machines. If you still encounter problems, reach out to DaDesktop Support through the chat app – we're happy to assist.