Displaying 3 results from an estimated 3 matches for "p0000000000000048557".
2024 Jul 18
1
dbcheck gets uncaught exception
...on. How would I fix such a
duplicate key in that file through sam.ldb?
To identify the dup key I creted a tdbdump and then counted the keys:
awk '$1 ~ /^key/ {print $3}' DOMAINDNSZONES.tdbdump |sort|uniq -c | sort
-nr | head
the dupliate entry is
{
key(42) = "DN=@INDEX:USNCHANGED:p0000000000000048557\00"
data(116) =
"h\19\01&\02\00\00\00&\00\00\00 at INDEX:USNCHANGED:p0000000000000048557\00\00\00\00\00\00)\00\00\00\0B\00\00\00 at IDXVERSION\00\01\00\00\00\01\01\04\00\00\00 at IDX\00\01\00\00\00\01\103\00$s$\BB\D6;UJ\B1|\F3\B5\90l6\A4\00"
}
Maybe it is related or not bu...
2024 Jul 18
1
dbcheck gets uncaught exception
...; switch useful here.
>
> To identify the dup key I creted a tdbdump and then counted the keys:
>
> awk '$1 ~ /^key/ {print $3}' DOMAINDNSZONES.tdbdump |sort|uniq -c |
> sort -nr | head
>
> the dupliate entry is
>
> {
> key(42) = "DN=@INDEX:USNCHANGED:p0000000000000048557\00"
> data(116) =
> "h\19\01&\02\00\00\00&\00\00\00 at INDEX:USNCHANGED:p0000000000000048557\00\00\00\00\00\00)\00\00\00\0B\00\00\00 at IDXVERSION\00\01\00\00\00\01\01\04\00\00\00 at IDX\00\01\00\00\00\01\103\00$s$\BB\D6;UJ\B1|\F3\B5\90l6\A4\00"
> }
>
>
>...
2024 Jul 17
1
dbcheck gets uncaught exception
> Anything after the 'Join failed' can be ignored, it is just an
> artefact of the cleanup.
>
> I posted this:
>
> Do not remove the existing database, well not unless you want to
> recreate your domain.
>
> I will amend it:
>
> Do not touch 'DC=DOMAINDNSZONES,DC=COMPANY,DC=INTRA.ldb' (or any of the
> other files in the same directory)