NAME | Synopsis | Description | Options | Operands | Examples | Exit Status | Diagnostics | See Also
hadbm create [-package=package_name] [-packagepath=path] [-historypath=path] [-devicepath=path] [-datadevices=number_of_devices_per_node] [-portbase=base_number] [-spares=number_of_spares] [-set=attribute_name_value_list] [-agent=ma_url] [-cleanup] [-no-clear] [ [-devicesize=size] [––mimumsize] -dbpasswordfile=filename] [ -adminpasswordfile=filename | -no-adminauthentication] [-scrollprogress] -hosts=host_list [dbname]
The hadbm create command creates the specified database in the HADB management domain. The create command implicitly maps the hostlist to node numbers in the given order (i.e., the first host in the host list maps to physical node 0). You can specify where to store data devices, log devices, and history files. An HADB instance must have at least two active nodes. The hostlist defines which interfaces (IP addresses) the HADB nodes communicates on. If the hostlist consists of DNS names, an IP address will be resolved using a resolve mechanism in the management agent.
The database system user will be assigned the password that is supplied in the -dbpasswordfile option.
All the paths used for the database should exist and should be writeable on the hosts.
If necessary, the create command will create or extend the HADB management domain, using the hosts in the hostlist. It also registers the HADB software package on all the hosts in the hostlist given for the create command. If a package has been registered on only some of the hosts in the domain, the create command will register the package on the remaining hosts with its current packagepath.
To easily create an HADB test system, use the -minimumsize option that will create a minimum configuration instance of HADB. This option will create a database with the following settings: devicesize=64, logbuffersize=4, databufferpoolsize=16, internallogbuffersize=4, relalgdevicesize=32.
Apart from the domain management issues, the create command is atomic. If it fails, use the -cleanup option to clean up all database resources.
If a failure occurs during the startup phase of the nodes, hadbm will report the error. However the database will not be removed by default to preserve HADB history files for analysis. The HADB history files are removed by default when the database is deleted. Always use the -cleanup option to perform a cleanup.
The file from which the administrator user password is read. Passwords can only be supplied interactively or through the password file.
The name identifying the software package. If the package is not found, a default package is registered.
Path to the HADB software package. Only used if the package is not registered in the domain. This option is deprecated. Use the hadbm registerpackage command to register a package in the domain.
The full path to the history files. If the historypath option is not specified, the default path is set up by the management agent(s). The management agent uses the entries in the configuration file (ma.server.dbhistorypath).
The path for the data and log devices. The path to the device must already exist. To set the path differently for each node or device, use the -set option. There are four types of devices:
DataDevice
NiLogDevice (node internal log device
RelalgDevice (relational algebra query device)
NoManDevice (node manager device)
If the devicepath option is not specified, the default path is set up by the management agent(s). The management agent uses the entries in the configuration file (ma.server.dbdevicepath).
The number of data devices. The number must be between 1 and 8, on each node.
Port base number used for the nodes. If there are multiple nodes on the same host, the extra nodes will get their port bases incremented by 20. The table below shows how the port bases are set up on a four node database using two hosts (hostA and hostB) with port base 15000:
Node |
Host |
Portbase |
---|---|---|
0 |
HostA |
15000 |
1 |
HostB |
15000 |
2 |
HostA |
15020 |
3 |
HostB |
15020 |
The number of spares. The number must be less than the length of the host list and at least two active nodes should be there.
Identifies the configuration parameters that will be set to the database. Must be specified as a comma-separated list of database configuration attributes in name=value format.
Use this option to set a different -devicepath for each node or each device. The syntax for each name=value pair is:
Node-nodenumber.device-devicenumber.DevicePath=path
Where: -devicenumber is only required if the device is a DataDevice.
For example: Node-0.DataDevice-0.DevicePath=/disk0. Any device path that is not set for a particular node or device defaults to the -devicepath value.
The following table identifies the configuration attributes available.
Variable |
Range |
Default |
---|---|---|
ConnectionTrace |
true/false |
false |
CoreFile |
true/false |
false |
DataBufferPoolSize |
16–2047 |
200 MB |
DataDeviceSize |
32–262144 |
1024 MB |
DevicePath |
n/a |
n/a |
EagerSessionThreshold |
0–100 |
50 (% of NumberOfSessions) |
EagerSessionTimeout |
0–2147483647 |
120 seconds |
EventBufferSize |
0–2097152 |
0 MB |
HistoryPath |
n/a |
n/a |
InternalLogBufferSize |
4–128 |
12 MB |
LogBufferSize |
4–2047 |
48 MB |
MaxTables |
200–1200 |
1200 |
NationalCollation |
<collation> |
binary |
NumberOfDatadevices |
1–8 |
1 |
NumberOfLocks |
20000–1073741824 |
50000 |
NumberOfSessions |
1–10000 |
100 |
Portbase |
10000–63000 |
15000 |
RelalgDeviceSize |
32–262144 |
128 MB |
SQLTraceMode |
none/short/full |
none |
SessionTimeout |
0–214743647 |
1800 seconds |
StartRepairDelay |
0–100000 |
20 seconds |
StatInterval |
0–600 |
600 |
SyslogFacility |
<facility> |
local0 |
SyslogLevel |
<level> |
warning |
SyslogPrefix |
<string> |
hadb-<db_name> |
TakeoverTime |
500–16000 |
10000 MS |
Valid values for NationalCollation (<collation>) are: binary/en_US/de_DE/fr_FR/zh_CN/ja_JA. Additionally, each of these values except "binary" may have a prefix "#ci", "#ai" or "#ci#ai" added to indicate case insensitivity, accent insensitivity or both.
Valid values for SyslogFacility are: local0/local1/local2/local3/local4/local5/local7/kern/mail/none
Valid values for SyslogLevel are: info/warning/error/alert/severe/none
Heterogenous attributes:
Node-<nodeno>.HistoryPath=<path_to_history_files>
Node-<nodeno>.DevicePath=<default_path_for_devices_on_node>
Node-<nodeno>.<device>.DevicePath=<path_for_device_on_node>
Where <device> is one of:
DataDevice-<datadevicenumber>
RelalgDevice
NiLogDevice
NoManDevice
<datadevicenumber> is a number in range of 0 to number of data devices specified in the -datadevices option.
Identifies the URL to the Management Agent(s) (hostlist:port).
Delete the database and its history files if the servers fails to start or if the create command fails.
By default the database is initalized and started. However, if this option is set, the database processes will not be started, the devices will not be initialized, and you must use the clear command to start the database for the first time.
The size of the data devices (specified in MB). A node may have multiple data devices, each -devicesize MB large.
create a stripped down, bare minimum configuration instance of HADB. This is to simplify setup for users wanting a simple test system, or want to play with HADB in a development scenario.
Unless overridden by other option settings, the minimumsize option will create a database with the following settings:
devicesize = 64
logbuffersize = 4
databufferpoolsize = 16
internallogbuffersize = 4
relalgdevicesize = 32
Identifies the file containing the password to be used for the system user of the database.
The file from which the administrator user password is read. Passwords can only be supplied interactively or through the password file.
Using this option eliminates the need of password identification.
If the -scrollprogress option is specified, the progress messages scroll down the screen, instead of being overwritten. The progress bar will not be displayed if the -––quiet option is specified. By default, progress messages are not specified.
A comma-separated list of all the host names or IP addresses used for all the nodesin the database. An HADB Management Agent must be running on each host. Using the IP address is recommended because there is no dependence on DNS lookups. Hostnames must be absolute. Do not use localhost or 127.0.0.1 as a hostname.
Configuring an HADB instance with double networks: To make HADB tolerate single network failures, the HADB server machines can be equiped with two NIC cards. The HADB instance must be configured to exploit these cards by specifiying both IP addresses of the NIC cards for each node. The first IP address the HADB considers as “net-0,” the second is set to “net-a.” The syntax for a two-node configuration is: -hosts=h0a+h0b,h1a+h1b.
h0a is host-0's IP address on net-0
h0b is host-0's IP address on net-1
h1a is host-1's IP address on net-0
h1b is host-1's IP address on net-1
All nodes in a database instance must be connected to both networks. It is not allowed to have some nodes connected to both networks while others are connected to only one network. The IP address of each NIC card must be on separate IP subnets.
The following example creates a database with the default database name hadb with two active nodes, and a single data device. The system prompts you for the password twice. All paths are default paths and must be created before initiating this command.
hadbm create --devicesize=256 --hosts=host1,host2 Database successfully created and started |
The following example creates a database named mydb with two active nodes, two spare nodes, two devices per node, and a specific port base number for some specific path.
hadbm create -H host1,host2 --packagepath=/home/hadb/install --historypath=/export/home/hadb/history --devicepath =/export/home/hadb/device --configpath /home/hadb/config --datadevices=2 --portbase=1500 --dbpasswordfile=/home/hadb/dbpfile --spares=2 --devicesize=512 --set "Node-0.DataDevice-0.DevicePath=/disk0 Node-0.DataDevice-0.DevicePath=/disk1" mydb Database successfully created and started |
Node 0 gets two data devices: /disk0/mydb.data.0 and /disk1/mydb.data1.1. Since Node 1 is not specified with any specific device path in the -set option, and since the -datadevices option was set to 2, Node 1 gets both devices on the path given in the -devicepath option. The devices for Node 1 are then /export/home/hadb/device/mydb.data.1 and /export/home/hadb/device/mydb.data1.1.
database exists
specified path does not exist
specified path does not have write permissions
host unreachable
hosts not added in pairs
database name specified is not valid
port base number is not valid
specified number for data devices cannot be supported
specified device size cannot be supported
specified number of spares could not be allocated
attributes are not recognized
password string not valid
invalid value set for attributes
hadbm-clear(1), hadbm-delete(1), hadbm-list(1)hadbm-start(1), hadbm-restart(1), hadbm-status(1)hadbm-stop(1)
NAME | Synopsis | Description | Options | Operands | Examples | Exit Status | Diagnostics | See Also