使用0备初始化HDR的问题，求解答！在使用0备初始化HDR的时候，如果0备在备机物理恢复完成后，主机的逻辑日志已经出现了覆盖的情况，但是有这部分逻辑日志的备份。应该在备机上如何操作，才能完成HDR的初始化。测试环境11.7+RH6测试备机直接执行ontape -l -C后，应用日志备份后，这时备机fast recovery状态，onmode -d s...在使用0备初始化HDR的时候，如果0备在备机物理恢复完成后，主机的逻辑日志已经出现了覆盖的情况，但是有这部分逻辑日志的备份。应该在备机上如何操作，才能完成HDR的初始化。测试环境11.7+RH6测试备机直接执行ontape -l -C后，应用日志备份后，这时备机fast recovery状态，onmode -d secondary xxx后，备机直接挂掉。如果在备机执行了ontape -l -C后，执行ontape -l -X,备机会进入Qes模式，onmode -ky后，oninit -PHY启动到fast recovery状态，在onmode -d secondary xxx后，备机转化为secondary模式，但是主机onmode -l后，备机不同步，使用onstat -g dri 发现state是off的。关注问题9回答信息分析/架构师
, 回复 7# archivezip 来一个操作示例给你。。ontape -ponmode -d secondaryontape -linformix@suse10sp4:/home/idshdr> onstat -lshared memory not initialized for INFORMIXSERVER 'idshdr'informix@suse10sp4:/home/idshdr> ontape -p -t STDIO < /home/idspri/fullba...回复
archivezip 来一个操作示例给你。。ontape -ponmode -d secondaryontape -linformix@suse10sp4:/home/idshdr> onstat -lshared memory not initialized for INFORMIXSERVER 'idshdr'informix@suse10sp4:/home/idshdr> ontape -p -t STDIO < /home/idspri/fullbakinformix@suse10sp4:/home/idshdr> onstat -mIBM Informix Dynamic Server Version 11.50.FC9W3 -- Fast Recovery -- Up 00:00:21 -- 245384 KbytesMessage Log File: /home/informix/tmp/online_idshdr.log04:36:11&&Maximum server connections 0 04:36:11&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 0, Llog used 004:36:11&&Checkpoint Completed:&&duration was 0 seconds.04:36:11&&Wed Mar 26 - loguniq 13, logpos 0xf018, timestamp: 0x7d30f Interval: 10704:36:11&&Maximum server connections 0 04:36:11&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 0, Llog used 004:36:11&&Increasing # of AIO VPs to 304:36:12&&Physical Restore of rootdbs, userdbs Completed.04:36:12&&Checkpoint Completed:&&duration was 0 seconds.04:36:12&&Wed Mar 26 - loguniq 13, logpos 0xf018, timestamp: 0x7d318 Interval: 10704:36:12&&Maximum server connections 0 04:36:13&&DR: Local and Remote server type and/or last change(LC) incompatible& && && && &&&[Local&&type: Invalid,& & LC: DR has not been initialized.]& && && && &&&[Remote type: Invalid,& & LC: ]informix@suse10sp4:/home/idshdr> onstat -mIBM Informix Dynamic Server Version 11.50.FC9W3 -- Fast Recovery -- Up 00:00:22 -- 245384 KbytesMessage Log File: /home/informix/tmp/online_idshdr.log04:36:11&&Maximum server connections 0 04:36:11&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 0, Llog used 004:36:11&&Checkpoint Completed:&&duration was 0 seconds.04:36:11&&Wed Mar 26 - loguniq 13, logpos 0xf018, timestamp: 0x7d30f Interval: 10704:36:11&&Maximum server connections 0 04:36:11&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 0, Llog used 004:36:11&&Increasing # of AIO VPs to 304:36:12&&Physical Restore of rootdbs, userdbs Completed.04:36:12&&Checkpoint Completed:&&duration was 0 seconds.04:36:12&&Wed Mar 26 - loguniq 13, logpos 0xf018, timestamp: 0x7d318 Interval: 10704:36:12&&Maximum server connections 0 04:36:13&&DR: Local and Remote server type and/or last change(LC) incompatible& && && && &&&[Local&&type: Invalid,& & LC: DR has not been initialized.]& && && && &&&[Remote type: Invalid,& & LC: ]informix@suse10sp4:/home/idshdr> onmode -d secondary idspriinformix@suse10sp4:/home/idshdr> onstat -lIBM Informix Dynamic Server Version 11.50.FC9W3 -- Fast Recovery (Sec) -- Up 00:00:37 -- 245384 KbytesPhysical LoggingBuffer bufused&&bufsize&&numpages& &numwrits& &pages/io&&P-1&&2& && &&&128& && &1& && && & 0& && && & 0.00& && &phybegin& && && &physize& & phypos& &&&phyused& & %used& && && &1:263& && && && &5000& && & 4197& && & 2& && && & 0.04& & Logical LoggingBuffer bufused&&bufsize&&numrecs& & numpages& &numwrits& &recs/pages pages/io&&L-1&&0& && &&&128& && &0& && && & 0& && && & 0& && && & 0.0& && &&&0.0& &&&& && &&&Subsystem& & numrecs& & Log Space usedaddress& && && & number& &flags& & uniqid& &begin& && && && && & size& &&&used& & %used4b9bd850& && && &1& && &&&U---C-L&&13& && & 1:5263& && && && && &2500& && & 17& &&&0.684b9bd8b8& && && &2& && &&&F------&&0& && &&&1:7763& && && && && &2500& && &&&0& &&&0.004b9bd920& && && &3& && &&&F------&&0& && &&&1:10263& && && && &&&2500& && &&&0& &&&0.004b9bd988& && && &4& && &&&F------&&0& && &&&1:12763& && && && &&&2500& && &&&0& &&&0.004b9bd9f0& && && &5& && &&&F------&&0& && &&&1:15263& && && && &&&2500& && &&&0& &&&0.004b9bda58& && && &6& && &&&F------&&0& && &&&1:17763& && && && &&&2500& && &&&0& &&&0.00 6 active, 6 totalinformix@suse10sp4:/home/idshdr> onstat -mIBM Informix Dynamic Server Version 11.50.FC9W3 -- Fast Recovery (Sec) -- Up 00:00:40 -- 245384 KbytesMessage Log File: /home/informix/tmp/online_idshdr.log04:36:12&&Physical Restore of rootdbs, userdbs Completed.04:36:12&&Checkpoint Completed:&&duration was 0 seconds.04:36:12&&Wed Mar 26 - loguniq 13, logpos 0xf018, timestamp: 0x7d318 Interval: 10704:36:12&&Maximum server connections 0 04:36:13&&DR: Local and Remote server type and/or last change(LC) incompatible& && && && &&&[Local&&type: Invalid,& & LC: DR has not been initialized.]& && && && &&&[Remote type: Invalid,& & LC: ]04:36:25&&DR: Local and Remote server type and/or last change(LC) incompatible& && && && &&&[Local&&type: Invalid,& & LC: DR has not been initialized.]& && && && &&&[Remote type: Primary,& & LC: ]04:36:36&&DR: Reservation of the last logical log for log backup turned off04:36:36&&DR: new type = secondary, primary server name = idspri 04:36:36&&DR: Trying to connect to primary server = idspri04:36:38&&DR: Secondary server connected04:36:39&&DR: Secondary server needs failure recovery04:36:40&&DR: Start failure recovery from tape ... informix@suse10sp4:/home/idshdr> ontape -lRoll forward should start with log number 13Restore will use log backup file /home/idspri/logbak/suse10sp4_12_Log. Press Return to continue ...Rollforward log file /home/idspri/logbak/suse10sp4_12_Log ...Rollforward log file /home/idspri/logbak/suse10sp4_12_Log ...Program over.informix@suse10sp4:/home/idshdr> onstat -lIBM Informix Dynamic Server Version 11.50.FC9W3 -- Read-Only (Sec) -- Up 00:00:50 -- 245384 KbytesPhysical LoggingBuffer bufused&&bufsize&&numpages& &numwrits& &pages/io&&P-1&&17& && & 128& && &16& && && &0& && && & 0.00& && &phybegin& && && &physize& & phypos& &&&phyused& & %used& && && &1:263& && && && &5000& && & 4197& && & 17& && && &0.34& & Logical LoggingBuffer bufused&&bufsize&&numrecs& & numpages& &numwrits& &recs/pages pages/io&&L-1&&0& && &&&128& && &0& && && & 0& && && & 0& && && & 0.0& && &&&0.0& &&&& && &&&Subsystem& & numrecs& & Log Space usedaddress& && && & number& &flags& & uniqid& &begin& && && && && & size& &&&used& & %used4b9bd850& && && &1& && &&&U-B---L&&13& && & 1:5263& && && && && &2500& && & 23& &&&0.924b9bd8b8& && && &2& && &&&U-B----&&14& && & 1:7763& && && && && &2500& && &&&9& &&&0.364b9bd920& && && &3& && &&&U---C--&&15& && & 1:10263& && && && &&&2500& && &&&6& &&&0.244b9bd988& && && &4& && &&&F------&&0& && &&&1:12763& && && && &&&2500& && &&&0& &&&0.004b9bd9f0& && && &5& && &&&F------&&0& && &&&1:15263& && && && &&&2500& && &&&0& &&&0.004b9bda58& && && &6& && &&&F------&&0& && &&&1:17763& && && && &&&2500& && &&&0& &&&0.00 6 active, 6 total赞同信息分析/架构师
, 这种情况下，逻辑日志必须备份，然后在备机上进行逻辑日志恢复。如果没有逻辑日志备份和备机恢复，那么是无法进行建立HDR的。HDR（以及RSS）的关键点是检查点同步，如果逻辑日志覆盖，那么检查点就无法同步了，故HDR无法创建。...这种情况下，逻辑日志必须备份，然后在备机上进行逻辑日志恢复。如果没有逻辑日志备份和备机恢复，那么是无法进行建立HDR的。HDR（以及RSS）的关键点是检查点同步，如果逻辑日志覆盖，那么检查点就无法同步了，故HDR无法创建。赞同系统工程师
, boco回复 2# liaosnet 我在测试环境也尝试应用了日志的备份，但是出现的问题如我所描述的，是否有官方一点的操作文档。另外有没有onbar初始化hdr的官方文档。回复
liaosnet 我在测试环境也尝试应用了日志的备份，但是出现的问题如我所描述的，是否有官方一点的操作文档。另外有没有onbar初始化hdr的官方文档。赞同信息分析/架构师
, ====原始=====备机上的操作应该是ontape -p&&仅执行物理恢复。在物理恢复完成后，会提示是会进行逻辑恢复，如果是，继续执行到ontape -l 直到恢复至主机当前的逻辑日志之前，即可进行onmode -d secondary (前提是主机已经执行onmode -d primary)ontape -p后再ontape -...====原始=====备机上的操作应该是ontape -p&&仅执行物理恢复。在物理恢复完成后，会提示是会进行逻辑恢复，如果是，继续执行到ontape -l 直到恢复至主机当前的逻辑日志之前，即可进行onmode -d secondary (前提是主机已经执行onmode -d primary)ontape -p后再ontape -l 后，就相当于ontape -r了。。======修正=======备机上的操作应该是ontape -p&&仅执行物理恢复。物理恢复完成后，执行onmode -d secondary (前提是主机已经执行onmode -d primary)待日志中提示04:36:39&&DR: Secondary server needs failure recovery04:36:40&&DR: Start failure recovery from tape ... 时，执行ontape -l进行从逻辑日志备份中恢复（需要恢复主机上已经备份的所有逻辑日志），而后自动从主机同步完成创建HDR。赞同系统工程师
, boco回复 4# liaosnet 在ontape -l恢复完后，备机进入Qes模式，onmode -ky,oninit -PHY,onmode -d secondary xxx,备机报错挂了，不知道什么原因?03:12:05&&IBM Informix Dynamic Server Started.Tue Jun 10 03:12:06 :06&&Event alarms enabled.&nbs...回复
liaosnet 在ontape -l恢复完后，备机进入Qes模式，onmode -ky,oninit -PHY,onmode -d secondary xxx,备机报错挂了，不知道什么原因?03:12:05&&IBM Informix Dynamic Server Started.Tue Jun 10 03:12:06 201403:12:06&&Event alarms enabled.&&ALARMPROG = '/opt/informix/etc/alarmprogram.sh'03:12:06&&Booting Language
from module 03:12:06&&Loading Module 03:12:06&&Booting Language
from module 03:12:06&&Loading Module 03:12:11&&DR: DRAUTO is 2 (Reverse)03:12:11&&DR: ENCRYPT_HDR is 0 (HDR encryption Disabled)03:12:11&&Event notification facility epoll enabled.03:12:11&&IBM Informix Dynamic Server Version 11.70.UC5TL Software Serial Number AAA#B00000003:12:11&&Your evaluation license will expire on
00:00:0003:12:12&&IBM Informix Dynamic Server Initialized -- Shared Memory Initialized.03:12:12&&Started 1 B-tree scanners.03:12:12&&B-tree scanner threshold set at 5000.03:12:12&&B-tree scanner range scan size set to -1.03:12:12&&B-tree scanner ALICE mode set to 6.03:12:12&&B-tree scanner index compression level set to med.03:12:12&&DR: Reservation of the last logical log for log backup turned on03:12:12&&Data replication type and state information reset. To start DR, use& && && & the 'onmode -d' command and wait for the pair to be operational,& && && & before shutting down the database server03:12:12&&Warning: Invalid (non-existent/blobspace/disabled) dbspace listed& && && && && && & in DBSPACETEMP: 'TEMPDBS1'03:12:12&&Warning: Invalid (non-existent/blobspace/disabled) dbspace listed& && && && && && & in DBSPACETEMP: 'TEMPDBS2'03:12:12&&Dataskip is now OFF for all dbspaces03:12:12&&Restartable Restore has been ENABLED03:12:12&&Recovery Mode03:12:12&&DR: Local and Remote server type and/or last change(LC) incompatible& && && && &&&[Local&&type: Invalid,& & LC: DR has not been initialized.]& && && && &&&[Remote type: Invalid,& & LC: ]03:12:15&&Physical Restore of rootdbs, plogdbs, llogdbs started.03:12:17&&Checkpoint Completed:&&duration was 0 seconds.03:12:17&&Tue Jun 10 - loguniq 60, logpos 0x8018, timestamp: 0xaa5d3 Interval: 55303:12:17&&Maximum server connections 0 03:12:17&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 0, Llog used 003:12:17&&Checkpoint Completed:&&duration was 0 seconds.03:12:17&&Tue Jun 10 - loguniq 60, logpos 0x8018, timestamp: 0xaa5d9 Interval: 55403:12:17&&Maximum server connections 0 03:12:17&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 0, Llog used 003:12:17&&Checkpoint Completed:&&duration was 0 seconds.03:12:17&&Tue Jun 10 - loguniq 60, logpos 0x8018, timestamp: 0xaa5df Interval: 55503:12:17&&Maximum server connections 0 03:12:17&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 0, Llog used 003:12:18&&Physical Restore of rootdbs, plogdbs, llogdbs Completed.03:12:18&&Checkpoint Completed:&&duration was 0 seconds.03:12:18&&Tue Jun 10 - loguniq 60, logpos 0x8018, timestamp: 0xaa5ed Interval: 55503:12:18&&Maximum server connections 0 03:12:23&&Logical Recovery Started.03:12:23&&10 recovery worker threads will be started.03:12:23&&Dynamically allocated new virtual shared memory segment (size 8192KB)03:12:23&&Memory sizes:resident:111516 KB, virtual:40848 KB, no SHMTOTAL limit03:12:23&&Warning: Invalid (non-existent/blobspace/disabled) dbspace listed& && && && && && & in DBSPACETEMP: 'TEMPDBS1'03:12:23&&Warning: Invalid (non-existent/blobspace/disabled) dbspace listed& && && && && && & in DBSPACETEMP: 'TEMPDBS2'03:12:23&&Checkpoint Completed:&&duration was 0 seconds.03:12:23&&Tue Jun 10 - loguniq 60, logpos 0x8018, timestamp: 0xaa5ef Interval: 55503:12:23&&Maximum server connections 0 03:12:23&&Start Logical Recovery - Start Log 60, End Log ?03:12:23&&Starting Log Position - 60 0x801803:12:23&&Clearing the physical and logical logs has started03:12:24&&DR: Local and Remote server type and/or last change(LC) incompatible& && && && &&&[Local&&type: Invalid,& & LC: DR has not been initialized.]& && && && &&&[Remote type: Primary,& & LC: ]03:12:36&&Cleared 2070 MB of the physical and logical logs in 12 seconds03:12:36&&Logical Log 60 Complete, timestamp: 0xaa624.03:12:36&&Logical Log 61 Complete, timestamp: 0xaa639.03:12:36&&DR: Local and Remote server type and/or last change(LC) incompatible& && && && &&&[Local&&type: Invalid,& & LC: DR has not been initialized.]& && && && &&&[Remote type: Primary,& & LC: ]03:12:37&&Logical Log 62 Complete, timestamp: 0xaa643.03:12:37&&Checkpoint Completed:&&duration was 0 seconds.03:12:37&&Tue Jun 10 - loguniq 63, logpos 0xc018, timestamp: 0xaa66d Interval: 55603:12:37&&Maximum server connections 0 03:12:37&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 18, Llog used 003:12:38&&Logical Log 63 Complete, timestamp: 0xaa66d.03:12:38&&Checkpoint Completed:&&duration was 0 seconds.03:12:38&&Tue Jun 10 - loguniq 64, logpos 0x8018, timestamp: 0xaa69a Interval: 55703:12:38&&Maximum server connections 0 03:12:38&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 14, Llog used 003:12:39&&Logical Log 64 Complete, timestamp: 0xaa69a.03:12:40&&Logical Log 65 Complete, timestamp: 0xaa6af.03:12:40&&Checkpoint Completed:&&duration was 0 seconds.03:12:40&&Tue Jun 10 - loguniq 66, logpos 0xc018, timestamp: 0xaa6d6 Interval: 55803:12:40&&Maximum server connections 0 03:12:40&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 14, Llog used 003:12:40&&Checkpoint Completed:&&duration was 0 seconds.03:12:40&&Tue Jun 10 - loguniq 66, logpos 0xe018, timestamp: 0xaa6db Interval: 55903:12:40&&Maximum server connections 0 03:12:40&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 2, Llog used 003:12:40&&Checkpoint Completed:&&duration was 0 seconds.03:12:40&&Tue Jun 10 - loguniq 66, logpos 0x11018, timestamp: 0xaa6e0 Interval: 56003:12:40&&Maximum server connections 0 03:12:40&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 0, Llog used 003:12:41&&Logical Log 66 Complete, timestamp: 0xaa700.03:12:41&&Checkpoint Completed:&&duration was 0 seconds.03:12:41&&Tue Jun 10 - loguniq 67, logpos 0xf018, timestamp: 0xaa738 Interval: 56103:12:41&&Maximum server connections 0 03:12:41&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 15, Llog used 003:12:41&&Checkpoint Completed:&&duration was 0 seconds.03:12:41&&Tue Jun 10 - loguniq 67, logpos 0x1b018, timestamp: 0xaa76e Interval: 56203:12:41&&Maximum server connections 0 03:12:41&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 16, Llog used 003:12:42&&Logical Log 67 Complete, timestamp: 0xaa76e.03:12:42&&Checkpoint Completed:&&duration was 0 seconds.03:12:42&&Tue Jun 10 - loguniq 68, logpos 0x4018, timestamp: 0xaa790 Interval: 56303:12:42&&Maximum server connections 0 03:12:42&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 13, Llog used 003:12:43&&Logical Log 68 Complete, timestamp: 0xaa7a5.03:12:43&&Checkpoint Completed:&&duration was 0 seconds.03:12:43&&Tue Jun 10 - loguniq 69, logpos 0x4018, timestamp: 0xaa7b8 Interval: 56403:12:43&&Maximum server connections 0 03:12:43&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 13, Llog used 003:12:43&&Checkpoint Completed:&&duration was 0 seconds.03:12:43&&Tue Jun 10 - loguniq 69, logpos 0x4d018, timestamp: 0xaa8a4 Interval: 56503:12:43&&Maximum server connections 0 03:12:43&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 16, Llog used 003:12:43&&Checkpoint Completed:&&duration was 0 seconds.03:12:43&&Tue Jun 10 - loguniq 69, logpos 0x72018, timestamp: 0xaa931 Interval: 56603:12:43&&Maximum server connections 0 03:12:43&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 17, Llog used 003:12:44&&Logical Recovery has reached the transaction cleanup phase.03:12:44&&Checkpoint Completed:&&duration was 0 seconds.03:12:44&&Tue Jun 10 - loguniq 70, logpos 0x18, timestamp: 0xaad62 Interval: 56703:12:44&&Maximum server connections 0 03:12:44&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 2, Llog used 103:12:44&&Logical Recovery Complete.& && && & 236 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks03:12:44&&Logical Recovery Complete.03:12:44&&Quiescent Mode03:12:44&&Checkpoint Completed:&&duration was 0 seconds.03:12:44&&Tue Jun 10 - loguniq 70, logpos 0x2018, timestamp: 0xaad77 Interval: 56803:12:44&&Maximum server connections 0 03:12:44&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 3, Llog used 203:12:48&&Defragmenter cleaner thread now running03:12:48&&Defragmenter cleaner thread cleaned:0 partitions03:12:48&&DR: Local and Remote server type and/or last change(LC) incompatible& && && && &&&[Local&&type: Invalid,& & LC: DR has not been initialized.]& && && && &&&[Remote type: Primary,& & LC: ]03:12:55&&WARNING: Modifying the setting of LTAPEDEV to the null device willallow log files to be overwritten without being backed up. It will not bepossible to roll forward any logs past the most recently backed up log file.Be especially careful with this LTAPEDEV setting in a replication environment.03:12:55&&Value of LTAPEDEV has been changed to /dev/null.03:13:00&&DR: Local and Remote server type and/or last change(LC) incompatible& && && && &&&[Local&&type: Invalid,& & LC: DR has not been initialized.]& && && && &&&[Remote type: Primary,& & LC: ]03:13:02&&Checkpoint Completed:&&duration was 0 seconds.03:13:02&&Tue Jun 10 - loguniq 70, logpos 0x4018, timestamp: 0xaad80 Interval: 56903:13:02&&Maximum server connections 0 03:13:02&&Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 0, Llog used 203:13:03&&IBM Informix Dynamic Server Stopped.03:13:10&&IBM Informix Dynamic Server Started.Tue Jun 10 03:13:11 201403:13:11&&Event alarms enabled.&&ALARMPROG = '/opt/informix/etc/alarmprogram.sh'03:13:11&&Booting Language
from module 03:13:11&&Loading Module 03:13:11&&Booting Language
from module 03:13:11&&Loading Module 03:13:16&&DR: DRAUTO is 2 (Reverse)03:13:16&&DR: ENCRYPT_HDR is 0 (HDR encryption Disabled)03:13:16&&Event notification facility epoll enabled.03:13:16&&IBM Informix Dynamic Server Version 11.70.UC5TL Software Serial Number AAA#B00000003:13:16&&Your evaluation license will expire on
00:00:0003:13:17&&IBM Informix Dynamic Server Initialized -- Shared Memory Initialized.03:13:17&&Started 1 B-tree scanners.03:13:17&&B-tree scanner threshold set at 5000.03:13:17&&B-tree scanner range scan size set to -1.03:13:17&&B-tree scanner ALICE mode set to 6.03:13:17&&B-tree scanner index compression level set to med.03:13:17&&Data replication type and state information reset. To start DR, use& && && & the 'onmode -d' command and wait for the pair to be operational,& && && & before shutting down the database server03:13:17&&Warning: Invalid (non-existent/blobspace/disabled) dbspace listed& && && && && && & in DBSPACETEMP: 'TEMPDBS1'03:13:17&&Warning: Invalid (non-existent/blobspace/disabled) dbspace listed& && && && && && & in DBSPACETEMP: 'TEMPDBS2'03:13:17&&Physical Recovery Started at Page (2:11746).03:13:17&&Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored.03:13:17&&Dataskip is now OFF for all dbspaces03:13:17&&Restartable Restore has been ENABLED03:13:17&&Recovery Mode03:13:22&&DR: Local and Remote server type and/or last change(LC) incompatible& && && && &&&[Local&&type: Invalid,& & LC: DR has not been initialized.]& && && && &&&[Remote type: Invalid,& & LC: ]03:13:30&&DR: new type = secondary, primary server name = sdspri 03:13:30&&DR: Trying to connect to primary server = sdspri03:13:34&&DR: Secondary server connected03:13:35&&DR: Secondary server needs failure recovery03:13:36&&DR: Failure recovery from disk in progress ... 03:13:36&&Logical Recovery Started.03:13:36&&10 recovery worker threads will be started.03:13:36&&Dynamically allocated new virtual shared memory segment (size 8192KB)03:13:36&&Memory sizes:resident:111516 KB, virtual:40848 KB, no SHMTOTAL limit03:13:36&&Warning: Invalid (non-existent/blobspace/disabled) dbspace listed& && && && && && & in DBSPACETEMP: 'TEMPDBS1'03:13:36&&Warning: Invalid (non-existent/blobspace/disabled) dbspace listed& && && && && && & in DBSPACETEMP: 'TEMPDBS2'03:13:36&&Start Logical Recovery - Start Log 70, End Log ?03:13:36&&Starting Log Position - 70 0x401803:13:37&&DR: Cleared 19990 KB of logical log in 0 seconds.03:13:37&&Defragmenter cleaner thread now running03:13:37&&Defragmenter cleaner thread cleaned:0 partitions03:13:37&&Checkpoint Record not Found in Logical Log.03:13:37&&DR_ERR set to -503:13:37&&Assert Failed: DR: Log Record Apply Thread Exited Abnormally. Internal Error.& && && && &&&A restart of the database server shall be required to correct& && && && &&&this problem.03:13:37&&IBM Informix Dynamic Server Version 11.70.UC5TL03:13:37& &Who: Session(15, informix@, 0, 0x4af53340)& && && && && & Thread(30, dr_secapply, 4af26874, 1)& && && && && & File: hdr/hdrApply.c Line: 58403:13:37& &Results: Dynamic Server must abort03:13:37& &Action: Reinitialize shared memory03:13:37&&stack trace for pid 12337 written to /opt/informix/tmp/af.406076103:13:37& &See Also: /opt/informix/tmp/af.4060761, shmem.03:13:39&&Starting crash time check of:03:13:39&&1. memory block headers03:13:39&&2. stacks03:13:39&&Crash time checking found no problems03:13:39&&hdr/hdrApply.c, line 584, thread 30, proc id 12337, DR: Log Record Apply Thread Exited Abnormally. Internal Error.& && && && &&&A restart of the database server shall be required to correct& && && && &&&this problem..03:13:40&&The Master Daemon Died03:13:40&&PANIC: Attempting to bring system down赞同信息分析/架构师
, 回复 5# archivezip & & ontape -l 恢复完后怎么会进入模式呢？？！！应该一直处于fast recovery状态。。你能说一下你的具体操作吗？！回复
archivezip & & ontape -l 恢复完后怎么会进入模式呢？？！！应该一直处于fast recovery状态。。你能说一下你的具体操作吗？！赞同系统工程师
, boco回复 6# liaosnet
基本步骤如下主机侧：ontape -s -L 0& && & 0备ontape -c& && && && && &持续备份日志onmode -l 和onmode -c&&切换日志，覆盖0备时的当前日志onmode -d primary xxx，主...回复
基本步骤如下主机侧：ontape -s -L 0& && & 0备ontape -c& && && && && &持续备份日志onmode -l 和onmode -c&&切换日志，覆盖0备时的当前日志onmode -d primary xxx，主机改模式备机侧：ftp 0备和日志备份ontape -p 做物理恢复，结束后处于fast recovery状态ontape -l 做逻辑恢复，结束后备机处于Qes模式，无法改模式onmode -ky 停备机oninit -PHY,将备机启动到fast recovery模式onmode -d secondary xxx，改备机模式，备机报错挂了。赞同系统工程师
, boco为什么是这个顺序？ onmode -d secondary 要在ontape -l 前面做，如果是使用onbar做0备初始化HDR，是不是也要这个顺序呢。ontape -ponmode -d secondaryontape -l为什么是这个顺序？ onmode -d secondary 要在ontape -l 前面做，如果是使用onbar做0备初始化HDR，是不是也要这个顺序呢。ontape -ponmode -d secondaryontape -l赞同信息分析/架构师
, 回复 9# archivezip & & ontape -p后再ontape -l 后，就相当于ontape -r了。。回复
archivezip & & ontape -p后再ontape -l 后，就相当于ontape -r了。。赞同撰写回答系统工程师, boco关注发布23回答11请稍候...}