Oracle RAC administrative commands - Part 1

 Dear All,

In this post i am going to share few RAC database admin commands (ASM & Listener)

> Connect to RAC server and user below commands from User session level.

srvctl add asm -n node_name -i asminstance -o ORACLE_HOME [-p spfile]

srvctl remove asm -n node_name [-i asminstance] [-f]

srvctl remove asm -n db6

srvctl start asm -n node_name [-i asminstance] [-o start_options] [-c connect_str|-q]

srvctl start asm -n node_name [-i asminstance] [-o open]

srvctl start asm -n node_name [-i asminstance] -o nomount

srvctl start asm -n node_name [-i asminstance] -o mount

srvctl start asm -n linux01

srvctl stop asm -n node_name [-i asminstance] [-o stop_options] [-c connect_str|-q]

srvctl stop asm -n node_name [-i asminstance] [-o normal]

srvctl stop asm -n node_name [-i asminstance] -o transactional

srvctl stop asm -n node_name [-i asminstance] -o immediate

srvctl stop asm -n node_name [-i asminstance]-o abort

srvctl stop asm -n racnode1
srvctl stop asm -n devnode1 -i +asm1

srvctl status asm -n node_name

srvctl status asm -n racnode1

srvctl enable asm -n node_name [-i asminstance]
srvctl enable asm -n lnx03 -i +asm3

srvctl disable asm -n node_name [-i asminstance]

srvctl disable asm -n lnx02 -i +asm2

srvctl config asm -n node_name
srvctl config asm -n lnx08

srvctl modify asm -n node_name -i asminstance [-o ORACLE_HOME] [-p spfile]
srvctl modify asm –n rac6 -i +asm6 –o /u01/app/oracle/product/11.1/asm

 some command's syntax has been changed from next releases:

$  srvctl add asm [-l lsnr_name] [-p spfile] [-d asm_diskstring]

srvctl add asm
srvctl add asm -l LISTENERASM -p +dg_data/spfile.ora

srvctl remove asm [-f]
srvctl remove asm -f

srvctl start asm [-n node_name] [-o start_options]
srvctl start asm -n devnode1

srvctl stop asm [-n node_name] [-o stop_options] [-f]
srvctl stop asm -n devnode1 -f

srvctl status asm [-n node_name] [-a]
srvctl status asm -n devnode1 -a

srvctl enable asm [-n node_name]
srvctl enable asm -n devnode1

srvctl disable asm [-n node_name]
srvctl disable asm -n devnode1

srvctl config asm [-a]
srvctl config asm -a

srvctl modify asm [-l lsnr_name] [-p spfile] [-d asm_diskstring]
srvctl modify asm [-n node_name] [-l listener_name] [-d asm_diskstring] [-p spfile_path_name]
srvctl modify asm -l lsnr1

srvctl getenv asm [-t name[, ...]]
srvctl getenv asm

srvctl setenv asm {-t "name=val [,...]" | -T "name=value"}
srvctl setenv asm -t LANG=en

srvctl unsetenv asm -t "name[, ...]"
srvctl unsetenv asm -t CLASSPATH

Next Listener Admin commands:

srvctl add listener -n node_name -o ORACLE_HOME [-l listener_name]  

srvctl remove listener -n node_name [-l listener_name] -- 11g R1 command

 srvctl start listener -n node_name [-l listener_names]

srvctl start listener -n node1

srvctl stop listener -n node_name [-l listener_names]

srvctl stop listener -n node1

srvctl status listener [-n node_name] [-l listener_names] -- 11g R1 command
srvctl status listener -n node2

srvctl config listener -n node_name

srvctl modify listener -n node_name [-l listener_names] -o ORACLE_HOME               -- 11g R1 command
srvctl modify listener -n racdb4 -o /u01/app/oracle/product/11.1/asm -l "LISTENER_RACDB4"

 some command's syntax has been changed from next releases:

srvctl add listener [-l lsnr_name] [-s] [-p "[TCP:]port[, ...][/IPC:key][/NMP:pipe_name][/TCPS:s_port] [/SDP:port]"] [-k network_number] [-o ORACLE_HOME]
srvctl add listener -l LISTENERASM -p "TCP:1522" -o $ORACLE_HOME
srvctl add listener -l listener112 -p 1341 -o /ora/ora112

srvctl remove listener [-l lsnr_name|-a] [-f]
srvctl remove listener -l lsnr01

srvctl stop listener [-n node_name] [-l lsnr_name] [-f]

srvctl enable listener [-l lsnr_name] [-n node_name]
srvctl enable listener -l listener_dev -n node5

srvctl disable listener [-l lsnr_name] [-n node_name]
srvctl disable listener -l listener_dev -n node5

srvctl config listener [-l lsnr_name] [-a]
srvctl config listener

srvctl modify listener [-l listener_name] [-o oracle_home] [-u user_name] [-p "[TCP:]port_list[/IPC:key][/NMP:pipe_name][/TCPS:s_port][/SDP:port]"] [-k network_number]
srvctl modify listener -n node1 -p "TCP:1521,1522"

srvctl getenv listener [-l lsnr_name] [-t name[, ...]]
srvctl getenv listener

srvctl setenv listener [-l lsnr_name] {-t "name=val [,...]" | -T "name=value"}
srvctl setenv listener -t LANG=en

srvctl unsetenv listener [-l lsnr_name] -t "name[, ...]"
srvctl unsetenv listener -t "TNS_ADMIN"

Thanks,

Srini

POST JWS Enablement All Browsers setup steps for EBS R12.2 Application

 Dear All,

In this post i am going to share post JWS enablement browser setup steps.

Post JWS enable All Browsers setup steps for EBS R12.2  :

 

JWS post steps on  Google Chrome

Google Chrome has not supported the Java Plug-in since release 45. Therefore, the Forms application and regular Java applets as part of the EBS can only run with JWS.

 Google Chrome for Windows Users

 Recommended browser configuration using Chrome policies on Windows Operating System

Google Chrome version 84 and later supports automatic opening of the Forms application and regular Java applets as part of EBS offering the best user experience for the end users. This requires the configuration of two Chrome policies.

Chrome policy	Description	Required value
AutoOpenFileTypes	List of file types that should be automatically opened on download.	jnlp
AutoOpenAllowedForURLs	URLs where AutoOpenFileTypes can apply.	.ebs.example.com

>> point 1 :  Chrome policy AutoOpenFileTypes requires Windows clients to be joined to a Microsoft Active Directory domain, running on Windows 10 Pro, or enrolled in Chrome Browser Cloud Management.

>> point 2 :  It is recommended to match the exact hostname of the Oracle E-Business Suite web entry point. This is done by adding a leading period. For example a value of .exacthost.example.com will match only the hostname exacthost.example.com.

Chrome policies are centrally managed by system administrators as Group Policy Object (GPO) using Microsoft Active Directory or Microsoft Intune. Deployment instructions supported by administrative templates (.admx) for Google Chrome are described on the following Google Chrome Enterprise Help pages:

• Chrome Browser on Windows (managed on premise), Chrome Browser Deployment Guide (Windows), section Policies and Templates
• Cloud-managed Chrome Browser, Manage Chrome Browser with Microsoft Intune

To properly configure these Chrome policies, please consult your system administrator. To confirm whether the Chrome policies are correctly configured on the client, perform the following steps:

1. Open Google Chrome
2. Type chrome://policy in the location bar and press enter
3. Verify the following Chrome policy values and status:
• Policy values
• AutoOpenAllowedForURLs: hostname(s) of the Oracle E-Business Suite environment(s)
• AutoOpenFileTypes: jnlp
• Status value: OK

 Default behavior (without Chrome policies)

The following describes a common use case of launching the Forms application with Java Web Start using Google Chrome. The same concept applies to regular Java applets.

1. Open Google Chrome.
2. Log in to Oracle E-Business Suite.
3. Choose a responsibility (for example, System Administrator).
4. Click on an Oracle Forms-based menu item (such as Security → User → Define) to initiate the download of the frmservlet.jnlp file.
5. Google Chrome displays the following message: "This type of file can harm your computer. Do you want to keep frmservlet.jnlp anyway?"
   

Note: This warning message is expected due to restrictions enforced by Google Chrome.

6. Click Keep to save the frmservlet.jnlp file.
7. Click the frmservlet.jnlp file in the download bar to run it.
   
8. The Forms application is now started with Java Web Start.

A new frmservlet.jnlp file is downloaded each time the Forms application or a regular Java applet is launched. The file is saved in the default download location as defined in Google Chrome. Upon launching frmservlet.jnlp, the Java Web Start launcher will automatically remove this file.

Behavior when having a specific location for each download preference set

Google Chrome has the option to present a Save As dialog window for every file downloaded. This feature is described on the Chrome Help page Download a file on Chrome. More specifically, the section "Change download locations" covers the "Ask where to save each file before downloading" user preference.

The following describes a common use case of launching the Forms application with Java Web Start using Google Chrome when the "Ask where to save each file before downloading" preference is enabled.

1. Open Google Chrome.
2. Log in to Oracle E-Business Suite.
3. Choose a responsibility (such as System Administrator).
4. Click on an Oracle Forms based menu item (for example, Security → User → Define) to initiate the download of frmservlet.jnlp.
5. Google Chrome displays a Save As dialog window, asking where to save the frmservlet.jnlp.
6. Click frmservlet.jnlp in the download bar to run it:
   
7. The Forms application is started with Java Web Start.

Google Chrome for macOS Users

Recommended browser configuration using Chrome policies on macOS Operating System

Google Chrome version 111 and later supports automatic opening of the Forms application and regular Java applets as part of EBS offering the best user experience for the end users. This requires the configuration of a Chrome policy.

Chrome policy	Description	Required value
AutoLaunchProtocolsFromOrigins	List of protocols that can launch an external application from listed origins without prompting the user.	<key>AutoLaunchProtocolsFromOrigins</key> <array>   <dict>     <key>allowed_origins</key>     <array>       <string>example.com</string>       <string>http://ebs.example.com:8000</string>     </array>     <key>protocol</key>     <string>jnlp</string>   </dict>   <dict>     <key>allowed_origins</key>     <array>       <string>example.com</string>       <string>https://ebs.example.com:8000</string>     </array>     <key>protocol</key>     <string>jnlps</string>   </dict> </array>

To properly configure this Chrome policy, please consult your system administrator.

 

 

JWS Browser set for Edge Browser :

 Microsoft Edge Browser setup steps :

The Forms application and regular Java applets as part of Oracle E-Business Suite can run only with Java Web Start when using the Microsoft Edge web browser. It has never supported NPAPI-based extensions such as the Java Plug-in.

Default behavior

The following describes a common use case of launching the Forms application with Java Web Start using Edge. The same concept applies to regular Java applets.

1. Open the Edge web browser.
2. Log in to Oracle E-Business Suite.
3. Choose a responsibility (such as System Administrator).
4. Click on an Oracle Forms based menu item (for example, Security → User → Define) to initiate the download of frmservlet.jnlp.
5. A new browser tab opens and the downloaded frmservlet.jnlp is saved in the Downloads folder as shown in the following image:
   
6. Click Open to run the file frmservlet.jnlp.
7. The Forms application is started with Java Web Start.

The Java Web Start launcher automatically removes the downloaded frmservlet.jnlp file from the browser's download folder.

The extra blank browser tab in step 5 remains open even after opening the Forms application. This is the expected behavior as a result of web browser limitations. It is safe to close this browser tab that opened when downloading the frmservlet.jnlp file.

 Microsoft Edge (Chromium)

Microsoft Edge (Chromium) version 83 and later requires the usage of Java Web Start to launch Oracle Forms based modules and other Java applets that are part of Oracle E-Business Suite.

Recommended browser configuration using Edge policies (Windows only)

Microsoft Edge (Chromium) version 85 and later supports automatic opening of the Forms application and regular Java applets as part of Oracle E-Business Suite offering the best user experience for the end users. This requires the configuration of two Microsoft Edge policies.

Microsoft Edge policy	Description	Required value
AutoOpenFileTypes 1	List of file types that should be automatically opened on download.	jnlp
AutoOpenAllowedForURLs	URLs where AutoOpenFileTypes can apply.	.ebs.example.com 2

>>  Microsoft Edge policy AutoOpenFileTypes requires Windows clients to be joined to a Microsoft Active Directory domain, running on Windows 10 Pro, or associated with Enterprise instances that are enrolled for device management.

>>  It is recommended to match the exact hostname of the Oracle E-Business Suite web entry point. This is done by adding a leading period. For example a value of .exacthost.example.com will match only the hostname exacthost.example.com.

Microsoft Edge policies are centrally managed by system administrators as Group Policy Object (GPO) using Microsoft Active Directory or Microsoft Intune. Deployment instructions supported by administrative templates (.admx) for Microsoft Edge (Chromium) are described on the following Microsoft Edge Enterprise pages:

To properly configure these Microsoft Edge policies, please consult your system administrator. To confirm whether the Microsoft Edge policies are correctly configured on the client, perform the following steps:

1. Open Microsoft Edge (Chromium)
2. Type edge://policy in the location bar and press enter
3. Verify the following Chrome policy values and status:
• Policy values
• AutoOpenAllowedForURLs: hostname(s) of the Oracle E-Business Suite environment(s)
• AutoOpenFileTypes: jnlp
• Status value: OK

Default behavior (without Microsoft Edge policies)

The following describes a common use case of launching the Forms application with Java Web Start using Microsoft Edge (Chromium). The same concept applies to regular Java applets.

1. Open Microsoft Edge (Chromium).
2. Log in to Oracle E-Business Suite.
3. Choose a responsibility (for example, System Administrator).
4. Click on an Oracle Forms-based menu item (such as Security → User → Define) to initiate the download of the frmservlet.jnlp file.
5. Microsoft Edge (Chromium) displays the following message: "This type of file can harm your computer. Do you want to keep frmservlet.jnlp anyway?"
   

Note: This warning message is expected due to restrictions enforced by Microsoft Edge (Chromium).

6. Click Keep to save the frmservlet.jnlp file.
7. Click the frmservlet.jnlp file in the download bar to run it.
   
8. The Forms application is now started with Java Web Start.

A new frmservlet.jnlp file is downloaded each time the Forms application or a regular Java applet is launched. The file is saved in the default download location as defined in Microsoft Edge. Upon launching frmservlet.jnlp, the Java Web Start launcher will automatically remove this file.

 

Thanks,

Srini