You execute the following set of commands to create a database user and to grant the system privileges in your production environment. SQL> CREATE USER user01 IDENTIFIED BY oracle DEFAULT TABLESPACE…

A full tablespace produces ORA-01653 (unable to extend table) rather than ORA-01950, which is strictly a quota privilege error unrelated to available free space.

Ownership or access to the SYSTEM tablespace has no bearing on a user's ability to create objects in a separately assigned default tablespace like TBS1.

In Oracle, the CREATE TABLE system privilege only authorizes the user to issue the DDL statement; it does not grant any physical storage allocation in a tablespace. A separate quota must be assigned via ALTER USER user01 QUOTA UNLIMITED ON tbs1 or a specific byte limit, and because no quota was granted during user creation, Oracle raises ORA-01950 when the user attempts to write an extent to TBS1. This is a common provisioning oversight that is distinct from system privilege management.

The CREATE TABLE system privilege was explicitly granted to user01, so the privilege to issue the statement exists; the missing element is storage quota, which is a separate configuration from system privileges.

CREATE TABLE covers table creation in any tablespace where the user holds quota; the problem is not the scope of the privilege but the complete absence of a quota grant on TBS1.