0% found this document useful (0 votes)
69 views

Errors & Documentation

Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
69 views

Errors & Documentation

Copyright
© © All Rights Reserved
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 46

ERROR: ORA-01031

--For the above error,cause due to password file problem during the
installation.so we manually create the password file in th directory dbs.

Path:/ORACLE_HOME/dbs

Steps to create password file:

$orapwd file=’/ORACLE_HOME/dbs/file_name’
password=password_name entries=3

Note: here entries mean in which number of attempts to failed to login


to the account.

$ sqlplus sys/password_name as sysdba.


Cloning :

Cloning: cloning is a method which is used to create the same copy of


the database for testing purpose. When the code developers develop
the code is not apply on production database directly before that
tested on the cloning database.

Steps :

-for the database startup parameter file is


important(pfile/spfile). Pfile is text file ,spfile is binary file so
here for the editing we choose pfile, copy the original database
pfile (initOLDSID.ora) to clone database pfile
(initNEWSID.ora).

Here and replace the old sid’s to new sid’s in new pfile.

-for the database mount control file is necessary so we need


controlfile, but actually controlfile is binary file so we can’t
copied and edited for this we create a script(i.e clone.sql) is
making from trace file for this,

When database in open state,


SQL> alter database backup controlfile to trace;

Due to this command control file is traced to


udump directory by default
(/ORACLE_HOME/admin/SID/udump)

Open that trace file (this is text file) and copy the some content
like below:

Old script:

STARTUP NOMOUNT
CREATE CONTROLFILE REUSE DATABASE "TEST" RESETLOGS
ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 '/dbfiles/oradata/test/redo01.log' SIZE 50M,
GROUP 2 '/dbfiles/oradata/test/redo02.log' SIZE 50M,
GROUP 3 '/dbfiles/oradata/test/redo03.log' SIZE 50M
-- STANDBY LOGFILE
DATAFILE
'/dbfiles/oradata/test/system01.dbf',
'/dbfiles/oradata/test/undotbs01.dbf',
'/dbfiles/oradata/test/sysaux01.dbf',
'/dbfiles/oradata/test/users01.dbf',
'/dbfiles/oradata/test/example01.dbf',
'/dbfiles/oradata/test/dbf1',
'/dbfiles/oradata/test/.df2',
'/dbfiles/oradata/test/.df3',
'/dbfiles/oradata/test/.df4',
'/dbfiles/oradata/test/.df5',
'/dbfiles/oradata/test/ramn_01.dbf'
CHARACTER SET WE8ISO8859P1
;

New script:

STARTUP NOMOUNT
CREATE CONTROLFILE SET DATABASE "CLONE" RESETLOGS
ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 '/dbfiles/oradata/clone/redo01.log' SIZE 50M,
GROUP 2 '/dbfiles/oradata/clone/redo02.log' SIZE 50M,
GROUP 3 '/dbfiles/oradata/clone/redo03.log' SIZE 50M
-- STANDBY LOGFILE
DATAFILE
'/dbfiles/oradata/clone/system01.dbf',
'/dbfiles/oradata/clone/undotbs01.dbf',
'/dbfiles/oradata/clone/sysaux01.dbf',
'/dbfiles/oradata/clone/users01.dbf',
'/dbfiles/oradata/clone/example01.dbf',
'/dbfiles/oradata/clone/dbf1',
'/dbfiles/oradata/clone/.df2',
'/dbfiles/oradata/clone/.df3',
'/dbfiles/oradata/clone/.df4',
'/dbfiles/oradata/clone/.df5',
'/dbfiles/oradata/clone/ramn_01.dbf'
CHARACTER SET WE8ISO8859P1
;

Here also change the old sid name(like test) to new sid
name(like clone)

Here helping command :%s/oldSID/newSID/g.


And replace word “reuse” by set.

This is script for creating the controlfile for cloning database.

for the database datafiles are important for mainting data so


we copy the all datafiles and place them in the new directory
like clone. Here we take the backup in offline.

don’t copy thr control files

$ORACLE_BASE/oradata/clone

if we open and see the pfile contain the


udump,cdump,adump, bdump paths , so we create those
directories in the clone directory

/ORACLE_HOME/admin/clone

Here copy the pfile directory from old sid-name(test) directory


clone.

-now we run the script at sql console(database is in


shutdown mode).
SQL>! Export ORACLE_SID=clone
SQL>@clone.sql
Due to this script controlfile is created and
database is mounted automatically because script contain the
code.

Now we give the following command at sql console is

SQL>alter database open resetlogs;

Here the database is in open mode

SQL>select status from v$instance;

STATUS
-----------
OPEN

Now the cloning database is available.

-due to the cloning cloning database name and old database


name is same. Same sid name is effects when the we require
the rman backup because rman backup needs the database –id
otherwise its no need to change. Sid name changing process as
follows:

 From sqlplus:
 shutdown immediate
 startup mount
 exit

From unix:

nid target=/

NID will ask if you want to change the ID. Respond with 'Y'. Once it
has finished, start the database up again in sqlplus
shutdown immediate
startup mount
alter database open resetlogs
/

SQL>select dbid from v$database;

Some quiries:

 alter database backup controlfile to trace as


'/home/oracle/cr_<new sid>.sql'

 create pfile='init<new database sid>.ora' from


spfile;

 15. Set the databases global name


The new database will still have the source databases global name.
Run the following to reset it:
 alter database rename global_name to <new
database sid>
Oracle Apps dba single node 11i installation steps:

Download Software

Download two additional packages from Metalink Patch 4198954.

Make sure an appropriate Java JDK (1.3.1) is available on the system.

Unpack Files

First unzip the Oracle patch:


unzip p4198954_21_LINUX.zip

Next, create a staging area for the Oracle Applications software:


mkdir /Stage11i
cd /Stage11i

# Start Here
mkdir startCD

# APPL_TOP
mkdir oraApps

# RDBMS
mkdir oraDB

# Tools
mkdir oraiAS

# Databases
mkdir oraAppDB

Copy the contents of all the DVDs into the appropriate directories.

Hosts File

The /etc/hosts file must contain a fully qualified name for the server:
<IP-address> <fully-qualified-machine-name> <machine-name>
Set Kernel Parameters

Add the following lines to the /etc/sysctl.conf file:


kernel.shmmax = 2147483648
kernel.shmmni = 100
kernel.shmall = 2097152
# semaphores: semmsl, semmns, semopm, semmni
kernel.sem = 100 256 100 100
fs.file-max = 327679
kernel.hostname = testapps01.localdomain #<--- full qualified
hostname !!
kernel.domainname = localdomain #<--- correct domain name !!

Run the following command to change the current kernel parameters:


#sysctl -p

Add the following lines to the /etc/security/limits.conf file:


oracle soft nofile 65536
oracle hard nofile 65536
oracle soft nproc 16384
oracle hard nproc 16384

Setup

The following additional packages are required. Depending on the update/respin version of
Enterprise Linux, the exact package versions and locations may vary.
alsa-lib-devel-*
audiofile-devel-*
compat-db-*
compat-gcc-32-3*
compat-gcc-32-c++-3*
compat-libcwait-2*
compat-libgcc-296-2*
compat-libstdc++-296-2*
compat-oracle-rhel4-1*
esound-0*
esound-devel-0*
fontconfig-devel-2*
freetype-devel-2*
gcc-3*
gcc-c++-3*
glib-1*
glib-devel-1*
gnome-libs-1*
gnome-libs-devel-1*
gtk+-devel-1*
gtk2-devel-2*
imlib-1*
imlib-devel-1*
jdk-1*
libaio-0*
libaio-devel-0*
libjpeg-devel-*
libtiff-devel-*
libungif-devel-*
libungif-progs-*
make-3*
openmotif21*
ORBit-devel-*
xorg-x11-deprecated-libs-6*
xorg-x11-deprecated-libs-devel-6*
xorg-x11-devel-*

Due to all the package inter-dependencies, it probably makes sense to copy all these packages
from the CDs to a single directory, then install then using the following command. For
convenience, I wrapped all the necessary packages for an OEL 4.5 installation into a single tar
file (11i-rh4-rpms.tar), making subsequent installations much simpler.
rpm -Uvh *.rpm

Install the packages associated with Patch 4198954:


cd 4198954
rpm -Uvh compat-oracle-rhel4-1*
rpm -Uvh compat-libcwait-2*

Create the new groups and users:


groupadd oinstall
groupadd dba
groupadd oper
groupadd apache

useradd -g oinstall -G dba oracle


passwd oracle

useradd -g oinstall -G apache apache


passwd apache

Create the directories in which the Oracle software will be installed:


mkdir -p /u01
chown -R oracle:oinstall /u01

Login as the oracle user and add the following line at the end of the .bash_profile file:
# Oracle 9i
LD_ASSUME_KERNEL=2.4.19; export LD_ASSUME_KERNEL

Installation

Log into the oracle user. If you are using X emulation then set the DISPLAY environmental
variable:
DISPLAY=<machine-name>:0.0; export DISPLAY

Start the Rapid Install Wizard by issuing the following commands:


cd /Stage11i/startCD/Disk1/rapidwiz/
chmod u+x rapidwiz
./rapidwiz

Follow any instructions and rerun as requested. The Rapid Installation Wizard installation is
shown below.

1. Click the "Next" button on the welcome screen.

2. Accept the default "Install Oracle Applications E-Business 11i" option by clicking the
"Next" button.
3. Select the "No" option, then click the "Next" button.

4. Select the "Single-node" option, then click the "Next" button.

5. Select the "fresh database" database type, enter a database name, in this case I used
"PLAY", then click the "Next" button.
6. Enter the appropriate base directory, in this case I used "/u01/oracle", then click the
"Next" button.
7. Select the "E-Business Suite licensing" option, then click the "Next" button.

8. Accept the default products by clicking the "Next" button.


9. Select the appropriate country functionality, then click the "Next" button.

10. Select any additional language support if necessary, then click the "Next" button.
11. Select the appropriate territory and characterset information, then click the "Next" button.

12. Enter the appropriate base directory, in this case I used "/u01/oracle", then click the
"Next" button.
13. Accept the global settings by clicking the "Next" button.

14. Note the location of the config files. It's worth taking a copy of this file as it comes in hady
when reloading or upgrading the software. Click the "Next" button.
15. Wait for the system checks to complete.

16. Assuming all the system checks were completed successfully, click the "Next" button.
17. Click the "Next" button on the installation review screen.

18. Click the "Yes" button to start the installation.


19. Wait while the installation takes place.

20. Assuming all the post-install checks are successful, click the "Next" button.
21. Click the "Finish button to exit the Rapid Install Wizard.

Post Installation :

 For Example, I create two users(like oracle,appsuser) and one


group(like dba). Oracle for database, appsuser for applications.
 So , we save the paths in bash_profiles for every user.
 For database user oracle,

$ vi .bash_profile

Add the following path

. /db/oracle1/SID-db/9.2.0/ SID_hostname.env

For example: . /db/oracle1/visdbadb/9.2.0/VISDBA_uday.env

Run the bash_profile by

$ . .bash_profile

 For applications user appsuser,

$ vi .bash_profile
Add the following path

. /apps/oracle2/visdbaappl/APPSVISDBA_uday.env

$ . .bash_profile

 For getting the front end page database listener must be in up, for
that run the following script at respective users

# su – oracle (database side)

$ cd /db/oracle1/visdbadb/9.2.0/appsutil/scripts/VISDBA_uday ---

$ sh addlnctl.sh start (it is a listerner script file)

# su – appsuser (apps side)

$ cd /apps/oracle2/visdbacomn/admin/scripts/VISDBA_uday ---

$ sh adstrtal.sh start

Rapid Installation Wizard Portal

Once the installation is complete, the Rapid Installation Portal can be accessed using the
following information.
 URL: http://machine-name:8000

Eg: http://192.168.1.114:8000

(or)

Add the IP address and host name to the /etc/hosts like follows

Vi /etc/hosts

192.168.1.114 uday.dbaworld.com uday

Here uday is alias


Now http://uday.dbaworld.com:8000

 Username: SYSADMIN
 Password: SYSADMIN

The front screen of the portal is shown below.

 Forms are open in internet explorer effectively only. For opening the forms JInitiater
is necessary

For the url reference :


http://www.oracle-base.com/articles/apps/OracleApps_11_5_10_2_InstallationOnOEL45.php

For configure the vnc viewer :

#vncserver :1
Passwd: narasimha
Veify narasimha
#vncpasswd -----to change the password
#vncserver –kill :1 -----to kill the process

Multi node installation:

    Hardware requirement
 
    For this installation type is good to have 2 personal computers with
this configuration:
  Pentium 4 Processor
 1Gb RAM
 200 Mb Hard Disk
 1 network card (Linux compatible). ( D-Link DFE-530 TX
network card could be used )
    Also a switch and 2 network cable are necessary in order to connect
the 2 computers. 
 
 
    Software download
 
Software Link
Oracle Applications http://edelivery.oracle.com/
CentOS 4 (a Red Hat 4
http://isoredirect.centos.org/centos/4/isos/i386/
Linux version)
Compatibility files for
running Oracle on RHEL 4:
http://oss.oracle.com/projects/compat-
compat-oracle-rhel4-1.0-
oracle/files/RedHat/
5.i386.rpm
compat-libcwait-2.1-
1.i386.rpm
 
 
    Linux installation
 
    I suggest a full Linux installation even if there are some components
which are not necessary to spend less time and to have all we need for
the Oracle Applications installation. I suggest also on the both computers
to create 1Gb tmp directory and a 2Gb swap directory.   
 
    Staging the Oracle Application
 
    Oracle Applications are downloaded in a compressed format, so these
files cannot be used directly for the installation. For this reason the files
must be unzipped in the same directory to create the staging directory:
    For that we have to:
  create a directory which can be read/ write by all users for the
download ( for example /media/usbdisk/download );
  create a directory which can be read/ write by all users for the
staging ( for example /media/usbdisk/APPS0 ); 
  unzip all the Oracle Application zip files in the staging directory
( /media/usbdisk/APPS0).  These directories must be created:
oraAppDB, oraApps, oraDB, oraiAS, startCD. 
    If we have the Oracle DVDs / CDs with the Oracle Applications
installation kit, we have to follow the next steps to set up a staging
directory:
 insert the Start Here disk in the CD-ROM (DVD-ROM) drive
 $ cd /media/cdrecorder/Disk1/rapidwiz
 run the AutoStage script: $ perl adautostg.pl
 set up the stage area directory (If you
chose  /media/usbdisk/APPS0 as the top-level directory, the
staging directory will be  /media/usbdisk/APPS0/Stage11i)
 indicate the components to be staged
 
    Preparing the Linux environment for the installation
 
    In order to have a Linux environment ready for the Oracle
Applications 11i multi-tier installation we have to:
 
    1)  connect the 2 computers (PC1 will be the database server, and
PC2 will be the server which will have the middle-tier installed on):
   
         on PC1 ( the database server):
         -  edit /etc/hosts and add the following lines:
            192.168.1.201   APPS_svr.localdomain      APPS_svr
            192.168.1.202   DB_svr.localdomain          DB_svr
         -  set the network card with 192.168.1.202 IP address and Mask:
255.255.255.0
        
         on PC2 ( the applications/ middle-tier server):
         -  edit /etc/hosts and add the following lines:
            192.168.1.201   APPS_svr.localdomain      APPS_svr
            192.168.1.202   DB_svr.localdomain          DB_svr
         -  set the network card with 192.168.1.201 IP address and Mask:
255.255.255.0
      2)  test the connection between the 2 computers (on each computer):
 
[root@localhost ~]# ping -c 2 DB_svr
PING DB_svr.localdomain (192.168.1.202) 56(84) bytes of data.
64 bytes from DB_svr.localdomain (192.168.1.202): icmp_seq=0 ttl=64
time=0.109 ms
64 bytes from DB_svr.localdomain (192.168.1.202): icmp_seq=1 ttl=64
time=0.113 ms

--- DB_svr.localdomain ping statistics ---


2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.109/0.111/0.113/0.002 ms, pipe 2

[root@localhost ~]# ping -c 2 APPS_svr


PING APPS_svr.localdomain (192.168.1.201) 56(84) bytes of data.
64 bytes from APPS_svr.localdomain (192.168.1.201): icmp_seq=0
ttl=64 time=0.038 ms
64 bytes from APPS_svr.localdomain (192.168.1.201): icmp_seq=1
ttl=64 time=0.031 ms

--- APPS_svr.localdomain ping statistics ---


2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.031/0.034/0.038/0.006 ms, pipe 2
    3) create the oracle user on the database server and
the applmgr user on the  applications/ middle-tier server. The oracle user
must be a member of the dba group as well 
 
    4) create /APPS_DB directory (owned by oracle:dba) on the
database server and /APPS_MI directory (owned
byapplmgr:oinstall) on the applications server
 
    5) install (on both computers) the compatibility files for running
Oracle on RHEL 4 
 
      rpm -ihv compat-oracle-rhel4-1.0-5.i386.rpm
      rpm -ihv compat-libcwait-2.1-1.i386.rpm
 
    Installing the Oracle Applications 11.5.10.2
 
    The Oracle Applications 11i multi-node installation is done with the
root account. 
   
    1. Start the installation on the database tier:
      #  cd /media/usbdisk/APPS0/Stage11i or in my case
/media/usbdisk/APPS0/11i_Unzipped/
      #  cd startCD/Disk1/rapidwiz
      #  ./rapidwiz
   
     Here are the windows which appears and the responses we have to
choose:
 
Select "Next".
Select "Next".

Select "Next".
Select "Multi-node" type.

Select "Next".
Select "No, do not enable load   balancing"

Select "Next".
Select "db_svr" for the database service and "apps_svr"
for the other services (Administration, Concurrent
Manager, Forms, Web)

Select "Next".
Select "Next".
Select the database install information as shown on this
screen.

Select "Next".

Select the application tier install information as shown on


this screen.

Select "Next".
Select "Next".
Change the configuration file path as shown in this
window. The configuration file must not be in a
temporary directory. 

Select "Next".

Select "Next".
Select "Next".

Select "Yes".
Wait until the installation will complete.

If the installation looks not to advance that could be


verified by looking to the CPU utilization or/ and disk
activity (io). vmstat utility is used for this.
Select "Next".
Select "Finish".
    
 
 2. Copy config.txt from /APPS_DB (database tier) to /APPS_MI
(application tier)  
 
 3. If the database server was stopped restart the database and database
listener
 
 4. Finish the installation on the application tier (connected as root):
      #  cd /media/usbdisk/APPS0/Stage11i or in my case
/media/usbdisk/APPS0/11i_Unzipped/
      #  cd startCD/Disk1/rapidwiz
      #  ./rapidwiz
   
     Here are the windows which appears and the responses we have to
choose:
 

Select "Next".
Select "Next".
Change the configuration file path as shown in this
window. The configuration file must not be in a
temporary directory. 

Select "Next".

Select "Next".
Select "Next".

Select "Yes".
Wait until the installation will complete.

Select "Next".
Press "Connect to Oracle Applications 11i" to test if
the Oracle Applications are running.  Press "Finish".

Now the installation is done.


 
 
5. Make the libjavaplugin_oji.so available for Firefox browser (if used)
 
cd /usr/lib/firefox-1.5.0.3/plugins
ln -sf
/APPS_MI/viscomn/util/java/1.4/j2sdk1.4.2_04/jre/plugin/i386/ns610-
gcc32/libjavaplugin_oji.so
 
 
In-Oracle.com  -> Oracle Applications (apps)  -> 11i
-> Oracle Applications 11i Multi-Node Installation on Linux

Oracle Applications EBS 11i, R12      Oracle Database      Data Warehouse &


BI      Oracle Middleware      PL/SQL      
Kernel parameters for 10g installation:

# vi /etc/sysctl.conf

#kernel.shmall = 2097152
#kernel.shmmax = 2147483648
kernel.shmmni = 4096
# semaphores: semmsl, semmns, semopm, semmni
kernel.sem = 250 32000 100 128
#fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default=262144
net.core.rmem_max=262144
net.core.wmem_default=262144
net.core.wmem_max=262144

# sysctl –p

To Change the sid of db:

 Backup the database.


 Mount the database after a clean shutdown:

 SHUTDOWN IMMEDIATE

STARTUP MOUNT

$ nid TARGET=/ DBNAME=<new sid>

Give choice Yes

Shutdown the database:


SHUTDOWN IMMEDIATE

Create new parameter file(Pfile) from old pfile and modify the
db.name

$ startup mount pfile=’ ---‘


ALTER DATABASE OPEN RESETLOGS;

You might also like