vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi All db2 version 8.2.2 Windows I have installed the database and created Sample db. Now when I am giving db2stop ,it says C:\Documents and Settings\buntyaru>db2stop 11/10/2005 00:13:14 0 0 SQL1025N The database manager was not stopped because databases are still active. SQL1025N The database manager was not stopped because databases are still active. I use db2stop force C:\Documents and Settings\buntyaru>db2stop force 11/10/2005 00:13:24 0 0 SQL1064N DB2STOP processing was successful. SQL1064N DB2STOP processing was successful. Then when I am giving db2start I am getting message C:\Documents and Settings\buntyaru>db2start SQL6030N START or STOP DATABASE MANAGER failed. Reason code "13". This is fourth time I am getting this error. On previous occasions I just reinstalled db2 and things went fine. But there should be some reason behind this. Can you guys help me out??? TIA Praveen |
| |||
| In article <ffaea04e08ce2c063765b8c6da7d2d11 @localhost.talkaboutdatabases.com>, Praveen_db2 (er_praveen278 @hotmail.com) says... > Then when I am giving db2start I am getting message > > C:\Documents and Settings\buntyaru>db2start > SQL6030N START or STOP DATABASE MANAGER failed. Reason code "13". > Use 'db2 ? sql6030n' to display the message text. Reason code 13 means 'No port value is defined for your DB2 instance id'. Check the docs at http://tinyurl.com/av7g9 For '/etc/services' read 'c:\windows\system32\drivers\etc\services' |
| ||||
| In article <84eae55974d4181b6c87cad9f0f98293 @localhost.talkaboutdatabases.com>, Praveen_db2 (er_praveen278 @hotmail.com) says... > Thanx Gert, > I restarted all the services of db2 and I was able to connect to the > db.But what I fail to understand is why is db2stop force affecting the > services. Is it that ,it kills my db2 service as well?? > > Praveen > > Yes, the db2stop command stops the service as well. As far as I know the force option forces all active connections offline and stops the instance. It looks like your TCPIP port was still in use after the 'db2stop force' command was finished but I don't know if this 'works as designed'. |