【DM版本】:DM8
【操作系统】:Win 7 专业版
【CPU】:Intel i7
【问题描述】:DM8服务突然停止,并且无法启动, 不是人为操作。
通过DM数据库配置助手,不能注册数据库服务,提示“创建数据库服务(DMServiceDMServer)失败, 请给予解答,谢谢。
日志如下:
2023-07-07 17:13:22.598 [INFO] database P0000002300 T0000000000000004644 checkpoint requested by CKPT_INTERVAL, rlog free space[536862720], used space[0]
2023-07-07 17:13:22.598 [INFO] database P0000002300 T0000000000000004644 checkpoint generate by ckpt_interval
2023-07-07 17:13:22.598 [INFO] database P0000002300 T0000000000000004468 checkpoint begin, used_space[0], free_space[536862720]...
2023-07-07 17:13:23.099 [INFO] database P0000002300 T0000000000000004468 ckpt2_log_adjust: full_status: 160, ptx_reserved: 0
2023-07-07 17:13:23.100 [INFO] database P0000002300 T0000000000000004468 ckpt2_log_adjust: ckpt_lsn(213500), ckpt_fil(0), ckpt_off(20934144), cur_lsn(213500), l_next_seq(12520), g_next_seq(12520), cur_free(20934144), total_space(536862720), used_space(0), free_space(536862720), n_ep(1)
2023-07-07 17:13:23.100 [INFO] database P0000002300 T0000000000000004468 checkpoint end, 0 pages flushed, used_space[0], free_space[536862720].
2023-07-07 17:13:38.600 [INFO] database P0000002300 T0000000000000002320 Server is stopping...
2023-07-07 17:13:38.661 [INFO] database P0000002300 T0000000000000002320 listener closed and all sessions disconnected
2023-07-07 17:13:42.779 [INFO] database P0000002300 T0000000000000002320 adjust undo_retention & wakeup purge thread...
2023-07-07 17:13:42.779 [INFO] database P0000002300 T0000000000000002320 INI parameter UNDO_RETENTION changed, the original value 0, new value 1
2023-07-07 17:13:42.798 [INFO] database P0000002300 T0000000000000002320 full check point starting...
2023-07-07 17:13:42.816 [INFO] database P0000002300 T0000000000000002320 generate force checkpoint, rlog free space[536862720], used space[0]
2023-07-07 17:13:42.816 [INFO] database P0000002300 T0000000000000004468 checkpoint begin, used_space[0], free_space[536862720]...
2023-07-07 17:13:43.016 [INFO] database P0000002300 T0000000000000004468 ckpt2_log_adjust: full_status: 160, ptx_reserved: 0
2023-07-07 17:13:43.016 [INFO] database P0000002300 T0000000000000004468 ckpt2_log_adjust: ckpt_lsn(213500), ckpt_fil(0), ckpt_off(20934144), cur_lsn(213500), l_next_seq(12520), g_next_seq(12520), cur_free(20934144), total_space(536862720), used_space(0), free_space(536862720), n_ep(1)
2023-07-07 17:13:43.016 [INFO] database P0000002300 T0000000000000004468 checkpoint end, 0 pages flushed, used_space[0], free_space[536862720].
2023-07-07 17:13:43.017 [INFO] database P0000002300 T0000000000000002320 full check point end.
2023-07-07 17:13:43.017 [INFO] database P0000002300 T0000000000000002320 shutdown audit subsystem...
2023-07-07 17:13:43.017 [INFO] database P0000002300 T0000000000000002320 shutdown schedule subsystem...
2023-07-07 17:13:43.027 [INFO] database P0000002300 T0000000000000002320 shutdown timer successfully.
2023-07-07 17:13:43.027 [INFO] database P0000002300 T0000000000000002320 pre-shutdown MAL subsystem...
2023-07-07 17:13:43.027 [INFO] database P0000002300 T0000000000000002320 shutdown worker threads subsystem...
2023-07-07 17:13:44.241 [INFO] database P0000002300 T0000000000000002320 wait for mtsk link worker to exit..
2023-07-07 17:13:44.275 [INFO] database P0000002300 T0000000000000002320 shutdown mpp session subsystem...
2023-07-07 17:13:44.275 [INFO] database P0000002300 T0000000000000002320 wait for rapply is all over...
2023-07-07 17:13:44.839 [INFO] database P0000002300 T0000000000000002320 rapply worker threads exit successfully.
2023-07-07 17:13:44.839 [INFO] database P0000002300 T0000000000000002320 pre ending task & worker threads...
2023-07-07 17:13:44.839 [INFO] database P0000002300 T0000000000000002320 shutdown dblink subsystem...
2023-07-07 17:13:45.275 [INFO] database P0000002300 T0000000000000002320 shutdown pthd_pools...
2023-07-07 17:13:45.326 [INFO] database P0000002300 T0000000000000002320 shutdown session subsystem...
2023-07-07 17:13:45.326 [INFO] database P0000002300 T0000000000000002320 shutdown aux session subsystem...
2023-07-07 17:13:45.427 [INFO] database P0000002300 T0000000000000002320 sess4_aux_tsksys_destroy, try_count:29, state:2
2023-07-07 17:13:45.801 [INFO] database P0000002300 T0000000000000002320 shutdown rollback segments purging subsystem...
2023-07-07 17:13:56.150 [INFO] database P0000002300 T0000000000000002320 ending tsk and worker threads...
2023-07-07 17:13:56.363 [INFO] database P0000002300 T0000000000000002320 ckpt2_exec_immediately begin.
2023-07-07 17:13:56.364 [INFO] database P0000002300 T0000000000000004468 checkpoint begin, used_space[0], free_space[536862720]...
2023-07-07 17:13:56.625 [INFO] database P0000002300 T0000000000000004468 ckpt2_log_adjust: full_status: 160, ptx_reserved: 0
2023-07-07 17:13:56.625 [INFO] database P0000002300 T0000000000000004468 ckpt2_log_adjust: ckpt_lsn(213663), ckpt_fil(0), ckpt_off(20934144), cur_lsn(213663), l_next_seq(12521), g_next_seq(12521), cur_free(20936704), total_space(536862720), used_space(2560), free_space(536860160), n_ep(1)
2023-07-07 17:13:56.626 [INFO] database P0000002300 T0000000000000004468 checkpoint end, 0 pages flushed, used_space[2560], free_space[536860160].
2023-07-07 17:13:56.626 [INFO] database P0000002300 T0000000000000004468 checkpoint begin, used_space[2560], free_space[536860160]...
2023-07-07 17:13:56.690 [INFO] database P0000002300 T0000000000000004468 ckpt2_log_adjust: full_status: 160, ptx_reserved: 0
2023-07-07 17:13:56.690 [INFO] database P0000002300 T0000000000000004468 ckpt2_log_adjust: ckpt_lsn(213663), ckpt_fil(0), ckpt_off(20936704), cur_lsn(213663), l_next_seq(12521), g_next_seq(12521), cur_free(20936704), total_space(536862720), used_space(0), free_space(536862720), n_ep(1)
2023-07-07 17:13:56.690 [INFO] database P0000002300 T0000000000000004468 checkpoint end, 0 pages flushed, used_space[0], free_space[536862720].
2023-07-07 17:13:56.691 [INFO] database P0000002300 T0000000000000004468 checkpoint begin, used_space[0], free_space[536862720]...
2023-07-07 17:13:56.731 [INFO] database P0000002300 T0000000000000004468 ckpt2_log_adjust: full_status: 160, ptx_reserved: 0
2023-07-07 17:13:56.732 [INFO] database P0000002300 T0000000000000004468 ckpt2_log_adjust: ckpt_lsn(213663), ckpt_fil(0), ckpt_off(20936704), cur_lsn(213663), l_next_seq(12521), g_next_seq(12521), cur_free(20936704), total_space(536862720), used_space(0), free_space(536862720), n_ep(1)
2023-07-07 17:13:56.732 [INFO] database P0000002300 T0000000000000004468 checkpoint end, 0 pages flushed, used_space[0], free_space[536862720].
2023-07-07 17:13:56.746 [INFO] database P0000002300 T0000000000000002320 shutdown archive subsystem...
2023-07-07 17:13:56.746 [INFO] database P0000002300 T0000000000000002320 OK
2023-07-07 17:13:56.747 [INFO] database P0000002300 T0000000000000002320 shutdown redo log subsystem...
2023-07-07 17:13:57.007 [INFO] database P0000002300 T0000000000000002320 rfil_close_low set main rfil[D:\dmdbms\data\WANCOM\WANCOM01.log]'s sta to inactive, l_next_seq = 12521, g_next_seq = 12521, clsn = 213663, handle = 64712, free=20936704, len=268435456
2023-07-07 17:13:57.316 [INFO] database P0000002300 T0000000000000002320 os_sema2_free, mutex name:Global\DM$INNER140590976!
2023-07-07 17:13:57.354 [INFO] database P0000002300 T0000000000000002320 shutdown MAL subsystem...
2023-07-07 17:15:23.120 [INFO] database P0000002300 T0000000000000002320 global inject hint deinit
2023-07-07 17:15:23.150 [INFO] database P0000002300 T0000000000000002320 global stat cache deinit
2023-07-07 17:15:24.071 [INFO] database P0000002300 T0000000000000002320 fil_sys_destroy
2023-07-07 17:16:20.986 [INFO] database P0000002300 T0000000000000002320 close lsnr socket
2023-07-07 17:16:21.043 [INFO] database P0000002300 T0000000000000002320 [for dem]SYSTEM SHUTDOWN SUCCESS.
2023-07-07 17:16:21.043 [INFO] database P0000002300 T0000000000000002320 DM Database Server shutdown successfully.
2023-07-07 17:16:21.044 [INFO] database P0000002300 T0000000000000002320 nsvr_notify_exit wakeup main thread to exit

1、window环境初始化实例后默认会注册数据库服务,无需单独再注册,从你的反馈来看服务是停止后无法启动,与注册实例服务无关;
2、当前日志中只能看到服务是被正常停止的,没有任何致命错误和警告错误。
建议:为直观观察具体启动失败原因,可以通过前台启动服务的方式核实具体原因,参考命令如下,路径以实际为准:
前台启动如果有报错会直接屏幕中打印,以便快速定位原因。解决后还是用后台服务方式启动服务。