Let’s check all that on a 12c non-cdb database.
But both are not exhaustive.Īnother exclusion list is the one used by logical standby: system.logstdby$skip which may be used as well to crosscheck (only records with ‘action=0’ are relevant for schema exclusion). The old exp has also its list stored in sys.exu8usr. Not exported by DataPumpĭataPump maintains its own list of users for which the tables are not exported, and you can query sys.ku_noexp_tab for that. Some Oracle provided users are missing, but the nice thing is that there is a description for the schemas that are listed. Sysaux occupantsĪnother idea that I took from Martin Bach is to crosscheck check with v$sysaux_occupants. Even if it includes all the Oracle maintained users, it has also some well known users which are not provided by database creation at all. The table sys.default_pwd$ stores the default password hash value so that we can check which users can log with trivial password. (except if you create C# common users in a cdb). And what is nice is that even when in a non-cdb the column is at ‘YES’ for Oracle maintained users and at ‘NO’ for created users. This is for CDB: the oracle dictionary is stored in the root container, and each PDB have links to it. Oracle 12c has another column to distinguish the user commonality. So it’s the right place to check when you are in 12c. It is YES for the users created by oracle scripts (create database, calalog.sql, catproc.sql). Oracle 12c has introduced the ORACLE_MAINTAINED in the DBA_USERS dictionary view. when you import or apply a password policy, etc.
You know SYS and SYSTEM, but there are many others – especially when you have installed all options.Īnd it is important to know them all, e. Do you want to know which users come with the Oracle Database and which are the ones you have created? This is that not easy, especially prior to Oracle 12c.
0 kommentar(er)
