You probably want to know about it as soon as possible so you can check on your database to make sure it’s okay.

If your linux server is configured to send mail, you can add a cron job to tell you when your server has been rebooted. Just add this entry to your crontab and substitute mail@example.com with your own email address:

@reboot /bin/sleep 120 && echo "*** $(hostname) has been rebooted $(date "+%h %d, %Y %H:%M %Z") ***" | /bin/mail -s "*** $(hostname) has been rebooted ***" mail@example.com

This cron job executes when the server comes back online. The cron entry above sleeps for 120 seconds before it sends an email to you. You can adjust the sleep time or remove it from the cron entry altogether:

@reboot echo "*** $(hostname) has been rebooted $(date "+%h %d, %Y %H:%M %Z") ***" | /bin/mail -s "Attention DBA team: $(hostname) has been rebooted" mail@example.com

@reboot is a non-standard crontab value that takes the place of the first 5 fields of the crontab entry (minute, hour, day of month, month, day of week).

The post Have your linux server email you when it gets rebooted appeared first on Bad DBA :(.

set lines 200
select name,
       trunc(total_mb/1024,2) as total_gb,
       trunc(free_mb/1024,2) as free_gb,
       trunc((total_mb - free_mb)/1024,2) as used_gb,
       trunc((free_mb/total_mb) * 100,2) as free_percent
  from gv$asm_diskgroup
 order by name;

The post Quick summary of ASM disk group sizes appeared first on Bad DBA :(.

Here’s a query you can run to see the segments that are in your recycle bin that are still taking up space in your tablespaces.

set pages 999
set lines 200
column owner format a20
column original_name format a30
select r.owner, 
       r.original_name, 
       r.type, 
       r.ts_name, 
       r.droptime, (t.block_size * r.space)/1024/1024 as megabytes
  from dba_recyclebin r, 
       dba_tablespaces t
 where t.tablespace_name = r.ts_name
 order by r.ts_name, 
          r.owner,
          r.original_name;

In this query, we are joining dba_recyclebin to dba_tablespaces to get the block size, since tablespaces may have custom block sizes and we’re not relying on the db_block_size initialization parameter.

Do you need all of these segments? Can they be purged to free up space? Make sure you talk to your users before you purge your recycle bin.

The post What’s in your recycle bin? appeared first on Bad DBA :(.