Oracle DG 逻辑备库故障--MAX Processes
OracleDG逻辑备库故障--MAXProcesses系统环境:操作系统:RedHatEL6Oracle:Oracle11gR2DataGuard环境:10:29:58SYS@test1selectdbid,name,database_role,protect
Oracle DG 逻辑备库故障--MAX Processes
系统环境:
操作系统:RedHat EL6
Oracle: Oracle 11gR2
DataGuard 环境:
10:29:58 SYS@ test1>select dbid,name,database_role,protection_mode from v$database;
DBID NAME DATABASE_ROLE PROTECTION_MODE
---------- --------- ---------------- --------------------
1174898526 TEST1 PRIMARY MAXIMUM PERFORMANCE
10:30:06 SYS@ sh>select dbid,name,database_role,protection_mode from v$database;
DBID NAME DATABASE_ROLE PROTECTION_MODE
---------- --------- ---------------- --------------------
1675496824 SHDB LOGICAL STANDBY UNPROTECTED
10:28:11 SYS@ sh>alter database open;
Database altered.
Elapsed: 00:00:08.18
启动逻辑备库的redo log 应用:
10:28:29 SYS@ sh>alter database start logical standby apply immediate;
Database altered.
Elapsed: 00:00:00.30
10:28:40 SYS@ sh>
查看告警日志:altert.log:
ALTER DATABASE START LOGICAL STANDBY APPLY (sh)
Tue Apr 8 10:37:08 2014
with optional part
IMMEDIATE
LSP0 started with pid=19, OS id=3263
Tue Apr 8 10:37:08 2014
Attempt to start background Logical Standby process
LOGSTDBY Parameter: DISABLE_APPLY_DELAY =
LOGSTDBY Parameter: LOG_AUTO_DELETE = FALSE
LOGSTDBY Parameter: REAL_TIME =
Completed: alter database start logical standby apply immediate
Tue Apr 8 10:37:08 2014
LOGSTDBY status: ORA-16111: log mining and apply setting up
Tue Apr 8 10:37:08 2014
LOGMINER: Parameters summary for session# = 1
LOGMINER: Number of processes = 3, Transaction Chunk Size = 201
LOGMINER: Memory Size = 30M, Checkpoint interval = 150M
LOGMINER: session# = 1, builder process P001 started with pid=21 OS id=3267
LOGMINER: session# = 1, reader process P000 started with pid=20 OS id=3265
LOGMINER: session# = 1, preparer process P002 started with pid=22 OS id=3269
LOGSTDBY Analyzer process P003 started with pid=23 OS id=3271
LOGSTDBY Apply process P004 started with pid=24 OS id=3273
LOGSTDBY Apply process P006 started with pid=26 OS id=3277
LOGSTDBY Apply process P007 started with pid=27 OS id=3279
LOGSTDBY Apply process P008 started with pid=28 OS id=3281
LOGSTDBY Apply process P005 started with pid=25 OS id=3275
Tue Apr 8 10:41:33 2014
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 3295
RFS[1]: Identified database type as 'logical standby'
Tue Apr 8 10:41:33 2014
RFS LogMiner: Client enabled and ready for notification
RFS[1]: Archived Log: '/disk1/arch_sh/arch_1_36_797856158.log'
Tue Apr 8 10:41:33 2014
RFS LogMiner: Registered logfile [/disk1/arch_sh/arch_1_36_797856158.log] to LogMiner session id [1]
Tue Apr 8 10:41:33 2014
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 3297
RFS[2]: Identified database type as 'logical standby'
Tue Apr 8 10:41:33 2014
RFS LogMiner: Client enabled and ready for notification
RFS[2]: Archived Log: '/disk1/arch_sh/arch_1_35_797856158.log'
Tue Apr 8 10:41:33 2014
RFS LogMiner: Registered logfile [/disk1/arch_sh/arch_1_35_797856158.log] to LogMiner session id [1]
Tue Apr 8 10:41:34 2014
LOGMINER: Begin mining logfile: /disk1/arch_sh/arch_1_35_797856158.log
Tue Apr 8 10:41:34 2014
LOGMINER: End mining logfile: /disk1/arch_sh/arch_1_35_797856158.log
Tue Apr 8 10:41:34 2014
LOGMINER: Begin mining logfile: /disk1/arch_sh/arch_1_36_797856158.log
Tue Apr 8 10:41:34 2014
LOGMINER: End mining logfile: /disk1/arch_sh/arch_1_36_797856158.log
Tue Apr 8 10:43:26 2014
RFS[2]: Successfully opened standby log 4: '/u01/app/oracle/oradata/sh/std_redo04a.log'
Tue Apr 8 10:43:26 2014
RFS LogMiner: Client enabled and ready for notification
Tue Apr 8 10:43:26 2014
LOGMINER: Begin mining logfile: /u01/app/oracle/oradata/sh/std_redo04a.log
Tue Apr 8 10:43:26 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/sh/std_redo04a.log
Tue Apr 8 10:43:26 2014
RFS LogMiner: Registered logfile [/disk1/arch_sh/arch_1_37_797856158.log] to LogMiner session id [1]
在备库上查看redolog 的应用:
11:00:27 SYS@ sh>select THREAD#,SEQUENCE#,APPLIED from dba_logstdby_log;
THREAD# SEQUENCE# APPLIED
---------- ---------- --------
1 31 YES
1 32 YES
1 33 YES
1 34 YES
1 35 YES
1 36 YES
1 37 YES
1 38 YES
1 39 YES
1 40 YES
10 rows selected.
在告警日志中出现以下,故障现象:
Errors in file /u01/app/oracle/admin/sh/bdump/sh_m000_3326.trc:
ORA-00018: maximum number of sessions exceeded
Tue Apr 8 10:50:29 2014
Errors in file /u01/app/oracle/admin/sh/bdump/sh_m000_3332.trc:
ORA-00018: maximum number of sessions exceeded
Tue Apr 8 10:51:29 2014
Errors in file /u01/app/oracle/admin/sh/bdump/sh_m000_3335.trc:
ORA-00018: maximum number of sessions exceeded
10:50:37 SYS@ sh>select count(*) from v$session;
解决问题:
1、查看当前process
10:51:11 SYS@ sh>show parameter process
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
aq_tm_processes integer 0
db_writer_processes integer 1
gcs_server_processes integer 0
job_queue_processes integer 0
log_archive_max_processes integer 3
processes integer 40
2、当前建立的session
10:51:11 SYS@ sh>select count(*) from v$session;
COUNT(*)
----------
29

热AI工具

Undresser.AI Undress
人工智能驱动的应用程序,用于创建逼真的裸体照片

AI Clothes Remover
用于从照片中去除衣服的在线人工智能工具。

Undress AI Tool
免费脱衣服图片

Clothoff.io
AI脱衣机

AI Hentai Generator
免费生成ai无尽的。

热门文章

热工具

记事本++7.3.1
好用且免费的代码编辑器

SublimeText3汉化版
中文版,非常好用

禅工作室 13.0.1
功能强大的PHP集成开发环境

Dreamweaver CS6
视觉化网页开发工具

SublimeText3 Mac版
神级代码编辑软件(SublimeText3)

热门话题

Oracle 数据库启动顺序为:1. 检查前置条件;2. 启动监听器;3. 启动数据库实例;4. 等待数据库打开;5. 连接到数据库;6. 验证数据库状态;7. 启用服务(如果需要);8. 测试连接。

Oracle 数据库日志的保留期限取决于日志类型和配置,包括:重做日志:由 "LOG_ARCHIVE_DEST" 参数配置的最大大小决定。归档重做日志:由 "DB_RECOVERY_FILE_DEST_SIZE" 参数配置的最大大小决定。在线重做日志:不归档,在数据库重启时丢失,保留期限与实例运行时间一致。审计日志:由 "AUDIT_TRAIL" 参数配置,默认保留 30 天。

Oracle 所需内存量取决于数据库大小、活动水平和所需性能水平:用于存储数据缓冲区、索引缓冲区、执行 SQL 语句和管理数据字典缓存。具体数量受数据库大小、活动水平和所需性能水平影响。最佳实践包括设置适当的 SGA 大小、调整 SGA 组件大小、使用 AMM 和监控内存使用情况。

Oracle 可以通过以下步骤读取 dbf 文件:创建外部表,引用 dbf 文件;查询外部表,检索数据;将数据导入 Oracle 表。

Oracle 数据库服务器硬件配置要求:处理器:多核,主频至少 2.5 GHz,大型数据库建议 32 核以上。内存:小型数据库至少 8GB,中等规模 16-64GB,大型数据库或高负载工作负载高达 512GB 或更多。存储:SSD 或 NVMe 磁盘,RAID 阵列提高冗余和性能。网络:高速网络(10GbE 或更高),专用网卡,低延迟网络。其他:稳定电源、冗余组件、兼容操作系统和软件、散热和冷却系统。

Oracle 数据库所需内存量取决于数据库大小、工作负载类型和并发用户数量。通常建议:小型数据库:16-32 GB,中型数据库:32-64 GB,大型数据库:64 GB 或更多。其他需考虑因素包括数据库版本、内存优化选项、虚拟化和最佳实践(监视内存使用情况、调整分配)。

要在 Oracle 中创建每天执行一次的定时任务,需要执行以下三个步骤:创建一个作业。为作业添加一个子作业,并设置其计划表达式为“INTERVAL 1 DAY”。启用作业。

Oracle 数据库的内存需求取决于以下因素:数据库大小、活动用户数量、并发查询、启用的功能和系统硬件配置。确定内存要求的步骤包括:确定数据库大小、估计活动用户数量、了解并发查询、考虑启用的功能和检查系统硬件配置。
