-204 RETURN CODE

Raey

-204 RETURN CODE
I have executed the below SQL statement which resulted in -204 return
code. Please see the .sync points and the return codes in each of the SQL
statements.

Create table B ( VERSION INT NOT NULL,
OPRDEFNDESC CHAR(30) NOT NULL) in Z1XXABC.T1;

DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

Insert into table B as select * from table A;
DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

DROP TABLE A
;
DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION
.SYNC 00003
BPA0027I: SYNCPOINT TAKEN AND ALL WORK COMMITTED
RETCODE = 0

RENAME B TO A ;
DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

create unique index c on Table A (version) ;

DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

.SYNC 00004
BPA0027I: SYNCPOINT TAKEN AND ALL WORK COMMITTED
RETCODE = 0

Then, after a while I have tried to create
another index on table A, but I got -204 return code saying that
the table does not exit in DB2.

This is the third time my team runs into this scenarios.

We are in DB2 V8 COMPATABILITY Mode, and we are in CA/DB2 DB2 Tools (R11.5
SP0)

Can any one shade any light on this problem?

Thanks,

Ayalew "Mark"

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

David Seibert

Re: -204 RETURN CODE
(in response to Raey)
Hello Ayalew

Cam you post the full -204 msg ?

Sometimes there are -204 not found msgs on objects you don't expect.


Dave

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Ayalew "Mark" Kassa
Sent: Monday, January 08, 2007 9:40 PM
To: [login to unmask email]
Subject: [DB2-L] -204 RETURN CODE

I have executed the below SQL statement which resulted in -204 return
code. Please see the .sync points and the return codes in each of the
SQL statements.

Create table B ( VERSION INT NOT NULL,
OPRDEFNDESC CHAR(30) NOT NULL) in Z1XXABC.T1;

DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

Insert into table B as select * from table A; DSNT400I SQLCODE = 000,
SUCCESSFUL EXECUTION

DROP TABLE A
;
DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION .SYNC 00003
BPA0027I: SYNCPOINT TAKEN AND ALL WORK COMMITTED
RETCODE = 0

RENAME B TO A ;
DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

create unique index c on Table A (version) ;

DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

.SYNC 00004
BPA0027I: SYNCPOINT TAKEN AND ALL WORK COMMITTED
RETCODE = 0

Then, after a while I have tried to create another index on table A, but
I got -204 return code saying that the table does not exit in DB2.

This is the third time my team runs into this scenarios.

We are in DB2 V8 COMPATABILITY Mode, and we are in CA/DB2 DB2 Tools
(R11.5
SP0)

Can any one shade any light on this problem?

Thanks,

Ayalew "Mark"

------------------------------------------------------------------------
---------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm

The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

GANESH GOSAVI

Re: -204 RETURN CODE
(in response to David Seibert)
Check under which schema the table has got created. It must be d
Mark,

Check under which schema the table has got created. It must be different than which you are using your SQL statement. Your SQL statement might be refferening to that table with the CURRENT SCHEMA .

So try specifying the table name with the correct schema.

Thanks and Regards,
GANESH GOSAVI (IBM, Pune India Labs)

----- Original Message ----
From: "Ayalew "Mark" Kassa" <[login to unmask email]>
To: [login to unmask email]
Sent: Tuesday, 9 January, 2007 8:09:51 AM
Subject: [DB2-L] -204 RETURN CODE


I have executed the below SQL statement which resulted in -204 return
code. Please see the .sync points and the return codes in each of the SQL
statements.

Create table B ( VERSION INT NOT NULL,
OPRDEFNDESC CHAR(30) NOT NULL) in Z1XXABC.T1;

DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

Insert into table B as select * from table A;
DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

DROP TABLE A
;
DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION
.SYNC 00003
BPA0027I: SYNCPOINT TAKEN AND ALL WORK COMMITTED
RETCODE = 0

RENAME B TO A ;
DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

create unique index c on Table A (version) ;

DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

.SYNC 00004
BPA0027I: SYNCPOINT TAKEN AND ALL WORK COMMITTED
RETCODE = 0

Then, after a while I have tried to create
another index on table A, but I got -204 return code saying that
the table does not exit in DB2.

This is the third time my team runs into this scenarios.

We are in DB2 V8 COMPATABILITY Mode, and we are in CA/DB2 DB2 Tools (R11.5
SP0)

Can any one shade any light on this problem?

Thanks,

Ayalew "Mark"

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Send free SMS to your Friends on Mobile from your Yahoo! Messenger. Download Now! http://messenger.yahoo.com/download.php

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Steen Rasmussen

Re: -204 RETURN CODE
(in response to GANESH GOSAVI)
Hello Mark,

From what you posted, I cannot see if everything is done within one
Batch Processor script - or your second create index is happening in a
complete different session.

When you create the second index - are you trying to do this in a CA/DB2
session (e.g. RC/Update) or is it being created in a new session after
you exited the CA/DB2 products.

Can I contact you after 10am CDT Tuesday, so we can go through each step
in order to find out what is happening ????

Steen Rasmussen
CA
Senior Consultant DB2 tools
Tel : +1-630-505-6673 (US direct)
Tel : +1-815-274-9589 (US mobile)
Tel : +45-22 15 44 98 (Europe mobile)
[login to unmask email]


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Ayalew "Mark" Kassa
Sent: Monday, January 08, 2007 8:40 PM
To: [login to unmask email]
Subject: [DB2-L] -204 RETURN CODE

I have executed the below SQL statement which resulted in -204 return
code. Please see the .sync points and the return codes in each of the
SQL
statements.

Create table B ( VERSION INT NOT NULL,
OPRDEFNDESC CHAR(30) NOT NULL) in Z1XXABC.T1;

DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

Insert into table B as select * from table A;
DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

DROP TABLE A
;
DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION
.SYNC 00003
BPA0027I: SYNCPOINT TAKEN AND ALL WORK COMMITTED
RETCODE = 0

RENAME B TO A ;
DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

create unique index c on Table A (version) ;

DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

.SYNC 00004
BPA0027I: SYNCPOINT TAKEN AND ALL WORK COMMITTED
RETCODE = 0

Then, after a while I have tried to create
another index on table A, but I got -204 return code saying that
the table does not exit in DB2.

This is the third time my team runs into this scenarios.

We are in DB2 V8 COMPATABILITY Mode, and we are in CA/DB2 DB2 Tools
(R11.5
SP0)

Can any one shade any light on this problem?

Thanks,

Ayalew "Mark"

------------------------------------------------------------------------
---------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Raey

Re: -204 RETURN CODE
(in response to Steen Rasmussen)
Steen,

I
I have tried to create the index using CA’s batch processor. I have created the table about 10 AM Eastern Standard time, and tried to create the index, which resulted -204 around 4 PM. I am using the same schema name in the create index and create table statement.

Unfortunately, I am not at work this week so we will not be able to talk.

Thanks,

"Rasmussen, Steen" <[login to unmask email]> wrote:
Hello Mark,

From what you posted, I cannot see if everything is done within one
Batch Processor script - or your second create index is happening in a
complete different session.

When you create the second index - are you trying to do this in a CA/DB2
session (e.g. RC/Update) or is it being created in a new session after
you exited the CA/DB2 products.

Can I contact you after 10am CDT Tuesday, so we can go through each step
in order to find out what is happening ????

Steen Rasmussen
CA
Senior Consultant DB2 tools
Tel : +1-630-505-6673 (US direct)
Tel : +1-815-274-9589 (US mobile)
Tel : +45-22 15 44 98 (Europe mobile)
[login to unmask email]


-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email] On
Behalf Of Ayalew "Mark" Kassa
Sent: Monday, January 08, 2007 8:40 PM
To: [login to unmask email]
Subject: [DB2-L] -204 RETURN CODE

I have executed the below SQL statement which resulted in -204 return
code. Please see the .sync points and the return codes in each of the
SQL
statements.

Create table B ( VERSION INT NOT NULL,
OPRDEFNDESC CHAR(30) NOT NULL) in Z1XXABC.T1;

DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

Insert into table B as select * from table A;
DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

DROP TABLE A
;
DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION
.SYNC 00003
BPA0027I: SYNCPOINT TAKEN AND ALL WORK COMMITTED
RETCODE = 0

RENAME B TO A ;
DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

create unique index c on Table A (version) ;

DSNT400I SQLCODE = 000, SUCCESSFUL EXECUTION

.SYNC 00004
BPA0027I: SYNCPOINT TAKEN AND ALL WORK COMMITTED
RETCODE = 0

Then, after a while I have tried to create
another index on table A, but I got -204 return code saying that
the table does not exit in DB2.

This is the third time my team runs into this scenarios.

We are in DB2 V8 COMPATABILITY Mode, and we are in CA/DB2 DB2 Tools
(R11.5
SP0)

Can any one shade any light on this problem?

Thanks,

Ayalew "Mark"

------------------------------------------------------------------------
---------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and
home page at http://www.idugdb2-l.org/archives/db2-l.html. From that
page select "Join or Leave the list". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. The IDUG List Admins can be reached at
[login to unmask email] Find out the latest on IDUG conferences
at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm


---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm