Postgres Master Slave setup

 


bash-4.2$ pwd

/database/edb/as14

bash-4.2$ cat postgresql.conf | grep 'max_wal_senders\|max_replication_slots\|wal_level\|hot_standby\|archive_mode\|archive_command\|shared_preload_libraries'

wal_level = replica # minimal, replica, or logical

archive_mode = on # enables archiving; off, on, or always

archive_command = '/bin/true'

#archive_command = 'test ! -f barman@postonline:/var/lib/barman/dev-pgsql/incoming/%f && rsync -a %p barman@postonline:/var/lib/barman/dev-pgsql/incoming/%f' # command to use to archive a logfile segment

max_wal_senders = 10 # max number of walsender processes

max_replication_slots = 10 # max number of replication slots

hot_standby = on # "off" disallows queries during recovery

#hot_standby_feedback = off # send info from standby to prevent

shared_preload_libraries = '$libdir/dbms_pipe,$libdir/edb_gen,$libdir/dbms_aq,repmgr'

bash-4.2$ 


bash-4.2$ /usr/edb/as14/bin/psql -d postgres -U enterprisedb

psql (14.11.0)

Type "help" for help.


postgres=# create user repmgr;

CREATE ROLE

postgres=# create database repmgr with owner repmgr;

CREATE DATABASE

postgres=# \l

                                           List of databases

   Name    |    Owner     | Encoding |   Collate   |    Ctype    | ICU |       Access privileges       

-----------+--------------+----------+-------------+-------------+-----+-------------------------------

 dev       | test         | UTF8     | C           | C           |     | 

 edb       | enterprisedb | UTF8     | C           | C           |     | 

 postgres  | enterprisedb | UTF8     | C           | C           |     | 

 repmgr    | repmgr       | UTF8     | C           | C           |     | 

 sit       | test         | UTF8     | en_US.UTF-8 | en_US.UTF-8 |     | 

 template0 | enterprisedb | UTF8     | C           | C           |     | =c/enterprisedb              +

           |              |          |             |             |     | enterprisedb=CTc/enterprisedb

 template1 | enterprisedb | UTF8     | C           | C           |     | =c/enterprisedb              +

           |              |          |             |             |     | enterprisedb=CTc/enterprisedb

(7 rows)


postgres=# 



bash-4.2$ /usr/edb/as14/bin/repmgr

ERROR: following errors were found in the configuration file:

  "node_id": required parameter was not found

  "node_name": required parameter was not found

  "data_directory": required parameter was not found

  "conninfo": required parameter was not found

DETAIL: configuration file is: "/etc/repmgr/14/repmgr.conf"

bash-4.2$ 



cat /etc/repmgr/14/repmgr.conf | grep "node_id\|node_name\|conninfo\|data_directory\|failover\|promote_command\|follow_command"


[root@postoffline ~]# cat /etc/repmgr/14/repmgr.conf | grep "node_id\|node_name\|conninfo\|data_directory\|failover\|promote_command\|follow_command"

node_id=1 # A unique integer greater than zero

node_name='postoffline' # An arbitrary (but unique) string; we recommend

conninfo='host=postoffline user=repmgr dbname=repmgr connect_timeout=2' # Database connection information as a conninfo string.

# For details on conninfo strings, see:

# "connect_timeout" in the conninfo string to determine

data_directory='/database/edb/as14' # The node's data directory. This is needed by repmgr

# defaults to the user defined in "conninfo".

# is used during failover to check visibility of the

#use_primary_conninfo_password=false # explicitly set "password" in "primary_conninfo"

#passfile='' # path to .pgpass file to include in "primary_conninfo"

failover='automatic' # one of 'automatic', 'manual'.

promote_command='/usr/edb/as14/bin/repmgr standby promote -f /etc/repmgr/14/repmgr.conf --log-to-file' # command repmgrd executes when promoting a new primary; use something like:

follow_command='/usr/edb/as14/bin/repmgr standby follow -f /etc/repmgr/14/repmgr.conf --log-to-file --upstream-node-id=%n' # command repmgrd executes when instructing a standby to follow a new primary;

# executing "follow_command" (defaults to the value set in "standby_reconnect_timeout")

#standby_disconnect_on_failover=false # If "true", in a failover situation wait for all standbys to

#sibling_nodes_disconnect_timeout=30 # If "standby_disconnect_on_failover" is true, the maximum length of time

#primary_visibility_consensus=false # If "true", only continue with failover if no standbys have seen

#failover_validation_command='' # Script to execute for an external mechanism to validate the failover

# value: %n (node_id), %a (node_name). *Must* be the same on all nodes.

#election_rerun_interval=15 # if "failover_validation_command" is set, and the command returns

#service_promote_command = '' # This parameter is intended for systems which provide a

# for "promote_command"; do not use "repmgr standby promote"

[root@postoffline ~]# 


bash-4.2$ cat pg_hba.conf | grep repmgr

host    repmgr          repmgr          192.168.0.110/32               md5

bash-4.2$ 




/usr/edb/as14/bin/repmgr -f /etc/repmgr/14/repmgr.conf primary register



bash-4.2$ /usr/edb/as14/bin/repmgr -f /etc/repmgr/14/repmgr.conf primary register

INFO: connecting to primary database...

NOTICE: attempting to install extension "repmgr"

ERROR: "repmgr" is not a superuser and no superuser name supplied

HINT: supply a valid superuser name with -S/--superuser

bash-4.2$ 



ALTER USER repmgr WITH SUPERUSER;


bash-4.2$ /usr/edb/as14/bin/psql -d postgres -U enterprisedb

psql (14.11.0)

Type "help" for help.


postgres=# ALTER USER repmgr WITH SUPERUSER;

ALTER ROLE

postgres=# \l

                                           List of databases

   Name    |    Owner     | Encoding |   Collate   |    Ctype    | ICU |       Access privileges       

-----------+--------------+----------+-------------+-------------+-----+-------------------------------

 dev       | test         | UTF8     | C           | C           |     | 

 edb       | enterprisedb | UTF8     | C           | C           |     | 

 postgres  | enterprisedb | UTF8     | C           | C           |     | 

 repmgr    | repmgr       | UTF8     | C           | C           |     | 

 sit       | test         | UTF8     | en_US.UTF-8 | en_US.UTF-8 |     | 

 template0 | enterprisedb | UTF8     | C           | C           |     | =c/enterprisedb              +

           |              |          |             |             |     | enterprisedb=CTc/enterprisedb

 template1 | enterprisedb | UTF8     | C           | C           |     | =c/enterprisedb              +

           |              |          |             |             |     | enterprisedb=CTc/enterprisedb

(7 rows)


postgres=# \du

                                         List of roles

       Role name       |                         Attributes                         | Member of 

-----------------------+------------------------------------------------------------+-----------

 aq_administrator_role | No inheritance, Cannot login                              +| {}

                       | Profile default                                            | 

 barman                | Superuser                                                 +| {}

                       | Profile default                                            | 

 enterprisedb          | Superuser, Create role, Create DB, Replication, Bypass RLS+| {}

                       | Profile default                                            | 

 repmgr                | Superuser                                                 +| {}

                       | Profile default                                            | 

 test                  | Superuser                                                 +| {}

                       | Profile default                                            | 


postgres=# 



/usr/edb/as14/bin/repmgr -f /etc/repmgr/14/repmgr.conf primary register


bash-4.2$ /usr/edb/as14/bin/repmgr -f /etc/repmgr/14/repmgr.conf primary register

INFO: connecting to primary database...

NOTICE: attempting to install extension "repmgr"

NOTICE: "repmgr" extension successfully installed

NOTICE: primary node record (ID: 1) registered

bash-4.2$ 



/usr/edb/as14/bin/repmgr -f /etc/repmgr/14/repmgr.conf  cluster show


bash-4.2$ /usr/edb/as14/bin/repmgr -f /etc/repmgr/14/repmgr.conf  cluster show

 ID | Name        | Role    | Status    | Upstream | Location | Priority | Timeline | Connection string                                           

----+-------------+---------+-----------+----------+----------+----------+----------+--------------------------------------------------------------

 1  | postoffline | primary | * running |          | default  | 100      | 1        | host=postoffline user=repmgr dbname=repmgr connect_timeout=2

bash-4.2$ 


STANDBY - postonline


bash-4.2$ cd /usr/edb/as14/bin

bash-4.2$ ./repmgr

ERROR: following errors were found in the configuration file:

  "node_id": required parameter was not found

  "node_name": required parameter was not found

  "data_directory": required parameter was not found

  "conninfo": required parameter was not found

DETAIL: configuration file is: "/etc/repmgr/14/repmgr.conf"

bash-4.2$ 


[root@postonline ~]# cat /etc/repmgr/14/repmgr.conf | grep "node_id\|node_name\|conninfo\|data_directory\|failover\|promote_command\|follow_command"

node_id=2 # A unique integer greater than zero

node_name='postonline' # An arbitrary (but unique) string; we recommend

conninfo='host=postonline user=repmgr dbname=repmgr connect_timeout=2' # Database connection information as a conninfo string.

# For details on conninfo strings, see:

# "connect_timeout" in the conninfo string to determine

data_directory='/database/edb/as14' # The node's data directory. This is needed by repmgr

# defaults to the user defined in "conninfo".

# is used during failover to check visibility of the

#use_primary_conninfo_password=false # explicitly set "password" in "primary_conninfo"

#passfile='' # path to .pgpass file to include in "primary_conninfo"

failover='automatic' # one of 'automatic', 'manual'.

promote_command='/usr/edb/as14/bin/repmgr standby promote -f /etc/repmgr/14/repmgr.conf --log-to-file' # command repmgrd executes when promoting a new primary; use something like:

follow_command='/usr/edb/as14/bin/repmgr standby follow -f /etc/repmgr/14/repmgr.conf --log-to-file --upstream-node-id=%n' # command repmgrd executes when instructing a standby to follow a new primary;

# executing "follow_command" (defaults to the value set in "standby_reconnect_timeout")

#standby_disconnect_on_failover=false # If "true", in a failover situation wait for all standbys to

#sibling_nodes_disconnect_timeout=30 # If "standby_disconnect_on_failover" is true, the maximum length of time

#primary_visibility_consensus=false # If "true", only continue with failover if no standbys have seen

#failover_validation_command='' # Script to execute for an external mechanism to validate the failover

# value: %n (node_id), %a (node_name). *Must* be the same on all nodes.

#election_rerun_interval=15 # if "failover_validation_command" is set, and the command returns

#service_promote_command = '' # This parameter is intended for systems which provide a

# for "promote_command"; do not use "repmgr standby promote"

[root@postonline ~]# 


[root@postoffline ~]# firewall-cmd --list-services

dhcpv6-client postgresql ssh

[root@postoffline ~]# firewall-cmd --add-port=5444/tcp

success

[root@postoffline ~]# 




/usr/edb/as14/bin/repmgr -h postoffline -U repmgr -d repmgr -f /etc/repmgr/14/repmgr.conf standby clone --dry-run


bash-4.2$ /usr/edb/as14/bin/repmgr -h postoffline -U repmgr -d repmgr -f /etc/repmgr/14/repmgr.conf standby clone --dry-run

NOTICE: destination directory "/database/edb/as14" provided

INFO: connecting to source node

DETAIL: connection string is: host=postoffline user=repmgr dbname=repmgr

DETAIL: current installation size is 102 MB

INFO: "repmgr" extension is installed in database "repmgr"

INFO: replication slot usage not requested;  no replication slot will be set up for this standby

INFO: parameter "max_wal_senders" set to 10

NOTICE: checking for available walsenders on the source node (2 required)

INFO: sufficient walsenders available on the source node

DETAIL: 2 required, 10 available

NOTICE: checking replication connections can be made to the source server (2 required)

INFO: required number of replication connections could be made to the source server

DETAIL: 2 replication connections required

WARNING: data checksums are not enabled and "wal_log_hints" is "off"

DETAIL: pg_rewind requires "wal_log_hints" to be enabled

NOTICE: standby will attach to upstream node 1

HINT: consider using the -c/--fast-checkpoint option

INFO: would execute:

  pg_basebackup -l "repmgr base backup"  -D /database/edb/as14 -h postoffline -p 5444 -U repmgr -X stream 

INFO: all prerequisites for "standby clone" are met

bash-4.2$ 



/usr/edb/as14/bin/repmgr -h postoffline -U repmgr -d repmgr -f /etc/repmgr/14/repmgr.conf standby clone


bash-4.2$ /usr/edb/as14/bin/repmgr -h postoffline -U repmgr -d repmgr -f /etc/repmgr/14/repmgr.conf standby clone

NOTICE: destination directory "/database/edb/as14" provided

INFO: connecting to source node

DETAIL: connection string is: host=postoffline user=repmgr dbname=repmgr

DETAIL: current installation size is 102 MB

INFO: replication slot usage not requested;  no replication slot will be set up for this standby

NOTICE: checking for available walsenders on the source node (2 required)

NOTICE: checking replication connections can be made to the source server (2 required)

WARNING: data checksums are not enabled and "wal_log_hints" is "off"

DETAIL: pg_rewind requires "wal_log_hints" to be enabled

INFO: checking and correcting permissions on existing directory "/database/edb/as14"

NOTICE: starting backup (using pg_basebackup)...

HINT: this may take some time; consider using the -c/--fast-checkpoint option

INFO: executing:

  pg_basebackup -l "repmgr base backup"  -D /database/edb/as14 -h postoffline -p 5444 -U repmgr -X stream 

NOTICE: standby clone (using pg_basebackup) complete

NOTICE: you can now start your PostgreSQL server

HINT: for example: pg_ctl -D /database/edb/as14 start

HINT: after starting the server, you need to register this standby with "repmgr standby register"

bash-4.2$ 


[root@postonline ~]# firewall-cmd --add-port=5444/tcp

success

[root@postonline ~]# 


bash-4.2$ /usr/edb/as14/bin/pg_ctl -D /database/edb/as14 -l logfile start

waiting for server to start.... done

server started

bash-4.2$ /usr/edb/as14/bin/pg_ctl -D /database/edb/as14 -l logfile status

pg_ctl: server is running (PID: 6344)

/usr/edb/as14/bin/edb-postgres "-D" "/database/edb/as14"

bash-4.2$ 



/usr/edb/as14/bin/repmgr -f /etc/repmgr/14/repmgr.conf standby register


bash-4.2$ /usr/edb/as14/bin/repmgr -f /etc/repmgr/14/repmgr.conf standby register

INFO: connecting to local node "postonline" (ID: 2)

INFO: connecting to primary database

WARNING: --upstream-node-id not supplied, assuming upstream node is primary (node ID: 1)

INFO: standby registration complete

NOTICE: standby node "postonline" (ID: 2) successfully registered

bash-4.2$ 






/usr/edb/as14/bin/repmgr -f /etc/repmgr/14/repmgr.conf cluster show


bash-4.2$ /usr/edb/as14/bin/repmgr -f /etc/repmgr/14/repmgr.conf cluster show

 ID | Name        | Role    | Status    | Upstream    | Location | Priority | Timeline | Connection string                                           

----+-------------+---------+-----------+-------------+----------+----------+----------+--------------------------------------------------------------

 1  | postoffline | primary | * running |             | default  | 100      | 1        | host=postoffline user=repmgr dbname=repmgr connect_timeout=2

 2  | postonline  | standby |   running | postoffline | default  | 100      | 1        | host=postonline user=repmgr dbname=repmgr connect_timeout=2 

bash-4.2$ 



/usr/edb/as14/bin/repmgrd -f /etc/repmgr/14/repmgr.conf


bash-4.2$ /usr/edb/as14/bin/repmgrd -f /etc/repmgr/14/repmgr.conf

[2024-03-03 15:59:52] [NOTICE] repmgrd (repmgrd 5.3.2) starting up

[2024-03-03 15:59:52] [INFO] connecting to database "host=postonline user=repmgr dbname=repmgr connect_timeout=2"

bash-4.2$ [2024-03-03 15:59:52] [ERROR] PID file "/tmp/repmgrd.pid" exists and seems to contain a valid PID

[2024-03-03 15:59:52] [HINT] if repmgrd is no longer alive, remove the file and restart repmgrd


bash-4.2$ [2024-03-03 16:00:18] [INFO] node "postonline" (ID: 2) monitoring upstream node "postoffline" (ID: 1) in normal state


bash-4.2$ 


/usr/edb/as14/bin/repmgr -f /etc/repmgr/14/repmgr.conf cluster event


bash-4.2$ /usr/edb/as14/bin/repmgr -f /etc/repmgr/14/repmgr.conf cluster event

 Node ID | Name        | Event            | OK | Timestamp           | Details                                                                            

---------+-------------+------------------+----+---------------------+-------------------------------------------------------------------------------------

 2       | postonline  | repmgrd_start    | t  | 2024-03-03 15:55:17 | monitoring connection to upstream node "postoffline" (ID: 1)                       

 2       | postonline  | standby_register | t  | 2024-03-03 15:54:08 | standby registration succeeded; upstream node ID is 1                              

 2       | postonline  | standby_clone    | t  | 2024-03-03 15:40:23 | cloned from host "postoffline", port 5444; backup method: pg_basebackup; --force: N

 1       | postoffline | primary_register | t  | 2024-03-03 15:03:31 |                                                                                    

 1       | postoffline | cluster_created  | t  | 2024-03-03 15:03:31 |                                                                                    


bash-4.2$ 






Comments

Post a Comment

Popular Posts

AWR Report Analysis

Image
AWR report analysis is important for  Oracle DBA on Daily issues or P1/P2 issues time. Below some of the main things we general look to figure out issue. 1. 2.  3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13.
Read more

Goldengate 19c Installation with issue resolution

Image
  Basic Installation of GoldenGate 19c in OEL6. Tested with below requirements: Step1: Vmware requirements:   For installing OEL6.8 and Oracle DB 12c  installation, please refer URL https://venuoracledba.blogspot.com/2020/08/oracle-12c-2-node-rac-setup-in-vmware.html     Step2: After OEL6.8 installation finished. We will use /opt for goldengate installation.   Step3: unzip GG software in folder. Here unzipped in gg_software folder.     Folder fbo_ggs_Linux_x64_shiphome will create. Step4:  Enable GUI by issuing x host + command in root user. and keep open this root terminal.   Step5:  Enable GUI by issuing x host + command in oracle user.   Move to software path   execute ./runInstaller and select database version. Selected 12c version for my environment. and click Next     provide GG home, oracle home and port number and click Next.     After verifying paths and information, Click Install   ...
Read more

Oracle 11g Physical Standy Setup

  Step1: take Binaries tar backup from Primary DB server tar -cvf /path/11.2.0.4.tar 11.2.0.4 Step2: untar Binaries tar back on Standby DB server tar -xvf /path/11.2.0.4.tar -C /path ###################### Binaries Cloning ################### Step3: run clone command on Standby DB server export ORACLE_HOME=<PATH> cd $ORACLE_HOME/clone/bin perl $ORACLE_HOME/clone/bin/clone.pl ORACLE_BASE='<PATH>' ORACLE_HOME='<PATH>' ORACLE_HOME_NAME='<ANY_NAME>' ###################### POST Binaries Cloning ################### Step4: run root scripts $ORACLE_BASE/oraInventory/orainstRoot.sh $ORACLE_HOME/root.sh ###################### Pre-requisites ################### Standby: Step5: update hostnames in listener and tnsnames files Step6: start the listener in standby Server Primary: Step7: check force logging enabled -- to make sys activities will logged in redo logs SQL> select force_logging from v$database; - NO ( default ) to enable force logging - S...
Read more

Oracle 12c 2-node RAC setup in VMware Player 15 -- Part01

Image
Tried to install Oracle 12c 2-node RAC for testing purpose but due to low Hardware configuration, ended up with Single Node RAC. I got lot of issues during Installation and tried to resolve them with my best knowledge. Please find below installation steps and troubleshooting. Main issues started from Step90. you can go through quickly. Requirements Most of the times, bridge option in VMWARE will not connect with host machine. I tried below option to use internet connection from host machine. We need to cross verify vmnet8 is NAT or not. Installation Steps Step1 launch VMware and click on New Virtual Machine Step2   select OEL iso Image Step3 Provide New Virtual Machine Name Step4 Provide HDD size and select single virtual disk. Step5  Select host setting for monitor and Network as NAT Step6 New Virtual Machine is ready for launch. Step7 OEL Installation starts automatically. Press Enter Step8 Skip Disk Checking Step9 Click Next Step10   Select langu...
Read more

Oracle to Postgres

Image
  Round 1: Created metadata for tables, sequences, packages Round 2: Created indexes Round 3: freeze column name to freezes to_date function updated GEOMETRY datatype , installed POSTGIS package to support this datatype Round 4: created triggers created Functions Migration: bash-4.2$ pwd /usr/edb/migrationtoolkit/etc bash-4.2$ cat toolkit.properties SRC_DB_URL=jdbc:oracle:thin:@localhost:1521:orcl SRC_DB_USER=hr SRC_DB_PASSWORD=hr TARGET_DB_URL=jdbc:edb://postoffline:5444/dev TARGET_DB_USER=enterprisedb TARGET_DB_PASSWORD=password bash-4.2$  -bash-4.2$ pwd /usr/edb/migrationtoolkit/bin -bash-4.2$ ls -lrt total 724 -rwxr-xr-x. 1 root root   2439 Dec 11 13:29 runJavaApplication.sh -rwxr-xr-x. 1 root root    544 Dec 11 13:33 runMTK.sh -rwxr-xr-x. 1 root root 729258 Dec 11 13:33 edb-migrationtoolkit.jar -bash-4.2$  ./runMTK.sh HR OUTPUT: Running EnterpriseDB Migration Toolkit (Build 55.7.0) ... Source database connectivity info... conn =jdbc:oracle:thin:@o...
Read more

Execution_Explain Plan

Whenever we get request for application slowness or sql query then we need to identify sql_id and to analyze sql_id, we need to check SQL execution/explain plan. 1. EXECUTION_PLAN: select id,plan_hash_value,operation, options,object_name,cardinality,cost,bytes,cpu_cost,io_cost,time,partition_start,partition_stop, object_node,other_tag,qblock_name,other_xml from dba_hist_sql_plan where sql_id='<SQL_ID>'; or select * from table(dbms_xplan.display_awr('<SQL_ID>')); EXPLAIN_PLAN: explain plan for <SQL_QUERY>; select * from table(dbms_xplan.display);
Read more

Active Session History Analysis

Image
ASH  analysis is important for  Oracle DBA on Daily issues or P1/P2 issues time. Below some of the main events we general look to figure out issue. RAC / Cloud RDS: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. Redo Generation: 14. 15. 16. 17. 18. 19.
Read more

General Queries

                                                                              Tablespace growth Size We can use view to check tablespace size greater than 80% RAC / NON-RAC / Cloud RDS: SELECT tbm.TABLESPACE_NAME,   round(tbm.USED_SPACE * tb.BLOCK_SIZE /(1024*1024*1024),2) as USED_SPACE_GB,   round(tbm.TABLESPACE_SIZE * tb.BLOCK_SIZE /(1024*1024*1024),2) as TBS_SIZE_GB,   round((tbm.TABLESPACE_SIZE - tbm.USED_SPACE) * tb.BLOCK_SIZE /(1024*1024*1024),2) as TBS_FREE_SIZE_GB,   round(tbm.USED_PERCENT) as PERCENT_USEDFROM dba_tablespace_usage_metrics tbm      join dba_tablespaces tb on tb.TABLESPACE_NAME = tbm.TABLESPACE_NAME w...
Read more

Fragmentation & Re-organisation

Total  Savings: set verify off column file_name format a50 word_wrapped column smallest format 999,990 heading "Smallest|Size|Poss." column currsize format 999,990 heading "Current|Size" column savings format 999,990 heading "Poss.|Savings" break on report compute sum of savings on report column value new_val blksize select value from v$parameter where name = 'db_block_size' / select file_name, ceil( (nvl(hwm,1)*&amp;&amp;blksize)/1024/1024 ) smallest, ceil( blocks*&amp;&amp;blksize/1024/1024) currsize, ceil( blocks*&amp;&amp;blksize/1024/1024) - ceil( (nvl(hwm,1)*&amp;&amp;blksize)/1024/1024 ) savings from dba_data_files a, ( select file_id, max(block_id+blocks-1) hwm from dba_extents group by file_id ) b where a.file_id = b.file_id(+) order by savings desc / HWM query for all datafiles: col data_file_name for a50 col tablespace_name for a20 set lines 300 select tablespace_name, file_id, file_name DATA_FILE_NAME, Al...
Read more

OEM patches & vulnerabilities

Image
  Tools: Agent: agentpatcher OMS: omspatcher coherence/weblogic: optach 1. Agent JDK update. please refer the below oracle reference page Supported Java SE Downloads on MOS (oracle.com) 2. Removing log4j-core-2.8.2.jar validate jar file exist cd $OEM_BASE/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/tmp/_WL_user/emdb/1danf1/database/jet/emsaasui/emcdbms-ui/ear/APP-INF/lib $OEM_BASE/agent_13.5.0.0.0/oracle_common/jdk/bin/jar tvf log4j-core-2.8.2.jar | grep JndiLookup.class output 2974 Sun Apr 02 15:24:22 AEST 2017 org/apache/logging/log4j/core/lookup/JndiLookup.class stop OMS  $OEM_BASE/middleware/bin/emctl status oms -details  $OEM_BASE/middleware/bin/emctl stop oms -all remove log4j zip -q -d log4j-core-2.8.2.jar org/apache/logging/log4j/core/lookup/JndiLookup.class validate jar file exist $OEM_BASE/agent_13.5.0.0.0/oracle_common/jdk/bin/jar tvf log4j-core-2.8.2.jar | grep JndiLookup.class start OMS  $OEM_BASE/middleware/bin/emctl status oms -details ...
Read more