Oracle DBA Daily Checklist

Oracle DBA Daily Checklist

1. Check that all instances are up.

2. Monitor alert log entries (using tail -f)

3. Check that dbsnmp(SNMP subagent for Oracle DB) is running.

4. Check all last night backups were successful.

5. Check all database archiving are done.

6. Check tablespaces should not be used more that 95%.

7. Check all crons and Oracle Jobs are completed without any error

8. Verify resources for acceptable performance.

9. Identify bad growth of Segments.

10. Identify atleast 1 top resource consuming query

Related Links:
- Database Routine Checklist Queries
- Total Size of Database
- Find 10 largest objects



Labels:

11 comments:

  1. Anuj SharmaMay 17, 2011 at 12:28 PM

    why "(using tail -f)" in point 2

    ReplyDelete
  2. Nimish GargMay 17, 2011 at 12:33 PM

    its a suggestion only (for linux)
    tail -f continues to 'follow' the file. When some lines are added to file, they will be displayed on the terminal automatically. This is very useful for watching log files.

    ReplyDelete
  3. Anuj SharmaMay 17, 2011 at 12:55 PM

    but if you check alert log with "tail -f", wouldn't you miss the errors/warning generated last night, as you are 'following' the file for current and future entries.

    ReplyDelete
  4. Nimish GargMay 17, 2011 at 2:27 PM

    yes u have to check last night error using some text editor or vi.

    ReplyDelete
    Replies
    1. Nimish GargMarch 28, 2013 at 10:01 PM

      make some shell script to grep some special logs (usually other then checkpoint and log switch) in alert log and send a mail or sms to you

      Delete
    2. UnknownSeptember 3, 2019 at 4:18 PM

      Hi Nimish, "send a mail or sms to you" you have a script that does that? kindly share

      Delete
  5. Anuj SharmaMay 17, 2011 at 4:04 PM

    and what about logs other then alert log ( listener.log or sqlnet.log etc. )

    ReplyDelete
  6. Nimish GargMay 17, 2011 at 5:35 PM

    listener.log is usually not monitored on daily basis. we usually check it when we get one of following error(s).
    TNS-12500: TNS:listener failed to start a dedicated server process
    TNS-12540: TNS:internal limit restriction exceeded
    TNS-12560: TNSrotocol adapter error
    TNS-00510: Internal limit restriction exceeded

    Here I want to add that listener is usually the target of many database attacks, this information can reveal
    valuable clues and help you build better defenses.

    ReplyDelete
  7. Nimish GargMay 17, 2011 at 5:52 PM

    also i got one oracle document about this, plz check this out
    http://download.oracle.com/docs/cd/B19306_01/network.102/b14212/troublestng.htm#i440403

    ReplyDelete
  8. Anuj SharmaMay 17, 2011 at 6:11 PM

    "listener.log is usually not monitored on daily basis. we usually check it when we get one of following error(s).
    TNS-12500: TNS:listener failed to start a dedicated server process
    TNS-12540: TNS:internal limit restriction exceeded
    TNS-12560: TNSrotocol adapter error
    TNS-00510: Internal limit restriction exceeded"

    And where did you get these errors??

    ReplyDelete
  9. Nimish GargMay 24, 2011 at 10:04 AM

    usually at the application level

    ReplyDelete

Subscribe to: Post Comments (Atom)