By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,514 Members | 1,693 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,514 IT Pros & Developers. It's quick & easy.

Modifying DB2 Profiles/Config files

P: n/a
Hello,

I have had a lot of problems installing a DB2 v8.1 Personal Edition on
a RHEL4. Solved most of them by using a JDK-1.4.1 instead of the
default 1.3.1, which comes with DB2. But I still have two problems,
and I think they have something in common:

1) an instance was created during the installation. I am trying to add
a new instance by using: "/opt/IBM/db2/V8.1/instance/db2icrt -d -a
server -s ese -u db2fenc1 db2inst2", and this fails in the set_cfgfile
routine. The debug looks like:

+ set_cfgfile
+ trac set_cfgfile
+ '[' 0 -eq 0 ']'
+ echo '## call function set_cfgfile'
+ tee -a /tmp/db2icrt.log.4581
## call function set_cfgfile
+ set -x
+ '[' ese = EEE -o ese = eee ']'
+ '[' ese = EE -o ese = ee ']'
+ '[' ese = ESE -o ese = ese ']'
+ CFGFILE=db2sysmp
+ '[' '!' -f /opt/IBM/db2/V8.1/cfg/db2sysmp ']'
+ trax set_cfgfile
+ '[' 0 -eq 0 ']'
+ echo '## exit function set_cfgfile'

Indeed, there isn't such a file "/opt/IBM/db2/V8.1/cfg/db2sysmp". In
that directory, there are two files starting with "db2sys": "db2sysrq"
and "db2syssr". When copying one of these "profile" files to
"db2sysmp", the instance is created. The question is: why wasn't a
profile file for ESE/WSE set up from the very beginning by the
installation process?

2) whenever I create a new instance, or try to use the instance
created during the installation, a lot of tools like "db2ca", "db2cc",
etc. don't work because:

sh: /opt/IBMJava2-131/jre/bin/java: No such file or directory
DB2JAVIT : RC = 127

This "IBMJava2-131" seems to be hardcoded in many utilities. The DB2
installation used a "IBMJava2-141" JVM, there wasn't/isn't any "131"
on the disk.

I can update the "JDK_PATH" pro database manager, and then the
instance tools "db2cc", "db2ca", etc. work. But when creating new
instances, they inherit the old IBMJava2-131 path.

What's even more interesting, this "hardcored path" IBMJava2-131
appears in both "profiles" files mentioned above, "db2sysrq" and
"db2syssr". How can one modify/generate this sort of profile files,
and modify variables like "JDK_PATH" at the "DB2 Installation" level
(as opposed to "DB2 Instance/DBM level")?

Thank you,
Bogdan

Oct 18 '07 #1
Share this Question
Share on Google+
1 Reply


P: n/a
bo*********@gmail.com wrote:
Hello,

I have had a lot of problems installing a DB2 v8.1 Personal Edition on
a RHEL4. Solved most of them by using a JDK-1.4.1 instead of the
default 1.3.1, which comes with DB2. But I still have two problems,
and I think they have something in common:

1) an instance was created during the installation. I am trying to add
a new instance by using: "/opt/IBM/db2/V8.1/instance/db2icrt -d -a
server -s ese -u db2fenc1 db2inst2", and this fails in the set_cfgfile
routine. The debug looks like:
You have personal edition, you claim. So why are you trying to create a wse
(or even ese) instance? Just leave the "-s" flag out of your command
altogether (with the 'ese' parameter). That should solve that problem.

db2icrt defaults to the "largest" available instance type. If you have ESE
installed, it defaults to ESE. If you have WSE or Express installed, it
defaults to that type (Express uses the WSE instance type). Similarly
Personal Edition uses the "standalone" type (which doesn't have a -s flag
option on Linux, you need to use the default), and clients use the "client"
type.
Indeed, there isn't such a file "/opt/IBM/db2/V8.1/cfg/db2sysmp". In
There shouldn't be ... unless you have ESE installed.
that directory, there are two files starting with "db2sys": "db2sysrq"
and "db2syssr". When copying one of these "profile" files to
"db2sysmp", the instance is created. The question is: why wasn't a
profile file for ESE/WSE set up from the very beginning by the
installation process?
Because you don't have ESE or WSE installed?
2) whenever I create a new instance, or try to use the instance
created during the installation, a lot of tools like "db2ca", "db2cc",
etc. don't work because:

sh: /opt/IBMJava2-131/jre/bin/java: No such file or directory
DB2JAVIT : RC = 127

This "IBMJava2-131" seems to be hardcoded in many utilities. The DB2
installation used a "IBMJava2-141" JVM, there wasn't/isn't any "131"
on the disk.
The default for v8.1 is Java 1.3 because Java 1.4 didn't exist at the time.
You should upgrade to v8.2, that should change the default.
I can update the "JDK_PATH" pro database manager, and then the
instance tools "db2cc", "db2ca", etc. work. But when creating new
instances, they inherit the old IBMJava2-131 path.

What's even more interesting, this "hardcored path" IBMJava2-131
appears in both "profiles" files mentioned above, "db2sysrq" and
"db2syssr". How can one modify/generate this sort of profile files,
and modify variables like "JDK_PATH" at the "DB2 Installation" level
(as opposed to "DB2 Instance/DBM level")?
As far as I'm aware, you can't. These are instance variables, and there is
no global version of these variables to use.
Oct 20 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.