Shulou(Shulou.com)05/31 Report--

This article mainly introduces what to do when the host computer modifies the time zone under RAC so that db cannot open. It has a certain reference value. Interested friends can refer to it. I hope you can learn a lot after reading this article. Let's take a look at it.

11.2.0.4.rac host modifies the time zone so that db cannot open

Os:redhat linux

Db:11.2.0.4 rac

After desc:crs starts, everything except db can start normally.

Check the log of crs and db. The last modification time of the file is the same as the host time, but the time in log is different. The following is the log in crs and dblog.

Crs log

= =

2015-05-04 10 30 24 139:

[client (19430)] CRS-4743:File / u02/app/11.2.0/grid/oc4j/j2ee/home/OC4J_DBWLM_config/system-jazn-data.xml was updated from OCR (Size: 13365 (New), 13378 (Old) bytes)

2015-05-04 10 31V 33.583:

[cssd (18287)] CRS-1601:CSSD Reconfiguration complete. Active nodes are gzsjdb1 gzsjdb2.

2015-05-04 10 31R 56.583:

[crsd (19096)] CRS-2772:Server 'gzsjdb2' has been assigned to pool' Generic'.

2015-05-04 10 31R 56.584:

[crsd (19096)] CRS-2772:Server 'gzsjdb2' has been assigned to pool' ora.jzxn'. # Log when something goes wrong

2015-05-04 16 31V 02.619: # Log after the problem is resolved

[client (26295)] CRS-10051:CVU found following errors with Clusterware setup: PRVF-7573: Sufficient swap size is not available on node "gzsjdb1" [Required = 16GB (1.6777216E7KB); Found = 10GB (1.0485752E7KB)]

PRVF-5415: Check to see if NTP daemon or service is running failed

PRVG-1101: SCAN name "scan-cl

Db log

= =

Fri Jun 12 03:45:16 2015 # Log when something goes wrong

Thread 1 advanced to log sequence 54 (LGWR switch)

Current log# 3 seq# 54 mem# 0: / oradata/oradata/jzxn/redo03.log

Fri Jun 12 03:47:38 2015

Thread 1 cannot allocate new log, sequence 55

Checkpoint not complete

Current log# 3 seq# 54 mem# 0: / oradata/oradata/jzxn/redo03.log

Fri Jun 12 03:47:43 2015

Opidcl aborting process unknown ospid (29020) as a result of ORA-28

Fri Jun 12 05:13:24 2015

Thread 1 advanced to log sequence 55 (LGWR switch)

Current log# 1 seq# 55 mem# 0: / oradata/oradata/jzxn/redo01.log

Fri Jun 12 14:31:04 2015 # Log after problem Resolution

Starting ORACLE instance (normal)

* Large Pages Information *

Per process system memlock (soft) limit = UNLIMITED

Total Shared Global Region in Large Pages = 0 KB (0%)

The solution process: did not pay attention to this time problem at first, after restarting the crs, the resources of db are still abnormal, and then it is found that the log time is incorrect. After asking the project team node 2 from the default time (Etc/GMT-1) to the time zone of East Zone 8 (Asia/Shanghai), Node 2 cannot connect to db, and Node 1 can still connect after modifying the time zone. To this day, Node 1 cannot connect to db.

The db log, crs log, and so on are inconsistent with the host time because in the new release of rac, grid also has its own time zone, and during installation, the default value is the same as the operating system's TZ environment variable.

This example is due to time inconsistency, resulting in db cannot open, after modifying the grid time zone, restart crs,db can be normal open.

1. View the system time zone

$cat / etc/sysconfig/clock

ZONE=Asia/Shanghai

two。 View the time zone configured in crs

[root@gzsjdb1 install] # cat s_crsconfig_gzsjdb1_env.txt.bak

# This file can be used to modify the NLS_LANG environment variable, which determines the charset to be used for messages.

# For example, a new charset can be configured by setting NLS_LANG=JAPANESE_JAPAN.UTF8

# Do not modify this file except to change NLS_LANG, or under the direction of Oracle Support Services

TZ=Etc/GMT-1 # is still the default US time zone

NLS_LANG=AMERICAN_AMERICA.AL32UTF8

TNS_ADMIN=

ORACLE_BASE=

3. Change the time zone of crs to Asia/Shanghai

[root@gzsjdb1 install] # cat s_crsconfig_gzsjdb1_env.txt

# This file can be used to modify the NLS_LANG environment variable, which determines the charset to be used for messages.

# For example, a new charset can be configured by setting NLS_LANG=JAPANESE_JAPAN.UTF8

# Do not modify this file except to change NLS_LANG, or under the direction of Oracle Support Services

TZ=Asia/Shanghai

NLS_LANG=AMERICAN_AMERICA.AL32UTF8

TNS_ADMIN=

ORACLE_BASE=

[root@gzsjdb1 install] # pwd

/ u02/app/11.2.0/grid/crs/install

[root@gzsjdb1 install] #

4. Restart crs

5. It has been verified that the crs log and db log are consistent with the host, and the database can be logged in through plsqldev.

[root@gzsjdb2 ~] # date

Fri Jun 12 15:12:58 CST 2015

Thank you for reading this article carefully. I hope the article "what to do when db cannot open due to host modification under RAC" shared by the editor is helpful to everyone. At the same time, I also hope you can support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.