cancel
Showing results for 
Search instead for 
Did you mean: 

SAP not starting up after restart

former_member1334776
Participant
0 Kudos
508

Dear all,

I am facing a issue that i cant start DB after restart.Un fortunately OS guys changed IP Again i changed to old IP. If i stsrat DB manually it is coming up ..

Checking required environment variables

R3trans -d:
SQL1063N  DB2START processing was successful.
Database activated
R3trans connect failed
This is R3trans version 6.22 (release 720 - 26.10.11 - 13:00:00).
unicode enabled version
2EETW169 no connect possible: "DBMS = DB6                              --- DB2DBDFT = 'KSM'"
R3trans finished (0012)

DB log:

DB2INSTANCE  is >db2ksm<
DB2DBDFT     is >KSM<

------------------------------ Fri Nov 23 15:51:32 IST 2012
Connect to the database to check the database state:

R3trans check finished with return code: 12
There is no database connect possible -
Database is probably already stopped.

Trans.log:
4 ETW000  [     dev trc,00000]  Info: successfully loaded DB2 library '/usr/sap/KSM/SYS/global/db6/LINUXX86_64/db6_clidriver/lib/libdb2.so'
4 ETW000                                                                                                  45  0.024611
4 ETW000  [     dev trc,00000]  Running with UTF-8 Unicode                                                16  0.024627
4 ETW000  [     dev trc,00000]  Running with CLI driver.                                                3632  0.028259
4 ETW000  [     dev trc,00000]  Fri Nov 23 15:37:11 2012                                              667365  0.695624
4 ETW000  [     dev trc,00000]  *** ERROR in DB6Connect[dbdb6.c, 1802] CON = 0 (BEGIN)                    21  0.695645
4 ETW000  [     dev trc,00000]  &+     DbSlConnectDB6( SQLConnect 😞 [IBM][CLI Driver] SQL30081N  A communication error has been detected. Communication
4 ETW000                                                                                                  28  0.695673
4 ETW000  [     dev trc,00000]  &+     protocol being used: "TCP/IP". Communication API being used: "SOCKETS".  Location where the error was detected: "
4 ETW000                                                                                                  22  0.695695
4 ETW000  [     dev trc,00000]  &+     0.0.0.0".  Communication function detecting the error: "connect".  Protocol specific error code(s): "111", "*", "*
4 ETW000                                                                                                  21  0.695716
4 ETW000  [     dev trc,00000]  &+     ".  SQLSTATE=08001                                                
4 ETW000                                                                                                  22  0.695738
4 ETW000  [     dev trc,00000]  &+                                                                       
4 ETW000                                                                                                  22  0.695760
4 ETW000  [     dev trc,00000]  &+                                                                       
4 ETW000                                                                                                  24  0.695784
4 ETW000  [     dev trc,00000]  &+                                                                       

4 ETW000                                                                                                  41  0.695825
4 ETW000  [     dev trc,00000]  *** ERROR in DB6Connect[dbdb6.c, 1802] (END)                              16  0.695841
4 ETW000  [    dbdb6.c ,00000]  *** ERROR => DbSlConnect to 'KSM' as 'sapksm' failed                      68  0.695909
2EETW169 no connect possible: "DBMS = DB6                              --- DB2DBDFT = 'KSM'"
                                                                                       107,2         95%


Thanks,
Thamodaran

Accepted Solutions (1)

Accepted Solutions (1)

premsukh_bishnoi
Employee
Employee
0 Kudos

Hi,

For these errors, could you please refer to the followings to see if
these could be helpful for this issue:

1,The remote database server has not been cataloged correctly at the
  client. Pls ensure the host entries are cataloged correctly.

2,The database manager configuration file at the server has not been
  configured properly with the proper communication parameters. Pls
  check the SVCENAME database manager configuration parameter,
  the TCP/IP service name or port number is unique.
  If database manager configuration parameters have been updated
  at the server, the database manager must be stopped for the changes
  to take effect. There might be a mismatch between the TCP/IP service
  name or port number specified on the server and on the client.
  Ensure the service name maps to the correct port number by checking
  the services file. You can check this by reading the services file
  or checking the output from running the command "netstat -a".

3,A firewall at the remote database server has prevented the connection
  from being established. Verify that the firewall is properly
  configured to accept connection requests from the client.

4,The DB2COMM environment variable at the server does not specify the
  communication protocol used by the client. Check that TCPIP has been
  specified. Issue db2set to see what has already been set. Run the
  command "db2set DB2COMM = TCPIP" to set the value.

5,Network failure, contact your network team. You can try a test
  with SAP tool niping as note 500235.

6. note 1364372

Regards, Premsukh

former_member1334776
Participant
0 Kudos

dear Premsukh,

As we are new to DB2 can you provide commands to execute in each step.

I Checked the connection in services it is working there

Thanks,

Thamodaran

premsukh_bishnoi
Employee
Employee
0 Kudos

Hi,

Please read  below  link:

all the commands are listed in notes.

For the error SQL30081N with RC 79 check the following link, please:
http://www-1.ibm.com/support/docview.wss?uid=swg21164785

Please ensure that the parameter SVCENAME (get dbm cfg) is set on your
db server according SAP Note 584952. This entry must be maintained in
the /etc/service file !
=> SVCENAME=<port number> or <service name>
=> SVCENAME=sapdb2<DBSID> (SAP Note 584952)

Ensure that DB2 environment variable DB2COMM (db2set -all) is set:
=> DB2COMM=TCPIP

Check the client(s):
=> db2 list db directory (to find the NODE name)
=> db2 list node directory (to find HOST/IP-address defined in host
file)

Now check the entries in files:
/etc/hosts
/etc/services

Please check also if server's port is opened by command:
telnet <hostname> <port>

Regards, Premsukh

Former Member
0 Kudos

Hi,

Please check the following

1) in /etc/hosts  -- file your new IP address ( as you mentioned unix team changed the IP )

2) Check dbcli.ini file in /usr/sap/KSM/SYS/global/db6 directory for the service for DB2 communication port info and check if IP address their for DB host. For example

; Comment lines start with a semi-colon.

[KSM]

Database=KSM

Protocol=tcpip

Hostname= check the hostname / ip

Servicename=5912

Also check the sercice entries in /etc/services file

sapdb2KSM               5912/tcp

Servicename in db2cli.ini file must be same as in /etc/service file

If non of these steps work, thean perform uncatelog and catelog your database port config.

Regards,

Dipam

Answers (0)