Oracle10205 dbconsole啟動報ssl:Open wallet failed, ret = 28750

luckyfriends發表於2014-08-19

OracleAI

Oracle10205下dbconsole無法啟動報ssl: Open wallet failed, ret = 28750

問題現象：

啟動報錯

利用dbca及netca刪除資料庫及監聽、dbconsole等

C:\>sqlplus / as sysdba

SQL> startup

ORACLE 例程已經啟動。

Total System Global Area 1610612736 bytes

Fixed Size 2077872 bytes

Variable Size 553651024 bytes

Database Buffers 1023410176 bytes

Redo Buffers 31473664 bytes

資料庫裝載完畢。

資料庫已經開啟。

SQL> select file_name from dba_data_Files;

FILE_NAME

--------------------------------------------------------------------------------

D:\ORACLE\PRODUCT\10.2.0\ORADATA\UFNC\USERS01.DBF

D:\ORACLE\PRODUCT\10.2.0\ORADATA\UFNC\SYSAUX01.DBF

D:\ORACLE\PRODUCT\10.2.0\ORADATA\UFNC\UNDOTBS01.DBF

D:\ORACLE\PRODUCT\10.2.0\ORADATA\UFNC\SYSTEM01.DBF

F:\NCDATA\NNC_DATA01.DBF

F:\NCDATA\NNC_DATA02.DBF

F:\NCDATA\NNC_DATA03.DBF

F:\NCDATA\NNC_INDEX01.DBF

F:\NCDATA\NNC_INDEX02.DBF

F:\NCDATA\NNC_INDEX03.DBF

已選擇10行。

SQL> shutdown immediate

資料庫已經關閉。

已經解除安裝資料庫。

ORACLE 例程已經關閉。

SQL> exit

從 Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options(情

況複雜) 斷開

C:\>netca

Oracle Net Services 配置:

使用者終止了 Oracle Net Services 配置。退出程式碼是-1

C:\>netca

Oracle Net Services 配置:

停止 Oracle Net 監聽程式:

正在執行監聽程式控制:

D:\oracle\product\10.2.0\db_1\bin\lsnrctl stop LISTENER

監聽程式控制完成。

停止監聽程式失敗。

已刪除的監聽程式服務: LISTENER 0

已刪除的監聽程式: LISTENER

成功完成 Oracle Net Services 配置。退出程式碼是0

C:\>dbca

如下重新配置dbconsole

C:\>set ORACLE_SID=ufnc

C:\>set ORACLE_HOME=D:\oracle\product\10.2.0\

C:\>set ORACLE_HOME=D:\oracle\product\10.2.0\db_1

C:\>emca -repos create

EMCA 開始於 2011-12-20 16:00:25

EM Configuration Assistant, 10.2.0.5.0 正式版

輸入以下資訊:

資料庫 SID: ufnc

監聽程式埠號: 1521

SYS 使用者的口令:

SYSMAN 使用者的口令:

是否繼續? [是(Y)/否(N)]: y

2011-12-20 16:00:36 oracle.sysman.emcp.EMConfig perform

資訊: 正在將此操作記錄到 D:\oracle\product\10.2.0\db_1\cfgtoollogs\emca\ufnc\emc

a_2011-12-20_04-00-25-下午.log。

2011-12-20 16:00:38 oracle.sysman.emcp.DatabaseChecks performReposChecks

嚴重: 資料檔案庫已存在。改正錯誤, 然後以獨立模式重新執行 EM Configuration Assi

stant。

C:\>emca -repos drop、

EMCA 開始於 2011-12-20 16:00:53

EM Configuration Assistant, 10.2.0.5.0 正式版

輸入以下資訊:

資料庫 SID: ufnc

監聽程式埠號: 1521

SYS 使用者的口令:

SYSMAN 使用者的口令:

----------------------------------------------------------------------

WARNING : While repository is dropped the database will be put in quiesce mode.

----------------------------------------------------------------------

是否繼續? [是(Y)/否(N)]: y

2011-12-20 16:01:05 oracle.sysman.emcp.EMConfig perform

資訊: 正在將此操作記錄到 D:\oracle\product\10.2.0\db_1\cfgtoollogs\emca\ufnc\emc

a_2011-12-20_04-00-53-下午.log。

2011-12-20 16:01:11 oracle.sysman.emcp.EMReposConfig invoke

資訊: 正在刪除 EM 資料檔案庫 (此操作可能需要一段時間)...

2011-12-20 16:01:11 oracle.sysman.emcp.EMReposConfig dropRepository

資訊: 正在刪除 EM 資料檔案庫 (此操作可能需要一段時間)...

2011-12-20 16:01:50 oracle.sysman.emcp.EMReposConfig invoke

資訊: 已成功刪除資料檔案庫

已成功完成 Enterprise Manager 的配置

EMCA 結束於 2011-12-20 16:01:50

C:\>emca -repos create

EMCA 開始於 2011-12-20 16:02:22

EM Configuration Assistant, 10.2.0.5.0 正式版

輸入以下資訊:

資料庫 SID: ufnc

監聽程式埠號: 1521

SYS 使用者的口令:

SYSMAN 使用者的口令:

是否繼續? [是(Y)/否(N)]: y

2011-12-20 16:02:43 oracle.sysman.emcp.EMConfig perform

資訊: 正在將此操作記錄到 D:\oracle\product\10.2.0\db_1\cfgtoollogs\emca\ufnc\emc

a_2011-12-20_04-02-22-下午.log。

2011-12-20 16:02:49 oracle.sysman.emcp.EMReposConfig createRepository

資訊: 正在建立 EM 資料檔案庫 (此操作可能需要一段時間)...

2011-12-20 16:04:13 oracle.sysman.emcp.EMReposConfig invoke

資訊: 已成功建立資料檔案庫

已成功完成 Enterprise Manager 的配置

EMCA 結束於 2011-12-20 16:04:14

C:\>emca -config dbcontrol db

EMCA 開始於 2011-12-20 16:06:04

EM Configuration Assistant, 10.2.0.5.0 正式版

輸入以下資訊:

資料庫 SID: ufnc

監聽程式埠號: 1521

SYS 使用者的口令:

DBSNMP 使用者的口令:

SYSMAN 使用者的口令:

通知的電子郵件地址 (可選):

通知的發件 (SMTP) 伺服器 (可選):

-----------------------------------------------------------------

已指定以下設定

資料庫 ORACLE_HOME ................ D:\oracle\product\10.2.0\db_1

Local hostname ................ NCDB2

監聽程式埠號 ................ 1521

資料庫 SID ................ ufnc

通知的電子郵件地址 ...............

通知的發件 (SMTP) 伺服器 ...............

-----------------------------------------------------------------

是否繼續? [是(Y)/否(N)]: y

2011-12-20 16:07:49 oracle.sysman.emcp.EMConfig perform

資訊: 正在將此操作記錄到 D:\oracle\product\10.2.0\db_1\cfgtoollogs\emca\ufnc\emc

a_2011-12-20_04-06-04-下午.log。

2011-12-20 16:08:06 oracle.sysman.emcp.util.DBControlUtil secureDBConsole

資訊: 正在保護 Database Control (此操作可能需要一段時間)...

2011-12-20 16:08:22 oracle.sysman.emcp.util.DBControlUtil secureDBConsole

資訊: 已成功保護 Database Control。

2011-12-20 16:08:22 oracle.sysman.emcp.util.DBControlUtil startOMS

資訊: 正在啟動 Database Control (此操作可能需要一段時間)...

2011-12-20 16:17:42 oracle.sysman.emcp.EMConfig perform

嚴重: 啟動 Database Control 時出錯

有關詳細資料, 請參閱 D:\oracle\product\10.2.0\db_1\cfgtoollogs\emca\ufnc\emca_20

11-12-20_04-06-04-下午.log 中的日誌檔案。

無法完成配置。有關詳細資料, 請參閱 D:\oracle\product\10.2.0\db_1\cfgtoollogs\em

ca\ufnc\emca_2011-12-20_04-06-04-下午.log 中的日誌檔案。

C:\>

啟動dbconsole還是報錯：

日誌D:\oracle\product\10.2.0\db_1\cfgtoollogs\emca\ufnc

配置: Waiting for service 'OracleDBConsoleufnc' to fully start

2011-12-20 16:17:42 oracle.sysman.emcp.util.PlatformInterface serviceCommand

配置: Waiting for service 'OracleDBConsoleufnc' to fully start

2011-12-20 16:17:42 oracle.sysman.emcp.util.PlatformInterface serviceCommand

配置: Initialization failure for service during start

2011-12-20 16:17:42 oracle.sysman.emcp.EMConfig perform

嚴重: 啟動 Database Control 時出錯

有關詳細資料, 請參閱 D:\oracle\product\10.2.0\db_1\cfgtoollogs\emca\ufnc\emca_2011-12-20_04-06-04-下午.log 中的日誌

檔案。

2011-12-20 16:17:42 oracle.sysman.emcp.EMConfig perform

配置: Stack Trace:

oracle.sysman.emcp.exception.EMConfigException: 啟動 Database Control 時出錯

at oracle.sysman.emcp.EMDBPostConfig.performConfiguration(EMDBPostConfig.java:649)

at oracle.sysman.emcp.EMDBPostConfig.invoke(EMDBPostConfig.java:227)

at oracle.sysman.emcp.EMDBPostConfig.invoke(EMDBPostConfig.java:196)

at oracle.sysman.emcp.EMConfig.perform(EMConfig.java:184)

at oracle.sysman.emcp.EMConfigAssistant.invokeEMCA(EMConfigAssistant.java:494)

at oracle.sysman.emcp.EMConfigAssistant.performConfiguration(EMConfigAssistant.java:1161)

at oracle.sysman.emcp.EMConfigAssistant.statusMain(EMConfigAssistant.java:478)

at oracle.sysman.emcp.EMConfigAssistant.main(EMConfigAssistant.java:426)

網路卡多個為儲存連線所需，排除多個活動網路卡導致該問題

檢視dbconsole的trace

日誌D:\oracle\product\10.2.0\db_1\NCDB2_ufnc\sysman\logs

-12-20 16:30:15 Thread-36604 ERROR ssl: nmehlenv_openWallet failed

2011-12-20 16:30:15 Thread-36604 ERROR http: 1840: Unable to initialize ssl connection with server, aborting connection attempt

2011-12-20 16:30:15 Thread-36604 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://NCDB2:1158/em/upload/: retStatus=-1

2011-12-20 16:30:15 Thread-36604 ERROR ssl: Open wallet failed, ret = 28750

2011-12-20 16:30:15 Thread-36604 ERROR ssl: nmehlenv_openWallet failed

2011-12-20 16:30:15 Thread-36604 ERROR http: 1840: Unable to initialize ssl connection with server, aborting connection attempt

2011-12-20 16:30:15 Thread-36604 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://NCDB2:1158/em/upload/: retStatus=-1

2011-12-20 16:30:15 Thread-2724 ERROR ssl: Open wallet failed, ret = 28750

2011-12-20 16:30:15 Thread-2724 ERROR ssl: nmehlenv_openWallet failed

2011-12-20 16:30:15 Thread-2724 ERROR http: 1892: Error initializing SSL connection for incoming request, aborting request. ret=-1

2011-12-20 16:30:45 Thread-684 ERROR ssl: Open wallet failed, ret = 28750

2011-12-20 16:30:45 Thread-684 ERROR ssl: nmehlenv_openWallet failed

2011-12-20 16:30:45 Thread-684 ERROR http: 1840: Unable to initialize ssl connection with server, aborting connection attempt

2011-12-20 16:30:45 Thread-684 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://NCDB2:1158/em/upload/: retStatus=-1

2011-12-20 16:30:45 Thread-684 ERROR ssl: Open wallet failed, ret = 28750

2011-12-20 16:30:45 Thread-684 ERROR ssl: nmehlenv_openWallet failed

2011-12-20 16:30:45 Thread-684 ERROR http: 1840: Unable to initialize ssl connection with server, aborting connection attempt

2011-12-20 16:30:45 Thread-684 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://NCDB2:1158/em/upload/: retStatus=-1

2011-12-20 16:30:46 Thread-38900 ERROR ssl: Open wallet failed, ret = 28750

2011-12-20 16:30:46 Thread-38900 ERROR ssl: nmehlenv_openWallet failed

2011-12-20 16:30:46 Thread-38900 ERROR http: 1888: Error initializing SSL connection for incoming request, aborting request. ret=-1

確認該問題是有oracle bug[ID 1278564.1]導致，需要安裝補丁Patch 8350262，參考文件如下：

http://www.linuxidc.com/Linux/2011-01/31708.htm

http://www.cnblogs.com/spatial/archive/0001/01/01/1529366.html

http://openwares.net/database/x64_oracle_10g_emdbconsole_error.html

Error Starting Database Control. emagent.trc shows "Open wallet failed, ret = 28750" error - After 31-Dec-2010 [ID 1278564.1]

	修改時間 05-JAN-2011 型別 PROBLEM 狀態 PUBLISHED

In this Document
Symptoms
Cause
Solution
References

Applies to:

Enterprise Manager Grid Control - Version: 10.2.0.4 to 10.2.0.5 - Release: 10.2 to 10.2
Information in this document applies to any platform.
Enterprise Manager Database Control 10.2.0.4
Enterprise Manager Database Control 10.2.0.5
Any platform.
Applies to Single Instance and RAC.

Symptoms

When running EMCA, DBCA or DBUA on a 10.2.0.4/10.2.0.5 database past the 31st Dec 2010, operation fails at EM DB Console starting phase.
Database Configuration Assistant (DBCA) and Database Upgrade Assistant (DBUA) will report the following error in the console:

Could not complete the Enterprise Manager configuration.
Enterprise manager configuration failed due to the following error –
Error starting Database Control

Enterprise Manager Configuration Assistant (EMCA) will write errors similar to those below to the emca.log file:

CONFIG: Securing Database Control completed successfully .
Jan 2, 2011 7:22:47 PM oracle.sysman.emcp.ParamsManager getParam
CONFIG: No value was set for the parameter ORACLE_HOSTNAME.
Jan 2, 2011 7:22:47 PM oracle.sysman.emcp.util.DBControlUtil startOMS
INFO: Starting Database Control (this may take a while) ...
Jan 2, 2011 7:22:47 PM oracle.sysman.emcp.util.PlatformInterface addEnvVarToList
CONFIG: Value for env var 'ORACLE_HOSTNAME' is '', discarding the same
CONFIG: Returning env array from cache
Jan 2, 2011 7:22:47 PM oracle.sysman.emcp.util.PlatformInterface executeCommand
CONFIG: Starting execution: /myhost/bin/emctl start dbconsole
Jan 2, 2011 7:27:26 PM oracle.sysman.emcp.util.PlatformInterface executeCommand
CONFIG: Exit value of 1
Jan 2, 2011 7:27:26 PM oracle.sysman.emcp.util.PlatformInterface executeCommand
CONFIG: Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
https://myhost:5501/em/console/aboutApplication
Starting Oracle Enterprise Manager 10g Database Control
............................................................................................. failed.
------------------------------------------------------------------
Logs are generated in directory /myhost/sysman/log
Jan 2, 2011 7:27:26 PM oracle.sysman.emcp.util.PlatformInterface executeCommand
WARNING: Error executing /myhost/bin/emctl start dbconsole
Jan 2, 2011 7:27:26 PM oracle.sysman.emcp.EMConfig perform
SEVERE: Error starting Database Control
Refer to the log file at /myhost/dbua/d4/upgrade/emConfig.log for more details.
Jan 2, 2011 7:27:26 PM oracle.sysman.emcp.EMConfig perform
CONFIG: Stack Trace:
oracle.sysman.emcp.exception.EMConfigException: Error starting Database Control
at oracle.sysman.emcp.EMDBPostConfig.performUpgrade(EMDBPostConfig.java:763)
at oracle.sysman.emcp.EMDBPostConfig.invoke(EMDBPostConfig.java:232)
at oracle.sysman.emcp.EMDBPostConfig.invoke(EMDBPostConfig.java:193)
at oracle.sysman.emcp.EMConfig.perform(EMConfig.java:184)
at oracle.sysman.assistants.util.em.EMConfiguration.run(EMConfiguration.java:436)
at oracle.sysman.assistants.util.em.EMConfigStep.executeImpl(EMConfigStep.java:140)
at oracle.sysman.assistants.util.step.BasicStep.execute(BasicStep.java:210)
at oracle.sysman.assistants.util.step.BasicStep.callStep(BasicStep.java:251)
at oracle.sysman.assistants.dbma.backend.EMConfigStep.executeStepImpl(EMConfigStep.java:104)
at oracle.sysman.assistants.dbma.backend.SummarizableStep.executeImpl(SummarizableStep.java:175)
at oracle.sysman.assistants.util.step.BasicStep.execute(BasicStep.java:210)
at oracle.sysman.assistants.util.step.Step.execute(Step.java:140)
at oracle.sysman.assistants.util.step.StepContext$ModeRunner.run(StepContext.java:2488)
at java.lang.Thread.run(Thread.java:534)

Checking the ORACLE_HOME\_\sysman\log\emagent.trc, one can see also:

2011-01-09 09:36:56 Thread-51125136 ERROR pingManager: nmepm_pingReposURL: Cannot connect to https://myhost:1158/em/upload/: retStatus=-1
2011-01-09 09:36:56 Thread-51125136 ERROR ssl: Open wallet failed, ret = 28750
2011-01-09 09:36:56 Thread-51125136 ERROR ssl: nmehlenv_openWallet failed
2011-01-09 09:36:56 Thread-51125136 ERROR http: 15: Unable to initialize ssl connection with server, aborting connection attempt

Cause

The Root Certificate Authority (CA) expired on 31-DEC-2010 00:00:0

Solution

Follow solution in note 1222603.1.
For Single instance database, use section Recovering from Configuration Errors on a Single Instance Database
For RAC database, use Recovering from Configuration Errors in an Oracle Real Application Clusters (RAC) Environment

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1222603.1

Enterprise Manager Database Control Configuration - Recovering From Errors Due to CA Expiry on Oracle Database 10.2.0.4 or 10.2.0.5 [Video] [ID 1222603.1] s

Recovering from Configuration Errors on a Single Instance Database

1. Ignore any errors and continue with the installation or upgrade. The database will be created without errors.
2. Apply Patch 8350262 to your Oracle Home installation using OPatch. The patch is also included in 10.2.0.5 database patch 5 and 10.2.0.5.3 (PSU3).
NOTE: The database instance and the listener DO NOT have to be stopped for applying this patch, but ensure that all java processes sourced from the Oracle Home being patached are stopped in this case (i.e., all Oracle Home-related java.exe on Windows, for instance).

opatch apply
Invoking OPatch 10.2.0.4.2
Oracle Interim Patch Installer version 10.2.0.4.2
Copyright (c) 2007, Oracle Corporation. All rights reserved.
Oracle Home : /myhost
Central Inventory : /scratch/pchebrol/oraInventory
from : /etc/oraInst.loc
OPatch version : 10.2.0.4.2
OUI version : 10.2.0.4.0
OUI location : /myhost/oui
Log file location : /myhost/cfgtoollogs/opatch/opatch2011-01-02_11-00-00AM.log
ApplySession applying interim patch '8350262' to OH '/myhost'
Running prerequisite checks...
OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '8350262' for restore. This might take a while...
Backing up files affected by the patch '8350262' for rollback. This might take a while...
Patching component oracle.sysman.agent.core, 10.2.0.4.0a...
Updating jar file "/myhost/sysman/jlib/emCORE.jar" with
"/sysman/jlib/emCORE.jar/oracle/sysman/eml/sec/fsc/FSWalletUtil.class"
Updating jar file "/myhost/sysman/jlib/emCORE.jar" with
"/sysman/jlib/emCORE.jar/oracle/sysman/eml/sec/rep/RepWalletUtil.class"
Updating jar file "/myhost/sysman/jlib/emCORE.jar" with
"/sysman/jlib/emCORE.jar/oracle/sysman/eml/sec/util/RootCert.class"
Updating jar file "/myhost/sysman/jlib/emCORE.jar" with
"/sysman/jlib/emCORE.jar/oracle/sysman/eml/sec/util/SecConstants.class"
Updating jar file "/myhost/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_
java.jar/oracle/sysman/eml/sec/fsc/FSWalletUtil.class"
Updating jar file "/myhost/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_
java.jar/oracle/sysman/eml/sec/rep/RepWalletUtil.class"
Updating jar file "/myhost/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_
java.jar/oracle/sysman/eml/sec/util/RootCert.class"
Updating jar file "/myhost/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd_
java.jar/oracle/sysman/eml/sec/util/SecConstants.class"
ApplySession adding interim patch '8350262' to inventory
Verifying the update...
Inventory check OK: Patch ID 8350262 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 8350262 are present in Oracle Home.
OPatch succeeded.

3. After applying the patch, force stop the Database Control (dbconsole) process using the killDBConsole script bundled with the patch. Note that the dbconsole process cannot be stopped using the emctl stop dbconsole command, as EMCTL is unable to connect to the process.
To execute the killDBConsole script:

Set the ORACLE_HOME and ORACLE_SID environment variables.
Execute /killDBConsole.

Note for Windows Platform Only:
It is not necessary to force stop the dbconsole process on the Windows platform, because the process will
already be in a stopped state at the end of the failed configuration attempt.

The killDBConsole script output is shown below:

$ /killDBConsole
ORACLE_HOME=/myhost/db_1
ORACLE_SID=caem31
State directory = /myhost/db_1/staxd10_caem31
WatchDog PID = 802932
DBconsole PID = 577716
EMAgent PID = 512156
Killing WatchDog (pid=802932) ...
Successfully killed process 802932
Killing DBConsole (pid=577716) ...
Successfully killed process 577716
Killing EMAgent (pid=512156) ...
Successfully killed process 512156

4. Re-secure Database Control with the following command:
/bin/emctl secure dbconsole -reset
You will be prompted twice to confirm that the Root key must be overwritten. In both cases, enter upper-case "Y" as the response. Any other response (including lower-case "y") will cause the command to terminate without completing. If this happens, the command can be re-invoked.

$ ./emctl secure dbconsole -reset
Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
https://myhost:5501/em/console/aboutApplication
Enter Enterprise Manager Root Password :
DBCONSOLE already stopped... Done.
Agent is already stopped... Done.
Securing dbconsole... Started.
Checking Repository... Done.
Checking Em Key... Done.
Checking Repository for an existing Enterprise Manager Root Key...
WARNING! An Enterprise Manager Root Key already exists in
the Repository. This operation will replace your Enterprise
Manager Root Key.
All existing Agents that use HTTPS will need to be
reconfigured if you proceed. Do you wish to continue and
overwrite your Root Key
(Y/N) ?
Y
Are you sure ? Reset of the Enterprise Manager Root Key
will mean that you will need to reconfigure each Agent
that is associated with this OMS before they will be
able to upload any data to it. Monitoring of Targets
associated with these Agents will be unavailable until
after they are reconfigured.
(Y/N) ?
Y
Generating Enterprise Manager Root Key (this takes a minute)... Done.Fetching Root Certificate from
the Repository... Done.
Updating HTTPS port in emoms.properties file... Done.
Generating Java Keystore... Done.
Securing OMS ... Done.
Generating Oracle Wallet Password for Agent.... Done.
Generating wallet for Agent ... Done.
Copying the wallet for agent use... Done.
Storing agent key in repository... Done.
Storing agent key for agent ... Done.
Configuring Agent...
Configuring Agent for HTTPS in DBCONSOLE mode... Done.
EMD_URL set in /myhost/myhost/sysman/config/emd.properties
Done.
Configuring Key store.. Done.
Securing dbconsole... Sucessful.