My Blog List

Saturday, July 18, 2009

Upgrade Process Flow

Initial Pass



Move to Production

CA Setup for Application Upgrade

Step -1-


Step -2



step -3



step -4



Final-

Sunday, July 12, 2009

PeopleSoft Application upgrade- Finance Upgrade Kickoff Agenda

PeopleSoft Application upgrade FSCM88 to FSCM9MP5 – Estimated timeline diagram

PeopleSoft Application upgrade – Delete non PS statistics, SQL Server

SELECT sysobj.NAME TableName, stat.name StatisticsName
FROM sys.stats stat, SYSOBJECTS sysobj
WHERE stat.object_id = sysobj.ID
AND ( substring(stat.name,1,2) <> 'PS' AND substring(stat.name,2,2) <> 'WA')
AND sysobj.NAME like 'PS\_%' ESCAPE '\'

Sunday, December 28, 2008

Monitor the Peoplesoft PIA running on weblogic

####################################################################################
# SCRIPT: web-srv-tst.sh
#
# AUTHOR: Pandey, Deep Chandra
# Citagus Software Pvt. Ltd.
#
# DESCRIPTION:
#
# This script is run by crontab at scheduled intervals.
# It will monitor the Peoplesoft PIA running on weblogic
#
# FILES:
#
# REVISION HISTORY
# WHO WHEN (DD/MM/YY) WHY
#
# Pandey, Deep Chandra JUly 14, 2008
#
#
#DBA to whome mail will be sent
DBALIST="deep_pandey@citagus.com";
#####################################################################################
cwd=`pwd`
WBLOG=$cwd/webstatus.log
cd /bea/weblogic92/server/bin
source setWLSEnv.sh
java weblogic.Admin -url t3://citagus-srv8:80 -username system -password citagus04 GETSTATE PIA >> $WBLOG
java weblogic.Admin -url t3://citagus-srv8:80 -username system -password citagus04 GET -pretty -type ServerRuntime >> $WBLOG
#-------> finding any Error message in the Webstatus.log file

egrep "RUNNING" ${WBLOG} >/dev/null 2>&1
if test $? = 0 # Testing the output of previous command - egrep...
then
echo "Web serer is Up and running"
#mail -s "Alert !! Web Server is Running at [$HOSTNAME] Machine" $DBALIST < ${WBLOG}
else
echo "Web server is Down"
mail -s "Alert !! Web Server is down at [$HOSTNAME] Machine" $DBALIST < ${WBLOG}
fi
mv $cwd/webstatus.log $cwd/webstatus.log.bkp

Thursday, September 25, 2008

How do I restrict or allow a few client machines to connect to Oracle Server ?

If you do not want a particular client machine say machine of person X , connect to oracle server or vice versa.

The step are very simple , you need the following things

You must know the IP-address or host name of the client machine.

# Add the following lines in SQLNET.ora if you want to invite only the following client machine to connect
TCP.INVITED_NODES =(, )
# Add the following lines to SQLNET.ora if you want to invite all the client machine except the following
TCP.EXCLUDED_NODES=(, )
# The following is the required parameter in SQLNET.ora.
TCP.VALIDNODE_CHECKING=yes

Here is the simple example, to allows the user to connect to the oracle database with IP-ADDRESS 172.16.8.209 or 172.16.8.207 only , configure the protocol.ora as follows :-

tcp.invited_nodes=(172.16.8.209 , 172.16.8.207 )
tcp.validnode_checking=yes

Stop and restart the listener to make this effect.


Note :
There are certian bugs attached with this method , check the oracle support or metalink for this for your specific platform and oracle version.
For further information check the metalink doc 185936.1