Case study of sql00002c error solution for DB2 database

After an old DB2 database on the test machine stops the database normally, the sql1_2c error is reported when the database is started. The details are as follows:

# Su-db2inst1

 

$ Db2start

2013-04-23 13:23:08 0 0 sql1_2c An unexpected system error occurred.

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

 

This error must be checked:

O check whether the file system space is sufficient

O check whether sufficient memory and swap/paging space are available

O The correct system time and date are related to the expiration of the db2 authorization license

O view the trace file and the content in db2diag. log to confirm the problem

After inspection, the first three problems are normal. View the DB2DIAG. LOG. Note the following information:

 

PID: 1388642 TID: 1 PROC: db2star2

INSTANCE: db2inst1 NODE: 000

FUNCTION: DB2 UDB, base sys utilities, LicCheckProcessors, probe: 20

MESSAGE: adm1e e The number of processors on this machine exceeds

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

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

Db2licm utility, refer to the DB2 Command Reference.

CPU authorization permission for this issue. You can view the license file information for 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 red lines, you will find that the number of system processors is different from the number of authorizations. In this case, use db2licm-n "DB2ESE" 2 (Note: 2 corresponds to the number of processors in the system. Command: #/home/db2inst1/sqllib/adm/db2licm-n "DB2ESE" 2DBI1418I The number of licensed processors on this system has been updated successfully.
Then, 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 = ""

When the database is restarted, The sql1_2c error is still reported.

 

$ Db2start

2013-04-23 13:59:28 0 0 sql1_2c An unexpected system error occurred.

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

 

The following information is found in the log: PID: 315522 TID: 1 PROC: db2sysc 0 INSTANCE: db2inst1 NODE: 000 FUNCTION: DB2 UDB, using system services, sqloRunInstance, probe: 210 CALLED: OS,-, unspecified_system_functionOSERR: EPERM (1) "Not owner" to solve this problem, you can use the following methods:

1) Stop all DB2 Processes

# Ps-ef | grep db2

If a DB2 process exists, it can be forcibly terminated (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 obtain some new product options, especially after the change) or change the package access.

And then start

 

$ Db2start

2013-04-23 14:23:39 0 0 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 normal after testing.

 

Bkjia qr code

650) this. width = 650; "alt =" "border =" 0 "src =" http://www.bkjia.com/uploads/allimg/131228/22560962O-0.jpg "/>

This article from the "Drop water stone" blog, please be sure to keep this source http://xjsunjie.blog.51cto.com/999372/1184826