Best Practices for Creating an Oracle Database

Best Practice	Reasoning
Make the SYSTEM tablespace locally managed	Doing this enforces that all tablespaces created in this database are locally managed
Use the REUSE clause with caution. Normally, you should use it only when you’re re-creating a database	The REUSE clause instructs Oracle to overwrite existing files, regardless of whether they’re in use. This is dangerous
Create a default temporary tablespace with TEMP somewhere in the name	Every user should be assigned a temporary tablespace of type TEMP, including the SYS user. If you don’t specify a default temporary tablespace, the SYSTEM tablespace is used. You never want a user to be assigned a temporary tablespace of SYSTEM. If your database doesn’t have a default temporary tablespace, use the ALTER DATABASE DEFAULT TEMPORARY TABLESPACE statement to assign one
Create a default permanent tablespace named USERS	This ensures that users are assigned a default permanent tablespace other than SYSTEM. If your database doesn’t have a default permanent tablespace, use the ALTER DATABASE DEFAULT TABLESPACE statement to assign one
Use the USER SYS and USER SYSTEM clauses to specify nondefault passwords	Doing this creates the database with nondefault passwords for database accounts that are usually the first targets for hackers
Create at least three redo log groups with two members each	At least three redo log groups provides time for the archive process to write out archive redo logs between switches. Two members mirror the online redo log members, providing some fault tolerance
Name the redo logs something like redoNA.rdo	This deviates slightly from the OFA standard, but it's better to avoid to name it with the extension of .log because you can accidentally delete it