Graphic data and graphic functions not supported for DB2

db2user · #1 (**permalink**) 12-05-07, 19:29

Hello,

I'm working on a 64 bit DB2 UDB database on Linux and keep getting this error when I run the db2look command:

SQL1216N Graphic data and graphic functions are not supported for this
database.

Any idea how I can enable this? I don't have this problem on our other db servers. I find the db2look command very useful so would be great if anyone can help!

Thanks!

sivaswami · #2 (**permalink**) 12-06-07, 08:27

Hope the db does not supports Vargraphic data types.

Quote:

Originally Posted by db2user

Hello,

I'm working on a 64 bit DB2 UDB database on Linux and keep getting this error when I run the db2look command:

SQL1216N Graphic data and graphic functions are not supported for this
database.

Any idea how I can enable this? I don't have this problem on our other db servers. I find the db2look command very useful so would be great if anyone can help!

Thanks!

n_i · #3 (**permalink**) 12-06-07, 11:10

Code:

SQL1216N Graphic data and graphic functions are not supported
          for this database.

Explanation:

The code page of the database does not support graphic data.  The
data types GRAPHIC, VARGRAPHIC, and LONG VARGRAPHIC are not valid
for this database.  The GRAPHIC literal and the VARGRAPHIC scalar
functions are not valid for this database.

 The statement cannot be processed.

 Federated system users: this situation can also be detected by
the data source.

Looks like you will have to re-create the database with the proper codepage.

db2user · #4 (**permalink**) 12-06-07, 15:44

Looks like you will have to re-create the database with the proper codepage.

What does this mean? How do I know if I'm using the proper codepage?

Is there an add on I can install... or do I really have to recreate the db? Thanks!

stolze · #5 (**permalink**) 12-06-07, 16:03

We have no idea what you try to do. Could you explain to us what your situation is? Do you want to run db2look on an existing database to extract DDL and then get the error? Or did you already extract DDL from somewhere else and try to apply it to another database? Please show us exactly the statements/commands you try to execute.

db2user · #6 (**permalink**) 12-06-07, 16:32

Hi,

Yes, I want to run db2look on an existing database to extract DDL and then get the error.. here's the output :

db2look -d db1 -e -x -t contact -o contact.ddl
-- No userid was specified, db2look tries to use Environment variable USER
-- USER is: DBINST1
-- The db2look utility will consider only the specified tables
-- Creating DDL for table(s)
-- Output is sent to file: contact.ddl
SQL1216N Graphic data and graphic functions are not supported for this
database. SQLSTATE=56031

Any thoughts? Thx!

db2user · #7 (**permalink**) 12-10-07, 02:05

Another thing I noticed is that the table I'm running the db2look command on doesn't have the varchar graphic data type...only varchar. How do I make sure that the codepage will support the command? How do I do this? Thanks!

stolze · #8 (**permalink**) 12-10-07, 09:13

Hmm... looks strange to me. What did you find in the db2diag output for the time when db2look is run (with DIAGLEVEL set to 4)?

If you can't find anything helpful there, you should open a PMR with IBM support.

db2user · #9 (**permalink**) 12-11-07, 18:13

Hello,

Didn't find anything helpful there...I found this on another posting somewhere though :

Setting UTF-16 encoding option solved the problem.

How do I set this option? Does anyone know.. the OP didn't go into any detail about this...also found this :

Usually, no one uses UTF-16 to store data in DB2. You
could use a regular UTF-8 database with normal VARCHAR/CHAR data types and
store non-ASCII data in UTF-8.

How can I check this? Any other thoughts? Thx!

stolze · #10 (**permalink**) 12-12-07, 06:47

VARGRAPHIC data types are for UTF-16.

I have no further idea. So you should open a PMR with IBM support as I suggested.

db2user · #11 (**permalink**) 12-13-07, 00:27

Thanks for the reply stolze. Yes, the problem is really strange... the machine we were working on had a lot of other issues as well...so the full image will be redone.. thanks for the help..

db2user · #12 (**permalink**) 12-14-07, 00:12

Hi, just thought I'd let you know that the issue was due to the locale being set wrong on the machine. It's all fixed now. Thanks for the replies...you all are very helpful!

Internet Services

Web Development

Digital Marketing

Consumer Tech