Executing:opmnctl start coreapplication_obisch1 failure

最新推荐文章于 2024-04-12 09:10:43 发布
原创 最新推荐文章于 2024-04-12 09:10:43 发布 · 288 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文详细介绍了在安装BIEE11G时遇到内存不足导致opmnctl启动失败的问题，通过增加安装时的内存分配成功解决了该问题。同时提醒用户在安装大型软件时，应确保有足够的系统资源。
安装biee 11g到配置进度时电脑出现虚拟内存不足，将拒绝所有内存请求，然后进行的[color=red]Executing:opmnctl start coreapplication_obisch1[/color]就报出了失败，日志文件没有任何报错，怀疑是内存拒绝请求，opmnctl关闭引起，命令行打开C:\biee\instances\instance1\bin，运行opmnctl start，启动opmnctl，然后点击安装界面Executing:opmnctl start coreapplication_obisch1项的重试按钮，成功安装。

[color=red]注：安装biee11g非常消耗内存，安装时尽量多给的内存，不然因为内存可能会引起报错。[/color]
Qt for android 移植android studio项目报错activity_main.xml:9: AAPT: error: attribute layout_constraintBott
波风水门
12-31 2852
文章目录问题报错代码解决方案方案一治标(某种意义上也算是治根)针对Qt方案二治根 针对Android,Qt也无妨 问题报错代码 简约错误 activity_main.xml:9: AAPT: error: attribute layout_constraintBottom_toBottomOf (aka com.jni.f:layout_constraintBottom_toBottomOf) not found. 全部错误如下： * What went wrong: Execution failed
Error while executing: am start -n错误解决方案
热门推荐
菜鸟博客
07-05 3万+
今天真机运行项目发现报了这个错误： Error while executing: am start -n "pagekageName/pagekageName.ac.WelcomeActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER Starting: Intent { act=android.int...
OBIEE 11g opmnctl 启动报错：Permission denied
ygj26's blog
11-29 3398
今天在Linux 64位系统中启动BIEE 11g时遇到以下错误 /app/biee/Oracle/Middleware/Oracle_BI1/Oracle_IDM1/opmn/bin/opmn: error while loading shared libraries: /app/biee/Oracle/Middleware/Oracle_BI1/lib/libdms2.so: cannot
Oracle AS opmnctl.exe 启动问题
cnwa79132的博客
08-16 185
最近安装Oracle as 发现用NOD32杀毒软件的一些问题, 在安装AS之前不能安装NOD32软件,安装之后,安全威胁保护模块中的IMON中有个设定的HTTP ----&gt设定-----&gt启动HTTP...
Oracle AS 报Connection refused opmnctl: opmn start failed.solution解决放法
熊熊的菜园子
07-30 374
昨天项目组成员在OracleAS 下发布程序，以往一直可以成功发布，但是昨天怎么也发布不成功，系统报“Temporary failure in name resolution。。。 Connection refused opmnctl: opmn start failed.solution): Connection refused。。。。。”错误。我重新启动了linux服务器，然后在重启 Orac...
OPMN
weixin_30719711的博客
02-23 328
OPMN is installed and configured with every Oracle Application Server installation type and is essential for running Oracle Application Server. OPMN features the following functionality: •Prov...
BIEE服务启动有问题
zhzhiqun的专栏
03-24 630
Weblogic服务日志文件： BI Managed Server: OBIEE_HOME\user_projects\domains\bifoundation_domain\servers\bi_server1\logs下bi_server1.out； Admin Server: OBIEE_HOME\user_projects\domains\bifoundation_domain\s...
VirtualBox：NS_ERROR_FAILURE (0x80004005)
yimtcode
11-15 7063
Vagrant：NS_ERROR_FAILURE 环境：macOS11.0.1 1. 前言 macOS10.15.7升级最新的11.0.1过后，使用Vagrant创建CentOS7虚拟机启动提示如下错误。 You're running an up-to-date version of Vagrant! yimt@MacBook-Pro centos7-docker % vagrant up Bringing machine 'default' up with 'virtualbox' provider.
diffusers 出现TypeError: For single controlnet: `controlnet_conditioning_scale` must be type `float`.
尘思录
04-12 1842
而pipeline_stable_diffusion_xl_instantid.py文件中的调用如下 （大约在453行）测试ComfyUI-InstantID 时出现如下。
TypeError: __new__() missing 1 required positional argument: ‘is_raw‘
qq_36717487的博客
03-16 2866
Traceback (most recent call last): File "Dicom_2_Png.py", line 75, in <module> slices = load_patient(dicom_dir) File "Dicom_2_Png.py", line 37, in load_patient instance = pydicom.dcmread(src_dir + '/' + s) File "/home/USER/anaconda2/env
【BIEE】05_启动BIEE时，无法启动BI_SERVER
ajsyipsc40270的博客
01-21 323
本地修改资料库后，重新启动BIEE，结果报错： 点击【查看日志信息】后 从这里是没看出是什么问题造成的，那么我们就要去查询启动日志了 问题解决 找到日志路径：D:\obiee\instances\instance1\diagnostics\logs\OracleBIServerComponent\coreapplication_obis1 打开文件后可以看到如下内容...
BIEE11g--bi server1无法正常启动原因之二
cj320521的博客
08-03 278
环境： Windows server 2008 + BIEE 11.1.6 ，rcu安装在本地主机现象： 使用BIEE 11g 自带的RPD档案资料库可以正常启动，使用自定义的RPD（设置到另 ...
OBIEE 11g 启动与停止包含服务器重启
tomatofly的专栏
05-11 8344
ORACLE_BIEE_HOME为biee安装路径 注意：默认建立的是"instance1"但是如果你安装过多次可能实例名是不一样(例如： instance2以此类推)。因此，请找到正确的实例名。 一、启动您的数据库 二、手动启动 Oracle BIEE 11g （顺序不可颠倒） 1. ORACLE_BIEE_HOME/user_projects/domains/b
BIEE11g--bi server1无法正常启动原因之一
cj320521的博客
07-16 516
由于切换IP地址，导致biee11g 只有em组件启动，analytics等无法使用 方式一： 进入em后重启bi 所有服务后正常使用 方式二： 启动BIEE 前修改IP为安装时IP（不一定要联网），启动后再...
OBIEE11g Important Application/Services and directory paths
牧码人的专栏
05-28 1092
Posted by Debashis Paul * A Passionate Blogger * under OBIEE, OBIEE 11g | Tags: obiee 11g catalog server log file, obiee 11g cluster config files, obiee 11g javahost ODBC files, obiee 11g OPMN files s
[nQSError: 76015] The active Oracle BI Scheduler instance in the cluster could not be determined.
小小酒仙的专栏
03-18 3658
问题： 最近遇到一个很奇葩的问题，opmn启动服务时，好慢，每次都卡在BI Scheduler服务那，最终BI Scheduler启动失败。 查看日志文件信息： 1) /home/BIEE_HOME/instances/instance1/diagnostics/logs/OracleBISchedulerComponent/coreapplication_obisch1/nqschedul
oc4j启动故障处理
wangjialiang的专栏
12-20 4373
./opmnctl status 查看状态 ./opmnctl startall 启动所有服务 ./opmnctl stopall 停止所有应用 ./opmnctl shutdown 关闭所有服务，包括管理服务 ./opmnctl startproc ias-component=HTTP_Server 启动单个服务 ./opmnctl startproc proc
oracle存储控制器,Oracle 10g网格控制器安装指南
weixin_36057741的博客
04-09 267
Oracle的网格控制器可以用来集中管理oracle数据库和中间件等，用处很多，还可以在网格控制器上简单化rac和dg的管理，唐sir有句名言：“没有网格控制器的rac，基本不能用！” oracle的网格控制器 gridcontrol，简称gc，主要由OMR,OMS和OMA三大部件组成。OMR主要指存放gc数据的资料档案库，OMS主要指应用服务器，在10g中oracle使用的是oc4j,11g则使...
BIEE日志
Stephen.G
04-20 1958
BIEE各个组件日志 /u01/app/oracle/product/fmw/instances/instance1/diagnostics/logs 下存各个组件日志 比如： /u01/app/oracle/product/fmw/instances/instance1/diagnostics/logs/OracleBIServerComponent/coreapplic
mysql> SELECT * FROM performance_schema.replication_applier_status_by_worker \G *************************** 1. row *************************** CHANNEL_NAME: WORKER_ID: 1 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752528 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.872259 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.872259 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:07:20.962510 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:07:20.964174 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 2. row *************************** CHANNEL_NAME: WORKER_ID: 2 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752527 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.871746 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.871746 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:07:20.961392 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:07:20.963864 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 3. row *************************** CHANNEL_NAME: WORKER_ID: 3 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 1062 LAST_ERROR_MESSAGE: Worker 3 failed executing transaction '5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752529' at master log mysql_bin.040867, end_log_pos 15254660; Could not execute Write_rows event on table kk_control.control_site_venue_bet_statistics; Duplicate entry '2025-09-29-5-28-TY' for key 'control_site_venue_bet_statistics.unique_index', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log mysql_bin.040867, end_log_pos 15254660 LAST_ERROR_TIMESTAMP: 2025-10-04 08:07:20.962997 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752516 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.807107 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.807107 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:07:20.785319 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:07:20.787189 APPLYING_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752529 APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.874823 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.874823 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:07:20.962589 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 4. row *************************** CHANNEL_NAME: WORKER_ID: 4 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752456 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.660213 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.660213 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:07:20.707483 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:07:20.708907 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 5. row *************************** CHANNEL_NAME: WORKER_ID: 5 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241752459 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.664357 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:07:20.664357 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:07:20.708929 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:07:20.711737 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 6. row *************************** CHANNEL_NAME: WORKER_ID: 6 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241748791 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:06:02.424222 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:06:02.424222 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:06:02.412803 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:06:02.413778 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 7. row *************************** CHANNEL_NAME: WORKER_ID: 7 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241748792 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:06:02.424239 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:06:02.424239 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:06:02.412833 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:06:02.413784 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 *************************** 8. row *************************** CHANNEL_NAME: WORKER_ID: 8 THREAD_ID: NULL SERVICE_STATE: OFF LAST_ERROR_NUMBER: 0 LAST_ERROR_MESSAGE: LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION: 5f4f1683-6f8b-11ec-ad71-bc97e1abd35c:14241748686 LAST_APPLIED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-10-04 08:06:02.304209 LAST_APPLIED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-10-04 08:06:02.304209 LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP: 2025-10-04 08:06:02.292898 LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP: 2025-10-04 08:06:02.293895 APPLYING_TRANSACTION: APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_START_APPLY_TIMESTAMP: 0000-00-00 00:00:00.000000 LAST_APPLIED_TRANSACTION_RETRIES_COUNT: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: LAST_APPLIED_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 APPLYING_TRANSACTION_RETRIES_COUNT: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_NUMBER: 0 APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_MESSAGE: APPLYING_TRANSACTION_LAST_TRANSIENT_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000 8 rows in set (0.00 sec) mysql>
最新发布
10-05
ALTER TABLE kk_control.control_site_venue_bet_statistics ADD UNIQUE (column1, column2); ``` #### 重新初始化从库 若上述方法无法解决问题，可以重新初始化从库。步骤如下： 1. 在主库上创建备份： ```bash ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值