In DataSpider Servista, all settings information such as projects, global resources, and triggers are stored in the repository DB if you are using it. If the repository DB is not used, the DataSpider Servista stores the information in the local directory.

 

For this reason, the error occurs when the above information cannot be browsed for some reason.

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

 

 

 

Depending on the existence of the repository DB, a place to save the setting information differs. For this reason, you need to confirm the existence of the repository DB in the beginning.

 

        2-1. If you are using the repository DB

 

If you activated it without accessing repository DB, DataSpiderServer will start without the repository DB and will run without it even if it can be accessed later on.

 

In this case, settings information that is saved in the repository DB is not browsed so projects, global resources, triggers cannot be browsed.

 

In order to confirm the above, the connection status to the repository DB is required.

 

Also, to resolve the above situation, you need to reboot the DataSpiderServer while able to connect to the repository DB.

 

        2-2. If you are not using the repository DB

 

If you are not using the repository DB, the DataSpider Servista saves the settings in a local directory.

 

In particular, information such as projects, global resources, and triggers are stored in the directory described in "Checkpoints".

For this reason, it is necessary that you need to check the directory status.

 

If you cannot browse the settings information despite the fact that it is saving, it is possible that a problem is occurring upon the DataSpiderServer startup.

 

Please check the status and environment information at the time of the startup and inquire to our support center.

 

Since the information you were able to check is unable to check now, the settings change may possibly the cause.

 

Please check if any setting was changed right before the error.

Are you using the repository DB? If so, please tell us the product name of a connecting database and its version.

Change the setting of log output by the following procedure to get the log:

 

■Procedure

Please stop the DataSpiderServer before changing the settings.

In order to obtain detailed logs, please specify the value ($ {DEBUG}) to output the most detailed log with the following settings file and key:

$ DATASPIDER_HOME / server / conf / dslog.properties

dslog = $ {DEBUG}

Please activate DataSpiderServer to reflect the changed settings.

Please get the following log and send it to our support center.

 

$ DATASPIDER_HOME / server / logs / server.log

 

$ DATASPIDER_HOME / server / logs / server.log. <Half-width number>

 

Reference information

 

 

・ Repository DB settings of DataSpider Studio

 

・CLI Console

 

・Details about the setting file(property reference)

 

・About the DataSpider Servista Log (Log Guide)