Oracle10g Logical DataGuard 详细搭建过程

2024-02-01 08:48

本文主要是介绍Oracle10g Logical DataGuard 详细搭建过程,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

logical standby是在physical standby基础上搭建

Oracle10g Physical DataGuard 详细搭建过程


--停止standby上的日志应用

SQL> alter database recover managed standby database  cancel;


Database altered.



--修改主库log_archive_dest_3参数,当切换为备库时在线日志归档路径

SQL> alter system set log_archive_dest_3='LOCATION=/u01/app/oracle/oradata/dbserver/arch valid_for=(standby_logfiles,standby_role) db_unique_name=dbserver';


System altered.


SQL> alter system set log_archive_dest_state_3=enable;


System altered.


--主库执行,alert.log显示Logminer Bld: Done

SQL> execute dbms_logstdby.build;


PL/SQL procedure successfully completed.



--修改备库log_archive_dest_3参数,备库在线日志归档路径

SQL> alter system set log_archive_dest_3='LOCATION=/u01/app/oracle/oradata/standby/arch valid_for=(standby_logfiles,standby_role) db_unique_name=standby';


System altered.


SQL> alter system set log_archive_dest_state_3=enable;


System altered.


--如果备库没有临时表空间需要创建

--在standby端将物理备库转为逻辑备库,最后一个standby是逻辑备库名称

SQL> select status from v$instance;


STATUS
------------
MOUNTED


SQL> select database_role from v$database;


DATABASE_ROLE
----------------
PHYSICAL STANDBY


SQL> startup mount force
ORACLE instance started.


Total System Global Area  612368384 bytes
Fixed Size                  2085872 bytes
Variable Size             167775248 bytes
Database Buffers          436207616 bytes
Redo Buffers                6299648 bytes
Database mounted.
SQL> alter database recover to logical standby standby;


Database altered.


SQL> select status from v$instance;


STATUS
------------
STARTED


SQL> startup mount force
ORACLE instance started.


Total System Global Area  612368384 bytes
Fixed Size                  2085872 bytes
Variable Size             167775248 bytes
Database Buffers          436207616 bytes
Redo Buffers                6299648 bytes
Database mounted.
SQL> select database_role from v$database;


DATABASE_ROLE
----------------
LOGICAL STANDBY


SQL> alter database open resetlogs;


Database altered.


SQL> select name from v$database;


NAME
---------
STANDBY



--在主库switch logfile

SQL> alter system switch logfile;


System altered.


SQL> /


System altered.


SQL> /


System altered.


SQL> /


System altered.


SQL> /


System altered.


SQL> /


System altered.



--standby alert.log

RFS[3]: Assigned to RFS process 10806
RFS[3]: Identified database type as 'logical standby'
Mon Mar  3 13:10:28 2014
RFS LogMiner: Client enabled and ready for notification
RFS[3]: Successfully opened standby log 6: '/u01/app/oracle/oradata/standby/standby03.log'
Mon Mar  3 13:10:28 2014
RFS LogMiner: Client enabled and ready for notification
Mon Mar  3 13:11:21 2014
RFS LogMiner: Client enabled and ready for notification
Mon Mar  3 13:11:22 2014
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 5: '/u01/app/oracle/oradata/standby/standby02.log'
Mon Mar  3 13:11:33 2014
RFS LogMiner: Client enabled and ready for notification
Mon Mar  3 13:11:34 2014
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 5: '/u01/app/oracle/oradata/standby/standby02.log'


--在备库启用实时应用

SQL> alter database start logical standby apply immediate;


Database altered.



--接下来就是测试了,在主库插入数据在备库查看是否同步,以下是备库的alert.log

RFS LogMiner: Registered logfile [/u01/app/oracle/oradata/standby/arch/ARC0000000136_0839199018.0001] to LogMiner session id [1]
LOGMINER: session# = 1, reader process P000 started with pid=40 OS id=10844
LOGMINER: session# = 1, builder process P001 started with pid=41 OS id=10846
LOGMINER: session# = 1, preparer process P002 started with pid=42 OS id=10848
Mon Mar  3 13:17:08 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 136, /u01/app/oracle/oradata/standby/arch/ARC0000000136_0839199018.0001
Mon Mar  3 13:17:08 2014
LOGMINER: Turning ON Log Auto Delete
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000136_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 137, /u01/app/oracle/oradata/standby/arch/ARC0000000137_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000137_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 138, /u01/app/oracle/oradata/standby/arch/ARC0000000138_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000138_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 139, /u01/app/oracle/oradata/standby/arch/ARC0000000139_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000139_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 140, /u01/app/oracle/oradata/standby/arch/ARC0000000140_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000140_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 141, /u01/app/oracle/oradata/standby/arch/ARC0000000141_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000141_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 142, /u01/app/oracle/oradata/standby/arch/ARC0000000142_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000142_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 143, /u01/app/oracle/oradata/standby/arch/ARC0000000143_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000143_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 144, /u01/app/oracle/oradata/standby/arch/ARC0000000144_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000144_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 145, /u01/app/oracle/oradata/standby/arch/ARC0000000145_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000145_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 146, /u01/app/oracle/oradata/standby/arch/ARC0000000146_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000146_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 147, /u01/app/oracle/oradata/standby/arch/ARC0000000147_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000147_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 148, /u01/app/oracle/oradata/standby/arch/ARC0000000148_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000148_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: Begin mining logfile during dictionary load for session 1 thread 1 sequence 149, /u01/app/oracle/oradata/standby/arch/ARC0000000149_0839199018.0001
Mon Mar  3 13:17:14 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000149_0839199018.0001
LNS1 started with pid=43, OS id=10850
Mon Mar  3 13:17:17 2014
Thread 1 advanced to log sequence 2 (LGWR switch)
  Current log# 2 seq# 2 mem# 0: /u01/app/oracle/oradata/standby/redo02.log
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ATTRCOL$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_CCOL$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_CDEF$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_COL$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_COLTYPE$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_ICOL$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_IND$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDCOMPART$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDPART$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_INDSUBPART$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOB$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_LOBFRAG$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_OBJ$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TAB$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABCOMPART$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABPART$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TABSUBPART$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TS$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_TYPE$ have been marked unusable
Mon Mar  3 13:17:19 2014
Some indexes or index [sub]partitions of table SYSTEM.LOGMNR_USER$ have been marked unusable
Indexes of table  SYSTEM.LOGMNR_ATTRCOL$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_ATTRIBUTE$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_CCOL$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_CDEF$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_COL$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_COLTYPE$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_DICTIONARY$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_ICOL$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_IND$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_INDCOMPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_INDPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_INDSUBPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_LOB$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_LOBFRAG$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_OBJ$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TAB$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TABCOMPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TABPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TABSUBPART$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TS$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_TYPE$ have been rebuilt and are now usable
Indexes of table  SYSTEM.LOGMNR_USER$ have been rebuilt and are now usable
LSP2 started with pid=44, OS id=10853
Mon Mar  3 13:17:26 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 136, /u01/app/oracle/oradata/standby/arch/ARC0000000136_0839199018.0001
Mon Mar  3 13:17:26 2014
LOGMINER: Turning ON Log Auto Delete
LOGSTDBY Analyzer process P003 started with pid=45 OS id=10855
LOGSTDBY Apply process P006 started with pid=48 OS id=10861
LOGSTDBY Apply process P008 started with pid=50 OS id=10865
LOGSTDBY Apply process P007 started with pid=49 OS id=10863
LOGSTDBY Apply process P004 started with pid=46 OS id=10857
LOGSTDBY Apply process P005 started with pid=47 OS id=10859
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000136_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 137, /u01/app/oracle/oradata/standby/arch/ARC0000000137_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000137_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 138, /u01/app/oracle/oradata/standby/arch/ARC0000000138_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000138_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 139, /u01/app/oracle/oradata/standby/arch/ARC0000000139_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000139_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 140, /u01/app/oracle/oradata/standby/arch/ARC0000000140_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000140_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 141, /u01/app/oracle/oradata/standby/arch/ARC0000000141_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000141_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 142, /u01/app/oracle/oradata/standby/arch/ARC0000000142_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000142_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 143, /u01/app/oracle/oradata/standby/arch/ARC0000000143_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000143_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 144, /u01/app/oracle/oradata/standby/arch/ARC0000000144_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000144_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 145, /u01/app/oracle/oradata/standby/arch/ARC0000000145_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000145_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 146, /u01/app/oracle/oradata/standby/arch/ARC0000000146_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000146_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 147, /u01/app/oracle/oradata/standby/arch/ARC0000000147_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000147_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 148, /u01/app/oracle/oradata/standby/arch/ARC0000000148_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000148_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 149, /u01/app/oracle/oradata/standby/arch/ARC0000000149_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: End mining logfile: /u01/app/oracle/oradata/standby/arch/ARC0000000149_0839199018.0001
Mon Mar  3 13:17:27 2014
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 150, /u01/app/oracle/oradata/standby/standby03.log
Mon Mar  3 13:18:05 2014
RFS LogMiner: RFS id [10797] assigned as thread [1] PING handler

这篇关于Oracle10g Logical DataGuard 详细搭建过程的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/666725

相关文章

Windows环境下解决Matplotlib中文字体显示问题的详细教程

《Windows环境下解决Matplotlib中文字体显示问题的详细教程》本文详细介绍了在Windows下解决Matplotlib中文显示问题的方法,包括安装字体、更新缓存、配置文件设置及编码調整,并... 目录引言问题分析解决方案详解1. 检查系统已安装字体2. 手动添加中文字体(以SimHei为例)步骤

Linux进程CPU绑定优化与实践过程

《Linux进程CPU绑定优化与实践过程》Linux支持进程绑定至特定CPU核心,通过sched_setaffinity系统调用和taskset工具实现,优化缓存效率与上下文切换,提升多核计算性能,适... 目录1. 多核处理器及并行计算概念1.1 多核处理器架构概述1.2 并行计算的含义及重要性1.3 并

nginx -t、nginx -s stop 和 nginx -s reload 命令的详细解析(结合应用场景)

《nginx-t、nginx-sstop和nginx-sreload命令的详细解析(结合应用场景)》本文解析Nginx的-t、-sstop、-sreload命令,分别用于配置语法检... 以下是关于 nginx -t、nginx -s stop 和 nginx -s reload 命令的详细解析,结合实际应

Spring boot整合dubbo+zookeeper的详细过程

《Springboot整合dubbo+zookeeper的详细过程》本文讲解SpringBoot整合Dubbo与Zookeeper实现API、Provider、Consumer模式,包含依赖配置、... 目录Spring boot整合dubbo+zookeeper1.创建父工程2.父工程引入依赖3.创建ap

Linux下进程的CPU配置与线程绑定过程

《Linux下进程的CPU配置与线程绑定过程》本文介绍Linux系统中基于进程和线程的CPU配置方法,通过taskset命令和pthread库调整亲和力,将进程/线程绑定到特定CPU核心以优化资源分配... 目录1 基于进程的CPU配置1.1 对CPU亲和力的配置1.2 绑定进程到指定CPU核上运行2 基于

Spring Boot集成Druid实现数据源管理与监控的详细步骤

《SpringBoot集成Druid实现数据源管理与监控的详细步骤》本文介绍如何在SpringBoot项目中集成Druid数据库连接池,包括环境搭建、Maven依赖配置、SpringBoot配置文件... 目录1. 引言1.1 环境准备1.2 Druid介绍2. 配置Druid连接池3. 查看Druid监控

创建Java keystore文件的完整指南及详细步骤

《创建Javakeystore文件的完整指南及详细步骤》本文详解Java中keystore的创建与配置,涵盖私钥管理、自签名与CA证书生成、SSL/TLS应用,强调安全存储及验证机制,确保通信加密和... 目录1. 秘密键(私钥)的理解与管理私钥的定义与重要性私钥的管理策略私钥的生成与存储2. 证书的创建与

使用Docker构建Python Flask程序的详细教程

《使用Docker构建PythonFlask程序的详细教程》在当今的软件开发领域,容器化技术正变得越来越流行,而Docker无疑是其中的佼佼者,本文我们就来聊聊如何使用Docker构建一个简单的Py... 目录引言一、准备工作二、创建 Flask 应用程序三、创建 dockerfile四、构建 Docker

Python设置Cookie永不超时的详细指南

《Python设置Cookie永不超时的详细指南》Cookie是一种存储在用户浏览器中的小型数据片段,用于记录用户的登录状态、偏好设置等信息,下面小编就来和大家详细讲讲Python如何设置Cookie... 目录一、Cookie的作用与重要性二、Cookie过期的原因三、实现Cookie永不超时的方法(一)

Java进程异常故障定位及排查过程

《Java进程异常故障定位及排查过程》:本文主要介绍Java进程异常故障定位及排查过程,具有很好的参考价值,希望对大家有所帮助,如有错误或未考虑完全的地方,望不吝赐教... 目录一、故障发现与初步判断1. 监控系统告警2. 日志初步分析二、核心排查工具与步骤1. 进程状态检查2. CPU 飙升问题3. 内存