Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Internal\s+error\s+DBLOG666\s+$5\.4\.0\.3\s+Win32\-Server$\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Internal\s+error\s+DBLOG666\s+$5\.4\.0\.3\s+Win32\-Server$\s*$/: 5 ]

Total 5 documents matching your query.

1. [ADSM-L] Internal error DBLOG666 (5.4.0.3 Win32-Server) (score: 1): Author: Michael Bartl <michael.bartl AT SPACE DOT NET>; Date: Mon, 18 Feb 2008 11:18:05 +0100; Good morning everybody, our TSM server won't start and brings one of those feared ANR9999D messages (see below). First I thought about the Log being full and did an extend of 100MB (from 10000 to 101; /lists/html/ADSM-L/2008-02/msg00246.html (10,879 bytes)
2. Re: [ADSM-L] Internal error DBLOG666 (5.4.0.3 Win32-Server) (score: 1): Author: Henrik Vahlstedt <SHWL AT STATOILHYDRO DOT COM>; Date: Mon, 18 Feb 2008 12:03:23 +0100; Hello, I would open a support case asap! Neither Google or IBM support pages have any relevant information about these error. //Henrik --Original Message-- From: ADSM: Dist Stor Manager [mailto:ADSM-; /lists/html/ADSM-L/2008-02/msg00247.html (11,589 bytes)
3. Re: [ADSM-L] Internal error DBLOG666 (5.4.0.3 Win32-Server) (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Mon, 18 Feb 2008 07:04:41 -0500; Michael - Henrik's advice is the best... It appears that you have a damaged Recovery Log, or at least one which is inconsistent with the database. Unfortunately, TSM's architecture leaves the informa; /lists/html/ADSM-L/2008-02/msg00248.html (9,916 bytes)
4. Re: [ADSM-L] Internal error DBLOG666 (5.4.0.3 Win32-Server) (score: 1): Author: Michael Bartl <michael.bartl AT SPACE DOT NET>; Date: Mon, 18 Feb 2008 23:50:00 +0100; Hi all, first of all, many thanks for the fast replies. You've been right, we had a corrupted Recovery Log. We've opened a PMR with IBM service and had to make this decision: A) Restore the DB (Point; /lists/html/ADSM-L/2008-02/msg00251.html (9,525 bytes)
5. Re: [ADSM-L] Internal error DBLOG666 (5.4.0.3 Win32-Server) (score: 1): Author: William Boyer <bjdboyer AT COMCAST DOT NET>; Date: Mon, 18 Feb 2008 20:28:57 -0500; I know this won't help you now, but if you are running with LOGCOPY volumes I've been able to recover from a corrupted log file in the past by renaming the primary log volumes in the filesystem and b; /lists/html/ADSM-L/2008-02/msg00252.html (10,372 bytes)

Current List: 1 - 5
Page: [1]