Tuesday, July 24, 2018

Install Oracle Linux 6.9 OS Using Local or Remote Media

This procedure describes how to install the Oracle Linux 6.9 OS from local or remote media. The procedure assumes that you are booting the Oracle Linux installation media from one of the following sources:

Oracle Linux 6.9 DVD set
Oracle Linux 6.9 ISO DVD image (network repository)

If you are booting the installation media from a PXE environment, see Installing an Operating System Using PXE Network Boot for instructions.

Access the host console.
For instructions, see Selecting the Console Display.
Ensure that the installation media is available to boot.
For instructions, see Selecting the Boot Media Option.
Reset or power on the server.
For details, see Resetting or Powering on the Server.

Note - The next event occurs very quickly; therefore, be ready to press F8 to display the BBS Popup. Watch carefully for messages as they appear on the screen for a brief time. You might want to enlarge the size of your screen to eliminate scroll bars.
On the BIOS screen, press F8 to specify a temporary boot device for the Linux OS installation.
On the Please Select Boot Device menu, select an option according to the Linux OS media installation method you elected to use, and press Enter.
For example, to use the Oracle ILOM Remote System Console Plus application delivery, select [UEFI]USB:VIRTUAL:Remote Iso CDROM2.04.

On the Booting Oracle Linux Server 6.9 boot screen, press Enter or allow the screen to time out.

In the Disc Found dialog box, if this is the first time that you are doing an install from this media, consider selecting OK to test the media; otherwise, select Skip and press Enter.

On the Oracle Linux 6 splash screen, scroll to the bottom, and click Next.
Follow the on-screen prompts to complete the Oracle Linux installation up to the point where you create partitions.
For instructions on completing the Oracle Linux 6.9 installation up to the point where you create partitions, refer to the Oracle Linux 6 installation documentation at https://docs.oracle.com/cd/E37670_01/.

To create partitions, for each mount point, use the following file system type and size.

Mount Point

File System Type

Size (MB)

/boot/efi

EFI System Partition

200

/

ext4

20000

None

swap

16384

Format the disk. To recover and reformat the disk without aborting the install, click the keyboard Back button on the install screen several times to return to the initial Oracle Linuxsplash screen and perform these steps:

To start the recovery shell, type Ctrl+Alt+F2.

To reformat the disk in GPT format or MBR format for this installation, enter the following shell commands:

anaconda root@localhost /]# parted /dev/sdb
GNU Parted 2.1
Using /dev/sda
Welcome to GNU Parted! Type ???help' to view a list of commands.
(parted) p
Model: HITACHI H101860SFSUN600G (scsi)
Disk /dev/sda: 600GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos (or gpt for Legacy BIOS Boot Mode)
Number Start End Size Type File system Flags
1 1049kB 21.5GB 21.5GB primary ext2
(parted) mklabel
New disk label type? gpt (or msdos for Legacy BIOS Boot Mode)
Warning: The existing disk label on /dev/sda will be destroyed and all data will be
lost.
Do you want to continue?
Yes/No? yes
(parted) p
Model: HITACHI H101860SFSUN600G (scsi)
Disk /dev/sda: 600GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
(parted) g
Information: You may need to update /etc/fstab.
anaconda root@localhost /]#

Press Ctrl+Alt+F6 to return to the graphical installation screen and continue the installation from the point of creating a partition (go to Step 10).

Note - In most cases, the values that you entered for this installation were saved, so you do not have to reenter them.

On the Install boot loader screen, select Install boot loader on /dev/sdb1, and click Next.
On the Select Server screen, for the purposes of this sample installation, accept the Basic Server default option and click Next.
After the installation completes, reboot the installation.
Press F2 to access the BIOS Setup Utility so that you can set the server to boot from the operating system you just installed.
Verify that the boot entry name you created (in this case, [Oracle Linux]) is listed as the first option in the UEFI Boot Option Priority field.
Press F10 to exit the BIOS Setup Utility and reboot the installation.
Press any key to display the GNU GRUB menu.
Select Oracle Linux Server Red Hat Compatible Kernel (2.6.32-696.el6.x86_64) and press Enter.
Log in to Linux and perform these steps:
1. Configure the network connection.
2. Verify that the Linux Internet connection is active.
Confirm that the UEK entry appears in: /etc/yum.repos.d/public-yum-ol6.repo
Update to Oracle Unbreakable Kernel Release 4 by running yum update kernel-uek or yum update.
When the update is complete, reboot the server with the reboot command to start the server with the new Oracle Unbreakable Enterprise Kernel.

Wednesday, July 11, 2018

Make Oracle password never expire

Solution for making a password never expire:

SQL> connect sys/secret_password as sysdba;

SQL> alter user sysman account unlock ;

-- SQL> alter user DBUSER identified by newpa$$word;

Next, change the profile limit to unlimited.

SQL> alter profile DEFAULT limit PASSWORD_REUSE_TIME unlimited;

SQL> alter profile DEFAULT limit PASSWORD_LIFE_TIME  unlimited;

Check the password expiry date

SQL> select username, account_status, EXPIRY_DATE from dba_users where username='PRAMUDITHA';

USERNAME ACCOUNT_STATUS EXPIRY_DATE
------------------------------ ---------------------------- -------
BACMONIT OPEN UNLIMITED

Tuesday, July 10, 2018

E-Business Suite Applications Manager Rapidclone Script Adcfgclone Fails with Error 'RC-50014: Fatal: Execution of AutoConfig was failed Raised by oracle.apps.ad.clone.ApplyDBTechStack' And AC-00423 With File adcrdb.sh Missing (Doc ID 549872.1)

APPLIES TO:

Oracle Applications Manager - Version 11.5.10.2 to 12.0.6 [Release 11.5.10 to 12]
Information in this document applies to any platform.

SYMPTOMS

While running the command 'adcfgclone.pl dbTier' on the target E-Business Suite instance, the following error may occur:

AC-00423: Template file: <DB ORACLE_HOME>/appsutil/template/adcrdb.sh missing from file system.
Raised by oracle.apps.ad.autoconfig.InstantiateFile

[INSTANTIATE PHASE]
AutoConfig could not successfully instantiate the following files:
Directory: <DB ORACLE_HOME>/appsutil/install/XXX_YYYY
adcrdb.sh INSTE8

AutoConfig is exiting with status 1
RC-50014: Fatal: Execution of AutoConfig was failed
Raised by oracle.apps.ad.clone.ApplyDBTechStack

CAUSE

The template adcrdb.sh is missing from the target "<DB $ORACLE_HOME>/appsutil/template"

SOLUTION

To implement the solution test the following steps in a development instance and then migrate accordingly:

1. copy the missing 'adcrdb.sh' template from the Source to the Target Instance:

Source Location :

<DB $ORACLE_HOME>/appsutil/template

Target Location :

<DB $ORACLE_HOME>/appsutil/template

2. Change ownership and permission of adcrdb.sh file to match with the other templates, which resides in the template directory.

3. Rerun the command 'adcfgclone dbTier' on the target instance and confirm the RC-50014 error no longer occurs.

Tuesday, July 3, 2018

Installing the Unbreakable Enterprise Kernel

If the installed system is configured to use the Red Hat Compatible Kernel and the Unbreakable Enterprise Kernel (UEK) is not installed, you can use yum to install the kernel-uek package:

# yum install kernel-uek

Installing kernel-uek also installs the kernel-uek-firmware package on which it depends, and configures the UEK as the default kernel in /etc/grub.conf. Reboot the system to use this kernel.

Tuesday, June 26, 2018

Oracle Linux & Red Hat Linux

Get the opened ports with service and port number

# netstat -tulpn
# iptables -L

Enable ports from the fire wall

[root@evis ~]# iptables -I INPUT -p tcp -m tcp --dport 5901 -j ACCEPT

[root@evis ~]# service iptables save

Monday, June 4, 2018

Basics of the crontab ∞

Crontab file controls how and what to run by cron. The crontab line has a format as follows:

.---------------- minute (0-59)
|  .------------- hour (0-23)
|  |  .---------- day of month (1-31)
|  |  |  .------- month (1-12) OR jan,feb,mar,apr ...
|  |  |  |  .---- day of week (0-6) (Sunday=0 or 7) OR sun,mon,tue ...
|  |  |  |  |
*  *  *  *  *  command to be executed


To add a cron job for your current user, run
$ crontab -e

use crontab extensions ∞

crontab provides some extensions to support this: ranges can include “steps” like /2. 1-9/2 is the same as 1,3,5,7,9. This can be the easiest method if the job is intended to be run every two N in a range such as N is “day” and the range is “days in a month”. Check the crontab man page for more details about ranges and steps of crontab.

An example.

To run the command every two months at 1:00 on the first day of the month, the crontab is
0 1 1 */2 * command to be executed

Friday, June 1, 2018

Generating the AWR Report

This chapter focuses on the skills required for reading and interpreting an Automated Workload Repository (AWR) report (awrrpt.sql), which is very similar to the STATSPACK elapsed-time report. The AWR elapsed-time report (awrrpt.sql)contains valuable information regarding the health of the Oracle instance, but considerable skill is required to fully understand and interpret each section.

The easy way to generate an AWR report from from the SQL*Plus command line:

SQL>@$ORACLE_HOME/rdbms/admin/awrrpt.sql

Generating the AWR Report

The procedure for creating a standard report provided by the STATSPACK utility in previous Oracle releases has already been introduced. The only way to get a final STATSPACK report is to manually run the spreport.sql script in an ad-hoc SQL environment like SQL*Plus. The procedure of report generation in Oracle10g is quite different with AWR. The final AWR report can be built by using the PL/SQL API provided in the dbms_workload_repository package.

Two procedures that generate AWR reports from awrrpt.sql are awr_report_textand awr_report_html . These procedures generate the AWR report for the specified snapshot range in TEXT or HTML formats, respectively. The following script shows one way of retrieving the AWR text report for the particular snapshot range:

SELECT

output

FROM

TABLE

(dbms_workload_repository.awr_report_text

(37933856,1,2900,2911 )

);

You can create snap using the below
EXEC DBMS_WORKLOAD_REPOSITORY.create_snapshot;

Below query help to find snaps information
select snap_id,BEGIN_INTERVAL_TIME,END_INTERVAL_TIME from dba_hist_snapshot where BEGIN_INTERVAL_TIME > systimestamp -1 order by BEGIN_INTERVAL_TIME desc;

Oracle Database and Linux Support Articles