關于達夢數據庫一些疑難雜癥的解決

1.在用root用戶時開啟了./manage 或 ./console 工具后，用其他用戶開啟顯示No protocol specified
具體的報錯：
[dmdba@localhost tool]$ ./manager

(Manager:10369): GLib-GObject-WARNING **: 18:44:34.490: invalid (NULL) pointer instance

(Manager:10369): GLib-GObject-CRITICAL **: 18:44:34.490: g_signal_connect_data: assertion ‘G_TYPE_CHECK_INSTANCE (instance)’ failed

(Manager:10369): Gtk-CRITICAL **: 18:44:34.491: IA__gtk_settings_get_for_screen: assertion ‘GDK_IS_SCREEN (screen)’ failed

(Manager:10369): Gtk-WARNING **: 18:44:34.498: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window

(Manager:10369): Gtk-WARNING **: 18:44:34.498: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window

(Manager:10369): Gdk-CRITICAL **: 18:44:34.498: IA__gdk_screen_get_display: assertion ‘GDK_IS_SCREEN (screen)’ failed

(Manager:10369): Gdk-CRITICAL **: 18:44:34.498: IA__gdk_display_get_pointer: assertion ‘GDK_IS_DISPLAY (display)’ failed

(Manager:10369): Gdk-CRITICAL **: 18:44:34.498: IA__gdk_screen_get_monitor_at_point: assertion ‘GDK_IS_SCREEN (screen)’ failed

(Manager:10369): Gtk-WARNING **: 18:44:34.498: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window

(Manager:10369): Gdk-CRITICAL **: 18:44:34.498: IA__gdk_screen_get_n_monitors: assertion ‘GDK_IS_SCREEN (screen)’ failed

(Manager:10369): Gtk-WARNING **: 18:44:34.498: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window

(Manager:10369): Gdk-CRITICAL **: 18:44:34.498: IA__gdk_screen_get_monitor_geometry: assertion ‘GDK_IS_SCREEN (screen)’ failed

(Manager:10369): Gdk-CRITICAL **: 18:44:34.498: IA__gdk_screen_get_default_colormap: assertion ‘GDK_IS_SCREEN (screen)’ failed

(Manager:10369): Gdk-CRITICAL **: 18:44:34.498: IA__gdk_colormap_get_visual: assertion ‘GDK_IS_COLORMAP (colormap)’ failed

(Manager:10369): Gdk-CRITICAL **: 18:44:34.498: IA__gdk_screen_get_default_colormap: assertion ‘GDK_IS_SCREEN (screen)’ failed

(Manager:10369): Gdk-CRITICAL **: 18:44:34.498: IA__gdk_screen_get_root_window: assertion ‘GDK_IS_SCREEN (screen)’ failed

(Manager:10369): Gdk-CRITICAL **: 18:44:34.498: IA__gdk_screen_get_root_window: assertion ‘GDK_IS_SCREEN (screen)’ failed

(Manager:10369): Gdk-CRITICAL **: 18:44:34.498: IA__gdk_window_new: assertion ‘GDK_IS_WINDOW (parent)’ failed

A fatal error has been detected by the Java Runtime Environment:

SIGSEGV (0xb) at pc=0x00007f016c3ea2c7, pid=10369, tid=139644245047040

JRE version: 6.0_26-b03

Java VM: Java HotSpot? 64-Bit Server VM (20.1-b02 mixed mode linux-amd64 compressed oops)

Problematic frame:

C [libgdk-x11-2.0.so.0+0x7b2c7] __float128+0x7

An error report file with more information is saved as:

/dm8/tool/hs_err_pid10369.log

If you would like to submit a bug report, please visit:

http://java.sun.com/webapps/bugreport/crash.jsp

The crash happened outside the Java Virtual Machine in native code.

See problematic frame for where to report the bug.

./manager: 行 17: 10369 已放棄 (吐核)“$JAV{A}_{H}OME/bin/java"?XX:+PerfDisableSharedMem?DD{M}_{H}OME="$DM_HOME” -Djava.library.path=“$D{M}_{H}OME/bin"?Ddameng.log.file="$TOOL_HOME/log4j.xml” -DeclipseHome=“$TOO{L}_{H}OME"?Dosgi.nl="$INSTALL_LANGUAGE” -Ddameng.dts.explorer.root=“$TOO{L}_{H}OME/workspace/local/dts"?Ddameng.isql.explorer.root="$TOOL_HOME/workspace/local/isql” -Duse_bak2=true -Dapp.name=manager -XX:MaxPermSize=256m -jar “$TOO{L}_{H}OME/plugins/org.eclipse.equinox.launche{r}_1.1.1.R36x_{v}20101122_{1}400.jar"?oslinux?wsgtk?archx86_{6}4?showsplash"$TOOL_HOME/manager.bmp” -data "$TOO{L}_{H}OME/workspace/manager"?productcom.dameng.manager.product?nameManager[dmdba@localhosttool]$

問題原因：用root用戶登錄后Display變量改變
解決辦法：將ROOT用戶下和普通用戶下的 Display變量值改成一致，并分別運行 xhost+命令關閉用戶訪問權限
ROOT用戶這里改成DISPLAY =: 0

普通用胡也改成DISPLAY =: 0
運行xhost+


大功告成

2.安裝數據運行命令時提醒No protocol Specified
其實這個問題和第一個一樣

問題原因：當前操作系統的登錄用戶應該為非dmdba用戶，如果在當前會話中啟用圖形界面需要將圖形界面權限放開。

No protocol specified

Exception in thread “main” org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]

at org.eclipse.swt.SWT.error(SWT.java:4109)at org.eclipse.swt.widgets.Display.createDisplay(Display.java:902)at org.eclipse.swt.widgets.Display.create(Display.java:890)at org.eclipse.swt.graphics.Device.<init>(Device.java:154)at org.eclipse.swt.widgets.Display.<init>(Display.java:499)at org.eclipse.swt.widgets.Display.<init>(Display.java:490)at org.eclipse.swt.widgets.Display.getDefault(Display.java:1693)at org.eclipse.swt.widgets.Shell.<init>(Shell.java:260)at org.eclipse.swt.widgets.Shell.<init>(Shell.java:358)at org.eclipse.jface.window.Window.createShell(Window.java:487)at org.eclipse.jface.window.Window.create(Window.java:430)at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1089)at org.eclipse.jface.window.Window.open(Window.java:790)at com.dameng.install.ui.MainApplication.run(Unknown Source)at com.dameng.install.ui.MainApplication.main(Unknown Source)

[dmdba@localhost mnt]$

解決方法 切換到root用戶后在命令行中輸入xhost +，可以使得dmdba可以調用圖形界面進行安裝。

利用DMRMAN備份時出現“管道連接失敗”的錯誤信息現象描述備份時出現 故障“管道連接失敗”
問題原因
遇到這種問題時的場景，一般是安裝時在完成安裝之前沒有注冊dmap服務，這樣的情況下需要去注冊并啟動dmap服務；也有可能是dmap服務被意外關閉，這種情況下啟動dmap服務即可。

解決方法

1、重啟dmap服務

若沒有注冊dmap服務，有三種啟動方式可供參考：

1.前臺啟動dmap

前臺啟動dmap，在安裝路徑下的bin目錄下，用./dmap即可啟動dmap服務，但在前臺啟動的方式下，關閉啟動的當前窗口，dmap即會被關閉。

2.后臺啟動dmap

以這種方式啟動dmap，在關閉當前窗口后dmap服務不會被關閉。

3.通過腳本注冊dmap服務，用服務方式啟動

利用腳本進行dmap服務注冊并啟動，在完整的軟件安裝過程中，在完成安裝前原本應該以root身份運行腳本來注冊啟動dmap的。腳本在$DM_HOME/root目錄下。

總結

以上是生活随笔為你收集整理的达梦数据库一些疑难杂症的解决的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。