Thinking Out Loud

January 28, 2017

Goldengate Importance of Commenting

Filed under: GoldenGate — mdinh @ 2:35 am

I was curious to determine effect for modifying ./dirdat/aa to dirdat/aa for Goldengate parameter.

While it may look to be the same, it is not treated the same.

$ ll dirdat/*
-rw-r-----. 1 oracle oinstall    3719 Jan 27 14:15 dirdat/aa000000000
-rw-r-----. 1 oracle oinstall 8086335 Jan 27 18:16 dirdat/aa000000001

$ ll ./dirdat/*
-rw-r-----. 1 oracle oinstall    3719 Jan 27 14:15 ./dirdat/aa000000000
-rw-r-----. 1 oracle oinstall 8086335 Jan 27 18:16 ./dirdat/aa000000001

Here is what happens when parameter is modified from ./dirdat/aa to dirdat/aa

$ grep EXTTRAIL ggserr.log
2017-01-27 10:45:15  INFO    OGG-00987  Oracle GoldenGate Command Interpreter for Oracle:  GGSCI command (oracle): ADD EXTTRAIL ./dirdat/aa EXTRACT e_hawk, MEGABYTES 500.
2017-01-27 10:45:16  INFO    OGG-00987  Oracle GoldenGate Command Interpreter for Oracle:  GGSCI command (oracle): ADD EXTRACT p_hawk  EXTTRAILSOURCE ./dirdat/aa.
2017-01-27 18:18:26  ERROR   OGG-01044  Oracle GoldenGate Capture for Oracle, e_hawk.prm:  The trail 'dirdat/aa' is not assigned to extract 'E_HAWK'. 
Assign the trail to the extract with the command "ADD EXTTRAIL/RMTTRAIL dirdat/aa, EXTRACT E_HAWK".

How do you find how trail file as added?

GGSCI (arrow1.localdomain) 1> info all

Program     Status      Group       Lag at Chkpt  Time Since Chkpt

MANAGER     RUNNING
EXTRACT     ABENDED     E_HAWK      00:00:04      00:12:25
EXTRACT     STOPPED     P_HAWK      00:00:00      07:44:04


GGSCI (arrow1.localdomain) 2> info e*

EXTRACT    E_HAWK    Last Started 2017-01-27 18:18   Status ABENDED
Checkpoint Lag       00:00:04 (updated 00:12:27 ago)
Log Read Checkpoint  Oracle Integrated Redo Logs
                     2017-01-27 18:16:52
                     SCN 0.3369629 (3369629)


GGSCI (arrow1.localdomain) 3> info e* showch

EXTRACT    E_HAWK    Last Started 2017-01-27 18:18   Status ABENDED
Checkpoint Lag       00:00:04 (updated 00:12:41 ago)
Log Read Checkpoint  Oracle Integrated Redo Logs
                     2017-01-27 18:16:52
                     SCN 0.3369629 (3369629)


Current Checkpoint Detail:

Read Checkpoint #1

  Oracle Integrated Redo Log

  Startup Checkpoint (starting position in the data source):
    Timestamp: 2017-01-27 10:45:14.000000
    SCN: Not available

  Recovery Checkpoint (position of oldest unprocessed transaction in the data source):
    Timestamp: 2017-01-27 18:16:52.000000
    SCN: 0.3369628 (3369628)

  Current Checkpoint (position of last record read in the data source):
    Timestamp: 2017-01-27 18:16:52.000000
    SCN: 0.3369629 (3369629)

Write Checkpoint #1

  GGS Log Trail

  Current Checkpoint (current write position):
    Sequence #: 1
    RBA: 8086335
    Timestamp: 2017-01-27 18:16:56.302658
    Extract Trail: ./dirdat/aa
    Seqno Length: 9
    Flip Seqno Length: No
    Trail Type: EXTTRAIL

Header:
  Version = 2
  Record Source = A
  Type = 13
  # Input Checkpoints = 1
  # Output Checkpoints = 1

File Information:
  Block Size = 2048
  Max Blocks = 100
  Record Length = 2048
  Current Offset = 0

Configuration:
  Data Source = 3
  Transaction Integrity = 1
  Task Type = 0

Status:
  Start Time = 2017-01-27 18:18:26
  Last Update Time = 2017-01-27 18:16:56
  Stop Status = A
  Last Result = 520



GGSCI (arrow1.localdomain) 4>

Alternatively, make it easier by commenting parameter files.

$ head dirprm/e_hawk.prm
EXTRACT e_hawk
-- CHECKPARAMS
-- ADD EXTRACT e_hawk, INTEGRATED TRANLOG, BEGIN NOW
-- ADD EXTTRAIL ./dirdat/aa EXTRACT e_hawk, MEGABYTES 500
USERIDALIAS ggs_user
EXTTRAIL ./dirdat/aa
INCLUDE dirprm/global_ggenv.inc
Advertisements

January 20, 2017

Goldengate Network Troubleshooting

Filed under: GoldenGate — mdinh @ 2:50 pm

We encounter the following error:

GGS ERROR 150  Oracle GoldenGate Capture for Oracle, pump.prm:  TCP/IP error 9 (Bad file descriptor).

Note: server collectors at target will not be started and ports not opened until pump at source is started.
Using nc to test port.

$ nc -v -z -w 3 target.local 7960; echo $?
nc: connect to target.local port 7960 (tcp) failed: Connection refused
1

$ nc -v -z -w 3 target.local 7970; echo $?
Connection to target.local 7970 port [tcp/*] succeeded!
0

Not preferred and does not mean it’s wrong – Entry starting at 16.

DYNAMICPORTLIST 7960-7980 (20)

In hindsight, I should have started a few more pump extracts
to determine if Entry values cycle back to 0 and
if port assignment will start at 7960 or will fail.

This is what happens when dozen of pump extracts are stopped and started in groups while manager is RUNNING.

Sending GETPORTINFO request to MANAGER ...

Dynamic Port List

Starting Index 20
Reassign Delay 30 seconds

Entry Port  Error  Process     Assigned             Program
----- ----- ----- ----------   -------------------  -------
  16   7976     0       6260   2017/01/19 12:06:12  Server
  17   7977     0       6261   2017/01/19 12:06:12  Server
  18   7978     0       6262   2017/01/19 12:06:12  Server
  19   7979     0       6263   2017/01/19 12:06:12  Server

Houston, we have a problem.
Look at Error column.
Anything other than 0 is not good.
Look at the date assigned.
These look to be orphaned processes and manager still thinks port is assigned.

GGSCI> SEND MANAGER GETPORTINFO

Sending GETPORTINFO request to MANAGER ...

Dynamic Port List

Starting Index 18
Reassign Delay 30 seconds

Entry Port  Error  Process     Assigned             Program
----- ----- ----- ----------   -------------------  -------
   0   7841    98      31663   2016/12/30 08:03:18  Server
   1   7842    98      31664   2016/12/30 08:03:18  Server
   2   7843    98                
   3   7844    98                
   4   7845    98                
   5   7846    98       1243   2016/12/30 08:14:01  Server
   6   7847    98       4543   2016/12/30 08:34:28  Server
   7   7848    98       4815   2016/12/30 08:35:55  Server
   8   7849    98       5094   2016/12/30 08:37:07  Server
   9   7850    98       5151   2016/12/30 08:37:20  Server
  10   7851    98       5152   2016/12/30 08:37:25  Server
  11   7852    98      26856   2017/01/17 21:57:38  Server
  12   7853    98      32133   2017/01/17 22:30:35  Server
  13   7854    98      16390   2017/01/06 03:56:56  Server
  14   7855    98      32220   2017/01/17 22:30:41  Server
 
  15   7856     0       4774   2017/01/17 22:57:40  Server
  16   7857     0       4777   2017/01/17 22:57:52  Server
  17   7858     0       4779   2017/01/17 22:57:59  Server
  
  18   7859    98      26854   2017/01/17 21:57:38  Server
  19   7860    98      26855   2017/01/17 21:57:38  Server

This is what I like.
Notice the timestamp for Assigned are all the same.
This is because pump from source was started using wildcard, i.e. start p*
Oracle support does not recommend this and YMMV.

GGSCI> !
SEND MANAGER GETPORTINFO

Sending GETPORTINFO request to MANAGER ...

Dynamic Port List

Starting Index 14
Reassign Delay 30 seconds

Entry Port  Error  Process     Assigned             Program
----- ----- ----- ----------   -------------------  -------
   0   7960     0       7744   2017/01/19 12:15:13  Server
   1   7961     0       7745   2017/01/19 12:15:13  Server
   2   7962     0       7746   2017/01/19 12:15:13  Server
   3   7963     0       7747   2017/01/19 12:15:13  Server
   4   7964     0       7748   2017/01/19 12:15:13  Server
   5   7965     0       7749   2017/01/19 12:15:13  Server
   6   7966     0       7750   2017/01/19 12:15:13  Server
   7   7967     0       7751   2017/01/19 12:15:13  Server
   8   7968     0       7752   2017/01/19 12:15:13  Server
   9   7969     0       7753   2017/01/19 12:15:13  Server
  10   7970     0       7754   2017/01/19 12:15:13  Server
  11   7971     0       7755   2017/01/19 12:15:13  Server
  12   7972     0       7756   2017/01/19 12:15:13  Server
  13   7973     0       7757   2017/01/19 12:15:13  Server

GGSCI> sh ps -ef|grep ./server

512       7744  7742  0 12:15 ?        00:00:00 ./server -p 7960 -k -l /ggs1040/ggserr.log
512       7745  7742  0 12:15 ?        00:00:00 ./server -p 7961 -k -l /ggs1040/ggserr.log
512       7746  7742  0 12:15 ?        00:00:00 ./server -p 7962 -k -l /ggs1040/ggserr.log
512       7747  7742  0 12:15 ?        00:00:00 ./server -p 7963 -k -l /ggs1040/ggserr.log
512       7748  7742  0 12:15 ?        00:00:00 ./server -p 7964 -k -l /ggs1040/ggserr.log
512       7749  7742  0 12:15 ?        00:00:00 ./server -p 7965 -k -l /ggs1040/ggserr.log
512       7750  7742  0 12:15 ?        00:00:00 ./server -p 7966 -k -l /ggs1040/ggserr.log
512       7751  7742  0 12:15 ?        00:00:00 ./server -p 7967 -k -l /ggs1040/ggserr.log
512       7752  7742  0 12:15 ?        00:00:00 ./server -p 7968 -k -l /ggs1040/ggserr.log
512       7753  7742  0 12:15 ?        00:00:00 ./server -p 7969 -k -l /ggs1040/ggserr.log
512       7754  7742  0 12:15 ?        00:00:00 ./server -p 7970 -k -l /ggs1040/ggserr.log
512       7755  7742  0 12:15 ?        00:00:00 ./server -p 7971 -k -l /ggs1040/ggserr.log
512       7756  7742  0 12:15 ?        00:00:00 ./server -p 7972 -k -l /ggs1040/ggserr.log
512       7757  7742  0 12:15 ?        00:00:00 ./server -p 7973 -k -l /ggs1040/ggserr.log
512       7759  7741  0 12:16 pts/1    00:00:00 sh -c ps -ef|grep ./server
512       7761  7759  0 12:16 pts/1    00:00:00 grep ./server

GGSCI>

Good followup reading.
OGG GGS Error 150: No Dynamic Ports Available Orphan Ports Server Collector (Doc ID 965356.1)

A SERVER process is an "orphan" if netstat or lsof shows only a "listening" port, with no "ESTABLISHED" connections.

Updated Jan 25 2017
In TCP networking, what is a FIN_WAIT state?
https://kb.iu.edu/d/ajmi

Sending GETPORTINFO request to MANAGER ...

Dynamic Port List

Starting Index 32
Reassign Delay 30 seconds

Entry Port  Error  Process     Assigned             Program
----- ----- ----- ----------   -------------------  -------
   0   7841    98                
   1   7842    98                
   2   7843    98                
   3   7844    98                
   4   7845    98                
   5   7846     0       1397   2017/01/24 21:03:55  Server
   6   7847    98                
   7   7848     0       1398   2017/01/24 21:03:55  Server
   8   7849    98                
   9   7850     0       1399   2017/01/24 21:03:55  Server
  10   7851     0       1400   2017/01/24 21:03:55  Server
  11   7852     0       1547   2017/01/24 21:04:24  Server
  12   7853    98                
  13   7854    98                
  14   7855    98                
  15   7856    98                
  16   7857     0       1548   2017/01/24 21:04:24  Server
  17   7858     0       1549   2017/01/24 21:04:24  Server
  18   7859    98                
  19   7860    98                
  20   7861    98                
  21   7862    98                
  22   7863    98                
  23   7864    98                
  24   7865     0       1550   2017/01/24 21:04:24  Server
  25   7866     0       1587   2017/01/24 21:04:38  Server
  26   7867     0       1588   2017/01/24 21:04:38  Server
  27   7868     0       1589   2017/01/24 21:04:38  Server
  28   7869     0       1590   2017/01/24 21:04:38  Server
  29   7870     0       1596   2017/01/24 21:05:00  Server
  31   7872     0       6491   2017/01/24 21:31:14  Server
  

$ netstat -an|grep 7864
tcp        0      0 0.0.0.0:7864                0.0.0.0:*                   LISTEN      
tcp        1      0 10.80.25.64:7864            10.80.25.64:42242           CLOSE_WAIT  
tcp        0      0 10.80.25.64:42242           10.80.25.64:7864            FIN_WAIT2 

$ netstat -an|grep 7870
tcp        0      0 0.0.0.0:7870                0.0.0.0:*                   LISTEN      
tcp        0      0 10.80.25.64:7870            10.80.26.36:13810           ESTABLISHED

$ netstat -an|grep 7841
tcp        0      0 0.0.0.0:7841                0.0.0.0:*                   LISTEN      
tcp        0      0 10.80.25.64:39288           10.80.25.64:7841            TIME_WAIT

January 7, 2017

Not Another Post Configuring HugePages for Oracle on Linux (x86-64)

Filed under: 11g,linux,oracle — mdinh @ 6:46 am

USE_LARGE_PAGES (TRUE/FALSE/ONLY)

Test case is only for one database instance on server.

DB is using memory_target.

SQL> show parameter use_large_pages

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
use_large_pages                      string      TRUE

SQL> show parameter sga

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
lock_sga                             boolean     FALSE
pre_page_sga                         boolean     FALSE
sga_max_size                         big integer 768M
sga_target                           big integer 0

SQL> show parameter pga

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
pga_aggregate_target                 big integer 0

SQL> show parameter target

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
archive_lag_target                   integer     900
db_flashback_retention_target        integer     1440
fast_start_io_target                 integer     0
fast_start_mttr_target               integer     0
memory_max_target                    big integer 1G
memory_target                        big integer 1G
parallel_servers_target              integer     16
pga_aggregate_target                 big integer 0
sga_target                           big integer 0

SQL> show sga

Total System Global Area  801701888 bytes
Fixed Size                  2257520 bytes
Variable Size             276827536 bytes
Database Buffers          520093696 bytes
Redo Buffers                2523136 bytes
SQL> exit

Gather memory configuration.

$ grep Huge /proc/meminfo
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB

++++++++++

$ grep PageTables /proc/meminfo
PageTables:        24428 kB

++++++++++

$ free
             total       used       free     shared    buffers     cached
Mem:       1534604    1484476      50128       1512      20352     335916
-/+ buffers/cache:    1128208     406396
Swap:      4194300          0    4194300

Calculate memlock.

SQL> select round(1534604*.875) from dual;

ROUND(1534604*.875)
-------------------
            1342779

Edit /etc/security/limits.conf to add memlock as shown below.
Logout, login, check ulimit -l

$ grep memlock /etc/security/limits.conf
#        - memlock - max locked-in-memory address space (KB)
oracle   soft   memlock    1342779
oracle   hard   memlock    1342779

++++++++++

$ ulimit -l
134217728

Run hugepages_settings.sh ERROR due to memory target being used.

$ ./hugepages_settings.sh

This script is provided by Doc ID 401749.1 from My Oracle Support
(http://support.oracle.com) where it is intended to compute values for
the recommended HugePages/HugeTLB configuration for the current shared
memory segments on Oracle Linux. Before proceeding with the execution please note following:
 * For ASM instance, it needs to configure ASMM instead of AMM.
 * The 'pga_aggregate_target' is outside the SGA and
   you should accommodate this while calculating SGA size.
 * In case you changes the DB SGA size,
   as the new SGA will not fit in the previous HugePages configuration,
   it had better disable the whole HugePages,
   start the DB with new SGA size and run the script again.
And make sure that:
 * Oracle Database instance(s) are up and running
 * Oracle Database 11g Automatic Memory Management (AMM) is not setup
   (See Doc ID 749851.1)
 * The shared memory segments can be listed by command:
     # ipcs -m


Press Enter to proceed...

***********
** ERROR **
***********
Sorry! There are not enough total of shared memory segments allocated for
HugePages configuration. HugePages can only be used for shared memory segments
that you can list by command:

    # ipcs -m

of a size that can match an Oracle Database SGA. Please make sure that:
 * Oracle Database instance is up and running
 * Oracle Database 11g Automatic Memory Management (AMM) is not configured

Remove memory target configuration from DB.
Note reset was used as shown:
alter system reset memory_target scope=spfile sid=’*’;
alter system reset memory_max_target scope=spfile sid=’*’;

oracle@arrow1:HAWKA:/home/oracle
$ sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Fri Jan 6 21:33:31 2017

Copyright (c) 1982, 2013, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning and Real Application Testing options

SQL> show parameter spfile

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
spfile                               string      /u01/app/oracle/product/11.2.0
                                                 .4/db_1/dbs/spfileHAWKA.ora
SQL> alter system reset memory_target scope=spfile sid='*';

System altered.

SQL> alter system reset memory_max_target scope=spfile sid='*';

System altered.

SQL> alter system set sga_max_size=768M scope=spfile sid='*';

System altered.

SQL> alter system set sga_target=768M scope=spfile sid='*';

System altered.

SQL> alter system set pga_aggregate_target=256M scope=spfile sid='*';

System altered.

SQL> shu immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup;
ORACLE instance started.

Total System Global Area  801701888 bytes
Fixed Size                  2257520 bytes
Variable Size             276827536 bytes
Database Buffers          520093696 bytes
Redo Buffers                2523136 bytes
Database mounted.
Database opened.
SQL> @show.sql
SQL> show parameter use_large_pages

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
use_large_pages                      string      TRUE
SQL> show parameter sga

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
lock_sga                             boolean     FALSE
pre_page_sga                         boolean     FALSE
sga_max_size                         big integer 768M
sga_target                           big integer 768M
SQL> show parameter pga

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
pga_aggregate_target                 big integer 256M
SQL> show parameter target

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
archive_lag_target                   integer     900
db_flashback_retention_target        integer     1440
fast_start_io_target                 integer     0
fast_start_mttr_target               integer     0
memory_max_target                    big integer 0
memory_target                        big integer 0
parallel_servers_target              integer     16
pga_aggregate_target                 big integer 256M
sga_target                           big integer 768M
SQL> show sga

Total System Global Area  801701888 bytes
Fixed Size                  2257520 bytes
Variable Size             276827536 bytes
Database Buffers          520093696 bytes
Redo Buffers                2523136 bytes
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning and Real Application Testing options
oracle@arrow1:HAWKA:/home/oracle
$

Run hugepages_settings.sh – Recommended setting: vm.nr_hugepages = 388

$ ./hugepages_settings.sh

This script is provided by Doc ID 401749.1 from My Oracle Support
(http://support.oracle.com) where it is intended to compute values for
the recommended HugePages/HugeTLB configuration for the current shared
memory segments on Oracle Linux. Before proceeding with the execution please note following:
 * For ASM instance, it needs to configure ASMM instead of AMM.
 * The 'pga_aggregate_target' is outside the SGA and
   you should accommodate this while calculating SGA size.
 * In case you changes the DB SGA size,
   as the new SGA will not fit in the previous HugePages configuration,
   it had better disable the whole HugePages,
   start the DB with new SGA size and run the script again.
And make sure that:
 * Oracle Database instance(s) are up and running
 * Oracle Database 11g Automatic Memory Management (AMM) is not setup
   (See Doc ID 749851.1)
 * The shared memory segments can be listed by command:
     # ipcs -m


Press Enter to proceed...

Recommended setting: vm.nr_hugepages = 388

Manually calculate vm.nr_hugepages in KB using [sga_max_size(768M) * 1024 * Hugepagesize(2048 kB)]

SQL> select round(768*1024/2048)+1 from dual;

ROUND(768*1024/2048)+1
----------------------
                   385

SQL>

From alert log – vm.nr_hugepages=385

Fri Jan 06 21:34:33 2017
Starting ORACLE instance (normal)
************************ Large Pages Information *******************
Per process system memlock (soft) limit = 128 GB

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

Large Pages used by this instance: 0 (0 KB)
Large Pages unused system wide = 0 (0 KB)
Large Pages configured system wide = 0 (0 KB)
Large Page size = 2048 KB

RECOMMENDATION:
  Total System Global Area size is 770 MB. For optimal performance,
  prior to the next instance restart:
  1. Increase the number of unused large pages by at least 385 
     (page size 2048 KB, total size 770 MB) system wide to get 
     100% of the System Global Area allocated with large pages
********************************************************************

Configure Dynamic vm.nr_hugepages=385

[root@arrow1 ~]# sysctl -w vm.nr_hugepages=385
vm.nr_hugepages = 385
[root@arrow1 ~]# grep Huge /proc/meminfo
HugePages_Total:     353
HugePages_Free:      353
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB

Configure Static vm.nr_hugepages=385 and restart server – Oracle recommended.

[root@arrow1 ~]# grep vm.nr_hugepages /etc/sysctl.conf
[root@arrow1 ~]# vi /etc/sysctl.conf
[root@arrow1 ~]# grep vm.nr_hugepages /etc/sysctl.conf
vm.nr_hugepages=385
[root@arrow1 ~]# cat /etc/system-release
Oracle Linux Server release 6.6
[root@arrow1 ~]#

HugePages on Oracle Linux 64-bit (Doc ID 361468.1)
Modified:Mar 7, 2016

Step 6: Stop all the database instances and reboot the server
(Although settings could have been done dynamically they would not be effective to the extent we require before a reboot.
The best practice is to do a persistent system configuration and perform a reboot to complete the configuration as presented through the steps above)

ALERT: Disable Transparent HugePages on SLES11, RHEL6, RHEL7, OL6, OL7, and UEK2 and above (Doc ID 1557478.1)
cat /boot/grub/grub.conf

Actual error example.

$ free 
              total        used        free      shared  buff/cache   available
Mem:      263760440    34016732   173314152      786468    56429556   228457668
Swap:      16777212           0    16777212

++++++++++

ARROW1:(SYS@HAWKA):PRIMARY> select round(263760440*.875) memlock from dual;

 MEMLOCK
----------
 230790385

ARROW1:(SYS@HAWKA):PRIMARY>

++++++++++

$ grep Huge /proc/meminfo
AnonHugePages:         0 kB
HugePages_Total:   15400
HugePages_Free:    15023
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB

$ grep memlock /etc/security/limits.conf
oracle	soft    memlock 	unlimited
oracle	hard    memlock 	unlimited

*.sga_max_size=32212254720/1024 = KB

SYS@HAWKA> select round(32212254720/1024/2048)+1 from dual;

ROUND(32212254720/1024/2048)+1
------------------------------
                         15361

select 'vm.nr_hugepages='||to_char(round(32212254720/1024/2048,-2)+100) hugepages
from dual
 3 ;

HUGEPAGES
---------------------
vm.nr_hugepages=15500

ARROW1:(SYS@HAWKA):PRIMARY>

From alert.log
    Thu Feb 09 15:16:55 2017
      PAGESIZE  AVAILABLE_PAGES  EXPECTED_PAGES  ALLOCATED_PAGES  ERROR(s)
    Thu Feb 09 15:16:55 2017
         2048K            15023           15362           15012        NONE

January 6, 2017

Check Oracle Preinstallation/Validated RPM Logs

Filed under: 11g,12c,linux,oracle — mdinh @ 12:50 am

Quick and dirty note to self.

Grid Infrastructure Installation Guide
https://docs.oracle.com/cd/E11882_01/install.112/e41961/prelinux.htm#CWLIN2928

Check the RPM log file to review the system configuration changes. For example:

Oracle Linux 6:
/var/log/oracle-rdbms-server-11gR2-preinstall/results/orakernel.log

Oracle Linux 5 and Oracle Linux 4:
/var/log/oracle-validated/results/orakernel.log

Here are the results for 12c with Oracle Linux 6
[root@arrow1 ~]# cd /var/log/oracle-rdbms-server-12cR1-preinstall/
[root@arrow1 oracle-rdbms-server-12cR1-preinstall]# ls
backup results
[root@arrow1 oracle-rdbms-server-12cR1-preinstall]# ll *
backup:
total 8
drwx——. 2 root root 4096 Apr 26 2014 Apr-26-2014-08-37-17
drwx——. 2 root root 4096 Jun 24 2015 Jun-24-2015-17-20-47

results:
total 4
-rw-r–r–. 1 root root 3322 Jun 24 2015 orakernel.log
[root@arrow1 oracle-rdbms-server-12cR1-preinstall]# cat /etc/system-release
Oracle Linux Server release 6.6
[root@arrow1 oracle-rdbms-server-12cR1-preinstall]#

Here are the results for 12c with Oracle Linux 7
[root@owl ~]# cd /var/log/oracle-rdbms-server-12cR1-preinstall/
[root@owl oracle-rdbms-server-12cR1-preinstall]# ls
backup results
[root@owl oracle-rdbms-server-12cR1-preinstall]# ll *
backup:
total 0
drwx——. 2 root root 91 Dec 13 00:03 Dec-13-2016-00-03-21

results:
total 4
-rw-r–r–. 1 root root 3584 Dec 13 00:03 orakernel.log
[root@owl oracle-rdbms-server-12cR1-preinstall]# cat /etc/system-release
Oracle Linux Server release 7.3
[root@owl oracle-rdbms-server-12cR1-preinstall]#

Create a free website or blog at WordPress.com.