Dba tips and_tricks
Download as PPTX, PDF0 likes601 views
This document provides tips and best practices for Oracle DBAs to become successful professionals. It recommends obtaining certifications like OCP and OCA. It also recommends maintaining blogs and participating in user groups. The document outlines rules for DBAs, including protecting data, testing changes before implementing, and frequent backups. It discusses evolving DBA roles and provides advice on automation, change management, incident response, performance tuning, and continuous learning.
Dba tips and_tricks
- 1. Oracle DBASome tips and Best PracticesTo become a successful professional
- 2. 8/9i/10g/11g OCP, RAC OCE, AS OCA, E-Business OCP , SQL /PLSQL OCA , Oracle 7 OCMOracle 7 and Oracle 11gR2 Beta TesterITIL CertifiedBlog: www.oraclenz.comEmail: [email protected]: fcomunozFrancisco Munoz AlvarezDBIS - Copyright 20102Oracle ACE DirectorNZOUG PresidentLAOUC PresidentCLOUG PresidentDBIS – CEO & Technical Director
- 3. DBIS - Copyright 20103Born hereGrow up hereGot Married HereMature hereNow Living here
- 4. Copyright 20104Agenda1Change yourself2The 3 Rules3Evolution of the DBA Role4Some tips and best practices5The 3 DBAs
- 5. First: Learn to Change YourselfIf do you want to become a successful professional, first you need to educate yourself to be successful!Your future success depends only in your attitude today! You control your life, nobody else!DBIS - Copyright 20105Comm.SUCCESSSuccessInnovateAttitudeResearch
- 6. 6
- 7. My 3 Rules1Protect Your Data2Always Try Before3Backup, Backup & Backup
- 8. “The most important rule with respect to data is to never put yourself into an unrecoverable situation.” Protect your data!The importance of this guideline cannot be stressed enough, but it does not mean that you can never use time saving or performance enhancing options.8
- 9. Always Try it Before!When it comes to theory, “NEVER” believe anything you hear or read until you have tried it yourself. 9
- 10. 10
- 11. Backup, Backup & BackupWhy? Because bad stuff happens…11
- 12. Servers (DB/AS), NET, Security ...Oracle DBsDBABackupsDW24 x 7Other DBAsAnd DevelopersRACDR & Standby DBsSystem & Net. Admin.MySQLSQL ServerDB2,etcHRFinanceYou named12
- 13. Some tips and Best PracticesCopyright 201013
- 14. Copyright 200914Backup, Backup & BackupWhyNormalApproachRemember each environment is different
- 15. Always Backup before a change
- 16. Always Backup after a change
- 17. If possible Encrypt Backups for your security
- 18. Nothing bad will happen … is a easy change…
- 19. I test it before and nothing happens …
- 20. Reduce Risks
- 21. Allow an easy Rollback if necessary
- 22. Could save your jobCopyright 200915Have a Good Backup StrategyNormalApproachBackup your Archivelogs to tape several times a day
- 23. Generate a daily Datapump for logical recover, just in case…WhyI have a full backup daily, that’s enough!
- 24. Reduce Risks
- 25. Will have your users happy when ask you to recover a table from last week…
- 26. Always be proactive, use the “What if…” MethodologyA massive data outage for Sidekick handheld users has become a massive PR headache for Microsoft and carrier T-Mobile. A massive data outage in Microsoft's Danger unit left many T-Mobile Sidekick users without access to their calendar, address book, and other key data. However, things got even worse as Microsoft said in a statement that data not recovered thus far may be permanently lost. Microsoft and T-Mobile have not said how many of the roughly 800,000 Sidekick customers have lost data. T-Mobile USA has, at least temporarily, stopped selling all models of the device as the company continues to investigate the recent problems.
- 27. Copyright 200917Separate EnvironmentsWhyNormalApproachOne server for each environment (Think about OVM)
- 28. Developers only need to have full access to Dev
- 29. Transform Test and Prod in High Secure areas
- 30. Yes, we have a Dev/Test/Prod. But they are in the same server…
- 31. Everyone know what each one is doing…
- 32. We are saving money to the company…
- 33. Reduce Risks
- 34. Allow you to be really responsible for the Environments
- 35. Protect System Performance and Availability
- 36. Protect Business ContinuityCopyright 200918Have a Change RegisterWhyNormalApproachCreate your own promotion procedures
- 37. Always create a Change Request
- 38. Always try to involve all affected users
- 39. Always only promote changes after obtain all approvals(Share responsibility) It’s an small change, no one will notice…
- 40. It will not affect no one…
- 41. It’s better to say sorry than ask for authorization…
- 42. Will allow you to document and review the process.
- 43. Will allow others to review your process.
- 44. Will contain all approvals and tests (for your safety and mental health)
- 45. In case a system is affected, will be easy to detect was changed!What’s an Incident?“An incident is always when something affects the business continuity or the business revenue”Copyright 201019
- 46. Copyright 200920Incident is always a priorityInvestigate and solve it as soon as possible
- 47. After solved, create an Incident report, it will help you to:Detect the root cause of the problemDocument how it can be prevented to happen againDocument all steps to solve the problemNormalApproachWhyI will do it early in the morning when back to the office…
- 48. It can wait a few minutes more, I’m on break now…
- 49. It’s lunch time, will take a look when back…
- 50. Reduce Company Revenue losses
- 51. Will save your job
- 52. Shows that you really care about your EmployerCopyright 200921Avoid Dead LocksNormalApproachWhyCreate Index on Foreign Keys (Script on www.oraclenz.com)
- 53. Check for Bitmap Indexes on OLTP Environment
- 54. Dead Locks are Developers fault…
- 56. Will help you to have a good relationship with DevelopersCopyright 200922Automatic ProcessesNormalApproachWhyIf a process or work can be made automatic, do it!
- 57. If it can’t be made automatic, try to delegate it!
- 58. I can do it by myself…
- 59. I love to be involved on everything…
- 60. I love to create users, extend tablespaces, change passwords…
- 61. I love to run a checklist every day…
- 62. You have more important stuff to do!Copyright 200923Oracle HomesWhyNormalApproachReduce Risks
- 63. Allow an easy Rollback if necessary
- 64. All versions Catalog scripts will be preserved
- 66. Patches are applied to the same Oracle Home
- 67. Use a different Oracle Home for each upgrade or Patching, example:
- 69. For the next patch, use a new Oracle Home
- 71. /u01/app/oracle/product/10.2/asm_02Copyright 200924DB Init ParametersWhyNormalApproachBe proactive, set all parameters your environment will need now, specially the ones you can’t not modify later using ALTER SYSTEM.
- 72. Remember to set _trace_files_public = TRUE, soon or later you will need to give access to some trace files to the developers.Will change them only when required!Will avoid inconvenient restarts of the DB.
- 73. Will save you time and headaches
- 74. Be proactive always will improve your DB performance and availabilityCopyright 200925.LOG ExtensionWhyNormalApproachI always use .log for my redolog files… is the standard!Someone (including you) could delete it by mistake.
- 75. Use a different extension for redo logs like .RDOCopyright 200926Metadata RepositoryWhyNormalApproachI have all I need on my current DB.I use my Dev/Test as a DDL repository.Allow you to detect changes easily.
- 76. Allow you to create your own Version Control.
- 77. You never know when you will need it
- 78. Create your own metadata repository.
- 79. Use datapump for this :$ expdp user/password content=metadata_only full=y directory=datapumpdumpfile=metadata_24112010.dmp$ impdp user/password directory=datapumpdumpfile= metadata_24112010.dmp sqlfile=metadata_24112010.sql
- 80. Copyright 200927Non OFA LayoutNormalApproachWhyLet’s Oracle manage all using OFA, that way all will be standard on all environments.Easy to manage and keep organized
- 81. Allow you to use different mount points
- 82. Reduce Risks
- 84. /u01/udump – for user files
- 85. /proddata/SID/*
- 87. /prodlogs/SID/*Copyright 200928Study, Study & StudyWhyNormalApproachI know everything I need…Will keep you up to date
- 88. You never know when you will need to use it
- 89. Will help with your professional development
- 90. Read Manuals
- 91. /Read the official documentation at http://tahiti.oracle.com
- 92. Read and practice OBE at OTN website
- 93. Help others at OTN Forums (Fantastic way to learn)
- 94. Participate at OUG Activities (If possible try to speak)Copyright 200929Listen! Ask Question! Be involvedWhyNormalApproachDon't just sit back waiting for the create table requests.
- 95. Learn more about your systems and usersI just will do something when asked to do…If is working I don’t need to care…Know what to do before necessary
- 96. Allow you to know who to contact in case of…
- 97. Show how engaged you are with the company30Copyright 2009
- 98. 3 Kind of DBA’s1The Firefighter2The Proactive3The Balanced
- 99. What kind of DBA you are?Copyright 201032
- 100. Francisco Munoz AlvarezAucklandNew [email protected] 2010Questions? Comments?