Db2move export and sql error

[Former Member]

During Db2move export:

• Table "SAPBW2 "."TCNVDATA": ERROR -3022. Check message file tab261.msg!

• SQLCODE: -3022 - SQLSTATE:

• SQL3022N An SQL error "-901" occurred while processing the SELECT string in the Action String parameter.

I can't see data into table with db2 select.

[Former Member]

Database was partially recovered.

[Former Member]

Hi Gianluca,

Could you please verify/provide the content of the tab261.msg file and the call of db2move. If the information available there is not enough to identify the cause of the problem, you could also take a look at the db2diag.log file of your instance, as you run the db2move command with the EXPORT option.

Regarding your two error messages, the error message -901 seems to be generic and the error message -3022 only states that there was an SQL error when procession the SELECT string of your EXPORT.

To get the complete error explanation of the message, you can run:

db2 "? SQL3022N"

db2 "? SQL0901N"

Best regards, Edgardo

[Former Member]

My problem was due a corruption of database, my index was broken.

I use db2 dart /mi databasename

and after I insert table space and pool about every index.

After I marked bad also table with db2dart bw2 /mt same things with id of table and table space.

Thanks for support.

Gianluca Vinco

Edited by: Gianluca Vinco on May 29, 2008 8:16 PM

[Former Member]

SQL0901N

The SQL statement failed because of a non-severe system error. Subsequent SQL statements can be processed. (Reason reason.)

Explanation:

An error has occurred which is due to a system error. Processing of the SQL statement has ended for reason reason (this is in English only and is useful only to IBM support personnel).

User response:

Record the message number (SQLCODE) and reason reason.

If trace was active, invoke the Independent Trace Facility at the operating system command prompt. Then contact your technical service representative with the following information:

• Problem description

• SQLCODE

• reason reason

• SQLCA contents if possible

• Trace file if possible.

Federated system users: isolate the problem to the data source failing the request (refer to the Troubleshooting Guide to determine which data source is failing to process the SQL statement) and take the necessary diagnostic steps for that data source. The problem determination procedures for data sources vary, so refer to the applicable data source manuals.

sqlcode: -901

*Post message file tab261.msg*