SQL 复制环境，进程不能进程正常停止

最新推荐文章于 2021-12-22 14:16:44 发布
最新推荐文章于 2021-12-22 14:16:44 发布
阅读量448 收藏
点赞数
分类专栏： DB2 SQL Replication
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_40658897/article/details/87483377
版权
  1. 环境
    DB2 9.5
    SQL Replication

背景信息：
DBA 团队维护人员发现数据库维护脚本长期执行，没有停止下来。
检查日志找到Apply进程没有停止下来。

  1. 问题现象：
    SQL复制的Apply端进程不能正常停止。
    Apply日志显示一直在运行过程中。 没有接收到STOP命令的信号，导致数据库周维护脚本不能继续向下进行。

尝试停止Apply进程的脚本日志：

Maintain check end: Sun Feb 3 11:27:21 BRST 2019
End 
Step 2: Stop_Apply
Start to force application
DB20000I The FORCE APPLICATION command completed successfully.
DB21024I This command is asynchronous and may not be effective immediately.

There are 0 applications connecting to PROM_DW currently
2019-02-03-11.27.22.663296 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.27.30.670859 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).
2019-02-03-11.27.30.698669 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.27.38.704735 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).
2019-02-03-11.27.38.730952 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.27.46.736826 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).
2019-02-03-11.27.46.765199 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.27.54.771442 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).
2019-02-03-11.27.54.800140 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.28.02.806075 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).
2019-02-03-11.28.02.834397 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.28.10.840373 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).
2019-02-03-11.28.20.929295 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.28.28.935275 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).
2019-02-03-11.28.28.963148 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.28.36.969152 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).
2019-02-03-11.28.36.997498 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.28.45.003476 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).
2019-02-03-11.28.45.031106 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.28.53.037173 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).
2019-02-03-11.28.53.065487 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.29.01.071580 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).
2019-02-03-11.29.01.099321 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.29.09.105558 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).
2019-02-03-11.29.19.192983 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.29.27.199061 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).
2019-02-03-11.29.27.226878 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.29.35.232951 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).
2019-02-03-11.29.35.261635 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.29.43.267691 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).
2019-02-03-11.29.43.295588 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.29.51.301679 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).
2019-02-03-11.29.51.329809 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.29.59.335915 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).
2019-02-03-11.29.59.363234 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.30.07.369353 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).
2019-02-03-11.30.17.458325 ASN0600I "AsnAcmd" : "" : "Initial" : Program "applycmd 9.5.10" is starting.
2019-02-03-11.30.25.464664 ASN0506E "AsnAcmd" : "TEST001" : "Initial" : The command was not processed because the target replication program "Apply" was not running or because you entered an incorrect parameter value (for example, a server name, schema, or qualifier might be misspelled).

Apply的日志。

2019-02-03-11.27.13.662269 <CPREST(01/00)> ASN1044I APPLY "TEST001" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-03-11.28.13.706808 <CPREST(01/00)> ASN1044I APPLY "TEST001" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-03-11.29.13.759718 <CPREST(01/00)> ASN1044I APPLY "TEST001" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-03-11.30.13.804167 <CPREST(01/00)> ASN1044I APPLY "TEST001" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-03-11.31.13.846738 <CPREST(01/00)> ASN1044I APPLY "TEST001" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-03-11.32.13.892540 <CPREST(01/00)> ASN1044I APPLY "TEST001" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-03-11.33.13.936337 <CPREST(01/00)> ASN1044I APPLY "TEST001" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-03-11.34.13.992169 <CPREST(01/00)> ASN1044I APPLY "TEST001" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-03-11.35.14.034834 <CPREST(01/00)> ASN1044I APPLY "TEST001" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-03-11.36.14.080520 <CPREST(01/00)> ASN1044I APPLY "TEST001" : "WorkerThread". The Apply program will become inactive for "0" minutes and "59" seconds.
2019-02-03-11.37.13.128013 <CPREST(01/00)> ASN1044I APPLY "TEST001" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-03-11.38.13.173299 <CPREST(01/00)> ASN1044I APPLY "TEST001" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-03-11.39.13.229953 <CPREST(01/00)> ASN1044I APPLY "TEST001" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-03-11.40.13.274607 <CPREST(01/00)> ASN1044I APPLY "TEST001" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds

3：在测试环境中重现，发现不能重现这个问题。 SQL复制都可以正常停止下来。
测试环境中显示的Apply端停止的日志。

测试环境中都会收到这个命令“ The program received the “STOP” command.”

2019-02-15-14.25.14.889290 <cmdsEngine> ASN0522I  "Apply" : "MYQUAL1" : "Initial" : The program received the "STOP" command.
	2019-02-15-14.25.16.891334 <asnThread::stop> ASN0590I  "Apply" : "MYQUAL1" : "Initial" The thread "Initial" received return code "2011" from the exiting thread "AdminThread".
	2019-02-15-14.25.22.895746 <asnThread::stop> ASN0590I  "Apply" : "MYQUAL1" : "Initial" The thread "Initial" received return code "2011" from the exiting thread "WorkerThread".
	2019-02-15-14.25.22.895926 <Asnenv:delEnvIpcQRcvHdl> ASN0595I  "Apply" : "MYQUAL1" : "Initial" The program removed an IPC queue with keys "(0x3000d6a9, 0x3100d6a9, 0x3200d6a9)".
	2019-02-15-14.25.22.895943 <asnThread::stop> ASN0590I  "Apply" : "MYQUAL1" : "Initial" The thread "Initial" received return code "0" from the exiting thread "HoldLThread".
	2019-02-15-14.25.22.896008 <erWhatSignal> ASN0591I  "Apply" : "MYQUAL1" : "HoldLThread" The thread "HoldLThread" received "Handled" signal "SIGUSR2".

4：问题的原因：
经过咨询IBM工程师，怀疑是临时文件夹中IPC文件被删除。有可能导致这个问题。
https://www.ibm.com/support/docview.wss?uid=swg21289248
其实自己也查到了这篇technote.但是没有仔细的研究这段话的含义。
看到technote中报错日志和我环境的日志没有类似的，就排除掉了。

个人怀疑这个文件记录了SQL复制启动的进程号的信息。
SQL复制正常启动时候会一直挂住发出启动命令的那个进程。 如果这个进程被关闭了。数据库也会停止的。所以这个IPC文件被删除了，当停止命令发出来以后，找不到对应的进程信息，所以日志中看到没有收到STOP命令。

The IPC files created by replication programs in either /tmp or TMPDIR are accidentally
deleted. These files identify IPC message queues and shared memory and are used by
asnccmd, asnqccmd, asnacmd, asnqacmd to communicate with the replication program

5：重现这个问题。

在测试环境中启动SQL复制。观察/tmp文件夹。 发现生成了一个后缀名为IPC的问题文件。 并且这些文件的是以SQL复制的一些配置进行命令的。（而且这些文件的大小是0KB）
如下：

-rw-r--r--. 1 e95q10a db2iadm1    0 Feb 16 23:16 e95q10a.SAMPLE.ASN.CAP.IPC
-rw-r--r--. 1 e95q10a db2iadm1    0 Feb 16 23:16 e95q10a.SAMPLE.MYQUAL1.APP.IPC

重现步骤：

  • 启动SQL复制 capture 和apply
  • 到tmp文件夹目录。删除这个0K大小的 IPC文件。
  • 尝试停止SQL复制的capture及apply（无论是否force掉apply及capture 对应的db2的application ）
  • 问题重现。
  • 日志不断的报错。但是capture 及apply的日志运行正常。
    日志如下：
2019-02-16-23.16.48.991344 <CPREST(01/00)> ASN1044I  APPLY "MYQUAL1" : "WorkerThread". The Apply program will become inactive for "0" minutes and "33" seconds.
2019-02-16-23.17.21.998772 <CPREST(01/00)> ASN1044I  APPLY "MYQUAL1" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-16-23.18.22.004724 <CPREST(01/00)> ASN1044I  APPLY "MYQUAL1" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-16-23.19.22.011058 <CPREST(01/00)> ASN1044I  APPLY "MYQUAL1" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-16-23.20.22.022288 <CPREST(01/00)> ASN1044I  APPLY "MYQUAL1" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-16-23.21.22.031237 <CPREST(01/00)> ASN1044I  APPLY "MYQUAL1" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-16-23.22.22.038483 <CPREST(01/00)> ASN1044I  APPLY "MYQUAL1" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-16-23.23.22.046662 <CPREST(01/00)> ASN1044I  APPLY "MYQUAL1" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-16-23.24.22.057401 <CPREST(01/00)> ASN1044I  APPLY "MYQUAL1" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-16-23.25.22.065753 <CPREST(01/00)> ASN1044I  APPLY "MYQUAL1" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
2019-02-16-23.26.22.073823 <CPREST(01/00)> ASN1044I  APPLY "MYQUAL1" : "WorkerThread". The Apply program will become inactive for "1" minutes and "0" seconds.
  1. 解决方式
    临时解决方案：
    如果遇到这种情况。其实是可以使用操作系统命令直接Kill掉的。
    kill掉以后也不会启动不起来。
    脚本中可以这样写：
kill -9 ` ps -ef|grep -v grep|grep -iE 'asncap|asnapply'  | awk '{print $2}'`

永久解决方案：
这个问题的触发原因是，SQL复制写了一个IPC文件到临时文件夹中去。
如果临时IPC文件夹被删除，就会遇到这个问题。我个人认为这个设计有缺陷，谁也不能保证临时文件不被删除。 但是DB2还是给出了一个解决方案。

设置TMPDIR环境变量。
https://www.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.swg.im.iis.repl.qrepl.doc/topics/iiyrqenvtempdir.html

apply
mkdir apply_ipc
export TMPDIR=/db2/prom_dba/PROM_DW/apply/apply_ipc
cd ~
vi .profile
#this env variable used for DB2 replication apply temp file#
export TMPDIR=/db2/prom_dba/PROM_DW/apply/apply_ipc
#this env variable used for DB2 replication apply temp file#



capture 
mkdir  capture_ipc
cd ~
vi .profiles
#this env variable used for DB2 replication capture temp file#
export TMPDIR=/db2/prom_dba/PROM/capture/capture_ipc
#this env variable used for DB2 replication capture temp file#

最后将那个technote内容附上。
Why am I getting asn0506e when trying to stop SQL/Q Apply or SQL/Q Capture?
https://www-01.ibm.com/support/docview.wss?uid=swg21289248

Technote (troubleshooting)

Problem(Abstract)
Getting ASN0506E when trying to stop SQL/Q Apply or SQL/Q Capture

Symptom
When trying to stop any of the replication programs using any of these commands -

asnccmd, asnqccmd, asnacmd, asnqacmd, ASN0506E is returned and the program is not stopped.

For example,

  1. asnqacmd apply_server=<apply_server> stop

ASN0600I “AsnQAcmd” : “” : “Initial” :Program “asnqacmd 9.1.0” is starting.
ASN0506E “AsnQAcmd” : “ASN” : “Initial” :
The command was not processed. The “Q Apply” program is presumed down.

  1. asnccmd Capture_server=<capture_server> stop

ASN0600I “AsnCcmd” : “” : “Initial” : Program “capcmd 9.1.0” is starting.
ASN0506E “AsnCcmd” : “ASN” : “Initial” : The command was not processed. The “Capture” program is presumed down.
Cause
The IPC files created by replication programs in either /tmp or TMPDIR are accidentally

deleted. These files identify IPC message queues and shared memory and are used by
asnccmd, asnqccmd, asnacmd, asnqacmd to communicate with the replication program

Environment
Linux, Unix

Diagnosing the problem
asnqacmd apply_server=<apply_server> apply_schema=<apply_schema> stop logstdout

asnqccmd capture_server=<capture_server> capture_schema=<capture_schema> stop logstdout
asnacmd apply_server=<apply_server> apply_schema=<apply_schema> stop logstdout
asnccmd capture_server=<capture_server> capture_schema=<capture_schema> stop logstdout

TMPDIR environment variable setting

Resolving the problem
If the processes do not stop due to this error, a forceful stop maybe needed. To avoid this problem, in future, please set TMPDIR environment variable to point to a directory where the SQL Apply/Q Apply program or SQL Capture/Q Capture program can write the files. Then start the SQL Apply/Q Apply or SQL Capture/Q Capture program.

weixin_40658897
关注
专栏目录
各种数据库查询运行中的sql以及终止进程
s07aser123的专栏
11-23 1347
查询各种数据源，查询运行中的sql以及终止进程总结。
不停机进行数据库克隆的实验
cuidai9315的博客
04-08 293
目标：主库不停机，搭建出一个测试环境，允许少量的数据不同步，不用逻辑导入导出，使用rman实现 同机复制数据库-131服务器上将PROD库通过rman-duplicate target database to ...
DB2活动日志满的原因及解决与避免方案
william823的专栏
04-02 1659
下图显示了并发事务条件下，日志使用的示意 有3个并发的程序Process 1、Process 2、Process 3。每一个程序都有两个事务。蓝块代表SQL语句，红块代表commit操作，绿块代表rollback操作。每一个向下的箭头都代表日志缓冲区的数据被刷新到日志磁盘上（默认是每一次提交操作都会导致日志缓冲被刷新到磁盘上）。 在T1时刻，事务A commit，日志缓冲区被刷新到磁盘上。 在T2时刻，事务B commit，日志缓冲区被刷新到磁盘上，此时日志X使用完，但由于X中的事务C还没有提交，所
mysql 前滚指定时间_DB2关于指定时间点前滚恢复方法
weixin_32246721的博客
01-30 219
1)备份数据库[db2inst1@bytest ~ 22]$db2 backup db sample online include logsBackup successful. The timestamp for this backup image is : 20051223120837[db2inst1@bytest ~ 23]$(2)删除数据库[db2inst1@bytest ~ 5]$db2...
IBM Q复制启动停止查看状态
hbhe0316的专栏
10-06 249
1.源端启动capture https://www.cndba.cn/hbhe0316/article/4864 https://www.cndba.cn/hbhe0316/article/4864 [db2inst1@node02 scripts]$ cd /home/db2inst1/scripts [db2inst1@node01 ~]$ nohup asnqc...
SQL Server数据库复制失败的原因及解决方法
09-10
1. **服务未停止**：SQL Server的复制过程通常需要对数据库进行读写操作，当mssqlserver服务正在运行时，数据库可能处于活动状态，这会阻止复制进程正确地访问和修改数据文件，从而导致复制失败。 2. **权限问题**...
SQL Server复制功能要避开缺陷的干扰小结
12-15
然而，合并复制也有其缺点：如果无法连接到另一个服务器，复制进程将在尝试n次（默认为10次）后停止工作，直到人工干预恢复。此外，如果复制前已有数据，设置复制可能较为复杂，且在复制过程中不宜频繁更改表结构。 ...
如何优雅、安全的关闭MySQL进程
12-14
- 在主从复制环境中，主服务器处理与普通连接相同，而从服务器会依次关闭IO和SQL线程，同样标记为killed后再关闭。 5. **关闭所有线程与存储引擎** - 所有线程关闭，存储引擎关闭，表缓存刷新，所有打开的表关闭...
mysql 主从数据不一致,提示： Slave_SQL_Running: No 的解决方法
09-08
1. 首先，需要停止从服务器上的复制进程，可以通过执行以下命令实现： ``` mysql> stop slave; ``` 2. 接着，设置全局变量sql_slave_skip_counter的值，以便跳过一个或多个错误事件。例如，跳过一个错误可以设置...
Linux系统监控shell程序包-含内存cpu硬盘监控进程监控进程守护删除过期日志url监控webservice监控
02-25
sysWeblogicMonitorRestart.sh：系统weblogic监控重启（守护进程），当weblogic进程停止时调用脚本（startPssc.sh）自动重启 startPssc.sh：重启weblogic并生成带日期的日志文件 sh\utils:工具文件夹 ...
DB2 SQL复制详细手册
08-31
傻瓜式的记录DB2数据库的SQL复制操作手册，就算你不会DB2，也能根据手册把复制配置起来，本文档是针对多对一的复制，可自行根据文档配置一对一，一对多等模式。
DB2活动日志满情况分析与处理
aryoyo的博客
01-05 2313
[test@demo ~]$ db2 ? sql0964 SQL0964C The transaction log for the database is full. Explanation: All space in the transaction log is being used. 活动日志满一般有下面2种情形： 1.事务特别大，迅速占满日志空间（比如insert非常多数据)  L...
Linux下学习DB2命令的笔记
热门推荐
sunrier的专栏
08-06 4万+
本笔记接在上一篇 > http://blog.csdn.net/sunrier/article/details/7826233,学习过程中使用下载的官网DB2数据库(免费版本)测试的,由于工作中DB2是用在项目中的,而且是收费的数据库,故我只在项目编程中使用它(即公司的DB2数据库收费版本),没用来作为自己测试用。嘿嘿,所以下面的大部分操作主要来自下载的官网DB2数据库(免费版本)。
DB2 解决db2stop 停止不了，数据库仍是活动的
qq1099866969的专栏
03-19 1万+
1. [odsuser@localhost ~]$  db2stop SQL1025N  The database manager was not stopped because databases are still active 2. [odsuser@localhost ~]$ db2 force application all DB20000I  The FORCE APPLICAT
db2关闭下一句sql的日志_分析DB2活动日志满的原因及解决DB2日志满方法与避免方案...
weixin_39635314的博客
12-21 290
日志使用下图显示了并发事务条件下，日志使用的示意有3个并发的程序Process 1、Process 2、Process 3。每一个程序都有两个事务。蓝块代表SQL语句，红块代表commit操作，绿块代表rollback操作。每一个向下的箭头都代表日志缓冲区的数据被刷新到日志磁盘上(默认是每一次提交操作都会导致日志缓冲被刷新到磁盘上)。在T1时刻，事务A commit，日志缓冲区被刷新到磁盘上。在T...
DB2日志被hold导致日志空间满模拟(转载)
peace
10-09 937
  在窗口1，设置非自动提交 db2set db2options=+c  在窗口1，执行一条insert，但是不提交 $ db2 +c "insert into t1 values('leo1','leo2')" DB20000I The SQL command completed successfully. $ db2 "select * from t1" ...
DB2: 解除被锁定的表。
小旭的技术博客
12-12 2万+
解除DB2数据库中表的死锁某日无法查询DB2的数据库的某一张表，执行查询语句的后返回死锁或超时的错误:SQL0911N The current transaction has been rolled back because of a deadlockor timeout. Reason code "68". SQLSTATE=40001’ 其他的表实行数据库没有什么问题，只有一张
navicat停止正在运行的sql
wszhm123的博客
12-22 9941
今天在执行数据的时候由于其中一个表数据比较多，我正在查询的时候，修改数据字段导致数据库一直运行中。所以这个时候需要把正在运行的sql停止了。 首先：查看运行的sql show PROCESSLIST 这样我们就可以看到一些正在执行的sql 其中id就是我们要处理的 其次。杀死进程。 kill 156 最后再次查看执行的sql show PROCESSLIST 这样就看不到刚刚杀死的sql了。 ...
终止所有mysql进程_终止SQL Server中的用户进程方法
weixin_33196555的博客
01-30 1449
一、情景：在很多情况下，往往会要求数据库管理员终止SQL Server中的用户进程。本文将为大家介绍如何创建一个简单的存储过程来实现同时终止多个会话、结束连续的会话和结束连接到数据库的所有会话等功能。 在很多情况下，往往会要求数据库管理员终止SQL Serv一、情景：在很多情况下，往往会要求数据库管理员终止SQL Server中的用户进程。本文将为大家介绍如何创建一个简单的存储过程来实现同时终止多...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值