✉️contact@dadesktop.co.nz

Oracle Server Issues and Fixes

Most applications run perfectly fine when set up on a Fresh Start machine with DaDesktop (DD). However, a handful of applications may not behave as expected after cloning, and will need a few extra steps to get them working normally again.

System Details

 

Fresh Start Fix Notes

  1. Please note this is a generic guide to fixing this application when using Fresh Start. The steps may differ depending on your exact configuration.

  2. Summary of the Fresh Start fix: The original hostname of the Fresh Start machine is used, but cloning changes the machine name, so the old hostname no longer makes sense. Instead, we point to 127.0.0.1 (localhost) rather than the original hostname. Additionally, extra database Listeners may have been added, which can confuse the configuration – it's best to remove them as shown below.

     

Fix process

1. The screenshot below shows the network connection failure when using the Oracle SQL Developer application.

Failure Test

2. Open the Oracle Net Manager application.

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

Oracle Net Manager

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

Connection test fails

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

5. No databases are shown as configured to work with LISTENER1. Check for any Listeners that don't have database services configured for them. If you find any, delete that Listener.

Listeners

6. Therefore, delete LISTENER1 and confirm. Note: This is an example from our setup, and may not always occur, but it's shown here to illustrate.

Delete Listener

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

Default Listener

8. So, delete the DEFAULT SERVER LISTENER.

Delete Listener

9. Now only LISTENER remains. Here we see the existing VM hostname, which needs to be changed because it will differ after cloning.

Fix Network

10. Change the host from the one shown (in our case, 'alexi.uuae.vm') to 127.0.0.1, leaving 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, then close the application.

13. Open a Command Prompt; we'll restart the listener service.

Type 'lsnrctl status', then 'lsnrctl stop', and then '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. Connection Test: Click the small button shown in the image below to run the Connection Test.

Click to test

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

Connection test succesful

Save the network connection if required.

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

Oracle app

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

21. Continue configuring the Fresh Start machine as needed, then clone the Fresh Start machines to the Trainer's and Participants' machines.

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

If you still experience issues, please contact DaDesktop Support via the chat app, and we'll be happy to help.