@UpenderReddyJinna The "HikariPool-1 is not available" error usually happens when all available database connections are in use and no more are available to handle incoming requests. This can occur if your maximum pool size is set too low or if connections are not being released properly. To fix this, you can increase the maximumPoolSize setting  a common starting point is 20 to 30, depending on your application's load and your database capacity. Also, ensure connectionTimeout is set to a reasonable value like 30000 milliseconds (30 seconds), which means the system will wait up to 30 seconds for a connection to become available before timing out. Check your logs for slow queries or connection leaks, and use connection pool monitoring to analyze usage patterns. If you're running Pega, ensure the database and application node count can support the increased connections.