Pages

Sunday, June 20, 2021

Exadata DCLI Utility for Database Engineer

 Exadata DCLI Utility for Database Engineer


DCLI:


 Distributed command line utility(dcli) provides an option to execute the monitoring and administration commands on multiple servers simultaneously.In exadata database  machine , you may need to create the griddisks on all the exadata storage cells frequently. Each time , you need to login to all the storage cells and create the griddisk manually.But dcli will make our life easier once you configured  the all the storage cells on any one of the storage cell or on the database node. In this article ,we will see how to configure the dcli on multiple storage cells.


# dcli [Options] [Command]



Options



Option Use

-c CELLNAMES Executes the commands only on those cells (Storage Servers).

-g GROUPFILE Executes the command on the cells mentioned in the file.

-l USERNAME The default user is celladmin; but we can use any other user to use for remote ssh execution. Make sure the user has ssh equivalency across all the cells where you run this command

-n This shows an abbreviated output instead of a long output from each command execution

-r REGEXP Suppresses the output that matches the regular expression

-t Displays the target cells where the command will run

-x script_name The script will be executed on the target cells

-k Establishes the ssh user equivalency

-f FILENAE Copies the files to the other cells but does not execute them. It's useful for copying files and executing them later.

-d DESTFILE Destination directory or file

-s SSHOPTIONS String of options passed through to ssh

--scp=SCPOPTIONS String of options passed through to scp if different  from sshoptions

--serial Serialize execution over the cells

--unkey Drop keys from target cell's authorized_keys file

-v Verbose, print extra messages to stdout

--vmstat=VMSTATOPS vmstat command options

--version Show dcli version number

-h, --help Show help message


Importent Commands:


Command to find the image version of all db nodes

[root@exadb-adm01 ~]# dcli -l root -g /root/dbs_group imageinfo|grep "Image version"


exadb-adm01: Image version: 22.1.8.0.0.230211


exadb-adm02: Image version: 22.1.8.0.0.230211


exadb-admnp01: Image version: 22.1.8.0.0.230211


exadb-admnp02: Image version: 22.1.8.0.0.230211


exadb-admnp03: Image version: 22.1.8.0.0.230211


[root@exadb-adm01 ~]# 



List celldisks in all Cell servers:


[root@exadbcel-adm01 ~]#  dcli -g ~/cell_group -l root "cellcli -e list celldisk attributes name,status"


exadbcel-adm01: CD_00_ash_xd08cel_adm01 normal


exadbcel-adm01: CD_01_ash_xd08cel_adm01 normal


exadbcel-adm01: CD_02_ash_xd08cel_adm01 normal


exadbcel-adm01: CD_03_ash_xd08cel_adm01 normal


exadbcel-adm01: CD_04_ash_xd08cel_adm01 normal


.


.


.



List all Harddisks with name, freespace attributes


[root@exadb-adm01 ~]# dcli -g ~/cell_group_prod -l root "cellcli -e list celldisk attributes name,freespace where disktype=harddisk"


exadbcel-adm01: CD_00_exdbcel_adm01 1.447296142578125T


exadbcel-adm01: CD_01_exadbcel_adm01 1.447296142578125T


exadbcel-adm01: CD_02_exadacel_adm01 1.447296142578125T


exadbcel-adm01: CD_03_exadbcel_adm01 1.447296142578125T


.

.

.

.



[root@exadb-adm01 ~]#

Thursday, May 20, 2021

How to Resizing EXAVMIMAGES File System

 How to Resizing EXAVMIMAGES File System

The objective is to expand the size of the /EXAVMIMAGES file system using the provided instructions:

  1. Check the current size of the /EXAVMIMAGES file system:

# df -h /EXAVMIMAGES

  1. Verify the volume group (VG) details:

# vgdisplay -s

  1. Extend the logical volume (LV) named LVDbExaVMImages with 15% free space within the VGExaDb volume group:

# lvextend -l +15%FREE /dev/VGExaDb/LVDbExaVMImages

  1. Expand the XFS file system on /EXAVMIMAGES to accommodate the newly allocated space:

# xfs_growfs /EXAVMIMAGES

  1. Confirm the updated size of the /EXAVMIMAGES file system:

# df -h /EXAVMIMAGES

Note: The procedure aims to increase the size of the /EXAVMIMAGES file system by extending the logical volume and growing the XFS file system accordingly.

Wednesday, November 8, 2017

Oracle EBS JDK7 Upgrade - Step By Step

 


Oracle EBS JDK7 Upgrade - Step By Step 


EBS  Applications JDK7 Upgrade:


Using the Latest JDK 7.0 Update with Oracle E-Business Suite Release 12.2 (Doc ID 1530033.1)

Detailed steps for JDK upgrade - /extmount/security_patches/Jan17Patches/EBS/JDK7


1.Rename below folders


$ cd $COMMON_TOP/util/

$ mv jdk32 jdk32_pre_upgrade

$ mv jdk64 jdk64_pre_upgrade

2. Copy JDK7 From /extmount to $COMMON_TOP/util directory


 $ cd /opt/app/EBSPRD/fs1/EBSapps/comn/util

 $ cp -RH /extmount/security_patches/Jan17Patches/EBS/JDK7/jdk64 .

 $ cp -RH /extmount/security_patches/Jan17Patches/EBS/JDK7/jdk32 .

 $ chmod -R +w jdk*

$ ls -ltr $FMW_HOME/Oracle_EBS-app1/jdk

lrwxrwxrwx 1 applmgr appdba 43 Aug 13  2015 /opt/app/EBSPRD/fs1/FMW_Home/Oracle_EBS-app1/jdk -> /opt/app/EBSPRD/fs1/EBSapps/comn/util/jdk64

4. Copy the Albany Fonts Required for Invoice.

$ cp /opt/app/EBSPRD/fs1/EBSapps/comn/util/jdk64_pre_upgrade/jre/lib/fonts/ALB* /opt/app/EBSPRD/fs1/EBSapps/comn/util/jdk64/jre/lib/fonts


$ls -ltr /opt/app/EBSPRD/fs1/EBSapps/comn/util/jdk64/jre/lib/fonts/ALB*

$cp /opt/app/EBSPRD/fs1/EBSapps/comn/util/jdk32_pre_upgrade/jre/lib/fonts/ALB* /opt/app/EBSPRD/fs1/EBSapps/comn/util/jdk32/jre/lib/fonts


$ls -ltr /opt/app/EBSPRD/fs1/EBSapps/comn/util/jdk32/jre/lib/fonts/ALB*


3. Update jdk in $ORACLE_HOME (Forms 10.1.2)


 $ cd $ORACLE_HOME

 $ mv jdk jdk_pre_upgrade

 $ cp -RH /extmount/security_patches/Jan17Patches/EBS/JDK7/jdk32 jdk

4. Rebuild Forms and Reports Executables

$ cd $ORACLE_HOME/forms/lib

$ make -f ins_forms.mk sharedlib install

$ cd $ORACLE_HOME/reports/lib

$ make -f ins_reports.mk install



5. Verifications -

$ $ADJVAPRG -version

$ echo $CLASSPATH

$ $AFJVAPRG -version

$ echo $AF_CLASSPATH

EBS Database JRE7 Upgrade:


1) Login to Database Node Database nodes and perform the below

Copy


$ cd $ORACLE_HOME/appsutil

$ mv jre jre_pre_upgrade

$ tar -xvzf /extmount_new/security_patches/Jan17Patches/EBS/JDK7/JRE7/jre-7u121-linux-x64.tar.gz

$ mv jre1.7.0_121 jre

$ cd $ORACLE_HOME/appsutil/jre/bin

$ ./java -version


Thursday, January 14, 2016

Oracle EBS Suite Upgrade from 12.1.3 to 12.2.4 - Critical Login Issue

 Oracle EBS Suite Upgrade from 12.1.3 to 12.2.4 - Critical Login Issue 


We have recently upgraded from 12.1.3 to 12.2.4 and after go-live we started seing issues where users randomly getting the error JBO-30012, this was majorly caused by the bug fixes in the initial release and further stabilization and patching in this version fixed the issues, we have upgrade 12.2.6 and later we never seen this issue.


Error:

Error while invoking Main Menu. JBO-30012: A cookie for session g5FHanr4vzZEfS3kbZs5fXxERN and application oracle.apps.fnd.framework.navigate.server.OANavigatePortletAM has already been registered with application pool oracle.prod.orgPAYoracle.apps.fnd.framework.navigate.server.OANavigatePortletAM. The cookie must be removed first.

Monday, December 14, 2015

Oracle EBS Architecture

 

Oracle EBS Architecture Architecture Overview


The Oracle E-Business Suite Architecture is a framework for multi-tiered, distributed computing that supports Oracle E-Business Suite products. In this model, various servers or services are distributed among three levels, or tiers.





The Client Tier

The client interface is provided through HTML for the large number of HTML-based applications, and via a Java applet in a Web browser for the smaller number of Forms-based applications. A browser is used for all client access to Oracle E-Business Suite, whichever of these types of application is in use.


Application Tier

The application tier has a dual role: hosting the various servers and service groups that process the business logic, and managing communication between the desktop tier and the database tier. This tier is sometimes still referred to as the middle tier. Several service groups or servers comprise the basic Oracle E-Business Suite application tier:
  • HTTP services
  • Java services
  • Forms services
  • Concurrent Processing server

Oracle Homes

Oracle E-Business Suite Release 12.2 uses two application tier ORACLE_HOMEs.
  • An OracleAS 10.1.2 ORACLE_HOME that was used in previous 12.x releases.
  • An Oracle Fusion Middleware (FMW) ORACLE_HOME that supports Oracle WebLogic Server (WLS) and supersedes the Java (OracleAS 10.1.3) ORACLE_HOME that was used in previous releases.


Web Services

The Web services component of Oracle Application Server processes requests received over the network from the desktop clients, and includes the following major components:
  • Web Listener (Oracle HTTP Server powered by Apache)
  • Java Servlet Engine (Oracle WebLogic Server, WLS)
The Web listener component of the Oracle HTTP server accepts incoming HTTP requests (for particular URLs) from client browsers, and routes the requests to WLS.

HTML-Based Applications

The Oracle HTML-based applications (originally known as Self-Service applications) add a browser-based, walk-up-and-use functionality to Oracle E-Business Suite. They include numerous products such as iSupplier, iProcurement.


An HTML-based Applications module uses the following access path:
  1. The user clicks the hyperlink of a function from a browser.
  2. The browser makes a URL request to the Web listener.
  3. The Web listener contacts the Servlet engine (Oracle WebLogic Server), where it runs a JSP.
  4. The JSP obtains the content from the Oracle E-Business Suite tables and uses information from the metadata dictionary to construct the HTML page.
  5. The resulting HTML page is passed back to the browser, via the Web server.

Oracle Application Framework

The Oracle Application Framework is the development platform for HTML-based applications. It consists of a Java-based application tier framework and associated services, designed to facilitate the rapid deployment of HTML-based applications. Notable Oracle Application Framework components include:
  • Business Components for Java (BC4J), included in Oracle JDeveloper, is used to create Java business components for representing business logic. It also provides a mechanism for mapping relational tables to Java objects, and allows the separation of the application business logic from the user interface.
  • Oracle WebLogic Server supplies the Oracle Application Framework with underlying security and applications Java services. It provides the Oracle Application Framework with its connection to the database, and with application-specific functionality such as flexfields.


The following is a more detailed explanation of how the JSP obtains the content from the Oracle E-Business Suite tables and uses information from the metadata dictionary to construct the HTML page.
  1. Oracle WebLogic Server validates user access to the page.
  2. The page definition (metadata UI definition) is loaded from the metadata repository on the database tier into the application tier.
  3. The BC4J objects that contain the application logic and access the database are instantiated.
  4. The Java Controller programmatically manipulates the page definition as necessary, based on dynamic UI rules.
  5. UIX (HTML UI Generator) interprets the page definition, creates the corresponding HTML in accordance with UI standards, and sends the page to the browser.

Forms Services

  1. The Forms listener servlet is a Java servlet that delivers the ability to run Oracle Forms applications over HTTP or HTTPS connections. It hosts the Oracle E-Business Suite forms and associated runtime engine, mediating the communication between the desktop client and the Oracle database server, displaying client screens, and initiating changes in the database according to user actions.
  2. The Forms listener servlet caches data and provides it to the client as needed, for example when scrolling through multiple order lines that exceed the limitations of a single screen.
  3. The Forms listener servlet can communicate with the desktop client using either a standard HTTP network connection or secure HTTPS network connection. In contrast, Forms services (formerly known as Forms server) communicates with the desktop client using the TCP/IP network protocol, on top of which it layers its own protocol.
  4. The Forms listener servlet communicates with the Oracle database server using the Oracle Net networking infrastructure.
  5. The Forms listener servlet manages the creation of a Forms runtime process for each client, as well as network communications between the client and its associated Forms runtime process. The client sends HTTP requests and receives HTTP responses from the Web services, which acts as the network endpoint for the client.

Concurrent Processing Server

Concurrent Processing is an Oracle E-Business Suite feature that allows non–interactive and potentially long-running functions to be executed efficiently alongside interactive operations. It uses operating system facilities to enable background scheduling of data- or resource-intensive jobs, via a set of programs and forms.To ensure that resource-intensive concurrent processing operations do not interfere with interactive operations, they are run by a specialized component , the Concurrent Processing server.
Internal Concurrent Manager(ICM) controls all the other managers, it must be running before any other manager can be activated. Once the ICM has been activated, it starts a Service Manager on each node that is enabled for concurrent processing. Acting as an agent of the ICM, the Service Manager starts the concurrent managers on its node, excluding any managers that have been deactivated, or that have no current work shift. The ICM can be activated and deactivated from the operating system prompt, or Oracle Applications Manager. It can also be deactivated (but not activated) from the Administer Concurrent Managers form.
The ICM starts up a Service Manager on each node that is enabled for concurrent processing, by instructing the node's Applications Listener (which is dedicated to Concurrent Processing) to spawn a process running the Service Manager executable (FNDSM). The Applications Listener must be configured to source the Oracle E-Business Suite environment file before FNDSM is spawned. Following startup, the Service Manager acts as an agent of the ICM to start and stop concurrent managers on that node, according to their defined work shifts.