If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > How to set CODEPAGE to be a Global variable (on Linux) ?

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 09-22-04, 12:16
colmmagoo colmmagoo is offline
Registered User
 
Join Date: Aug 2004
Posts: 15
How to set CODEPAGE to be a Global variable (on Linux) ?

How do you set DB2CODEPAGE to be a global [g] variable ?

The following command, executed as db2inst1, sets DB2CODEPAGE to be an instance [i] variable:

db2set DB2CODEPAGE=1252

Thanks,
Colm.
Reply With Quote
  #2 (permalink)  
Old 09-22-04, 13:20
n_i n_i is offline
:-)
 
Join Date: Jun 2003
Location: Toronto, Canada
Posts: 4,449
db2set DB2CODEPAGE=1252 -g

Surprisingly, it's mentioned in the manual, right there, on page 203
Reply With Quote
  #3 (permalink)  
Old 09-22-04, 14:06
colmmagoo colmmagoo is offline
Registered User
 
Join Date: Aug 2004
Posts: 15
Surprisingly, that doesn't work for me. When I do db2set DB2CODEPAGE=1252 -g,
followed by db2set -all, I don't see DB2CODEPAGE listed in the output.
Reply With Quote
  #4 (permalink)  
Old 09-22-04, 18:42
n_i n_i is offline
:-)
 
Join Date: Jun 2003
Location: Toronto, Canada
Posts: 4,449
Could that be some kind of permission problem? You probably need to be an instance owner to change a global value. Also, do you issue the command at the server or while being connected remotely?
Reply With Quote
  #5 (permalink)  
Old 09-22-04, 20:54
colmmagoo colmmagoo is offline
Registered User
 
Join Date: Aug 2004
Posts: 15
It turned out to be a permissions issue. I issued the db2set command locally, as the instance owner (db2inst1 in this case), but the instance owner did not have permissions to write to the default.env file because they were not in the 'root' group. (default.env is created by root, I'm guessing, as part of installation). So either giving default.env world write permissions or adding db2inst1 to the root group works.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On