HPE NonStop SQL/MX Error – 13065 End of file was found after syntax-item1 when syntax-item2 was expected, near line number.

In this blog post, let’s learn about the error message “13065 End of file was found after syntax-item1 when syntax-item2 was expected, near line number.” when working with HPE NonStop SQL/MX, the reason for the error and the solution to fix this error message.

Error Message

13065 End of file was found after syntax-item1 when syntax-item2 was expected, near line number.

Reason for the Error

The compiler found end-of-file specified after syntax-item1 when it was expecting syntax-item2near line number.

For example, when the preprocessor parses host variables in an EXEC SQL/MX statement, they must be preceded with a : (colon). If the colon is missing, the preprocessor would probably find the name of the host variable next, but keeps looking until it reaches the end of file or finds a colon. If it reaches end-of-file first and the next thing the preprocessor finds before reaching the end-of-file is the name of a host variable, the message would look like this:

*** ERROR[13065] End of file was found after host variable expression when : was expected, near line 54.

Solution

Correct the syntax and resubmit

Leave A Reply

Your email address will not be published. Required fields are marked *

You May Also Like

In this blog post, let’s learn about the client error message “EngineNotSupported with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022
In this blog post, let’s learn about the client error message “EngineVersionNotSupported with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022
In this blog post, let’s learn about the client error message “IncorrectDBClusterLockMode with HTTP Status 400” when working with PolarDB...
  • Data
  • December 15, 2022