Performing failover NOW, please wait... Error: ORA-16585: operation cannot be performed on a primary database
时间: 2024-04-06 16:33:24 浏览: 103
ORA-16585 错误表示无法在主数据库上执行故障转移操作。这通常是因为你正在尝试在主数据库上执行一个只能在备用数据库上执行的操作。在进行故障转移之前,你需要首先将主数据库转变为备用数据库,然后才能执行故障转移操作。你可以使用 Data Guard 等工具来实现主备切换。在进行任何操作之前,请务必参考相关的文档和手册,并在可能的情况下寻求专业帮助。
相关问题
15:58:08: 为项目CTK执行步骤 ... 15:58:08: Persisting CMake state... 15:58:19: 正在启动 "D:\BaiduNetdiskDownload\cmake-3.16.0-win64-x64\bin\cmake.exe" --build . --target all Scanning dependencies of target Log4Qt [ 4%] Creating directories for 'Log4Qt' [ 8%] Performing download step (git clone) for 'Log4Qt' Cloning into 'Log4Qt'... fatal: unable to access 'https://github.com/MEONMedical/Log4Qt.git/': OpenSSL SSL_read: Connection was reset, errno 10054 Cloning into 'Log4Qt'... fatal: unable to access 'https://github.com/MEONMedical/Log4Qt.git/': OpenSSL SSL_read: Connection was reset, errno 10054 Cloning into 'Log4Qt'... fatal: unable to access 'https://github.com/MEONMedical/Log4Qt.git/': Failed to connect to github.com port 443: Timed out -- Had to git clone more than once: 3 times. CMake Error at Log4Qt-cmake/tmp/Log4Qt-gitclone.cmake:31 (message): Failed to clone repository: 'https://github.com/MEONMedical/Log4Qt.git' NMAKE : fatal error U1077: “D:\BaiduNetdiskDownload\cmake-3.16.0-win64-x64\bin\cmake.exe”: 返回代码“0x1” Stop. NMAKE : fatal error U1077: “"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\amd64\nmake.exe"”: 返回代码“0x2” Stop. NMAKE : fatal error U1077: “"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\amd64\nmake.exe"”: 返回代码“0x2” Stop. 15:59:23: 进程"D:\BaiduNetdiskDownload\cmake-3.16.0-win64-x64\bin\cmake.exe"退出,退出代码 2 。 Error while building/deploying project CTK (kit: cmake-3.16.0) The kit cmake-3.16.0 has configuration issues which might be the root cause for this problem. When executing step "CMake Build"
根据提供的日志信息,你的CMake构建过程中遇到了与克隆 'Log4Qt' 项目相关的问题。错误提示表明无法访问 'https://github.com/MEONMedical/Log4Qt.git/',并且出现了连接复位、连接超时等错误。
这个问题可能是由于以下原因导致的:
1. 网络问题:你的网络连接可能存在问题,***
06-06 14:46:58.953 25664 25664 I crash_dump32: performing dump of process 25099 (target tid = 25124) 06-06 14:46:58.958 25664 25664 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 06-06 14:46:58.958 25664 25664 F DEBUG : Build fingerprint: 'samsung/star2qltezh/star2qltechn:9/PQ3B.190801.002/G9650ZHU2ARC6:user/release-keys' 06-06 14:46:58.958 25664 25664 F DEBUG : Revision: '0' 06-06 14:46:58.958 25664 25664 F DEBUG : ABI: 'x86' 06-06 14:46:58.958 25664 25664 F DEBUG : pid: 25099, tid: 25124, name: GLThread 82 >>> com.yuanshi.huaxia.fk <<< 06-06 14:46:58.958 25664 25664 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x382dae 06-06 14:46:58.958 25664 25664 F DEBUG : eax d1d16040 ebx 8000000c ecx 00000001 edx d1365970 06-06 14:46:58.958 25664 25664 F DEBUG : edi 00382dae esi 00000002 06-06 14:46:58.958 25664 25664 F DEBUG : ebp efbd3760 esp d1365110 eip ef5b76a5 06-06 14:46:58.959 25664 25664 F DEBUG : 06-06 14:46:58.959 25664 25664 F DEBUG : backtrace: 06-06 14:46:58.959 25664 25664 F DEBUG : #00 pc 001366a5 /system/lib/libhoudini.so 06-06 14:46:59.242 1471 1471 E /system/bin/tombstoned: Tombstone written to: /data/tombstones/tombstone_03
这是一段安卓崩溃日志,可以初步判断是由于 SIGSEGV 信号导致的崩溃。SIGSEGV 是一种信号,表示进程试图访问未分配给它的内存地址,或者试图向只读地址写入数据等非法操作。通常情况下,这种崩溃是由程序中的内存错误引起的,例如空指针引用、数组越界等。
从日志中可以看到,该崩溃发生在 GLThread 线程中,是由 libhoudini.so 库中的某个函数引起的,具体的函数名称需要进一步分析堆栈跟踪信息才能确定。由于该日志中缺少堆栈跟踪信息,无法进一步判断崩溃原因。
如果你需要对这个崩溃进行深入分析,可以尝试在开发环境中运行应用程序,并使用调试工具对其进行调试,以获取更详细的信息。
阅读全文