![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||||||||
Solution Type Sun Alert Sure Solution 2308117.1 : (DB40) Database instance startup slow or ASM rebalance slow on 8-socket database servers with 12.1.0.2.170718 or 12.1.0.2.170814
In this Document
Applies to:Exadata X7-8 HardwareOracle Exadata Storage Server Software - Version 12.1.2.3.0 and later Exadata X6-8 Hardware Exadata X4-8 Hardware Exadata X5-8 Hardware Information in this document applies to any platform. DescriptionOne or both of the following issues may occur:
OccurrencePre-requisite ConditionsThe following conditions must exist for these issues to occur:
1. To determine if the database server is an 8-socket or 2-socket server run the following command as root on the first database server: # dmidecode -s system-product-name
ORACLE SERVER X5-8 Only X4-8 and later generation 8-socket database servers are affected by this issue. 2. To determine Exadata version run the following command as root on database servers: # imageinfo -ver
12.1.2.3.5.170418
3. To determine if the fix for bug 25256170 is installed run the following OPatch command. Run this command for both the database home and grid infrastructure home. The following example output shows the fix for bug 25256170 is installed: $ $ORACLE_HOME/OPatch/opatch lsinventory -bugs_fixed | grep 25256170
25256170 25869760 Tue Jul 18 22:59:12 PDT 2017 TRACKING BUG FOR BDSQL 3.1.0 RELEASE ON TOP OF
This issue occurs on database servers with multiple loopback IP addresses (i.e. loopback addresses in addition to 127.0.0.1, like 127.0.0.2/3/4, defined and used by the database or ASM). Multiple loopback IP addresses are created only on X4-8 and later generation 8-socket database servers running Exadata 12.1.2.3.0 or higher.
SymptomsSymptoms include the following:
WorkaroundN/A NOTE: The recommended resolution is to apply the patch. As a temporary workaround, it is possible to limit the number of loopback IP addresses to one by setting an underscore initialization parameter. However, configuring this workaround will prevent a customer from allocating more than 64k database processes, which may substantially impact a customer's ability to run normal workload. In such cases the patch must be applied to permit more than 64k processes. Before configuring the workaround check v$process during peak workload to determine the number of processes the customer's application(s) must support. To implement the workaround, set initialization parameter _bug20480623_posting_ips="127.0.0.1" in both ASM and database initialization files. Ensure this parameter is removed after applying the patch. PatchesUpdate grid infrastructure and database homes to 12.1.0.2.171017, or later. Alternatively, apply <patch 26762083> to 12.1.0.2 grid infrastructure and database homes that have the fix for bug 25256170 installed. Note that the patch available for 12.1.0.2.170718 is applicable to both 12.1.0.2.170718 and 12.1.0.2.170814 software homes.
History18-Oct-2017 - Fixed in 12.1.0.2.171017; patch for 12.1.0.2.170718 also applicable to 12.1.0.2.170814 Attachments This solution has no attachment |
||||||||||||||||||||||||||
|