放在三厂的 SAP 容灾 HANA 已配置了管理地址：

https://172.35.253.69/
用户名/密码：dell/Vip0eps(

PERFORM_CONFLICT_UC_STRUCT
CONVT_NO_NUMBER
TIME_OUT

下边需要你继续进行配置：
1. 9 块 1.92T SSD，需做 raid（5？10？）。
2. 安装操作系统，安装到 boss 卡中（240g，raid1，出厂已设置）
3. 操作系统 IP 可配置为 172.19.94.42，（网卡应做绑定？）
4. 划分逻辑卷
5. 安装 HDB

1080525318

Unable to configure the network card because the kernel device(eth0,wlan0) is not
present. This is mostly caused by missing firemware

dmesg|grep firmware

kernel-firmware' package installed.

NetXtreme BCM5720 Gigabit

select start_time from V$RMAN_BACKUP_JOB_DETAILS where input_type='•ARCHIVELOG' and
status='COMPLETED';

SELECT TO_CHAR(start_time,'MM/DD/YYYY HH24:MI:SS') from V$RMAN_BACKUP_JOB_DETAILS;

留 1 块做 hotspares
2 代 CPU 支持 SUSE 12SP3 才知道

NDC

PERFORM_CONFLICT_UC_STRUCT
UC_OBJECTS_NOT_CHARCONV(顾问账号编辑数据)

步骤 15 点击"Software"选择所要装的软件，包括"SAP BusinessOne Server Base"、"SAP

HANA Server Base"、"SAP Netweaver Server Base"、"High Availablity"。
# tar zxf ice-<x.x.x>.tar.gz
# cd ice-<x.x.x>/src/
# make install
3. Change to the driver src directory, where <x.x.x> is the version number
for the driver tar:

4. Compile the driver module:

400 884 5117 G5WS3L3

ALTER SYSTEM RECLAIM LOG;

这个改了你要重新用 GPT 分区表格盘安装系统

BIOS 模式系统盘只支持 MBR，数据盘可以 GPT
UEFI 的话系统盘也可以用 GPT

从 xtrabackup_info 获取 GTID 信息
binlog_pos = filename 'bin939.028209', position '4939', GTID of the last change
'd58351dc-66ce-11eb-bbda-005056ba484c:1-5420603775,d7221b1c-66db-11eb-b75d-
005056ba2029:1'
或：从 xtrabackup_binlog_info 获取 GTID 信息
d58351dc-66ce-11eb-bbda-005056ba484c:1-5420603775,d7221b1c-66db-11eb-b75d-
005056ba2029:1

mysqld_safe --user=mysql &

d58351dc-66ce-11eb-bbda-005056ba484c:5420603776' at master log bin939.028209

SHOW BINLOG EVENTS in 'bin939.028209' from 4939 limit 20;

| bin939.028209 | 4939 | Gtid | 939 | 5014 | SET
@@SESSION.GTID_NEXT= 'd58351dc-66ce-11eb-bbda-005056ba484c:5420603777'

SHOW BINLOG EVENTS in 'bin939.028209' from 4505 limit 20;

| bin939.028209 | 4505 | Gtid | 939 | 4580 | SET
@@SESSION.GTID_NEXT= 'd58351dc-66ce-11eb-bbda-005056ba484c:5420603776'

出错：
Last_Errno: 1032
Last_Error: Coordinator stopped because there were error(s) in
the worker(s). The most recent failure being: Worker 1 failed executing transaction
'd58351dc-66ce-11eb-bbda-005056ba484c:5420603776' at master log bin939.028209,
end_log_pos 4912. See error log and/or
performance_schema.replication_applier_status_by_worker table for more details
about this failure or others, if any.

error:
2022-01-01T23:37:46.240124+08:00 64 [ERROR] [MY-010584] [Repl] Slave SQL for
channel '': Worker 1 failed executing transaction 'd58351dc-66ce-11eb-bbda-
005056ba484c:5420603776' at master log bin939.028209, end_log_pos 4912; Could not
execute Delete_rows event on table cmip_mp.branch_table; Can't find record in
'branch_table', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's
master log FIRST, end_log_pos 4912, Error_code: MY-001032

其他都不需要 就需要根据你 apply log 里面的 MASTER_LOG_FILE MASTER_LOG_POS 重新 change 就

行
2019-07-12
赞同
评论
fengzhencai fengzhencai
CHANGE MASTER TO MASTER_HOST=' ', MASTER_PORT=3306, MASTER_USER='repl',
MASTER_PASSWORD='uyIVUpxYZ6ai', MASTER_LOG_FILE='mysql-bin.000287',
MASTER_LOG_POS=6285525 , master_auto_position=0; 用这个目前是可以，等看下同步完成，对下数
据是不是没问题，数据一致性校验 是用什么方法和工具呢 ？

reset master;
reset slave;
reset slave all;

set global gtid_purged='d58351dc-66ce-11eb-bbda-005056ba484c:1-5420603775,d7221b1c-

66db-11eb-b75d-005056ba2029:1';

CHANGE MASTER TO
MASTER_HOST='10.5.9.39',MASTER_USER='repluser',MASTER_PASSWORD='repluser@!
#',MASTER_PORT=3306,MASTER_AUTO_POSITION = 1,MASTER_CONNECT_RETRY=10;

show variables like '%read_only%';

set global read_only=1;
set global super_read_only=1;

db940>show master status\G;

*************************** 1. row ***************************
File: bin940.028210
Position: 231
Binlog_Do_DB:
Binlog_Ignore_DB:
Executed_Gtid_Set: d58351dc-66ce-11eb-bbda-005056ba484c:1-5420603776,
d7221b1c-66db-11eb-b75d-005056ba2029:1
1 row in set (0.00 sec)

2303243

42-5B-D8-0E-2E-81
40-5B-D8-0E-2E-81
db2 connect to

MP 从库重新搭建同步，mysql 大事务方面问题多
alter table t_eap_log_invoking rename T_EAP_LOG_INVOKING20220101;

CREATE TABLE `t_eap_log_invoking` (

`INV_ID` varchar(36) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL,
`INV_PROJECTID` varchar(36) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT
NULL,
`INV_SERVICEURL` varchar(100) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT
NULL,
`INV_ACCESSTIME` datetime(3) DEFAULT CURRENT_TIMESTAMP(3),
`INV_BROWSER` int(11) DEFAULT NULL,
`INV_ACCESSIP` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT
NULL,
`INV_PLATTYPE` varchar(20) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT
NULL,
`INV_USERID` varchar(36) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT NULL,
`INV_USERNAME` varchar(50) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT
NULL,
PRIMARY KEY (`INV_ID`),
KEY `idx_log_invoking` (`INV_SERVICEURL`(32)),
KEY `idx_log_invoking_2` (`INV_ACCESSTIME`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin;

show index from t_eap_log_invoking;

alter table t_eap_sys_navigation_log rename t_eap_sys_navigation_log20220101;

CREATE TABLE `t_eap_sys_navigation_log` (

`LOG_ID` varchar(36) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL COMMENT
'序号',
`LOG_TYPE` int(11) NOT NULL DEFAULT '0' COMMENT '日志类型 0 菜单 1 流程发起',
`USER_ID` varchar(36) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL COMMENT
'用户 id',
 `MENU_ID` varchar(36) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL COMMENT
'菜单 id',
`MENU_NAME` varchar(200) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT NULL
COMMENT '菜单名称',
`MENU_URL` varchar(400) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin DEFAULT NULL
COMMENT '菜单地址',
`LAST_UPDATED_TIME` datetime(3) NOT NULL DEFAULT CURRENT_TIMESTAMP(3) COMMENT '修
改时间',
PRIMARY KEY (`LOG_ID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin COMMENT='导航方案日志';

show create table XXX;

The procedure for installing multiple database instances is the same as that
specified that in Installing the SAP HANA Database. Note that the SID of each
instance should be unique and the new instance numbers should be greater than
existing ones by at least 2.

global.ini->[connmunication]-->tcp_backlog=4096

logshipping_max_retention_size from 1T to 80% capacity of the /hana/log

innodb_undo_log_truncate=off

watching: •SAP HANA Academy on system

replication:http://scn.sap.com/community/hana-in-memory/blog/2015/05/19/sap-hana-
system-replicationYou should also be aware of these SAP notescontaining valuable
information on SAP HANA system replication:••SAP Note 1999880 -FAQ: SAP HANA System
Replication•SAP Note 2165547 -FAQ: SAP HANA Database Backup & Recovery in an SAP
HANA System Replication Landscape1

SET GLOBAL innodb_undo_log_truncate=1;

333867 | system user | | NULL | Query |

0 | waiting for handler commit | NULL

CREATE UNDO TABLESPACE myundo ADD DATAFILE 'myundo.ibd';

CREATE UNDO TABLESPACE myundo ADD DATAFILE 'myundo.ibu';

SELECT * FROM INFORMATION_SCHEMA.INNODB_TABLESPACES WHERE ROW_FORMAT = 'Undo' and
NAME = 'myundo'\G
ALTER UNDO TABLESPACE myundo SET INACTIVE;
在删除一个 undo tablespace 之前，首先要把 undo tablespace 设置为 inactive 状态
ALTER UNDO TABLESPACE myundo SET INACTIVE;
DROP UNDO TABLESPACE myundo;
即使状态为 inactive 的，但要保证如下几点才能被删除：

没有任何事务需要看到其中的老版本数据，也就是说所有在该事务之前开启的 read view 必须全部关闭

所有使用该 undo tablespace 的事务必须全部提交或回滚掉
purge 线程需要将其中的 Undo log 全部清理掉
如果 undo tablespace 非空，在 drop 时，会返回错误码 HA_ERR_TABLESPACE_IS_NOT_EMPTY. 所以在设
置为 inactive 到真正可以删除可能存在时间差，我们可以通过监控
INFORMATION_SCHEMA.INNODB_TABLESPACES 中的 undo space 状态是否为 empty 来判定是否可以删除。
Note:系统创建的 Undo space 不允许被删除

rename table T_EAP_LOG_INVOKING to T_EAP_LOG_INVOKING220101;

Rows_affected、Bytes_sent

1032

pt-slave-restart -uroot -putf8mb4 --error-numbers=1032

select *
from (select ttplanpull0_.TT_PLAN_PULL_ID as TT_PLAN_1_376_,
ttplanpull0_.CREATE_DATE as CREATE_D2_376_,
ttplanpull0_.UPDATE_DATE as UPDATE_D3_376_,
ttplanpull0_.CREATE_BY as CREATE_B4_376_,
ttplanpull0_.UPDATE_BY as UPDATE_B5_376_,
ttplanpull0_.VERSION as VERSION6_376_,
ttplanpull0_.COMPLETED_TIME as COMPLETE7_376_,
ttplanpull0_.DELIVERY_TYPE as DELIVERY8_376_,
ttplanpull0_.NO as NO9_376_,
ttplanpull0_.NOTE1 as NOTE10_376_,
ttplanpull0_.NOTE2 as NOTE11_376_,
ttplanpull0_.NOTE3 as NOTE12_376_,
ttplanpull0_.PULL_DATE as PULL_DA13_376_,
ttplanpull0_.PULL_TYPE as PULL_TY14_376_,
ttplanpull0_.range_group as range_g15_376_,
ttplanpull0_.REQURITE_TIME as REQURIT16_376_,
ttplanpull0_.STATUS as STATUS17_376_,
ttplanpull0_.WARN_FLAG as WARN_FL18_376_
from TT_PLAN_PULL ttplanpull0_
where 1 = 1
and ttplanpull0_.PULL_TYPE = '6'
and ttplanpull0_.STATUS = '0'
and ttplanpull0_.range_group = 'DLZC 发动机线供给'
and (ttplanpull0_.TT_PLAN_PULL_ID in
(select ttplanpull1_.TT_PLAN_PULL_ID
from TT_PLAN_PULL_DETAIL ttplanpull1_,
TM_PART_WH tmpartwh2_
where ttplanpull1_.TM_PART_WH_ID = tmpartwh2_.TM_PART_WH_ID
and tmpartwh2_.TYPE = '3'))
order by ttplanpull0_.TT_PLAN_PULL_ID)
where rownum <= 500;