Behavior Changes of RHEL 7.x Operating System

RHEL 7.x had taken lots of changes by default …

1.) Default file system changes: XFS
In RHEL7 /CentOS 7 and Oracle Linux have adopted XFS as their default file system.
Apart of these there are other numerous changes that you could find from faq forum like http://simplylinuxfaq.blogspot.in/p/major-difference-between-rhel-7-and-6.html

Some of them i found to be mandatory change before use it for Database Server in Production.
2.) Default HugePages is On On
Oracle recommends that you disable Transparent HugePages before you start installation.

3.) Default Setting RemoveIPC=yes
Setting RemoveIPC=yes on Redhat 7.2 Crashes ASM and Database Instances as Well as Any Application That Uses a Shared Memory Segment (SHM) or Semaphores (SEM)

Recommended to follow below steps
1. Set RemoveIPC=no in /etc/systemd/logind.conf
2. Reboot the server or restart systemd-logind as follows:
# systemctl daemon-reload
# systemctl restart systemd-logind

RHEL7: rc.local service not starting

Found this on some Red Hat blog:

“Systemd is a system and service manager for Linux operating systems. It is designed to be backwards compatible with SysV init scripts, and provides a number of features such as parallel startup of system services at boot time, on-demand activation of daemons, support for system state snapshots, or dependency-based service control logic. In Red Hat Enterprise Linux 7, systemd replaces Upstart as the default init system.”

chmod +x /etc/rc.d/rc.local
systemctl enable rc-local
systemctl status rc-local

https://grepora.com/2016/07/15/rhel7-rc-local-service-not-starting/

Remove Extra member from standby redo group

Tips , Reset below parameters before create standby redo group
db_create_online_log_dest_1=+DATA1 and db_create_online_log_dest_2=+DATA2

If you have set these parameters and you create standby redo log then it will be multiplexed in +DATA1 and +DATA2, Not recommended in Prod:)

@Primary
SQL> show parameter standby_file_management=MANUAL;
SQL> alter system set standby_file_management=MANUAL;

System altered.

SQL> ALTER DATABASE DROP STANDBY LOGFILE MEMBER ‘+ORADATA/BLRDB/ONLINELOG/group_5.319.922465363’;

Database altered.

SQL> ALTER DATABASE DROP STANDBY LOGFILE MEMBER ‘+ORADATA/BLRDB/ONLINELOG/group_6.310.922465367’;

Database altered.

SQL> ALTER DATABASE DROP STANDBY LOGFILE MEMBER ‘+ORADATA/BLRDB/ONLINELOG/group_7.311.922465371’;

Database altered.

SQL> ALTER DATABASE DROP STANDBY LOGFILE MEMBER ‘+ORADATA/BLRDB/ONLINELOG/group_8.299.922465375’;

Database altered.

SQL> ALTER DATABASE DROP STANDBY LOGFILE MEMBER ‘+ORADATA/BLRDB/ONLINELOG/group_9.872.922465379’;

Database altered.

SQL> ALTER DATABASE DROP STANDBY LOGFILE MEMBER ‘+ORADATA/BLRDB/ONLINELOG/group_10.874.922465383’;

Database altered.

SQL> select member from v$logfile;

MEMBER
——————————————————————————–
+ORADATA/BLRDB/ONLINELOG/group_2.305.922465353
+ORADATA/BLRDB/ONLINELOG/group_2.622.922465353
+ORADATA/BLRDB/ONLINELOG/group_1.307.922465349
+ORADATA/BLRDB/ONLINELOG/group_1.306.922465351
+ORADATA/BLRDB/ONLINELOG/group_3.620.922465355
+ORADATA/BLRDB/ONLINELOG/group_3.323.922465357
+ORADATA/BLRDB/ONLINELOG/group_4.322.922465359
+ORADATA/BLRDB/ONLINELOG/group_4.320.922465361
+ORADATA/BLRDB/ONLINELOG/group_5.313.922465365
+ORADATA/BLRDB/ONLINELOG/group_6.301.922465369
+ORADATA/BLRDB/ONLINELOG/group_7.302.922465373

MEMBER
——————————————————————————–
+ORADATA/BLRDB/ONLINELOG/group_8.300.922465377
+ORADATA/BLRDB/ONLINELOG/group_9.873.922465381
+ORADATA/BLRDB/ONLINELOG/group_10.875.922465385
+ORADATA/BLRDB/ONLINELOG/group_11.1351.927649007

15 rows selected.

SQL> show parameter standby_file_management=AUTO scope=both;
SQL> ALTER SYSTEM SET standby_file_management=AUTO scope=both;

System altered.

SQL> select member from v$logfile;

MEMBER
——————————————————————————–
+ORADATA/BLRDB/ONLINELOG/group_2.305.922465353
+ORADATA/BLRDB/ONLINELOG/group_2.622.922465353
+ORADATA/BLRDB/ONLINELOG/group_1.307.922465349
+ORADATA/BLRDB/ONLINELOG/group_1.306.922465351
+ORADATA/BLRDB/ONLINELOG/group_3.620.922465355
+ORADATA/BLRDB/ONLINELOG/group_3.323.922465357
+ORADATA/BLRDB/ONLINELOG/group_4.322.922465359
+ORADATA/BLRDB/ONLINELOG/group_4.320.922465361
+ORADATA/BLRDB/ONLINELOG/group_5.313.922465365
+ORADATA/BLRDB/ONLINELOG/group_6.301.922465369
+ORADATA/BLRDB/ONLINELOG/group_7.302.922465373

MEMBER
——————————————————————————–
+ORADATA/BLRDB/ONLINELOG/group_8.300.922465377
+ORADATA/BLRDB/ONLINELOG/group_9.873.922465381
+ORADATA/BLRDB/ONLINELOG/group_10.875.922465385
+ORADATA/BLRDB/ONLINELOG/group_11.1351.927649007

15 rows selected.

SQL>
SQL> alter system switch logfile;

System altered.

SQL> exit
Disconnected from Oracle Database 12c Enterprise Edition Release 12.1

@DR

alter system set standby_file_management=MANUAL;
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

SQL> ALTER DATABASE DROP STANDBY LOGFILE MEMBER ‘+ORADATA/BLRDB/ONLINELOG/group_5.319.922465363’;

Database altered.

SQL> ALTER DATABASE DROP STANDBY LOGFILE MEMBER ‘+ORADATA/BLRDB/ONLINELOG/group_6.310.922465367’;

Database altered.

SQL> ALTER DATABASE DROP STANDBY LOGFILE MEMBER ‘+ORADATA/BLRDB/ONLINELOG/group_7.311.922465371’;

Database altered.

SQL> ALTER DATABASE DROP STANDBY LOGFILE MEMBER ‘+ORADATA/BLRDB/ONLINELOG/group_8.299.922465375’;

Database altered.

SQL> ALTER DATABASE DROP STANDBY LOGFILE MEMBER ‘+ORADATA/BLRDB/ONLINELOG/group_9.872.922465379’;

Database altered.

SQL> ALTER DATABASE DROP STANDBY LOGFILE MEMBER ‘+ORADATA/BLRDB/ONLINELOG/group_10.874.922465383′;

Database altered.

Standby redo logs without multiplexting:-

SQL> SELECT MEMBER FROM V$LOGFILE WHERE TYPE=’STANDBY’;

MEMBER
——————————————————————————–
+ORADATA/BLRDB/ONLINELOG/group_5.313.922465365
+ORADATA/BLRDB/ONLINELOG/group_6.301.922465369
+ORADATA/BLRDB/ONLINELOG/group_7.302.922465373
+ORADATA/BLRDB/ONLINELOG/group_8.300.922465377
+ORADATA/BLRDB/ONLINELOG/group_9.873.922465381
+ORADATA/BLRDB/ONLINELOG/group_10.875.922465385

SQL> SELECT GROUP#,THREAD#,STATUS FROM V$STANDBY_LOG;

GROUP# THREAD# STATUS
———- ———- ———-
5 1 UNASSIGNED
6 1 UNASSIGNED
7 1 UNASSIGNED
8 2 UNASSIGNED
9 2 UNASSIGNED
10 2 UNASSIGNED

Set PASSWORD UNLIMITED for PDB Application Schema

SQL> SELECT dba_users.USERNAME,
dba_users.ACCOUNT_STATUS,
dba_users.EXPIRY_DATE
FROM dba_users
WHERE ACCOUNT_STATUS=’OPEN’;
2 3 4 5
USERNAME ACCOUNT_STATUS EXPIRY_DA
——————————————————————————————————————————– ——————————– ———
NETVERTEXBLR OPE 17-APR-17
PDBADMIN OPE 17-MAR-17
ELITELDAPBLR OPE 21-MAR-17
ELITEPMRO OPE 13-APR-17
ELITEPROXYBLR OPE 17-APR-17
SYSTEM OPE 17-MAR-17
SYS OPE 17-MAR-17

7 rows selected.

SQL> ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;

Profile altered.

SQL> SELECT dba_users.USERNAME,
dba_users.ACCOUNT_STATUS,
dba_users.EXPIRY_DATE
FROM dba_users
WHERE ACCOUNT_STATUS=’OPEN’; 2 3 4 5

USERNAME ACCOUNT_STATUS EXPIRY_DA
——————————————————————————————————————————– ——————————– ———
NETVERTEXBLR OPEN
PDBADMIN OPEN
ELITELDAPBLR OPEN
ELITEPMRO OPEN
ELITEPROXYBLR OPEN
SYSTEM OPEN
SYS OPEN

7 rows selected.

SQL>

If you want to remove password expiry date for your schema then you have to use “ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;”

How to protect your cronjob in linux ?

https://en.wikipedia.org/wiki/Chattr

A very useful Linux tip on how to make files and directories undeletable even by the root user. You can apply this tip on all important configuration files so that no one accidentally or intentionally deletes it. To achieve this the chattr (Change Attribute) command is used it Linux. The chattr command “immunizes” the file not only from deletion but also modification. The chattr command does care about chmod values, even if a file has 777 permissions immunizing the file will prevent it from being deleted or modified.

chattr +i /path/to/filename

How to view file attributes ?
lsattr /path/to/directory

How to remove the immutable flag ?
chattr -i /path/to/file

http://websistent.com/make-undeletable-files-and-directories-linux/

ORA-01110

My Database Setup is :

Primary : 2 Node RAC 12.1.0.2 with Multitenant Architecture and ASM file structure

Standby : 2 Node RAC 12.1.0.2 with Multitenant Architecture and ASM file structure

During Data Guard Configuration, the standby file management was kept to manual (by mistake). After that we have created one new tablespace in primary database and which has shutdown the MRP process in Data Guard with below errors in alert log of standby instance.

ORA-01111: name for data file 87 is unknown – rename to correct file

ORA-01110: data file 87: ‘/u01/app/oracle/product/12.1.0/db_1/dbs/UNNAMED00087’

ORA-01157: cannot identify/lock data file 87 – see DBWR trace file

ORA-01111: name for data file 87 is unknown – rename to correct file

ORA-01110: data file 87: ‘/u01/app/oracle/product/12.1.0/db_1/dbs/UNNAMED00087’

MRP0: Background Media Recovery process shutdown (blrdr2)

SQL> show parameter standby

NAME TYPE VALUE
———————————— ———– ——————————
standby_archive_dest string ?/dbs/arch
standby_file_management string MANUAL
http://www.oracle-ckpt.com/unnamed-file-in-standby-after-adding-new-file-to-primary-ora-01111-ora-01110-ora-01157/
http://www.oracle-ckpt.com/unnamed-file-in-standbypdb-after-adding-new-file-to-primarypdb/

https://community.oracle.com/thread/3980984