SQL error

Raj

i get this error SQL30020N when selecting data from a table . I
altered this table earlier today when i do it a select * from the table
query runs OK, but when i join this table with 10 other tables (in a
scheduled job) i get this error. The job has been running fine untill
we added this new column, it runs fine if i don't include this column.
The new column added is a date column with a default value.Any help
greatly appreciated
error SQL30020N no return code, reason code 1, the select returns 2
rows and the second row has all garbled characters..
Thanks..

Apr 28 '06 #1

Mark A

"Raj" <sp****@yahoo.com> wrote in message
news:11**********************@i40g2000cwc.googlegr oups.com...

i get this error SQL30020N when selecting data from a table . I
altered this table earlier today when i do it a select * from the table
query runs OK, but when i join this table with 10 other tables (in a
scheduled job) i get this error. The job has been running fine untill
we added this new column, it runs fine if i don't include this column.
The new column added is a date column with a default value.Any help
greatly appreciated
error SQL30020N no return code, reason code 1, the select returns 2
rows and the second row has all garbled characters..
Thanks..

Check the messages and codes manual for that error code.

Apr 28 '06 #2

Visu

This might help

http://www-1.ibm.com/support/docview...id=swg1IY47935

Apr 28 '06 #3

Mehmet Baserdem

Raj,

When you use a different username & passwd combination for the
scheduled job, are you getting the same SQL error?

regards,

Mehmet

Apr 28 '06 #4

Raj

Visu,
We are on a V8 client, The SQL works fine if i don't include the new
column in the SQL...

Mehmet ,
I have tried running it using couple of user id's ... there is no
difference

Also, select * from the tables work fine, so the data is good.

Apr 28 '06 #5

Raj

This is all i have in the manual...
SQL30020N Execution failed because of a Distributed Protocol
Error that will affect the successful execution of
subsequent commands and SQL statements: Reason Code
"<reason-code(subcode)>".

Explanation:

A system error occurred that prevented successful execution of
the current environment command or SQL statement, as well as any
subsequent commands or SQL statements.

The subcode, when nonzero, consist of two bytes such that the
high-order byte indicates the site at which the error was
detected. This is X'01' if the error was detected by the local
DB2 server. It is X'02' if the error was detected by the remote
server. The low-order byte is an error code specific to the
reason code.

Reason code 124C indicates that the DRDA data stream for the
request contains a syntax error.

The command or statement cannot be processed. The current
transaction is rolled back and the application is disconnected
from the remote database.

User Response:

Record the message number (SQLCODE) and the reason code. Record
all error information from the SQLCA, if possible. Attempt to
connect the remote database and rerun the application.

If sufficient memory resources exist and the problem continues,
invoke the Independent Trace Facility at the operating system
command prompt.

Required information:

o Problem description

o SQLCODE and reason code

o SQLCA contents if possible

o Trace file if possible.

Some possible reason codes include:
121C Indicates that the user is not authorized to perform the
requested command.

1232 The command could not be completed because of a permanent
error. In most cases, the server will be in the process of an
abend.

1254 A command sent from the client has resulted in an
unarchitected and implementation specific condition on the remote
server for which there is no architected message to return to the
client.

If the remote server is DB2 UDB for OS/390,zOS then check the
console log for information about this error.

If the remote server is DB2 UDB for iSeries, the job log of the
server job, and/or a first failure data capture (FFDC) spooled
file is usually necessary to determine the cause of the error.

If the remote server is DB2 UDB for Unix/Windows then check the
remote database server's administration notification log for
information regarding this error.

220A The target server has received an invalid data description.
If a user SQLDA is specified, ensure that the fields are
initialized correctly. Also, ensure that the length does not
exceed the maximum allowed length for the data type being used.

If you are using the DB2 Connect product in a gateway server
environment with downlevel clients, this error may occur if your
application's host variables and the queried table's column
descriptions do not match.

sqlcode : -30020

sqlstate : 58009

Apr 28 '06 #6