The following table lists additional users and databases created during the installation process.
| System Database/User | Description |
|---|---|
| CRASHDUMPS | CRASHDUMPS is defined in the Data Dictionary when the Environment is created. This user is created for use by the system for logging internal errors. Adjust the space allocation accordingly and monitor its usage. CRASHDUMPS provides temporary storage of dumps generated by the Parallel Database Extensions (PDE) software. You may need to allocate more PERM space, based on the size of your configuration, to accommodate at least three dumps. |
| Sys_Calendar | Sys_Calendar is defined in the Data Dictionary when the Environment is created. This database contains tables and views related to the system calendar, including the Calendar view, which is a user-accessible tool for date arithmetic. For more information, see System Calendar View.
|
| TD_SYSFNLIB | The TD_SYSFNLIB system database is created when the Environment is created. This database contains the non-type-specific embedded services functions offered as part of the database release. See Embedded Services System Functions .
Do not create any database objects in the TD_SYSFNLIB database. The TD_SYSFNLIB database is for internal use only.
|
ALL, DEFAULT, and PUBLIC, which are used by the database system software, may appear as databases or user names but have no content, tables, views, or PERMANENT space. Users cannot log on to ALL, DEFAULT, and PUBLIC.
User DBC owns all these system databases/users and has access privileges on everything in the system. Therefore, rather than use DBC to manage the system and risk accidentally changing the system users, create an administrative user to manage the system.