When it is time to go on a vacation break or there is inclement weather, someone (staff and client) always report a database log in failed error which is always expected as everyone is trying to retrieve information that they will need during their time off from work or school since time restrictions can be placed on the resources for maintenance.
Database Log In Failed
TNS is unable to connect to destination. Invalid TNS address supplied or destination is not listening. This error can also occur because of underlying network transport problems.
Verify that the TNS name in the connectstring entry of the DAD for this URL is valid and the database listener is running.
ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist SVR4 Error: 2: No such file or directory Error-Code:1034 Error TimeStamp:Sat, 17 Jan 2015 07:45:02 GMT
Why It Happens
This is usually a sign that the database is down and needs to be restarted. Since it is near vacation break or closure due to inclement weather (as I mentioned earlier), the database geeks are most likely taking the opportunity to do maintenance without giving anyone sufficient forewarning. At times, notifications are sent via email at the last minute when people are ignoring emails and is planning what fun they will have over the break or lost access to email.
It is not my duty to restart the database server but it is my duty to make sure that the free Internet browsers that our staff and clients are accessing the database with is Internet Explorer (if on a Windows PC) and at least version 9. For the staff, this is an easy fix as I can make changes to their devices. I cannot update their home devices but since the release of Windows 10, I have not gotten a call regarding the issue.