Installed client V9.5 on Linux --> file access error
in [DB2]
|
Prev: Huge overhead of federation server: can it be improved
Next: How to roll-out old data in V8 EEE, migrated to V9.5 is not an option
From: danfan46 on 26 May 2010 17:09 Hi! I have installed version 9.5.5 of db2 runtime client. I previously had 9.1 server installed. drop the old instance and recreated a new. I have cataloged remote nodes and databases and can connect and access databases from the command line. When I try to compile a COBOL-program with Microfocus cob32 compiler ( 64-bit not supported) it fails with sql5005 and I get os open errors in db2diag.log releated to .../sqllib/db2systm 2010-05-26-22.43.28.922201+120 E2815G534 LEVEL: Warning (OS) PID : 10226 TID : 4157310656 PROC : cobchecker32 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80 MESSAGE : ZRC=0x840F0001=-2079391743=SQLO_ACCD "Access Denied" DIA8701C Access denied for resource "", operating system return code was "". CALLED : OS, -, open OSERR: EACCES (13) DATA #1 : File name, 30 bytes /home/db2inst1/sqllib/db2systm 2010-05-26-22.43.28.922959+120 I3350G359 LEVEL: Error PID : 10226 TID : 4157310656 PROC : cobchecker32 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, config/install, sqlf_fix_dbm_cfg, probe:10 MESSAGE : SQL5005: sqloopen rc = DATA #1 : Hexdump, 4 bytes 0xFFFFCBD8 : 0100 0F84 .... 2010-05-26-22.43.28.923089+120 I3710G261 LEVEL: Error PID : 10226 TID : 4157310656 PROC : cobchecker32 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, config/install, sqlfcsys, probe:110 RETCODE : ZRC=0xFFFFEC73=-5005 2010-05-26-22.43.28.923239+120 I3972G341 LEVEL: Error PID : 10226 TID : 4157310656 PROC : cobchecker32 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0 MESSAGE : bytesr DATA #1 : Hexdump, 4 bytes 0xFFFFCC28 : 0010 0000 .... 2010-05-26-22.43.28.923378+120 I4314G345 LEVEL: Error PID : 10226 TID : 4157310656 PROC : cobchecker32 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0 MESSAGE : ptr->release DATA #1 : Hexdump, 2 bytes 0xF6BEACDC : 000C .. 2010-05-26-22.43.28.923484+120 I4660G346 LEVEL: Error PID : 10226 TID : 4157310656 PROC : cobchecker32 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0 MESSAGE : ptr->chksum DATA #1 : Hexdump, 4 bytes 0xF6BEACCC : 1723 0000 .#.. 2010-05-26-22.43.28.923589+120 I5007G353 LEVEL: Error PID : 10226 TID : 4157310656 PROC : cobchecker32 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0 MESSAGE : ptr->dbm_cfg_version DATA #1 : Hexdump, 2 bytes 0xF6BEACE0 : 8C23 .# 2010-05-26-22.43.28.923693+120 I5361G372 LEVEL: Error PID : 10226 TID : 4157310656 PROC : cobchecker32 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0 MESSAGE : dbm config DATA #1 : Dumped object of size 4096 bytes at offset 0, 49 bytes /home/db2inst1/sqllib/db2dump/102264157310656.000 2010-05-26-22.43.28.923910+120 E5734G424 LEVEL: Warning (OS) PID : 10226 TID : 4157310656 PROC : cobchecker32 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, oper system services, sqloclose, probe:20 MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found." DIA8411C A file "" could not be found. CALLED : OS, -, close OSERR: EBADF (9) 2010-05-26-22.43.28.924104+120 I6159G319 LEVEL: Severe PID : 10226 TID : 4157310656 PROC : cobchecker32 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, config/install, sqlf_alert, probe:1 DATA #1 : Hexdump, 4 bytes 0xFFFFCC58 : 73EC FFFF s... 2010-05-26-22.43.28.924212+120 I6479G260 LEVEL: Severe PID : 10226 TID : 4157310656 PROC : cobchecker32 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, config/install, sqlfcsys, probe:1 RETCODE : ZRC=0xFFFFEC73=-5005 2010-05-26-22.43.28.924350+120 I6740G344 LEVEL: Severe PID : 10226 TID : 4157310656 PROC : cobchecker32 INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, probe:30 DATA #1 : Hexdump, 4 bytes 0xFFFFCFB8 : 73EC FFFF Any idea - been googling but no luck so far. I must fix this tonight or try to revert to 9.1 /dg
From: danfan46 on 26 May 2010 17:19 danfan46 wrote: > Hi! > > I have installed version 9.5.5 of db2 runtime client. > I previously had 9.1 server installed. drop the old instance and > recreated a new. > > I have cataloged remote nodes and databases and can connect and access > databases from the command line. > > When I try to compile a COBOL-program with Microfocus cob32 compiler ( > 64-bit not supported) it fails with sql5005 > and I get os open errors in db2diag.log releated to .../sqllib/db2systm > > 2010-05-26-22.43.28.922201+120 E2815G534 LEVEL: Warning (OS) > PID : 10226 TID : 4157310656 PROC : cobchecker32 > INSTANCE: db2inst1 NODE : 000 > FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80 > MESSAGE : ZRC=0x840F0001=-2079391743=SQLO_ACCD "Access Denied" > DIA8701C Access denied for resource "", operating system > return code > was "". > CALLED : OS, -, open OSERR: EACCES (13) > DATA #1 : File name, 30 bytes > /home/db2inst1/sqllib/db2systm > > 2010-05-26-22.43.28.922959+120 I3350G359 LEVEL: Error > PID : 10226 TID : 4157310656 PROC : cobchecker32 > INSTANCE: db2inst1 NODE : 000 > FUNCTION: DB2 UDB, config/install, sqlf_fix_dbm_cfg, probe:10 > MESSAGE : SQL5005: sqloopen rc = > DATA #1 : Hexdump, 4 bytes > 0xFFFFCBD8 : 0100 0F84 .... > > 2010-05-26-22.43.28.923089+120 I3710G261 LEVEL: Error > PID : 10226 TID : 4157310656 PROC : cobchecker32 > INSTANCE: db2inst1 NODE : 000 > FUNCTION: DB2 UDB, config/install, sqlfcsys, probe:110 > RETCODE : ZRC=0xFFFFEC73=-5005 > > 2010-05-26-22.43.28.923239+120 I3972G341 LEVEL: Error > PID : 10226 TID : 4157310656 PROC : cobchecker32 > INSTANCE: db2inst1 NODE : 000 > FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0 > MESSAGE : bytesr > DATA #1 : Hexdump, 4 bytes > 0xFFFFCC28 : 0010 0000 .... > > 2010-05-26-22.43.28.923378+120 I4314G345 LEVEL: Error > PID : 10226 TID : 4157310656 PROC : cobchecker32 > INSTANCE: db2inst1 NODE : 000 > FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0 > MESSAGE : ptr->release > DATA #1 : Hexdump, 2 bytes > 0xF6BEACDC : 000C .. > > 2010-05-26-22.43.28.923484+120 I4660G346 LEVEL: Error > PID : 10226 TID : 4157310656 PROC : cobchecker32 > INSTANCE: db2inst1 NODE : 000 > FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0 > MESSAGE : ptr->chksum > DATA #1 : Hexdump, 4 bytes > 0xF6BEACCC : 1723 0000 .#.. > > 2010-05-26-22.43.28.923589+120 I5007G353 LEVEL: Error > PID : 10226 TID : 4157310656 PROC : cobchecker32 > INSTANCE: db2inst1 NODE : 000 > FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0 > MESSAGE : ptr->dbm_cfg_version > DATA #1 : Hexdump, 2 bytes > 0xF6BEACE0 : 8C23 .# > > 2010-05-26-22.43.28.923693+120 I5361G372 LEVEL: Error > PID : 10226 TID : 4157310656 PROC : cobchecker32 > INSTANCE: db2inst1 NODE : 000 > FUNCTION: DB2 UDB, trace services, sqlt_logerr_data, probe:0 > MESSAGE : dbm config > DATA #1 : Dumped object of size 4096 bytes at offset 0, 49 bytes > /home/db2inst1/sqllib/db2dump/102264157310656.000 > > 2010-05-26-22.43.28.923910+120 E5734G424 LEVEL: Warning (OS) > PID : 10226 TID : 4157310656 PROC : cobchecker32 > INSTANCE: db2inst1 NODE : 000 > FUNCTION: DB2 UDB, oper system services, sqloclose, probe:20 > MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found." > DIA8411C A file "" could not be found. > CALLED : OS, -, close OSERR: EBADF (9) > > 2010-05-26-22.43.28.924104+120 I6159G319 LEVEL: Severe > PID : 10226 TID : 4157310656 PROC : cobchecker32 > INSTANCE: db2inst1 NODE : 000 > FUNCTION: DB2 UDB, config/install, sqlf_alert, probe:1 > DATA #1 : Hexdump, 4 bytes > 0xFFFFCC58 : 73EC FFFF s... > > 2010-05-26-22.43.28.924212+120 I6479G260 LEVEL: Severe > PID : 10226 TID : 4157310656 PROC : cobchecker32 > INSTANCE: db2inst1 NODE : 000 > FUNCTION: DB2 UDB, config/install, sqlfcsys, probe:1 > RETCODE : ZRC=0xFFFFEC73=-5005 > > 2010-05-26-22.43.28.924350+120 I6740G344 LEVEL: Severe > PID : 10226 TID : 4157310656 PROC : cobchecker32 > INSTANCE: db2inst1 NODE : 000 > FUNCTION: DB2 UDB, base sys utilities, sqleInitApplicationEnvironment, > probe:30 > DATA #1 : Hexdump, 4 bytes > 0xFFFFCFB8 : 73EC FFFF > > > Any idea - been googling but no luck so far. > > I must fix this tonight or try to revert to 9.1 > > /dg I forget to mention that the file has attributes -rw-rw-r-- 1 db2inst1 db2iadm1 4096 May 26 22:41 db2systm /dg
From: Helmut Tessarek on 26 May 2010 18:19 Hi, On 26.05.10 17:09 , danfan46 wrote: > I have installed version 9.5.5 of db2 runtime client. > I previously had 9.1 server installed. drop the old instance and > recreated a new. I'm a little bit confused. According to your text you have replaced 9.1 server with 9.5 runtime client. Can you please be a bit more specific with your description of the environment? One machine, two machines? server/client levels. OS. bitwidth. > I have cataloged remote nodes and databases and can connect and access > databases from the command line. it would help, if you either posted the commands or the output of 'db2 list node directory' and 'db2 list db directory'. > When I try to compile a COBOL-program with Microfocus cob32 compiler ( > 64-bit not supported) it fails with sql5005 > and I get os open errors in db2diag.log releated to .../sqllib/db2systm Those errors seem to be a side effect of something else. I'm not familiar with the cobol compiler, so please help me out a little bit. Does cobchecker32 try to read db2systm? This is kind of strange, since this is an db2 internal binary file and I don't think that non DB2 products can understand this file. Which user are you using to compile the program? Can this user access db2systm? -- Helmut K. C. Tessarek DB2 Performance and Development /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */
From: danfan46 on 26 May 2010 20:30 Helmut Tessarek wrote: > Hi, > > On 26.05.10 17:09 , danfan46 wrote: >> I have installed version 9.5.5 of db2 runtime client. >> I previously had 9.1 server installed. drop the old instance and >> recreated a new. > > I'm a little bit confused. According to your text you have replaced 9.1 server > with 9.5 runtime client. > > Can you please be a bit more specific with your description of the environment? The environment is a Linux red hat 64-bit application server. Apps on this server talks to db2 databases on remote machines. Up to now we have had a full db2 install, but have not used any local databases lately. I wanted to upgrade from 9.1 to 9.5 and also reduce the footprint. > > One machine, two machines? server/client levels. OS. bitwidth. > >> I have cataloged remote nodes and databases and can connect and access >> databases from the command line. > > it would help, if you either posted the commands or the output of 'db2 list > node directory' and 'db2 list db directory'. > >> When I try to compile a COBOL-program with Microfocus cob32 compiler ( >> 64-bit not supported) it fails with sql5005 >> and I get os open errors in db2diag.log releated to .../sqllib/db2systm > > Those errors seem to be a side effect of something else. > I'm not familiar with the cobol compiler, so please help me out a little bit. > Does cobchecker32 try to read db2systm? This is kind of strange, since this is > an db2 internal binary file and I don't think that non DB2 products can > understand this file. > > Which user are you using to compile the program? Can this user access db2systm? > I finally db2idrop -ed to new db2inst1 of V9.5 and recreated the old 9.1 instance. Now the compilation works OK. I assume it is a Microfocus related problem. I'll open a PMR with them tomorrow. Perhaps I need to get a newer compiler version to match 9.5.5 Thanks for your support /dg
From: Helmut Tessarek on 26 May 2010 21:25
> The environment is a Linux red hat 64-bit application server. Apps on > this server talks to db2 > databases on remote machines. Up to now we have had a full db2 install, > but have not used any > local databases lately. I wanted to upgrade from 9.1 to 9.5 and also > reduce the footprint. If you are using a 64bit OS, the DB2 server instance can only be 64bit. But you can still use the 32bit libraries to link against. Only the client is supported to be 32bit on a 64bit system. But this was also true for 9.1, so in that case nothing should have changed for you. > I finally db2idrop -ed to new db2inst1 of V9.5 and recreated the old > 9.1 instance. > Now the compilation works OK. > I assume it is a Microfocus related problem. I'll open a PMR with them > tomorrow. > Perhaps I need to get a newer compiler version to match 9.5.5 Maybe they provide a 64bit version as well. I always try to get rid of bitwidth differences to exclude problems that arise in hybrid environments. Can you please post a short status update, if you find out that it was a compiler issue? -- Helmut K. C. Tessarek DB2 Performance and Development /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */ |