Oracle Server Issues and Fixes

Most applications run without any issues on a Fresh Start machine with DaDesktop (DD). However, a couple of applications might not work as expected after cloning, and may require some additional configuration to function properly.

System Details

Oracle Database 19c (other versions likely behave the same way)
Set up using a Windows 10 template

Fresh Start Fix Notes

Please note that this is a general guide for resolving this issue on Fresh Start. The steps may vary based on your specific configuration.
Summary — Follow the fix below. The Fresh Start machine’s hostname is used, but after cloning the machine name changes, making the original hostname irrelevant. So, we replace it with 127.0.0.1 (localhost). Also, extra Listeners may be present which cause confusion, and it’s best to remove them, as demonstrated below.

Fix Process

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

Failure Test

2. Open the Oracle Net Manager application.

The xe service details are displayed, along with the original host information (here alexei-uuae.vm).

Oracle Net Manager

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

Connection test fails

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

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

Listeners

6. Therefore, delete LISTENER1 and confirm. Note: This is an example from our own setup; your scenario may differ, but it serves as an illustration.

Delete Listener

7. For the DEFAULT SERVER LISTENER, check each Listener one by one. In this case, no listening location is present.

Default Listener

8. So, delete the DEFAULT SERVER LISTENER.

Delete Listener

9. Now, on the remaining LISTENER (the only one left), you’ll see the existing VM hostname, which must be updated because it will change after cloning.

Fix Network

10. Update the host from the current value (here 'alexi.uuae.vm') to 127.0.0.1, leaving the port unchanged.

Chnage Network

Next, configure the existing database.

11. Set the SID to XE and the Global Database Name to xe.local.

Change details of SID and global db name

12. Save the network configuration and close the application.

13. Open Command Prompt to restart the listener service.

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

Then run ‘lsnrctl start’.

Cmd prompt

Launch Oracle Net Manager once more.

14. Remove 'alexei-vm' from the Service Naming > xe section.

15. Set the host to 127.0.0.1.

16. Save the network connection.

17. Test the connection: click the small button shown in the image below to initiate the Connection Test.

Click to test

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

Connection test succesful

If needed, save the network connection again.

19. Return to the main Oracle SQL Developer application and run the Connection Test again.

Oracle app

20. Once the connection is successful, go to the Connections pane on the left, expand Oracle Connections, and verify that the database tables appear as expected.

21. Proceed with the remaining FreshStart configuration as needed, and clone the FreshStart machines to the Trainer and Participant machines.

The Oracle Database server should now operate correctly on both Trainer and Participant machines.

If you continue to face difficulties, reach out to DaDesktop Support through the chat application. We’ll be glad to assist.