ALTER TABLE ALTER COLUMN

[Gregor Kova�]

Hi!

I have a table with a column of BIGINT and I want to change the type to
SMALLINT.
Command ALTER TABLE TABLE1 ALTER COLUMN COL1 SET DATA TYPE SMALLINT
does not work since I cannot specify SMALLINT in set data type clause
(acording to
http://publib.boulder.ibm.com/infoce...c/r0000888.htm)
Then I thought I could drop the column: ALTER TABLE TABLE1 DROP COLUMN COL1
but running this I get:
21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL0901N The SQL statement failed because of a non-severe system error.
Subsequent SQL statements can be processed. (Reason "column number out of
range".) SQLSTATE=58004

Is this as expected? :)) It doesn't sound like that to me.

Best regards,
Kovi

--
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
| In A World Without Fences Who Needs Gates? |
| Experience Linux. |
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

[Knut Stolze]

Gregor Kova� wrote:

Hi!

I have a table with a column of BIGINT and I want to change the type to
SMALLINT.
Command ALTER TABLE TABLE1 ALTER COLUMN COL1 SET DATA TYPE SMALLINT
does not work since I cannot specify SMALLINT in set data type clause
(acording to

http://publib.boulder.ibm.com/infoce...c/r0000888.htm)

Then I thought I could drop the column: ALTER TABLE TABLE1 DROP COLUMN
COL1 but running this I get:
21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL0901N The SQL statement failed because of a non-severe system error.
Subsequent SQL statements can be processed. (Reason "column number out of
range".) SQLSTATE=58004

SQL0901 -open a PMR with IBM support.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany

[Gregor Kova�]

Knut Stolze wrote:

Gregor Kova� wrote:

>Hi!

I have a table with a column of BIGINT and I want to change the type to
SMALLINT.
Command ALTER TABLE TABLE1 ALTER COLUMN COL1 SET DATA TYPE SMALLINT
does not work since I cannot specify SMALLINT in set data type clause
(acording to

http://publib.boulder.ibm.com/infoce...c/r0000888.htm)

>Then I thought I could drop the column: ALTER TABLE TABLE1 DROP COLUMN
COL1 but running this I get:
21034E Â*The command was processed as an SQL statement because it was not
a valid Command Line Processor command. Â*During SQL processing it
returned: SQL0901N Â*The SQL statement failed because of a non-severe
system error. Subsequent SQL statements can be processed. Â*(Reason
"column number out of range".) Â*SQLSTATE=58004

SQL0901 -open a PMR with IBM support.

Knut Stolze
DB2 Information Integration Development
IBM Germany

Thanks.
Does it mean that I should open a PMR every time I get SQL0901?

Best regards,
Kovi
--
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
| In A World Without Fences Who Needs Gates? |
| Experience Linux. |
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

[Knut Stolze]

Gregor Kova� wrote:

>>Then I thought I could drop the column: ALTER TABLE TABLE1 DROP COLUMN
COL1 but running this I get:
21034E Â*The command was processed as an SQL statement because it was not
a valid Command Line Processor command. Â*During SQL processing it
returned: SQL0901N Â*The SQL statement failed because of a non-severe
system error. Subsequent SQL statements can be processed. Â*(Reason
"column number out of range".) Â*SQLSTATE=58004

SQL0901 -open a PMR with IBM support.

Does it mean that I should open a PMR every time I get SQL0901?

My personal opinion: yes, do that. (Of course not for the same error
situation again and again.)

--
Knut Stolze
DB2 Information Integration Development
IBM Germany