Shulou(Shulou.com)05/31 Report--

This article introduces to you what is the solution to the SQL1042C error of DB2 database, the content is very detailed, interested friends can refer to, hope to be helpful to you.

An old DB2 database on the test machine made an error in the opening Times SQL1042C after the normal shutdown. The specific information is as follows:

# su-db2inst1

$db2start

2013-04-23 13:23:08 00 SQL1042C An unexpected system error occurred.

SQL1032N No start database manager command was issued. SQLSTATE=57019

The information that this error must check:

O see if there is enough space in the file system

O check to see if enough memory and swap / paging space are available

O the system time and date are set correctly, which is related to the expiration of the db2 license

O check the trace file, the contents of the db2diag.log to identify the problem

After examination, the first three problems are normal. Now check the DB2DIAG.LOG log, there is the following information to pay attention to

PID: 1388642 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.

For this issue, the license of CPU. You can check the license file information about this issue.

$db2licm-l

Product Name = "DB2 Enterprise Server Edition"

Product Identifier = "DB2ESE"

Version Information = "8.2"

Expiry Date = "Permanent"

Registered Connect User Policy = "Disabled"

Number Of Entitled Connect Users = "5"

Enforcement Policy = "Soft Stop"

Number of processors = "2"

Number of licensed processors = "1"

Database partitioning feature = "Not entitled"

Annotation = ""

Other information = ""

Product Name = "DB2 High Availability Disaster Recovery

Option "

Product Identifier = "DB2HADR"

Version Information = "8.2"

Expiry Date = "Permanent"

Annotation = ""

Other information = ""

Product Name = "DB2 Advanced Security Option"

Product Identifier = "DB2ASO"

Version Information = "8.2"

Expiry Date = "Permanent"

Annotation = ""

Other information = ""

If you notice the two red lines, you will find that the number of processors in the system is not the same as the number of licenses. In this case, use db2licm-n "DB2ESE" 2 (Note: 2 corresponding to the number of processors in the system).

The command is as follows:

# / home/db2inst1/sqllib/adm/db2licm-n "DB2ESE" 2

DBI1418I The number of licensed processors on this system has

Been updated successfully.

Then look, the CPU license has changed.

$db2licm-l

Product Name = "DB2 Enterprise Server Edition"

Product Identifier = "DB2ESE"

Version Information = "8.2"

Expiry Date = "Permanent"

Registered Connect User Policy = "Disabled"

Number Of Entitled Connect Users = "5"

Enforcement Policy = "Soft Stop"

Number of processors = "2"

Number of licensed processors = "2"

Database partitioning feature = "Not entitled"

Annotation = ""

Other information = ""

Product Name = "DB2 High Availability Disaster Recovery

Option "

Product Identifier = "DB2HADR"

Version Information = "8.2"

Expiry Date = "Permanent"

Annotation = ""

Other information = ""

Product Name = "DB2 Advanced Security Option"

Product Identifier = "DB2ASO"

Version Information = "8.2"

Expiry Date = "Permanent"

Annotation = ""

Other information = ""

Restart the database and find that SQL1042C error is still reported

$db2start

2013-04-23 13:59:28 00 SQL1042C An unexpected system error occurred.

SQL1032N No start database manager command was issued. SQLSTATE=57019

Continue to check the log and find the following information:

PID: 315522 TID: 1 PROC: db2sysc 0

INSTANCE: db2inst1 NODE: 000

FUNCTION: DB2 UDB, oper system services, sqloRunInstance, probe:210

CALLED: OS,-unspecified_system_function

OSERR: EPERM (1) "Not owner"

To solve this problem, we can use the following methods:

1) stop all DB2 processes

# ps-ef | grep db2

If there are DB2 processes, you can force kill to ensure that all DB2 processes have been terminated

2) execute the following statement

# / usr/opt/db2_08_01/instance/db2iupdt tstdb # instance name

Or

# / usr/opt/db2_08_01/instance/db2iupdt-e

Db2inst1

Db2inst2

DBI1070I Program db2iupdt completed successfully.

Note: update the instance to gain access to some new product options (especially after the change) or revision package.

And then turn it on.

$db2start

2013-04-23 14:23:39 00 SQL1063N DB2START processing was successful.

SQL1063N DB2START processing was successful.

$db2 connect to tstdb

Database Connection Information

Database server = DB2/6000 8.2.3

SQL authorization ID = DB2INST1

Local database alias = tstdb

Finally, the database got up and everything was fine after testing.

On the DB2 database SQL1042C error solution is shared here, I hope that the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.