Oracle Server issues/fixes

Most applications function perfectly when prepared in the Fresh Start machine using DaDesktop (DD). However, a few applications, owing to the cloning process, do not work as expected and require a few additional steps to operate normally.

System Details

• Oracle Database 19c (other versions are likely to exhibit the same behaviour)

• Installed using Windows 10 template

 

Fresh Start Fix Notes

1. Kindly note that this is a generic guide for fixing this application when used within Fresh Start. The steps may differ based on your exact set-up configuration.

2. Summary – The fix on Fresh Start is as under. The hostname of the Fresh Start machine is used; however, when it is cloned, a different machine name will be utilised, so the original hostname becomes irrelevant. Instead, we use 127.0.0.1 (localhost) rather than the original hostname. Furthermore, extra database Listeners are added, which confuses the configuration; these are best removed, as shown below.
   
    

Fix process

1. The image below depicts the database connection network failure when using the Oracle SQL Developer application.

2. Launch the Oracle Net Manager application.

The xe service details are shown, with the original host information (in this case, alexei-uuae.vm).

3. The connection test fails (after entering user ID=system and password).

4. Oracle Net Manager, Listening Locations, Listener
Host details showing the original hostname 'alexei-uue.vm' which will be changed.

5. No databases are shown as configured to work with LISTENER1. Check for any Listeners that do not have database services configured for them. If found, delete that Listener.

6. Hence, delete LISTENER1 and confirm. Note: This is an example of what occurred during our set-up; it may not always happen, but is shown here for illustration.

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

8. Hence, DELETE DEFAULT SERVER LISTENER.

9. On LISTENER (only this is left now), we see the existing VM hostname, which needs to be changed as it will change during cloning.

10. Change the host from the one shown (in our case, 'alexi.uuae.vm') to 127.0.0.1, keeping the port same as before.

Next, configure the existing database.

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

12. Save the network configuration and close the application.

13. Start the Command Prompt; we will restart the listener service.

Type ‘lsnrctl status’, then type 'lsnrctl stop'.

Then type 'lsnrctl start'.

Launch Oracle Net Manager once more.

14. Remove 'alexei-vm' from 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 in the image below to invoke the Connection Test.

18. Change the login. Change the username to ‘system’ and enter the appropriate password.

Save the network connection if necessary.

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

20. Assuming a successful connection, go to Connections in the left-hand panel, expand Oracle Connections, and confirm that database tables are displayed as expected.

21. Continue with the FreshStart machine configuration as required, and clone the FreshStart machines to the Trainer’s and Participants’ machines.

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

Please contact DaDesktop Support via the chat app if you still face any issues; we shall be happy to assist.