Pular para o conteúdo principal

How to recreate oraInventory in ebs R12

Edit the oraInst.loc file:
vi /etc/oraInst.loc

Change the inventory_loc to a new location:
inventory_loc=/prod/oraInventory_new

Create the new directory:
mkdir /prod/oraInventory_new

Give permissions to the new directory:
chmod -R 777 /prod/oraInventory_new

-- Add the 10.1.3 Oracle Home to the new created oraInventory:
cd $INST_TOP/ora/10.1.3
. ./APP.env

Go to the $ORACLE_HOME:
cd $ORACLE_HOME

Edit the oraInst.loc and point it to the same location ad done in step 1:
inventory_loc=/prod/oraInventory_new

Add the 10.1.3 Oracle Home to the new oraInventory location:
cd $ORACLE_HOME/appsutil/clone
./ouicli.pl

Verify if the 10.1.3 is added to the new oraInventory directory:

cd /prod/oraInventory_new/ContentsXML

cat inventory.xml

If it's not added, check the /prod/oraInventory_new/logs file.

Verify the oraInventory has the information about the 10.1.3 Oracle Home:
export PATH=$ORACLE_HOME/OPatch:$PATH
opatch lsinventory -detail

-- Add the 10.1.2 Oracle Home to the new created oraInventory:
cd $INST_TOP/ora/10.1.2
. ./APP.env

Go to the $ORACLE_HOME:
cd $ORACLE_HOME

Edit the oraInst.loc and point it to the same location ad done in step 1:
inventory_loc=/prod/oraInventory_new

export TMP=/tmp

Add the 10.1.2 Oracle Home to the new oraInventory location:
cd $ORACLE_HOME/appsutil/clone
./ouicli.pl

Verify if the 10.1.2 is added to the new oraInventory directory:
cd /prod/oraInventory_new/ContentsXML
cat inventory.xml

If it's not added, check the /prod/oraInventory_new/logs file.

Verify the oraInventory has the information about the 10.1.2 Oracle Home:

export PATH=$ORACLE_HOME/OPatch:$PATH
opatch lsinventory -detail

--Add the DB Oracle Home to the new created oraInventory:
cd $ORACLE_HOME
. ./BD.env

Go to the $ORACLE_HOME:
cd $ORACLE_HOME

Edit the oraInst.loc and point it to the same location ad done in step 1:
inventory_loc=/prod/oraInventory_new

Add the DB Oracle Home to the new oraInventory location:
cd $ORACLE_HOME/appsutil/clone
./ouicli.pl

Verify if the DB Oracle Home is added to the new oraInventory directory:
cd /prod/oraInventory_new/ContentsXML
cat inventory.xml

If it's not added, check the /prod/oraInventory_new/logs file.
Verify the oraInventory has the information about the DB Oracle Home:

export PATH=$ORACLE_HOME/OPatch:$PATH
opatch lsinventory -detail


Note:

Running ouicli.pl can result in error:
"Exception in thread "main" java.lang.NoClassDefFoundError: oracle/apps/ad/clone/util/OracleHomeCloner"

This can be fixed by setting Context variable s_clonestage to \clone

For example:

\oracle\PROD\apps\apps_st\comn\clone

Comentários

Postagens mais visitadas deste blog

Webcenter Content - Cache Configuration for JdbcFileStore configuration

The configuration values below, control the temporarily cached files keep in FileCache table. FsCacheThreshold Specifies the maximum cache size, in megabytes (default=100) Once the threshold is met, Content Server starts deleting files that are older than the minimum age, as specified by the FsMinimumFileCacheAge parameter FsMaximumFileCacheAge The age at which files are deleted, expressed in days. The default is 365 days FsMinimumFileCacheAge The minimum age at which cached files can be deleted This parameter is used in conjunction with the FsCacheThreshold parameter to determine when to delete cached files FsCleanUpCacheDuringIndexing This parameter activates vault cache cleaning, while FsCacheThreshold, FsMaximumFileCacheAge and FsMinimumFileCacheAge are controling its behaviour.  Expect, when this is enabled on a system that currently has a large number of files in the FileCache table, the first cycle will take a long time to complete. How to Confi...

Assign Backup Policy for Boot and Block Volumes - OCI

To get Availability Domain oci iam availability-domain list  #!/bin/bash OCI_AD="hQsi:SA-SAOPAULO-1-AD-1" OCI_COMPARTMENT="ocid1.compartment.oc1..aaaaaaaavgyjpoffz5qliieawamjaksfb6juxejurtduclqjkvv66ookcxja" #Get Silver policy ocid funct_get_policy(){ OCI_POL_OCID=$(oci bv volume-backup-policy list | jq -r '.data[] | select(."display-name"|contains("silver"))' | jq -r '.id') } funct_boot_vol (){ #Create a file with all boot volume ocid oci bv boot-volume list --availability-domain ${OCI_AD} -c  ${OCI_COMPARTMENT} | jq -r '.data[].id' > boot-vol.txt while IFS="" read -r p || [ -n "$p" ] do   printf 'Seeting backup policy for %s\n' "$p"   oci bv volume-backup-policy-assignment create  --asset-id  $p  --policy-id ${OCI_POL_OCID} done < boot-vol.txt } funct_block_vol (){ #Create a file with all block volume ocid oci bv volume list  -c ${OCI_COMPARTMENT} | jq -r '.data[].id' ...

Logical Backup Using dbms_datapump

Sample scripts to make a logical backup using dbms_datapump -- BACKUP BY SCHEMA declare h1 NUMBER; begin h1 := dbms_datapump.open (operation => 'EXPORT', job_mode => 'SCHEMA', job_name => 'TESTE2', version => 'COMPATIBLE'); dbms_datapump.set_parallel(handle => h1, degree => 1); dbms_datapump.add_file(handle => h1, filename => 'BKP_SCHEMAS.LOG', directory => 'BKP_DATA_PUMP', filetype => 3); dbms_datapump.set_parameter(handle => h1, name => 'KEEP_MASTER', value => 0); dbms_datapump.metadata_filter(handle => h1, name => 'SCHEMA_EXPR', value => 'IN(''DENILSON'')'); dbms_datapump.add_file(handle => h1, filename => 'BKP_SCHEMAS.DMP', directory => 'BKP_DATA_PUMP', filetype => 1); dbms_datapump.set_parameter(handle => h1, name => 'INCLUDE_METADATA', value => 1); dbms_datapump.set_parameter(handle => h1, name ...