Eddie C wrote:
I ran
DB ERROR: db_verify: Page 30: out-of-order key at entry 498
DB ERROR: db_verify: DB->verify: db/o_com/channelcontentowner.db4:
DB_VERIFY_BAD: Database verification failed
I'm assuming that you are running the correct version of db_verify (it
should
perform a version che
Eddie C wrote:
The document I had suggested using ldapsearch and ldapadd to migrate
data. If lidf2db commands are faster/better I will use them.
>> Try creating all of the required indexes first, then doing the
import of
>> your original LDIF.
I am willing to try this, but It is scary to me.
The document I had suggested using ldapsearch and ldapadd to migrate data.
If lidf2db commands are faster/better I will use them.
Try creating all of the required indexes first, then doing the import of
your original LDIF.
I am willing to try this, but It is scary to me. I would have rather yo
Richard Megginson wrote:
Eddie C wrote:
I recently did an ldif backup of our iplanet 52 database. Its about
an 88 MB ldif file.
I took this to a new FDS server Dell 850 3 ghz duel core 2 sata hard
disks.
I ran an ldapadd the data imported perfectly.
Are there any reason to use ldapadd ins
Eddie C wrote:
I recently did an ldif backup of our iplanet 52 database. Its about an
88 MB ldif file.
I took this to a new FDS server Dell 850 3 ghz duel core 2 sata hard
disks.
I ran an ldapadd the data imported perfectly.
Then I tried to cutover some systems and give the database some load.
I recently did an ldif backup of our iplanet 52 database. Its about an 88 MB
ldif file.
I took this to a new FDS server Dell 850 3 ghz duel core 2 sata hard disks.
I ran an ldapadd the data imported perfectly.
Then I tried to cutover some systems and give the database some load.
System went 200%
