1- Put your Database into ARCHIVELOG Mode
2- Use DBMS_STATS for statistic collection
3- Using Recovery Manager(RMAN) for Backup and Recovery needs
4- Resumable Statements and Space Allocation
5- Maintenance of Global Partitioned Indexes
6- Default Tablespaces
7- PL/SQL Bulk Operations
8- Locking Issues
9- Oracle System Event Triggers
10- Autonomous Transactions
11- Defining Application Services for Oracle Database 10g
12- Cost Based Optimizer Best Practices and Advised Strategy
Thanks to Tom and of course Oracle, In 2012 Tom kyte could visit Madrid and shared a little of his knowledge, Oracle call this day
“A day with Tom Kyte” start at 9:00 to 17:30 in that time we could
ask to tom a lot of question.
Have you find yourself you need import a export from other server and this dump not fit in any filesytem.
Solution is very simple,from Oracle 10g now you can use network to import data from a remote database
In Oracle 10g, the Data Pump version of import can eliminate the dump file entirely by importing directly from another database instance.
Many times like all Oracle DBAs have face with this problem sometimes is easy avoid sometimes you discover for example that table have LOBS and this LOBs dont use the UNDO tablespace and datbase UNDO_RETENTION parameter and have his own paramter and stores undo on data tablespace.
This problem can cause a lot of waste time because it is more likely to occur when you are running long queries so the return to process them again will be a big waste of time.
I can resume this post and say DBAs have three basic tasks: backup, BACKUP, BACKUP!!. Although data integrity is clearly the first job, if the data isn’t good doesnt matter if the database is available or database perfomance is fast.
So first and principal task is Establish and maintain backup and recovery policies and procedures