Configuration errors using SQLEXP in OpenEdge 10.2B

[jeremysimmons]

I could use some help getting SQLEXP working.
Windows 7 x64. OpenEdge 10.2B 32-bit.

started ProEnv.
ran command sql_env.
tried to run sqlexp in character mode using:
proenv>sqlexp -char -url jdbc:jdbcprogress:T:localhost:9800:sxe61

OpenEdge Release 10.2B as of Mon Dec 14 17:02:01 EST 2009
Connecting user "jsimmons" to URL "jdbc:jdbcprogress:T:localhost:9800:sxe61"...
(8920)
Error: No suitable driver. (8933)
See "C:\OpenEdge\WRK\sqlexp.log" and "C:\OpenEdge\WRK\SQLExplorer.exceptions" fi
les for more information. (8950)

C:\OpenEdge\WRK\sqlexp.log
[2/28/11 8:15:17 AM] [3] [SQLExplorer] === SQLExplorer starting. ===
[2/28/11 8:15:17 AM] [3] [SQLExplorer] ### ARGS: -char -url jdbc:jdbcprogress:T:localhost:9800:sxe61
[2/28/11 8:15:18 AM] [3] [SQLExplorer] Connecting user "jsimmons" to URL "jdbc:jdbcprogress:T:localhost:9800:sxe61"... (8920)
[2/28/11 8:15:18 AM] [3] [SQLExplorer] Loading JDBC driver com.ddtek.jdbc.openedge.OpenEdgeDriver.
[2/28/11 8:15:18 AM] [0] [*UnexpectedError*] * recorded as exception #13 in file C:\OpenEdge\WRK\SQLExplorer.exceptions.
[2/28/11 8:15:18 AM] [3] [SQLExplorer] === SQLExplorer ending. ===
C:\OpenEdge\WRK\SQLExplorer.exceptions
====== Start exception logging == "C:\OpenEdge\WRK\SQLExplorer.exceptions" opened == Mon Feb 28 08:15:18 MST 2011 ======
**** 13 ****
Exception at Mon Feb 28 08:15:18 MST 2011: java.sql.SQLException
Message (throw): ### Connect stack trace. ###
Message (excp): No suitable driver
Stack Trace:
java.sql.SQLException: No suitable driver
at java.sql.DriverManager.getConnection(DriverManager.java:545)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at com.progress.sql.explorer.SQLConnectServer.call(SQLConnectServer.java:41)
at com.progress.common.rmiregistry.TryIt.run(TryIt.java:186)

 

[medu]

you need to use the new datadirect driver...

sqlexp -url jdbc:datadirectpenedge://localhost:9800;databaseName=sxe61

or simply use

sqlexp -db sxe61 -S 9800

 

[jeremysimmons]

Tried this command:
proenv>sqlexp -char -db sxe61 -S 9800 -user UUUUU -password PPPPP

OpenEdge Release 10.2B as of Mon Dec 14 17:02:01 EST 2009
Connecting user "UUUUUU" to URL "jdbc:datadirectpenedge://uscsnjsimmons1:9800;databaseName=sxe61"... (8920)
Error: [DataDirect][OpenEdge JDBC Driver]OE Broker fails to find a server available for connecting .. (8933)
See "C:\OpenEdge\WRK\sqlexp.log" and "C:\OpenEdge\WRK\SQLExplorer.exceptions" files for more information. (8950)

[C:\OpenEdge\WRK\sqlexp.log]
[3/1/11 1:49:07 PM]
[3/1/11 1:49:07 PM]=== Start logging. Local time: 3/1/11 1:49:07 PM. ===
[3/1/11 1:49:07 PM]
[3/1/11 1:49:07 PM] [3] [SQLExplorer] Local C:\OpenEdge\WRK\SQLExplorer.properties file will be used. (SQLMsg036)
[3/1/11 1:49:07 PM] [3] [SQLExplorer] Setting Connect to jdbc:datadirectpenedge://uscsnjsimmons1:9800;databaseName=sxe61
[3/1/11 1:49:07 PM] [3] [SQLExplorer] === SQLExplorer starting. ===
[3/1/11 1:49:07 PM] [3] [SQLExplorer] ### ARGS: -char -db sxe61 -H uscsnjsimmons1 -S 9800 -user 1000sys -password xxx
[3/1/11 1:49:07 PM] [3] [SQLExplorer] Connecting user "UUUUUU" to URL "jdbc:datadirectpenedge://uscsnjsimmons1:9800;databaseName=sxe61"... (8920)
[3/1/11 1:49:07 PM] [3] [SQLExplorer] Loading JDBC driver com.ddtek.jdbc.openedge.OpenEdgeDriver.
[3/1/11 1:49:07 PM] [0] [*UnexpectedError*] * recorded as exception #17 in file C:\OpenEdge\WRK\SQLExplorer.exceptions.
[3/1/11 1:49:07 PM] [3] [SQLExplorer] === SQLExplorer ending. ===

====== Start exception logging == "C:\OpenEdge\WRK\SQLExplorer.exceptions" opened == Tue Mar 01 13:49:07 MST 2011 ======

**** 17 ****
Exception at Tue Mar 01 13:49:07 MST 2011: java.sql.SQLException
Message (throw): ### Connect stack trace. ###
Message (excp): [DataDirect][OpenEdge JDBC Driver]OE Broker fails to find a server available for connecting .
Stack Trace:
java.sql.SQLException: [DataDirect][OpenEdge JDBC Driver]OE Broker fails to find a server available for connecting .
... rest of stack trace ...

 

[Casper]

Database is most lilely not confiured for sql access. The error is just what it is: There is no available server (_sqlsrv2 process) for the sql explorer to connect too. Did you set up a secondary broker for sql connections for that database? Here on Progresstalk and in the KB there are plenty examples on how to do this.

http://www.progresstalk.com/showthread.php?114511-Cannot-create-Secondary-Broker-in-Multi-User-Mode

Regards,
Casper

 

[jeremysimmons]

Thanks for the post casper.
I used the instructions at How to set up a secondary login broker for SQL-92 connections for Progress 9.1D and above to setup my Database server correctly.

I also had to use a user that had the SQL RESOURCE priviledge. In this case it was the user sysprogress. The article Basic Guide to Defining Progress SQL-92 Database Permissions & Security was very helpful for this.

 

[vinod_home]

Re: норма ток мал

what do you see in the database log file. You can also run a promon on the database and check if there are any SQSV servers available to accept any sql connections.

HTH

 

[jeremysimmons]

Re: норма ток мал

@vinod_home - didn't check the log file. as stated earlier, I was able to fix the issue by allocating more login brokers for my database server.
Thanks for the tip about the promon. I'll look into that.