DaDesktop

Oracle Server issues/fixes

Most applications run without a hitch on the Fresh Start machine when used with DaDesktop (DD). But a handful of applications might not behave as expected because of the cloning process, and require a few extra steps to get them running smoothly.

System Details

 

Fresh Start Fix Notes

  1. Please note this is a generic guide to sorting out this application when using Fresh Start. The steps could vary depending on your specific setup.

  2. Summary – Apply the fix on Fresh Start as described below. The Fresh Start machine's hostname is used, but once cloned, the machine name changes, so that original hostname becomes irrelevant. Instead, we'll use 127.0.0.1 (localhost) rather than the original hostname. Additionally, there are extra database Listeners added, which can complicate the configuration, so they are best removed as shown below.

     

Fix process

1. Here's what a database connection network failure looks like when using Oracle SQL Developer.

Failure Test

2. Open Oracle Net Manager.

The XE service details appear, showing the original host info (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. Oracle Net Manager, Listening Locations, Listener
The host details show the original hostname 'alexei-uue.vm' – this will be changed.

5. No databases are shown configured to work with LISTENER1. Check for any Listeners that might not have database services set up for them. If any exist, delete that Listener.

Listeners

6. So, delete LISTENER1 and confirm. Note: this is an example from our setup; it may not always happen, but we're showing it here as an illustration.

Delete Listener

7. DEFAULT SERVER LISTENER – check each Listener one by one; in this case, no listening location is available.

Default Listener

8. So, delete DEFAULT SERVER LISTENER.

Delete Listener

9. On LISTENER (the only one left now), you'll see the existing VM hostname that needs to be updated because it will change during cloning.

Fix Network

10. Change the host from what's shown (in our case, 'alexei-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 Command Prompt; we'll restart the listener service.

Type ‘lsnrctl status’, then ‘lsnrctl stop’, then ‘lsnrctl start’.

Cmd prompt

Open Oracle Net Manager again.

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

15. Change host to 127.0.0.1 

16. Save the network connection.

17. Connection Test: click the small button 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 necessary.

19. Go back to the main Oracle SQL Developer app. Run the Connection Test again.

Oracle app

20. Assuming the connection is successful, go to Connections on the left-hand side, expand Oracle Connections to confirm that the database tables appear as expected.

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

The Oracle Database server should now run correctly on the trainers' and participants' machines.

If you still run into issues, please get in touch with DaDesktop Support via the chat app, and we'll be happy to help.