はじめに
MSE では Database が生成するアーカイブログを定期的に削除するプログラムが動かないために、アーカイブログが増大し、MSE サービスが停止するという問題が発生しておりました。
一旦、アーカイブログが増大すると、その削除を行いシステム回復させるには、複雑な手順が必要となっておりました。
参照:
Mobility Services Engine (MSE) サービスが停止する問題
MSE 8.0.140.0 以降では、増大したアーカイブログを削除する自動スクリプトが実装されておりますので、ご利用ください。
参照:
Release Notes for Cisco Mobility Services Engine, Release 8.0.140.x
Release Notes for Cisco Mobility Services Engine, Release 8.0.150.x
アーカイブログ増大の確認方法
1. 'getserverinfo' を取得できない
[root@CISCOMSE ~]# getserverinfo
Health Monitor is running
Retrieving MSE Services status.
Checking status of service at port 7555
Checking status of service at port 7555
:
Checking status of service at port 7555
Failed to get the status for process at port 7555
2. 'rundiag' 出力において、/opt/data/flash_recovery_area/MSEORCL/archivelog 配下で数十GByte を消費している
[root@CISCOMSE ~]# rundiag
:
------- Disk Usage for /opt/data/ -------
8.0K /opt/data/flash_recovery_area/MSEORCL/onlinelog
:
8.0K /opt/data/flash_recovery_area/MSEORCL/archivelog/2018_01_25
70G /opt/data/flash_recovery_area/MSEORCL/archivelog
3. /opt/mse/logs/framework/archiveLogsDeletion_mseorcl.log の最後に記録されているアーカイブログ削除の最終実行タイムスタンプが古い
[root@CISCOMSE ~]# clock
Sat 27 Jan 2018 10:18:40 AM JST -0.031961 seconds
[root@CISCOMSE ~]# tail -200 /opt/mse/logs/framework/archiveLogsDeletion_mseorcl.log
:
Recovery Manager: Release 11.2.0.4.0 - Production on Thu Jan 18 08:36:45 2018
アーカイブログ削除スクリプトの実行方法
1. /opt/mse/framework/bin/manualDeleteArchiveLogs.sh を実行
[root@CISCOMSE ~]# /opt/mse/framework/bin/manualDeleteArchiveLogs.sh
2. 途中、MSE サービス停止してよいか尋ねられるので、"y" を選択
MSE services need to be stopped before deleting the archive logs.
Continue with stopping MSE services? (y/n): y
================================================================================
Stopping MSE Platform
Apache Service is running...will not stop it
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJ configured for FIPS mode
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJCE turning on FIPS...
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJCEProvider version 2.0520150519 loading...
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - Executing Java version = 1.7.0_45
Shutting down framework and services ......
Framework and services successfully shutdown. Shutting down database .....
MSE platform shutdown complete
3. アーカイブログ削除を続けてよいか尋ねられるので、"y" を選択
================================================================================
MSE services stopped. Do you want to continue/ (y/n): y
Oracle DB is already shut down.
Archive Logs size before deletion = 9572
Starting Oracle DB ...
================================================================================
Starting Listener and Database for SID: mseorcl
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJ configured for FIPS mode
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJCE turning on FIPS...
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJCEProvider version 2.0520150519 loading...
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - Executing Java version = 1.7.0_45
4. あとはスクリプトが終了するのを待つ
5. 下記出力がされたら終了
Starting MSE Platform
Flushing any pending data from Admin Process read and write pipe.
Starting Apache HTTPD Server
Apache Server is already running. Skipping restart.
Starting Health Monitor, Waiting to check the status.
Health Monitor successfully started
Starting Admin process...
Started Admin process.
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJ configured for FIPS mode
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJCE turning on FIPS...
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - CiscoJCEProvider version 2.0520150519 loading...
[main] INFO com.cisco.ciscossl.provider.ciscojce.CiscoJCEProvider - Executing Java version = 1.7.0_45
Database started successfully. Starting framework and services ...
Database started successfully. Starting framework and services ..................
Framework and services successfully started
================================================================================
Archive log deletion successful.
Exiting.
