1.1.1

Table Of Contents
A sub-directory called datadictionary is created by default in the current working directory of the locator
and contains the persistent meta-data of the DDLs required for startup by locator (for example, authentication
related privileges) that have been executed in the distributed system from any of the clients or peers. This directory
is necessary for a SQLFire locator to startup and function properly.
As the output above indicates, a network server is also started by default that binds to localhost on port 1527.
This service allows thin clients to connect to one of the servers and execute SQL commands using the DRDA
protocol.
If you are restarting a locator that was used in a distributed system, the locator may need to wait for another
member (server or locator) to join the system in order to synchronize disk store persistence les. In this case,
the locator reaches a "waiting" state and does not complete startup until the dependent members join the system.
For example:
Starting SQLFire Locator using peer discovery on: 0.0.0.0[10334]
Starting network server for SQLFire Locator at address
localhost/127.0.0.1[1527]
Logs generated in
/Users/yozie/vmware/sqlf/vFabric_SQLFire_11_b40332/locator1/sqlflocator.log
SQLFire Locator pid: 9496 status: waiting
Region /_DDL_STMTS_META_REGION has potentially stale data. It is waiting
for another member to recover the latest data.
My persistent id:
DiskStore ID: ff28402d-4fa1-488f-ba47-7bf9dec8248e
Name:
Location:
/10.0.1.31:/Users/yozie/vmware/sqlf/vFabric_SQLFire_11_b40332/locator1/./datadictionary
Members with potentially new data:
[
DiskStore ID: ea249383-b103-43d5-957b-f9789eadd37c
Name:
Location:
/10.0.1.31:/Users/yozie/vmware/sqlf/vFabric_SQLFire_11_b40332/server2/./datadictionary
,
DiskStore ID: ff7d62c5-4e03-4c74-975f-c8d3639c1cee
Name:
Location:
/10.0.1.31:/Users/yozie/vmware/sqlf/vFabric_SQLFire_11_b40332/server1/./datadictionary
]
Use the "sqlf list-missing-disk-stores" command to see all disk stores that
are being waited on by other members. - See log file for details.
The locator synchronizes persistent data and completes startup after the dependent members join the system.
sqlf Logging Support
You can specify JDBC boot properties with sqlf server and sqlf locator commands to congure the
log le location and log severity level for SQLFire servers and locators, respectively.
Conguring and Using SQLFire Log Files on page 261 provides more information.
sqlf merge-logs
Merges multiple log les into a single log.
Syntax
sqlf merge-logs <logFile>+ [-out=<outFile>]
vFabric SQLFire User's Guide382
vFabric SQLFire Reference