ADSM-L

[ADSM-L] Fw: Journal retention

2007-09-05 09:36:53
Subject: [ADSM-L] Fw: Journal retention
From: Avy Wong <AWong AT MOHEGANSUN DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 5 Sep 2007 09:34:28 -0400
Hi,
      The problem is the jbbdb files in one of the server has grown (see
size below). I looked at other servers that uses journaling has only 1KB
or low in size. Can some of the older data inside the jbbdb be deleted. Can
the size growth be contained?

tsmD__.jdb.jbbdb      2273KB
tsmC__.jdb.jbbdb    161760KB



Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860)862-8164
(cell) (860)961-6976

----- Forwarded by Avy Wong/MTGA/LNN on 09/05/2007 09:34 AM -----

             Avy Wong/MTGA/LNN

             09/05/2007 09:15                                           To
             AM                        ADSM-L AT VM.MARIST DOT EDU
                                                                        cc

                                                                   Subject
                                       Journal retention









Hello,
      I understand that there is 'errorlogretention' and
'schedlogretention' that you can set in the dsm.opt file so that to make it
easier to manage on the dsmerror.log and  the dsmsched,log. But is there a
way to manage the jbbdb files? If yes, how do you go about doing that? If
not why so? Thank you in advance.

tsmD__.jdb.jbbdb
tsmC__.jdb.jbbdb

Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860)862-8164
(cell) (860)961-6976
**************************************************************************************************
The information contained in this message may be privileged and confidential and
protected from disclosure. If the reader of this message is not the intended 
recipient, or
an employee or agent responsible for delivering this message to the intended 
recipient,
you are hereby notified that any dissemination, distribution, or copy of this
communication is strictly prohibited. If you have received this communication 
in error,
please notify us immediately by replying to the message and deleting it from 
your
computer.
**************************************************************************************************

<Prev in Thread] Current Thread [Next in Thread>