Differences between revisions 2 and 4 (spanning 2 versions)
Revision 2 as of 2008-05-16 05:36:51
Size: 254
Comment:
Revision 4 as of 2008-05-16 05:52:54
Size: 1259
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 *
 *
  *
  *
 * Install SQL database. This could be either on same server that control reside or different.
 * Also download and install odbc driver for your database. This will put the file in /etc/odbc.ini which you will need to configure:
  * [control] - this is a connection name that you use for database
  * Driver: - this is driver that is used
  * Databasename: dabasename that you create
  * login:
  * password:
 * Create database now using following command
  * #createdb databasename
 * Create table command
  * #createtb --help ( to see option)
  * #createtb -d
 * kill all control users
 * Set flag in cooad. i.e Enable update of odbc data file =y . Now this flag will start loging in dblog.dat.
 * If the sql database is not used from the begining of control, all files will not be logged in dblog.dat to update in sql database. So simple enabling flag will not logged old files of control to dblog.dat, only the new files will be logged. To update old and as well as old , use this command.
  * #fdb2log

This instruction will help you understand how CONTROL and SQL database works together. Also this instruction will be helpful to troubleshoot or implementing sql database for the client.

Steps to configure sql database and control

  • Install SQL database. This could be either on same server that control reside or different.
  • Also download and install odbc driver for your database. This will put the file in /etc/odbc.ini which you will need to configure:
    • [control] - this is a connection name that you use for database
    • Driver: - this is driver that is used
    • Databasename: dabasename that you create
    • login:
    • password:
  • Create database now using following command
    • #createdb databasename
  • Create table command
    • #createtb --help ( to see option)
    • #createtb -d
  • kill all control users
  • Set flag in cooad. i.e Enable update of odbc data file =y . Now this flag will start loging in dblog.dat.
  • If the sql database is not used from the begining of control, all files will not be logged in dblog.dat to update in sql database. So simple enabling flag will not logged old files of control to dblog.dat, only the new files will be logged. To update old and as well as old , use this command.
    • #fdb2log

SQL_Mirroring (last edited 2013-09-18 06:09:33 by localhost)