✉️contact@dadesktop.com.br
🌐 Português

Oracle Server Issues and How to Fix Them

When you prepare applications in a Fresh Start machine using DaDesktop (DD), most of them run without any trouble. However, a couple of applications don't behave as expected after cloning and need a few extra steps to work properly.

System Details

 

Fresh Start Fix Notes

  1. Keep in mind this is a general guide for fixing this application within Fresh Start. Your specific configuration might call for slightly different steps.

  2. In brief – the fix for Fresh Start goes like this. The original machine's hostname is used, but after cloning, the machine name changes, so that original hostname no longer makes sense. Instead, we rely on 127.0.0.1 (localhost). Additionally, extra database Listeners are usually present and confuse the configuration; removing them, as shown below, is the cleanest approach.

     

The Fix Procedure

1. The image below captures the network failure when trying to connect to the database via Oracle SQL Developer.

Failure Test

2. Open the Oracle Net Manager application.

You'll see the XE service details, along with the original host info (in this case, alexei-uuae.vm).

Oracle Net Manager

3. Attempting a connection test (entering userid=system and the password) fails.

Connection test fails

4. In Oracle Net Manager, go to Listening Locations and then Listener.
The host details displaying the original hostname 'alexei-uue.vm' – this will be changed.

5. No databases are shown configured for LISTENER1. Look for any Listeners that lack database service configurations. If you find any, delete that Listener.

Listeners

6. So delete LISTENER1 and confirm the action. (Note: This is what occurred in our setup; it may not always be the case, but we include it here as an example.)

Delete Listener

7. DEFAULT SERVER LISTENER – Check each Listener. In this instance, no listening location is configured.

Default Listener

8. So delete the DEFAULT SERVER LISTENER as well.

Delete Listener

9. Now only LISTENER remains. Here you can see the existing VM hostname, which must be changed because cloning will assign a different name.

Fix Network

10. Replace the host (in our example, 'alexi.uuae.vm') with 127.0.0.1, leaving the port unchanged.

Change Network

Now configure the existing database 

11. Set the SID to XE, and change 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 a Command Prompt to restart the listener service.

Run the commands: lsnrctl status, then lsnrctl stop, and finally lsnrctl start.

Cmd prompt

Launch Oracle Net Manager again.

14. Go to Service Naming -> XE and remove the entry that mentions alexei-vm.

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 a connection test.

Click to test

18. Enter the login details: set the username to ‘system’ and provide the password.

Connection test successful

Save the network connection if prompted.

19. Go back to the main Oracle SQL Developer window and run the connection test once more.

Oracle app

20. Assuming the connection works, go to the Connections panel on the left, expand Oracle Connections, and confirm the database tables appear as expected.

21. Continue configuring the FreshStart machine as required, then clone the FreshStart machines to the Trainer and Participants' machines.

The Oracle Database server should now run correctly on the Trainers' and Participants' machines.

If you still run into issues, reach out to DaDesktop Support through the chat app – we're happy to help.