Binoy Kumar

What is vi? The default editor that comes with the UNIX operating system is called vi (visual editor). The UNIX vi editor is a full screen editor and has two modes of operation: Command mode commands which cause action to be taken on the file, and Insert mode in which entered text is inserted into the file. In the command mode, every character typed is a command that does something to the text file being edited; a character typed in the command mode may even cause the vi editor to enter the insert mode. In the insert mode, every character typed is added to the text in the file; pressing the (Escape) key turns off the Insert mode. While there are a number of vi commands, just a handful of these is usually sufficient for beginning vi users. To assist such users, this Web page contains a sampling of basic vi commands. The most basic and useful commands are marked with an asterisk (* or star) in the tables below. With practice, these commands should become automatic. NO...

Starting in Oracle9i, rollback segments are re-named undo logs. Traditionally transaction undo information was stored in Rollback Segments until a commit or rollback statement was issued, at which point it was made available for overlaying. Best of all, automatic undo management allows the DBA to specify how long undo information should be retained after commit, preventing "snapshot too old" errors on long running queries. This is done by setting the UNDO_RETENTION parameter. The default is 900 seconds (5 minutes), and you can set this parameter to guarantee that Oracle keeps undo logs for extended periods of time. Rather than having to define and manage rollback segments, you can simply define an Undo tablespace and let Oracle take care of the rest. Turning on automatic undo management is easy. All you need to do is create an undo tablespace and set UNDO_MANAGEMENT = AUTO. However it is worth to tune the following important parameters The size of the UND...

"oratab" is a file created by Oracle in the /etc or /var/opt/oracle directory when installing database software. Originally ORATAB was used for SQL*Net V1, but lately is's being used to list the databases and software versions installed on a server. This file may contain comments staring with a pound signs (#) in column one, and data lines consisting of entries in the following format: database_sid:oracle_home_dir:Y|N - database_sid is the system id (SID) of an Oracle instances on the server. - Oracle_home_dir is the ORACLE_HOME directory associated with this instance. - The Y|N flags indicate if the instance should automatically start at boot time (Y=yes, N=no). Besides acting as a registry for what databases and software versions are installed on the server, ORATAB is also used for the following purposes: ◦Oracle's "dbstart" and "dbshut" scripts use this file to figure out which instances are to be start up or shut do...

To configure SSH, you must first create RSA and DSA keys on each cluster node, and then copy the keys from all cluster node members into an authorized keys file on each node. Note that the SSH files must be readable only by root and by the oracle user. SSH ignores a private key file if it is accessible by others To configure SSH, complete the following steps: Create RSA and DSA keys on each node: Complete the following steps on each node: 1.Log in as the oracle user. 2.If necessary, create the .ssh directory in the oracle user's home directory and set the correct permissions on it: $ mkdir ~/.ssh $ chmod 700 ~/.ssh $ chmod 700 3.Enter the following commands to generate an RSA key for version 2 of the SSH protocol: $ /usr/bin/ssh-keygen -t rsa At the prompts: ◦Accept the default location for the key file. ◦Enter and confirm a pass phrase that is different from the oracle user's password. This command writes the public key to the ~/.ssh/id_rsa.pub...

Before installing the software, complete the following procedure to verify that the user nobody exists on the system: 1.To determine if the user exists, enter the following command: # id nobody If this command displays information about the nobody user, then you do not have to create that user. 2.If the nobody user does not exist, then enter the following command to create it: # /usr/sbin/useradd nobody

Determining if an Oracle Software Owner User Exists To determine whether an Oracle software owner user named oracle exists, enter the following command: # id oracle If the oracle user exists, then the output from this command is similar to the following: uid=440(oracle) gid=200(oinstall) groups=201(dba),202(oper)

About the Oracle Validated Configuration RPM If your Linux distribution is Oracle Linux, or Red Hat Enterprise Linux, and you are an Unbreakable Linux customer, then you can complete most preinstallation configuration tasks by using the Oracle Validated Configurations Setup RPM, available from the Unbreakable Linux Network, or available on the Oracle Linux DVD disks. When it is installed, the Oracle Validated Configuration RPM does the following: • Automatically installs any additional packages needed for installing Oracle Grid Infrastructure and Oracle Database • Creates an oracle user, and creates the oraInventory (oinstall) and OSDBA (dba) groups for that user • Sets and verifies sysctl.conf settings, system startup parameters, user limits, and driver parameters to values based on recommendations from the Oracle Validated Configurations program To become an Unbreakable Linux Network customer, contact your sales representative, or purchase a license from the Unbreakable ...

________________________________________ Scope : i) The passed UAT server E-Business Suite to be cloned. ii) The Apps Tier and DB Tier to be separated. Precloning Steps on the UAT server E-Business Suite to be cloned. 1. Startup 1.1 Start Database Tier 1.1.1 Login as database tier user – sys as sysdba 1.1.2 Set environment variable by running $SID_hostname.envfrom $INSTALL_BASE/db/tech_st/11.1.0 —- cd /u01/oracle/PNGRB/db/tech_st/11.1.0 —- . PNGRB_apps.env (note: dot in front) 1.1.3 Start database —- sqlplus “/as sysdba” —- SQL> startup 1.1.4 Start Database Listener (lsnrctl start $SID) —- lsnrctl start PNGRB . 1.2 Start Application Tier 1.2.1 Login as application tier user - apps 1.2.2 Set environment variable by running $SID_hostname.envfrom $INSTALL_BASE/apps/apps_st/appl —- cd /oracle/PNGRB/apps/apps_st/appl —- . PNGRB_apps.env (note: dot in front) 1.2.3 Start Application Tier (adstrtal.sh apps/$apps_password) —- cd $ADMIN_SC...

Since Oracle EBS or E-Business Suite is a complete automated application and caters the need of variety of industries. It has an architecture called MultiOrg or “Multiple Organization”. Whenever we talk about an organization irrespective of its multiple structure, we will find certain common things or feature or let me call it departments. It is not necessary that every organization has every department. But some departments and/or processes are more or less the same. What is an Organization? In EBS it is a vague term, infact, varied term. In Oracle EBS an organization can be a Legal Entity, or an Inventory, or a department. Anything can be treated as organization in Oracle. When we go through the Oracle EBS documentation we will find the excessive use word Organization. But it not the organization we refer it to here in daily routine. In our daily routine if we say the word “organization”, we will certainly be referring to some company, for example, Inbox Business Technologies, ...

Database Replay workload capture of external clients is performed at the database server level. Therefore, Database Replay can be used to assess the impact of any system changes below the database tier level such as below:      Database upgrades, patches, parameter, schema changes, etc. Configuration changes such as conversion from a single instance to RAC etc. Storage, network, interconnect changes Operating system, hardware migrations, patches, upgrades, parameter changes         DB replay does this by capturing a workload on the production system with negligible performance overhead( My observation is 2-5% more CPU usage ) and replaying it on a test system with the exact timing, concurrency, and transaction characteristics of the original workload. This makes possible complete assessment of the impact of the change including undesired results; new contentions points or performance regressions. Extensive analysis and reporting ( AWR , ADDM report and DB replay report) is provided to ...

-Multi-Org Access Control feature allows you to enter, process data and generate reports from a single responsibility. -This is achieved by providing the Operating Unit field on the forms/pages and while running the concurrent processes. -To Set this feature you need to define the security profile containing operating units and set it at MO: Security Profile. -You can default the Operating Unit on forms/pages by setting the MO: Default Operating Unit profile. 1) Business Grou p (Which dealt with HRMS Module) It is the Higest level in the ORG structure. 2) Legal Entity ( Dealt with Tax entities, Govt reporting authorities) 3) Set of Books ( Dealt with 4 C's that is Chart of Account, Currencies and Calender, Accounting Convention) 4) Operating Unit (Dealt with 5 sub ledger modules by name AP/AR/GL/PO/OM 5) Inventory Organization (Dealt with INV/BOM/WIP/MS_MRP) You can assign any no. of Organization under a Operating Unit.

MO_GLOBAL Package MOAC functionality is provided through the MO_GLOBAL package (AFMOGBLB.pls).  Following are some of the more important functions and procedures in the package. Init () This is generally called by forms and reports to setup the list of orgs that can be accessed.  It calls the set_org_access procedure, which in turn calls populate_orgs.  This inserts the orgs a user is allowed to access in a global temporary table -- MO_GLOB_ORG_ACCESS_TMP.  The table is populated based on the MO: Security Profile and MO: Operating Unit profile option values. Org_security() This returns a sql predicate (where clause) that controls which records can be accessed.  Example: EXISTS (SELECT 1                     FROM mo_glob_org_access_tmp oa                     WHERE oa...

Here is a list of security enhancement features: Column-Level VPD - Virtual Private Database (VPD) is now finer grained. You are now able to enforce VPD rewrite when a query references a particular column. VPD Static and Dynamic Policies - Virtual Private Database (VPD) now lets you distinguish between static policies, which are suitable for hosting environments that always need to enforce an unchanging policy, and dynamic policies, which are suitable for time-dependent enforcement, such as time of day, where rows returned must vary at a particular time. Fine-Grained Auditing (FGA) on DML - Fine-Grained Auditing (FGA) extends the support to include UPDATE, INSERT, and DELETE statements. Virtual Private Database Virtual Private Database (VPD) was first introduced in Oracle8i. It set a new standard in database security, being built into the database server, instead of each application accessing the data. Security is no longer bypassed when a user accesses the ...

Oracle uses two types of histograms for column statistics: height-balanced histograms and frequency histograms. The type of histogram is stored in the HISTOGRAM column of the *TAB_COL_STATISTICS views (USER and DBA). This column can have values of HEIGHT BALANCED, FREQUENCY, or NONE. In a height-balanced histogram, the column values are divided into bands so that each band contains approximately the same number of rows. The useful information that the histogram provides is where in the range of values the endpoints fall. In a frequency histogram, each value of the column corresponds to a single bucket of the histogram. Each bucket contains the number of occurrences of that single value. Frequency histograms are automatically created instead of height-balanced histograms when the number of distinct values is less than or equal to the number of histogram buckets specified. Frequency histograms can be viewed using the *TAB_HISTOGRAMS views.

  Part I: Installing Enterprise Linux 5 This section describes how to install Oracle Enterprise Linux 5 (OEL5) on your hardware (but the same steps will apply for RHEL5).  Please take a moment to make sure that your hardware meets or exceeds the minimum hardware requirements for Oracle Database 11 g Release 1. Minimum hardware requirements: 32-bit (x86) x86 compatible CPU 1 GB RAM 10 GB available disk space (3.5 GB for the Oracle software + 1.5 GB for the database + 3 GB for OEL5 + 2 GB swap) 64-bit (x86_64) x86_64 compatible CPU 1 GB RAM 10.5 GB available disk space (4 GB for the Oracle software + 1.5 GB for the database + 3 GB for OEL5 + 2 GB swap) Note: Both Linux and Oracle must be installed for the same architecture. 32-bit Oracle will only run on 32-bit Linux and 64-bit Oracle will only run on 64-bit Linux. Now, let's walk through the process of installing the Linux operating system on a server. The instructions assume a fresh install of Linux (as opposed to an upgrade)...