Avaya Business Communications Manager - PeriRDB Manual de usuario descargar pdf (Pagina 42)

PeriRDB User’s Guide

Page 42

Using Option U

An example of using the SQLClnt with option U is given below:

"sqlclnt -v 2 -s 221 -m oracle -U

uiYLCVuOUkLOyMpDjkj/4myePZhW5HhwhBYbgw== -1 /tmp/sqlclntlog -c"

The U option is followed by the encrypted RDBMS connect string which is generated

by the Cryptutil. The SQLClnt decrypts this string and connects to the RDBMS.

The options U and u cannot be specified together as there can only be one primary

database.

Using Option B

The encrypted RDBMS connect strings can be used with the Backup/Fail-Over

database as well as the primary database. The example for the same is given below:

"sqlclnt -v 254 -s 221 -m oracle -U

uiYLCVuOUkLOyMpDjkj/4myePZhW5HhwhBY/jointfilesconvert/86605/bgw==-B

uiYLCVuOUkLOyMpDjkj/4myePZhW5HhwhBY/jointfilesconvert/86605/bgw== -1

/tmp/sqlclntlog & -c"

Option B is followed by an encrypted RDBMS Connect string. Unlike option U, there

can be more than one option B specified when starting a SQLClnt as there can be

more than one backup/failover server.

Using encrypted Connect Strings with gen.cfg

For starting the SQLClnt from gen.cfg, the procedure mentioned in the “Using the

Encrypted Connect String with SQLClnt” on page 41 holds good. A sample entry in

the gen.cfg for a SQLClnt with encrypted RDBMS connect string is given below.

"sqlclnt - 0 0 "sqlclnt v 2 -s 221 -m oracle -U

uiYLCVuOUkLOyMpDjkj/4myePZhW5HhwhBY/jointfilesconvert/86605/bgw== -l

/tmp/sqlclntlog -c""

1 2 ... 37 38 39 40 41 42 43 44 45 46 47 ... 59 60

Sin comentarios

Avaya Business Communications Manager - PeriRDB Manual de usuario Pagina 42