Oops !
Hello Nagesh.
For your information, any information displayed on SEPM Console (excepted the graphic information) are the information present on your Database.
If there is an issue like information not correctly updated on your SEPM interface then it's coming from your Database or permissions issue.
As you mentioned that it was working perfectly 2 days ago, I highly suspect that something happened 2 days ago.
So ...
Did you get any power interruption ? Even a short network outage ?
You probably have an Embedded Database as you mentioned you restarted the SEPM services
Could you please try the ODBC connection test that Chetan already mentioned on his feedback ? => http://www.symantec.com/docs/TECH103832
Let us know the results of the ODBC test to ensure the connection to your Database is working correctly.
Next step:
Ensure before to not run your SEPM Console and to stop the SEPM Services (Symantec Endpoint Protection Manager and Symantec Embedded Database).
Then the funny actions to do because your scm-server-0.log clearly mentioned what's going on.
All your managed SEP clients are sending to your SEPM some threads (ie: .dat file; tmp file, .err file when stuck for too long time, etc...). These threads are sent by following the Heartbeat Interval set on the Groups where your SEP clients are (communication settings aspect).
Your scm-server-0.log is telling you that AgentLogCollector is encountering an issue and even the BatchLogHandlerProcess as well (more known as the process bcp.exe) that regularly loads and unloads on your SEPM server in order to handle the threads received from your managed SEP clients.
As the issue started to occur 2 days ago, there is a very high chance that you have plenty of threads stuck on your SEPM server at this time.
To verify that point, you can go to the Symantec Endpoint Protection Manager installation path and go to the following directories:
%\Symantec Endpoint Protection Manager\data\inbox\agentinfo\
And check all the subfolders inside the directory below as well.
%\Symantec Endpoint Protection Manager\data\inbox\logs\
(ie: behavior, traffic, lansensor, security, etc ...).
Delete all the .dat, .tmp, .err files stuck over there. Do not delete any folders for sure 
Don't worry about their deletion, your managed SEP clients will still send their threads continuously by following their Heartbeat Interval.
So if you see new recent threads coming up, do not try to delete them.
Restart your SEPM services.
Restart IIS as well.
Try to connect back to your SEPM Console and see if it's still blank like before or not.
Further step if it's still not working:
Try to search with the help of Windows Search the log file called "agentlogcollector" and attach it there then we will be able to see what can be done as it will probably reveal important information related to your issue.
As an example, it has been noticed in the past that sometimes after some Windows updates some permissions on some SEPM folders has been changed (known with 11.0 MR4 MP2 from personnal experience with some customers).
So you could check at the same occasion the folder "data" => %\Symantec Endpoint Protection Manager\data
Check on the security tabs of the "data" folder if "Everyone" is on Full Access and these permissions are correctly herited for all files and subfolders inside of the data folder. If it's not set like that, fix it.
Keep us updated 
Kind Regards,
A. Wesker