Steps:
1: This issue is related to JRA-16780. We are now logging error if the schema name of the database is in upper case but after logging the error message we still proceed with the creation of table(I started with blank table). And if a user sees that log in end, he/she is bound to get confuse as there are so many error messages logged due to table creation getting failed.(log attach for reference)

Expected:
1. It will be really good , if after the first error message that schema name is in upper case, we stop the whole process. Hence when user access the log, can clearly see what is the issue.