Table of Contents
・Points to check when you want to isolate the problem
・If you want to know the reasons why checking is required
・If you still cannot determine the cause or recover from the problem even after reading this document

Also, if you would like more information related to this inquiry, please check "Reference Information."

 

1. Check related to when using repository DB

Please verify whether you are using repository DB.
You can verify from DataSpider Studio, WebConsole, and CLI Console.

Please refer to the product help for more details.
Links to the help are also noted in "Reference Information."
 

2-1. If you are using repository DB

Please check if DataSpiderServer is able to access the repository DB.
Please refer to FAQ No.24374 for how to check.

If it is unable to connect, please use the following workaround.

Workaround:
After checking repository DB is working properly, please restart the DataSpiderServer.
 

2-2. If you are not using repository DB

Please check whether the directories and files exist under the following directories.

$DATASPIDER_HOME/server/home/<User Name>
$DATASPIDER_HOME/server/etc

If the directories and files do not exist, please use the following workaround.

Workaround:
Please recover the DataSpider Servista installation directory from the backup.
 

 

1. Check related to when using repository DB
 

Depending on the repository DB existence, a directory where settings information is saved will be different.
Therefore, you first need to check the existence of repository DB.
 

2-1. If you are using repository DB

If you start under the situation where repository DB is unable to be accessed, DataSpider Server will start without the repository DB. As a result, even if it becomes available to be accessed, it will still operate without it.

In this case, it will create a problem in which the project, global resource, and trigger are unable to browse because settings information saved in the repository DB are not being browsed.
In order to check the situation mentioned above, a connection status to repository DB is required.

Also, in order to solve the problem mentioned above, you must restart the DataSpider Server under the condition where repository DB is able to be connected.

 

2-2. If you are not using repository DB

If you are not using repository DB, DataSpider Servista will save settings under the local directory.
Especially, information such as project, global resource trigger, etc. is saved under the directory mentioned in the "Points to Check."

Therefore, you must check the directory status.

 

 

 

If it still cannot browse even if the settings information is saved, a problem may exist at the DataSpiderServer startup.

Check the situation and environment of the program startup, and please inquire at the Support Center.

 

(1) Settings you changed right before the problem started to occur

Because the information you were able to see is not available anymore, one of the settings you changed might be the reason.

Please check whether there is any setting you changed right before the problem started to occur.

 

(2) Repository DB Information

Check to see whether repository DB is used. If you are using repository DB, please tell us the connection host information regarding database product name and its version.

 

(3) Detailed log of when starting DataSpiderServer

Export a detailed log of when starting DataSpiderServer and check whether a problem is occurring at the time of startup.

Take the following steps to configure the log output settings to obtain the log.

■ Procedure
1. Stop DataSpider Server
　Stop DataSpiderServer before changing the settings.

2. Change the log output settings
　Specify a value (${DEBUG}) to export the most detailed log at the following settings file and key to obtain a detailed log.

・Settings File
　$DATASPIDER_HOME/server/conf/dslog.properties

・Settings Key and Settings
　dslog=${DEBUG}

3.  Start DataSpiderServer

　In order to reflect the settings changes, start the DataSpiderServer.

4. Obtaining logs
　Obtain the following log and send it to the Support Center.
　$DATASPIDER_HOME/server/logs/server.log
　$DATASPIDER_HOME/server/logs/server.log.<Half-width Alphanumeric>

 

 

[Reference Information]

 

FAQ No.24374
As a part of operation monitoring, I want to check whether DataSpiderServer can be connected to the Repository DB.What is the checking method?

・DataSpider Studio's Repository DB settings
　https://www.hulft.com/help/en-us/DataSpider/latest/help/en/studio/repository_database.html
・CLI Console
　https://www.hulft.com/help/en-us/DataSpider/latest/help/en/cli/cli.html
・Detail of Settings File (Property Reference)
　https://www.hulft.com/help/en-us/DataSpider/latest/help/en/servista/properties_reference.html#dslog_srv
・About DataSpider Servista Logs (Log Guide)
　https://www.hulft.com/help/en-us/DataSpider/latest/help/en/servista/service_production.html#log_guide