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

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



To query the Oracle tablespace size, follow the following steps: Determine the tablespace name by running the query: SELECT tablespace_name FROM dba_tablespaces; Query the tablespace size by running the query: SELECT sum(bytes) AS total_size, sum(bytes_free) AS available_space, sum(bytes) - sum(bytes_free) AS used_space FROM dba_data_files WHERE tablespace_

There are the following methods to get time in Oracle: CURRENT_TIMESTAMP: Returns the current system time, accurate to seconds. SYSTIMESTAMP: More accurate than CURRENT_TIMESTAMP, to nanoseconds. SYSDATE: Returns the current system date, excluding the time part. TO_CHAR(SYSDATE, 'YYY-MM-DD HH24:MI:SS'): Converts the current system date and time to a specific format. EXTRACT: Extracts a specific part from a time value, such as a year, month, or hour.

Oracle View Encryption allows you to encrypt data in the view, thereby enhancing the security of sensitive information. The steps include: 1) creating the master encryption key (MEk); 2) creating an encrypted view, specifying the view and MEk to be encrypted; 3) authorizing users to access the encrypted view. How encrypted views work: When a user querys for an encrypted view, Oracle uses MEk to decrypt data, ensuring that only authorized users can access readable data.

There are three ways to view instance names in Oracle: use the "sqlplus" and "select instance_name from v$instance;" commands on the command line. Use the "show instance_name;" command in SQL*Plus. Check environment variables (ORACLE_SID on Linux) through the operating system's Task Manager, Oracle Enterprise Manager, or through the operating system.

Uninstall method for Oracle installation failure: Close Oracle service, delete Oracle program files and registry keys, uninstall Oracle environment variables, and restart the computer. If the uninstall fails, you can uninstall manually using the Oracle Universal Uninstall Tool.

Oracle Invalid numeric errors may be caused by data type mismatch, numeric overflow, data conversion errors, or data corruption. Troubleshooting steps include checking data types, detecting digital overflows, checking data conversions, checking data corruption, and exploring other possible solutions such as configuring the NLS_NUMERIC_CHARACTERS parameter and enabling data verification logging.

SQL statements can be created and executed based on runtime input by using Oracle's dynamic SQL. The steps include: preparing an empty string variable to store dynamically generated SQL statements. Use the EXECUTE IMMEDIATE or PREPARE statement to compile and execute dynamic SQL statements. Use bind variable to pass user input or other dynamic values to dynamic SQL. Use EXECUTE IMMEDIATE or EXECUTE to execute dynamic SQL statements.

The method to solve the Oracle cursor closure problem includes: explicitly closing the cursor using the CLOSE statement. Declare the cursor in the FOR UPDATE clause so that it automatically closes after the scope is ended. Declare the cursor in the USING clause so that it automatically closes when the associated PL/SQL variable is closed. Use exception handling to ensure that the cursor is closed in any exception situation. Use the connection pool to automatically close the cursor. Disable automatic submission and delay cursor closing.
