Blocking condition within Tuxedo on the client

The service PostReport could not be sent because of a blocking condition within Tuxedo on the client. Check the message monitor and you can see that most processes are in posting status. Check your process scheduler through psadmin and you can see psdstsrv process is hung.

First thing to NOT do is recreate the process scheduler! I believe I found a blog somewhere that suggessted this which reaaallly should be the very very last resort. 

anyway, simple solution is to bounce the hung process which is PSDSTSRV. this can be done using the Tuxedo comand line of psadmin.

## restart psdstsrv in windows:
Normally the PSDSTSRV.exe process has an ID of 103, you can check this using task manager (Follow the steps here on how to view the process in Task Manager).

Open up psadmin, navigate to Tuxedo command line and enter the following commands to shutdown/boot the process.

shutdown -g BASE -i 103
boot -g BASE -i 103

If psdstsrv wont shutdown, kill the specific process from task manager.

## Restart psdstsrv in UNIX
Basically the same steps but to get the process ID, use the command instead:

ps -ef|grep -i ps|grep -i psdstsrv



Some info you might want to know but is not used here.

Dist status when looking at the table backend:

DISTSTATUS 0 = None
DISTSTATUS 1 = Scheduled (N/A)
DISTSTATUS 2 = Processing
DISTSTATUS 3 = Generated
DISTSTATUS 4 = Unable to Post
DISTSTATUS 5 = Posted
DISTSTATUS 6 = Delete

DISTSTATUS 7 = Posting (stuck).

Run Appmsgarch process manually

PeopleTools> Integration Broker>
Service Operations Monitor> Monitoring> Monitoring Data Archiving

Enabling Virus Scan for PT 8.52

OK, so we all know that Oracle documents aren't always as detailed, but when you get it, you suddenly realize that it was really as straight forward as what the docs says.

We had that moment when enabling virus scan for our peoplesoft environment. We were looking for the documentations for when you want to use a different version of a virus scanner. Anyway, long story short, the old version of Symantec protection engine has been replaced by Symantec Protection Engine for Cloud services v12. So use this one instead.

Easy steps:

1. Install Symantec Protection Engine for Cloud services v12 - this has been tested to work with PT8.51 and PT8.53.

2.  Update the VirusScan.xml file on your webserver on its two locations:

<ps_home>/webserv/applications/peoplesoft/PORTAL.war/WEB-INF/classes/psft/pt8/virusscan 

and

<ps_home>/webserv/applications/peoplesoft/PSIGW.war/WEB-INF/classes/psft/pt8/virusscan

3. The entry should be exaclty the same as the one provided in Peoplebooks, you only need to update the IP address with the one where you've installed Symantec

http://docs.oracle.com/cd/E26239_01/pt851h3/eng/psbooks/tmcf/book.htm?File=tmcf/htm/tmcf15.htm#2E3D5C96_132F532B140__18BB

4. bounce your servers and clear the cache.

5. test.

log can be seen in your PIA logs

Happy Holidays Everyone!

Just a friendly reminder :)

WINDOWS: Add a script to right-click mouse menu

Yup that's right. I'm lazy like that.

I once created a Menu script in windows that sets the PS_HOME and PS_CFG_HOME variables automatically and calls the psadmin executable. This is useful if you have a multiple PS_HOME installation in one windows server (usually the setup for non-production environments.)

Instead of saving the file to my desktop, I added it to the right-click menu of my mouse so I wouldn't have to double click on the file.heh.

Here's how I did it:

Note: You can change the value of those in red font.

1. Open a new notepad and save with a .reg extension.
2. Paste the following lines and edit as appropriate (make sure the script location has double slash):

Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Directory\Background\shell\MENU]
@="MENU script"
"Position"="Top"

[HKEY_CLASSES_ROOT\Directory\Background\shell\MENU\command]
@="E:\\MENU\\menu.bat"

3. Save the .reg file then double click on it to add your script.

 

UNIX: Crontab

*    *    *    *    *  command to be executed
-    -    -    -    -
¦    ¦    ¦    ¦    ¦
¦    ¦    ¦    ¦    ¦
¦    ¦    ¦    ¦    +----- day of week (0 - 7) (0 or 7 are Sunday, or use names)
¦    ¦    ¦    +---------- month (1 - 12)
¦    ¦    +--------------- day of month (1 - 31)
¦    +-------------------- hour (0 - 23)
+------------------------- min (0 - 59)

Oracle Database: How to Know DB Startup time

Another quick information.

In checking when your database was last started, you can run the following command:

select to_char(startup_time, 'DD-MON-YYY HH24:MI:SS') "Startup time" from v$instance;

This is specially helpful when you do not have visibility on the DB side but has sysadm account (which is the ccase for most support guys out there.)