Since I use DB2, I have encountered several times a prompt SQL1032N error, and the error message is approximately as follows.
11/21/2004 22:15:33 0 0 0 SQL1042C unexpected system error.
SQL1032N does not issue a command to start the database manager. SQLSTATE = 57019.
Every time there is a problem, I have found a lot of information online, and I also asked many people, and I have a little effort to get it. The reasons and solutions for mistakes are not the same, and I only have a simple record. I always wanted to write them down, and it was convenient to meet the same problem. People who were looking for me everywhere, and I also wrote some nonsense. For example, how do I find mistakes, and even what is useless.
The first SQL1032N error is that the instance of DB2 is suddenly unable to start with DB2Start, and the following error message is probably:
12/30/2004 11:28:39 0 0 0 SQL1042C unexpected system errors.
SQL1032N does not issue a command to start the database manager. SQLSTATE = 57019.
I have encountered this problem for the first time, I thought it would not be a database, what is the urgent need? For example, activate the database only class, it will try trials, instances can't come, at the time, run these commands, definitely No.
Later, suddenly found that when the machine is turned on, it is prompted that there is a service error. It is not to start. It should be that the DB2 instance service that is set to automatically start in the Window service is not normal. I will start it in the service. mistake:
Windows cannot launch DB2-DB2-0 on the local computer. For more information, check the system event log. And refer to the specific service code -8000.
View Event Manager, have such a record:
DB2-DB2-0 service stops due to 4294959296 service errors. Source Service Control Events ID: 7024
I have done so much, all are useless, only to know that the service is gone, it is not looking for.
Afterwards, I later found the reason: License expired.
Run DB2LICM -L under the DB2CMD interface, it can be obvious that the license has expired.
I know the reason, the rest is that I want to solve this problem.
Summary: Until now, in some forums, I often see someone to send this post to ask, at least I have encountered three times in two months. Therefore, if it is not possible to determine that there is already a permanent authorization, this happens, use DB2LICM -L to check, it is not bad.
There is also a situation, similar to the previous
It is also a SQL1032N error that occurs when the instance is started. Unable to start DB2-DB0 service in Windows NT service, at the same time:
Error 1069, login failed error.
This error is relatively simple, is a username or password error used to start the service. Just in the properties of the service, choose the Login tab, select the user, and fill the password, and restart the service.
Summary: This situation, generally happens to switch the user to log in to the NT system or change the password of the DB2 user.
The third case is this:
At the beginning, it was a sudden DB2 client connection not server, prompting as follows:
C: / Documents and Settings / Administrator> DB2 Connect To fjdldw user install using install3211
SQL30081N detects a communication error. Communication protocols being used: "TCP / IP". Communication API: "Sockets" is being used. The location of the error was detected: "10.142.12.1". A communication function that detects an error: "Connect". Congregard
Special error code: "10061", "*", "*". SQLState = 08001
I have thought that it is really a TCP / IP protocol issue, and I went to find a lot of information related to SQL30081N errors, and I can't solve the problem. Later, I was checked on the server and found that the DB2 instance did not get up.
Use the db2start command, still prompt:
D: / Program QlliB / Bin> DB2Start
12/30/2004 11:28:39 0 0 0 SQL1042C unexpected system errors.
SQL1032N does not issue a command to start the database manager. SQLSTATE = 57019
Use DB2 Get DBM CFG to view the configuration file, because there is no other operation, there is no exception
View the db2diag.log file under the appropriate instance, pick the true useful part of the wrong log:
Failed to create the memory segment used for communication with fenced routines. If re-starting db2, ensure no db2fmp processes were on the instance prior to start. Otherwise, you can ajust by decreasing your ASLHEAPSZ setting this value through DB2_FMP_COMM_HEAPSZ db2set value, or.
Based on EnSure No DB2FMP Processes WERE on the instance prior to start, kill all DB2FMP processes in the task manager and then restart the instance. DB2START, OK!
Summary: After you check it, the DB2FMP process is used to perform protected stored procedures, or custom functions. The reason for this error has not been figured out. However, through this solution, you can explain a little, out of the error, and the DB2Diag.log file can always be not wrong. ^ _ ^
