How to Create a Query-only Responsibility for HR

There is not a delivered responsibility that is query only but you can create one...

1. copy the seeded responsibility you want to use

2. in System Administrator responsibility, go to Profile > System

3. select your newly created responsibility in the Responsibility field

4. Select HR:Query Only Mode in the Profile field

5. set "HR:Query Only Mode" to "Yes" in the responsibility column

6. save

The new responsibility will have access to all the data but the user will not be able to update anything.

Creating a read-only APPS schema

To create a read-only APPS schema, use the following query.

CREATE USER "ROAPPS" PROFILE "DEFAULT" IDENTIFIED BY roapps
DEFAULT TABLESPACE "APPS_TS_TX_DATA"
TEMPORARY TABLESPACE "TEMP"
ACCOUNT UNLOCK
GRANT SELECT ANY SEQUENCE TO "ROAPPS"
GRANT SELECT ANY TABLE TO "ROAPPS"
GRANT UNLIMITED TABLESPACE TO "ROAPPS"
GRANT "CONNECT" TO "ROAPPS"
GRANT "RESOURCE" TO "ROAPPS"
GRANT "SELECT_CATALOG_ROLE" TO "ROAPPS"
GRANT "CREATE SESSION" TO "ROAPPS"

script for creating soft link for all Custom concurrent programs on target system after cloning

This code snippet helps to create all the soft link for custom concurrent program after clone on a target system.
Prerequisites
=============
Script is invoked from applmgr user account.
Shell Script for soft link creation on target system after cloning.
===================================================================
#!/usr/bin/ksh
doc()
{
cat <<-EOF
# Usage create_soft_link.sh
#
# Used for target System after cloning to take care of soft link
# for all the custom program to the executable $FND_TOP/bin/fndcpesr
#
#----------------------------------------------------------------
# Procedure :
# Should be run manually
# ---------------------------------------------------------------
# Dependencies :
# NO
# Change history :
# ---------------------------------------------------------------
#
EOF
}
#=====================================
# For displaying help and usuage
#=====================================

while getopts h OPT
do
case $OPT in
h) doc
exit 0;;
\?) echo "Usage : $0 "
exit -1;;
esac
done
shift `expr $OPTIND - 1`
#=====================================
# Check for APPL_TOP
#=====================================

if [ t${APPL_TOP} = "t" ]
then echo "Appl Top is not set, Set the appltop and run it again"
exit 0;
fi

cd $APPL_TOP
#=====================================
# Code for soft link creation
#=====================================

for prgName in `ls */11.5.0/bin/*prog`
do
echo "Creating link for - $prgName"
rm `echo $prgName sed 's/\.prog//'`
ln -s $FND_TOP/bin/fndcpesr `echo $prgName sed 's/\.prog//'`
echo "\t\t\t.......created for $prgName"
done

Creating the Central Inventory when it is lost or corrupted

Oracle Universal Installer enables you to set up the Central Inventory on a host or register an existing Oracle home with the Central Inventory, when it is lost or corrupted. You can set up the Central Inventory by using the -attachHome flag of Oracle Universal Installer using the following syntax


./runInstaller -silent -attachHome -invPtrLoc ./oraInst.loc
ORACLE_HOME="Oracle_Home_Location" ORACLE_HOME_NAME="Oracle_Home_Name"
"CLUSTER_NODES={node1,node2,...}" LOCAL_NODE="node_name"

You can use the session variables ORACLE_HOME, ORACLE_HOME_NAME, CLUSTER_NODES, REMOTE_NODES, and LOCAL_NODE.

In a cluster installation, if you don't pass the CLUSTER_NODES session variable, Oracle Universal Installer takes it from the $ORACLE_HOME/inventory/ContentsXML/oraclehomeproperties.xml file.


You may pass the REMOTE_NODES variable if you want to specify the list of remote nodes. If you want to set up the Central Inventory in the local node, you need to pass the -local flag and the REMOTE_NODES variable empty. The syntax is as follows:


./runInstaller -silent -attachHome -invPtrLoc ./oraInst.loc
ORACLE_HOME="Oracle_Home_Location" ORACLE_HOME_NAME="Oracle_Home_Name"
"REMOTE_NODES={}" -local

When you use the -local flag, it performs the action on the local node irrespective of the cluster nodes specified.


For a non-Real Application Clusters setup, you need not pass the LOCAL_NODE variable, and the CLUSTER_NODES variable is empty. The syntax is as follows:

./runInstaller -silent -attachHome -invPtrLoc ./oraInst.loc
ORACLE_HOME="Oracle_Home_Location" ORACLE_HOME_NAME="Oracle_Home_Name"

If the Central Inventory does not already exist, Oracle Universal Installer creates the Central Inventory in the location specified by the oraInst.loc file.