Thursday, 20 December 2012

RC-50014: Fatal: Execution of AutoConfig was failed Raised by oracle.apps.ad.clone.ApplyDBTechStack


OS: OEL 5.7
Application : R12.1.3
DB 11.2.0.3


adcfgclone on dbtier fails with RC-00110 - error displayed on terminal
RC-50014: Fatal: Execution of AutoConfig was failed Raised by oracle.apps.ad.clone.ApplyDBTechStack - from ApplyDBTier_%.log file


Post cloning process of dbtier with adcfgclone kept giving me this error RC-00110: Erro occurred while relinking of ApplyDBTechStack 
 



The log files was showing the error: Autoconfig could not successfully instantiate the following files
Adcrdb.sh INSTE8
RC-50014:  




Checked the location shown in the log file and found the file was available
  /u04/oracle/ERPCLONE/db/tech_st/11.2.0/appsutil/install/ERPCLONE_bkp

Digging further showed me  that the script autoconfig complaining about  “adcrdb.sh”  is not available on the target system $db_home/appsutil/template direcotry . I don’t know how it got missed from copying the source to target !

bash-3.2$ pwd
/u04/oracle/ERPCLONE/db/tech_st/11.2.0/appsutil/template

The ls of template folder shows that adcrdb.sh is not available


I just copied the adcrdb.sh from the source system, changed the ownership and set the permission to match with the other templates, which resides in the template directory

Result of ls after copying it from source template folder

bash-3.2$ ls -l adcrd*
-rw-r--r-- 1 oraclone oinstall 4113 Jul 13 2012 adcrdb.cmd
-rw-r--r-- 1 oraclone oinstall 3038 Jul 13 2012 adcrdbrdlg.cmd
-rwxr----- 1 oraclone oinstall 2626 Jul 13 2012 adcrdbrdlg.sh
-rw-r--r-- 1 oraclone oinstall 4015 Mar 27 14:27 adcrdb.sh


Run the adcfgclone.pl again,  the script completed successfully

Reference
see MOS: 549872.1


Wednesday, 19 December 2012

APP-OFA-47230 Set up the retirement convention for this retirement date - R12 FA



Retiring  asset showed this error “Set up the retirement convention for this retirement date”


The prorate daily calendar was not entered for the current financial year, once we entered the program completed successfully

Mass Additions Post program completes with errors - Oracle R12 FA



The request log show the following error message


The prorate calendar and prorate convention are not set up for this date.
Mass Addition ID: 12730 ==> ** Failed **


The prorate daily calendar was not entered for the current financial year, once we entered the program completed successfully


Friday, 16 November 2012

Failed to create The VirtualBox COM object


Trying to start virtual box ended up giving this error on fedora 17.





There is a file called VirtualBox.xml in the location cd [home_dir]/.VirtualBox.xml In the same location there is another file called VirtualBox.xml-prev which is kind of backup of the VirtualBox.xml. 

I just renamed the  VirtualBox.xml to something and made a new copy of
VirtualBox.xml-prev with the name VirtualBox.xml. This just fixed the issue and i can start virtual box now :)


Sunday, 4 November 2012

Setting default template for concurrent requests with xml reports oracle R12

Setting default template for concurrent requests with xml reports

 


Go to System Administrator > System Administration > Concurrent > Programs

Enter the name of the concurrent program and click go
Click the Update




Go to Onsite Setting Tab
Select the template you want to default from the template list box


Sunday, 16 September 2012

Fixing Grub 2 dual boot issue with windows 7 - Fedora 17

Pc is configured dual boot with windows 7 and fedora 17.  


Windows boot manger got corrupted and unable to boot. Grub2 boot loader comes up with windows 7 boot entry but selecting to boot to windows 7 started giving boot mgr error.

I fixed windows boot issue first with win 7 cd then reinstalled grub2 using Fedora 17 live cd

  1. Fix windows 7 boot mgr

Use windows 7 installation cd to fix the win 7 boot issue
Boot from the windows 7 cd
  • Repair Your Computer




  • Select User Recovery tools



  • Startup Repair



This will find the installed windows and fix windows 7 boot issue. Windows 7 will erase grub 2 boot loader and install windows 7 boot manager so we will not be able to access  fedora. Now we have to install grub again to be able to dual boot properly.

2. Reconfigure Grub 2 for dual boot


Start the pc with fedora 17 live cd
Start a terminal
Change user to root
su - root
Mount the root partition
mount /dev/sda2 /mnt

As I have separate partition for boot, I have to mount root partition and the boot partition

mount /dev/sda1 /mnt/boot

(I am mounting to the boot directory in the previous mounted root partition so that grub2 installs on the correct location)

Root partition = /dev/sda2
Boot partition =/dev/sda1



  • Now install grub2
grub2-install –root-directory=/mnt /dev/sda





add windows boot in to the grub boot loader

grub2-mkconfig -o /mnt/boot/grub2/grub.cfg






Sunday, 12 August 2012

Physical Machine to Virtual Machine converting – Linux P2V (Unable to access resume device)


Unable to access resume device 
mount: could not find file system /dev/root
setuproot : error mounting /proc: No such file or directory
Kernel panic - not syncing: attempted to kill init!


Convert Linux Physical Machine to Virtual machine (vmware  and Virtualbox). Same procedure is working on vmware and virtual box


A fine morning started with a new question in mind, what if I could convert our Linux physical server to vm. This lead me to finishing the task and documenting it.


The  complete migration process of Linux physical machine to virtual machine. The following steps have been tested on oracle enterprise Linux 5. I will be sticking to OEL 5 during complete process.

The process comprises of taking a backup of physical machine and restoring it on a virtual machine


Back up the physical server

Startup a terminal on the physical server and change to maintenance mode

shutdown -y -g1 (in 1 minutes system will go to single user mode)






Unmount all partitions that you don’t want to include in the backup, in our case we are going to backup only root file system



tar cvpf  - --exclude=/proc --exclude=/lost+found --exclude=/bkp.tar.gz --exclude=/mnt --exclude=/sys / | gzip > /bkp.tar.gz

or

tar cvpzf  /u01/bkp.tar.gz --exclude=/proc --exclude=/lost+found --exclude=/u01/bkp.tar.gz --exclude=/mnt --exclude=/sys / 




--exclude :- use this option to exclude any file/directory from backup

Tar with z option is using absolute path in this example

Note:
make sure you have excluded the current backup file name using exclude option

copy the tar file and save at a location which we can access when restoring.

Creating Virtual Machine of Physical Server (Restoring)

Create a virtual machine and start it with Oracle Enterprise Linux 5 bootable media(cd/iso)

Type linux rescue in the prompt




During the boot up process in rescue mode system prompts you to configure network if you want  to copy files  from network configure network here,

Note:
By default vm is in NAT so don’t forget to change it to bridge if you are copying from a network


Partition the hard disk.

fdisk /dev/sda
                       
use n to create new partition

use t to change partition id to swap(82)

use a to toggle bootable flag

/dev/sda1 is our root partition(/)
/dev/sda2 is our swap partition(swap)


create file system

mkfs.ext3 /dev/sda1

this is going to be our root partition for new server

mount the partition under a new directory

mkdir a

mount /dev/sda1 /a


now copy the backup files from the media (copy over network or any other way you prefer)

I am going to copy from an external hard drive which is connected to the vm during startup

mount the external hard drive with backup files

mkdir backup
mount /dev/sdb1 /backup

copy the backup files to /a

cd /a

cp bkp.tar.gz /a or extract files to root directory directly (/a)

gzip -dc /backup/bkp.tar.gz | tar xzpvf -

or

tar xvpzf /backup/bkp.tar.gz

chroot /a

create the following directories
mkdir proc sys mnt


edit /etc/fstab to remove or comment automatically loaded partitions
and add the new entries for our new root partition and swap

/dev/sda1 / ext3  defaults 1 1     
/dev/sda2   swap  swap     0 0




Edit the grub.con file to modify the root partition related info




install grub

Either install it or reconfigure. To install just issue grub-install /dev/sda

Or setup as follows

grub
find /boot/grub/stage1
root (hd0,0)
setup (hd0)
            

at this stage restart the vm in rescue mode again. during the rescue startup system will ask to mount the Linux partitions automatically say yes and let system mount the already created Linux partition for you




system will mount it under /mnt/sysimage

now issue chroot /mnt/sysimage to change root to our newly recovered partition

configure the swap partition

mkswap /dev/sda2
swapon /dev/sda2

swapon –s :- will show you swap partition details if you did it skipping the auto mount option this is not going to give you swap details

Note:
if you manually mount the partition yourself without letting the system to do it for you and chroot to manually mounted root partition to configure the above swap setup, this is also resulting in kernel panic error. So let system mount it for you before you start configuring swap space. if you don’t do this way even after creating new ramdisk system will stop and booting with kernel panic screen







 now create new ramdisk image

backup the existing one

cp /boot/initrd-2.6.18-274.el5.img  initrd-2.6.18-274.el5.img.bkp

uname -r  to see your current kernel

ls /lib/modules     will list you all the kernel modules you have

I am using the default kernel as the other kernel is having errors while creating ramdisk. As base kernel is listed second in the grub.conf file you will have to make it default in grub.conf or select this kernel while booting up the system


mkinitrd -v /boot/initrd-2.6.18-274.el5.img  2.6.18-274.el5




exit
poweroff
remove bootable cd

Note:
don’t forget to select the base kernel 2.6.18-274.el5 while booting up if you have already not configured it to boot to base kernel.

After booting up system will fail to start xserver and asks you to reconfigure with new xserver setup say yes and system will automatically start xserver.




Wednesday, 11 July 2012

Tracing/Debugging Oracle Applications Concurrent Programmes - 11i/R12


Diagnosing/Tracing Oracle Applications Concurrent Programmes 11i/R12
  1. Simple tracing :- Creates a trace file without bind or wait (tracing without using event 10046 at level 12)

    1. Query the Concurrent programmes definition
    2. Check the Enable Trace check box


    3. Run the concurrent program using relevant responsibility
    4. Note down the concurrent request number after submitting
    5. Go to the oracle udump directory and find the trace file. Trace file names normally contain the os process id.


  2. Extended Tracing:- Creates a trace file with bind and wait (tracing with binds and waits using event 10046 at level 12)
  • Set Profile Value at respective level 

  • Go to the SRS screen of the respective responsibility to submit the request you want to trace
  • Select the name of the request 
  • Click on the debug options button (If you don’t set the profile option the debug option won’t be enabled)
  • Clicking debug options take you to create debug rule page   


  • Select the SQL Trace check box and select SQL Trace with Binds and waits
  • Click the OK button

  •  Click the Ok button


  • Submit the Request
  • After submitting the request note down the request id
  • Find out the process id which is actually doing the work
  • Go to the udump directory on the database server and find out the trace file, trace file name contains the process id you have from the above step

    Use the following sql to find out process id
    select request_id,oracle_process_id from fnd_concurrent_requests WHERE request_id = :request_id ;

    Ex:
    Go the udump location and search for trace file which contains this process id, the above query gave me my process id 16301.
    So here is my trace file name test_ora_16301.trc

    Use tkprof or trcanlzr to format the trace file.
    tkprof does not report on bind variables but you can see bind variable info in the trace file

Note: On R12 make sure you have applied Patch:8743459(MOS:1273539.1) . Trace file can be found in the user_dump_dust location with file name  <dbname>_ora_<process_id>_<USER_NAME>_CR<reqno>.trm