ODBC Access: How to start/configure a database with OE Explo

Posted by Stefan Marquardt on 24-Sep-2015 02:57

I had a database with configuration -n 20 and got

[2015/09/24@09:14:38.893+0200] P-4060       T-3716  I BROKER  0: (8839)  No SQL servers are available.  Try again later.

I increased -n to 50 and still have the same error.

How can I identify the cause and how to start a second broker for SQL only with OE Explorer?
Usually it should work with one broker.

Broker: 0 Pid: 4060 Logins: 86 Pend: 0 Connected: 0
                                Maximum Port for Auto Servers (-maxport): 5000
                                Minimum Port for Auto Servers (-minport): 3000
                              Maximum Number of Clients Per Server (-Ma): 12
                                        Minimum Clients Per Server (-Mi): 1
                                               Message Buffer Size (-Mm): 1024
                                              Servers per Protocol (-Mp): 0
                                       Maximum Servers Per Broker (-Mpb): 4
                                                       Network Type (-N): TCP
                    Pending client connection timeout (-PendConnTimeout): 0
                                                       Service Name (-S): 19200

                               Broker server group support (-ServerType): BOTH
                               SQL Server Max Open Cursors (-SQLCursors): 0
                                       SQL Server Stack Size (-SQLStack): 0
                         SQL Server Statement Cache Size (-SQLStmtCache): 0
Size [1K byte units] of SQL Server temp table buffer (-SQLTempStoreBuff): 0
Size [1K byte units] of SQL Server temp table disk storage (-SQLTempStoreDisk):
0
Size [1K byte units] of SQL Server temp table data page (-SQLTempStorePageSize): 0
                       Authorized data truncation (-SQLTruncateTooLarge): OFF

Sv                                                   Pend.   Cur.   Max.   Port
No    Pid  Type       Protocol               Logins  Users  Users  Users    Num

  0   4060 Login      TCP                        87      0      0     12  19200
  1   3700 Auto       TCP                        50      0      3     12   3000
  2   4016 Auto       TCP                        10      0      3     12   3001
  3   5336 Auto       TCP                         4      0      2     12   3002
  4   5372 Auto       TCP                        23      0      2     12   3003

OE Explorer should display the parameters in parentheses for easy identification....

Posted by Libor Laubacher on 24-Sep-2015 03:24

 

Ø  How can I identify the cause

The cause would be in the db.lg file, but I believe the cause lies in the fact you have only 4 remote servers (and also remote ABL clients I am assuming).
SQL client cannot connect to a remote server which has been previously spawned and used (connected to)  by ABL remote client. You may try increasing –Mn/Mpb and Mi (so the new remote server won’t be spawn immediately after client logs in), but SQL broker is a cleaner solution.
 

Ø  and how to start a second broker for SQL only with OE Explorer?

It starts automatically with the database when the group is available/defined; otherwise I believe dbman.

All Replies

Posted by Libor Laubacher on 24-Sep-2015 03:24

 

Ø  How can I identify the cause

The cause would be in the db.lg file, but I believe the cause lies in the fact you have only 4 remote servers (and also remote ABL clients I am assuming).
SQL client cannot connect to a remote server which has been previously spawned and used (connected to)  by ABL remote client. You may try increasing –Mn/Mpb and Mi (so the new remote server won’t be spawn immediately after client logs in), but SQL broker is a cleaner solution.
 

Ø  and how to start a second broker for SQL only with OE Explorer?

It starts automatically with the database when the group is available/defined; otherwise I believe dbman.

This thread is closed