Login Register

Oracle Server Issues and Fixes

Most applications run perfectly when set up on a Fresh Start machine using DaDesktop (DD) across Australia. However, a couple of applications can be a bit temperamental after cloning and need a few extra tweaks to get back on track.

System Details

 

Fresh Start Fix Notes

  1. Just a heads-up – this is a general guide for fixing the application when using Fresh Start. The exact steps might vary a bit based on your particular setup configuration.

  2. Summary of the fix: The Fresh Start machine's hostname is used initially, but after cloning, the machine gets a new name, so the old hostname becomes meaningless. We'll switch to using 127.0.0.1 (localhost) instead. Plus, there might be extra database listeners thrown into the mix that confuse things, so it's best to delete them as shown below.

     

Fix process

1. Here's an example of a database connection network failure in the Oracle SQL Developer application.

Failure Test

2. Open the Oracle Net Manager application.

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

Oracle Net Manager

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

Connection test fails

4. In Oracle Net Manager, under Listening Locations for the Listener, you'll see the host details showing the original hostname 'alexei-uue.vm'. This needs to be changed.

5. No databases appear to be configured for LISTENER1. Check each listener to see if any are missing database service configurations. If you find one, delete that listener.

Listeners

6. So delete LISTENER1 and confirm. (Note: This is an example from our setup; your situation may differ, but it's shown here as a guide.)

Delete Listener

7. For the DEFAULT SERVER LISTENER, check each listener – in this case, there's no listening location available.

Default Listener

8. So delete the DEFAULT SERVER LISTENER.

Delete Listener

9. Now on the remaining LISTENER, you'll see the existing VM hostname that needs to be swapped out, as it'll change during cloning.

Fix Network

10. Change the host from the old one (in our case 'alexi.uuae.vm') to 127.0.0.1, keeping the port unchanged.

Chnage Network

Next, configure the existing database.

11. Change 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 a Command Prompt and restart the listener service. Type 'lsnrctl status', then 'lsnrctl stop', and finally 'lsnrctl start'.

Cmd prompt

Open 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. Test the connection: Click the small button shown in the image below to run the Connection Test.

Click to test

18. Change the login: set the username to 'system' and enter the password.

Connection test succesful

Save the network connection if prompted.

19. Return to the main Oracle SQL Developer app and run the connection test once more.

Oracle app

20. Assuming the connection is successful, go to the Connections panel on the left, expand Oracle Connections, and confirm that the database tables are displaying as expected.

21. Continue with the FreshStart machine configuration as needed, then clone the machines to the trainer's and participants' machines.

The Oracle Database server should now be running properly on both trainers' and participants' machines.

If you're still running into trouble, reach out to DaDesktop Support through the chat app – we're here to help.