Error: [INS-44002] The Oracle home location contains directories or files on following remote nodes

 

When trying to install grid 19.3 software on RAC01 getting below error..

I had below issue..I checked with "ls -la: there hidden files.   .opatchauto_storage  .patch_storage

I removed them with their own name "rm -rf ..opatchauto_storage  .patch_storage"

Solution:

======

Goto to second rac home /u02/softw 

$ cd /u02/softw

$ ls -la

.opatchauto_storage

.patch_storage

$ rm -rf .opatchauto_storage

$ rm -rf .patch_storage

Oracle Linux 7:Found /var/log/messages is Empty And Not Being Updated (Doc ID 2580481.1)

 

Found /var/log/messages is empty and no logs being written eventhough Rsyslog service is running.

Misconfiguration in /etc/rsyslog.d/ignore-systemd-session-slice.conf.

Solution

Edit /etc/rsyslog.d/ignore-systemd-session-slice.conf.

if $programname == "systemd-logind" and ($msg contains "New session" or $msg contains "Removed session" or $msg contains "Removed slice" or $msg contains "Stopping") then stop

if $programname == "systemd" and ($msg contains "Started Session" or $msg contains "Starting Session" or $msg contains "Created slice" or $msg contains "Starting user-0.slice" or $msg contains "Stopping user-0.slice" or $msg contains "Removed slice user-0.slic") then stop

Need to be changed as below .

 

if $programname == "systemd-logind" and ($msg contains "New session" or $msg contains "Removed session" or $msg contains "Removed slice" or $msg contains "Stopping") then stop

if $programname == "systemd" and ($msg contains "Started Session" or $msg contains "Starting Session" or $msg contains "Created slice" or $msg contains "Starting user-0.slice" or $msg contains "Stopping user-0.slice" or $msg contains "Removed slice user-0.slic" or $msg contains "Starting User Slice" or $msg contains "Removed slice User Slice" or $msg contains "Stopping User Slice") then stop

 After this restart the service

#systemctl restart rsyslog.service

After this check /var/log/messages .

Failed to load SELinux Policy Freezing

Scenario 1

I facing  below error while I copy data from host computer to Virtual Machine the host computer drive full. The virtual machine stuck...Once I restart the Virtual machine...it's given this error.

"Failed to load SELinux policy, freezing."

Solution:

=======

• Press “e” at the boot screen to edit the startup parameters.

• Modify the line that starts with “linux16” and append “selinux=0” to the end

• Press “ctrl+x” to boot.

This allows us to boot with SELinux disabled. We can now re-edit the SELinux configuration file and fix our typo.

Scenario 2

Failed to load SELinux policy freezing. Well, that’s a new one – at least for me. So what went wrong?

While performing some configuration changes on one of my Linux hosts, I needed to temporarily disable SELinux to test. Easy enough, right? Edit /etc/selinux/config and change SELINUX to disabled.

Changes made, host rebooted. I go off to perform another task, and when I come back to check on it I cannot log in. I load up the console and it’s stuck at loading CentOS. When I pull up the console logs, I see this:

Failed to load SELinux policy freezing. Well, that’s a new one – at least for me. So what went wrong?

While performing some configuration changes on one of my Linux hosts, I needed to temporarily disable SELinux to test. Easy enough, right? Edit /etc/selinux/config and change SELINUX to disabled.

Changes made, host rebooted. I go off to perform another task, and when I come back to check on it I cannot log in. I load up the console and it’s stuck at loading CentOS. When I pull up the console logs, I see this:

Upgrade Oracle 11g to 19c using Expdp/Impdp

 

Upgrade Oracle 11.2.4 to 19.3.0 Using Expdp / Impdp

Example of Using Oracle Data Pump The steps for using Oracle Data Pump to upgrade or migrate a database have not changed from previous releases. If you would like to migrate with Oracle Data Pump using conventional dump files, the steps would be as follows: 

SQL> create directory bkup_dir as '/u02/oradb/bkup';

1. Export the source database to a dump file:

2.$ expdp srcadmin/password  DIRECTORY=bkup_dir DUMPFILE=expfulldb.dmp LOGFILE=expfulldb.log FULL=Y METRICS=Y PARALLEL=4 EXCLUDE=STATISTICS 

3. Make the dump file available on the destination system, either by copying it to the destination           

   system or placing it on a network-mounted disk. 

4. Create a CDB on the destination system, including a PDB into which you will import the source 

    database. 

5. In the destination PDB, create a directory object for the dump file to be imported.

6. SQL> create directory bkup_dir as '/u02/oradb/bkup'';

7. SQL> create user test identified by test123

 8. Import the Data Pump dump file into the destination PDB: 

$ impdp test/test123@pdb DIRECTORY=bkup_dir DUMPFILE=expfulldb.dmp LOGFILE=expfulldb.log PARALLEL=4 METRICS=Y LOGTIME=ALL 

In this example, we take advantage of Oracle Data Pump features such as the PARALLEL parameter to improve performance. In other cases, you might use network mode to eliminate the need for a dump file. Oracle Data Pump is fully documented in Oracle Database Utilities Guide.