I have some problems  with the discussion:
When we want to show a fact or a report like "... you will see that the number of normalized object models is much higher than databases! ", I think we need some references.
about "normalized object model", I can't find this phrase in Google search or other search engines and I think normalization belongs to relational model but in Object model, when you want to map your objects into relational model, you have some other problems.
In my experience, in large or enterprise systems to get reports, complex  summary query of entities and some other things like that, you can't do every thing with hibernate  and other ORMs. In these cases you need to to use SQL.
In relational database  design, as Arash said, we have normalization process, but in ORM we have a nice concept like "lazy fetching".
In some large projects, when you have many entities, you may find some problems like lack of memories and alike, that you never think about them in SQL and JDBC.
Although I believe that using ORM can help us in all of project  and keep us away from database and its component, in many cases you need to write SQL script.