<!-- Title: 08:16:10  Thu Oct 17 2002 -->
<!-- Crewchief: New Day -->
<!-- Op1: &nbsp; -->
<!-- Op2: &nbsp; -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre>database activity 
</pre>


<!-- Date: Thu Oct 17 08:18:14 2002 -->
<pre>Further investigation of the b0dau36 looks fine. 
 
There is 1 error on the cdfondev instance but it 
not associated with the new disks or the  
successful migration to 9.  We ran successful 
rman database backups early this morning. 
 
The instances (cdfondev & cdfonint) are both at 
Oracle 9.2.0.   Jack & Bill have done some initial 
testing, and we should continue with more  
comprehensive testing.  I will speak to Jeff/Sergei 
later this week to define a plan for new disk 
utilization. 
 
Investigating Error: 
 
ERROR, tran=20.90.2449, session#=1, ose=0: 
ORA-28546: connection initialization failed, probable Net8 admin error 
ORA-02068: following severe error from CDFONPRD 
ORA-03113: end-of-file on communication channel 
 
Cause:A failure occurred during initialization of a network 
connection from the Oracle server to a second process: The 
connection was completed but a disconnect occurred while trying 
to perform protocol-specific  initialization, usually due to 
use of different network protocols by opposite sides of the connection.  
</pre>
<!-- Author: nstanfield  -->


<!-- Date: Thu Oct 17 09:40:52 2002 -->
<pre>1.  Richard has completed the work on cdfrep01. 
2.  Anil has completed the runconfigurations replication to cdfofprd and cdfrep01. 
 
Solved:  dbshut was not called.  Changed the dbora 
to add touch /var/lock/subsys/dbora before calling the 
dbstart --&gt; this solved the problem. 
 
Looking at the logs:  the machine was down: 
8:45 -&gt; 8:58   I see CAF going to cdfofprd 
9:20 -&gt; 9:25   I see CAF going to cdfofprd 
 
So the only interruption would be for those jobs that 
were in the database at reboot times.  And the 
period between 9:30 and 9:35 (less then this) when 
replication was sync'd up. 
 
</pre>
<!-- Author: nstanfield  -->
<!-- Comment: Thu Oct 17 09;42;07 comment by...nstanfield  -->
<pre>Did not see any additional load on fcdfora1. </pre>


<!-- Date: Thu Oct 17 10:31:13 2002 -->
<pre>Caf failed over to cdfofprd database during the time machine  
was shutdown for maintenance. Here are results of query showing  
CAF failed over to cdfofprd. This query is run between 8:30AM  
and 9:00AM on 10/17/02 
 
SQL&gt; select * from global_name; 
 
GLOBAL_NAME 
-------------------------------------------------------------------------------- 
CDFOFPRD.FNAL.GOV 
10/17/02 08:39:41 CDF_READER                     cafuser 
fcdfcaf037.fnal.gov 
 
10/17/02 08:45:23 CDF_READER                     cafuser 
fcdfcaf034.fnal.gov 
 
10/17/02 08:46:23 CDF_READER                     cafuser 
fcdfcaf067.fnal.gov 
 
10/17/02 08:46:44 CDF_READER                     cafuser 
fcdfcaf012.fnal.gov 
 
10/17/02 08:46:51 CDF_READER                     cafuser 
fcdfcaf067.fnal.gov 
 
10/17/02 08:47:02 CDF_READER                     cafuser 
fcdfcaf012.fnal.gov 
 
10/17/02 08:47:10 CDF_READER                     cafuser 
fcdfcaf064.fnal.gov 
 
10/17/02 08:47:14 CDF_READER                     cafuser 
fcdfcaf064.fnal.gov 
10/17/02 08:47:20 FILECATALOG_READUSER           cafuser 
fcdfcaf019.fnal.gov 
 
10/17/02 08:47:23 FILECATALOG_READUSER           cafuser 
fcdfcaf019.fnal.gov 
 
10/17/02 08:47:26 FILECATALOG_READUSER           cafuser 
fcdfcaf019.fnal.gov 
 
10/17/02 08:47:29 CDF_READER                     cafuser 
fcdfcaf049.fnal.gov 
 
10/17/02 08:47:35 CDF_READER                     cafuser 
fcdfcaf023.fnal.gov 
 
10/17/02 08:47:41 CDF_READER                     cafuser 
fcdfcaf019.fnal.gov 
 
10/17/02 08:47:50 CDF_READER                     cafuser 
fcdfcaf036.fnal.gov 
 
10/17/02 08:47:53 CDF_READER                     cafuser 
fcdfcaf015.fnal.gov 
 
10/17/02 08:47:57 CDF_READER                     cafuser 
fcdfcaf052.fnal.gov 
 
10/17/02 08:48:16 CDF_READER                     cafuser 
fcdfcaf050.fnal.gov 
 
10/17/02 08:48:24 CDF_READER                     cafuser 
fcdfcaf036.fnal.gov 
 
10/17/02 08:48:28 CDF_READER                     cafuser 
fcdfcaf029.fnal.gov 
 
10/17/02 08:48:39 CDF_READER                     cafuser 
fcdfcaf054.fnal.gov 
 
10/17/02 08:49:01 CDF_READER                     cafuser 
fcdfcaf025.fnal.gov 
 
10/17/02 08:49:02 CDF_READER                     cafuser 
fcdfcaf029.fnal.gov 
 
10/17/02 08:49:10 CDF_READER                     cafuser 
fcdfcaf010.fnal.gov 
 
10/17/02 08:49:13 CDF_READER                     cafuser 
fcdfcaf059.fnal.gov 
 
10/17/02 08:49:13 FILECATALOG_READUSER           cafuser 
fcdfcaf018.fnal.gov 
10/17/02 08:49:20 FILECATALOG_READUSER           cafuser 
fcdfcaf018.fnal.gov 
 
10/17/02 08:49:31 CDF_READER                     cafuser 
fcdfcaf018.fnal.gov 
 
10/17/02 08:49:34 CDF_READER                     cafuser 
fcdfcaf035.fnal.gov 
 
10/17/02 08:49:53 CDF_READER                     cafuser 
fcdfcaf024.fnal.gov 
 
10/17/02 08:49:58 CDF_READER                     cafuser 
fcdfcaf050.fnal.gov 
 
10/17/02 08:50:12 CDF_READER                     cafuser 
fcdfcaf023.fnal.gov 
 
10/17/02 08:50:26 CDF_READER                     cafuser 
fcdfcaf067.fnal.gov 
 
10/17/02 08:50:52 CDF_READER                     cafuser 
10/17/02 08:55:32 CDF_READER                     cafuser 
fcdfcaf043.fnal.gov 
 
10/17/02 08:55:33 CDF_READER                     cafuser 
fcdfcaf043.fnal.gov 
 
10/17/02 08:55:36 CDF_READER                     cafuser 
fcdfcaf049.fnal.gov 
 
10/17/02 08:55:39 FILECATALOG_READUSER           cafuser 
fcdfcaf018.fnal.gov 
 
10/17/02 08:55:39 FILECATALOG_READUSER           cafuser 
fcdfcaf018.fnal.gov 
 
10/17/02 08:55:40 FILECATALOG_READUSER           cafuser 
fcdfcaf018.fnal.gov 
 
10/17/02 08:55:49 CDF_READER                     cafuser 
fcdfcaf018.fnal.gov 
 
10/17/02 08:55:49 CDF_READER                     cafuser 
fcdfcaf036.fnal.gov 
 
10/17/02 08:56:00 CDF_READER                     cafuser 
fcdfcaf003.fnal.gov 
 
10/17/02 08:56:03 CDF_READER                     cafuser 
fcdfcaf029.fnal.gov 
 
10/17/02 08:56:07 CDF_READER                     cafuser 
fcdfcaf052.fnal.gov 
10/17/02 08:56:07 CDF_READER                     cafuser 
fcdfcaf052.fnal.gov 
 
10/17/02 08:56:12 CDF_READER                     cafuser 
fcdfcaf050.fnal.gov 
 
 
</pre>
<!-- Author: akumar -->

<!-- Date: Thu Oct 17 10:32:51 2002 -->
<pre>
Target Name : cdfofprd.fnal.gov 
Target Type : Database 
Node Name : fcdfora1.fnal.gov 


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


<!-- Date: Thu Oct 17 10:32:51 2002 -->
<pre>
Target Name : cdfofprd.fnal.gov 
Target Type : Database 
Node Name : fcdfora1.fnal.gov 


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


<!-- Date: Thu Oct 17 10:41:27 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 


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


<!-- Date: Thu Oct 17 11:13:32 2002 -->
<pre>
Target Name : cdfofprd.fnal.gov 
Target Type : Database 
Node Name : fcdfora1.fnal.gov 

Maximum Extents 
Segment CDFTRIG_PRD_REP.DATASETS_TRIGGER_PATHS in tablespace CDFTRIG_PRD_REP_DATA can only allocate 9 additional extents. Segment CDFPQCD.CDF2_FILE_LIVETIMES in tablespace USERDATA_01 can only allocate 9 additional extents. Segment CDFPQCD.CDF2_RUNSECTION_RANGES in tablespace USERDATA_01 can only allocate 3 additional extents. Segment CDFPBOT.CDF2_FILESETS in tablespace USERDATA_01 can only allocate 4 additional extents. Segment CDFPBOT.CDF2_FILES in tablespace USERDATA_01 can only allocate 3 additional extents. Segment CDFPBOT.CDF2_FILE_LIVETIMES in tablespace USERDATA_01 can only allocate 9 additional extents. Segment CDFPBOT.CDF2_RUNSECTION_RANGES in ... 
CRITICAL 
Oct 17 2002 11:10:29 AM 


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


<!-- Date: Fri Oct 18 10:32:36 2002 -->
<pre>
Target Name : cdfofprd.fnal.gov 
Target Type : Database 
Node Name : fcdfora1.fnal.gov 


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


<!-- Date: Fri Oct 18 10:32:36 2002 -->
<pre>
Target Name : cdfofprd.fnal.gov 
Target Type : Database 
Node Name : fcdfora1.fnal.gov 


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


<!-- Date: Fri Oct 18 10:34:30 2002 -->
<pre>
Target Name : cdfofprd.fnal.gov 
Target Type : Database 
Node Name : fcdfora1.fnal.gov 


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


<!-- Date: Fri Oct 18 10:34:30 2002 -->
<pre>
Target Name : cdfofprd.fnal.gov 
Target Type : Database 
Node Name : fcdfora1.fnal.gov 


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



<!-- Date: Fri Oct 18 11:23:12 2002 -->
<pre>CALIBRATION/PRECUT/CALORIMETER 
 
Added table OFFSCL to online production.  
Needs to be added to replication. 
 
</pre>
<!-- Author: jcranshaw -->

<!-- Date: Fri Oct 18 12:25:44 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 


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


<!-- Date: Fri Oct 18 12:29:53 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 


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


<!-- Date: Fri Oct 18 12:30:12 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 


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



<!-- Date: Fri Oct 18 16:08:10 2002 -->
<pre>I talked to Donatella she said this was cdfonprd. 
I have gone ahead and allocating an additional 100 extents 
to this FK. 
 
ALTER INDEX "CDFTRIG_PRD"."GDS_PTS_FK_I" 
    STORAGE ( MAXEXTENTS 335 ); 
 
Application owner should define this in the cvs area 
and define whether it's enough or not. 
 
You should send future db concerns to cdfdb-support@fnal.gov 
and if it affects production please fill out a helpdesk ticket. 
 
-Nelly 
 
----- Original Message ----- 
From: "Donatella Torretta" &lt;torretta@fnal.gov&gt; 
To: "William Badgett, Fermilab 1(630)840-6674" &lt;badgett@fnal.gov&gt;; "Kirsten Tollefson" &lt;kirsten@b0urpc03.fnal.gov&gt;; "Nelly 
Stanfield" &lt;nelly@fnal.gov&gt; 
Cc: &lt;torretta@fnal.gov&gt; 
Sent: Friday, October 18, 2002 3:53 PM 
Subject: max # extents (235) reached in index CDFTRIG_PRD.GDS_PTS_FK_I 
 
 
&gt; 
&gt; hi... 
&gt;  could someone please help on (/fix) this ? 
&gt;  thanks a lot 
&gt; 
&gt;                Donatella 
&gt; 
&gt; ------- Forwarded Message 
&gt; 
&gt; Return-Path: jdl@fnal.gov 
&gt; Delivery-Date: Fri Oct 18 15:37:13 2002 
&gt; Return-Path: &lt;jdl@fnal.gov&gt; 
&gt; Received: from heffalump.fnal.gov (heffalump.fnal.gov [131.225.9.20]) 
&gt; by b0dap09.fnal.gov (8.9.3/8.9.3) with ESMTP id PAA16618 
&gt; for &lt;torretta@b0dap09.fnal.gov&gt;; Fri, 18 Oct 2002 15:37:12 -0500 
&gt; Received: from fnal.gov ([131.225.235.235]) 
&gt;  by smtp.fnal.gov (PMDF V6.0-24 #37519) 
&gt;  with ESMTP id &lt;0H47005P42LZ09@smtp.fnal.gov&gt; for torretta@b0dap09.fnal.gov 
&gt;  (ORCPT torretta@fnal.gov); Fri, 18 Oct 2002 15:37:11 -0500 (CDT) 
&gt; Date: Fri, 18 Oct 2002 15:37:11 -0500 
&gt; From: "Jonathan D. Lewis" &lt;jdl@fnal.gov&gt; 
&gt; Subject: trigger table constraint violated 
&gt; Sender: jdl@heffalump.fnal.gov 
&gt; To: wittich@fnal.gov, torretta@fnal.gov, twright@fnal.gov, varganov@fnal.gov, 
&gt;         luciano@fnal.gov, jdl@fnal.gov, kirsten@fnal.gov, 
&gt;         cdf-ops-managers@fnal.gov, proudfoot@fnal.gov 
&gt; Message-id: &lt;3DB070F7.1190AFB0@fnal.gov&gt; 
&gt; MIME-version: 1.0 
&gt; X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.9-31 i686) 
&gt; Content-type: text/plain; charset=us-ascii 
&gt; Content-transfer-encoding: 7bit 
&gt; X-Accept-Language: en 
&gt; 
&gt; In trying to build PHYSICS_TEST_1_03_v7, I got the following error: 
&gt; 
&gt; 
&gt; ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 
&gt; 
&gt; &lt;&lt;-the trigger = L1_TWO_TRK10_DPHI20_v-2 was placed in RAM #7 
&gt; &lt;&lt;-the trigger = L1_TWO_TRK2.5_OPPQ_DPHI135_SUMPT6.5_v-1 was placed in RAM 
&gt; #7 
&gt; Error accessing the database:java.sql.SQLException: ORA-01632: max # 
&gt; extents (235) reached in index CDFTRIG_PRD.GDS_PTS_FK_I 
&gt; 
&gt; Error Log:  ERROR: Phyics table PHYSICS_TEST_1_03_v-7 failed L1 validation 
&gt; !!! 
&gt;  ******************************* 
&gt;  I'm sorry ! L1all Step Validation Failed !! 
&gt;  ******************************* 
&gt; 
&gt; ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 
&gt; 
&gt; What does this mean?  What is wrong with the table? 
&gt; 
&gt; The only difference between this table and v6 was adding one path the the 
&gt; TEST_JET_2 data.  If I look at the "view all" display in the gui, 
&gt; everything looks fine. 
&gt; 
&gt; Ops-managers:  I think this problem puts out tests on hold.  We need this 
&gt; change. 
&gt; 
&gt; Regards, 
&gt; 
&gt; Jonathan 
&gt; 
&gt; +-----------------------------------------------------------------+ 
&gt; | Jonathan Lewis                         Voice: (630)840-3779     | 
&gt; | Fermilab                               Fax:   (630)840-2968   | 
&gt; | MS-318                                 Pager: (630)314-3148     | 
&gt; | PO Box 500   | 
&gt; | Batavia, IL 60510                      Office: CDF Trailer 163K | 
&gt; +-----------------------------------------------------------------+ 
&gt; 
&gt; ------- End of Forwarded Message 
&gt; 
&gt; 
&gt; 
&gt; 
</pre>
<!-- Author: nstanfield  -->
<!-- Comment: Fri Oct 18 16;10;15 comment by...ns -->
<pre>also changed to cdfofprd  and will change on cdfrep01 

ALTER INDEX "CDFTRIG_PRD_REP"."GDS_PTS_FK_I" 
    STORAGE ( MAXEXTENTS 335)</pre>


<!-- Comment: Fri Oct 18 16;11;53 comment by...ns -->
<pre>already unlimited on cdfrep01 </pre>
<!-- Date: Fri Oct 18 16:11:47 2002 -->
<pre>Increased the max extents for index GDS_PTS_FK_I for CDFTRIG 
schema from 235 to 250 on table generated_downloads(physics_table_tag, physics_table_name).  
 
Same change has been implemented on cdfofprd. 
 
Application co-ordinator of CDFTRIG should let ods-dba 
know how many more extents we must allocate to this index.  
 
 
</pre>
<!-- Author: akumar -->



<!-- Date: Fri Oct 18 16:15:31 2002 -->
<pre>Ok nelly increased maxextents to 335. So ignore my elog entry  
for maxextents to 250 for one of the index of CDFTRIG schema </pre>
<!-- Author: akumar -->

<!-- Date: Sat Oct 19 10:33:05 2002 -->
<pre>
Target Name : cdfofprd.fnal.gov 
Target Type : Database 
Node Name : fcdfora1.fnal.gov 


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


<!-- Date: Sat Oct 19 10:33:05 2002 -->
<pre>
Target Name : cdfofprd.fnal.gov 
Target Type : Database 
Node Name : fcdfora1.fnal.gov 


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


<!-- Date: Sat Oct 19 21:35:32 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 


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


<!-- Date: Sun Oct 20 18:35:55 2002 -->
<pre>
Target Name : cdfofprd.fnal.gov 
Target Type : Database 
Node Name : fcdfora1.fnal.gov 


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


<!-- Date: Sun Oct 20 18:35:55 2002 -->
<pre>
Target Name : cdfofprd.fnal.gov 
Target Type : Database 
Node Name : fcdfora1.fnal.gov 


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


<!-- Date: Sun Oct 20 20:11:00 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Multiple Extents 
Segment {MCS_PRD.MLOG$_SENSORS} in tablespace MLOG_DATA is comprised of 539 extents. 
WARNING 
Oct 06 2002 01:41:13 PM 


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


<!-- Date: Sun Oct 20 20:11:00 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Multiple Extents 
Segment {MCS_PRD.MLOG$_SENSORS} in tablespace MLOG_DATA is comprised of 588 extents. Segment {MCS_PRD.MLOG$_SENSOR_HISTORIES} in tablespace MLOG_DATA is comprised of 540 extents. 
WARNING 
Oct 06 2002 09:41:22 PM 


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


<!-- Date: Sun Oct 20 20:11:00 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Multiple Extents 
Segment {MCS_PRD.MLOG$_SENSORS} in tablespace MLOG_DATA is comprised of 661 extents. Segment {MCS_PRD.MLOG$_SENSOR_HISTORIES} in tablespace MLOG_DATA is comprised of 616 extents. 
CRITICAL 
Oct 07 2002 09:41:32 AM 


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


<!-- Date: Sun Oct 20 20:11:24 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Multiple Extents 
Segment {MCS_PRD.MLOG$_SENSORS} in tablespace MLOG_DATA is comprised of 693 extents. Segment {MCS_PRD.MLOG$_SENSOR_HISTORIES} in tablespace MLOG_DATA is comprised of 654 extents. 
CRITICAL 
Oct 07 2002 03:41:38 PM 


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


<!-- Date: Sun Oct 20 20:11:24 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Tablespace Full 
Tablespace RBS is 83.26% full.  325270.0 KBytes of free space remain. 
WARNING 
Oct 07 2002 08:23:54 PM 


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


<!-- Date: Sun Oct 20 20:11:24 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Tablespace Full 
Tablespace RBS is 83.26% full.  325270.0 KBytes of free space remain. Tablespace RUNDB_DATA is 80.76% full.  1.45783e+06 KBytes of free space remain. 
WARNING 
Oct 07 2002 10:54:10 PM 


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


<!-- Date: Sun Oct 20 20:11:24 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Tablespace Full 
Tablespace RUNDB_DATA is 80.79% full.  1.45575e+06 KBytes of free space remain. 
WARNING 
Oct 07 2002 11:53:52 PM 


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


<!-- Date: Sun Oct 20 20:11:24 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Node UpDown 
Event test "Node UpDown" is cleared 
CLEARED 
Oct 17 2002 07:07:13 AM 
Database UpDown 
The database instance is down. 
CRITICAL 
Oct 08 2002 11:15:29 AM 


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


<!-- Date: Sun Oct 20 20:11:24 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Alert 
The following errors are in the ALERT file : ORA-00470: LGWR process terminated with error. 
WARNING 
Oct 08 2002 11:23:15 AM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Node UpDown 
Event test "Node UpDown" is cleared 
CLEARED 
Oct 17 2002 07:07:13 AM 
Database UpDown 
Event test "Database UpDown" is cleared 
CLEARED 
Oct 08 2002 11:25:31 AM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Alert 
The following errors are in the ALERT file : ORA-12012: error on auto execute of job 27040 ORA-00030: User session ID does not exist. ORA-06512: at "BADGETT.CDFDB", line 43 ORA-06512: at line 1. 
WARNING 
Oct 08 2002 12:09:27 PM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Maximum Extents 
Segment RUNDB_PRD.SVT_CONDITIONS_FULL in tablespace RUNDB_DATA can only allocate 1 additional extents. 
WARNING 
Oct 09 2002 04:42:26 PM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Alert 
The following errors are in the ALERT file : ORA-12012: error on auto execute of job 27040 ORA-00030: User session ID does not exist. ORA-06512: at "BADGETT.CDFDB", line 43 ORA-06512: at line 1. 
WARNING 
Oct 09 2002 05:41:37 PM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Alert 
The following errors are in the ALERT file : ORA-12012: error on auto execute of job 27040 ORA-00030: User session ID does not exist. ORA-06512: at "BADGETT.CDFDB", line 43 ORA-06512: at line 1. 
WARNING 
Oct 10 2002 02:58:07 PM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Alert 
The following errors are in the ALERT file : ORA-12012: error on auto execute of job 27040 ORA-00031: session marked for kill ORA-06512: at "BADGETT.CDFDB", line 43 ORA-06512: at line 1. 
WARNING 
Oct 11 2002 04:14:48 PM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Multiple Extents 
Segment {MCS_PRD.MLOG$_SENSORS} in tablespace MLOG_DATA is comprised of 693 extents. 
CRITICAL 
Oct 14 2002 11:44:27 AM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Alert 
The following errors are in the ALERT file : ORA-12012: error on auto execute of job 28412 ORA-00001: unique constraint (HDWDB_PRD.CU_PK) violated ORA-06512: at "HDWDB_PRD.CARDUPDATES18", line 17 ORA-04088: error during execution of trigger 'HDWDB_PRD.CARDUPDATES18' ORA-06512: at "HDWDB_PRD.HDWDB", line 605 ORA-06512: at line 1. 
WARNING 
Oct 16 2002 02:52:48 PM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Failed Jobs 
Event test "Failed Jobs" is cleared 
CLEARED 
Oct 16 2002 09:37:56 PM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Alert 
The following errors are in the ALERT file : ORA-12012: error on auto execute of job 27040 ORA-00030: User session ID does not exist. ORA-06512: at "BADGETT.CDFDB", line 43 ORA-06512: at line 1. 
WARNING 
Oct 16 2002 09:38:16 PM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Failed Jobs 
Event test "Failed Jobs" is cleared 
CLEARED 
Oct 16 2002 11:37:56 PM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Maximum Extents 
Segment RUNDB_PRD.SVT_CONDITIONS_FULL in tablespace RUNDB_DATA can only allocate 1 additional extents. Segment CDFTRIG_PRD.GDS_PTS_FK_I in tablespace CDFTRIG_IDX can only allocate 1 additional extents. 
WARNING 
Oct 17 2002 05:45:43 PM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Alert 
The following errors are in the ALERT file : ORA-12012: error on auto execute of job 28462 ORA-00001: unique constraint (HDWDB_PRD.CU_PK) violated ORA-06512: at "HDWDB_PRD.CARDUPDATES18", line 17 ORA-04088: error during execution of trigger 'HDWDB_PRD.CARDUPDATES18' ORA-06512: at "HDWDB_PRD.HDWDB", line 605 ORA-06512: at line 1. 
WARNING 
Oct 17 2002 06:39:43 PM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Maximum Extents 
Segment RUNDB_PRD.SVT_CONDITIONS_FULL in tablespace RUNDB_DATA can only allocate 0 additional extents. Segment CDFTRIG_PRD.GDS_PTS_FK_I in tablespace CDFTRIG_IDX can only allocate 1 additional extents. 
CRITICAL 
Oct 18 2002 02:45:53 AM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Alert 
The following errors are in the ALERT file : ORA-1632: max # extents 235 reached in index CDFTRIG_PRD.GDS_PTS_FK_I. 
WARNING 
Oct 18 2002 03:26:06 PM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Node UpDown 
 VNI-4044 : Cannot contact agent. Node may be down, or the network may be down or slow.  
NODE UNREACHABLE 
Oct 20 2002 08:09:34 PM 
Database UpDown 
Event test "Database UpDown" is cleared 
CLEARED 
Oct 08 2002 11:25:31 AM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Node UpDown 
Event test "Node UpDown" is cleared 
CLEARED 
Oct 20 2002 08:09:39 PM 
Database UpDown 
Event test "Database UpDown" is cleared 
CLEARED 
Oct 08 2002 11:25:31 AM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Maximum Extents 
Segment RUNDB_PRD.SVT_CONDITIONS_FULL in tablespace RUNDB_DATA can only allocate 0 additional extents. Segment CDFTRIG_PRD.GDS_PTS_FK_I in tablespace CDFTRIG_IDX can only allocate 0 additional extents. 
CRITICAL 
Oct 18 2002 03:46:05 PM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Maximum Extents 
Segment RUNDB_PRD.SVT_CONDITIONS_FULL in tablespace RUNDB_DATA can only allocate 0 additional extents. 
CRITICAL 
Oct 18 2002 04:46:07 PM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Maximum Extents 
Segment RUNDB_PRD.SVT_CONDITIONS_FULL in tablespace RUNDB_DATA can only allocate 0 additional extents. Segment MCS_PRD.LIMH_SENSL_FK_I in tablespace MCS_INDEX can only allocate 1 additional extents. 
CRITICAL 
Oct 20 2002 01:38:35 PM 


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


<!-- Date: Sun Oct 20 20:13:05 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Tablespace Full 
Tablespace SYSTEM is 43.93% full.  160768.0 KBytes of free space remain. Tablespace RBS is 62.18% full.  734870.0 KBytes of free space remain. Tablespace CALIB_DATA is 55.07% full.  690096.0 KBytes of free space remain. Tablespace CALIB_INDEX is 75.22% full.  253744.0 KBytes of free space remain. Tablespace RUNDB_DATA is 82.64% full.  1.31523e+06 KBytes of free space remain. Tablespace RUNDB_INDEX is 66.65% full.  2.62946e+06 KBytes of free space remain. Tablespace LRG_RBS is 55.56% full.  409592.0 KBytes of free space remain. Tablespace CALIB_SML_DATA is 37.22% full.  1.22143e+06 KBytes of free space remain. Tablespace CALIB_MED_DATA is 56.09% full.  2.... 
CRITICAL 
Oct 20 2002 07:57:31 PM 


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


<!-- Date: Sun Oct 20 20:13:29 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 


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


<!-- Date: Sun Oct 20 20:13:29 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 


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



<!-- Date: Mon Oct 21 07:52:43 2002 -->
<pre>trying to understand why i haven't been getting cdfonprd job alerts 
so i forced a 1 minute job.. it didn't trigger either.. did some clean 
up and now the alerts are coming through! .. this was bugging me 
since friday we received an alert about a trig index not being able 
to extent from donnatella vs our monitoring! 
 
even stranger was i was trying to resolve this last night and the 
damn oms went down-- &lt; Andy Romero restarted it for me today, 
since I cannot get to odsoem from home.. but he can... so that 
was very nice of him.. 
 
</pre>
<!-- Author: nstanfield  -->

<!-- Date: Mon Oct 21 10:33:30 2002 -->
<pre>
Target Name : cdfofprd.fnal.gov 
Target Type : Database 
Node Name : fcdfora1.fnal.gov 


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


<!-- Date: Mon Oct 21 10:33:30 2002 -->
<pre>
Target Name : cdfofprd.fnal.gov 
Target Type : Database 
Node Name : fcdfora1.fnal.gov 


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


<!-- Date: Mon Oct 21 10:33:30 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 


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


<!-- Date: Mon Oct 21 10:33:30 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 


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


<!-- Date: Mon Oct 21 12:19:55 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Maximum Extents 
Segment MCS_PRD.LIMH_SENSL_FK_I in tablespace MCS_INDEX can only allocate 1 additional extents. 
WARNING 
Oct 21 2002 12:16:40 PM 


</pre>
<!-- Author: oem-admin (email) -->
<!-- Comment: Mon Oct 21 12;21;59 comment by...ns -->
<pre>ALTER INDEX "MCS_PRD"."LIMH_SENSL_FK_I" 
    STORAGE ( MAXEXTENTS 60);</pre>


<!-- Comment: Mon Oct 21 13;29;05 comment by...nstanfield  -->
<pre>I am preparing a similar report for CDFTRIG for
Tom Wright.. I thought you might like to see if for Slow Controls.

Defines extents used and max extents.

Julie up'd the one that alerted today to 300!

Segment MCS_PRD.LIMH_SENSL_FK_I in tablespace MCS_INDEX can only allocate 1 


Tablespace           Table                          Extents Max Extents
-------------------- ------------------------------ ------- -----------
MCS_INDEX            SENSH_SENS_FK_I                     40          75
MCS_INDEX            LIMH_SENSL_FK_I                     39         300
MCS_INDEX            SENSH_HISTYP_FK_I                   29          75
MCS_INDEX            SENSH_PK                            23          75
MCS_INDEX            SENSH_SENST_FK_I                    23          75
MCS_INDEX            LIMH_PK                             22          40
MCS_INDEX            LIMH_SENST_FK_I                     22          40
MCS_DATA             LIMIT_HISTORIES                     13          15
MCS_DATA             SENSOR_HISTORIES                    12          75
MCS_INDEX            SENS_SENST_FK_I                      3           5
MCS_DATA             GLOBALTAGS                           2          15
MCS_INDEX            SENSOR_TIMES_IFIX_MEAS_TIME          2          20
MCS_DATA             DETECTORS                            1          10
MCS_DATA             HISTORY_TYPES                        1          10
MCS_DATA             SENSORS                              1          10
MCS_DATA             SENSORS_SENSOR_LIMITS                1           5
MCS_DATA             SENSOR_LIMITS                        1           5
MCS_DATA             SENSOR_PROPERTIES                    1          10
MCS_DATA             SENSOR_TIMES                         1          75
MCS_DATA             SENSOR_UNITS                         1           5
MCS_INDEX            DET_PK                               1           5
MCS_INDEX            GLOBT_PK                             1          15
MCS_INDEX            GLOBT_SENST_FK_I                     1          15
MCS_INDEX            HISTYP_PK                            1           5
MCS_INDEX            RC_RUNNUMBER_IND                     1          75
MCS_INDEX            SENSL_PK                             1           5
MCS_INDEX            SENSL_SENST_FK_I                     1           5
MCS_INDEX            SENSL_TAG_I                          1           5
MCS_INDEX            SENSP_PK                             1          10
MCS_INDEX            SENSP_SENSU_FK_I                     1         505
MCS_INDEX            SENST_PK                             1          75
MCS_INDEX            SENSU_PK                             1          10
MCS_INDEX            SENS_DET_FK_I                        1           5
MCS_INDEX            SENS_PK                              1          10
MCS_INDEX            SENS_SENSL_PK                        1           5
MCS_INDEX            SENS_SENSL_SENSL_FK_I                1          10
MCS_INDEX            SENS_SENSL_SENS_FK_I                 1          10
MCS_INDEX            SENS_SENSP_FK_I                      1           5
MCS_INDEX            SENS_TAG_I                           1           5

</pre>
<!-- Date: Mon Oct 21 12:23:40 2002 -->
<pre>Will be doing significant DELETEs and INSERTs  
on the RUNDB DOWNTIME_HISTORY table today. 
 
I don't think this is replicated right now, so  
only effect should be in archive log.  Guessing  
that effect will be small, but that's just  
a guess. 
</pre>
<!-- Author: W.Badgett -->
<!-- Comment: Mon Oct 21 12;26;07 comment by...bb -->
<pre>Since it's not replicated, I think I will 
drop the table instead of doing DELETEs, 
then recreate.

It's not used in any production API yet.
</pre>

<!-- Date: Mon Oct 21 13:19:58 2002 -->
<pre>
Target Name : cdfonprd.fnal.gov 
Target Type : Database 
Node Name : b0dau35.fnal.gov 

Maximum Extents 
Event test "Maximum Extents" is cleared 
CLEARED 
Oct 21 2002 01:16:42 PM 


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



<!-- Date: Mon Oct 21 13:28:21 2002 -->
<pre>Tom, 
 
Below report, shows extents and max extents for CDFTRIG application. 
We get OEM alerts regarding extents plus we get a report 
every Monday that shows us if the next extent will fail. 
 
We had an issue with our monitoring so we didn't capture 
that GDS_PTS_FK_I was about to fail.  Monitoring is 
back in place, and below is a report that will help see 
if we are in trouble anywhere else. 
 
-Nelly 
 
 
Tablespace           Table                          Extents Max Extents 
-------------------- ------------------------------ ------- ----------- 
CDFTRIG_IDX          GDS_CAPTOS_FK_I                    360         404 
CDFTRIG_IDX          GDS_PK                             294         821 
CDFTRIG_DATA         GENERATED_DOWNLOADS                244         893 
CDFTRIG_IDX          GDS_PTS_FK_I                       237         335 
CDFTRIG_IDX          GDS_SOTTS_FK_I                     214         700 
CDFTRIG_IDX          TFS_PK                              59         229 
CDFTRIG_DATA         TRIGGER_FILES                       55         334 
CDFTRIG_IDX          PBS_TPS_FK_I                        41        1000 
CDFTRIG_IDX          PBS_PK                              40        1000 
CDFTRIG_IDX          TBS_PTS_FK_I                        38          40 
CDFTRIG_IDX          TBS_PK                              34          40 
CDFTRIG_IDX          PBS_PTS_FK_I                        31        1000 
CDFTRIG_DATA         PATH_BITMASKS                       30        1000 
CDFTRIG_IDX          TBS_TNS_FK_I                        21          30 
CDFTRIG_IDX          TFS_PTS_FK_I                        21          47 
CDFTRIG_DATA         TRIGGER_BITMASKS                     6          10 
CDFTRIG_IDX          DTPS_DATS_FK_I                       6           9 
CDFTRIG_IDX          DTPS_PK                              6          10 
CDFTRIG_IDX          L3C_PK                               6          10 
CDFTRIG_IDX          CLA_TT_PK                            5         210 
CDFTRIG_DATA         L3_CALIBS                            4          10 
CDFTRIG_DATA         L3_OPTION_CLASSES_L3_TALKTOS         4         250 
CDFTRIG_IDX          DPTS_DATS_FK_I                       4           9 
CDFTRIG_IDX          DTPS_TPS_FK_I                        4          10 
CDFTRIG_IDX          PTS_GPS_FK_I                         4          21 
CDFTRIG_IDX          TNS_PK                               4          18 
CDFTRIG_IDX          TNTPS_PK                             4          10 
CDFTRIG_IDX          TNTPS_TNS_FK_I                       4          10 
CDFTRIG_IDX          TNTPS_TPS_FK_I                       4          10 
CDFTRIG_DATA         L2_TAGSETS                           3        1667 
CDFTRIG_IDX          CLA_TT_CLA_FK_I                      3         100 
CDFTRIG_IDX          CLA_TT_TT_FK_I                       3         125 
CDFTRIG_IDX          DPTS_PK                              3           7 
CDFTRIG_IDX          DPTS_PTS_FK_I                        3           7 
CDFTRIG_IDX          TPS_PK                               3          10 
CDFTRIG_IDX          L3T_PK                               2          10 
CDFTRIG_IDX          OS_PK                                2          10 
CDFTRIG_IDX          OS_TNS_FK_I                          2          10 
CDFTRIG_IDX          PTS_PK                               2          10 
CDFTRIG_DATA         CUTS_AND_PARAMETERS                  1          10 
CDFTRIG_DATA         CUTS_AND_PARAMETERS_TO_OPTIONS       1          10 
CDFTRIG_DATA         DATASETS                             1           5 
CDFTRIG_DATA         DATASETS_PHYSICS_TABLES              1           7 
CDFTRIG_DATA         DATASETS_TRIGGER_PATHS               1          10 
CDFTRIG_DATA         DEPENDENCIES                         1          10 
CDFTRIG_DATA         GLOBAL_PARAMETERS                    1           5 
CDFTRIG_DATA         GLOBAL_PARAMETER_DEFAULTS            1           5 
CDFTRIG_DATA         L2_TAGSET_DEFAULTS                   1        1250 
CDFTRIG_DATA         L3_CUT_AND_PARAMETERS                1          20 
CDFTRIG_DATA         L3_EXES                              1          10 
CDFTRIG_DATA         L3_OPTION_CLASSES                    1          10 
CDFTRIG_DATA         L3_OPTION_INSTANCES                  1          10 
CDFTRIG_DATA         L3_OPTION_SEQUENCES                  1          10 
CDFTRIG_DATA         L3_TALKTOS                           1          10 
CDFTRIG_DATA         L3_TCLS                              1          10 
CDFTRIG_DATA         OPTIONS                              1          10 
CDFTRIG_DATA         PHYSICS_TABLES                       1          10 
CDFTRIG_DATA         SPECIFIC_OPTIONS                     1          10 
CDFTRIG_DATA         SPECIFIC_OPTIONS_TO_TRIGGERS         1           7 
CDFTRIG_DATA         SPECIFIC_OPTIONS_WITH_VALUES         1          10 
CDFTRIG_DATA         TRIGDB_VERSION_TAGS                  1          10 
CDFTRIG_DATA         TRIGGER_NAMES                        1          25 
CDFTRIG_DATA         TRIGGER_NAMES_TRIGGER_PATHS          1          10 
CDFTRIG_DATA         TRIGGER_PATHS                        1          10 
CDFTRIG_DATA         VALID_TAG_SETS                       1          10 
CDFTRIG_IDX          CAPS_PK                              1           9 
CDFTRIG_IDX          CAPTOS_CAPS_FK_I                     1          10 
CDFTRIG_IDX          CAPTOS_OPTS_FK_I                     1          10 
CDFTRIG_IDX          CAPTOS_PK                            1          10 
CDFTRIG_IDX          CLA_PK                               1          10 
CDFTRIG_IDX          CP_OPT_FK_I                          1          25 
CDFTRIG_IDX          CP_PK                                1          25 
CDFTRIG_IDX          CP_TT_FK_I                           1          25 
CDFTRIG_IDX          DATS_PK                              1           5 
CDFTRIG_IDX          DEPS_CAPS_FK_I                       1           9 
CDFTRIG_IDX          DEPS_CAPS_FROM_FK_I                  1           9 
CDFTRIG_IDX          DEPS_PK                              1          10 
CDFTRIG_IDX          GPD_PK                               1           5 
CDFTRIG_IDX          GPS_PK                               1           5 
CDFTRIG_IDX          GP_DEFAULT_I                         1           5 
CDFTRIG_IDX          L3E_PK                               1          10 
CDFTRIG_IDX          L3E_PTS_FK_I                         1          10 
CDFTRIG_IDX          L3T_PTS_FK_I                         1          10 
CDFTRIG_IDX          LTD_PK                               1          41 
CDFTRIG_IDX          LTS_PK                               1          50 
CDFTRIG_IDX          LTS_PTS_FK_I                         1         750 
CDFTRIG_IDX          OPTS_PK                              1           9 
CDFTRIG_IDX          OPT_CLA_FK_I                         1          10 
CDFTRIG_IDX          OPT_PK                               1          10 
CDFTRIG_IDX          OS_OPT_FK_I                          1          10 
CDFTRIG_IDX          SOS_PK                               1          10 
CDFTRIG_IDX          SOTTS_PK                             1           7 
CDFTRIG_IDX          SOTTS_SOS_FK_I                       1           7 
CDFTRIG_IDX          SOTTS_TNS_FK_I                       1           7 
CDFTRIG_IDX          SOWVS_CAPTOS_FK_I                    1          10 
CDFTRIG_IDX          SOWVS_PK                             1          10 
CDFTRIG_IDX          SOWVS_SOS_FK_I                       1          10 
CDFTRIG_IDX          TRIGDB_VERSION_TAGS_PK               1          10 
CDFTRIG_IDX          TT_PK                                1          10 
CDFTRIG_IDX          VTS_L3C_FK_I                         1          10 
CDFTRIG_IDX          VTS_L3E_FK_I                         1          10 
CDFTRIG_IDX          VTS_L3T_FK_I                         1          10 
CDFTRIG_IDX          VTS_PK                               1          10 
 
 
 
 
 
 
 
----- Original Message -----  
From: "Alan Sill" &lt;Alan.Sill@TTU.EDU&gt; 
To: &lt;trwright@umich.edu&gt; 
Cc: "Alan Sill" &lt;Alan.Sill@TTU.EDU&gt;; "Nelly Stanfield" &lt;nelly@fnal.gov&gt; 
Sent: Friday, October 18, 2002 9:42 PM 
Subject: Fwd: max # extents (235) reached in index CDFTRIG_PRD.GDS_PTS_FK_I 
 
 
&gt; Hi Tom, 
&gt;  
&gt; Could you review the allocation of space for the trigger db tables and  
&gt; contact Nelly to make sure this is not about to happen anywhere else,  
&gt; please? 
&gt;  
&gt; (I seem to recall sending on at least one warning about this within the  
&gt; past few weeks...) 
&gt;  
&gt; Thanks, 
&gt; Alan 
&gt;  
</pre>
<!-- Author: nstanfield  -->