Sun Java System Application Server Enterprise Edition 8.1 2005Q2 High Availability Administration Guide

- Previous: Refragmenting the Database
- Next: Monitoring HADB

## Adding Nodes by Recreating the Database

If online refragmentation fails persistently when you add new nodes (either due to lack of data device space or other reasons), recreate the database with new nodes. This will lead to the loss of existing user data and schema data.

### To add nodes by recreating the database

This procedure enables you to maintain HADB availability throughout the process.

1. For each Application Server instance:

   1. Disable the Application Server instance in the load balancer.

   2. Disable session persistence.

   3. Restart the Application Server instance.

   4. Re-enable the Application Server instance in the load balancer.

   If you do not need to maintain availability, you can disable and re-enable all the server instances at once in the load balancer. This saves time and prevents failover of outdated session data.

2. Stop the database as described in Stopping a Database .

3. Delete the database as described in Removing a Database .

4. Recreate the database with the additional nodes as described in Creating a Database

5. Reconfigure the JDBC connection pool as described in Configuring the JDBC Connection Pool

6. Reload the session persistence store.

7. For each Application Server instance:

   1. Disable the Application Server instance in the load balancer.

   2. Enable session persistence.

   3. Restart the Application Server instance.

   4. Re-enable the Application Server instance in the load balancer.

   If you do not need to maintain availability, you can disable and re-enable all the server instances at once in the load balancer. This saves time and prevents failover of outdated session data.

- Previous: Refragmenting the Database
- Next: Monitoring HADB

- © 2010, Oracle Corporation and/or its affiliates