DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 
Configuring an Address Allocation Server (AAS)

Resetting the state of the AAS database

To display information about the transaction log, select Database -> View Transaction Log. This shows the pathname of the log file, its size in bytes, and the times when it was last modified or accessed.

To display the names and times of the checkpoint files, select Database -> View Checkpoint Files.

If the transaction log has become corrupted, and the server will not start, select Database -> Delete Transaction Log, and click on OK when asked to confirm. Select Server -> Start Server to restart the server. See the warning below.

If the server will not start from the most recent checkpoint file, select Database -> Delete Checkpoint File, select the most recent entry, and then click on OK. Click on OK when asked to confirm. Select Server -> Start Server to restart the server. See the warning below.


WARNING: These procedures reset the state of the AAS database to that stored in a checkpoint file. This may result in inconsistencies in the state of addresses in the AAS database. If an address is shown as allocated, but you know that it has expired or was released, release it as described in ``Releasing, disabling, and re-enabling addresses''.

If an address is shown as unused, expired, or released, but you know that it is currently allocated, disable it and then release and re-enable it when the client has finished with the address.


If necessary, you can delete the transaction log and all checkpoint files by selecting Database -> Delete All.


WARNING: This will completely destroy all information about allocated addresses held in the AAS database.


Next topic: Troubleshooting the Address Allocation Server
Previous topic: Configuring the address server

© 2003 Caldera International, Inc. All rights reserved.
SCO OpenServer Release 5.0.7 -- 11 February 2003