Skip to main content


Showing posts from 2008

admrgpch -- One way/Highway to apply multiple patches

This utility is availabble under under AD_TOP/bin There are 2 ways to you can use this utility. Just copy all the patches that you need to merge as single patch. Make sure that they all belong to the same version. Open the driver file and check the version in the header. compatible release 11.5.0 compatible platform GENERIC characterset us7ascii extension recordpatch 4219646 US extension patch_type software base compatible feature checkfile NLS lang and release should be the same for all the patches which will be merged as one. Place all the zip files under one directory and unzip all the patches in the same directory. This becomes your source and create a directory at the same level where you have the source directory. Following are the usage details. usage: admrgpch -help admrgpch admrgpch -s -d [-verbose ] [-merge_name ] [-manifest ] [-logfile ]where * -help Print help message. * -verbose Can be one of: { 0(SILENT),

How to clone an Express/OFA instance

First make sure that the OS and its Parameters are set to the same values as the source system. Copy the entire Express and OFA installation to the destination(Clone) server. Retain its directory structure. Follow the steps below to configure the Clone. 1. Got to the directory where you have all your database files by default it will be under ORACLE_HOME/<>dba name<>/users/<>workstation name<> 2. Open the cfg file for the current workstation/analyst/db. 3. Notedown the path mentioned for variable "OFASYSCFPATH" 4. Goto OFASYSCFPATH 5. Open ofasyscf.cfg Change SHAREDHOST and SUPERHOST to the destionation ipadress 6. Note the path for super user database and move on to step 7. 7. Open the database database using Express administrator. Browser for user.catalog under Variables tree (If there is no user.catalog then move ) Goto data section, under this modify the ipaddress for all the databases to the destination address. Notedown the databas

CPU -- Critical Patch Updates

CPU -- Critical Patch Updates This is a way through with Oracle releases security fixes for Oracle products. CPU's are release for the supported products mainly for the following reasons. 1) Data confidentiality, i.e. an attacker is able to view information that he or she should be prevented from viewing. 2) Data integrity, i.e. an attacker is able to modify information that he or she should be prevented from modifying. 3) System availability, i.e. an attacker is able to disrupt legitimate use of or access to a system. CPU's patches are released every 3 months on a specific date. So if you are planning to apply any of the security patches/fixes then you can wait for the recent one. The dates are as follows, a. 15th Jan b. 15th Apr c. 15th Jul d. 15th Oct Per Oracle patches will be released on tuesdays close to 15th of the months mentioned above. For more information refer to Oracle Official link on CPU's:

10gAS Rel 3 FAQ's

1. Compatible JDBC Driver version for 10g release 3. Any recommendations. Following are the JDBC versions compatible with 10gR3., (THIN) Use metalink document 365120.1 : Statement of Direction - JDBC Driver Support within Oracle Application Server 2. List of all common actions that can be performed on the instances in a group. Common actions on the group are as follows, a. Create/delete a group b. Start/stop a group c. Delete/add instances to a group 3. Moving instances across groups and impact if any. No there are no impact of moving OC4J instances across the groups. 4. Can we seperate OC4J and other components. No this cannot be done in 10.1.3.x. You can remove these components from the list but these cannot be seperated. Each OC4J instance comes with the following components, a. ascontrol -- Only one instance of ascontrol can be up and running for the entire application server home. b. default application b1. datatags b2. javasso 5. Custo

CPIO -- Oracle's widely used archiving utility

CPIO is the most widely used archival tool by Oracle apart from ZIP archival. CPIO means -- CoPy In CoPy Out CPIO was earlier being used for tape archivals like its counterpart TAR. CPIO always needs an standard input for archiving or for extracting the same. CPIO takes over other counterparts by archiving the files comparitively smaller than others do. I have never tested this but will surely try it and try to update the blog in sometime. Following are the few useful commands that you should know before un-archiving any CPIO file. 1. To extract a CPIO file. cpio -id <> any.CPIO Here -o signifies cpio to read the standard output and copy it the files onto standard output -v signifies verbose which will list all the file names > signifies standard output file Other advanced options can be found with the man pages on your OS. Refer: