IBM Data Studio连接错误SQL1035N [英] IBM Data Studio Connection error SQL1035N

问题描述

我在IBM论坛/文档，Google和StackOverflow主题中搜索有关此错误的信息，但我无法设法找到解决方案。

I have been searching in IBM forums/documentation, Google, and StackOverflow topics about this error, but I can't manage to find the solution.

为了测试和教育目的安装DB2，因为我是学生，我必须对此数据库的用法做一个手册。
通过Data Studio安装DB2和图形管理。

Installed DB2 for test and education purposes, since I'm a student and I have to do a manual about the usage of this DB. Installation of DB2 and graphical administration through Data Studio.

操作系统： Debian 7.7 Wheezy

OS: Debian 7.7 Wheezy

DB2版本： 10.5 FixPack 4（Cancuun版本）

DB2 Version: 10.5 FixPack 4 (Cancuun Release)

IBM Data Studio版本 4.1.1

以root身份安装DB2和Data Studio。

Installed DB2 and Data Studio as root.

我可以在终端执行命令like： / p>

I can execute commands in terminal like:

db2start
db2stop
db2_kill
db2

我也可以在db2命令行处理器中执行命令：
我可以创建一个数据库： db2 = CREATE DATABASE SAMPLE
也可以正确连接： db2 => CONNECT TO SAMPLE
，我可以查询连接的数据库： db2 => SELECT COUNT（COL）FROM TABLE

Also I can execute commands in db2 Command Line Processor like: I can create a database: db2 => CREATE DATABASE SAMPLE also it connects correctly: db2 => CONNECT TO SAMPLE and I can query to connected database: db2=> SELECT COUNT(COL) FROM TABLE

DB2工作正常，有时候挂起，我必须命令 db2_kill 并使用 db2start 重新启动
每当我创建一个新的DB时，它会挂起是很奇怪的。但无论如何，它能够连接和执行上面的命令。

DB2 is working good, sometimes it hangs and I have to command db2_kill and restart with db2start It's weird that it hangs everytime I create a new DB. But anyways, it's able to connect and execute commands like above.

Data Studio安装是正确的。

Data Studio installation is correct. The application is opened without problem.

我创建了一个名为example的新数据库：

I created a new database named example through:

db2inst1@debian:$ db2 CREATE DATABASE EXAMPLE

我安装了两个产品，在两个不同的机器。

I installed both products twice, and in two different machines. And the problem still exists.

我还要补充说，我试过运行Data Studio作为Debian用户和root，返回相同的错误。

I also have to add that I tried running Data Studio as Debian user and root, returning the same error.

在Data Studio中打开创建新连接的窗口/对话框时，数据库连接设置：

In Data Studio when I open the window/dialog of creating a new Connection, I configure the database connection settings:

数据库名称：示例
服务器：localhost
Port： 50000
用户名： db2inst1
密码：密码

Database Name: EXAMPLE Server: localhost Port: 50000 Username: db2inst1 Password: password

当我单击下一步或测试连接时，会出现问题：

And when I click Next or Test Connection, the problem appears:

手工翻译的西班牙语翻译成英语翻译：

Hand-translated Spanish to English translation:

Not successful conecction attempt
Summary: SQL1035N A connection attempt has failed and a SQL exception has been generated.
Explanation: The connection attempt has generated a SQL Exception. The SQL Exception content is: null
Check the SQL code associated to the SQL Exception to determinate the cause of the problem.

SQLSTATE: 57019

错误是SQL1035N

Error is SQL1035N

IBM证明SQL1035N是由以下原因引起的：

IBM documents that SQL1035N is caused because:

1. 还有一些打开的数据库连接。
   这不是这个，因为我有命令 db2_kill 和 db2start 和命令： db2 list active databases

1. There are remaining open connections to the database. It is not this one because I have command db2_kill and db2start and command: db2 list active databases returns no data.

数据库已被显式激活
我尝试了 ACTIVATE 和 DEACTIVATE 命令，仍然不工作，返回与Data Studio，SQL1035N相同的错误

The database has been activated explicitly I have tried ACTIVATE and DEACTIVATE commands, and still not working it returns the same error as Data Studio, SQL1035N

db2 => ACTIVATE DATABASE EJEMPLO
SQL1035N Laoperaciónha fallado porque la base de datos especificada no
puede conectarse en la modalidad solicitada。 SQLSTATE = 57019
SQL1035N操作失败，因为指定的数据库无法以请求的模式连接。 SQLSTATE = 57019

数据库处于WRITE SUSPEND模式。
我试图通过命令SET WRITE RESUME FOR DATABASE来修复这个问题，它返回：

The database is in WRITE SUSPEND mode. I tried fixing this by commanding SET WRITE RESUME FOR DATABASE, and it returns:

SQL1024没有到数据库的连接。 SQL = 08003

SQL1024 There are no connections to the database. SQL=08003

$ b $ p

这不是问题，因为没有连接到数据库

This is not the problem because there are no connections to the database

现在，如果我单击复制到剪贴板，它会复制完整的错误跟踪或堆栈跟踪。
这是它，但用西班牙语写。无论如何，它不应该是一个问题，了解它，因为大多数信息是技术性的，并且没有很多西班牙语的话。

Now, if I click the copy to clipboard it copies the complete error trace, or stack trace. Here it is, but written in spanish. Anyways, it shouldn't be a problem to understand it, since most information is technical, and there is not many spanish words.

感谢您的帮助。

Explicación

<b>Explicación:</b><br/><br/>el intento de conexión ha generado una excepción de SQL. El contenido de la excepción de SQL es:  null
<br/><b>Respuesta del usuario:</b><br/><br/>inspeccione el código SQL asociado a la excepción de SQL para determinar la causa del problema.
SQLSSTATE: 57019

Soporte

Propiedades de conexión

Base de datos: EJEMPLO
URL:  jdbc:db2://localhost:50000/EJEMPLO:retrieveMessagesFromServerOnGetMessage=true;
Nombre de usuario: db2inst1
Contraseña: (No se muestra)

Entorno

Nombre de clase de controlador = com.ibm.db2.jcc.DB2Driver
Versión de controlador = 4.18.60
Vía de acceso al archivo JAR del controlador = /opt/IBM/SDPShared/plugins/com.ibm.datatools.db2_2.2.100.v20140708_0755/driver/db2jcc4.jar:/opt/IBM/SDPShared/plugins/com.ibm.datatools.db2_2.2.100.v20140708_0755/driver/db2jcc_license_cisuz.jar
Nombre de sistema operativo = Linux
Arquitectura del sistema operativo = amd64
Versión del sistema operativo = 3.2.0-4-amd64
Proveedor de implementación de JVM = IBM Corporation
Tiempo de ejecución de JVM = Java(TM) SE Runtime Environment
Versión Java = JRE 1.7.0 IBM J9 2.7 Linux amd64-64 Compressed References 20140410_195893 (JIT enabled, AOT enabled)
J9VM - R27_Java727_SR1_20140410_1931_B195893
JIT  - tr.r13.java_20140410_61421
GC   - R27_Java727_SR1_20140410_1931_B195893_CMPRSS
J9CL - 20140410_195893
Lanzador = /opt/IBM/DS4.1.1/eclipse

Rastreo de pila

com.ibm.db2.jcc.am.SqlExceptioncom.ibm.db2.jcc.am.kd.a(Unknown Source)
com.ibm.db2.jcc.am.kd.a(Unknown Source)
com.ibm.db2.jcc.am.kd.a(Unknown Source)
com.ibm.db2.jcc.am.Connection.completeSqlca(Unknown Source)
com.ibm.db2.jcc.t4.z.q(Unknown Source)
com.ibm.db2.jcc.t4.z.p(Unknown Source)
com.ibm.db2.jcc.t4.z.l(Unknown Source)
com.ibm.db2.jcc.t4.z.d(Unknown Source)
com.ibm.db2.jcc.t4.b.k(Unknown Source)
com.ibm.db2.jcc.t4.b.b(Unknown Source)
com.ibm.db2.jcc.t4.b.a(Unknown Source)
com.ibm.db2.jcc.t4.b.b(Unknown Source)
com.ibm.db2.jcc.t4.b.a(Unknown Source)
com.ibm.db2.jcc.t4.b.a(Unknown Source)
com.ibm.db2.jcc.t4.b.a(Unknown Source)
com.ibm.db2.jcc.t4.b.<init>(Unknown Source)
com.ibm.db2.jcc.DB2SimpleDataSource.getConnection(Unknown Source)
com.ibm.db2.jcc.DB2SimpleDataSource.getConnection(Unknown Source)
com.ibm.db2.jcc.DB2Driver.connect(Unknown Source)
com.ibm.db2.jcc.DB2Driver.connect(Unknown Source)
org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.createConnection(Unknown Source)
org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(Unknown Source)
org.eclipse.datatools.connectivity.DriverConnectionBase.open(Unknown Source)
org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.open(Unknown Source)
org.eclipse.datatools.enablement.ibm.db2.internal.luw.JDBCLUWConnectionFactory.createConnection(Unknown Source)
org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(Unknown Source)
org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(Unknown Source)
com.ibm.datatools.connection.internal.ui.databases.NewDatabaseConnnectionWizardPage.handleTestConnection(Unknown Source)
com.ibm.datatools.connection.internal.ui.databases.NewDatabaseConnnectionWizardPage.access$6(Unknown Source)
com.ibm.datatools.connection.internal.ui.databases.NewDatabaseConnnectionWizardPage$10.handleEvent(Unknown Source)
org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)
org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
org.eclipse.jface.window.Window.runEventLoop(Unknown Source)
org.eclipse.jface.window.Window.open(Unknown Source)
com.ibm.datatools.connection.internal.ui.databases.actions.NewDBConnectionHandler.execute(Unknown Source)
org.eclipse.ui.internal.handlers.HandlerProxy.execute(Unknown Source)
org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(Unknown Source)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
java.lang.reflect.Method.invoke(Unknown Source)
org.eclipse.e4.core.internal.di.MethodRequestor.execute(Unknown Source)
org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(Unknown Source)
org.eclipse.e4.core.internal.di.InjectorImpl.invoke(Unknown Source)
org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(Unknown Source)
org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(Unknown Source)
org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(Unknown Source)
org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(Unknown Source)
org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(Unknown Source)
org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(Unknown Source)
org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)
org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(Unknown Source)
org.eclipse.core.databinding.observable.Realm.runWithDefault(Unknown Source)
org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(Unknown Source)
org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(Unknown Source)
org.eclipse.ui.internal.Workbench$5.run(Unknown Source)
org.eclipse.core.databinding.observable.Realm.runWithDefault(Unknown Source)
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown Source)
org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source)
org.eclipse.ui.internal.ide.application.IDEApplication.start(Unknown Source)
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Unknown Source)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Unknown Source)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Unknown Source)
org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
java.lang.reflect.Method.invoke(Unknown Source)
org.eclipse.equinox.launcher.Main.invokeFramework(Unknown Source)
org.eclipse.equinox.launcher.Main.basicRun(Unknown Source)
org.eclipse.equinox.launcher.Main.run(Unknown Source)
org.eclipse.equinox.launcher.Main.main(Unknown Source)

我也将此主题复制并粘贴到IBM论坛，只是为了直接解决这个错误。

I will also copy and paste this topic to IBM forum, just to address them this error directly.

再次感谢。

推荐答案

问题是已解决。

我会回答自己的问题：

我从V10.5降级到V9.7 FixPack 6

I downgraded from V10.5 to V9.7 FixPack 6

此外，我检查了DB2支持的Linux平台，我选择安装9.7在Ubuntu 12.04.5中升级FP6，现在，在安装整个系统，Ubuntu和DB2之后，我使用控制中心，允许我创建DB并成功查询数据库。

Also, I checked Linux platforms supported by DB2, and I chose to install 9.7 Express FP6 in Ubuntu 12.04.5, and right now, after installing the overall system, Ubuntu and DB2, I am using the Control Center, allowing me to create DB and query the DB successfully.

经典作品

谢谢

strong>

Edit at 18 January 2015

我重新安装了DB2 V10.5，并且此时间数据库创建工作正常。我要说时间，因为我不得不等待5分钟才能创建数据库。这是我认为我以前的主要问题，因为它是在IBM官方论坛回答，因为我试图在一个VM中创建它，并且进程需要一点时间。

I reinstalled DB2 V10.5 and this time the DB creation worked. And I'm remarking time, because I had to wait 5 minutes for the DB to be created. This is the main issue I think I had previously, as it was answered in IBM official forum, since I was trying to create it in a VM and the proccess takes a bit longer.

这篇关于IBM Data Studio连接错误SQL1035N的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！