PeopleSoft Learning

Sharing my simple script created to monitor the status of the PRCS scheduler services.

1. PRCS-List.txt is a file referred by my logic which contains PRCS Domain names which we have to monitor…

[Sandeep]:/dba/scripts>cat PRCS-List.txt

SANDEEP

SANSNEW

[Sandeep]:/dba/scripts>

Script starts here….

ScriptPath="/dba/scripts”

rm $ScriptPath/PRCS-Report.txt

cat $ScriptPath/PRCS-List.txt while read line

do

psadmin -p status -d $line > $ScriptPath/PRCS-TMP.txt

#The below statement “egrep” checks for the services within that domain, in this case I have checked if that domain has 'BBLPSPRCSRVPSDSTSRV' running… you can change this according to version and based on requirement … When you change this list you have to change the count of process you are monitoring in the if loop “if [ ${status} -ne 3 ]” in the below line accordingly … in my case since I am monitoring only 'BBLPSPRCSRVPSDSTSRV' hence I have mentioned 3 in the if loop “if [ ${status} -ne 3 ]”

status=`egrep 'BBLPSPRCSRVPSDSTSRV' $ScriptPath/PRCS-TMP.txt wc -l`

if [ ${status} -ne 3 ]

then

echo "" >> $ScriptPath/PRCS-Report.txt

echo $line >> $ScriptPath/PRCS-Report.txt

`echo "Process Scheduler is DOWN" >> $ScriptPath/PRCS-Report.txt`

echo "" >> $ScriptPath/PRCS-Report.txt

echo "++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++" >> $ScriptPath/PRCS-Report.txt

else

#echo $status >> $ScriptPath/PRCS-Report.txt

echo "" >> $ScriptPath/PRCS-Report.txt

echo $line >> $ScriptPath/PRCS-Report.txt

`echo "Up & Running" >> $ScriptPath/PRCS-Report.txt`

echo "" >> $ScriptPath/PRCS-Report.txt

echo "++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++" >> $ScriptPath/PRCS-Report.txt

fi

done

Script Output - PRCS-Report.txt will look as below; you can e-mail this to your ID from the UNIX Server….

SANDEEP

Up & Running

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

SANSNEW

Process Scheduler is DOWN

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

TraceOptions

This section enables you to specify the tracing options that you can enable on the application server to track the SQL and PeopleCode of the domains. You can also set all of the trace parameters from the PeopleSoft sign-in page.

TraceSQL

Enter the logging level for SQL tracing for all clients. Traces are written to <PS_HOME>/appserv/<domain>/LOGS/<Domain User ID>_<svrname>.tracesql. Enter 0 to disable tracing; enter 7 to enable a modest tracing level for debugging. For other levels of tracing, set this option to a value that equals the sum of the needed options. For example, to trace only SQL, enter 1; to trace SQL statements and connect statements enter 7 (1+ 2 + 4 = 7). Tracing can consume large amounts of disk space over time, so be sure to reset this option to 0 when you finish troubleshooting.

TraceSQLMask

Enter the logging level ceiling for SQL tracing for individual clients. Traces are written to <PS_HOME>/appserv/<domain>/LOGS/<Client User ID>_<svrname>.tracesql. Clients must specify the necessary SQL tracing level by using the PeopleSoft Configuration Manager on the Trace tab. To prevent clients from turning on the application server trace and consuming resources, the application server uses TraceSQLMask as an administrative control facility.

If a client transmits a request to trace SQL, the application server compares the value that is transmitted to the TraceSQLMask value. If the client value is less than or equal to the TraceSQLMask value, the application server enables the trace. However, if the client value is greater, the application server enables the trace up to the TraceSQLMask value. Trace files are written on the application server; no trace shows up on the client workstation. Trace values are set in the PSAPPSRV.CFG file. Output files are written to $PS_HOME/appserver/winx86/<domain>/logs.

TracePC

Enter a level for PeopleCode tracing for activity that is generated by all clients on a domain. Eligible values are defined in the configuration file. TracePC values are displayed in the PeopleSoft Configuration Manager on the Trace tab. You can find the results in <PS_HOME>/appserv/<domain>/LOGS/<domain>.log.

TracePCMask

Enter which PeopleCode trace options that are requested by client machines will be written to the trace file. You can find the results in <PS_HOME>/appserv/<domain>/LOGS/<ClientMachine>.<domain>.log.

The "standard" rollback plan has plenty of issues. Simply restoring the file backup will not revert the system to pre-migration state.

These are the steps to do a proper backup/rollback, it's not detailed but it should give you the general idea on what's involved and how to do it correctly.

Backup Steps:

1. Copy Project Definition Only to Target DB (e.g. Prod)
2. Open Project Definition in Target DB, and set Action for Project = COPY
3. Copy the Project Definition to a Project Backup file.
4. Run Data Mover or Oracle export to backup all the data in all the tables including any Message Catalog Entries and User Roles in the project.
5. At this point there should be 2 files -- the Project Backup and the Data Backup

Rollback Steps:

1. Open the project definition from the Source DB (e.g. QA)
2. Set Action for Project = DELETE (This will ensure all objects that moved are deleted)
3. Move the Project from the Source DB to the Target DB to perform the delete
4. Copy the Project Backup from file to the Target DB to restore the objects.
5. Alter Tables/Rebuild Views.
6. Run Data Mover or Oracle import to restore all Data and any Message Catalog Entries and User Roles from the Data Backup

IPC resources are operating system resources, such as message queues, shared memory, and semaphores. When an application server shuts down properly all IPC resources used are removed from the system. In some cases, however, an application server may fail to shut down properly and stray IPC resources may remain on the system. When this happens, it may not be possible to reboot the application server.

The command to remove IPC resources, tmipcrm, resides in TUXDIR/bin. This command reads the binary configuration file (TUXCONFIG), and attaches to the bulletin board using the information in this file.

To list all IPC resources

"tmipcrm -n [TUXCONFIG]" (Ex. tmipcrm -n D:\PS\appserv\PSDEMO\PSTUXCFG)

To Clean/remove all IPC resources used by the BEA Tuxedo system

Application Server Command
tmipcrm -y /apps/psoft/pt844/appserv/PSDEMO/PSTUXCFG

Process Scheduler Command
tmipcrm -y /apps/psoft/pt844/appserv/prcs/PSDEMO/PSTUXCFG

This will remove the IPC resources associated that particular domain…

The ERP Connectors are used with the Integration Broker product. If you do not plan to utilize the Integration Broker portion of PeopleTools, reply NO to the prompt. If you do plan to use Integration Broker, reply YES to the prompt. If you reply NO to the prompt but then later decide to use Integration Broker you will have to go back and reinstall PeopleTools. The YES will cause files to be unloaded to your PsHome for use with the Integration Broker product.