For the people who think differently Welcome aboard
This related to Topics such as EBS, Siebel, People Soft, .. etc
select RELEASE_NAME from fnd_product_groups;
output :
RELEASE_NAME
———————–
12.1.0.1
Thank you
Osama mustafa
the Rapid Install window will show many errors for HTTP.
Checking status of OPMN managed Oracle HTTP Server (OHS) instance …
Processes in Instance: PROD_ebs.ebs.sandiego.com
——————-+——————–+———+———
ias-component | process-type | pid | status
——————-+——————–+———+———
OC4J | oafm | 21168 | Alive
OC4J | forms | 21078 | Alive
OC4J | oacore | 20943 | Alive
HTTP_Server | HTTP_Server | N/A | Down
Download and apply the patch 6078836 from OracleMetaLink to fix an issue with the Oracle HTTP Server bundled with the E-Business Suite technology stack. We unzip the patch:
[oracle@ebs oracle]$ unzip p6078836_101330_LINUX.zip
Archive: p6078836_101330_LINUX.zip
creating: 6078836/
inflating: 6078836/libdb.so.2
inflating: 6078836/README.txt[oracle@ebs oracle]$ cd 6078836/
[oracle@ebs 6078836]$ ls
libdb.so.2 README.txtThen we copy to /usr/lib.
[root@ebs 6078836] $ cp libdb.so.2 /usr/lib
[root@ebs lib]# cd /usr/lib
[root@ebs lib]# pwd
/usr/lib[root@ebs lib]# ls libdb.so*
libdb.so libdb.so.2
Processes in Instance: PROD_ebs.ebs.sandiego.com
——————-+——————–+———+———
ias-component | process-type | pid | status
——————-+——————–+———+———
OC4J | oafm | 21168 | Alive
OC4J | forms | 21078 | Alive
OC4J | oacore | 20943 | Alive
HTTP_Server | HTTP_Server | 28519 | Alive
Thank You
Osama mustafa
There’s more than One Reason For this i will provide you with two solutions (Meta-link Note):
Solution One :
1. Backup and edit the forms configuration file (Default= formsweb.cfg)
2. Modify the HTMLdelimiter to have only one character as a value
HTMLdelimiter=%
3. Save and exit the file.
Solution Two :
Edit oracle_apache.conf and comment out the include related to the forms.conf as the following :
# Oracle Forms Developer
#include “/oas/product/oas2/forms/server/forms.conf”
Thank You
osama mustafa
SELECT COUNT(*)
FROM DBA_OBJECTS
WHERE STATUS = 'INVALID';
For a more detailed query, use the following script :
SELECT OWNER, OBJECT_TYPE, COUNT(*)
FROM DBA_OBJECTS
WHERE STATUS = 'INVALID'
GROUP BY OWNER, OBJECT_TYPE;
To recompile an individual object, connect to SQL*PLUS as the owner of the object (generally apps) and use one of the following depending on the object type :
alter package compile; (package specification)
alter package compile body; (package body)
alter view compile; (view)
If the object compiles with warnings, use either of the following to see the errors that caused the warnings :
show errorsOR
select * from user_errors where name = '';
Another way to correct invalid objects is to run the adadmin utility as follows:
1. Log in as APPS User : /
2. Start the adadmin-Utility from the Unix prompt with this command :
adadmin
The utility will then ask you a series of questions.
3. Under the Maintain Applications Database Objects Menu, select Compile APPS schema(s)
Other Way :
Also try running $ORACLE_HOME/rdbms/admin/utlrp.sql ( as sysdba )
Within Applications, there is a script to compile INVALID objects – called ADCOMPSC.pls
Arguments for ADCOMPSC.pls :
1 – Schema to run in
2 – Password for schema
3 – Check errors for objects starting with #3
NOTE: The order in which to compile Invalid Objects in schemas is SYS, SYSTEM, APPS and then all others. APPS_DDL and APPS_ARRAY_DDL should exist in all schema’s. In case of an ORA-1555 error while running adcompsc.pls, restart the script.
The script can be run as followed :
cd $AD_TOP/sql
sqlplus @adcompsc.pls SCHEMA_NAME SCHEMA_PASSWORD %Example : SQL> @adcompsc.pls apps apps %
After the script completes, check for invalid objects again. If the number has decreased, but invalid objects still exist, run adcompsc.pls again. Keep running adcompsc.pls until number of invalid objects stops decreasing.
If there are any objects still left INVALID, verify them by using the script ‘aderrchk.sql’ to record the remaining INVALID objects. ‘Aderrchk.sql’ uses the same syntax as ‘adcompsc.pls’. This script is also supplied with the Applications. Send the aderrchk.sql to a file using the spool command in sqlplus.
e.g. sqlplus x/y @aderrchk.sql SCHEMA_NAME SCHEMA_PASSWORD %
For objects which will not compile, try the following :
select text
from user_source
where name = 'OBJECTNAME'
and text like '%Header%';
This script will provide the script that creates the packages/recreates the packages.
SQL>@packageheader
SQL>@packagebody
If recreating the package does not make the package valid, analyze the user_errors table to determine the cause of the invalid package :
select text
from user_errors
where name = '';
Thank You
Osama Mustafa
1.Stop iasconsole
2.Secure iasconsole
3.Start iasconsole
1.Stop iasconsole
2.Update Oracle As Console StandAlone OC4J to support unsecure port :
<web-site <span="" display-name="Oracle Enterprise Manager iAS Console Website" host="[ALL]" port="" style="color: red;"> to <web-site <span="" display-name="Oracle Enterprise Manager iAS Console Website" host="[ALL]" port="" style="color: red;">
3.In same File
<ssl-config needs-client-auth="true" keystore="server/keystore.test" keystore-password="%EMD_KEYSTORE_PASSWORD%" />
<ssl-config needs-client-auth="false" keystore="server/keystore.test" keystore-password="%EMD_KEYSTORE_PASSWORD%" />
4.Update AS Console Local Management Agent to support the unsecure HTTP protocol.
The EMD_URL property in
$ORACLE_HOME/sysman/config/emd.properties
needs to get switched back to the HTTP (non-secure) protocol.
Change:
EMD_URL=https://:/emd/main
to
EMD_URL=http://:/emd/main
$ORACLE_HOME/sysman/emd/targets.xml
to change the StandaloneConsoleURL property of oracle_ias target to switch back to the HTTP (non-secure) protocol.
Change:
<target ...="" name="EnterpriseManager." type="oracle_ias"> <... <property 0);"="" 0,="" color:="" name="StandaloneConsoleURL" rgb(255,="" value="https://:/emd/console"/> to<target ...="" name="EnterpriseManager." type="oracle_ias"> <... <property 0);"="" 0,="" color:="" name="StandaloneConsoleURL" rgb(255,="" value="http://:/emd/console"/>
3) Make entry of hostname and domain name in /etc/sysctl.conf
kernel.hostname=
kernel.domainname=
* soft nproc 2047
* hard nproc 16384
* soft nofile 2048
* hard nofile 65536
session required /lib/security/pam_limits.so
if [ $USER = “oracle” ]; then
if [ $SHELL = “/bin/ksh” ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
fi
Primary Group – oinstall#groupadd oinstall
Secondary Group#groupadd dba
#useradd -g oinstall -G dba oracle
Give the password
# passwd oracle
Changing password for user oracle.
New UNIX password:
Retype new UNIX password:
passwd: all authentication tokens updated successfully.
Thank You
Osama mustafa
On the database tier server node,
shut down the database listener in the old Oracle home.
On the database server node,
as the owner of the Oracle 11g file system and database instance, unzip and extract the 11.1.0.7 patch set file for your platform.
Use the runInstaller in the patchset to start the OUI.
Once the OUi starts from the LOV s in the Oracle_home list choose the appropriate one to be upgraded and the location also.
The present oracle_home and its location will appear if the environment is set correctly.
Proceed with the next steps on the OUI screen.
On next Screen it will Say Configuration Assistant has failed.Skip this Step since its not required for Oracle E-Business Suite .
MOST IMPORTANT STEP IN UPGRADE .
After Installation you need to Apply the RDBMS patches7486407 and 7684818
Copy $APPL_TOP/admin/adstats.sql from the administration server node to the database server node.
$ sqlplus / as sysdba
SQL> shutdown normal;
SQL> startup restrict;
SQL> @adstats.sql
SQL> shutdown normal;
SQL> startup;
SQL> exit;
Thank You
Osama mustafa
Let start upgrading :
1 – You need To install this patch p6890831_111070_Linux-x86-64.zip.
2- Bring Down Database And Services Down And make sure it .
*Database :
sqlplus / as sysdba
SQL>shutdown immediate ;
$ps -ef | grep pmon “to make sure the database is not running”
Listener :
$lsnrctl status
$lsnrctl stop
$lsnrctl status
3-Just In case Take backup of your database .
4-unzip the patch , and run it under Oracle User
$./runInstaller
Select the ORACLE_HOME to upgrade and then click next, the prerequisites steps will complete last click INSTALL. At the end up the installation it will ask to run root.sh as root user. We need root user password or sudo user privilege to run root.sh script.
5-After Upgrade do the following and its mandatory :
cd $ORACLE_HOME/rdbms/admin
sqlplus / as sysdba
SQL> startup upgrade;
SQL>spool pre_upgrade.log
SQL> @utlu111i.sql
6-cd $ORACLE_HOME/rdbms/admin
sqlplus / as sysdba
SQL> spool upgrade_date.log
SQL> @catupgrd.sql
Take check the validity, version of the installed components
sqlplus / as sysdba
sql>set pages 250
sql> set lines 1000
sql> col comp_name for a40
sql> select comp_name, version, status from dba_registry;
7-SQL>shutdown immediate;
8-Recompiling the invalid objects
cd $ORACLE_HOME/rdbms/admin
sqlplus / as sysdba
SQL>startup;
SQL>spool recompile.log
SQL> @utlrp.sql
Controlfiles, datafiles, redo logs, archive files, tempfiles must be included in the backup. If the files are in different paths, the same has to be backedup.
As Oracle User :
$mkdir /backup_date
$cp /u01/oracle/oradata/orcl/*.* /backup/backup_date
$cd $ORACLE_HOME/dbs
$cp inittest.ora inittest.ora_bkpdate
$cp spfiletest.ora spfiletest.or_bkpdate
$cp orapwtest.ora orapwtest.ora_bkpdate
**Take a backup of home path
$mkdir product_bkp
$cd /u01/oracle/product
$tar czf /backup/oracle_11106.tar.gz 11.1.0
**dbhome, coraenv,oraenv backup
As Root User :
#cd /usr/local/bin
#cp dbhome dhome_bkpdate
#cp coraenv coraenv_bkpdate
#cp oraenv oraenv_bkpdate
revert back to old version :
1. untar the binary backup
2. Backup the current database and then replace them with cold back taken before applying the patch.
As Root User :
cd /usr/local/bin
#cp dbhome_bkpdate dbhome
#cp coraenv_bkpdate coraenv
#cp oraenv_bkpdate oraenv
As Oracle User :
oracle binary restoration
cd /u01/oracle/product
$rm -rf 11.1.0
$mkdir 11.1.0
$cp /backup/oracle_11106.tar.gz 11.1.0
$cd 11.1.0
$gunzip oracle_11106.tar.gz
$tar -xvf oracle_11106.tar
Datafile backup restoration
cd /u01/oracle/oradata/orcl/
$rm *
$cd /backup/backup_date
$cp *.* /App1/oracle/oradata/orcl/
$cd $ORACLE_HOME/dbs
$cp inittest.ora_bkpdate inittest.ora
$cp spfiletest.ora_bkpdate spfiletest.ora
$cp orapwtest.ora_bkpdate orapwtest.ora
sqlplus / as sysdba
SQL>startup;
SQL>select * from v$version;
SQL>select comp_name, version, status from dba_registry;
Osamamustafa.blogspot.com
Steps :
1.Stop the DB Control
On Unix
$ emctl stop dbconsole
On Windows Open a Command Window and type
**> emctl stop dbconsole
2.Check that the DB Control is stopped
On Unix$ emctl status dbconsole
On Windows
Open a Command Window and type
**>emctl status dbconsole
3.Connect to the database as a user with DBA privilege with SQL*Plus and execute:
SQL> alter user sysman identified by ; SQL> connect sysman/[@database_alias]
$ emctl setpasswd dbconsole
Provide the new SYSMAN password **>: emctl setpasswd dbconsoleProvide the new SYSMAN password$ emctl start dbconsole Open a DOS Command Window and type
**>: emctl start dbconsole Thank you
Osama Mustafa 1.Stop the DB Control
On Unix $ emctl stop dbconsole
On WindowsOpen a Command Window and type**> emctl stop dbconsole
2.Check that the DB Control is stopped$ emctl status dbconsole
On WindowsOpen a DOS Command Window and type**> emctl status dbconsole
SQL> alter user sysman identified by ;
SQL> connect sysman/[@database_alias]
5.Go to $ORACLE_HOME/host_sid/sysman/config do the following :
6.Restart the DB Control
On Unix
$ emctl start dbconsole Open a DOS Command Window and type**> emctl start dbconsole I Publish the same lesson but on 11g .
Thank you Osama mustafa
Technology Geek 