服务器

位置:IT落伍者 >> 服务器 >> 浏览文章

DataGuard数据库服务器硬盘故障处理


发布日期:2022年05月14日
 
DataGuard数据库服务器硬盘故障处理

昨天一台PC Server上的数据库又出问题同样是硬盘故障

这两台服务器用的都是联志的国产低端PC Server这些服务器的质量实在是差上次一台备机的硬盘损坏然后又有一台因为电源模块的问题反复重起现在这一台服务器的硬盘再次出现问题

Nov :: wapcom kernel: attempt to access beyond end of device

Nov :: wapcom kernel: :: rw= want= limit=

Nov :: wapcom kernel: EXTfs error (device sd()): ext_readdir:

directory # contains a hole at offset

Nov :: wapcom kernel: attempt to access beyond end of device

Nov :: wapcom kernel: :: rw= want= limit=

Nov :: wapcom kernel: EXTfs error (device sd()): ext_readdir:

directory # contains a hole at offset

Nov :: wapcom kernel: attempt to access beyond end of device

Nov :: wapcom kernel: :: rw= want= limit=

Nov :: wapcom kernel: EXTfs error (device sd()): ext_readdir:

directory # contains a hole at offset

Nov :: wapcom kernel: attempt to access beyond end of device

Nov :: wapcom kernel: :: rw= want= limit=

Nov :: wapcom kernel: EXTfs error (device sd()): ext_readdir:

directory # contains a hole at offset

好在数据库通过DataGuard可以切换到另外一台没有数据损失

Thu Nov ::

ARC: Complete FAL archive (thread sequence destination bmarksb)

ARC: Begin FAL archive (thread sequence destination bmarksb)

Creating archive destination LOG_ARCHIVE_DEST_: bmarksb

ARC: Complete FAL archive (thread sequence destination bmarksb)

ARC: Begin FAL archive (thread sequence destination bmarksb)

Creating archive destination LOG_ARCHIVE_DEST_: bmarksb

Thu Nov ::

ARC: Complete FAL archive (thread sequence destination bmarksb)

ARC: Begin FAL archive (thread sequence destination bmarksb)

Creating archive destination LOG_ARCHIVE_DEST_: bmarksb

Thu Nov ::

ARC: Complete FAL archive (thread sequence destination bmarksb)

Thu Nov ::

ARC: Complete FAL archive (thread sequence destination bmarksb)

现在是主库所在的服务器出现问题:

SQL> select dbidnamePROTECTION_MODEDATABASE_ROLESWITCHOVER_STATUS from v$database;

DBID NAME PROTECTION_MODE DATABASE_ROLE SWITCHOVER_STATUS

BMARK MAXIMUM PERFORMANCE PRIMARY SESSIONS ACTIVE

备库现在一切正常:

SQL> select dbidnamePROTECTION_MODEDATABASE_ROLESWITCHOVER_STATUS from v$database;

DBID NAME PROTECTION_MODE DATABASE_ROLE SWITCHOVER_STATUS

BMARK MAXIMUM PERFORMANCE PHYSICAL STANDBY SESSIONS ACTIVE

现在需要的是一点停机时间进行切换

Fri Nov ::

alter database commit to switchover to physical standby with session shutdown

Fri Nov ::

ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY

Fri Nov ::

SMON: disabling tx recovery

Fri Nov ::

Active process user oracle program ora (CJQ)

Active process user oracle program ora (TNS VV)

Active process user oracle program ora (TNS VV)

Active process user oracle program ora (TNS VV)

Active process user oracle program ora (TNS VV)

Active process user oracle program ora (TNS VV)

Active process user oracle program ora (TNS VV)

CLOSE: waiting for server sessions to complete

Fri Nov ::

CLOSE: all sessions shutdown successfully

Fri Nov ::

SMON: disabling cache recovery

Fri Nov ::

Shutting down archive processes

Archiving is disabled

Fri Nov ::

ARCH shutting down

Fri Nov ::

ARCH shutting down

Fri Nov ::

ARC: Archival stopped

Fri Nov ::

ARC: Archival stopped

Fri Nov ::

Thread closed at log sequence

Successful close of redo thread

Fri Nov ::

ARCH: noswitch archival of thread sequence

ARCH: EndOfRedo archival of thread sequence

ARCH: Evaluating archive log thread sequence

ARCH: Beginning to archive log thread sequence

Creating archive destination LOG_ARCHIVE_DEST_: bmarksb

Creating archive destination LOG_ARCHIVE_DEST_: /var/oradata/arch/_arc

ARCH: Completed archiving log thread sequence

ARCH: archiving is disabled due to current logfile archival

Clearing standby activation ID (xdddcc)

The primary database controlfile was created using the

MAXLOGFILES clause

The resulting standby controlfile will not have enough

available logfile entries to support an adequate number

of standby redo logfiles Consider recreating the

primary controlfile using MAXLOGFILES (or larger)

Use the following SQL commands on the standby database to create

standby redo logfiles that match the primary database:

ALTER DATABASE ADD STANDBY LOGFILE srlf SIZE ;

ALTER DATABASE ADD STANDBY LOGFILE srlf SIZE ;

ALTER DATABASE ADD STANDBY LOGFILE srlf SIZE ;

ALTER DATABASE ADD STANDBY LOGFILE srlf SIZE ;

Archivelog for thread sequence required for standby recovery

MRP started with pid=

MRP: Background Managed Standby Recovery process started

Media Recovery Log /var/oradata/arch/_arc

Identified endofREDO for thread sequence

Identified endofREDO for thread sequence

Media Recovery EndOfRedo indicator encountered

Media Recovery Applied until change

MRP: Media Recovery Complete: EndOfREDO

Resetting standby activation ID (xdddcc)

MRP: Background Media Recovery process shutdown

Fri Nov ::

Switchover: Complete Database shutdown required

Completed: alter database commit to switchover to physical st

Fri Nov ::

Shutting down instance: further logons disabled

Shutting down instance (immediate)

License high water mark =

Fri Nov ::

ALTER DATABASE CLOSE NORMAL

ORA signalled during: ALTER DATABASE CLOSE NORMAL

ARCH: Archiving is disabled

Shutting down archive processes

Archiving is disabled

Archive process shutdown avoided: active

ARCH: Archiving is disabled

Shutting down archive processes

Archiving is disabled

Archive process shutdown avoided: active

Fri Nov ::

Starting ORACLE instance (normal)

LICENSE_MAX_SESSION =

LICENSE_SESSIONS_WARNING =

SCN scheme

Using log_archive_dest parameter default value

LICENSE_MAX_USERS =

SYS auditing is disabled

Starting up ORACLE RDBMS Version:

System parameters with nondefault values:

processes =

timed_statistics = TRUE

shared_pool_size =

large_pool_size =

standby_archive_dest = /var/oradata/arch

fal_server = bmarksb

fal_client = bmark

log_archive_format = %t_%sarc

CJQ started with pid=

Fri Nov ::

ARCH: STARTING ARCH PROCESSES

ARC started with pid=

ARC: Archival started

ARC started with pid=

Fri Nov ::

ARCH: STARTING ARCH PROCESSES COMPLETE

Fri Nov ::

ARC: Archival started

Fri Nov ::

ARC: Thread not mounted

Fri Nov ::

ARC: Thread not mounted

Fri Nov ::

alter database mount standby database

Fri Nov ::

Successful mount of redo thread with mount id

Fri Nov ::

Standby Database mounted

Completed: alter database mount standby database

Fri Nov ::

ALTER DATABASE RECOVER managed standby database disconnect

Attempt to start background Managed Standby Recovery process

MRP started with pid=

MRP: Background Managed Standby Recovery process started

Fri Nov ::

Completed: ALTER DATABASE RECOVER managed standby database d

Fri Nov ::

Media Recovery Waiting for thread seq#

Media Recovery Log /var/oradata/arch/_arc

Media Recovery Waiting for thread seq#

Media Recovery Log /var/oradata/arch/_arc

Media Recovery Waiting for thread seq#

看来以后不能再采购联志服务器了

The End

上一篇:如何连接两台Oracle服务器(服务器A、服务器B,均装有NT)?

下一篇:建立数据库认证的FTP