Unable to boot Oracle Linux 5 on HP DL380/DL360 Gen8

Problem: After installation of oel 5.8 64 bit linux, while booting for the first time following occur.
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Analysis:This problem looks just like the problem described in the following document:
HP ProLiant DL360 G7 Server Does Not Boot With UEK Kernel 2.6.32-100.28.9.El5 [ID 1310016.1])

For displaying the detailed log:
1) Select the 2.6.32-300.10.1.el5uek entry and enter "e" to edit it
2) Highlight the line beginning "kernel vmlinuz-2.6.32...." and enter "e" again to edit it
3) Move the cursor to the end of the line and remove the parameters "rhgb quiet" and press <enter>
4) Press "b" to boot
5) Capture the error log if it is any more verbose than you already provided.
(Note That:
rhgb = redhat graphical boot - This is a GUI mode booting screen with most of the information hidden.
quiet = hides the majority of boot messages before rhgb starts.)

Problem Description : Bug
Workaround : Using base kernel.. (Oracle Linux contains two kernels , uek and base. There is no booting problem with base kernel.)

"Solution: Kernel Upgrade -> to 2.6.32-300.39.2.el5uek"
Boot with base kernel, upgrade uek with rpm, check and configure(if necessary) the grub.conf , and reboot.

Oracle E-Business Suite R12 on Exadata V2 Sun Oracle Database Machine -- Implemented case study

Scope:

•EBS installation using rapidwiz  11G 11.1.0.7 single database with EBS 12.1.1

•Upgrade 11.1.0.7 to 11.2.0.2 ( scan supported release)

•11.2.0.2 database patches for Ebs

•Asm/Rac conversion single instance to Exadata Asm.

•Ebusiness Suite Patches to support scan.

•Ebusiness Suite config for Rac and scan.

•Paralel Concurrent Processing configuration.

•Technical Testing

•Data Load

•Functional Testing

•Benchmarks

Installation Process

Target Specs

Target Specifications:

Oracle E-Business Suite R12 (12.1) running on Oracle Database 11gR2 2 node ASM/RAC (Exadata) .

Detailed Specification: 

DB servers(x2) : 

Oracle Enterprise Linux 5.5 64 bit96 Gb Physical Ram30 Gb Sga, 10 Gb Pga

Scan configured.

Application Servers(x2) : 

Oracle Enterprise Linux 5.5 64 bit8 Gb Physical Ram 

Node 1: Admin, Concurrent, Web, Forms

Node 2: Concurrent,Web,Forms

EBS Architecture on Exadata

OPTIMIZER_USE_PENDING_STATISTICS -- 11g Feature

In the previous releases, gathered statistics are immediately placed into dictionary tables, and started to be used by the optimizer.
Pending_statistics option can be used to place those statistics into pending tables. Thus new statistics can be tested by the sessions which has optimizer_use_pending_statistics set to TRUE.
If the new statistics are found useful, they can be placed on the dictionary tables.
By this method, there is an opportunity to prevent plan regressions that result from incomplete or incorrect statistics.

Pending statistics can be viewed from the USER_%_PENDING_STATS dictionary views.

Pending statistics can be collected by the dbms_stats.set_table_prefs as follows;

--First, set publish option for the table to FALSE;
DBMS_STATS.SET_TABLE_PREFS(‘SCHEMA NAME’,’TABLE_NAME’,‘PUBLISH’,’FALSE’);
--and then collect statistics;
DBMS_STATS.GATHER_TABLE_STATS(‘SCHEMA_NAME’,’TABLE_NAME’);

By this way, collected statistics for the TABLE_NAME will be not published.

Pending statistics can be published by the dbms_stats.publish_pending_stats  as follows;

DBMS_STATS.PUBLISH_PENDING_STATS(‘SCHEMA NAME’,’TABLE_NAME’);

I found this feature very useful, because sometimes you can't anticipate the results of  gathering statistics..

Described above, also shows the new capabilities of DBMS_STATS package on 11g.
DBMS_STATS package has been the most efficient way for gathering statistics since Oracle 8i . Oracle 11g introduces DBMS_STATS.SET_*_PREFS procedure which offers much granularity of control. (DBMS_STATS.SET_PARAM has deprecated..)

Added Self Developed Applications... 

I developed several applications in my career. In this page you will find some applications I developed. Actually these are my favorites, as they have been used  in Production Systems.

As a dba and system engineer, sometimes application development was a part of my job. But most of the time, I have been developed the applications (system applications) for extending my job and gaining a developer perspective...

Note that , I have a great interest in Operating System kernel, but so far I couldnt have much time to get into it...

->Click here to read more

Oracle Exastack and Exalytics for HA and DR solution (EBS, OFSAA ,OBIEE, Essbase)

Override address in R12 Notification Mailer

Override address is set to sent all the notification mails to a certain mail address..
If override address is set to a valid email, notification mailer will send all the mails to the address specified in override address.

To set override address and put it into use; a certain process should be followed.

First; overried address is set through the following steps,

*Log into Oracle Applications Manager
*Navigate: Site Map / Administration tab / Workflow section / Notification Mailer / View Details / Set      Override Address Button

*Give a valid Email Address / Submit

When pressed submit button; notification mailer will send a verification mail to the override address set in Noticatin Mailer properties.  This is for verification..

The verification code in the verification email must be entered in order to activate override address functionality.

Tip: In my opinion; override address can be used in test,dev,lab,preprod,uat environments for generally test purposes.

EBS R12 frmcmp > FRM-91500: Unable to start/complete the build

This error is produced even with command frmcmp help=y..
This is normal as a X server is needed for running frmcmp..
Use Vnc or run frmcmp directly from console..

EBS R12 FORMS error-- Internet Explorer has modified this page to prevent cross-site scripting--

Internet Explorer user can encounter this error, when launching Forms in EBS environments.
This error seems related with a deployment problem with Forms.(bug: 8608695) Redeploying the Forms 10.1.2.3 formsapp.ear file fixes the issue.

Bug 8608695 details:

Whenever you apply a patch set over the basic version (10.1.2.0.2), the form 
servlet is not re-deployed.
This causes a major problem in case some corrections are done at the servlet 
side. Not re-deploying the form servlet, the correction won't be taken into 
account.

Here are the steps for the solution: (reference : Oracle Support)

1)Make a backup copy of the original Forms system-jazn-data.xml.
This file is found in $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml

2=Change oc4jadmin password if the password is unknown [ per Note 397174.1 ]

3)Execute $FND_TOP/bin/txkrun.pl -script=CfgOC4JApp

         Enter Application name for re-deployment ? forms
         Enter Oc4j Instance password for re-deployment ? welcome (or current password)
         Run Autoconfig <Yes/No> ? No 

4)Run AutoConfig on the instance by running the command: $ADMIN_SCRIPTS_HOME/adautocfg.sh 

ORA-12516 and ORA-12520

ORA-12516 -> check lsnrctl status and services to make sure the instances are registered..

lsnrctl status;
lsnrctl services;

Make sure the service you want to connect (for exampla PROD1) is not a blocked state (state:blocked)

ORA-12520 -> Process limit reached.
Check the process values with the following sql;

select * from v$resource_limit where resource_name in ('processes','sessions');

For RAC.

Check lsnrctl services , and lsnrctl status and also check process limit..
If found any problems in service registration, check local listener of the rac nodes.(sqlplus > show parameter local_listener)
Local listener should be set to vip addresses..
For instance 1 Local_listener Should be like;

local_listener       string      (ADDRESS=(PROTOCOL=tcp)(HOST=erm1-vip)(PORT=1521))

Direct Path insert -- Reused Space and Referential Integrity

1) With Insert append, free space is not reused.  Data will be inserted in append mode. (above the HWM) After the commit; HWM is updated to the new value .. -->  requires more space than conventional-path 
2) Refrential integrity constraint can not be maintained..

It seems these 2 things makes direct load inserts generate less redo and undo than conventional path inserts..

Ref: docs.oracle

During direct-path INSERT, you can disable the logging of redo and undo entries. Conventional insert operations, in contrast, must always log such entries, because those operations reuse free space and maintain referential integrity.

In addition, It seems "insert /*+append*/ " can be ignored by oracle , if the underlying table has referential integrity or a trigger.

Ref: Ask Tom.


what it seems to neglect to say in that old documentation is that.... 
insert /*+ append */ will ignore the append hint and use conventional path loading when the table has referential integrity or a trigger...

sqlldr can and does ignore triggers/referential integrity and even uniqueness during a direct path load, insert /*+ append */ does not - you are not using direct path when they (constraints) exist. 

parallel is always a direct path, if you go parallel, you will be appending.