• Font Size
  • S
  • M
  • L

Search via FAQ No.

  • No : 24348
  • Open Date : 2016/06/13 14:16
  • 更新日時 : 2020/10/07 10:25
  • Print

[DataSpider Servista] How to verify the cause and resolution of an error that happens on script

Script error occurred. How can I verify the cause and its resolution?
Category : 


*Contents linked from this page might be in Japanese.
Starting Version 3.0, message codes have been added to error which has allowed user to determine the cause and its countermeasures much easier. For more details, please refer to the following.
Consider the followings and if there are no issues with the environment or with the connection end, please let us know that the cause of the problem is the product at the inquiry or comment.
Verify from message code
Please verify message code from components variable ”message_category” ”message_code” “message_level” or from XML log upon script execution. In case you are executing script from designer, please verify from execution result dialog, execution log view, or error log detail view.
We ask you to follow the following guidance in an example that for Oracle adapter on version 3.2 in such case that designated table does not exist or upon requesting invalid query which results in “ORACLE0001E”.
Verify the error message and please do the following.
  •  Verify whether the cause of the error is mentioned under the "main reason" of the help section of the error.
  •  Verify whether if anything pertaining to the error's cause and resolution is mentioned in the adapter's restriction.
  •  Verify if there's any information regarding the error on the connection host's database documents.
Message code varies per version so please confirm through the product's help section. You can visit the following link to view the latest message code list.
*For versions 2.4 and prior
For versions 2.4 and prior, message codes do not output; therefore, please verify from the error message itself. For more details, please refer to the next section.
Verifying from the error message
Verify whether if there is any information in connection host's application document about the error outputted after "Reason:" in the message.
One simple way to verify would be to search the message after the "Reason:" part of the error message on the WEB to see whether if there is any information regarding the application.
As one example, following message will output when if designated table does not exist or invalid query is requested from Oracle adapter.
[get_table_data(Database/Oracle/tableread)] process has failed. Reason:[java.sql.SQLSyntaxErrorException: ORA-00942: Table or view does not exist. ]
By searching “java.sql.SQLSyntaxErrorException: ORA-00942: Table or view does not exist.” on the web, you would be able to find the following information (*the followings links will direct you to a third-party site)
 5. Troubleshoot
Reference Information
・Message Code
・Log Guide