DB2 ESE 9.1 The inability to create a new database under Windows Server 2008 and its resolution

DB2 Enterprise Server Edition (DB2 ESE) 9.1 Scenarios and solutions for unable to create a new database under Windows Server 2008

On installation, DB2 version 9.1 of Windows Server 2008, the default installation method is used to cause the database to be created and related error prompts:

"A system error (Reason code =" ") occurred sql3012c. Unable to process subsequent SQL statements. Sqlstate=58005 ".

By parsing the log "%programfiles%\ibm\sqllib\db2\db2diag.log" (which is where it is by default), a lot of access is blocked (access Defined) and you see some error returns and hints:

RETCODE:ZRC=0X840F0001=-2079391743=SQLO_ACCD "Access Denied"

dia8701c Access denied for resource ' ", operating system return code

Was "".

This kind of error hint, the above code reason is empty may be originated from this wrong translation display.

How to solve the problem, search for the corresponding keywords, sqlstate=58005, Access denied in the IBM Knowledge Base to find the relevant information, this example solution is derived from this help.

The connection is as follows: http://www-01.ibm.com/support/docview.wss?uid=swg21442542 although the SQL????? in the header The content is not the same, but look at the scope of the environment, or a smooth solution.

The following is IBM's original document information:

Environment

Windows 2008 Server

DB2 9.1 ESE

Diagnosing the problem

View the Db2diag.log file for the errors above.

Resolving the problem

More Wonderful content: http://www.bianceng.cnhttp://www.bianceng.cn/database/db2/

Re-installation of DB2 is required. During the re-installation de-select "Enable operating system security for DB2 objects"

After making this change you are able to create the required databases for Sametime Advanced.

Note:sametime Advanced 8.0.1 does not yet support DB2 9.5 which does don't have this problem with Windows 2008 Server secur ity.

Although I did not install Sametime Advanced, this reason is indeed affected by the associated security permissions.

Figure 1 Workaround Install the DB2 9.1 ESE in the Add Removal program and uncheck the "Enable Operating system security" option

Summarize:

Meet some strange problems or make a lot of use of official resources, while some default check and operation may not be suitable for all operating systems, need to pay more attention to software installation version, System environment, as well as log information.

Author: cnblogs Zhou Guanyu