How To Setup ASM & ASMLIB On Native Linux Multipath Mapper disks?

Applies to:
Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 11.1.0.7
Linux Itanium
Linux x86-64
Goal
The present document provides an example about how to setup ASM & ASMLIB disks using
Mapper Multipath disks.
Solution

1) Install the ASMLIB API (on each node for RAC environments) and configure it following the steps described in the
next documents:
http://www.oracle.com/technology/tech/linux/asmlib/index.html
http://www.oracle.com/technology/tech/linux/asmlib/install.html

2) Partition the mapper devices located at /dev/dm-* thru the fdisk command, Oracle recommends creating one partition
per disks as follow:
# fdisk /dev/dm-
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-1017, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-1017, default 1017):
Using default value 1017
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Note: Keep in mind for ASMLIB disks you will need to use the /dev/dm-* disks instead of the /dev/mapper/mpath* devices since they are present in the partition table ==)> /proc/partitions and ASMLIB will look at that
file during the disk discovering phase. If you do not use the disks located at /dev/dm-* then ASM will not be
able to discover them.

3) Check the partition was created (you should see both the dm- and the dm-):
# ls -l /dev/dm-*
brw-rw---- 1 root disk 8, 0 Jun 11 15:11 dm-
brw-rw---- 1 root disk 8, 1 Jun 11 19:12 dm-

4) Update the kernel partition table with the new partition as follow:
# /sbin/partprobe /dev/dm-

5) Check the new partition is present in the /proc/partitions file.
# cat /proc/partitions

6) Create the ASMLIB disks on the new mapper partitions as follow:
# /etc/init.d/oracleasm createdisk DISK1 /dev/dm-

7) If this is a RAC configuration, then from each node execute:
# /etc/init.d/oracleasm scandisks
# /etc/init.d/oracleasm listdisks

8) After you complete the creation of each ASMLIB disk you will need to configure ASMLIB to use multipath disks as
described in the next document (from each node on RAC environments):
http://www.oracle.com/technology/tech/linux/asmlib/multipath.html
For the ORACLEASM_SCANORDER parameter you need to set it using the dm-XX devices as

follow:
ORACLEASM_SCANORDER="dm"

NOTE: When scanning, only the device names known by the kernel are scanned. With device-mapper, the
kernel sees the devices as /dev/dm-XX. The /dev/mapper/XXX names are created by udev for human readability.
Any configuration of ORACLEASM_SCANORDER or ORACLEASM_SCANEXCLUDE must use the dm prefix.

9) Create the diskgroup(s) on the new ASMLIB disks
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doc...

Example:
SQL> create diskgroup DATA external redundancy disk 'ORCL:DISK1';
Note: Oracle really and strongly recommends using ASMLIB instead of udev since it effectively handles
multipath disks per the advantages described in the next document:

Note: 394959.1 Device Persistence and Oracle Linux ASMLib

Note: On release RH 5 the /dev/dm-N devices are not persistent, starting, these devices are no longer created
by udev. So release RedHat 5 you can create the ASMLIB disks on the /dev/mpath/ or /dev/mapper
/
Example:
# /etc/init.d/oracleasm createdisk VOL1 /dev/mpath/sata01p1
Or
# /etc/init.d/oracleasm createdisk VOL1 /dev/mapper/mpath2p1

References
ASMLIB
mapper Linux /dev/dm-* /dev/mapper/mpath*
mapper ASMLIB Linux
multipath ASMLIB mapper
multipath ASM ASMLIB mapper
multipath ASMLIB mapper Linux
multi path ASMLIB mapper dm- mpath
fdisk partprobe ASMLIB ASM mapper
Related
Products

Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition
Keywords
CONFIGURATION; ORACLEASM; ASMLIB

Oracle 10g r2 application server configuration in linux

0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

* First make a user like oracle and create a group

(ex: groupadd dba, useradd –G dba oracle;)

* Then create a directory

(ex: mkdir /hisapps)

* Make sure that this directory have the those group permission

(ex: chown –R oracle:dba /hisapps/; chmod ………..)

*Edit .bash_profile of oracle directory

ex:

ORACLE_BASE=/opt/oracle

ORACLE_HOME=$ORACLE_BASE/OraHome_1

JAVA_HOME=$ORACLE_HOME/jdk

ORACLE_SID=ORCL

LD_LIBRARY_PATH=$ORACLE_HOME/lib

PATH=$PATH:$ORACLE_HOME/bin

ORACLE_TERM=vt220

export ORACLE_BASE ORACLE_HOME ORACLE_SID LD_LIBRARY_PATH ORACLE_TERM JAVA_HOME

TMPDIR=/usr/tmp

TEMP=/usr/tmp

REPORTS_PATH=$REPORTS_PATH:$ORACLE_HOME/guicommon/tk/admin/TTF

export REPORTS_PATH

#DISPLAY=192.168.10.7:0.0

#export DISPLAY

NLS_LANG=AMERICAN_AMERICA.UTF8

export NLS_LANG

export TMPDIR TEMP

####################################

echo "profile upadted

####################"

* Also check /etc/sysctl.conf and add parameter as required

Ex:

*run a script from /etc/init.d/ias

#! /bin/sh

#

# Author : Arun Singh, Novell Inc.

#

# 1. Add root to dba and oinstall group to function this script properly

#

# 2. Create this file in /etc/init.d directory (ias) and use "chkconfig ias on"

# You can put these and other commands in a single file (startup or shutdown)

# and use as single command. This example is to make instruction clear.

# $ORACLE_HOME/dcm/bin/dcmctl startup

# $ORACLE_HOME/opmn/bin/opmnctl start

# $ORACLE_HOME/bin/emctl start iasconsole

#

### BEGIN INIT INFO

# Provides: ias

# Required-Start: $network $syslog $remote_fs raw

# Required-Stop:

# Default-Start: 3 5

# Default-Stop: 0 1 2 6

# Description: Start the Oracle iAS

### END INIT INFO

ORACLE_BASE=/opt/oracle

ORACLE_HOME=$ORACLE_BASE/OraHome_1

ORA_OWNER=oracle

case "$1" in

start)

echo -n "Satring Oracle iAS"

su - $ORA_OWNER --command="$ORACLE_HOME/dcm/bin/dcmctl start" &

su - $ORA_OWNER --command="$ORACLE_HOME/opmn/bin/opmnctl startall" &

su - $ORA_OWNER --command="$ORACLE_HOME/bin/emctl start iasconsole" &

;;

stop)

echo -n "Stopping Oracle iAS"

su - $ORA_OWNER --command="$ORACLE_HOME/dcm/bin/dcmctl shutdown" &

su - $ORA_OWNER --command="$ORACLE_HOME/opmn/bin/opmnctl stopall" &

su - $ORA_OWNER --command="$ORACLE_HOME/bin/emctl stop iasconsole" &

;;

status)

echo -n "Checking for Oracle iAS"

su - $ORA_OWNER --command="$ORACLE_HOME/bin/emctl status iasconsole" &

;;

*)

echo "Usage: $0 {start|stop|status}"

exit 1

esac

* now install the application server. If this file is .cpio ext

then we execute the following command

cpio – idmv

* and need to change some basic change like

vi /etc/oratab

Y

Vi /etc/rc.local

Sh /etc/init.d/ias start

* After installation we need to configure the application server

/forms/server/formweb.cfg

Change rerquied as like attached file

[Apps]

form=/hisapps/LOGON.fmx usesdi=yes

userid=username/password@SID

width=100%

height=100%

colorscheme=teal

pageTitle=APPS:: DEVELOPED BY shumon khan

imagebase=codebase

archive=frmall.jar

WebUtilArchive=frmwebutil.jar,jacob.jar

baseHTMLJInitiator=webutiljpi.htm

lookAndFeel=Oracle

splashscreen=ati_splash.gif

logo=asd.jpg

separateFrame=true

*And copy here the following three file webutiljini.htm webutiljpi.htm webutilbase.htm s

*then change orahome_1/forms/java here add all jar which we are use.

*And hisapps\orahome_1\forms\java\oracle\forms\registry then open the registry.dat file and change the following

Ex: app.ui.lovButtons=true

• Add the following file in orahome_1/forms/

Namely are webutil.cfg, webutil.plx,

• make a folder form those directory and deploy all those form the folder.
• Finally configure tns using netca

Then network admin e tnsname.ora write

Apps =

(description =

(address_list =

(address = (protocol = tcp)

(host = 192.168.xx.xx) (Port = 1521)

(connect_data = )

(service_name = orcl)

)

)

Finally run the application from the below URL from any browser:

http://192.168.xx.xx:7778/froms/frmservlet?config=apps

How to Install MS Windows Services For FMW 11g WebLogic

How to Install MS Windows Services For FMW 11g WebLogic

Admin and Managed Servers?

Applies to:

Oracle Fusion Middleware - Version: 11.1.1.1.0 to 11.1.1.2.0

Oracle Weblogic Server - Version: 10.3.1 to 10.3.2

Generic Windows

Goal

By default the only Fusion Middleware 11g components configured as MS Windows Services by the install process are:

Weblogic Node Manager

(configured as a MS Windows Service if Custom Install route is chosen when installing Weblogic)

FMW 11g Process Manager (OPMN)

(installed as a MS Windows Service if a System Component Instance is configured)

How to install MS Windows Services for Fusion Middleware (FMW) 11g Weblogic Admin or Managed Servers?

Solution

Weblogic admin and managed servers can only be configured as MS Windows services after a Weblogic domain has

been created. It is achieved by manually running a cmd script.

The advice below can applied to generic Oracle Weblogic domains or FMW 11g Component Domains such as 'SOA',

'WebCenter', 'Identity Management' or 'Portal/Forms/Reports/Discoverer'.

The technique is discussed in the documentation

Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server 11g Release 1 (10.3.1)

Chapter 3 Setting Up a WebLogic Server Instance as a Windows Service

The examples given below are for an Admin Server and WLS_FORMS belonging to a Forms / Reports Domain.

For an Admin Server

1. Create a text file

%MIDDLEWARE_HOME%\user_projects\domains\\AdminServer\security\boot.properties

Add the following lines

username=weblogic

password=

Reference:

Note:980292.1 Starting AdminServer Without Username/Password Prompt in WebLogic Server 10.3

As soon as you start the Admin Server the username and password values in this file will be encrypted.

2. Create a command script called installAdmServer_Service.cmd which has lines like

SETLOCAL

set DOMAIN_NAME=ClassicDomain

set USERDOMAIN_HOME=C:\middleware\FMW11g\user_projects\domains\ClassicDomain

set SERVER_NAME=AdminServer

set PRODUCTION_MODE=true

cd %USERDOMAIN_HOME%

call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd

call "C:\middleware\FMW11g\wlserver_10.3\server\bin\installSvc.cmd"

ENDLOCAL

3. For troubleshooting / debugging purposes it is helpful to redirect standard out and error to a text file. Although most

information is captured in the AdminServer server log files, you will not see all standard out and error when the server is

started via a MS Windows Service (unlike when you start an AdminServer from the command prompt using

startWebLogic.cmd). To redirect standard out to a text file, backup and edit installSvc.cmd and change the line at the

bottom of the file so it include the -log parameter e.g

"%WL_HOME%\server\bin\beasvc" -install

-svcname:"%DOMAIN_NAME%_%SERVER_NAME%"

-javahome:"%JAVA_HOME%" -execdir:"%USERDOMAIN_HOME%"

-extrapath:"%WL_HOME%\server\bin" -password:"%WLS_PW%"

-cmdline:%CMDLINE%

-log:"C:\Middleware\FMW11g\user_projects\domains\ClassicDomain\AdminServer-stdout.txt"

4. Now run "installAdmServer_Service.cmd". The Service should be installed, it will have a name like ""beasvc

%DOMAIN_NAME%_%SERVER_NAME%" e.g

beasvc ClassicDomain_AdminServer

The Service "Startup Type" will be 'Automatic'. Just like any other MS Windows Service you can change the 'Startup

Type' to 'Manual'.

Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for AdminServer to

start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be

monitored by reviewing the stdout txt file.

Notes:

An alternative to the boot.properties approach to specifying the Admin Server weblogic username / password is to add

the following environment variables to your wrapper cmd script - installAdmServer_Service.cmd

set WLS_USER=weblogic

set WLS_PW=manager11g

To quote the documentation

The beasvc utility encrypts the login credentials and stores them in the Windows registry.

This is one of two possible methods for avoiding the username/password prompt when a server instance starts. The

disadvantage to this method is that changing the username or password for the server instance requires you to

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id...

delete the Windows service and set up a new one with the new username and password. Instead of this method,

you can use a boot identity file. With a boot identity file, you can change the login credentials without needing to

modify the Windows service.

For a managed server e.g WLS_FORMS

1. Create a text file

%MIDDLEWARE_HOME%\user_projects\domains\\AdminServer\security\boot.properties

Add the following lines

username=weblogic

password=

As soon as you start the managed server the username and password values in this file will be encrypted. The

alternative approach - like for AdminServer - is to specify WLS_USER and WLS_PW in the wrapper cmd script. See

next point

2. Create a command script called installWLSFORMS_Service.cmd which has lines like

SETLOCAL

set DOMAIN_NAME=ClassicDomain

set USERDOMAIN_HOME=C:\middleware\FMW11g\user_projects\domains\ClassicDomain

set SERVER_NAME=WLS_FORMS

set PRODUCTION_MODE=true

set ADMIN_URL=http://mymachine.mycompany.com:7001

cd %USERDOMAIN_HOME%

call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd

call "C:\middleware\FMW11g\wlserver_10.3\server\bin\installSvc.cmd"

ENDLOCAL

Notes:

a) The ADMIN_URL value should reference the AdminServer hostname and listen port

b) The SERVER_NAME value is case sensitive. For example, if you are creating a MS Windows service for a different

managed server such as 'wls_ods1' then the value needs to match the case of the server name otherwise the startup of

the server via the MS Windows service will fail.

c) Be careful that there are no trailing spaces after each line in the command file - trailing spaces will cause the

managed server to fail at startup. For example a trailing space in the ADMIN_URL value will result in the error

address for the Admin server

3. Now run "installWLSFORMS_Service.cmd". The Service should be installed, it will have a name like ""beasvc

%DOMAIN_NAME%_%SERVER_NAME%" e.g

beasvc ClassicDomain_WLS_FORMS

The Service "Startup Type" will be 'Automatic'. Just like any other MS Windows Service you can change the 'Startup

Type' to 'Manual'.

Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for the managed

server to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can

be monitored by reviewing the stdout txt file.

Finally:

The following enhancement request exists regards automating the creation of such services in a future release of Fusion

Middleware 11g

Bug:9285337 Abstract: MANAGED SERVERS FOR WLS_FORMS AND WLS_REPORTS DON'T GET STARTED

AUTOMATICALLY

References

Bug:9285337 Abstract: MANAGED SERVERS FOR WLS_FORMS AND WLS_REPORTS DON'T GET STARTED

AUTOMATICALLY

Bug:8989011 Abstract: DOCS - WHERE ARE THE STEPS ON STARTING WLS_FORMS AS A WINDOWS SERVICE?

NOTE:980292.1 - Starting AdminServer Without Username/Password Prompt in WebLogic Server 10.3

Related

Products

Middleware > Application Servers > Weblogic Server > Oracle Weblogic Server

Middleware > Application Servers > Oracle Application Server > Oracle Fusion Middleware

Keywords

WEBLOGIC; WINDOWS; WINDOWS SERVICE; INSTALL; CONFIGURATION