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

SQL1337N The service "db2inst1" was not found.

P: n/a
Hi:

I am trying to connect to DB with the following command
db2 connect to <dbnameuser <usernameusing <password>

It throws the following exception
SQL1337N The service "db2inst1" was not found.

I checked the /etc/services file also, it has entry in it. Any idea how
to resolve this?

Thanks in Advance
Ganesh

Aug 22 '06 #1
Share this Question
Share on Google+
9 Replies


P: n/a
In article <11**********************@74g2000cwt.googlegroups. com>,
ga********@gmail.com says...
Hi:

I am trying to connect to DB with the following command
db2 connect to <dbnameuser <usernameusing <password>

It throws the following exception
SQL1337N The service "db2inst1" was not found.

I checked the /etc/services file also, it has entry in it. Any idea how
to resolve this?

Thanks in Advance
Ganesh

Maybe the instance owner is not allowed to read the /etc/services file?
Aug 22 '06 #2

P: n/a
The user has read privilage to /etc/services. I am able to attach to
the instance, start and stop the db server. The problem is while
connecting to db. I also changed the port number and tried it out.
still the problem persists.

Thanks
Ganesh
Gert van der Kooij wrote:
In article <11**********************@74g2000cwt.googlegroups. com>,
ga********@gmail.com says...
Hi:

I am trying to connect to DB with the following command
db2 connect to <dbnameuser <usernameusing <password>

It throws the following exception
SQL1337N The service "db2inst1" was not found.

I checked the /etc/services file also, it has entry in it. Any idea how
to resolve this?

Thanks in Advance
Ganesh

Maybe the instance owner is not allowed to read the /etc/services file?
Aug 22 '06 #3

P: n/a
In article <11**********************@m73g2000cwd.googlegroups .com>,
ga********@gmail.com says...
The user has read privilage to /etc/services. I am able to attach to
the instance, start and stop the db server. The problem is while
connecting to db. I also changed the port number and tried it out.
still the problem persists.
Maybe the db2diag file gives you some more info?
Aug 22 '06 #4

P: n/a
Can i send the details your personal email -id?

-Ganesh

Gert van der Kooij wrote:
In article <11**********************@m73g2000cwd.googlegroups .com>,
ga********@gmail.com says...
The user has read privilage to /etc/services. I am able to attach to
the instance, start and stop the db server. The problem is while
connecting to db. I also changed the port number and tried it out.
still the problem persists.

Maybe the db2diag file gives you some more info?
Aug 22 '06 #5

P: n/a
In article <11**********************@h48g2000cwc.googlegroups .com>,
ga********@gmail.com says...
Can i send the details your personal email -id?

-Ganesh

Gert van der Kooij wrote:
In article <11**********************@m73g2000cwd.googlegroups .com>,
ga********@gmail.com says...
The user has read privilage to /etc/services. I am able to attach to
the instance, start and stop the db server. The problem is while
connecting to db. I also changed the port number and tried it out.
still the problem persists.
>
Maybe the db2diag file gives you some more info?
It shouldn't be that much info so it's better to post it to the group.
Others can jump into the problem also.
Aug 22 '06 #6

P: n/a
db2diag is follows:
2006-08-22-14.33.17.706017+300 I5916580C354 LEVEL: Severe
PID : 569366 TID : 1 PROC : db2hmon 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, routine_infrastructure, sqlerFmpOneTimeInit,
probe:100
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0x2FF22650 : FFFF FBEE ....

2006-08-22-14.35.58.574759+300 I5916935C311 LEVEL: Event
PID : 569412 TID : 1 PROC : db2star2
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Instance_Memory" <automaticFrom: "4724" To:
"4724"

2006-08-22-14.35.58.593624+300 E5917247C920 LEVEL: Warning
PID : 569412 TID : 1 PROC : db2star2
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, LicCheckProcessors, probe:20
MESSAGE : ADM12017E The number of processors on this machine exceeds
the
defined entitlement of "1" for the product "DB2 Enterprise
Server
Edition". The number of processors on this machine is "2".
You should
purchase additional processor based entitlements from your
IBM
representative or authorized dealer and update your license
using the
License Center or the db2licm command line utility. For more
information on updating processor based licenses, refer to
the Quick
Beginnings manual for your platform. For more information on
the
db2licm utility, refer to the DB2 Command Reference.

2006-08-22-14.35.59.815986+300 I5918168C357 LEVEL: Warning
PID : 548880 TID : 1 PROC : db2spmrsy 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-6
FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80
MESSAGE : errno:
DATA #1 : Hexdump, 4 bytes
0x2FF19390 : 0000 0011 ....

2006-08-22-14.35.59.816564+300 I5918526C280 LEVEL: Warning
PID : 548880 TID : 1 PROC : db2spmrsy 0
INSTANCE: db2inst1 NODE : 000
APPHDL : 0-6
MESSAGE : Path/Filename
DATA #1 : String, 38 bytes
/u02/db2inst1/sqllib/spmlog/SPMLOG.LCF

2006-08-22-14.35.59.867674+300 E5918807C973 LEVEL: Event
PID : 569412 TID : 1 PROC : db2star2
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911
MESSAGE : ADM7513W Database manager has started.
START : DB2 DBM
DATA #1 : Build Level, 124 bytes
Instance "db2inst1" uses "32" bits and DB2 code release "SQL08020"
with level identifier "03010106".
Informational tokens are "DB2 v8.1.1.64", "s040812", "U498350", FixPak
"7".
DATA #2 : System Info, 184 bytes
System: AIX arrow 3 5 0058241F4C00
CPU: total:2 online:2
Physical Memory: total:4096 free:2481
Virtual Memory: total:10624 free:8999
Swap Memory: total:6528 free:6518
Kernel Params: msgMaxMessageSize:4194304 msgMaxQueueSize:4194304
shmMax:2147483648 shmMin:1 shmIDs:131072
shmSegments:16
semIDs:131072 semNumPerID:65535 semOps:1024
semMaxVal:32767
semAdjustOnExit:16384

Any idea?
Gert van der Kooij wrote:
In article <11**********************@h48g2000cwc.googlegroups .com>,
ga********@gmail.com says...
Can i send the details your personal email -id?

-Ganesh

Gert van der Kooij wrote:
In article <11**********************@m73g2000cwd.googlegroups .com>,
ga********@gmail.com says...
The user has read privilage to /etc/services. I am able to attach to
the instance, start and stop the db server. The problem is while
connecting to db. I also changed the port number and tried it out.
still the problem persists.

>
Maybe the db2diag file gives you some more info?

It shouldn't be that much info so it's better to post it to the group.
Others can jump into the problem also.
Aug 22 '06 #7

P: n/a
In article <11**********************@h48g2000cwc.googlegroups .com>,
ga********@gmail.com says...
Any idea?
No. Maybe it helps when setting the diaglevel to 4, empty the db2diag
log and connect to the db to reproduce the error. Don't forget to set
diaglevel back to the original level.
Aug 22 '06 #8

P: n/a
Can u paste us these commands ?

1. Are u trying this connect statement from CLIENT ?

If yes

db2 list node directory
db2 list db directory

Looks like you have CATALOGED this node using the SVCENAME instead of
PORT number.

db2 "catalog tcpip node xxx remote <hostnameserver <portnumber"
db2 "catalog database at node xxx"

Then try again...

cheers...
Shashi Mannepalli

Gert van der Kooij wrote:
In article <11**********************@h48g2000cwc.googlegroups .com>,
ga********@gmail.com says...
Any idea?

No. Maybe it helps when setting the diaglevel to 4, empty the db2diag
log and connect to the db to reproduce the error. Don't forget to set
diaglevel back to the original level.
Aug 22 '06 #9

P: n/a
thank you. catalog done the trick.

- Ganesh

Shashi Mannepalli wrote:
Can u paste us these commands ?

1. Are u trying this connect statement from CLIENT ?

If yes

db2 list node directory
db2 list db directory

Looks like you have CATALOGED this node using the SVCENAME instead of
PORT number.

db2 "catalog tcpip node xxx remote <hostnameserver <portnumber"
db2 "catalog database at node xxx"

Then try again...

cheers...
Shashi Mannepalli

Gert van der Kooij wrote:
In article <11**********************@h48g2000cwc.googlegroups .com>,
ga********@gmail.com says...
Any idea?
No. Maybe it helps when setting the diaglevel to 4, empty the db2diag
log and connect to the db to reproduce the error. Don't forget to set
diaglevel back to the original level.
Aug 23 '06 #10

This discussion thread is closed

Replies have been disabled for this discussion.