Our server goes for frequent shutdowns due to power outages thereby rendering the DB corrupt having consistency errors. Is there any way out of this as a fix needs to be done quite regularly. Is there any measures that can be taken once the server comes up after shutdown to prevent the DB from having consistency errors.
As an immediate mitigation - can you put the server on a UPS system? That should help if the outages are short-lived, and in any case allow the system time to shutdown gracefully (thereby avoiding corruption). That doesn't solve the current issue of corruption though - just prevent future power issues causing more. As @sp-lock said, you need to solve the real problem, not just the symptom.
Do you have UPS software installed on your servers so that your servers get shut down cleanly after a fixed number of minutes (within the 20)? If not, check with your UPS vendor for software included with the hardware. Install the software and configure it with thresholds, you can probably fire off your custom scripts when UPS shuts down your server to make it as clean as possible. If you have a appserver and sqlserver, you could make the appserver go down first so that there are no connections to the sqlserver and then shutdown the sqlserver.
I'm going to pile on with everyone else here. The key point is that SQL Server stores information to disk. If that information is only partially written and the server goes away, you get a corrupt database. The answer is that you need to ensure that the UPS keeps the server from failing when the power goes away and then issues a shutdown command to the server so that it can gracefully finish all the writes on the system prior to turning off. The UPS should come with software for this. If not, you'll have to get it installed. There is no other way around it.