Database Problems

Refer to the NNSYMessageLog.nml and sybesp.log files for database-related errors. The sybesp.log file is located in the <server install directory>\io43svr\instances\<server name>\runtime directory. To enable debug level logging to this file, verify that the following runtime instance configuration properties are set:

Services Console Logging level: DEBUG
Services Debug Setting: TRUE
Services Log File Level: DEBUG

Verify that:

Your environment is configured properly for database access.
The database configuration in the Endpoint Manager contains the correct connection information.
The JDBC path is correct in Window>Preferences.
A connection to the target database is established.
The correct configuration data is correctly mapped for the instance.

For assistance in configuring databases, see JDBC and JDBC Driver Preferences.

Connection to database cannot be made


Problem	An error is returned when trying to connect to the database during runtime.
Resolution	Verify that your database endpoints are fully configured, including user name, password, and host machine. Verify that the JDBC files are in the server <install dir>/jar/ext/jdbc/lib directory Ping the database to ensure the host is up and the database is available.

Error invoking SQL request


Error	com.sybase.jplugin.util.FailureResultException: Error occurred invoking request. com.sybase.ai.common.adapter.AIException: GSP1017 JDBC call to invoke procedure failed: com.sybase.jdbc2.jdbc.SybSQLException: The name "some 'value''' is illegal in this context. Only constants, constant expressions, or variables allowed here. Column names are illegal.
Resolution	Make sure that your SQL statement uses single quotes to quote string values and double quotes to quote SQL identifiers.

Process fails at runtime when using a Database Service that has a schema changed from strongly-typed to generically-typed


Problem	When defining operations for database services, you can specify whether each operation is strongly-typed or generically-typed. A strongly-typed database operation has detailed information about the data type of each column of its result set. A generically-typed operation does not have this detailed information. The Database Service Wizard provides a page for specifying this choice. In releases up to 4.0.3, the user interface for editing a database operation allowed this option to be modified. This feature (changing the type of an existing operation) is not supported by the underlying product infrastructure, so any service with an operation modified in this manner causes errors at runtime.
Resolution	The page on which the strongly-typed or generically-typed choice could be changed for an existing operation is no longer provided. This is a valid option when new database services are created, and this feature is available in the New Database Service Wizard.

Database shuts down at runtime when using a modified operation in an updated version of a package


Problem	The runtime instance fails to start and the following Error message appears in NNSYMessageLog.nml: 2004-06-16 08:39:44.310\|psengine.exe\|2644\|1752\|?\|?\|Error\|?\|Message part "Resource1" was not found. com.sybase.ebd.eai.es.target.wsdl.sql.exception.SqlPluginException: Message part "Resource1" was not found. at com.sybase.ebd.eai.es.target.wsdl.sql.SQLService.setTypedInputs(Unknown Source) at com.sybase.ebd.eai.es.target.wsdl.sql.SQLService.doTyped(Unknown Source) at com.sybase.ebd.eai.es.target.wsdl.sql.SQLService.execute(Unknown Source) at com.sybase.ebd.eai.es.target.EndpointService.handleExecute(Unknown Source) at com.sybase.ebd.eai.es.target.EndpointService.handleExecute(Unknown Source) at com.sybase.jplugin.wsdl.sql.SqlPluginImpl.handleExecute(Unknown Source)
Resolution	Consider whether any operations were modified and included in an updated version of the package. If operations were modified and included in the updated package, verify that the auto-build preference is enabled. To set the auto-build preference: Go to Window > Preferences. Highlight Workbench. Select Perform build automatically on resource modification. Click OK. If the auto-build preference was previously disabled: Go to Project > Rebuild All. This manually produces the same result as when auto-build is enabled. Repackage. Redeploy. Start the runtime instance.