- Top Category > General Questions > DataSpider Servista > [DataSpider Servista] An error occurred when executing a process that specified JDBC Proxy Server in the global resource.
Search via FAQ No.
NEW
Please tell me about the cause and a way to resolve this problem.
[DataSpider Servista] An error occurred when executing a process that specified JDBC Proxy Server in the global resource.
The following error occurred when executing a process that specified JDBC Proxy Server in the global resource:
SQLRemoteException: An error occurred while communicating to the server.
- Category :
Answer
■ Cause
The error in the question occurs when DataSpiderServer fails to connect to JDBC Proxy Server. In the past case, it occurred for the following reasons:
- Connection Failure to JDBC Proxy Server
JDBC Proxy Server was stopped or the communication was unable to establish using the JDBC Proxy Server configuration information
- DataSpiderServer has not been restarted yet
If you have restarted only JDBC Proxy Server, but not DataSpiderServer, connection information held by the DataSpiderServer may remain old and the error may occur.
- Mismatch in Modules
A mismatch occurred between the versions of DataSpiderServer and JDBC Proxy Server. In this case, the error will occur due to the mismatch in modules.
■Workaround
- Check the operation status and the network settings of JDBC Proxy Server
Please make sure JDBC Proxy Server was running at the time of the error occurrence, and start it if it was stopped.
In addition, using the "Proxy server" and the "Proxy port number" value set in the global resource, check whether the server with DataSpiderServer can access the server with the JDBC Proxy Server.
If you cannot connect, please change the settings and the network environment settings
*A tool such as telnet can check the accessibility.
*Please check the "Reference Information" for details.
Please note that there is no way to specify NIC in the current JDBC Proxy Server settings, so if multiple NICs are configured, either enable only one NIC or install JDBC Proxy Server on the server with only one IP address.
- Restart DataSpiderServer
If you did restart the JDBC Proxy Server, then please check if you restarted the DataSpiderServer afterward. If it was not restarted or you cannot confirm whether it was restarted, please restart the DataSpiderServer and check if the problem resolves.
- Match the Module Versions
Please check whether DataSpiderServer and JDBC Proxy Server were installed with the same module version.
Also, if patches or service packs are applied to the DataSpiderServer and those contain the JDBC Proxy Server modules, make sure that the patches or the service packs are also applied to the JDBC Proxy Server.
If you cannot confirm it, please either reinstall JDBC Proxy Server to match the DataSpiderServer version or reapply patches or service packs for JDBC Proxy Server.
If the error is not resolved with the above method, please obtain "Information Required for Investigation" and contact the support center.
■Information Required for Investigation
- Error occurrence time
Please check the time when the error occurred. Also, please confirm any changes to settings and the work performed before and after the error.
- Occurrence frequency and Temporary Workaround Availability
In order to confirm the operation effect, please confirm the frequency of the error occurrence (daily, monthly, etc.) and the availability of temporary workaround (such as restarting with the service "recovery “).
- Log file
Please send the following log in order for us to check the status of the DataSpiderServer in which the error is occurring:
$ DATASPIDER_HOME / server / logs / server.log
$ DATASPIDER_HOME / server / logs / server.log.N (N: integer)
$ DATASPIDER_HOME / server / logs / server.error.log
$ DATASPIDER_HOME / server / logs / $ {execution date} /exec.log
In addition, please send the following log that was running during the corresponding time frame:
$ DATASPIDER_HOME / server / logs / $ {execution date} / execution / $ {execution ID} .xml
- JDBC Proxy Server Log
Please send the following log when the error occurred.
$ JDBCPROXY_HOME / logs / jdbcproxy.log
In addition, please send the following log that is output with the time stamp of when the error occurred, if it exists:
$ JDBCPROXY_HOME / logs / hs_err_pidNNNN.log (NNNN: integer)
- Log on the OS Side
Please check if there is no output related to JDBC Proxy Server in the OS event log etc. when the error occurred. If it is output, please send a copy of it to a text file.
Reference information
- How to use telnet
You can check if the specified host can be accessed with the specified port number by executing the following command.
telnet <host name> <port number>
If you cannot communicate properly, communication errors such as Connection refused will occur. If you can communicate normally, nothing is displayed on the screen. In this case, please quit the telnet by pressing Ctrl + [
Note that Telnet is not installed immediately after the OS installation, and must be installed separately. Please refer to the following public information for details:
- Telnet Client Overview (External Site)
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731442(v=ws.11)
* Since Telnet is a Microsoft tool, if you have any questions regarding the details of usage, please check with Microsoft.