Transaction log is full

If the schema defines too many attributes, you might get an error that the transaction log is full. Follow the steps to resolve this issue.

The following messages might be displayed at IBM® Security Directory Server startup:

SQL0965C The transaction log for the database is full
SQLSTATE=57011 slapd unable to start because all backends failed to configure

You might be required to increase the DB2® transaction log sizes. Type the following commands:

db2 update db cfg for ldaptest using logprimary X
db2 update db cfg for ldaptest using logsecond X

where X is greater than the currently defined size.

You can check the current log size by using the following command:

db2 get db cfg for dbname