Reserved schema names

In general, for certain objects, schema names that begin with the prefix SYS are reserved. The schema name for these objects cannot begin with SYS except for certain exceptions.

The schema name for the objects listed in the following table must follow the restrictions listed in the table.

Recommendations: Start of change
  • Do not to use SESSION as a schema name.
  • Do not use SYSPUBLIC as a schema name for a table or view.
End of change
Table 1. Objects with schema name restrictions and exceptions.
Object Schema name restriction Schema name exceptions
Distinct types Cannot begin with SYS The schema name can be:
  • SYSADM
  • SYSTOOLS1
User-defined functions Cannot begin with SYS The schema name can be:
  • SYSADM
  • SYSTOOLS1
  • SYSFUN2
Stored procedures Cannot begin with SYS The schema name can be:
  • SYSADM
  • SYSFUN2
  • SYSIBM
  • Start of changeSYSIBMADMEnd of change
  • SYSPROC
  • SYSTOOLS1
Sequences Cannot begin with SYS The schema name can be:
  • SYSADM
Triggers Cannot begin with SYS The schema name can be:
  • SYSADM
  • SYSTOOLS1
Column masks Cannot begin with SYS The schema name can be:
  • SYSADM
Row permissions Cannot begin with SYS The schema name can be:
  • SYSADM
Notes:
  1. If the user who executes the CREATE statement has the SYSADM or SYSCTRL privilege.
  2. For external user-defined scalar functions or external user-defined table functions if the user who executes the CREATE statement has the SYSADM or SYSCTRL privilege.