<!-- Title: 08:32:02  Wed Oct 27 2004 -->
<!-- Crewchief: New Day  -->
<!-- Op1: &nbsp; -->
<!-- Op2: &nbsp; -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre>database activity</pre>

<!-- Date: Wed Oct 27 10:34:17 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : WARNING 

User Defined SQL Test 
Current Value: 644 
WARNING 
Oct 27 2004 10:33:18 AM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Wed Oct 27 10:38:26 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : CLEARED 

User Defined SQL Test 
Current Value: 294 
CLEARED 
Oct 27 2004 10:38:18 AM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Wed Oct 27 12:13:32 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : WARNING 

User Defined SQL Test 
Current Value: 673 
WARNING 
Oct 27 2004 12:13:18 PM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Wed Oct 27 12:28:48 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : CLEARED 

User Defined SQL Test 
Current Value: 3 
CLEARED 
Oct 27 2004 12:28:18 PM 



</pre>
<!-- Author: oem-admin (email) -->



<!-- Date: Wed Oct 27 14:25:37 2004 -->
<pre> 
new accts hdw_manager 
 
Corrinne Mills 
Jared Yamaoka 
Sebastian Grinstein 
Jennifer Pursley 
 
</pre>
<!-- Author: nstanfield  -->


<!-- Date: Wed Oct 27 17:57:00 2004 -->
<pre>Art, 
 
Yes,  the rman should of grown with the new enhancements which 
is to back up the archives thru rman.   Follow-up rman's will 
simply backup new archives which have not already been 
backed up. 
 
In summary, the first rman should of been larger which you've 
proven is (176 GB to 182 GB)  and  consequent rman's 
will (of course current data) only reflect additional archives.  
 
Now  that I have said that, I decided to check... the rman logs 
show that an archive is backed up once,  once the archive ihas 
been backed up it will be skipped (see below skipping)  next 
time it runs,   and only backup new archives that it doesn't 
know about .  If takes one step further & deletes archives 
that are  SYSDATE-8 old. 
 
So the enhancements are still in place. 
 
Starting backup at 24-OCT-04 
current log archived 
skipping archive log file /dbs8/oradata/cdfonprd/arch/arch1_prd_313304.arc; already backed up 1 time(s) 
skipping archive log file /dbs8/oradata/cdfonprd/arch/arch1_prd_313305.arc; already backed up 1 time(s) 
skipping archive log file /dbs8/oradata/cdfonprd/arch/arch1_prd_313306.arc; already backed up 1 time(s) 
skipping archive log file /dbs8/oradata/cdfonprd/arch/arch1_prd_313307.arc; already backed up 1 time(s) 
skipping archive log file /dbs8/oradata/cdfonprd/arch/arch1_prd_313308.arc; already backed up 1 time(s) 
skipping archive log file /dbs8/oradata/cdfonprd/arch/arch1_prd_313309.arc; already backed up 1 time(s) 
skipping archive log file /dbs8/oradata/cdfonprd/arch/arch1_prd_313310.arc; already backed up 1 time(s) 
skipping archive log file /dbs8/oradata/cdfonprd/arch/arch1_prd_313311.arc; already backed up 1 time(s) 
skipping archive log file /dbs8/oradata/cdfonprd/arch/arch1_prd_313312.arc; already backed up 1 time(s) 
skipping archive log file /dbs8/oradata/cdfonprd/arch/arch1_prd_313313.arc; already backed up 1 time(s) 
skipping archive log file /dbs8/oradata/cdfonprd/arch/arch1_prd_313314.arc; already backed up 1 time(s) 
skipping archive log file /dbs8/oradata/cdfonprd/arch/arch1_prd_313315.arc; already backed up 1 time(s) 
 
... 
piece handle=/backup/rman/cdfonprd/acCDFONPRD_t540360872_s20263_p1 comment=NONE 
channel t1: backup set complete, elapsed time: 00:00:50 
Finished backup at 24-OCT-04 
 
deleted archive log 
archive log filename=/dbs8/oradata/cdfonprd/arch/arch1_prd_313304.arc recid=312633 stamp=539585681 
deleted archive log 
archive log filename=/dbs8/oradata/cdfonprd/arch/arch1_prd_313305.arc recid=312634 stamp=539587011 
deleted archive log 
archive log filename=/dbs8/oradata/cdfonprd/arch/arch1_prd_313306.arc recid=312635 stamp=539588341 
deleted archive log 
archive log filename=/dbs8/oradata/cdfonprd/arch/arch1_prd_313307.arc recid=312636 stamp=539589789 
deleted archive log 
archive log filename=/dbs8/oradata/cdfonprd/arch/arch1_prd_313308.arc recid=312637 stamp=539591277 
deleted archive log 
... 
 
 
 
----- Original Message -----  
From: "Art Kreymer" &lt;kreymer@fnal.gov&gt; 
To: &lt;cdfdb-support@fnal.gov&gt; 
Sent: Wednesday, October 27, 2004 5:46 PM 
Subject: cdfonprd rman size followup 
 
 
&gt; As mentioned earlier today, the rman area on cdfofprd has grown gradually 
&gt;  
&gt; from 140 GB uncompressed, and 52 GB after gzipping, in early February, 
&gt; to   180 GB uncompressed, and 68 GB after gzipping. 
&gt;  
&gt; That's about a 25% growth, gradually, in line with what one would expect. 
&gt;  
&gt; There was a big jump Sept 16 when the new rman scheme started, 
&gt; from 176 GB to 182 GB, but the size went back down the next day. 
&gt; ( Are we really sure the new scheme 'stuck' on cdfonprd ? ) 
&gt;  
&gt; Up to now I've been keeping a full 21 days worth of rman's on disk 
&gt; on fcdfdata012, just because we had the space. 
&gt;  
&gt; I have now cut this back to 15 days, to avoid filling the disks there. 
&gt; I still keep 21 days of arc files. 
&gt; </pre>
<!-- Author: nstanfield  -->

<!-- Date: Wed Oct 27 22:09:38 2004 -->
<pre>
Target Name : cdfofpr1.fnal.gov 
Target Type : Database 
Node Name : fcdfora4.fnal.gov 
Status : WARNING 

Maximum Extents 
Segment CDFOPR.FILE_1_CREATE_TIME in tablespace USERINDEX_01 can only allocate 2 additional extents. Segment CDFOPR.FILE_1_FS_FK_I in tablespace USERINDEX_01 can only allocate 2 additional extents. Segment CDFOPR.FILE_DS_FK_I in tablespace USERINDEX_01 can only allocate 2 additional extents. Segment CMIRCEA.FILE_1_FS_FK_I in tablespace USERINDEX_01 can only allocate 2 additional extents. 
WARNING 
Oct 27 2004 10:09:09 PM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Thu Oct 28 00:03:33 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : CLEARED 

Alert 
Event test "Alert" is cleared 
CLEARED 
Oct 28 2004 12:03:16 AM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Thu Oct 28 00:05:40 2004 -->
<pre>
Target Name : cdfofpr1.fnal.gov 
Target Type : Database 
Node Name : fcdfora4.fnal.gov 
Status : CLEARED 

Alert 
Event test "Alert" is cleared 
CLEARED 
Oct 28 2004 12:03:48 AM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Thu Oct 28 12:13:30 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : WARNING 

User Defined SQL Test 
Current Value: 601 
WARNING 
Oct 28 2004 12:13:19 PM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Thu Oct 28 12:19:03 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : CLEARED 

User Defined SQL Test 
Current Value: 456 
CLEARED 
Oct 28 2004 12:18:18 PM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Thu Oct 28 15:48:32 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : WARNING 

User Defined SQL Test 
Current Value: 611 
WARNING 
Oct 28 2004 03:48:18 PM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Thu Oct 28 15:53:45 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : CLEARED 

User Defined SQL Test 
Current Value: 80.00000000000000000000000000000000000001 
CLEARED 
Oct 28 2004 03:53:18 PM 



</pre>
<!-- Author: oem-admin (email) -->



<!-- Date: Thu Oct 28 16:14:59 2004 -->
<pre>Deleted the entry for DB_FRONTIER account from snipe exempt list.  
</pre>
<!-- Author: akumar -->
<!-- Comment: Thu Oct 28 16;23;27 comment by...akumar -->
<pre>DB_FRONTIER account will be sniped if INACTIVE for 20 minutes 
and no e-mail will be sent since OS account for DB_FRONTIER is 
'root' </pre>

<!-- Date: Thu Oct 28 18:45:10 2004 -->
<pre>
Target Name : cdfofpr1.fnal.gov 
Target Type : Database 
Node Name : fcdfora4.fnal.gov 
Status : WARNING 

Maximum Extents 
Segment CDFOPR.FILE_1_CREATE_TIME in tablespace USERINDEX_01 can only allocate 2 additional extents. Segment CDFOPR.FILE_1_FS_FK_I in tablespace USERINDEX_01 can only allocate 2 additional extents. Segment CDFOPR.FILE_DS_FK_I in tablespace USERINDEX_01 can only allocate 2 additional extents. 
WARNING 
Oct 28 2004 06:44:09 PM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Fri Oct 29 00:04:02 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : CLEARED 

Alert 
Event test "Alert" is cleared 
CLEARED 
Oct 29 2004 12:03:19 AM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Fri Oct 29 00:04:02 2004 -->
<pre>
Target Name : cdfofpr1.fnal.gov 
Target Type : Database 
Node Name : fcdfora4.fnal.gov 
Status : CLEARED 

Alert 
Event test "Alert" is cleared 
CLEARED 
Oct 29 2004 12:03:48 AM 



</pre>
<!-- Author: oem-admin (email) -->



<!-- Date: Fri Oct 29 09:45:25 2004 -->
<pre>Ray 
 
I assume you are not satisfied with the url 
http://www-css.fnal.gov/dsg/internal/backups/database_restore_recoveries.html 
that I forwarded you for information regarding backups.. 
in order close out the discussion on Data Guard implementation?! 
 
If you don't have enough info let me know what else might help... 
 
I want to point out a few pages off this url: 
 
Readme of rman/recovery: 
http://www-css.fnal.gov/dsg/internal/backups/recovery_readme.htm 
Test  defined for disaster 
recoveryhttp://www-css.fnal.gov/dsg/internal/backups/backup_testing_schedule 
_plan.htm 
Timings http://www-css.fnal.gov/dsg/internal/backups/timings_recovery.htm 
Disaster Recovery Requ 
http://www-css.fnal.gov/dsg/internal/backups/requirements_backup.htm 
Latest test of full rcovery to another box with timings 
http://www-css.fnal.gov/dsg/internal/backups/sept21_full_recvoery_cdfondev.htm 
Rman enhancements deployed 
http://www-css.fnal.gov/dsg/internal/backups/checklist_rman_implementation.htm 
 
Let us know 
Thanks 
Nelly 
</pre>
<!-- Author: nstanfield  -->

<!-- Date: Fri Oct 29 12:08:36 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : WARNING 

User Defined SQL Test 
Current Value: 729 
WARNING 
Oct 29 2004 12:08:18 PM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Fri Oct 29 12:13:31 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : CLEARED 

User Defined SQL Test 
Current Value: 590 
CLEARED 
Oct 29 2004 12:13:18 PM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Fri Oct 29 12:18:22 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : WARNING 

User Defined SQL Test 
Current Value: 655 
WARNING 
Oct 29 2004 12:18:18 PM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Fri Oct 29 12:28:44 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : CRITICAL 

User Defined SQL Test 
Current Value: 1065.000000000000000000000000000000000001 
CRITICAL 
Oct 29 2004 12:28:18 PM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Fri Oct 29 13:03:55 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : CLEARED 

User Defined SQL Test 
Current Value: 6 
CLEARED 
Oct 29 2004 01:03:18 PM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Fri Oct 29 15:09:13 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : WARNING 

User Defined SQL Test 
Current Value: 712 
WARNING 
Oct 29 2004 03:08:18 PM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Fri Oct 29 15:13:22 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : CLEARED 

User Defined SQL Test 
Current Value: 579 
CLEARED 
Oct 29 2004 03:13:18 PM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Fri Oct 29 15:18:30 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : WARNING 

User Defined SQL Test 
Current Value: 747 
WARNING 
Oct 29 2004 03:18:18 PM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Fri Oct 29 15:23:45 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : CRITICAL 

User Defined SQL Test 
Current Value: 945 
CRITICAL 
Oct 29 2004 03:23:18 PM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Fri Oct 29 15:39:07 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : CLEARED 

User Defined SQL Test 
Current Value: 203 
CLEARED 
Oct 29 2004 03:38:18 PM 



</pre>
<!-- Author: oem-admin (email) -->



<!-- Date: Fri Oct 29 16:54:38 2004 -->
<pre>kirsten requested a refresh of integration.. cdftrig.. 
 
i am dropping basic replication to prepare for this refresh. 
 
i will wait till monday to work with anil to drop streams 
testing in progress for cdftrig in int..  
 
then refresh </pre>
<!-- Author: nstanfield  -->
<!-- Comment: Mon Nov  8 10;48;24 comment by...ns -->
<pre>  The changes to the trigger database schema involve
adding 7 non-optional columns to 1 table.  There are no
Oracle triggers or constraints on these columns so it is
just adding and back filling them.  The change is not
difficult but there are several applications that need
to interact with these new columns.  We are proceeding
with testing in DEV as much as we can but soon we
will be at the point where we need the columns in INT
to finish our testing.  When will your streaming test
be done?  We'd like to have our system tested in INT
and cut into PRD before Nov. 22nd.

We were planning on reporting to the cdfdb meeting
before cutting into PRD but we can do it now.  When
is the cdfdb meeting next week?
</pre>
<!-- Date: Sat Oct 30 00:05:09 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : CLEARED 

Alert 
Event test "Alert" is cleared 
CLEARED 
Oct 30 2004 12:03:19 AM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Sat Oct 30 00:05:09 2004 -->
<pre>
Target Name : cdfofpr1.fnal.gov 
Target Type : Database 
Node Name : fcdfora4.fnal.gov 
Status : CLEARED 

Alert 
Event test "Alert" is cleared 
CLEARED 
Oct 30 2004 12:03:48 AM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Sun Oct 31 00:05:13 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : CLEARED 

Alert 
Event test "Alert" is cleared 
CLEARED 
Oct 31 2004 01:03:16 AM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Sun Oct 31 00:05:13 2004 -->
<pre>
Target Name : cdfofpr1.fnal.gov 
Target Type : Database 
Node Name : fcdfora4.fnal.gov 
Status : CLEARED 

Alert 
Event test "Alert" is cleared 
CLEARED 
Oct 31 2004 01:03:48 AM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Mon Nov 1 00:03:31 2004 -->
<pre>
Target Name : cdfonprd 
Target Type : Database 
Node Name : b0dau35.fnal.gov 
Status : CLEARED 

Alert 
Event test "Alert" is cleared 
CLEARED 
Nov 01 2004 12:03:17 AM 



</pre>
<!-- Author: oem-admin (email) -->


<!-- Date: Mon Nov 1 00:04:23 2004 -->
<pre>
Target Name : cdfofpr1.fnal.gov 
Target Type : Database 
Node Name : fcdfora4.fnal.gov 
Status : CLEARED 

Alert 
Event test "Alert" is cleared 
CLEARED 
Nov 01 2004 12:03:48 AM 



</pre>
<!-- Author: oem-admin (email) -->