Final answer:
The four problems with 1NF not present in 2NF are partial dependency on composite keys, data redundancy, update anomalies, and deletion anomalies. 2NF resolves these issues by ensuring full functional dependency of non-primary-key attributes on the primary key.
Step-by-step explanation:
The four kinds of problems found with First Normal Form (1NF) designs that do not exist in Second Normal Form (2NF) are: Partial dependency of non-primary-key attributes on a composite primary key. The possibility of having redundant data across multiple rows of a table. Update anomalies where changes to data need to be made in multiple places. Deletion anomalies where removing a row may inadvertently result in loss of additional data.
To elaborate, these problems stem from the definition of the normal forms themselves. 1NF requires that all table attributes are atomic and that the table has a primary key. However, 1NF doesn't address issues with non-primary-key attributes that depend only on part of the composite primary key, which is what 2NF solves by ensuring that all non-primary-key attributes are fully functionally dependent on the entire primary key.