2.3.7 Creating a Symfoware Database Cluster

Create the database cluster.
Note
- If the configuration requires password authentication, create a .pgpass file in the home directory of the operating system user who is to start Symfoware Server, and then specify a password for the template1 database as this is required. This will be used when PRIMECLUSTER checks the operation of the Symfoware database server. If authentication fails, a fault will be assumed to have occurred in the database server.
- The value specified for the port parameter in postgresql.conf needs to be set in the /etc/services files on all nodes.
- Since postgresql.conf is stored in the data directory, it becomes a common configuration file for each node in the shared disk. Therefore, it must be taken into account that the path set for postgresql.conf must be valid for the Symfoware Server processes started on each node. For example, if a local directory is specified in the core_directory parameter, that local directory must have been created on all nodes.
- To execute the Symfoware Server commands, you must configure the environment variables on each node.
- Use the initdb command to create a database cluster.
- Specify "off" for the restart_after_crash parameter in postgresql.conf.
  If "on" is specified, or the default value is used for the restart_after_crash parameter, behaviors equivalent to restarting the Symfoware Server, including crash recovery, will be performed when some server processes go down. When linking with PRIMECLUSTER, however, a failover will occur after an error is detected as soon as some server processes go down, and server processes restarting will be forced to stop. This is to inhibit complex behaviors such as processes being canceled in the middle of restarting for no particular meaningful purpose.
Check starting, connection, and stopping at each node. The procedure is as follows.
Note
Queries are issued to monitor the Symfoware Server from PRIMECLUSTER. With this connection process, if a password is requested, the monitoring process cannot be continued. For this reason, when checking the connection, ensure that connections can be made without entering a password.
1. Check the starting, connection, and stopping at node 1.
  Use the pg_ctl command to start and stop the node.
  For connection, execute the following to ensure that connections can be made without entering a password:
```
su - OsUser
psql -d template1 -p portNum [ -U dbUser]
```
  OsUser: Operating system user to start the Symfoware Server
  portNum: Port number specified when the database cluster was created
  dbUser: Database superuser
  If the database superuser is specified at the time of executing the initdb command, or if the database superuser has been changed after the initdb command was executed, specify the user for the -U option. If the database superuser is not specified or changed, omit this.
2. Unmount all file systems containing the resources required to create database clusters (such as the data storage destination directory) on node 1, and stop the GDS volume.
3. Start the GDS volume on node 2, and mount all file systems containing the resources required to create database clusters (such as the data storage destination directory).
4. Check starting, connection, and stopping at node 2.
  Perform the same check as step 1.
5. Unmount all file systems containing the resources required to create database clusters (such as the data storage destination directory) on node 2, and stop the GDS volume.
6. Start the GDS volume on node 1, and mount all file systems containing the resources required to create database clusters (such as the data storage destination directory).

See

Refer to "Using the initdb Command" of "Creating an Instance" in the "Installation and Setup Guide for Server" for information on how to create a database cluster.
Refer to "The Password File" in "Client Interfaces" in the PostgreSQL Documentation for information on files for which passwords are set.