I did not find this article very helpful. It was far too brief to cover this topic even on a high level. There was no real mention on what types of problems are best solved by choosing one schema type or the other.
There was no discussion of Oracle's star transformations (it must be turned on in init.ora and that older versions of Oracle don't have it thus making star schemas potentially impractical). There was no discussion on how bitmap indexes are crucial to star schemas and how they can sometimes pose limitations on the manner in which you update the tables.
There was no discussion of how in a snowflake schema smaller normalized dimension tables often stay completely pinned in Oracle's cache making de-normalizing them into a star nothing short of a waste of disk space and a maintenance hassle.
There was no example explain plans showing how a query would execute differently on the two schema types.
I also felt the inference that properly normalized schemas inevitably lead to performance problems on large databases was far too broad a statement. The degree of parallelism and other factors determine the validity of this statement on a case-by-case basis. I could also see how these comments as phrased could be taken by the reader as applying to OLTP schemas also and in that context it is probably false.
There was no discussion on a a legitimate third choice; Oracle's materialized views can essentially provide the best of both worlds and that these options should be considered prior to creating a special OLAP schema.