Data Loss Prevention

 View Only

  • 1.  If you delete the incidents tablespace Oracle does not increase.

    Posted Dec 23, 2015 10:51 PM

    Hi.

    I have a very serious problem.
    When I delete incidents, remove the logs confirmed incidents. 
    23 дек 2015 16:36:06,814- Thread: 81 INFO [com.vontu.manager] Incident deletion completed. Incident deletion ran for 17 minute(s) 28 second(s) 0 ms and deleted 23977 incident(s)
23 дек 2015 16:36:06,979- Thread: 81 INFO [com.vontu.manager.system.incident.deletion.IncidentDeletionTask$IncidentDeletorStoredProcedureWrapper] (MANAGER.302) The system will periodically delete stale Discover incident connection records. A connection record is stale when it is older than 90 days, a period determined by the com.vontu.manager.system.IncidentDeletion.StaleStorageConnectionRecordAgeInDays property in Manager.properties.
23 дек 2015 16:36:07,093- Thread: 81 INFO [com.vontu.manager] Incident deletion started. Incident deletion started
23 дек 2015 16:37:07,128- Thread: 81 INFO [com.vontu.manager] Incident deletion completed. Incident deletion ran for 35 second(s) 0 ms and deleted 0 incident(s)
23 дек 2015 16:40:06,986- Thread: 81 INFO [com.vontu.manager.system.incident.deletion.IncidentDeletionTask$IncidentDeletorStoredProcedureWrapper] (MANAGER.302) The system will periodically delete stale Discover incident connection records. A connection record is stale when it is older than 90 days, a period determined by the com.vontu.manager.system.IncidentDeletion.StaleStorageConnectionRecordAgeInDays property in Manager.properties.
23 дек 2015 16:40:06,999- Thread: 81 INFO [com.vontu.manager] Incident deletion started. Incident deletion started
23 дек 2015 16:41:07,080- Thread: 81 INFO [com.vontu.manager] Incident deletion completed. Incident deletion ran for 28 second(s) 0 ms and deleted 0 incident(s)
23 дек 2015 16:41:49,887- Thread: 98 INFO [com.vontu.manager] User "Administrator" initiated incident action "Marked for Deletion" for 61 104 incident(s)
23 дек 2015 16:44:06,994- Thread: 81 INFO [com.vontu.manager.system.incident.deletion.IncidentDeletionTask$IncidentDeletorStoredProcedureWrapper] (MANAGER.302) The system will periodically delete stale Discover incident connection records. A connection record is stale when it is older than 90 days, a period determined by the com.vontu.manager.system.IncidentDeletion.StaleStorageConnectionRecordAgeInDays property in Manager.properties.
23 дек 2015 16:44:07,010- Thread: 81 INFO [com.vontu.manager] Incident deletion started. Incident deletion started
    But monitoring the table space does not show any change. It took 12 hours.

    11.png

    Did I do something wrong doing. Please note that 96 Used_Percent was, after i van prodact Tablespace_size.

     

    Best Regards, 

    Nicholas Sokolov



  • 2.  RE: If you delete the incidents tablespace Oracle does not increase.
    Best Answer

    Trusted Advisor
    Posted Dec 28, 2015 06:41 AM

    h inicholas,

     you did nothing wrong. This is oracle way to work. Empty spaces are not released by oracle (it seems to me there is a specific command to force it you may ask a DB administrator).

    But you should neither see it increasing as oracle will reuse free spaces into this tablespace.

    regards.

     



  • 3.  RE: If you delete the incidents tablespace Oracle does not increase.

    Posted Dec 29, 2015 04:15 AM

    Hi Stephane,

     

     

    Thank you. Could you write this special script. We dont have DBA. I am very worried that the tablespace is again filled completely. I enclose a screenshot of Enterprise Manager. 
     

     

    screen.jpg

     And what if Enforсe reports a small amount of free tablespace?!

    Regards



  • 4.  RE: If you delete the incidents tablespace Oracle does not increase.
    Best Answer

    Trusted Advisor
    Posted Dec 30, 2015 03:37 AM

    hi nicholas,

     

     unfortunately i am not a DBA and my knowledge of oracle are just minimun necessary to perform basic action. 
    I cannot give you any script that will solve this issue becaue this could create more bigger issue for you and lead to a DLP not working anymore.

    I could just give you some hint to do this and let you decide when and how to do it:

    - you main issue is with lob segment in LOB_TABLESPACE. This segmlent are mainly uised by table MessageLob and messagecomponentlob. YOu may have full list of column and from which table are stored in this tablespace with following request

    select column_name, table_name from user_lobs where tablespace_name='LOB_TABLESPACE'

    -This request will give you real size used by blob fields :

    SELECT NVL((SUM(DBMS_LOB.GETLENGTH(<replacebyblobfield>))),0) AS BYTES FROM <replace by table name>;

    - you may try to shrink your table with

    ALTER TABLE <table name> SHRINK SPACE;

     

     unfortunately i cannot garantee this will solve your issue and not provide you any support on this (there is many oracle forum on internet with many different solution).

    enforce alarm about tablespace size are also wrong on estimating real space available. But as stated previously oracle may be able to reuse free space even if you dont see it as free so if you monitor

    regularly tablespace size you shoul dnot see it increased before few month as you have deleted many incident.

     

    Regards.