On The Peoplesoft Road

Peoplesoft HCM 9.1 Feature Pack 2

2011-11-10T21:18:00.001+01:00

It has been announced today, the HCM 9.1 feature pack 2 comes with Peopletools 8.52 and a lot more new features including “A new search-based, menu-free navigation capability allows users to easily locate and navigate to relevant information quickly and in context from any page”, find out the press release here.

It is not available for download yet on edelivery but that should be a matter of hours.
We could also expect the corresponding Peoplesoft OVM template to be release pretty soon, keep tracking edelivery/linux.

Nicolas.

GUID on Web domain

2011-11-10T18:27:00.001+01:00

I was managing Peoplesoft Web domains in OEM Grid Control (11.1) within the Peoplesoft plugin. After cloning different environments some strange behavior came out.

First, the GUID must be unique across the all the Peoplesoft databases (table PSOPTIONS), otherwise databases are somehow pointing to each other. Before starting with the whole OEM configuration, it’s probably better to set it to blank and restart the Application Server. A new value will be given when Application Server will start.

Then I came to know that a Webserver configuration file also contains the GUID. If it is the wrong one, your Web domain will point to the wrong database… fix it by updating the file $PIA_HOME/webserv/…/domain/webprof/option.prop within the proper GUID value.

Nicolas.

DomainConnectionPwd parameter

2011-11-10T17:10:00.001+01:00

A quick note after an issue I was facing to.
On Peopletools 8.51, I cloned an existing database, creating new application server domain and copied an existing web domain. Everything went fine, I could connect onto the front-end application and work… until I bounced the application server. On the Peoplesoft login page, an error was returned complaining that application server was down at that time… where it was obviously up and running.
Checking the application server log file reveals the following :
"ERROR: Jolt client (ip address <ip_address_is_given_here>) does not have proper application password"
After few minutes, solution came in the top of my head. A new parameter introduced in 8.50, DomainConnectionPwd, should match between configuration files of application server (psappsrv.cfg) and web server (configuration.properties).
Once fixed and bounced application server, it worked again. But I just wondering why and how it worked in a first place.

Nicolas.

Peopletools 8.52 : the PS_APP_HOME variable

2011-11-03T20:56:00.001+01:00

Up to Peopletools 8.51, the application installation (e.g. HRMS, FSCM…) must be done in the exact same folder where the Peopletools have been installed, known as PS_HOME directory. Otherwise you were not able to load any data in a newly created database (through the database setup of FataMover, no option was appearing). It was quite confusing, expecially for new comers in the Peoplesoft world.
As of Peopletools 8.52, it has been changed. You can install the application where ever you want, and say to the Peopletools where it is through a new variable PS_APP_HOME. That’s not an environment variable, but rather has to be set within the Configuration Manager.
Let’s have a look.
First you should create a profile for the database you want to load data in :

Then you will define it has a “database” (2tier connection) :

Next window, a new field is there to define where is the application installed :

Go till the end of the profile definition.
Now you should be able to see the application in Datamover, database setup :

And all the path directories are properly set for the INPUT datafiles in the created dms :

Now we can discuss the exact use of having separate home for Peopletools and Application, it could really be a debate in the organization.

Nicolas.

Peopletools 8.52 : managing PIA with psadmin

2011-11-01T21:16:00.001+01:00

Peopletools 8.52 introduces new options in the psadmin menu, that’s rather interesting to see. Let’s see the PIA part, totally new here.
It can be managed within the command line
[ptools852@orion5 appserv]$ ./psadmin -help
Usage:

Miscellaneous options:
----------------------
psadmin                              (Interactive utility)
psadmin -h                           (Display this message)
psadmin -v                           (Display version number)
psadmin -env                         (Display environment as set by psadmin)
psadmin -replicate -ch <PS_CFG_HOME>

Pure Internet Architecture (PIA) Options:
-----------------------------------
psadmin -w command -d domain       (Perform command on PIA domain)
    where 'command' must be one of the following:
             start     (Start the domain)
             shutdown (Shutdown this domain)
             shutdown! (Forced shutdown of this domain)
             status    (Show status for this domain)
             remove    (Delete the domain)

psadmin -w configure -d domain -c c_set -p p_set
    where 'c_set' specifies domain settings, having the following format:
          minHeapSize/maxHeapSize/maxThreads/authTokenDomain
      and 'p_set' specifies port settings, having the following format:
          httpPort/httpsPort

psadmin -w configure -d domain -s site -c c_set
where 'c_set' specifies site settings, having the following format:
appSrvConnString/webProfile/pooling/reportPath/webProfUser/webProfPword/appSrvConnPword
<…snipped…>

Or within the menu
[ptools852@orion5 appserv]$ env|grep PIA_HOME
PIA_HOME=/appl/psoft/hcm91fp1_web
[ptools852@orion5 appserv]$ env|grep CFG_HOME
PS_CFG_HOME=/appl/psoft/hcm91fp1_dom
[ptools852@orion5 appserv]$ ./psadmin

PSADMIN -- Tools Release: 8.52.02
Copyright (c) 1996, 2011, Oracle. All rights reserved.

--------------------------------
PeopleSoft Server Administration
--------------------------------

Config Home: /appl/psoft/hcm91fp1_dom

1) Application Server
2) Process Scheduler
3) Search Server
4) Web (PIA) Server
5) Switch Config Home
6) Replicate Config Home
q) Quit

Command to execute (1-6, q): 4

-----------------------------
PeopleSoft PIA Administration
-----------------------------

PIA Home: /appl/psoft/hcm91fp1_web

1) Administer a domain
2) Create a domain
3) Delete a domain

q) Quit

Command to execute:

=> Let’s create a new web domain for my new Peopletools 8.52 installation.
[ptools852@orion5 appserv]$ ./psadmin

PSADMIN -- Tools Release: 8.52.02
Copyright (c) 1996, 2011, Oracle. All rights reserved.

--------------------------------
PeopleSoft Server Administration
--------------------------------

Config Home: /appl/psoft/hcm91fp1_dom

1) Application Server
2) Process Scheduler
3) Search Server
4) Web (PIA) Server
5) Switch Config Home
6) Replicate Config Home
q) Quit

Command to execute (1-6, q): 4

-----------------------------
PeopleSoft PIA Administration
-----------------------------

PIA Home: /appl/psoft/hcm91fp1_web

1) Administer a domain
2) Create a domain
3) Delete a domain

q) Quit

Command to execute: 2

---------------------------------------------
PeopleSoft PIA Administration - Create Domain
---------------------------------------------

PIA Home: /appl/psoft/hcm91fp1_web

1) Create a domain
2) Replicate a domain

q) Quit

Command to execute: 1

---------------------------------------------
PeopleSoft PIA Administration - Create Domain
---------------------------------------------

PIA Home: /appl/psoft/hcm91fp1_web

1) Domain name                  :[peoplesoft]
2) Web server                   :[weblogic]
3) Web server root directory    :[/opt/oracle]
4) Web server login id          :[system]
5) Web server password          :[Passw0rd]
6) Website name                 :[ps]
7) Application server           :[orion5.phoenix.nga]
8) JSL Port                     :[9000]
9) HTTP Port                    :[80]
10) HTTPS Port                   :[443]
11) Authentication Token Domain :[]
12) Web profile                  :[PROD]
13) Web profile user id          :[PTWEBSERVER]
14) Web profile password         :[PTWEBSERVER]
15) PeopleSoft reports directory :[/appl/psoft/hcm91fp1_web]

c) Create the domain as shown
q) Quit

Command to execute:

Note that some strange behavior, especially when changing the Web Profile, when enter 12 as command to execute, it switches to the next one instead of prompting, it means you have to enter “12” until reaching the expected web profile.
---------------------------------------
PeopleSoft PIA Administration - Create Domain
---------------------------------------------

PIA Home: /appl/psoft/hcm91fp1_web

1) Domain name                  :[peoplesoft]
2) Web server                   :[weblogic]
3) Web server root directory    :[/appl/mdlware/weblogic]
4) Web server login id          :[system]
5) Web server password          :[Passw0rd]
6) Website name                 :[hcm91fp1]
7) Application server           :[orion5.phoenix.nga]
8) JSL Port                     :[9000]
9) HTTP Port                    :[8000]
10) HTTPS Port                   :[8443]
11) Authentication Token Domain :[]
12) Web profile                  :[DEV]
13) Web profile user id          :[PTWEBSERVER]
14) Web profile password         :[PTWEBSERVER]
15) PeopleSoft reports directory :[/appl/psoft/hcm91fp1_web/reports/hcm91fp1]

c) Create the domain as shown
q) Quit

Command to execute: c

Creating the domain. This may take several minutes, please be patient.
..............................................................
The domain has been created

-----------------------------
PeopleSoft PIA Administration
-----------------------------

PIA Home: /appl/psoft/hcm91fp1_web

1) Administer a domain
2) Create a domain
3) Delete a domain

q) Quit

Command to execute: 1

------------------------------------------------------
PeopleSoft PIA Domain Administration - Choose a Domain
------------------------------------------------------

1) peoplesoft

q) Quit

Command to execute: 1

------------------------------------
PeopleSoft PIA Domain Administration
------------------------------------

PIA Home: /appl/psoft/hcm91fp1_web
PIA Domain: peoplesoft

1) Boot this domain
2) Shutdown this domain
3) Get the status of this domain
4) Configure this domain
5) Edit configuration files
6) View log files
7) Administer a site
8) Delete a site

q) Quit

Command to execute: 1

Starting the domain.....
Server state changed to STARTING..............
Server state changed to STANDBY.
Server state changed to STARTING.............
Server state changed to ADMIN.
Server state changed to RESUMING.
Server state changed to RUNNING.
Verifying domain status......
The domain has started.

Now, I’m a bit struggled with the variable PIA_HOME, it appears not working afterwards until and unless I set PS_CFG_HOME=$PIA_HOME. Or maybe I did not understood very well that variable usage.
Anyway, with command line everything become much simpler than ever to start the entire street :
[ptools852@orion5 ~]$ cd $PS_HOME/appserv
[ptools852@orion5 appserv]$ env|grep PIA_HOME
PIA_HOME=/appl/psoft/hcm91fp1_web
[ptools852@orion5 appserv]$ env|grep PS_CFG_HOME
PS_CFG_HOME=/appl/psoft/hcm91fp1_dom
[ptools852@orion5 appserv]$ ./psadmin -c boot -d hcm91fp1
Attempting to boot bulletin board...
tmadmin - Copyright (c) 2007-2008 Oracle.
Portions * Copyright 1986-1997 RSA Data Security, Inc.
All Rights Reserved.
Distributed under license by Oracle.
Tuxedo is a registered trademark.
No bulletin board exists. Entering boot mode.

> INFO: Oracle Tuxedo, Version 10.3.0.0, 64-bit, Patch Level 071

Booting admin processes ...

exec BBL -A :
process id=24244 ... Started.
1 process started.
Attaching to active bulletin board.

> Attempting to boot ...
INFO: Oracle Tuxedo, Version 10.3.0.0, 64-bit, Patch Level 071

Booting server processes ...

exec PSWATCHSRV -o ./LOGS/stdout -e ./LOGS/stderr -A -- -ID 200223 -D hcm91fp1 -S PSWATCHSRV :
        process id=24248 ... Started.
exec PSAPPSRV -o ./LOGS/stdout -e ./LOGS/stderr -s@psappsrv.lst -- -D hcm91fp1 -S PSAPPSRV :
        process id=24249 ... Started.
<…snipped…>
exec JSL -o ./LOGS/stdout -e ./LOGS/stderr -A -- -n //orion5.phoenix.nga:9000 -m 9 -M 12 -I 5 -j ANY -x 40 -S 10 -c 1000000 -w JSH :
        process id=24374 ... Started.
exec JREPSVR -o ./LOGS/stdout -e ./LOGS/stderr -A -- -W -P /appl/psoft/hcm91fp1_dom/appserv/hcm91fp1/jrepository :
        process id=24384 ... Started.
15 processes started.
[ptools852@orion5 appserv]$ ./psadmin -p start -d hcm91fp1
Attempting to boot bulletin board...
tmadmin - Copyright (c) 2007-2008 Oracle.
Portions * Copyright 1986-1997 RSA Data Security, Inc.
All Rights Reserved.
Distributed under license by Oracle.
Tuxedo is a registered trademark.
No bulletin board exists. Entering boot mode.

> INFO: Oracle Tuxedo, Version 10.3.0.0, 64-bit, Patch Level 071

Booting admin processes ...

exec BBL -A :
process id=24391 ... Started.
1 process started.
Attaching to active bulletin board.

> Attempting to boot ...
INFO: Oracle Tuxedo, Version 10.3.0.0, 64-bit, Patch Level 071

Booting server processes ...

exec PSMSTPRC -o ./LOGS/stdout -e ./LOGS/stderr -A -- -CD hcm91fp1 -PS PSUNX -A start -S PSMSTPRC :
        process id=24410 ... Started.
exec PSAESRV -o ./LOGS/stdout -e ./LOGS/stderr -- -CD hcm91fp1 -S PSAESRV :
        process id=24419 ... Started.
<…snipped…>
exec PSMONITORSRV -o ./LOGS/stdout -e ./LOGS/stderr -A -- -ID 88726 -PS PSUNX -S PSMONITORSRV :
        process id=24473 ... Started.
8 processes started.
[ptools852@orion5 appserv]$ ./psadmin -w start -d peoplesoft
Domain Not Found: peoplesoft
[ptools852@orion5 appserv]$ export PS_CFG_HOME=$PIA_HOME
[ptools852@orion5 appserv]$ ./psadmin -w start -d peoplesoft

Starting the domain........
Server state changed to STARTING...........
Server state changed to STANDBY.
Server state changed to STARTING........
Server state changed to ADMIN.
Server state changed to RESUMING.
Server state changed to RUNNING.
Verifying domain status......
The domain has started.

[ptools852@orion5 appserv]$

Same behavior when using the interactive menu of psadmin, once the webserver is created as I showed above, it does not take it in account anymore :
[root@orion5 ~]# su - ptools852
[ptools852@orion5 ~]$ cd $PS_HOME/appserv
[ptools852@orion5 appserv]$ env|grep PIA_HOME
PIA_HOME=/appl/psoft/hcm91fp1_web
[ptools852@orion5 appserv]$ env|grep PS_CFG_HOME
PS_CFG_HOME=/appl/psoft/hcm91fp1_dom
[ptools852@orion5 appserv]$ ./psadmin

PSADMIN -- Tools Release: 8.52.02
Copyright (c) 1996, 2011, Oracle. All rights reserved.

--------------------------------
PeopleSoft Server Administration
--------------------------------

Config Home: /appl/psoft/hcm91fp1_dom

1) Application Server
2) Process Scheduler
3) Search Server
4) Web (PIA) Server
5) Switch Config Home
6) Replicate Config Home
q) Quit

Command to execute (1-6, q): 4

-----------------------------
PeopleSoft PIA Administration
-----------------------------

PIA Home: /appl/psoft/hcm91fp1_dom <—here it is not my predefined $PIA_HOME

1) Administer a domain
2) Create a domain
3) Delete a domain

q) Quit

Command to execute:

Well, from the Peoplebooks, we can read “If you have the PIA_HOME environment variable set, this overrides the use of PS_CFG_HOME for PIA installations.”, that’s fine, it worked as I showed above for install, but does it mean it won’t override PS_CFG_HOME afterwards ? Or preferably, you change PS_CFG_HOME on-line, or before running psadmin to the desired PIA_HOME.

Nicolas.

Peopletools 8.52 : psadmin

2011-11-01T18:13:00.001+01:00

There are few interesting changes in the Peopletools 8.52 psadmin menu :
PeopleSoft Server Administration
--------------------------------

Config Home: /appl/psoft/hcm91fp1_dom

1) Application Server
2) Process Scheduler
3) Search Server
4) Web (PIA) Server
5) Switch Config Home
6) Replicate Config Home
q) Quit

Option 4 and 5 have been added compared to the previous Peopletools version.
The option 5 is rather good, be able to change the PS_CFG_HOME on-line without exiting from the program. Managing different home is now greatly simplified :
Command to execute (1-6, q): 5

Please provide new Config Home location or q to quit:

The option 4, managing the PIA within the psadmin is useful if and only if the webserver is hosted on the same server.
[ptools852@orion5 appserv]$ ./psadmin

PSADMIN -- Tools Release: 8.52.02
Copyright (c) 1996, 2011, Oracle. All rights reserved.

--------------------------------
PeopleSoft Server Administration
--------------------------------

Config Home: /appl/psoft/hcm91fp1_dom

1) Application Server
2) Process Scheduler
3) Search Server
4) Web (PIA) Server
5) Switch Config Home
6) Replicate Config Home
q) Quit

Command to execute (1-6, q): 4

-----------------------------
PeopleSoft PIA Administration
-----------------------------

PIA Home: /appl/psoft/hcm91fp1_web

1) Administer a domain
2) Create a domain
3) Delete a domain

Here we can see the output of the PIA_HOME variable, if it is not set in the environment, it is set by default to PS_CFG_HOME (Config Home).
Well, I’m not sure how to quantify the customer having such configuration (Peopletools installed onto the webserver), but as far as I know from the shops I worked for, that’s rather rare. Anyway, I’ll test this option in a coming blog entry.

There’s also some new options in the psadmin command line, PIA management, delete an application domain, find out more within the command “psadmin –help”.
Find out more in the OTN hosted Peoplebooks : http://download.oracle.com/docs/cd/E25688_01/pt852pbr0/eng/psbooks/tsvt/book.htm?File=tsvt/htm/tsvt06.htm#H2001

Now, building a new environment for Peopletools 8.52 on Oracle Linux 6.1 (well, it is not certified yet, but looks to work like a charm), create a new application domain can return the following error :
----------------------------------------------
Quick-configure menu -- domain: hcm91fp1
----------------------------------------------
      Features                      Settings
     ==========                    ==========
1) Pub/Sub Servers   : No    16) DBNAME     :[hcm91fp1]
2) Quick Server      : No    17) DBTYPE     :[ORACLE]
3) Query Servers     : No    18) UserId     :[PS]
4) Jolt              : Yes   19) UserPswd   :[PS]
5) Jolt Relay        : No    20) DomainID   :[hcm91fp1]
6) WSL               : No    21) AddToPATH :[.]
7) PC Debugger       : No    22) ConnectID :[people]
8) Event Notification: No    23) ConnectPswd:[peop1e]
9) MCF Servers       : No    24) ServerName :[]
10) Perf Collator     : No    25) WSL Port   :[7000]
11) Analytic Servers : No    26) JSL Port   :[9000]
12) Domains Gateway   : No    27) JRAD Port :[9100]

Actions
=========
13) Load config as shown
14) Custom configuration
15) Edit environment settings
h) Help for this menu
q) Return to previous menu

Enter selection (1-27, h, or q): 13
Performing load prechecks ...
/appl/psoft/ptools852/bin/ubbgen: error while loading shared libraries: libtux.so: cannot open shared object file: No such file or directory

==============ERROR!================
UBBGEN encountered an error while configuring!

==============ERROR!================

It is nothing but LD_LIBRARY_PATH not set. Adding it in the .bash_profile as below :
[ptools852@orion5 ~]$ more .bash_profile
# .bash_profile

# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi

# User specific environment and startup programs

PATH=$PATH:$HOME/bin

export PATH

TUXDIR=/appl/mdlware/tuxedo; export TUXDIR
ORACLE_BASE=/appl/oracle; export ORACLE_BASE
ORACLE_HOME=$ORACLE_BASE/product/11.2.0; export ORACLE_HOME
ORACLE_BIN=$ORACLE_HOME/bin

PS_HOME=/appl/psoft/ptools852; export PS_HOME
PS_CFG_HOME=/appl/psoft/hcm91fp1_dom; export PS_CFG_HOME
PIA_HOME=/appl/psoft/hcm91fp1_web; export PIA_HOME

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib:$TUXDIR/lib; export LD_LIBRARY_PATH

PATH=$TUXDIR/bin:$ORACLE_BASE:$ORACLE_HOME:$ORACLE_BIN:$PATH

. $PS_HOME/psconfig.sh
[ptools852@orion5 ~]$

Now, disconnect, reconnect and rerun the configuration menu, it should work :
----------------------------------------------
Quick-configure menu -- domain: hcm91fp1
----------------------------------------------
      Features                      Settings
     ==========                    ==========
1) Pub/Sub Servers   : No    16) DBNAME     :[hcm91fp1]
2) Quick Server      : No    17) DBTYPE     :[ORACLE]
3) Query Servers     : No    18) UserId     :[PS]
4) Jolt              : Yes   19) UserPswd   :[PS]
5) Jolt Relay        : No    20) DomainID   :[hcm91fp1]
6) WSL               : No    21) AddToPATH :[.]
7) PC Debugger       : No    22) ConnectID :[people]
8) Event Notification: No    23) ConnectPswd:[peop1e]
9) MCF Servers       : No    24) ServerName :[]
10) Perf Collator     : No    25) WSL Port   :[7000]
11) Analytic Servers : No    26) JSL Port   :[9000]
12) Domains Gateway   : No    27) JRAD Port :[9100]

Actions
=========
13) Load config as shown
14) Custom configuration
15) Edit environment settings
h) Help for this menu
q) Return to previous menu

Enter selection (1-27, h, or q): 13
Performing load prechecks ...
Loading validation table...
setting DBName=hcm91fp1
setting DBType=ORACLE
setting UserId=PS
setting UserPswd=PS
setting ConnectId=people
setting ConnectPswd=peop1e
setting ServerName=
setting Port=7000
setting Port=9000
setting Listener Port=9100
setting Domain ID=hcm91fp1
setting Add to PATH=.
New CFG file written with modified Startup parameters

Log Directory entry not found in configuration file.
Setting Log Directory to the default... [PS_SERVDIR/LOGS]
Spawning disabled for server PSAPPSRV.
Configuration file successfully created.
CFG setting changes completed
Loading configuration...
Domain configuration complete.

Nothing new here, it has always been like that on Linux, but that’s always good to remind it.

As an other side note, creating a new process scheduler domain, you also may encounter the following warning (I don’t like warning, they sound like repeating error !) :
WARNING: PSDSTSRV is configured with Min instance set to 1. To avoid loss of service, configure Min instance to atleast 2.
Rather strange to have this when creating a default prcs, better to change it now, modify the configuration file $PS_CFG_HOME/appserv/prcs/hcm91fp1/psprcs.cfg and reload.

Nicolas.

Peopletools 8.52 client installation

2011-10-31T22:35:00.001+01:00

Peopletools 8.52 is shipped with a client binaries installer. That’s new, but what is it exactly ? Well, it is the bare-minimum you need to work on a Peoplesoft database instance. That’s rather good if you have developers around, they probably do not need the entire installation on their own workstation. For those who know the Peoplesoft OVM template, there was something similar in the latest one with the zipfile toolsclient.zip, please see here.
It is a much lighter installer, about 500Mb, from http://edelivery.oracle.com, select product pack “PeopleSoft Enterprise”, choose a platform (it does not actually matter which one), and click on “PeopleSoft PeopleTools 8.52 Media Pack”. Download “PeopleSoft PeopleTools 8.52 Client Only”, part V27722-01.
Note that the client is only for Windows plateform.
After unzipping, let’s go for the client install (here below on Windows 2008) :

The license code is the same for the “standard” Peopletools install :

Usually, the Non-Unicode/Unicode type is for the data we are loading into the database, since it won’t install any of the loading scripts and data files, I’m wondering why the question is there and what it does exactly, but keep consistency with you whole environment:

Choose a directory to install into :

Here also I’m not sure to understand why the PSEMHUB is there, it is used by the PSEMAgent, but you probably don’t want to manage remotely the client installation, but again, here we go :

In the process above, that’s interesting to note the installer never prompt for the Oracle binaries (%ORACLE_HOME%\bin) like it is for the server Peopletools installation on Windows.

The client can also be patch with the latest Peopletools patch, since the patch 8.52.02 is already available, let’s apply it on that client. So far, there’s no patch dedicated to the client only installation, so the patch is twice bigger than the client installer… :

Here you decide what kind of installation you are doing. However, I’m not sure what will happen if you choose to patch a client and here below check “Full Install”. Is your client become a server ? It probably has to be tested. Let’s have a client only patch install :

In the end of the process, here are the different folders present in the client home :

It’s really a light install, no script, no data. Should you load a database, do not use that installation, go for a full (or server) installation instead.
But that’s still good to have for developers’ local workstation installation.
***
You may receive the following error when launching AppDesigner and DataMover (“the application has failed to start because its side-by-side configuration is incorrect”) :

In that case, run from the client home, \setup\psvccrt\psvccrt_retail.msi, and follow the instruction :

It should solve the problem, and you will be able to run AppDesigner and DataMover from now.

Last but not least, it is not certified on Windows XP, I tried it though. “Not certified” has never meant “not working”, so, whether the installer Disk1\setup.bat seems hanging forever, the exe file under “Disk1\InstData\setup.exe” run fine and Peopletools 8.52 is installing successfully on my Windows XP SP3 Pro workstation.

Nicolas.

Peopletools patch 8.52.02 unzipping issue

2011-10-29T15:33:00.001+02:00

Peoplesoft delivered the patch 02 of Peopletools 8.52. As usual, the patch is zipped and password protected. But that time, the password contains a “very” special character, I named exclamation mark (!).

Unzipping a file within a password on Unix/Linux is quite simple :
unzip –P password zipfile.zip

Now the given instruction is something like this :
unzip –P "pass!word" zipfile.zip
The double-quotes should make the command successful in most of the cases even with special characters.

But because of the exclamation mark, it won’t work. The following error is returned :
-bash: !word": event not found

I won’t give the password here (password is available on My Oracle Support only – paid support required), but just a workaround to get the patch unzipped. The instruction should be :
unzip -P "pass"'!'"word" zipfile.zip
Note the double-quote and simple-quote around the exclamation mark.

Probably that exception has been forgotten by Oracle people when building the zip file or when writing the documentation shipped with the patch.

Hope that helps,

Nicolas.

Peopletools 8.52 is released !

2011-10-28T16:18:00.000+02:00

Two weeks ago, I wrote a blog entry about Peopletools 8.52 to get the infrastructure ready. Now it is done, Peopletools 8.52 is here, it has been released !
Available on edelivery, it is 3 disks (rather funny the 3rd is only 18M).
As previously announced no more WebSphere and COBOL software shipped within the Peopletools bundle.
A good surprise, a Windows client dedicated installer (Windows Client only - 598M, could make life easier on workstation).
~~Unless it is still too early, I did not see the traditional first patch on~~ ~~ftp://ftp.peoplesoft.com/outgoing/ptools~~ ~~for the corresponding release (on My Oracle Support neither), to be tracked.~~
As far as I read the Installation Documentation (available on edelivery), the installation itself does not change that much, I'll write a blog entry as soon as I'll done with one install. However, there's a really big change with the PSADMIN menu, it is worth to try !

Last but not least, so far none of the applications have been recut yet with the new Peopletools version, so be careful and do not forget to manage a Peopletools upgrade of your newly application installation within that Peopletools 8.52.

To be continued with the install,

Nicolas.

NB (28/10/2011 18:44 CET) : I was probably far too optimistic on patch, the “first” patch is now available, but not as 8.52.01, rather odd, but that’s 8.52.02, see ftp://ftp.peoplesoft.com/outgoing/ptools/85202/
NB (29/10/2011) : and here the announcement http://blogs.oracle.com/peopletools/entry/peopletools_8_52_is_generally

OEM 12c

2011-10-20T17:36:00.001+02:00

A new version of Oracle Enterprise Manager has been released sometime ago, the 12c !
The first thing I can say is regarding the Installer, it now includes all the requisites (well, except database). Weblogic is installed at the same time, no need anymore to look for it, which version, which patch as it was on previous version 11gr1.
The installation can really take a while depending of the network, but in the end it’s really nice :

What a change compared to all the previous version ! And changes do not stop on the login page, it is rather disturbing to get all the new habits, but that’s just a matter of time…
Home page :

And here the databases list :

I don’t know yet how heavy it is in terms of resources on the server, but looks really nice.
Few things though :
1. no Peoplesoft plugin yet for that version
2. OEM12c Server Manager is only certified within Agent 12c… hopefully all your databases are running on OS which support it.
3. Surprising (for me), it is not yet certified on Linux 6.x

Enjoy it,

Nicolas.

Oracle 11.2.0.3 patchset

2011-10-20T17:35:00.001+02:00

Sometime ago has been released the latest patchset, 11.2.0.3 (so far Linux only). Whether it is still not certified on Oracle Linux 6.x, it is working working fine.
Working in the same environment as I previously created here, Oracle Linux 6.0 and Oracle database 11.2.0.2, I’m doing an out-of-place upgrade.
The installer is complaining about missing RPMs…

Installing the corresponding RPMs (and remove pdksh if already installed, replaced by ksh) :

[root@orion4:/mnt]# mount /dev/cdrom /mnt/cdrom
mount: block device /dev/sr0 is write-protected, mounting read-only
[root@orion4:/mnt]# cd /mnt/cdrom/
[root@orion4:/mnt/cdrom]# cd Packages/
[root@orion4:/mnt/cdrom/Packages]# rpm -Uvh compat-libcap1-1.10-1.x86_64.rpm
warning: compat-libcap1-1.10-1.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID ec551f03: NOKEY
Preparing...                ########################################### [100%]
   1:compat-libcap1         ########################################### [100%]
[root@orion4:/mnt/cdrom/Packages]# rpm -Uvh ksh-20100621-2.el6.x86_64.rpm
warning: ksh-20100621-2.el6.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID ec551f03: NOKEY
error: Failed dependencies:
        pdksh conflicts with ksh-20100621-2.el6.x86_64
[root@orion4:/mnt/cdrom/Packages]# rpm -e pdksh
[root@orion4:/mnt/cdrom/Packages]# rpm -Uvh ksh-20100621-2.el6.x86_64.rpm
warning: ksh-20100621-2.el6.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID ec551f03: NOKEY
Preparing...                ########################################### [100%]
   1:ksh                    ########################################### [100%]
[root@orion4:/mnt/cdrom/Packages]#
[root@orion4:/mnt/cdrom/Packages]# cd /
[root@orion4:/]# umount /dev/cdrom
[root@orion4:/]#
Then check again and it’s going smoothly :

…

After changing the ORACLE_HOME setting of oracle user (OS user), upgrading the database successfully as well :

You can see the new features coming within this patchset in the on-line documentation.

Enjoy,

Nicolas.

Peopletools 8.52 : get your infrastructure ready

2011-10-13T22:20:00.001+02:00

It has been discussed several times during the last Oracle Open World 2-6 oct. 2011, Peopletools 8.52 is just next to the door. It seems this version will change a lot of things, see the pre-release notes #1335812.1 and the value proposition #1327656.1.
But in order to be able to run this Peopletools 8.52 version, the infrastructure needs to be up to dated. There’re indeed a couples of changes and decommissioned platforms on server as well as client side which may imply some work in front.
Starting by the client :
Up to Peopletools 8.51, Windows XP Pro (32bit) was certified and worked fine as a client for AppDesigner for developers. It is now ended. Not sure if it will work, but it is not planned to be certified. I know, Windows XP is quite an old OS, but still widely used. Client must be now on Windows 7, Vista (who really wants it by now ?), or Windows 2008 (honestly, I don’t know many workstation on that version). Keep in mind to verify the edition.
Speaking on client side, browsing is also changing a lot, a very new nice one, Apple iPad (browser Safari) will be certified ! And finally, Peoplesoft is introducing certification of Google Chrome.
On server side :
OS: HP-UX PA-RISC certification is now definitely ended, AIX 5.3 is also ended (7.1 added).
Surprisingly, Oracle Linux 6.x is not planned to be certified (right, Oracle database is not certified yet on this Linux version), but I tend to think it will be certified soon too.
Database : Oracle 11.2.0.2, 11.1.0.7 and 10.2.0.5 (10.2.0.4 and earlier is ended), probably the newly released 11.2.0.3 patchset will also be certified soon (not planned yet).
Applications : they must be 8.9 or above, whereas Peopletools 8.51 was certified from within applications 8.8.
WebSphere : keep in mind, that within Peopletools 8.52, WebSphere won’t be provide anymore, support must be obtained from IBM to get the software.
COBOL compiler : similarly to the above, Peopletools 8.52 won’t come anymore with a compiler, support must be obtained from the vendor (not only Microfocus, but also IBM).
Regarding these last two points, please read this roadmap.

Except that Peopletools 8.50 was certified on x64 architecture only, I don’t think there were so many changes on the previous 8.5x versions.
So, if you want the coming soon Peopletools 8.52 and are in one of the ended certifications as describe above, prepare your infrastructure for a change. Or if that’s for demo, proof of concept and/or training purpose, you can always wait for the associated Oracle VM Peoplesoft templates (well, that supposes you have a spare server in a corner for hosting Oracle VM… that’s an other story), but not sure how long it will take to be available.
All these changes could be quite problematic if you have to deal with much older Peopletools release and Application version… which require different OS on server but also on client side (Peopletools 8.48 and earlier are not certified on Windows 7).

Administration tasks :
Few administration tasks may also change.
New variable : this could have an impact on your architecture as well, in Peopletools 8.50 has been introduced a new environment variable, PS_CFG_HOME to decouple the application/batch domain from the PS_HOME. A new one is coming within Peopletools 8.52 to separate the application installation home from the Peopletools installation home, PS_APP_HOME. It often confused new-comers in Peoplesoft world, why the application must be installed in the same folder as the Peopletools, now it is finished, we could install application where ever we want using that variable, and have multiple applications pointing to a unique Peopletools home directory.
PSADMIN menu : new options to manage the PIA such as create, clone, delete, check status…
Active DataGuard : I hope also Peoplesoft be more integrated within Active Data Guard, as I showed in an earlier blog entry there’s no Crystal, COBOL and SQR on a standby database supported. But I’m quite disappointed, it does not appear to be in the pre-release notes linked above.

This Peopletools 8.52 will change a lot of things, here was a non-exhaustive list on admin side, but there’s much more.
I’m really looking forward that new version.

Enjoy,

Nicolas.

PS: please note that this blog entry is based on “pre-release” notes and current certification matrix as of today – 13-OCT-2011, so it may change…

Application server load balancing and failover

2011-09-30T00:03:00.001+02:00

In a previous blog’s entry, I explained about Multiple application messaging servers on Peopletools 8.51 and facilities for load balance and failover on messaging domain server.
In a very similar way, the application server can also be used in load balance and failover configuration.
First of all, you need at least two applications servers, please note that if you are on the same server, then domain name and JSL (jolt) port should be different from each other. Of course, there are not many advantages to have this configuration if working on one and only one server, but rather good to have different server, if one crash, the other one takes place.
Here we go.
First application server :

And the second one :

Please, note that whether I name one “first” and the other one “second”, there is no precedence of one compared to the other by default (except if you define a weight in configuration.properties, but let’s leave it for later explanation).
Then starting each application server

Note that the number of listened ports regarding Jolt is defined is the psappsrv.cfg of the domain as following :
[JOLT Listener]
;=========================================================================
; Settings for JOLT Listener
;=========================================================================
Address=%PS_MACH%
Port=9000
Encryption=0
Min Handlers=5
Max Handlers=7
In the current case, the ports between 9000 and 9005 will be immediately in use after started :
[psadm2@psovmfscmfp1 APPDOM]$ netstat -an|grep 900
tcp        0      0 192.168.1.150:9000          0.0.0.0:*                   LISTEN
tcp        0      0 192.168.1.150:9001          0.0.0.0:*                   LISTEN
tcp        0      0 192.168.1.150:9002          0.0.0.0:*                   LISTEN
tcp        0      0 192.168.1.150:9003          0.0.0.0:*                   LISTEN
tcp        0      0 192.168.1.150:9004          0.0.0.0:*                   LISTEN
tcp        0      0 192.168.1.150:9005          0.0.0.0:*                   LISTEN
[psadm2@psovmfscmfp1 APPDOM]$
It means the second domain needs to be configured with a port above 9005.

Here’s the output from the database side, since my two apps are on the same machine, there’s nothing really useful so far, cannot distinguished which domain a database session is coming from :
SQL> select username,program, client_info from v$session where username = 'SYSADM'
SQL> /

USERNAME                       PROGRAM                                          CLIENT_INFO
------------------------------ ------------------------------------------------ ----------------------------------------------------------------
SYSADM                         PSSUBDSP@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSSUBDSP,
SYSADM                         PSSUBHND@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSSUBHND,
SYSADM                         PSPUBDSP@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSPUBDSP,
SYSADM                         PSBRKDSP@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSBRKDSP,
SYSADM                         PSPUBHND@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSPUBHND,
SYSADM                         PSBRKHND@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSBRKHND,
SYSADM                         PSSAMSRV@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSSAMSRV,
SYSADM                         PSQRYSRV@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSQRYSRV,
SYSADM                         PSAPPSRV@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSAPPSRV,
SYSADM                         PSAPPSRV@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSAPPSRV,
SYSADM                         PSMONITORSRV@psovmfscmfp1.phoenix.nga (TNS V1-V3 VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSMONITORSRV,
SYSADM                         PSSUBDSP@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSSUBDSP,
SYSADM                         PSSUBHND@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSSUBHND,
SYSADM                         PSPUBDSP@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSPUBDSP,
SYSADM                         PSPUBHND@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSPUBHND,
SYSADM                         PSBRKDSP@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSBRKDSP,
SYSADM                         PSMONITORSRV@psovmfscmfp1.phoenix.nga (TNS V1-V3 VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSMONITORSRV,
SYSADM                         PSBRKHND@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSBRKHND,
SYSADM                         PSAPPSRV@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSAPPSRV,
SYSADM                         PSSAMSRV@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSSAMSRV,
SYSADM                         PSAPPSRV@psovmfscmfp1.phoenix.nga (TNS V1-V3)    VP1,psadm2,psovmfscmfp1.phoenix.nga,,PSAPPSRV,

21 rows selected.

Now, webserver configuration to be done in configuration.properties file ($PS_HOME/webserv/peoplesoft//applications/peoplesoft/PORTAL.war/WEB-INF/psftdocs/ps).
This is a easy configuration, put the application servers separated by simple comma as following :
[psadm2@psovmfscmfp1 peoplesoft]$ more ./applications/peoplesoft/PORTAL.war/WEB-INF/psftdocs/ps/configuration.properties
<<...snipped...>>
# psserver must point to your application server machine name (recommended) or IP address
# and JOLT port. The PeopleTools release of the application server must match the PeopleTools
# release of the PeopleSoft files on the web server.
#
# To enable jolt failover and load balancing, provide a list of application server
# domains in the format of; psserver=AppSrvr:JSLport,...
# For example: psserver=SERVER1:9000,SERVER2:9010,SERVER3:9020
## sd="Application Server Connect String", ld="This string embodies the failover and load balancing string for PIA to connect to Application Server domains. Consult the PeopleB
ooks recommendations on load balancing and failover for more information. The format is psserver=AppSrvr:JSLport where AppSrvr is your fully qualified domain name. Multiple d
omains should be comma separated", tip="Format: psserver=AppSrvr:JSLport where AppSrvr is your fully qualified domain name, e.g psserver=SERVER1.oracle.com:9000,SERVER2.oracle.
com:9010"
psserver=psovmfscmfp1:9000,psovmfscmfp1:9010
## sd="Jolt Pooling", dt="c", ld="Enable Jolt Pooling"
joltPooling=true
<<...snipped...>>
Configured as above, all the application servers have the same weight (the same priority) in the round-robin algorithm. This algorithm affect ingoing transaction randomly to one or the other configured application server, there’s no priority, no load checkup, no network checkup, it’s just random (find out more in the My Oracle Support note E-WS: Load Balancing Options for Web Server and Application Server [ID 618367.1]).
But we could also introduced weight (from 1 to 10) on application server to make one precedence on the other as following :
psserver=psovmfscmfp1:9000#10,psovmfscmfp1:9010#1
In that case, the first server can takes extra work for an heavy load compared to the second one.

Not only the load balance will be set, but the failover as well.

After the first connection to the front end application, we can check the client status of both application servers :

We can see a first pool as been instantiated.
Since round-robin algorithm is randomly given connection to the application server, it’s not always easy to show when alone, furthermore, the pool connection are making it even less simple.
But you probably can check it from the back end :
SQL> select username,program, client_info from v$session where username = 'SYSADM'
2* order by 2
SQL> /

3 months update later, finally

2011-09-19T22:45:00.001+02:00

I did not maintained this blog for quite a while during this last quarter, I should apology to the readers.
What happened during that time ? “Finally” is probably the word to keep in mind for that period.

CentOS 6.0
In July, CentOS finally released the version 6.0. It has been a very long waiting and many people moved away for an other (equivalent) distribution, I named Scientific Linux (see below). I do not know if the CentOS dev. team made the rights choice to go for the version 6.0 before the update 5.7, but truly enough, no update at all for several months is quite unusual and rather disappointed even though that’s a free distribution.
I did not tested this version yet, but according to my reading across a couple of article on Internet, it could have been done much better especially after that long (long) waiting.
Now, we may have to wait for the update 6.1 which has been promised very soon, still have to define “soon”.

CentOS 5.7
Few days ago, earlier in Sept., we also get that update I was looking for several months too. Much appreciated, the upgrade from 5.6 went smoothly, as usual. The only thing for that one was the delay since the RHEL 5.7 date release. Again, a lot of debates on that…

Oracle Linux 6.1
Of course, this is also free (the use, not the support), but developed by a company, a big company, so the time to get the new version is quite different compared to CentOS.
Oracle Linux is available since the 1st of June, 5.7 since August.

Scientific Linux 6.1 and 5.7
An other free distribution of a RHEL recut, Scientific Linux interest has considerably grown since CentOS took too much time for the newest release delivery.
Whether the update 5.7 has just been released, their update 6.1 is already out for a month. Some can argue the developers behind are also paid… still, this distribution has a good chance to see new customers.

Oracle VM 3.0 (August, the 23rd)
After several years of promises, Oracle has finally released a new version of their virtualization software, Oracle VM 3.0. A lot of new things has to be discovered, according to Oracle, it is much better than ever. But have they not too late compared the the concurrent like VMWare vSphere Hypervisor ?

Open World
On Oracle database and Peoplesoft sides, no major thingy, nothing unusual or non expected, the summer was rather quiet. So, no worries.
But the Oracle Open World is just in the corner by now. Probably we have to count on new Peopletools version 8.52 around that event, maybe new Peoplesoft OVM templates as well (?). Saying about Oracle Open World, this year I won’t attend. I hope attendees will report back on their blog about the exciting sessions.

Other
Above all, and most importantly my son is born also the 23rd of August, which explain the delay and absence of blog update a bit before and since then… but I’ll be back.
The only “problem” I have now, the room which was used to be my server room is occupied. I have to find new space for my noisy server and NAS. But that’s the part of the fun to have children !

Nicolas.

Multiple application messaging servers

2011-09-19T21:53:00.001+02:00

In a standard mode, when dealing within messaging, one domain is configured as followed, and most of the time it is enough :

However, if you have to deal with a high number of messages, to process a maximum number of messages, you may want to create multiple domains to handle those messages.
Let’s create a new one as below :

Then, coming back on the domain status’ page, we see that new domain :

We have to activate it to make this new domain processing messages. Change the status, and click “update” button :

Here we go. An error is raised, we cannot have more than one master domain. And being master is set by default for a given domain.

What is that ?
A master domain can be used to balance ingoing/outgoing messages between master and slave(s) domains. Particularly useful when dealing a very high number of messages in a short time.

We can handle it in two ways.

1. Static slave
In the configuration file appsrv.cfg, we can change a parameter value – Domain Slave Mode – from 0 to 1 to make the domain a slave domain.
Change from default value

To

Reload the application server domain, and coming back to the domain status’ page to make it active :

After updating the status, we can see the domain APPDOM2 activated and also that’s a slave domain. It is fixed, there’s no way to change but modify the configuration file manually and reload again the domain.
Without any failover set, it is probably the easiest way to achieve the goal : handle a high number of messages, you could make multiple slaves domains all managed by one and only master domain.
Using multiple slaves domains can also be useful, you could set a load balance in between all of them (click on “Master/Slave LoadBalance”) to configure all the priorities, such as following :

2. Dynamic slave
An other way for handling a high number of messages and multiple domains would be to make slave domain dynamic. It is maybe a little bit more tricky, but also probably more reliable and scalable.
A dynamic slave domain can become a master domain in case of failure of the current master domain. Really nice features if the messages have to be processed asap or with a minimum of down-time.
So, we return back to the original domain status’ page, the second domain APPDOM2 is inactive (it is not set as static slave in the configuration file):

Click on “SetUp Failover”, then check “enable Failover”, define a failover time (when the slave domain has to become master after original master failure, here 5 minutes) and most importantly check “Dynamic Slave Option”. Finally set a failover priority (1, 2, 3…) and save :

It makes that second domain defined as dynamic slave as shown above in the failover setting as well as below in the domain status page :

From now, we have two domains which proceed with the messages, given the fact that if the first one fails, the second will become the master.
Just to show it, here I stopped the first domain APPDOM, once the failover time is off (as shown earlier, 5 minutes), we can see the second domain APPDOM2 becoming master (it is not “dynamic slave” anymore), and the first obviously becoming inactive :

When the first domain APPDOM is restarted, it becomes the slave domain whereas the second domain APPDOM2 remains the master.

Making choice between static and dynamic slave domain may not be an easy task, it depends of your all architecture and requirements you have in messages processing. The first might be useful on not so big environment whereas the second is more than recommended on big environments (you don’t want to make dynamic domain on non-messages dedicated domain).

Enjoy,

Nicolas.

Find out more on OTN hosted Peoplebooks : http://download.oracle.com/docs/cd/E24150_01/pt851h2/eng/psbooks/tiba/book.htm?File=tiba/htm/tiba13.htm

AppServer does (not) reconnect to a bounced database

2011-06-13T22:08:00.001+02:00

Few weeks ago, I was facing some databases issues. Due to an unexpected overload on the server, the services were not responding, and a couple of scripts were configured to stop automatically the databases. Few minutes later, the scripts started again those databases, and everything went fine again (I won’t go in details of the reasons of overload and why scripts are bouncing the database, that’s not the subject here).
But one of these databases is a Peoplesoft database, having application server connections to it. The Peopletools version was 8.51.07, and unfortunately, was not able to reconnect automatically to the database once restarted. The front-end users were not able to connect anymore to the application until the application server is restarted, rather annoying.

I reproduce the case on the delivered PSOVM FSCM 9.1 FP1 Peopletools 8.51.07.
1. Connect to the front-end application, it is working fine
2. Stop the database, you are logged out from the front-end application

Note : click on link prompt the login page, logging out of the application send a strange error for the down status of the database (“Your User ID and/or Password are invalid”)

3. Start the database
4. Open a new browser, no connection possible, raising error “bea.jolt.ApplicationException: TPESVCFAIL – application level service failure”

5. Stop and start the application server
6. Open a new browser, new connections work fine again

There are two known bugs about it, one wrongly mentioned a fix within 8.51.08, the other one (#12358153) mentioned the patch 8.51.10.
Let’s have a try :
1. Install the patch 8.51.10 on top of the delivered PSOVM FSCM 9.1 FP1 Peopletools 8.51.07
2. Redeploy the PIA
3. Test the same scenario => now it is working, you can reconnect to the front-end application without bouncing the application server after a database stop and start. Good one.

So, that patch level 10 is probably the bare minimal to go in production with… even if a stop/start database is not expected.

Nicolas.

Peoplesoft OVM FSCM9.1 Feature Pack 1 Peopletools 8.51.07

2011-05-02T17:26:00.001+02:00

As promised, Peoplesoft team keeps the Peoplesoft OVM templates up-to-date. After The latest HCM 9.1 template based on Feature Pack 1 and Peopletools 8.51.02 (Dec-2010), last week has been released the second OVM template for FSCM (first was delivered earlier in Sept-2010).
This one is based on FSCM 9.1 Feature Pack 1 (up to Bundle #9/maintenance Pack #5) and Peopletools 8.51.07. Latest application version and Peopletools pach (well, the patch 08 has been released since then).

1. The database server
After importing the template, start the VM.
Do not use DHCP, but rather a static IP address :

Whatever you entered to start automatically the database, it won’t work (as documented in the readme file) :

As usual now in the PSOVM, CSS fails to start but it won’t harm anything later on :

For testing purpose, following up a previous post on an older PSOVM, I used a lower case database name.

If given a lower case database, you must update the table PS.PSDBOWNER, the deployment script are not doing it properly to make it upper :

And eventually, you’ll have your running database and listener (domain is .us.oracle.com) :

Note :
1. SYSADM’s password upper case :
[oracle@psovmfscmfp1db ~]$ sqlplus sysadm/sysadm

SQL*Plus: Release 11.1.0.7.0 - Production on Mon May 2 06:32:43 2011

ERROR:
ORA-01017: invalid username/password; logon denied

Enter user-name:
[oracle@psovmfscmfp1db ~]$ sqlplus sysadm/SYSADM

SQL*Plus: Release 11.1.0.7.0 - Production on Mon May 2 06:32:50 2011

Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
2. Installed language is English only :
SQL> select language_cd from pslanguages where installed=1;

LANGUAGE_CD
------------
ENG

3. Unlike the first PSOVMs released, there’s no issue with the profile :
SQL> conn / as sysdba
Connected.
SQL> select username,account_status,expiry_date,profile
from   dba_users
where username in ('PEOPLE','SYSADM') ;
2    3
USERNAME                       ACCOUNT_STATUS                   EXPIRY_DATE        PROFILE
------------------------------ -------------------------------- ------------------ ------------------------------
PEOPLE                         OPEN                                                DEFAULT
SYSADM                         OPEN                                                DEFAULT

SQL> l
1* select * from dba_profiles where profile='DEFAULT'
SQL> /

PROFILE                        RESOURCE_NAME                    RESOURCE_TYPE                    LIMIT
------------------------------ -------------------------------- -------------------------------- -----------------------------
DEFAULT                        PASSWORD_GRACE_TIME              PASSWORD                         UNLIMITED
DEFAULT                        PASSWORD_LOCK_TIME               PASSWORD                         UNLIMITED
DEFAULT                        PASSWORD_VERIFY_FUNCTION         PASSWORD                         NULL
DEFAULT                        PASSWORD_REUSE_MAX               PASSWORD                         UNLIMITED
DEFAULT                        PASSWORD_REUSE_TIME              PASSWORD                         UNLIMITED
DEFAULT                        PASSWORD_LIFE_TIME               PASSWORD                         UNLIMITED
DEFAULT                        FAILED_LOGIN_ATTEMPTS            PASSWORD                         UNLIMITED
DEFAULT                        PRIVATE_SGA                      KERNEL                           UNLIMITED
DEFAULT                        CONNECT_TIME                     KERNEL                           UNLIMITED
DEFAULT                        IDLE_TIME                        KERNEL                           UNLIMITED
DEFAULT                        LOGICAL_READS_PER_CALL           KERNEL                           UNLIMITED
DEFAULT                        LOGICAL_READS_PER_SESSION        KERNEL                           UNLIMITED
DEFAULT                        CPU_PER_CALL                     KERNEL                           UNLIMITED
DEFAULT                        CPU_PER_SESSION                  KERNEL                           UNLIMITED
DEFAULT                        SESSIONS_PER_USER                KERNEL                           UNLIMITED
DEFAULT                        COMPOSITE_LIMIT                  KERNEL                           UNLIMITED

16 rows selected.

2. The App/Batch/PIA server
After importing the template, start the VM.
Do not use DHCP, but rather a static IP address :

Once again, that works great.


3. Peopletools 8.51.07 zipped file for Windows client
[root@psovmfscmfp1 ~]# su - psadm2
cd [psadm2@psovmfscmfp1 ~]$ cd $PS_HOME
[psadm2@psovmfscmfp1 tools]$ ls
FSCM                        cblbin    log                     src
FSCM_InstallLog.log         class     peopletools.properties tmp
PSEMAgent                   data      psconfig.sh             toolsadmin.sh
PSEMViewer                  dict      scripts                 toolsclient.zip <--
PeopleTools_InstallLog.log etc       sdk                     utility
SecurityAddIns              fonts     secvault                verity
appserv                     jre       setup                   web
bin                         jre1.6.0 sqr                     webserv
[psadm2@psovmfscmfp1 tools]$ ls -lrt toolsclient.zip
-rwxr-xr-x 1 psadm1 oracle 61191937 Mar 23 21:57 toolsclient.zip
[psadm2@psovmfscmfp1 tools]$

Copy the file and unzip it onto your local desktop. In 2-tier, you’ll need an Oracle client, in 3-tier, no need Oracle client, but you’ll have to configure a WSL listener on the AppServer domain.
*******************************************************************************************************************************************************
NOTES :
1. The SELINUX errors/warnings I have reported a while ago here have been fixed.
2. The missing SETSPACE sqr I reported here has also been fixed.
3. The scripts under $PS_HOME/scripts I was requesting here have been added.
Nice to see they are listening and trying to keep these templates alive as much as possible.

PS: if for some reasons you need to mount a nfs point, that will work fine from the PSOVM database server but not from App/Batch/PIA server. You’ll need to install a couple of additional RPMs, please read more in the Peoplesoft OVM forum’s thread I created here.

Enjoy it,

Nicolas.

Application messaging troubleshooting : endless ping node

2011-04-14T19:05:00.001+02:00

It’s really common to use a small configuration for environments such as DEMO, SYS or even for development databases to avoid the server to be overloaded within useless processes. But doing so, you should be sure it is not set too small otherwise you could have some issues when setting the messaging up.
Here’s an example of a common issue a Peoplesoft DBA might be face to.
I’m working here on the PSOVM CRM 9.1 based on Peopletools 8.50.09. Of course, it is assuming the Pub/Sub service has been set to “Yes” as shown below:

Checking the local node for proper configuration (user and password must be set) :

So far, so good.
Now, let’s configure the gateway. For initial configuration, load the connector first :

And try to ping the gateway to confirm it works :

Now, let’s configure the node in the gateway :

Default user id is “administrator”, default password is “password”.

Now try to ping that new added node :

It will process endlessly until reaching the timeout.

Note that there’s no error messages in any log files, nothing to help.
Having a look into the configuration file, psappsrv.cfg, PSAPPSRV has only 1 min. instance :

Change it to a minimum of 2 :

Reconfigure and restart the application server :

Note there’s now 2 processes PSAPPSRV.

Coming back in the front end application, trying again to ping the local node within the gateway configuration as previously failed :

Few seconds later, it is successful :

So, when you want to work within the messaging, always set at least 2 as a minimum instances for PSAPPSRV process in the configuration file.

As a side note, if you fill a wrong Peopletools release as shown below, it will fail but that time with a clear explanation (Integration Gateway: PeopleSoftTargetConnector - invalid PeopleTools release). So, be sure about the correctness of the release until the patch level :

Nicolas.

Peoplesoft PIA silent deployment

2011-04-10T11:23:00.001+02:00

Whether the silent Weblogic installation is documented in the Peopletools Installation Guide (Task 2-1-5: Installing Oracle WebLogic on Linux or UNIX in Silent Mode), the silent PIA deployment is not. Is that because it does not exists ? Is that because there’s no use of that ? Well, it exists and in few cases it can help. Especially if you are applying Peopletools patch on regular basis. As you may know, it is most often required to redeploy the domain.

Last month I replied to a resurrected thread on Peoplesoft OTN Forum regarding a silent deployment of the PIA. I was initially – last year - thinking that was not possible. But working a lot with the PSOVM since then, I saw the PIA deployment on “fly” during the OVM template installation.

Going through the PSOVM App/Batch/PIA server once deployed, there’s a script which is called to deploy the PIA : /opt/oracle/psft/vm/installpia.sh
The script is relatively easy to understand :
PT_HOME=/opt/oracle/psft/pt TOOLS_HOME=$PT_HOME/tools BEA_HOME=$PT_HOME/bea SILENT_INSTALL_FILE=install.properties echo "Doing PIA silent install" if [ ! -d $TOOLS_HOME/tmp ]; then mkdir $TOOLS_HOME/tmp fi cd $TOOLS_HOME/tmp # If there is a pre-existing silent response file we # remove it if [ -f $SILENT_INSTALL_FILE ]; then rm -f $SILENT_INSTALL_FILE fi echo PS_HOME=$TOOLS_HOME >> $SILENT_INSTALL_FILE echo DOMAIN_NAME=peoplesoft >> $SILENT_INSTALL_FILE echo SERVER_TYPE=weblogic >> $SILENT_INSTALL_FILE echo BEA_HOME=$BEA_HOME >> $SILENT_INSTALL_FILE echo USER_ID=system >> $SILENT_INSTALL_FILE echo USER_PWD=password >> $SILENT_INSTALL_FILE echo INSTALL_ACTION=CREATE_NEW_DOMAIN >> $SILENT_INSTALL_FILE echo DOMAIN_TYPE=NEW_DOMAIN >> $SILENT_INSTALL_FILE echo INSTALL_TYPE=SINGLE_SERVER_INSTALLATION >> $SILENT_INSTALL_FILE echo WEBSITE_NAME=$PIA_SITENAME >> $SILENT_INSTALL_FILE echo APPSERVER_NAME=localhost >> $SILENT_INSTALL_FILE echo JSL_PORT=$JOLT_PORT >> $SILENT_INSTALL_FILE echo HTTP_PORT=$PIA_HTTP_PORT >> $SILENT_INSTALL_FILE echo HTTPS_PORT=$PIA_HTTPS_PORT >> $SILENT_INSTALL_FILE echo AUTH_DOMAIN= >> $SILENT_INSTALL_FILE echo WEB_PROF_NAME=DEV >> $SILENT_INSTALL_FILE echo WEB_PROF_USERID=PTWEBSERVER >> $SILENT_INSTALL_FILE echo WEB_PROF_PWD=PTWEBSERVER >> $SILENT_INSTALL_FILE echo REPORTS_DIR=/var/tmp/psreports >> $SILENT_INSTALL_FILE cd $TOOLS_HOME/setup/PsMpPIAInstall sh setup.sh -javahome $TOOLS_HOME/jre -i silent \ -DRES_FILE_PATH=$TOOLS_HOME/tmp/$SILENT_INSTALL_FILE -tempdir $TOOLS_HOME/tmp
So, first build your own response file with all the required fields according to your environment and action you are doing (deployment, re-deployment), and call it within DRES_FILE_PATH. That parameter was unknown for me. It is rather a nice learn. Of course, it might require a lot of testing, but it could be helpful if you have a high number of environments to re-build time to time, especially useful after a Peopletools (patch) upgrade which can be done on regular basis.

Save the response file in a secure place, and eventually you’ll see the advantages of silent PIA deployment. Run the installer with the silent option avoids some painful time to remember what ports are used, what webprofile, what reports directory…
I was initially not convinced about the usefulness of that, but try it. Use it.

Nicolas.

Manage Peoplesoft with OEM Grid Control (3/3)

2011-04-09T21:12:00.001+02:00

Last part of this series about Peoplesoft managed in OEM Grid Control, once the OEM Grid Control is installed with the Peoplesoft plug-in, once the Agent is installed on the targets with the Peoplesoft plug-in, it’s time for configuring the all thing in OEM GUI.

First, add the Peoplesoft target :
The user is the Peoplesoft domain owner (not necessarily the owner of the PS_HOME), for the PSOVM servers, that’s psadm2.

The discovery path is the PS_CFG_HOME. If it is missing from the environment variable, it is going to the user’s home directory. For the PSOVM servers, it is going to the psadm2’s home :

Choose the type you want to manage :

We can link the Oracle database when Peoplesoft is discovered (here the db server was not started) :

And finally, everything selected earlier is now recognized :

From now, we can start/stop (all in one shot if required) and configure the all Peoplesoft domain.

Let’s see the Process Scheduler possibilities :
Here, we can do whatever we are doing within the psadmin tool from the target host:

Let’s see the Application Server possibilities :

And the WebServer :
I won’t go through every single sub-menus over there, there are too many. But as you can see above, everything we – as Peoplesoft DBA - usually do from the backend, directly connected onto a server, can be done through OEM Grid Control. Rather nice, especially when managing a lot of environments. That’s maybe a bit of work for configuring everything properly, according to all the specificities of the environments, but that makes the life so easier once it is done that I think it is worth to do and to have on board.

Enjoy it.

Nicolas.

Manage Peoplesoft with OEM Grid Control (2/3)

2011-04-08T17:42:00.001+02:00

After installing the OEM Grid Control 11gR1 – the OVM template, including the Peoplesoft plug-in for OMS as shown here, it’s time for the target system to be prepared. All the client servers have to have the OM Agent. By client, it means client for the OMS, say so the clients are the databases servers and Apps/Batch/PIA servers which I created based on PSOVM as shown in previous posts. But the Peoplesoft plug-in is crawling a PS_HOME, it has to be installed only on Apps/Batch/PIA servers.

1. The OEM Agent
Whether there’s space enough in $ORACLE_HOME (/u01/app/oracle/product) on the PSOVM database servers (user oracle), there’s no space left next to the Oracle client (/opt/oracle/psft/pt) on the PSOVM App/Batch/PIA servers (user psadm1).
Before installing the Agent on App/Batch/PIA, let’s make a dedicated folder where’s space allows us to install it, as following :
[root@psovmhcm /]# cd /
[root@psovmhcm /]# df -k .
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/xvda2             3876120    724696   3111424 19% /
[root@psovmhcm /]# mkdir oracle_agent
[root@psovmhcm /]# chown -R psadm1:oracle oracle_agent
[root@psovmhcm /]# cd /opt/oracle/psft/pt
[root@psovmhcm pt]# ln -s /oracle_agent .
[root@psovmhcm pt]# ls -lrt
total 56
drwx------ 2 root   root   16384 Dec 20 19:44 lost+found
drwxr-xr-x 9 root   root    4096 Dec 20 20:08 bea
drwxr-xr-x 7 root   root    4096 Dec 20 20:12 oracle-client
drwxr-xr-x 5 root   root    4096 Jan 23 09:37 cobol
drwxr-xr-x 28 psadm1 oracle 4096 Jan 23 09:43 tools
lrwxrwxrwx 1 root   root      13 Mar 30 11:16 oracle_agent -> /oracle_agent
[root@psovmhcm pt]#

Remember, the PSOVMs are 64bit word sized (furthermore Peopletools 8.5x is only supported on 64bit OS), the Agent to be downloaded is from Linux x86-64, 11.1.0.1.0 :
http://www.oracle.com/technetwork/oem/grid-control/downloads/agentsoft-090381.html
Once downloaded, upload the file to the PSOVM OEM Grid Control previously installed, into the folder /u01/OracleHomes/Middleware/oms11g/sysman/agent_download/11.1.0.1.0 and unzip it.

Then, everything can be done through the OEM GUI. Much easier than ever, especially when deploying Agent through multiple target. However, screenshots below are coming from a deployment on one target only :

Choose the platform Linux-x86-64, that’s the one we’ve just upload to the OMS server :

Here you mention the owner of the Agent home (OMA_HOME),
=> for the PSOVM database servers it will be oracle,
=> for the PSOVM App/Batch/PIA servers it will be psadm1
Then, here you also mention the parent folder hosting the Agent home (OMA_HOME),
=> for the PSOVM database servers it will be /u01/app/oracle/product,
=> for the PSOVM App/Batch/PIA servers it will be /opt/oracle/psft/pt/oracle_agent
Uncheck the run of root.sh, it has to be done manually later on (somehow it failed in my case when it was checked).
Give the sysman password :

Be patient during these phases, depending of the number of targets you are deploying to and of the network bandwidth, it can take a quite while :

Now, the new host has been added in the host’s list :

Do not forget to run root.sh (in $OMA_HOME). We can eventually check the agent status from the target host :

And the database as well in the database’s list :

Just to show it, I also deployed the Agent through multiple targets at once :

In the end, we got all the hosts targets


Warning :
1. Do not forget to run root.sh from the target Agent home, otherwise you may encountered the following error (RemoteOperationException: ERROR: NMO not setuid-root (Unix-only)) later on when managing the environment :

2. Do not forget to maintain the /etc/hosts according to the all environment. The /etc/hosts from OMS server should contains its own IP address, hostname and domain name, but also all the target servers’ references (IP, hostname and domain). Here’s the one I’m using on the OMS host server :
[oracle@ovmoem111 ~]$ more /etc/hosts
127.0.0.1       localhost.localdomain   localhost
192.168.1.160 ovmoem111.phoenix.nga ovmoem111
192.168.1.133   psovmdb.phoenix.nga psovmdb
192.168.1.143   psovmcrm.phoenix.nga psovmcrm
192.168.1.142   psovmcrmdb.phoenix.nga psovmcrmdb
192.168.1.145   psovmfscm.phoenix.nga psovmfscm
192.168.1.144   psovmfscmdb.phoenix.nga psovmfscmdb
192.168.1.147   psovmhcm.phoenix.nga psovmhcm
192.168.1.146   psovmhcmdb.phoenix.nga psovmhcmdb
192.168.1.148   psovmhcmdb2.phoenix.nga psovmhcmdb2
[oracle@ovmoem111 ~]$

The /etc/hosts file from target hosts must contains their own IP address, hostname and domain name as well as the ones of the OMS server. Here’s an example on one of the target host :
[root@psovmcrm ~]# more /etc/hosts
127.0.0.1       localhost.localdomain   localhost
::1     localhost6.localdomain6 localhost6
192.168.1.143   psovmcrm.phoenix.nga psovmcrm
192.168.1.160 ovmoem111.phoenix.nga ovmoem111
[root@psovmcrm ~]#

If not doing so, you can have the following error (not possible to configure target database for instance) :

2. The Peoplesoft plug-in for the Agent
To be done only on App/Batch/PIA PSOVM servers.
To be able to manage the Peoplesoft environment from OEM Grid Control, the Agent must have the Peoplesoft plug-in. This is the same package used for the plug-in previously installed on OMS.
To be downloaded from https://edelivery.oracle.com (free registration), Product “Peoplesoft Enterprise”, Platform “Linux x86-64” (but the results do not differ, it does not matter for Peoplesoft packages), then choose the pack “Oracle Application Management Pack 1.0.0.2.0 for PeopleSoft Enterprise Media Pack v2” part number B60821-02.
Download the part number V22794-01 named “PeopleSoft Enterprise Environment Management Plug-in for Oracle Enterprise Manager (8.51.0.1.0)”. Despite the name, it is compatible on Peopletools 8.48 and above, moreover it is also compatible with OEM Grid Control 11gR1.

The Peoplesoft plug-in installation on Agent will be the easiest part, using the silent installation option as following.
Warning : the Peoplesoft plug-in for OEM Agent must be done whilst the psconfig.sh has not been previously invoked in the session (the PS environment must not be set), make it not happening.

Here I rename the psconfig.sh to avoid all confusion.
login as: root
root@192.168.1.143's password:
Last login: Wed Mar 30 11:19:04 2011 from 192.168.1.202
[root@psovmcrm ~]# su - psadm1
[psadm1@psovmcrm ~]$ cd $PS_HOME
[psadm1@psovmcrm tools]$ pwd
/opt/oracle/psft/pt/tools
[psadm1@psovmcrm tools]$ mv psconfig.sh _psconfig.sh
[psadm1@psovmcrm tools]$ exit
logout
[root@psovmcrm ~]# su - psadm1
-bash: /opt/oracle/psft/pt/tools/psconfig.sh: No such file or directory

From the Peoplesoft plug-in, unzip the file 5016553.zip (present under the downloaded Peoplesoft plug-in package) and copy it on your local server for installation (the target OMA host).
[psadm1@psovmcrm ~]$ cd /tmp
[psadm1@psovmcrm tmp]$ scp -r root@ovmoem111:/nfs/software/OracleCD/OEM/PeoplesoftPlugin/8.51/Disk1/5016553 .
root@ovmoem111's password:
<…snipped…>
[psadm1@psovmcrm tmp]$

You must set the ORACLE_HOME variable to the OMA_HOME and stop the Agent.
[psadm1@psovmcrm tmp]$ export ORACLE_HOME=/opt/oracle/psft/pt/oracle_agent/agent11g
[psadm1@psovmcrm tmp]$ cd $ORACLE_HOME/oui/bin
[psadm1@psovmcrm bin]$ cd ../../bin
[psadm1@psovmcrm bin]$ ./emctl stop agent

Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Agent is Not Running
[psadm1@psovmcrm bin]$

Then, from the OUI Installer of Agent, run the silent installation.
[psadm1@psovmcrm bin]$ cd -
/opt/oracle/psft/pt/oracle_agent/agent11g/oui/bin
[psadm1@psovmcrm bin]$ ./runInstaller.sh -silent -ignoreSysPrereqs -waitForCompletion -responseFile /tmp/5016553/Disk1/response/psemagent.rsp -sourceLoc /tmp/5016553/Disk1/stage/products.xml -invPtrLoc $ORACLE_HOME/oraInst.loc ORACLE_HOME=$ORACLE_HOME
Starting Oracle Universal Installer...

Checking swap space: must be greater than 500 MB. Actual 2055 MB Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2011-04-01_07-56-41AM. Please wait ...Oracle Universal Installer, Version 11.1.0.8.0 Production
Copyright (C) 1999, 2010, Oracle. All rights reserved.

You can find the log of this install session at:
/home/psadm1/oraInventory/logs/installActions2011-04-01_07-56-41AM.log
.................................................................................................... 100% Done.

Loading Product Information
............................................................... 100% Done.

Analyzing dependencies
............................................................... 100% Done.

-----------------------------------------------------------------------------
Summary
Global Settings
    Source: /tmp/5016553/Disk1/stage/products.xml
    Oracle Home: /opt/oracle/psft/pt/oracle_agent/agent11g (agent11g1)
    Installation Type: Typical
Product Languages
   English
Space Requirements
   / Required 23MB (includes 7MB temporary) : Available 1.82GB
New Installations (1 products)
   PeopleSoft Environment Management Plug-in (Agent) 8.51.0.1.0
-----------------------------------------------------------------------------

Installation in progress (Friday, April 1, 2011 7:58:52 AM EDT)
............................................................................................... 95% Done.
Install successful

Linking in progress (Friday, April 1, 2011 7:59:03 AM EDT)
Link successful

Setup in progress (Friday, April 1, 2011 7:59:03 AM EDT)
Setup successful

End of install phases.(Friday, April 1, 2011 7:59:11 AM EDT)
Starting to execute configuration assistants
Configuration assistant "PeopleSoft Environment Management Agent Plug-in" succeeded
The installation of PeopleSoft Environment Management Plug-in (Agent) was successful.
Please check '/home/psadm1/oraInventory/logs/silentInstall2011-04-01_07-56-41AM.log' for more details.
[psadm1@psovmcrm bin]$

The Agent is restarted automatically, we can check it.
[psadm1@psovmcrm bin]$ cd -
/opt/oracle/psft/pt/oracle_agent/agent11g/bin
[psadm1@psovmcrm bin]$ ./emctl status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent Version     : 11.1.0.1.0
OMS Version       : 11.1.0.1.0
Protocol Version : 11.1.0.0.0
Agent Home        : /opt/oracle/psft/pt/oracle_agent/agent11g
Agent binaries    : /opt/oracle/psft/pt/oracle_agent/agent11g
Agent Process ID : 1731
Parent Process ID : 1708
Agent URL         : https://psovmcrm.phoenix.nga:3872/emd/main/
Repository URL    : https://ovmoem111.phoenix.nga:4900/em/upload
Started at        : 2011-04-01 07:59:47
Started by user   : psadm1
Last Reload       : 2011-04-01 07:59:47
Last successful upload                       : 2011-04-01 08:01:25
Total Megabytes of XML files uploaded so far :     0.43
Number of XML files pending upload           :        0
Size of XML files pending upload(MB)         :     0.00
Available disk space on upload filesystem    :    52.60%
Last successful heartbeat to OMS             : 2011-04-01 08:05:27
---------------------------------------------------------------
Agent is Running and Ready
[psadm1@psovmcrm bin]$

Rename back to the original name the psconfig.sh for further connection.
[psadm1@psovmcrm bin]$ cd /opt/oracle/psft/pt/tools
[psadm1@psovmcrm tools]$ mv _psconfig.sh psconfig.sh
[psadm1@psovmcrm tools]$

From now, we should be able to add this Peoplesoft environment in the OEM Grid Control.
So far we have this :

Nest step is then to add Peoplesoft target. To be continued here.

Manage Peoplesoft with OEM Grid Control (1/3)

2011-04-07T21:11:00.001+02:00

Few weeks ago, I showed how to expand a Peoplesoft OVM use within a Physical Standby Database, how to enable the Active Data Guard, how a Batch server can run on Data Guard and how a App server can run on Data Guard.

Beside that, still through the given Peoplesoft OVM we can easily expand the Peoplesoft management and test how to manage a entire Peoplesoft environment within Oracle Enterprise Manager Grid Control. Right, that would required a bit more than just the Peoplesoft OVM. But all easy to get and easy to install.
Oracle is not only delivering templates for Applications layer, such as Peoplesoft, but also for OEM Grid Control (11gR1). The tests will also need the Peoplesoft plug-in for the OMS, the agent as well as the Peoplesoft plug-in for the agent.

Three steps to reach the expected results :
1. Install the OEM Grid Control 11gR1 (that will be done within the delivered template deployment), and the Peoplesoft plugin installation on top of the OMS. – this current post
2. Install the Agent for OEM on client server host, and the Peoplesoft plugin installation on top of the agent. – see here
3. Configuring the Peoplesoft in OEM Grid Control. – see here

1. OEM Grid Control 11gR1
So, first of all, let’s start with OEM Grid Control 11gR1. The template is downloadable on https://edelivery.oracle.com/linux (free registration), Product “Oracle VM templates”, Platform “X86 32 bit”, pack “Oracle VM Template for Enterprise Manager Grid Control 11.1 Media Pack v1 for x86 (32 bit)”, part number B60727-01. There are 4 disks to download, all together approx. 15Gb. Be aware, it is required 5Gb RAM available on the Oracle VM Server…

Then a standard VM template deployment, straightforward even though it took quite a while in my environment.

In the end, the OEM Grid Control is reachable within the URL : https://<ip_address>:7799/em/console/logon/logon

2. The Peoplesoft plugin for OMS
To be downloaded from https://edelivery.oracle.com (free registration), Product “Peoplesoft Enterprise”, Platform “Linux x86-64” (but the results do not differ, it does not matter for Peoplesoft packages), then choose the pack “Oracle Application Management Pack 1.0.0.2.0 for PeopleSoft Enterprise Media Pack v2” part number B60821-02.
Download the part number V22794-01 named “PeopleSoft Enterprise Environment Management Plug-in for Oracle Enterprise Manager (8.51.0.1.0)”. Despite the name, it is compatible on Peopletools 8.48 and above, moreover it is also compatible with OEM Grid Control 11gR1.
Once you have it, open a X-Window client to start the installation within a GUI. Note the plug-in has no installer embedded, it should be installed from within the existing OUI of the installed OMS.
On PSOVM OEM Grid Control, run the Installer from /u01/OracleHomes/MiddleWare/oms11g/oui/bin :

Then the installation is quite straightforward :

Once installed, in OEM Grid Control, under the tab “Target”, we’ll see one more sub-tab available, “Peoplesoft”:

Next step, the Agent on the target hosts. To be continued here.

COBOL Peopletools 8.51 and ulimit

2011-04-07T10:22:00.001+02:00

Whilst testing the Cobol on HCM9.1 after an upgrade from Peopletools 8.50 to Peopletools 8.51, the Cobol were just crashed. It did work fine in PT8.50 in the same environment, same platform, same OS settings, same PS_HOME (OS is AIX5.3ML9).
The Peopletools 8.51 have been installed on top of the existing PS_HOME 8.50.
But here, the Cobol just crashed, the log file being the following :
Oracle Enterprise Global Payroll and Absence Management – Version 9.0

Copyright (C) 2006
Oracle

All Rights Reserved

<...snipped...>

kgefec: fatal error 0
ORA-21503: program terminated by fatal error
ORA-04030: out of process memory when trying to allocate 2097184 bytes (Alloc statemen,intermBuf_kpdStm alloc)
Errors in file :
ORA-21503: program terminated by fatal error
ORA-04030: out of process memory when trying to allocate 2097184 bytes (Alloc statemen,intermBuf_kpdStm alloc)

----- Call Stack Trace -----
calling              call     entry                argument values in hex
location             type     point                (? means dubious value)
-------------------- -------- -------------------- ----------------------------
skgudmp+0044         bl       kgdsdst              FFFF3F50 ? 100A4848 ?
kgefec+00cc          bl       _ptrgl
kghnospc+089c        bl       kgefec               100A4848 ? 0 ? FBE ? 0 ?
kghalo+0d08          bl       kghnospc             BDE9694 ? 0 ? 16672750 ?
                                                   1666E878 ? 3EA0 ?
kpuhhalo+03cc        bl       kghalo               BDF0494 ? 0 ? 0 ? 0 ? 0 ? 0 ?
                                                   0 ? 0 ?
kpuertb_reallo+0110 bl       kpuhhalo             166747E8 ? 200000 ? CC1590C ?
kpuex_reallocT+00c0 bl       _ptrgl
kpuspi+05c0          bl       kpuex_reallocT       FFFF4AA0 ? 0 ? 0 ? 2 ?
OCIStmtSetPiec+0014 bl       kpuspi               1 ? FFFF4C8A ? 1 ? 2 ? 0 ?
                                                   0 ? 7 ? 17F3D278 ?
PSORA_FetchNex+02ec bl       0B876680
PS_sqlfet+002c       bl       0B8770F8
C_GETSTMT+0430       bl       0D415C10

<...snipped...>

----- End of Call Stack Trace -----

1110200: 1302083115: PSPAL::Abort: Unexpected signal received
1110200: 1302083115: PSPAL::Abort: Location: /vob/peopletools/src/pspal/exception_sigaction.cpp:494: PSPAL::SigactionSignalHandler::RecoverableSignalHandler(int, siginfo_t *, void *)
1110200: 1302083115: PSPAL::Abort: Generating process state report to ./process_state.txt
1110200: 1302083115: PSPAL::Abort: Terminating process now.

Execution error : file '/appl/psoft/hr91/cblbin/PTPSQLRT.gnt'
error code: 115, pc=0, call=1, seg=0
115 Unexpected signal (Signal 6)

It appears the ulimit for “data” was not set to unlimited, but to a low value. After setting it to unlimited for the Peoplesoft OS user, and re-linking the Cobol, it worked again.
That’s a small change within PT8.51, it was working fine without that unlimited data limit within 8.50.

Find out more, other workarounds about this error : E-COB: PTPSQLRT-114 Attempt to access item beyond bounds of memory (Signal 11) [ID 638612.1]

Nicolas.

Peopletools patches 8.50.14 and 8.50.15 removed

2011-04-07T09:41:00.001+02:00

Time to time I’m checking the Peopletools patch availability on ftp://ftp.peoplesoft.com/outgoing/ptools/.
I was surprised to see the date of patches 8.50.14 and 8.50.15 more recent than the date of patch 8.50.16, so I was going into there and saw nothing but a readme.txt with such explanation :
”PEOPLETOOLS PATCH 8.50.14 HAS BEEN REMOVED. PLEASE UPGRADE TO LATEST PEOPLETOOLS PATCH.”
and
”PEOPLETOOLS PATCH 8.50.15 HAS BEEN REMOVED. PLEASE UPGRADE TO LATEST PEOPLETOOLS PATCH on 8.50.”
It should be something seriously wrong with those patches, checking My Oracle Support does not give much information except the following notes where you can read the advice to upgrade to the latest Peopletools 8.50 patch (at least 8.50.16) :
E-PIA: PT8.50.14 / PT8.50.15 End Users Kicked Out of PeopleSoft [ID 1306952.1]
E-AS: Users Kicked Out Upon Applying For A Job In PeopleTools 8.50.14 [ID 1298866.1]

Searching over Internet does not give that much information neither, we can found that thread talking about a security flaw.

Well, if you are on one of these patches, you better should 1) raise a SR to the support 2) begin a patch upgrade.

Nicolas.

Peopletools 8.51 : psadmin is a symbolic link

2011-03-28T19:52:00.001+02:00

Up to Peopletools 8.50, you see that psadmin under $PS_HOME/appserv is an executable file :
[psadm2@psovmcrm ~]$ cd $PS_HOME/appserv
[psadm2@psovmcrm appserv]$ ls -lrt psadmin
-rwxr-xr-x 1 psadm1 oracle 281383 Apr 29 2010 psadmin
[psadm2@psovmcrm appserv]$ ./psadmin -v
Version 8.50.09
[psadm2@psovmcrm appserv]$

From Peopletools 8.51, psadmin under $PS_HOME/appserv became a symbolic link to $PS_HOME/bin/psadmin :
[psadm2@psovmhcm ~]$ cd $PS_HOME/appserv
[psadm2@psovmhcm appserv]$ ls -lrt psadmin
lrwxrwxrwx 1 psadm1 oracle 37 Dec 20 20:03 psadmin -> /opt/oracle/psft/pt/tools/bin/psadmin
[psadm2@psovmhcm appserv]$ ./psadmin -v
Version 8.51.02
[psadm2@psovmhcm appserv]$

It’s a kind of consolidation, all the binaries go into the same directory. Looks good, that’s fine by me.
But it could raise a problem.

When you are upgrading your Peopletools version, it has always been recommanded to install the new version on top of the existing PS_HOME, and that’s still the case within Peopletools 8.51 : see Task 3-1-4: Installing the PeopleTools Software, page 21 of the Enterprise PeopleTools 8.51 Upgrade :
”Run the PeopleSoft Installer and install the software to the same PS_HOME directory where you installed the previous PeopleSoft PeopleTools software.”

Doing so, installing the new Peopletools release on top of the existing PS_HOME works fine, except that the psadmin under $PS_HOME/appserv won’t be replaced by the symbolic link.
I’m not sure how the Peopletools installer is precisely working, but indeed, when you are trying to create a symbolic link whenever a file within the same name exist, an error is raised :
[psadm1@psovmcrm appserv]$ ln -s $PS_HOME/bin/psadmin .
ln: creating symbolic link `./psadmin' to `/opt/oracle/psft/pt/tools/bin/psadmin': File exists
[psadm1@psovmcrm appserv]$

Unfortunately, no error is returned by the installer, and nothing in the log file. So, it will “silently” continues to work on previous installed version. When you are upgrading an existing PS_HOME, always verify the version of the psadmin using the following :
./psadmin –v
It should obviously correspond to the version you installed. And be sure that from Peopletools 8.51, it is a symbolic link, otherwise, create it manually :
[psadm1@psovmcrm ~]$ cd $PS_HOME/appserv
[psadm1@psovmcrm appserv]$ rm -f psadmin
[psadm1@psovmcrm appserv]$ ln -s $PS_HOME/bin/psadmin .
[psadm1@psovmcrm appserv]$ ./psadmin –v

Enjoy it !

Find out more : My Oracle Support note E-UPG PT 8.51 New location of Psadmin.exe [ID 1251444.1] and E-UPG Master Note Upgrade Issues with PT 8.51 [ID 1262396.1]

Peopletools 8.51 : on TABLE’s build (bis)

2011-03-28T11:39:00.001+02:00

This blog entry continues the previous one I wrote about table’s build, especially about the partitioned tables. As it has been showed in the previous article, Peopletools 8.51 takes advantages of the DBMS_METADATA.GET_DDL package from the Oracle database, very useful if you are working within partitioned tables. Those are saved and survive a table rebuild through AppDesigner which has never been the case before.
Is it really right ? Does it really survive a table’s rebuild ? Well, I showed in the previous article that it does, but I came across a case which does not ! Example.

If you have to run the SETSPACE.SQR to update the tablespaces’ list in Peoplesoft, you’ll come in troubles within the partitioned tables.

Still working with my partitioned table PS_MYTABLE :

Now, I run SETSPACE.SQR :

Surprisingly, it updated the row of my table PS_MYTABLE to PTTBL (which has actually nothing to do with my table!).
Now from AppDesigner, the tablespace of this record has been changed :

And if I rebuild the table, the partitions are simply lost, the table going to PTTBL !

To retrieve the partitions, put back the table in the original tablespace CUAUDIT, and rebuild :

Pfew ! So, if the partitions are much better managed from AppDesigner table’s build than before, there’s still few surprise and thing to know !

So, working with partitions ? Take care, Peopletools 8.51 does not solve all, partitioned tables are still a very sensitive domain in Peoplesoft world !

Peopletools 8.51 : on TABLE’s build

2011-03-27T20:17:00.001+02:00

Peopletools 8.51 is coming with a very interesting improvement. The table definition (DDL) is taking from the backend before rebuilding the table. It means that if you have a partitioned table, it will survive a table rebuild, unlike the previous versions which just destroyed them recreating the table as non-partitioned. All the DBA working on Peoplesoft and Oracle have already encountered such situation. Sometimes, inadvertently a very big partitioned table to be rebuild become non-partitioned, raising a lot of subsequent issues.
On an other side, the indexes defined only in database are not (always) taking in account on table’s build. Note that I wrote “always”, it means that under some circumstances it does, have a look.

1. Table’s DDL from database
Firstly, let’s have a try to see how Peoplesoft is taking advantages of the DBMS_METADATA.GET_DDL package available in Oracle database.
Partitioning a table is still not available from AppDesigner, it must be done within the backend.
First, change a regular table to partition (let’s keep example simplest as possible) :

The table PS_MYTABLE is known from AppDesigner, but even being partitioned, we don’t see it from AppDesigner :

The DDL here is not coming from the database, but from the AppDesigner definition.
Let’s rebuild the table and see the generated script :

Now the script looks much better than ever. For the first time Peoplesoft is able to generated the script with a partitioned table definition as is from the backend :

That’ll save a lot of headaches. But overall, do not forget whenever sqlerror exit !

Addendum (28-MAR-2011) : coming across a case where Peopletools destroys the partitions definition, have a look here.

2. Index (shortname) on database only are not taken in account
The table’s DDL is taken from the backend, but if you have DBA in hurry creating indexes only from the backend without using AppDesigner for some performance reason, you’re still facing a known issue when rebuilding table. The database only index will be lost. Let’s create one with a Peoplesoft standard name :

Then rebuild the table (even forcing the index recreation) :

The script is as follow :
-- Start the Transaction

-- Data Conversion

-- Create temporary table

CREATE TABLE PSYMYTABLE (EMPLID VARCHAR2(11) NOT NULL,
MYSTRING VARCHAR2(30) NOT NULL,
MYNUM DECIMAL(8, 3) NOT NULL) PCTFREE 10 PCTUSED 40 INITRANS 1
MAXTRANS 255
STORAGE(
BUFFER_POOL DEFAULT)
TABLESPACE "CUAUDIT"
PARTITION BY RANGE ("EMPLID")
(PARTITION "PS_MYTABLE_P1" VALUES LESS THAN ('51')
PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS
2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "CUAUDIT" NOCOMPRESS ,
PARTITION "PS_MYTABLE_P2" VALUES LESS THAN (MAXVALUE)
PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS
2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "CUAUDIT" NOCOMPRESS )
/

-- Copy from source to temp table

INSERT INTO PSYMYTABLE (
        EMPLID,
    MYSTRING,
    MYNUM)
SELECT
        EMPLID,
    MYSTRING,
    MYNUM
FROM PS_MYTABLE
/

-- CAUTION: Drop Original Table

DROP TABLE PS_MYTABLE
/

-- Rename Table

RENAME PSYMYTABLE TO PS_MYTABLE
/

-- Done
=> As you can see, no index (re)creation !
It is a known case for ages on Peoplesoft. You have to define the same indexes manually onto AppDesigner as it is on database level. However in some cases there’re some bad surprise.

3. Index (longname) on database only are taken in account
Whether a database index is generally not visible from AppDesigner table’s rebuild, it can raise some issue in a specific case. Few weeks ago, I been faced to that case.
Let’s create an index on the the database only, specify a long name (!) :

And now, rebuild the underlying table PS_MYTABLE:

=> it will crash, closing the AppDesigner without any message box !
Here below, we can see the log file generated :
SQL Build process began on 27/03/2011 at 18:55:24 for database H91TMPLT.
File: E:\pt851-903-R1-retail\peopletools\src\psbld\bldcreat.cppSQL error. Stmt #: 2180 Error Position: 0 Return: 31603 - ORA-31603: object "PSBMYTABLE_LONG_IN" of type INDEX not found in schema "SYSADM" ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105 ORA-06512: at "SYS.DBMS_METADATA", line 3241 ORA-06512: at "SYS.DBMS_METADATA", line 4812 ORA-06512: at line 1
Failed SQL stmt:SELECT DBMS_METADATA.GET_DDL('INDEX',:1) from dual
There’s no way but rename the index to a shorter name !

Consequently, if a database short named index is not taking in account on table’s build, a long named index is !

Enjoy,

Peopletools 8.51 : “whenever sqlerror exit” is still missing

2011-03-27T17:22:00.001+02:00

Whether a lot of new features are coming within the latest Peopletools version 8.51 working closer from Oracle database, one is still missing. That one I’m awaiting for the last 10 years I’m working on Peoplesoft.
When you build a table, there no clause “whenever sqlerror exit” automatically added on top of the generated script, and that could save us from data loss. Here’s a simple example.
First of all, for the need of the test, I created two fields – MYSTRING VARCHAR2(30) and MYNUM NUMBER(8,3).
Then I create a record as following :

I put that record in a very small tablespace CUAUDIT which has been set in noextend mode :
SQL> alter database datafile '/u01/app/oracle/oradata/H91TMPLT/cuaudit.dbf' autoextend off;

Database altered.
Then I build that record, as usual :

The generated script is very simple, as follow :

Then, running the script in a SQL*Plus session :

So far, so good.
Now, populate the table with whatever you like (here with random values, that does not matter), but it fulfill the tablespace :

Now, I’d like to reduce the size of the column MYNUM from 8,3 to 7,3. As we all know, that’s not possible to achieve this by an ALTER TABLE when the column is not empty (ORA-01440 : column to be modified must be empty to decrease precision or scale) :

So, let’s go in AppDesigner, modifying the column length and rebuild the table, not through ALTER TABLES (that won’t work) but through CREATE TABLES (with a staging table) :

And the script is now :

As far as we can see, some efforts have been made in the script on the comments to warn people reading the script about the table drop command, but from my point of view this is far not enough.
Return in SQL*Plus session, and run it :

There’s obviously not enough space in my tablespace for the staging table, but the script does not care error, it continues and drop my source table. It is just gone !!
If you are lucky enough, or rather a “data safe guardian”, you have RECYCLEBIN feature turned on on your database, otherwise, a restore will be needed (sigh) :

And ultimately, you can recover the table from the recyclebin with flashback :

So, you have to set the famous clause “whenever sqlerror exit” in your SQL*Plus session and you’ll be able to run safely the script :

Now the source table still exists, and you are able to fix the issue before running it again. But before the next run, don’t forget to drop the staging table, otherwise it will fail again !
On a simple script, we can see easily the errors, if needed, what to recover, and how to fix it. But most of the time, during project migration, there’s much more to build (e.g. Peopletools upgrade), and very bad surprise are not rare.

As I said at the beginning of this blog entry, this case is not new, it has always been like that (at least from Peopletools 8.18 I started on), but seeing Peopletools working closer and closer from the Oracle Database, I sincerely hope that will be included in the next Peopletools release.
Awaiting that fix, take care !

OT: Dell OpenManage (Server Administration) - bis

2011-03-22T21:26:00.001+01:00

Last month I updated all the firmware of my server PowerEdge 2900 III implying the upgrade of the utility Dell OpenManage Server Administration (OMSA) as I explained here.
Since I was late of a couple of months on the versions, it raised a couple of errors that I was thinking to avoid by maintaining up-to-date the OMSA version. Today a new version as been released, the 6.5, let’s have it installed.
First, download from the Dell Drivers & Download Center. Then it should be a simple run of setup.sh script, since according to the documentation coming within the package, it is able to upgrade from a n-1 version (my current version is OMSA6.4).

A) Once gunziped and untared the downloaded package, run the setup.sh, unfortunately, it failed in my case :
[root@hercules /nfs/software/Utils/dell/OpenManage/6.5_RHEL5]# ./setup.sh

##############################################

Server Administrator Custom Install Utility

##############################################

Server Administrator version 6.4.0 is currently installed.
Installed components are:
   - srvadmin-argtable2-6.4.0-2.2.el5
   - srvadmin-omacore-6.4.0-1.195.2.el5
   - srvadmin-storelib-6.4.0-1.413.1.el5
   - srvadmin-isvc-6.4.0-1.98.1.el5
   - srvadmin-racdrsc-6.4.0-1.249.2.el5
   - srvadmin-racadm4-6.4.0-1.219.1.el5
   - srvadmin-omilcore-6.4.0-1.537.1.el5
   - srvadmin-xmlsup-6.4.0-1.231.1.el5
   - srvadmin-sysfsutils-6.4.0-1.3.el5
   - srvadmin-smweb-6.4.0-1.312.6.el5
   - srvadmin-storelib-sysfs-6.4.0-1.4.2.el5
   - srvadmin-racadm5-6.4.0-1.217.1.el5
   - srvadmin-omcommon-6.4.0-1.233.1.el5
   - srvadmin-smcommon-6.4.0-1.312.6.el5
   - srvadmin-jre-6.4.0-1.232.1.el5
   - srvadmin-storage-6.4.0-1.312.6.el5
   - srvadmin-hapi-6.4.0-1.52.1.el5
   - srvadmin-deng-6.4.0-1.59.1.el5
   - srvadmin-rac-components-6.4.0-1.249.2.el5

Do you want to upgrade Server Administrator to 6.5.0?
Press ('y' for yes | 'Enter' to exit): y
error: Failed dependencies:
        srvadmin-racadm5 = 6.4.0 is needed by (installed) dell_ie_rac_5-6.4.0-1.23.1.el5.x86_64
[root@hercules /nfs/software/Utils/dell/OpenManage/6.5_RHEL5]#

B) Trying to remove that RPM, it also failed :
[root@hercules /nfs/software/Utils/dell/OpenManage/6.5_RHEL5]# rpm -e srvadmin-racadm5
error: Failed dependencies:
        srvadmin-racadm5 = 6.4.0 is needed by (installed) dell_ie_rac_5-6.4.0-1.23.1.el5.x86_64

C) Trying to remove that last one also failed :
[root@hercules /nfs/software/Utils/dell/OpenManage/6.5_RHEL5]# rpm -e dell_ie_rac_5-6.4.0-1.23.1.el5.x86_64
error: Failed dependencies:
        dell_ie_rac_5 is needed by (installed) dell_ft_install-1.1-1.noarch

D) Finally, that the root one, this package is the installer utility for the firmware update, it can be re-installed later on, let’s remove all these RPMs :
[root@hercules /nfs/software/Utils/dell/OpenManage/6.5_RHEL5]# rpm -e dell_ft_install-1.1-1.noarch
[root@hercules /nfs/software/Utils/dell/OpenManage/6.5_RHEL5]# rpm -e dell_ie_rac_5-6.4.0-1.23.1.el5.x86_64
[root@hercules /nfs/software/Utils/dell/OpenManage/6.5_RHEL5]# rpm -e srvadmin-racadm5

E) Now the setup. sh must be successful :
[root@hercules /nfs/software/Utils/dell/OpenManage/6.5_RHEL5]# ./setup.sh

##############################################

Server Administrator Custom Install Utility

##############################################

Server Administrator version 6.4.0 is currently installed.
Installed components are:
   - srvadmin-argtable2-6.4.0-2.2.el5
   - srvadmin-omacore-6.4.0-1.195.2.el5
   - srvadmin-storelib-6.4.0-1.413.1.el5
   - srvadmin-isvc-6.4.0-1.98.1.el5
   - srvadmin-racdrsc-6.4.0-1.249.2.el5
   - srvadmin-racadm4-6.4.0-1.219.1.el5
   - srvadmin-omilcore-6.4.0-1.537.1.el5
   - srvadmin-xmlsup-6.4.0-1.231.1.el5
   - srvadmin-sysfsutils-6.4.0-1.3.el5
   - srvadmin-smweb-6.4.0-1.312.6.el5
   - srvadmin-storelib-sysfs-6.4.0-1.4.2.el5
   - srvadmin-omcommon-6.4.0-1.233.1.el5
   - srvadmin-smcommon-6.4.0-1.312.6.el5
   - srvadmin-jre-6.4.0-1.232.1.el5
   - srvadmin-storage-6.4.0-1.312.6.el5
   - srvadmin-hapi-6.4.0-1.52.1.el5
   - srvadmin-deng-6.4.0-1.59.1.el5
   - srvadmin-rac-components-6.4.0-1.249.2.el5

Do you want to upgrade Server Administrator to 6.5.0?
Press ('y' for yes | 'Enter' to exit): y
Preparing...                ########################################### [100%]
   1:srvadmin-xmlsup        ########################################### [ 6%]
   2:srvadmin-sysfsutils    ########################################### [ 11%]
   3:srvadmin-storelib-sysfs########################################### [ 17%]
   4:srvadmin-storelib      ########################################### [ 22%]
   5:srvadmin-hapi          ########################################### [ 28%]
   6:srvadmin-racadm4       ########################################### [ 33%]
   7:srvadmin-argtable2     ########################################### [ 39%]
   8:srvadmin-omilcore      ########################################### [ 44%]
     **********************************************************
     After the install process completes, you may need
     to log out and then log in again to reset the PATH
     variable to access the Dell OpenManage CLI utilities

     **********************************************************
   9:srvadmin-deng          ########################################### [ 50%]
10:srvadmin-omcommon      ########################################### [ 56%]
11:srvadmin-isvc          ########################################### [ 61%]
12:srvadmin-smcommon      ########################################### [ 67%]
13:srvadmin-omacore       ########################################### [ 72%]
14:srvadmin-rac-components########################################### [ 78%]
15:srvadmin-storage       ########################################### [ 83%]
16:srvadmin-jre           ########################################### [ 89%]
17:srvadmin-racdrsc       ########################################### [ 94%]
18:srvadmin-smweb         ########################################### [100%]

Do you want the Server Administrator services started?

   Press ('y' for yes | 'Enter' to exit): y
Starting Systems Management Device Drivers:
Starting dell_rbu:                                         [ OK ]
Starting ipmi driver: Already started                      [ OK ]
Starting Systems Management Data Engine:
Starting dsm_sa_datamgrd:                                  [ OK ]
Starting dsm_sa_eventmgrd:                                 [ OK ]
Starting dsm_sa_snmpd:                                     [ OK ]
Starting DSM SA Shared Services:                           [ OK ]

[root@hercules /nfs/software/Utils/dell/OpenManage/6.5_RHEL5]#

F) I noticed that for some reasons the Web Server component is not getting installed, re-run the setup.sh and add that one :
[root@hercules /nfs/software/Utils/dell/OpenManage/6.5_RHEL5]# ./setup.sh

##############################################

Server Administrator Custom Install Utility

##############################################

Components for Server Administrator Managed Node Software:

Installed Components:
[x] Server Instrumentation
[x] Storage Management

Add Components
    [ ] 1. Server Administrator Web Server
    [ ] 2. Remote Enablement
    [ ] 3. Remote Access Core Components
    [ ] 4. Remote Access SA Plugin Components
    [ ] 5. All

Enter the number to select a component from the above list.
Enter q to quit.

Enter : 1

##############################################

Server Administrator Custom Install Utility

##############################################

Selected Options
- Server Administrator Web Server

Dependencies

Components for Server Administrator Managed Node Software:

Installed Components:
[x] Server Instrumentation
[x] Storage Management

Add Components
    [x] 1. Server Administrator Web Server
    [ ] 2. Remote Enablement
    [ ] 3. Remote Access Core Components
    [ ] 4. Remote Access SA Plugin Components
    [ ] 5. All

Enter the number to select a component from the above list.
Enter c to copy selected components to destination folder.
Enter i to install the selected components.
Enter r to reset selection and start over.
Enter q to quit.

Enter : i
Installing the selected packages.

Preparing... ########################################### [100%]
1:srvadmin-iws ########################################### [100%]

Do you want the Server Administrator services started?

Starting DSM SA Connection Service: [ OK ]

G) Now, from a web browser, check the OMS version within the default url port 1311 (https://hercules.phoenix-nga:1311/servlet/OMSALogin?msgStatus=null):

Done ! Version has been updated to 6.5.

H) Since I removed dell_ft_install-1.1-1.noarch, I reinstall it again, it will reinstall the all three RPMs uninstalled earlier to get OMSA upgraded :
[root@hercules /root]# yum install dell_ft_install
Loaded plugins: dellsysid, fastestmirror
Loading mirror speeds from cached hostfile
* addons: mirror.leaseweb.com
* base: mirror.leaseweb.com
* extras: mirror.leaseweb.com
* updates: mirror.leaseweb.com
Excluding Packages in global exclude list
Finished
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package dell_ft_install.noarch 0:1.1-1 set to be updated
--> Processing Dependency: dell_ie_rac_5 for package: dell_ft_install
--> Running transaction check
---> Package dell_ie_rac_5.x86_64 0:6.4.0-1.23.1.el5 set to be updated
--> Processing Dependency: srvadmin-racadm5 = 6.4.0 for package: dell_ie_rac_5
--> Running transaction check
---> Package srvadmin-racadm5.x86_64 0:6.4.0-1.217.1.el5 set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

============================================================================================== Package                                      Arch                               Version                                       Repository
Size
==============================================================================================
Installing:
dell_ft_install                              noarch                             1.1-1                                         dell-omsa-indep                             2.7 k
Installing for dependencies:
dell_ie_rac_5                                x86_64                             6.4.0-1.23.1.el5                              dell-omsa-indep                             4.3 k
srvadmin-racadm5                             x86_64                             6.4.0-1.217.1.el5                             dell-omsa-indep                             961 k

Transaction Summary
==============================================================================================
Install 3 Package(s)
Upgrade 0 Package(s)

Total download size: 968 k
Is this ok [y/N]: y
Downloading Packages:
(1/3): dell_ft_install-1.1-1.noarch.rpm                                              | 2.7 kB
(2/3): dell_ie_rac_5-6.4.0-1.23.1.el5.x86_64.rpm                                     | 4.3 kB
(3/3): srvadmin-racadm5-6.4.0-1.217.1.el5.x86_64.rpm                                 | 961 kB
----------------------------------------------------------------------------------------------Total                                                                                                                                            221 kB/s | 968 kB     00:04
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing     : srvadmin-racadm5                                         1/3
Installing     : dell_ie_rac_5                                            2/3
Installing     : dell_ft_install                                          3/3

Installed:
dell_ft_install.noarch 0:1.1-1

Dependency Installed:
dell_ie_rac_5.x86_64 0:6.4.0-1.23.1.el5
srvadmin-racadm5.x86_64 0:6.4.0-1.217.1.el5

Complete!
[root@hercules /root]#

I) Now, a quick check of the firmware version :
[root@hercules /root]# update_firmware

Running system inventory...

Searching storage directory for available BIOS updates...
Checking SAS/SATA Backplane 0:0 Backplane Firmware - 1.05
        Available: dell_dup_componentid_11204 - 1.05
        Did not find a newer package to install that meets all installation checks.
Checking System BIOS for PowerEdge 2900 - 2.6.1
        Did not find a newer package to install that meets all installation checks.
Checking PERC 6/i Integrated Controller 0 Firmware - 6.3.0-0001
        Available: pci_firmware(ven_0x1000_dev_0x0060_subven_0x1028_subdev_0x1f0c) - 6.3.0-0001
        Did not find a newer package to install that meets all installation checks.
Checking BMC - 2.37
        Available: dell_dup_componentid_05814 - 2.37
        Did not find a newer package to install that meets all installation checks.
Checking NetXtreme II BCM5708 Gigabit Ethernet rev 12 (eth1) - 6.0.1
        Available: pci_firmware(ven_0x14e4_dev_0x164c) - 6.0.1
        Did not find a newer package to install that meets all installation checks.
Checking BIOS - 2.6.1
        Available: dell_dup_componentid_00159 - 2.6.1
        Did not find a newer package to install that meets all installation checks.
Checking NetXtreme II BCM5708 Gigabit Ethernet rev 12 (eth0) - 6.0.1
        Available: pci_firmware(ven_0x14e4_dev_0x164c) - 6.0.1
        Did not find a newer package to install that meets all installation checks.
Checking ST3500620SS Firmware - ms04
        Available: dell_dup_componentid_16861 - ms0c
        Did not find a newer package to install that meets all installation checks.

This system does not appear to have any updates available.
No action necessary.

[root@hercules /root]#

Enjoy !

PSOVM and Active Data Guard : Appserver

2011-03-14T17:26:00.001+01:00

After setting a Physical Standby Database and enable Active Data Guard, this part assume you’ve done all the requirements to run the batch process onto the read-only database, as explained in earlier post : secondary ACCESSID, secondary SYMBOLICID, database link, local synonyms and remote synonyms must have been configured.
This part will be focused on the Application Server which also can be configured to run onto the read-only database for few elements. Working on PSOVM make the configuration even easier for testing and learning purpose, it is coming with the latest Peopletools version, 8.51, which come with that configuration option in psappsrv.cfg :
[Startup]
;=========================================================================
; Database Signon settings
;=========================================================================
DBName=
DBType=
UserId=
UserPswd=
ConnectId=
ConnectPswd=
ServerName=
StandbyDBName=
StandbyDBType=
StandbyUserId=
StandbyUserPswd=
That option will work only for an enable Oracle Active Data Guard.
At the end of this stage, the global architecture of my PSOVM environment will be as follow (in green the changes compared to the previous post) :
1. Required scripts
Please follow instruction given for the Batch server configuration on Active Data Guard, step 1.

2. Create a secondary ACCESSID/SYMBOLICID on primary db – psadmin.sql
Please follow instruction given for the Batch server configuration on Active Data Guard, step 2.

3. Create a dedicated application user attached to the secondary SYMBOLICID
Please follow instruction given for the Batch server configuration on Active Data Guard, step 3.

4. Create database link on primary db to the primary db – createdblinktoprimarydb.sql
Please follow instruction given for the Batch server configuration on Active Data Guard, step 4.

5. Create local synonyms – createlocalsynonyms.sql
Please follow instruction given for the Batch server configuration on Active Data Guard, step 5.

6. Create remote synonyms – createremotesynonyms.sql
Please follow instruction given for the Batch server configuration on Active Data Guard, step 6.

7. Application server configuration
7.1 Be sure the tnsnames.ora is properly configured, please follow instruction given for the Batch server configuration on Active Data Guard, step 8.1.

7.2 Modify psappsrv.cfg
Set the standby database and standby user :
[Startup]
;=========================================================================
; Database Signon settings
;=========================================================================
DBName=H91TMPLT
DBType=ORACLE
UserId=PS
UserPswd=PS
ConnectId=people
ConnectPswd=peop1e
ServerName=____
StandbyDBName=H91STBY
StandbyDBType=ORACLE
StandbyUserId=PSBKP
StandbyUserPswd=PSBKP

7.3 Reconfigure the application server APPDOM (psadmin tool)
[psadm2@psovmhcm PRCSDOM]$ cd $PS_HOME/appserv
[psadm2@psovmhcm appserv]$ ./psadmin

--------------------------------
PeopleSoft Server Administration
--------------------------------

1) Application Server
2) Process Scheduler
3) Search Server
4) Replicate Config Home
q) Quit

Command to execute (1-4, q): 1

--------------------------------------------
PeopleSoft Application Server Administration
--------------------------------------------

1) Administer a domain
2) Create a domain
3) Delete a domain
4) Import domain configuration
q) Quit

Command to execute (1-4, q) : 1

Domain list:

1) APPDOM

Select domain: 1

--------------------------------
PeopleSoft Domain Administration
--------------------------------
Domain Name: APPDOM

1) Boot this domain
2) Domain shutdown menu
3) Domain status menu
4) Configure this domain
5) TUXEDO command line (tmadmin)
6) Edit configuration/log files menu
7) Messaging Server Administration menu
8) Purge Cache
9) Preload Cache
10) Clean IPC resources of this domain
q) Quit

Command to execute (1-10, q) : 4

This option will shutdown the domain.
Do you want to continue? (y/n) [n] :y

> INFO: Oracle Tuxedo, Version 10.3.0.0, 64-bit, Patch Level 031

Booting admin processes ...

exec BBL -A :
CMDTUX_CAT:821: INFO: Duplicate server.
0 processes started.

> Shutting down all admin and server processes in /home/psadm2/psft/pt/8.51/appserv/APPDOM/PSTUXCFG

Shutting down server processes ...
<…snipped…>
Shutting down admin processes ...

Server Id = 0 Group Id = psovmhcm.phoenix.nga Machine = psovmhcm.phoenix.nga: shutdown succeeded
18 processes stopped.

All domain processes have stopped.

----------------------------------------------
Quick-configure menu -- domain: APPDOM
----------------------------------------------
      Features                      Settings
     ==========                    ==========
1) Pub/Sub Servers   : Yes   15) DBNAME     :[H91TMPLT]
2) Quick Server      : No    16) DBTYPE     :[ORACLE]
3) Query Servers     : Yes   17) UserId     :[PS]
4) Jolt              : Yes   18) UserPswd   :[PS]
5) Jolt Relay        : No    19) DomainID   :[APPDOM]
6) WSL               : No    20) AddToPATH :[.]
7) PC Debugger       : No    21) ConnectID :[people]
8) Event Notification: No    22) ConnectPswd:[peop1e]
9) MCF Servers       : No    23) ServerName :[____]
10) Perf Collator     : No    24) WSL Port   :[7000]
11) Analytic Servers : Yes   25) JSL Port   :[9000]
12) Domains Gateway   : No    26) JRAD Port :[9100]

Actions
=========
13) Load config as shown
14) Custom configuration
h) Help for this menu
q) Return to previous menu

HINT: Enter 15 to edit DBNAME, then 13 to load

Enter selection (1-26, h, or q): 13
Performing load prechecks ...
Loading validation table...
setting DBName=H91TMPLT
setting DBType=ORACLE
setting UserId=PS
setting UserPswd=PS
setting ConnectId=people
setting ConnectPswd=peop1e
setting ServerName=____
setting Port=7000
setting Port=9000
setting Listener Port=9100
setting Domain ID=APPDOM
setting Add to PATH=.
New CFG file written with modified Startup parameters

Log Directory entry not found in configuration file.
Setting Log Directory to the default... [PS_SERVDIR/LOGS]
Spawning disabled for server PSAPPSRV.
Spawning disabled for server PSQRYSRV.
Spawning disabled for server PSBRKHND_dflt.
Spawning disabled for server PSPUBHND_dflt.
Spawning disabled for server PSSUBHND_dflt.
Configuration file successfully created.
CFG setting changes completed
Loading configuration...
Domain configuration complete.

7.4 Restart the application server
--------------------------------
PeopleSoft Domain Administration
--------------------------------
Domain Name: APPDOM

Command to execute (1-10, q) : 1

-------------------------------
PeopleSoft Domain Boot Menu
-------------------------------
Domain Name: APPDOM

1) Boot (Serial Boot)
2) Parallel Boot
q) Quit

Command to execute (1-2, q) [q]: 1

Archived a copy of the domain configuration to /home/psadm2/psft/pt/8.51/appserv/APPDOM/Archive/psappsrv.cfg
Attempting to boot bulletin board...
tmadmin - Copyright (c) 2007-2008 Oracle.
Portions * Copyright 1986-1997 RSA Data Security, Inc.
All Rights Reserved.
Distributed under license by Oracle.
Tuxedo is a registered trademark.
No bulletin board exists. Entering boot mode.

> INFO: Oracle Tuxedo, Version 10.3.0.0, 64-bit, Patch Level 031

Booting admin processes ...

exec BBL -A :
process id=1905 ... Started.
1 process started.
Attaching to active bulletin board.

> Attempting to boot ...
INFO: Oracle Tuxedo, Version 10.3.0.0, 64-bit, Patch Level 031

Booting server processes ...

exec PSWATCHSRV -o ./LOGS/stdout -e ./LOGS/stderr -A -- -ID 152926 -D APPDOM -S PSWATCHSRV :
process id=1909 ... Started.
…
<snipped>
…
exec JREPSVR -o ./LOGS/stdout -e ./LOGS/stderr -A -- -W -P /home/psadm2/psft/pt/8.51/appserv/APPDOM/jrepository :
process id=1975 ... Started.
17 processes started.

7.5 On secondary database, check for the connections
SQL> select substr(username,1,8) userm,machine,program,module from v$session where username is not null
SQL> /

USERM       MACHINE                   PROGRAM                                          MODULE
----------- ------------------------- ------------------------------------------------ --------------------------------------
SYSBKP      psovmhcm.phoenix.nga      PSMONITORSRV@psovmhcm.phoenix.nga (TNS V1-V3)    PSMONITORSRV@psovmhcm.phoenix.nga (TNS
SYSBKP      psovmhcm.phoenix.nga      PSSUBDSP@psovmhcm.phoenix.nga (TNS V1-V3)        PSSUBDSP@psovmhcm.phoenix.nga (TNS V1-
SYSBKP      psovmhcm.phoenix.nga      PSSUBHND@psovmhcm.phoenix.nga (TNS V1-V3)        PSSUBHND@psovmhcm.phoenix.nga (TNS V1-
SYSBKP      psovmhcm.phoenix.nga      PSPUBDSP@psovmhcm.phoenix.nga (TNS V1-V3)        PSPUBDSP@psovmhcm.phoenix.nga (TNS V1-
SYSBKP      psovmhcm.phoenix.nga      PSPUBHND@psovmhcm.phoenix.nga (TNS V1-V3)        PSPUBHND@psovmhcm.phoenix.nga (TNS V1-
SYSBKP      psovmhcm.phoenix.nga      PSBRKDSP@psovmhcm.phoenix.nga (TNS V1-V3)        PSBRKDSP@psovmhcm.phoenix.nga (TNS V1-
SYSBKP      psovmhcm.phoenix.nga      PSBRKHND@psovmhcm.phoenix.nga (TNS V1-V3)        PSBRKHND@psovmhcm.phoenix.nga (TNS V1-
SYSBKP      psovmhcm.phoenix.nga      PSANALYTICSRV@psovmhcm.phoenix.nga (TNS V1-V3)   PSANALYTICSRV@psovmhcm.phoenix.nga
SYSBKP      psovmhcm.phoenix.nga      PSANALYTICSRV@psovmhcm.phoenix.nga (TNS V1-V3)   PSANALYTICSRV@psovmhcm.phoenix.nga
SYSBKP      psovmhcm.phoenix.nga      PSANALYTICSRV@psovmhcm.phoenix.nga (TNS V1-V3)   PSANALYTICSRV@psovmhcm.phoenix.nga
SYSBKP      psovmhcm.phoenix.nga      PSSAMSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSSAMSRV@psovmhcm.phoenix.nga (TNS V1-
SYSBKP      psovmhcm.phoenix.nga      PSQRYSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSQRYSRV@psovmhcm.phoenix.nga (TNS V1-
SYSBKP      psovmhcm.phoenix.nga      PSAPPSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSAPPSRV@psovmhcm.phoenix.nga (TNS V1-
SYSBKP      psovmhcm.phoenix.nga      PSAPPSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSAPPSRV@psovmhcm.phoenix.nga (TNS V1-
SYSBKP      psovmhcm.phoenix.nga      PSMONITORSRV@psovmhcm.phoenix.nga (TNS V1-V3)    PSMONITORSRV@psovmhcm.phoenix.nga (TNS
SYSBKP      psovmhcm.phoenix.nga      PSPRCSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSPRCSRV@psovmhcm.phoenix.nga (TNS V1-
SYSBKP      psovmhcm.phoenix.nga      PSDSTSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSDSTSRV@psovmhcm.phoenix.nga (TNS V1-
SYSBKP      psovmhcm.phoenix.nga      PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)         PSAESRV@psovmhcm.phoenix.nga (TNS V1-
SYSBKP      psovmhcm.phoenix.nga      PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)         PSAESRV@psovmhcm.phoenix.nga (TNS V1-
SYSBKP      psovmhcm.phoenix.nga      PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)         PSAESRV@psovmhcm.phoenix.nga (TNS V1-
SYSBKP      psovmhcm.phoenix.nga      PSMSTPRC@psovmhcm.phoenix.nga (TNS V1-V3)        PSMSTPRC@psovmhcm.phoenix.nga (TNS V1-
PUBLIC      psovmhcmdb.phoenix.nga    oracle@psovmhcmdb.phoenix.nga (TNS V1-V3)        oracle@psovmhcmdb.phoenix.nga (TNS V1-
PUBLIC      psovmhcmdb.phoenix.nga    oracle@psovmhcmdb.phoenix.nga (TNS V1-V3)        oracle@psovmhcmdb.phoenix.nga (TNS V1-
PUBLIC      psovmhcmdb.phoenix.nga    oracle@psovmhcmdb.phoenix.nga (TNS V1-V3)        oracle@psovmhcmdb.phoenix.nga (TNS V1-
PUBLIC      psovmhcmdb.phoenix.nga    oracle@psovmhcmdb.phoenix.nga (TNS V1-V3)        oracle@psovmhcmdb.phoenix.nga (TNS V1-
SYS         psovmhcmdb2               sqlplus@psovmhcmdb2 (TNS V1-V3)                  sqlplus@psovmhcmdb2 (TNS V1-V3)

26 rows selected.

We can see now all the processes coming from the batch server as well as all the processes coming from the application server.

8. Test
8.1 The Application server is able to run a read-only component onto the secondary database. Let’s choose a simple one.

Onto the primary database, run the following :
SQL> select substr(username,1,8) userm,machine,program,module from v$session where username is not null
SQL> /

USERM       MACHINE                    PROGRAM                                          MODULE
----------- -------------------------- ------------------------------------------------ --------------------------------------
SYSADM      WORKGROUP\PHOENIX          pside.exe                                        pside.exe
SYSADM      psovmhcm.phoenix.nga       PSMONITORSRV@psovmhcm.phoenix.nga (TNS V1-V3)    PSMONITORSRV@psovmhcm.phoenix.nga
SYSADM      psovmhcm.phoenix.nga       PSPRCSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSPRCSRV@psovmhcm.phoenix.nga (TNS V1-
SYSADM      psovmhcm.phoenix.nga       PSDSTSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSDSTSRV@psovmhcm.phoenix.nga (TNS V1-
SYSADM      psovmhcm.phoenix.nga       PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)         PSAESRV@psovmhcm.phoenix.nga (TNS V1-
SYSADM      psovmhcm.phoenix.nga       PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)         PSAE
SYSADM      psovmhcm.phoenix.nga       PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)         PSAE
SYSADM      psovmhcm.phoenix.nga       PSMSTPRC@psovmhcm.phoenix.nga (TNS V1-V3)        PSMSTPRC@psovmhcm.phoenix.nga (TNS V1-
SYSADM      psovmhcm.phoenix.nga       PSMONITORSRV@psovmhcm.phoenix.nga (TNS V1-V3)    PSMONITORSRV@psovmhcm.phoenix.nga
SYSADM      psovmhcm.phoenix.nga       PSSUBDSP@psovmhcm.phoenix.nga (TNS V1-V3)        PSSUBDSP@psovmhcm.phoenix.nga (TNS V1-
SYSADM      psovmhcm.phoenix.nga       PSSUBHND@psovmhcm.phoenix.nga (TNS V1-V3)        PSSUBHND@psovmhcm.phoenix.nga (TNS V1-
SYSADM      psovmhcm.phoenix.nga       PSPUBDSP@psovmhcm.phoenix.nga (TNS V1-V3)        PSPUBDSP@psovmhcm.phoenix.nga (TNS V1-
SYSADM      psovmhcm.phoenix.nga       PSQRYSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSQRYSRV@psovmhcm.phoenix.nga (TNS V1-
SYSADM      psovmhcm.phoenix.nga       PSANALYTICSRV@psovmhcm.phoenix.nga (TNS V1-V3)   PSANALYTICSRV@psovmhcm.phoenix.nga
SYSADM      psovmhcm.phoenix.nga       PSBRKDSP@psovmhcm.phoenix.nga (TNS V1-V3)        PSBRKDSP@psovmhcm.phoenix.nga (TNS V1-
SYSADM      psovmhcm.phoenix.nga       PSPUBHND@psovmhcm.phoenix.nga (TNS V1-V3)        PSPUBHND@psovmhcm.phoenix.nga (TNS V1-
SYSADM      psovmhcm.phoenix.nga       PSAPPSRV@psovmhcm.phoenix.nga (TNS V1-V3)        HR_DR_SELECTION_UI
SYSADM      psovmhcm.phoenix.nga       PSANALYTICSRV@psovmhcm.phoenix.nga (TNS V1-V3)   PSANALYTICSRV@psovmhcm.phoenix.nga
SYSADM      psovmhcm.phoenix.nga       PSANALYTICSRV@psovmhcm.phoenix.nga (TNS V1-V3)   PSANALYTICSRV@psovmhcm.phoenix.nga
SYSADM      psovmhcm.phoenix.nga       PSBRKHND@psovmhcm.phoenix.nga (TNS V1-V3)        PSBRKHND@psovmhcm.phoenix.nga (TNS V1-
SYSADM      psovmhcm.phoenix.nga       PSSAMSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSSAMSRV@psovmhcm.phoenix.nga (TNS V1-
SYSADM      psovmhcm.phoenix.nga       PSAPPSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PROCESSMONITOR
PUBLIC      psovmhcmdb2                oracle@psovmhcmdb2 (TNS V1-V3)                   oracle@psovmhcmdb2 (TNS V1-V3)
SYS         psovmhcmdb.phoenix.nga     sqlplus@psovmhcmdb.phoenix.nga (TNS V1-V3)       sqlplus@psovmhcmdb.phoenix.nga (TNS
On the output above, in bold, the component we’ll work on (HR_DR_SELECTION_UI), this component in that test will read data only without updated anything, so a good candidate for the test.

8.2 Change the component property
Open the Application Designer, open that component :

Go to the properties definitions

Go to the tab “Use”

Check the read-only checkbox, click ok and save

8.3 Go back to the front-end application, and run the transaction

8.4 Whilst running the transaction, check the back-end
On the primary site, run the following :
SQL> select substr(username,1,8) userm,machine,program,module from v$session where username is not null
SQL> /

USERM      MACHINE                   PROGRAM                                          MODULE
---------- ------------------------- ------------------------------------------------ ----------------------------------------
SYSADM     WORKGROUP\PHOENIX         pside.exe                                        pside.exe
SYSADM     psovmhcm.phoenix.nga      PSMONITORSRV@psovmhcm.phoenix.nga (TNS V1-V3)    PSMONITORSRV@psovmhcm.phoenix.nga (TNS
SYSADM     psovmhcm.phoenix.nga      PSPRCSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSPRCSRV@psovmhcm.phoenix.nga (TNS V1-
SYSADM     psovmhcm.phoenix.nga      PSDSTSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSDSTSRV@psovmhcm.phoenix.nga (TNS V1-
SYSADM     psovmhcm.phoenix.nga      PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)         PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)
SYSADM     psovmhcm.phoenix.nga      PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)         PSAE
SYSADM     psovmhcm.phoenix.nga      PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)         PSAE
SYSADM     psovmhcm.phoenix.nga      PSMSTPRC@psovmhcm.phoenix.nga (TNS V1-V3)        PSMSTPRC@psovmhcm.phoenix.nga (TNS V1-
SYSADM     psovmhcm.phoenix.nga      PSMONITORSRV@psovmhcm.phoenix.nga (TNS V1-V3)    PSMONITORSRV@psovmhcm.phoenix.nga (TNS
SYSADM     psovmhcm.phoenix.nga      PSSUBDSP@psovmhcm.phoenix.nga (TNS V1-V3)        PSSUBDSP@psovmhcm.phoenix.nga (TNS V1-
SYSADM     psovmhcm.phoenix.nga      PSSUBHND@psovmhcm.phoenix.nga (TNS V1-V3)        PSSUBHND@psovmhcm.phoenix.nga (TNS V1-
SYSADM     psovmhcm.phoenix.nga      PSPUBDSP@psovmhcm.phoenix.nga (TNS V1-V3)        PSPUBDSP@psovmhcm.phoenix.nga (TNS V1-
SYSADM     psovmhcm.phoenix.nga      PSQRYSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSQRYSRV@psovmhcm.phoenix.nga (TNS V1-
SYSADM     psovmhcm.phoenix.nga      PSANALYTICSRV@psovmhcm.phoenix.nga (TNS V1-V3)   PSANALYTICSRV@psovmhcm.phoenix.nga (TNS
SYSADM     psovmhcm.phoenix.nga      PSBRKDSP@psovmhcm.phoenix.nga (TNS V1-V3)        PSBRKDSP@psovmhcm.phoenix.nga (TNS V1-
SYSADM     psovmhcm.phoenix.nga      PSPUBHND@psovmhcm.phoenix.nga (TNS V1-V3)        PSPUBHND@psovmhcm.phoenix.nga (TNS V1-
SYSADM     psovmhcm.phoenix.nga      PSAPPSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSAPPSRV@psovmhcm.phoenix.nga (TNS V1-
SYSADM     psovmhcm.phoenix.nga      PSANALYTICSRV@psovmhcm.phoenix.nga (TNS V1-V3)   PSANALYTICSRV@psovmhcm.phoenix.nga (TNS
SYSADM     psovmhcm.phoenix.nga      PSANALYTICSRV@psovmhcm.phoenix.nga (TNS V1-V3)   PSANALYTICSRV@psovmhcm.phoenix.nga (TNS
SYSADM     psovmhcm.phoenix.nga      PSBRKHND@psovmhcm.phoenix.nga (TNS V1-V3)        PSBRKHND@psovmhcm.phoenix.nga (TNS V1-
SYSADM     psovmhcm.phoenix.nga      PSSAMSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSSAMSRV@psovmhcm.phoenix.nga (TNS V1-
SYSADM     psovmhcm.phoenix.nga      PSAPPSRV@psovmhcm.phoenix.nga (TNS V1-V3)        HR_DR_SELECTION_UI
PUBLIC     psovmhcmdb2               oracle@psovmhcmdb2 (TNS V1-V3)                   oracle@psovmhcmdb2 (TNS V1-V3)
SYS        psovmhcmdb.phoenix.nga    sqlplus@psovmhcmdb.phoenix.nga (TNS V1-V3)       sqlplus@psovmhcmdb.phoenix.nga (TNS V1-

We still can see that component running onto the primary database, what about the secondary database.

On the secondary site, run the following :
SQL> select substr(username,1,8) userm,machine,program,module from v$session where username is not null
SQL> /

USERM     MACHINE                 PROGRAM                                          MODULE
--------- ----------------------- ------------------------------------------------ -------------------------------------------
SYSBKP    psovmhcm.phoenix.nga    PSMONITORSRV@psovmhcm.phoenix.nga (TNS V1-V3)    PSMONITORSRV@psovmhcm.phoenix.nga (TNS V1-
SYSBKP    psovmhcm.phoenix.nga    PSSUBDSP@psovmhcm.phoenix.nga (TNS V1-V3)        PSSUBDSP@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP    psovmhcm.phoenix.nga    PSSUBHND@psovmhcm.phoenix.nga (TNS V1-V3)        PSSUBHND@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP    psovmhcm.phoenix.nga    PSPUBDSP@psovmhcm.phoenix.nga (TNS V1-V3)        PSPUBDSP@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP    psovmhcm.phoenix.nga    PSPUBHND@psovmhcm.phoenix.nga (TNS V1-V3)        PSPUBHND@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP    psovmhcm.phoenix.nga    PSBRKDSP@psovmhcm.phoenix.nga (TNS V1-V3)        PSBRKDSP@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP    psovmhcm.phoenix.nga    PSBRKHND@psovmhcm.phoenix.nga (TNS V1-V3)        PSBRKHND@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP    psovmhcm.phoenix.nga    PSANALYTICSRV@psovmhcm.phoenix.nga (TNS V1-V3)   PSANALYTICSRV@psovmhcm.phoenix.nga (TNS V1-
SYSBKP    psovmhcm.phoenix.nga    PSANALYTICSRV@psovmhcm.phoenix.nga (TNS V1-V3)   PSANALYTICSRV@psovmhcm.phoenix.nga (TNS V1-
SYSBKP    psovmhcm.phoenix.nga    PSANALYTICSRV@psovmhcm.phoenix.nga (TNS V1-V3)   PSANALYTICSRV@psovmhcm.phoenix.nga (TNS V1-
SYSBKP    psovmhcm.phoenix.nga    PSSAMSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSSAMSRV@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP    psovmhcm.phoenix.nga    PSQRYSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSQRYSRV@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP    psovmhcm.phoenix.nga    PSAPPSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSAPPSRV@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP    psovmhcm.phoenix.nga    PSAPPSRV@psovmhcm.phoenix.nga (TNS V1-V3)        HR_DR_SELECTION_UI
SYSBKP    psovmhcm.phoenix.nga    PSMONITORSRV@psovmhcm.phoenix.nga (TNS V1-V3)    PSMONITORSRV@psovmhcm.phoenix.nga (TNS V1-
SYSBKP    psovmhcm.phoenix.nga    PSPRCSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSPRCSRV@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP    psovmhcm.phoenix.nga    PSDSTSRV@psovmhcm.phoenix.nga (TNS V1-V3)        PSDSTSRV@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP    psovmhcm.phoenix.nga    PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)         PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP    psovmhcm.phoenix.nga    PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)         PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP    psovmhcm.phoenix.nga    PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)         PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP    psovmhcm.phoenix.nga    PSMSTPRC@psovmhcm.phoenix.nga (TNS V1-V3)        PSMSTPRC@psovmhcm.phoenix.nga (TNS V1-V3)
PUBLIC    psovmhcmdb.phoenix.nga oracle@psovmhcmdb.phoenix.nga (TNS V1-V3)        oracle@psovmhcmdb.phoenix.nga (TNS V1-V3)
PUBLIC    psovmhcmdb.phoenix.nga oracle@psovmhcmdb.phoenix.nga (TNS V1-V3)        oracle@psovmhcmdb.phoenix.nga (TNS V1-V3)
PUBLIC    psovmhcmdb.phoenix.nga oracle@psovmhcmdb.phoenix.nga (TNS V1-V3)        oracle@psovmhcmdb.phoenix.nga (TNS V1-V3)
PUBLIC    psovmhcmdb.phoenix.nga oracle@psovmhcmdb.phoenix.nga (TNS V1-V3)        oracle@psovmhcmdb.phoenix.nga (TNS V1-V3)
SYS       psovmhcmdb2             sqlplus@psovmhcmdb2 (TNS V1-V3)                  sqlplus@psovmhcmdb2 (TNS V1-V3)

Ok, the HR_DR_SELECTION_UI we defined earlier as read-only component is running on the secondary database. However similarly to the batch server which run AE onto the secondary database, it runs few queries onto the primary database. Let’s have a look into a trace file.

8.5 Set the TraceSQL=7
After setting the TraceSQL, re-run the same transaction as above, and check for the generated file. Here below an extract of that file :
…<snipped>…
H91TMPLT RC=0 Dur=0.000007 Disconnect
H91TMPLT RC=0 Dur=0.000005 Commit
H91TMPLT RC=0 Dur=0.000007 Disconnect
notSamTran RC=0 Dur=0.000028 Open Cursor Handle=000000000FC0DB08
notSamTran RC=0 Dur=0.000009 Open Cursor Handle=000000000FC0DB08
H91TMPLT RC=0 Dur=0.000014 Disconnect
H91TMPLT RC=0 Dur=0.000004 Commit
H91TMPLT RC=0 Dur=0.000007 Disconnect
notSamTran RC=0 Dur=0.000011 Open Cursor Handle=000000000FC0DB08
notSamTran RC=0 Dur=0.000008 Open Cursor Handle=000000000FC0DB08
H91TMPLT RC=0 Dur=0.000008 Disconnect
H91TMPLT RC=0 Dur=0.000004 Commit
H91TMPLT RC=0 Dur=0.000006 Disconnect
notSamTran RC=0 Dur=0.000011 Open Cursor Handle=000000000FC0D9D0
H91STBY RC=0 Dur=0.000005 Commit
H91STBY RC=0 Dur=0.000008 Disconnect
notSamTran RC=0 Dur=0.000008 Open Cursor Handle=000000000FC0D9D0
H91STBY RC=0 Dur=0.000148 COM Stmt=SELECT A.TEXT_ID , TO_CHAR(A.EFFDT,'YYYY-MM-DD') , A.HR_SSTEXT_KEY1 , A.HR_SSTEXT_KEY2 ,
H91STBY RC=0 Dur=0.000005 Bind-1 type=2 length=3 value=HHR
H91STBY RC=0 Dur=0.000005 Bind-2 type=2 length=4 value=DRPT
H91STBY RC=0 Dur=0.000005 Bind-3 type=2 length=11 value=GROUP_INSTR
H91STBY RC=0 Dur=0.000004 Bind-4 type=26 length=10 value=2011-03-14
H91STBY RC=0 Dur=0.000004 Bind-5 type=2 length=13 value=HR_EE_INF_MGR
H91STBY RC=0 Dur=0.000004 Bind-6 type=2 length=1 value=
H91STBY RC=0 Dur=0.000004 Bind-7 type=2 length=1 value=
H91STBY RC=0 Dur=0.000005 Bind-8 type=2 length=1 value=
H91STBY RC=0 Dur=0.000005 Bind-9 type=2 length=1 value=
H91STBY RC=0 Dur=0.000004 Bind-10 type=2 length=1 value=
H91STBY RC=0 Dur=0.000006 Commit
H91STBY RC=0 Dur=0.000043 Disconnect
notSamTran RC=0 Dur=0.000013 Open Cursor Handle=000000000FC0D9D0
H91STBY RC=0 Dur=0.000006 Commit
H91STBY RC=0 Dur=0.000008 Disconnect
notSamTran RC=0 Dur=0.000009 Open Cursor Handle=000000000FC0D9D0
H91STBY RC=0 Dur=0.000126 COM Stmt=SELECT A.TEXT_ID , TO_CHAR(A.EFFDT,'YYYY-MM-DD') , A.HR_SSTEXT_KEY1 , A.HR_SSTEXT_KEY2 ,
H91STBY RC=0 Dur=0.000005 Bind-1 type=2 length=3 value=HHR
H91STBY RC=0 Dur=0.000005 Bind-2 type=2 length=4 value=DRPT
H91STBY RC=0 Dur=0.000006 Bind-3 type=2 length=15 value=GROUP_GROUP_HDR
H91STBY RC=0 Dur=0.000006 Bind-4 type=26 length=10 value=2011-03-14
H91STBY RC=0 Dur=0.000005 Bind-5 type=2 length=13 value=HR_EE_INF_MGR
H91STBY RC=0 Dur=0.000006 Bind-6 type=2 length=1 value=
…<snipped>…
Like for the batch server, the application server start running queries onto the primary database (H91TMPLT), then switch to the secondary database (H91STBY) for the main part of the component.

So, now we have batch server and application server able to run some queries onto the secondary database in read-only mode. But be aware, none of the Peoplesoft processes are purely read-only, that’s the reason it’s still continue to start/end transactions onto the primary database, and also the need for the remote synonyms.

Enjoy it !

Nicolas.

PSOVM and Active Data Guard : Batch Server

2011-03-13T18:04:00.002+01:00

After setting a Physical Standby Database and enabling Active Data Guard on Peoplesoft OVM, it is probably the nicest part for the Peoplesoft guys. Going further and look for Batch processes running onto that secondary database. Much useful for the big and heavy report, for instance.
As said earlier, the latest PSOVM is coming with the Peopletools 8.51, we can get all the latest technologies offered.
The new property regarding the standby database in the process scheduler configuration file allow us such thing, here in red from psprcs.cfg
[Startup]
;=========================================================================
; Database Signon settings
;=========================================================================
DBName=
DBType=
UserId=
UserPswd=
ConnectId=
ConnectPswd=
ServerName=
StandbyDBName=
StandbyDBType=
StandbyUserId=
StandbyUserPswd=
It is working only for an enabled Oracle Active Data Guard database.
At the end of this stage, the global architecture will be as follow (in red, the change compared to the previous state) :

1. Required scripts
Warning : 4 scripts are required to set up the configuration to run processes on read-only database through the Batch Server. Unfortunately, PSOVM does not offer any default scripts ($PS_HOME/scripts), so an additional Peoplesoft home installation is required before going further.
Those scripts are psadmin.sql ($PS_HOME/scripts/unix), createlocalsynonyms.sql, createdblinktoprimarydb.sql and createremotesynonyms.sql (from $PS_HOME/scripts). They are delivered on default Peoplesoft installation, but so far, not in PSOVM.
Eventually, here the copy onto the primary site (hosting primary database ) from an other Linux Peoplesoft installation I made on my own :
[root@psovmhcmdb ~]# su - oracle
[oracle@psovmhcmdb ~]$ scp root@192.168.1.141:/apps/psoft/pt851/scripts/unix/psadmin.sql .
root@192.168.1.141's password:
psadmin.sql                                   100% 2714     2.7KB/s   00:00
[oracle@psovmhcmdb ~]$ scp root@192.168.1.141:/apps/psoft/pt851/scripts/createlocalsynonyms.sql .
root@192.168.1.141's password:
createlocalsynonyms.sql                       100% 1986     1.9KB/s   00:01
[oracle@psovmhcmdb ~]$ scp root@192.168.1.141:/apps/psoft/pt851/scripts/createdblinktoprimarydb.sql .
root@192.168.1.141's password:
createdblinktoprimarydb.sql                   100% 1739     1.7KB/s   00:00
[oracle@psovmhcmdb ~]$ scp root@192.168.1.141:/apps/psoft/pt851/scripts/createremotesynonyms.sql .
root@192.168.1.141's password:
createremotesynonyms.sql                      100% 4485     4.4KB/s   00:00

2. Create a secondary ACCESSID/SYMBOLICID on primary db – psadmin.sql
2.1 PSADMIN.SQL on primary database
Run the script psadmin.sql will create an other Peoplesoft “owner” (ACCESSID) beside the default one SYSADM :
[oracle@psovmhcmdb ~]$ export ORACLE_SID=H91TMPLT
[oracle@psovmhcmdb ~]$ sqlplus / as sysdba
@psadmin
=> user : SYSBKP
=> pwd : SYSBKP
=> default permanent tablespace : psdefault

2.2 Insert the corresponding line in PS.PSDBOWNER for the new ACCESSID linked to the standby database
SQL> conn sysbkp/SYSBKP
Connected.
SQL> insert into ps.psdbowner values ('H91STBY','SYSBKP');

1 row created.
SQL> commit;

2.3 Add a new SYMBOLICID
Open Application Designer, and create a new SYMBOLICID for the newly created ACCESSID (step 2.1)

3. Create a dedicated application user attached to the secondary SYMBOLICID
Within the front-end application, copy a user (e.g. PS) which is able to manage process scheduler and application server.

Make sure you set the secondary SYMBOLICID created earlier on step 2.3 (here SYSADM2) :

We can check the PSACCESSPRFL table to see the new line :
SQL> select * from sysadm.psaccessprfl;
SYMBOLICID                          VERSION
-------------------------------- ----------
ACCESSID
----------------------------------------------------------------
ACCESSPSWD                                                        ENCRYPTED
---------------------------------------------------------------- ----------
SYSADM2                                 157
sBzLcoZSrag=
sBzLcoZSrag=                                                              1
SYSADM1                                   1
sBzLcYlPrag=
sBzLcYlPrag=                                                              1

4. Create database link on primary db to the primary db – createdblinktoprimarydb.sql
Before going further, a small explanation. Running a process through the process scheduler is never purely read-only even if the process itself is only selecting data. The process scheduler has to update a couple of tables, for instance to state the batch status. So, here it will be used a very nice little tricky thing. We’ll create a database link to the primary database on the primary (remember, whether the secondary database is open, it is open in read-only mode), it will become a remote database link onto the secondary database once replicated (it is assume the tnsnames.ora file on primary and secondary are same).
On the primary database, connected as the secondary ACCESSID SYSADM2 run :
SQL> CREATE DATABASE LINK PRIMARY CONNECT TO sysadm IDENTIFIED BY SYSADM USING 'H91TMPLT';

Database link created.

5. Create local synonyms – createlocalsynonyms.sql
The local synonyms are synonyms for the read-only objects (tables and views). Bear in mind to run it whenever you create customized records.
On the primary database, connected as the secondary ACCESSID SYSADM2 run the following script, it will create two subsequent scripts to be run :
[oracle@psovmhcmdb ~]$ more createlocalsynonyms.sql
...
SET ECHO ON

REM Create local synonyms for tables
SET HEADING OFF
Spool CREATELOCALTABLESYNONYMS.SQL
SELECT 'CREATE SYNONYM ' || TABLE_NAME || ' FOR SYSADM.' || TABLE_NAME || ';'
FROM ALL_TABLES
WHERE OWNER = 'SYSADM'
ORDER BY TABLE_NAME
;
Spool off
REM Create local synonyms for views
Spool CREATELOCALVIEWSYNONYMS.SQL
SET HEADING OFF
SELECT 'CREATE SYNONYM ' || VIEW_NAME || ' FOR SYSADM.' || VIEW_NAME || ';'
FROM ALL_VIEWS
WHERE OWNER = 'SYSADM'
ORDER BY VIEW_NAME
;
Spool off
[oracle@psovmhcmdb ~]$ sqlplus sysbkp/SYSBKP
SQL*Plus: Release 11.1.0.7.0 - Production on Fri Mar 11 10:11:06 2011
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> @createlocalsynonyms.sql
...
<snipped>
...
SQL> !ls
createdblinktoprimarydb.sql CREATELOCALTABLESYNONYMS.SQL createremotesynonyms.sql psadmin.sql scripts templates
createlocalsynonyms.sql CREATELOCALVIEWSYNONYMS.SQL psadmin.log scp.sh setup
SQL> @CREATELOCALTABLESYNONYMS.SQL
...
<snipped>
...
SQL> @CREATELOCALVIEWSYNONYMS.SQL
...
<snipped>
...
SQL>

6. Create remote synonyms – createremotesynonyms.sql
The remote synonyms are synonyms for the read-writable objects (the tables updated by the process scheduler itself). Bear in mind to run it whenever you create customized records.
On the primary database, connected as the secondary ACCESSID SYSADM2 run :
SQL> @createremotesynonyms.sql
...
<snipped>
...
SQL> Spool CREATEREMOTESYNONYMS.LOG
SQL>
SQL> CREATE or REPLACE SYNONYM PS_AE_QE_AETEST_TAO1 FOR PS_AE_QE_AETEST_TAO1@PRIMARY;

Synonym created.
...
<snipped>
...
SQL> CREATE or REPLACE SYNONYM PS_BAT_TIMINGS_FN FOR PS_BAT_TIMINGS_FN@PRIMARY;
Synonym created.
SQL>
SQL> Spool off

7. On the secondary site, confirm everything has been replicated
SQL> conn sysbkp/SYSBKP
Connected.
SQL> select * from ps.psdbowner;
DBNAME                           OWNERID
-------------------------------- --------------------------------
H91STBY                          SYSBKP
H91TMPLT                         SYSADM
SQL> select count(*), object_type from user_objects group by object_type;
COUNT(*) OBJECT_TYPE
---------- ----------------------------------------------------------------------------
         1 DATABASE LINK
     47701 SYNONYM

8. Configure the Batch server
8.1 Configure the tnsnames.ora file, it must contain both databases (primary and secondary)
[root@psovmhcm ~]# cat /etc/tnsnames.ora
H91TMPLT=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.1.146)(PORT=1521)))(CONNECT_DATA=(SERVER=DEDICATED)(SID=H91TMPLT)))
H91STBY=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.1.148)(PORT=1521)))(CONNECT_DATA=(SERVER=DEDICATED)(SID=H91TMPLT)))
[root@psovmhcm ~]#

8.2 Modify the psprcs.cfg file
[psadm2@psovmhcm ~]$ pwd
/home/psadm2
[psadm2@psovmhcm ~]$ ls
java0.log oradiag_psadm2 psft
[psadm2@psovmhcm ~]$ cd psft/pt/8.51/appserv/prcs/PRCSDOM/
[psadm2@psovmhcm PRCSDOM]$
[psadm2@psovmhcm PRCSDOM]$ more psprcs.cfg

[Startup]
;=========================================================================
; Database Signon settings
;=========================================================================
DBName=H91TMPLT
DBType=ORACLE
UserId=PS
UserPswd=PS
ConnectId=people
ConnectPswd=peop1e
ServerName=192.168.1.146
StandbyDBName=H91STBY
StandbyDBType=ORACLE
StandbyUserId=PSBKP
StandbyUserPswd=PSBKP
…

8.3 Reconfigure the modified PRCSDOM batch server
[psadm2@psovmhcm PRCSDOM]$ cd $PS_HOME/appserv
[psadm2@psovmhcm appserv]$ ./psadmin
PSADMIN -- Tools Release: 8.51.02
Copyright (c) 1996, 2010, Oracle. All rights reserved.
--------------------------------
PeopleSoft Server Administration
--------------------------------
1) Application Server
2) Process Scheduler
3) Search Server
4) Replicate Config Home
q) Quit
Command to execute (1-4, q): 2
--------------------------------------------
PeopleSoft Process Scheduler Administration
--------------------------------------------
1) Administer a domain
2) Create a domain
3) Delete a domain
4) Import domain configuration
q) Quit
Command to execute (1-4, q) : 1
Domain list:
   1) PRCSDOM
Select domain: 1
--------------------------------------------
PeopleSoft Process Scheduler Administration
--------------------------------------------
     Domain Name: PRCSDOM
1) Boot this domain
2) Domain shutdown menu
3) Domain status menu
4) Configure this domain
5) TUXEDO command line (tmadmin)
6) Edit configuration/log files menu
7) Clean IPC resources of this Domain
q) Quit
Command to execute (1-7, q) : 4
This option will shutdown the domain.
Do you want to continue? (y/n) [n] :y
<…snipped…>
----------------------------------------------
Quick-configure menu -- domain: PRCSDOM
----------------------------------------------
      Features                      Settings
     ==========                    ==========
1) App Engine        : Yes    5) DBNAME     :[H91TMPLT]
2) Master Scheduler : Yes    6) DBTYPE     :[ORACLE]
                                7) PrcsServer :[OVMDEMO]
                                8) UserId     :[PS]
                                9) UserPswd   :[PS]
                               10) ConnectID :[people]
                               11) ConnectPswd:[peop1e]
                               12) ServerName :[192.168.1.146]
                               13) Log/Output Dir:[%PS_SERVDIR%/log_output]
                               14) SQRBIN     :[%PS_HOME%/bin/sqr/%PS_DB%/bin]
                               15) AddToPATH :[.]
      Actions
     =========
3) Load config as shown
4) Custom configuration
h) Help for this menu
q) Return to previous menu
HINT: Enter 5 to edit DBNAME, then 3 to load
Enter selection (1-15, h, or q): 3
Performing load prechecks ...
Loading validation table...
setting DBName=H91TMPLT
setting DBType=ORACLE
setting UserId=PS
setting UserPswd=PS
setting ConnectId=people
setting ConnectPswd=peop1e
setting ServerName=192.168.1.146
setting PrcsServerName=OVMDEMO
setting Log/Output Directory=%PS_SERVDIR%/log_output
setting Add to PATH=.
setting SQRBIN=%PS_HOME%/bin/sqr/%PS_DB%/bin
New CFG file written with modified Startup parameters
Log Directory entry not found in configuration file.
Setting Log Directory to the default... [PS_SERVDIR/LOGS]
Spawning enabled for server PSDSTSRV.
Configuration file successfully created.
CFG setting changes completed
Loading configuration...
Domain configuration complete.

8.4 Start the modified PRCSDOM batch server
--------------------------------------------
PeopleSoft Process Scheduler Administration
--------------------------------------------
     Domain Name: PRCSDOM
1) Boot this domain
2) Domain shutdown menu
3) Domain status menu
4) Configure this domain
5) TUXEDO command line (tmadmin)
6) Edit configuration/log files menu
7) Clean IPC resources of this Domain
q) Quit
Command to execute (1-7, q) : 1
Archived a copy of the domain configuration to /home/psadm2/psft/pt/8.51/appserv/prcs/PRCSDOM/Archive/psprcs.cfg
Attempting to boot bulletin board...
tmadmin - Copyright (c) 2007-2008 Oracle.
Portions * Copyright 1986-1997 RSA Data Security, Inc.
All Rights Reserved.
Distributed under license by Oracle.
Tuxedo is a registered trademark.
No bulletin board exists. Entering boot mode.
> INFO: Oracle Tuxedo, Version 10.3.0.0, 64-bit, Patch Level 031
Booting admin processes ...
exec BBL -A :
        process id=1910 ... Started.
1 process started.
Attaching to active bulletin board.
> Attempting to boot ...
INFO: Oracle Tuxedo, Version 10.3.0.0, 64-bit, Patch Level 031
Booting server processes ...
exec PSMSTPRC -o ./LOGS/stdout -e ./LOGS/stderr -A -- -CD H91TMPLT -PS OVMDEMO -A start -S PSMSTPRC :
        process id=1914 ... Started.
exec PSAESRV -o ./LOGS/stdout -e ./LOGS/stderr -- -CD H91TMPLT -S PSAESRV :
        process id=1919 ... Started.
exec PSAESRV -o ./LOGS/stdout -e ./LOGS/stderr -- -CD H91TMPLT -S PSAESRV :
        process id=1923 ... Started.
exec PSAESRV -o ./LOGS/stdout -e ./LOGS/stderr -- -CD H91TMPLT -S PSAESRV :
        process id=1927 ... Started.
exec PSDSTSRV -o ./LOGS/stdout -e ./LOGS/stderr -p 1,600:1,1 -sPostReport -- -CD H91TMPLT -PS OVMDEMO -A start -S PSDSTSRV :
        process id=1931 ... Started.
exec PSPRCSRV -o ./LOGS/stdout -e ./LOGS/stderr -sInitiateRequest -- -CD H91TMPLT -PS OVMDEMO -A start -S PSPRCSRV :
        process id=1936 ... Started.
exec PSMONITORSRV -o ./LOGS/stdout -e ./LOGS/stderr -A -- -ID 51639 -PS OVMDEMO -S PSMONITORSRV :
        process id=1944 ... Started.
7 processes started.

8.5 On secondary database, check for the connections
SQL> conn / as sysdba
Connected.
SQL> select instance_name,host_name from v$instance;
INSTANCE_NAME    HOST_NAME
---------------- ----------------------------------------------------------------
H91TMPLT         psovmhcmdb2
SQL> select username,machine,program from v$session where username is not null;
USERNAME   MACHINE                        PROGRAM
---------- ------------------------------ ------------------------------------------------
SYSBKP     psovmhcm.phoenix.nga           PSMONITORSRV@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP     psovmhcm.phoenix.nga           PSPRCSRV@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP     psovmhcm.phoenix.nga           PSDSTSRV@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP     psovmhcm.phoenix.nga           PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP     psovmhcm.phoenix.nga           PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP     psovmhcm.phoenix.nga           PSAESRV@psovmhcm.phoenix.nga (TNS V1-V3)
SYSBKP     psovmhcm.phoenix.nga           PSMSTPRC@psovmhcm.phoenix.nga (TNS V1-V3)
PUBLIC     psovmhcmdb.phoenix.nga         oracle@psovmhcmdb.phoenix.nga (TNS V1-V3)
PUBLIC     psovmhcmdb.phoenix.nga         oracle@psovmhcmdb.phoenix.nga (TNS V1-V3)
PUBLIC     psovmhcmdb.phoenix.nga         oracle@psovmhcmdb.phoenix.nga (TNS V1-V3)
PUBLIC     psovmhcmdb.phoenix.nga         oracle@psovmhcmdb.phoenix.nga (TNS V1-V3)
SYS        psovmhcmdb2                    sqlplus@psovmhcmdb2 (TNS V1-V3)

12 rows selected.
We can see in the above output the process scheduler processes coming in with the secondary ACCESSID connection user.

9. Test, DDDAUDIT setting to read-only
9.1 We’ll first try to run a very well known process onto that secondary database. We first have to make the process as “read-only” on the process definition page.

9.2 Run the process DDDAUDIT

9.3 First result
Well, according to the databases connections, nothing is coming onto the standby database, on the contrary, a sqr connection is made from the client batch server onto the primary database.
The command line used to launch the SQR is not changed compared to a default one, still pointing to the primary database…
SQR Command = /opt/oracle/psft/pt/tools/bin/sqr/ORA/bin/sqr /opt/oracle/psft/pt/tools/sqr/dddaudit.sqr */*@H91TMPLT   "-o/home/psadm2/psft/pt/8.51/appserv/prcs/PRCSDOM/log_output/SQR_DDDAUDIT_851/dddaudit_851.out" -xb -xi "-i/home/psadm2/psft/pt/8.51/appserv/prcs/PRCSDOM/log_output/SQR_DDDAUDIT_851/,/opt/oracle/psft/pt/tools/sqr/,/,/,/" -zif/opt/oracle/psft/pt/tools/sqr/pssqr.unx "-f/home/psadm2/psft/pt/8.51/appserv/prcs/PRCSDOM/log_output/SQR_DDDAUDIT_851/dddaudit_851.PDF" -PRINTER:PD    H91TMPLT 851 PS psovmhcm
A bit disappointing, but there’s an clear explanation, SQR and COBOL processes are not designed yet to run on a standby database, despite the read-only property on the process definition page. It was well explained during one of the sessions of the last Open World as I reported on OOW2010 – Day 4. It is planned for a future version, you can read it as well on the Peopletools 8.51 roadmap.
So, no SQR on standby database, let’s try the simplest program ever, AEMINITEST.

10. Test, AEMINITEST setting to read-only
10.1 Make the AEMINITEST read-only

10.2 Run the AEMINITEST
Once it is running, we can see an incoming connection to the primary from the secondary database (as SYSADM – through the database link) to update the process scheduler’s tables :
Here an output from the primary database :
USERNAME    MACHINE                  PROGRAM
----------- ------------------------ ------------------------------------------------
SYSADM      psovmhcm.phoenix.nga     PSPRCSRV@psovmhcm.phoenix.nga (TNS V1-V3)
SYSADM      psovmhcmdb2              oracle@psovmhcmdb2 (TNS V1-V3)               <--
SYSADM      psovmhcm.phoenix.nga     PSMONITORSRV@psovmhcm.phoenix.nga (TNS V1-V3)

I was setting the SQLTrace (=7) on Process scheduler to see how it is behave when running a read-only process. It is rather interesting to see the trace file :
=> it connect onto the primary database to retrieve the object type and few other information.
H91TMPLT RC=0 Dur=0.000993 COM Stmt=SELECT VERSION FROM PSVERSION WHERE OBJECTTYPENAME = 'SYS'
H91TMPLT RC=0 Dur=0.000069 COM Stmt=SELECT OBJECTTYPENAME, VERSION FROM PSVERSION
H91TMPLT RC=0 Dur=0.000128 COM Stmt=SELECT MESSAGE_SET_NBR FROM PSMSGSETDEFN WHERE VERSION > :1
H91TMPLT RC=0 Dur=0.000004 Bind-1 type=8 length=4 value=3
H91TMPLT RC=0 Dur=0.000047 COM Stmt=SELECT SETCNTRLVALUE FROM PS_SET_CNTRL_TBL WHERE VERSION > :1
H91TMPLT RC=0 Dur=0.000004 Bind-1 type=8 length=4 value=3
H91TMPLT RC=0 Dur=0.000079 COM Stmt=SELECT PRCSTYPE, PRCSNAME FROM PS_PRCSDEFN WHERE VERSION > :1
H91TMPLT RC=0 Dur=0.000005 Bind-1 type=8 length=4 value=3
H91TMPLT RC=0 Dur=0.000060 COM Stmt=SELECT SERVERNAME FROM PS_SERVERDEFN WHERE VERSION > :1
H91TMPLT RC=0 Dur=0.000005 Bind-1 type=8 length=4 value=3
H91TMPLT RC=0 Dur=0.000048 COM Stmt=SELECT PRCSTYPE, OPSYS, DBTYPE FROM PS_PRCSTYPEDEFN WHERE VERSION > :1
H91TMPLT RC=0 Dur=0.000004 Bind-1 type=8 length=4 value=3
H91TMPLT RC=0 Dur=0.000064 COM Stmt=SELECT PRCSJOBNAME FROM PS_PRCSJOBDEFN WHERE VERSION > :1
H91TMPLT RC=0 Dur=0.000036 Bind-1 type=8 length=4 value=3
H91TMPLT RC=0 Dur=0.000085 COM Stmt=SELECT URL_ID FROM PSURLDEFN WHERE VERSION > :1 UNION SELECT URL_ID FROM PSURLDEL
H91TMPLT RC=0 Dur=0.000004 Bind-1 type=8 length=4 value=3
H91TMPLT RC=0 Dur=0.000005 Bind-2 type=8 length=4 value=3
H91TMPLT RC=0 Dur=0.000000 COM Stmt=SELECT SCOPRID, SCLANG FROM PSSCDICTDEFN WHERE VERSION > :1
H91TMPLT RC=0 Dur=0.000000 Bind-1 type=8 length=4 value=3
H91TMPLT RC=0 Dur=0.000005 Commit
H91TMPLT RC=0 Dur=0.000049 Disconnect
=> it connect onto the secondary database to run the AE, even some update appear to run onto the standby (which work fine since, as explained earlier, it is updating remote synonyms tables) :
H91STBY RC=0 Dur=0.018112 COM Stmt=SELECT 'PS_DOES_TABLE_EXIST' FROM PSOPTIONS
H91STBY RC=0 Dur=0.001922 COM Stmt=SELECT DBLENGTHTYPE,LANGUAGE_CD,MULTICURRENCY,MULTIJOB,MULTICOMPANY,HELP_CONTEXT_LAST,GRANT_A
H91STBY RC=0 Dur=0.000084 Disconnect
notSamTran RC=0 Dur=0.000021 Open Cursor Handle=0000000009954E60
H91STBY RC=0 Dur=0.000041 Disconnect
notSamTran RC=0 Dur=0.000012 Open Cursor Handle=0000000009954E60
H91STBY RC=0 Dur=0.000057 COM Stmt=SELECT JOBINSTANCE, MAINJOBINSTANCE FROM PSPRCSRQST WHERE PRCSINSTANCE = :1
H91STBY RC=0 Dur=0.000005 Bind-1 type=8 length=4 value=852
H91STBY RC=0 Dur=0.000052 Disconnect
notSamTran RC=0 Dur=0.000073 Open Cursor Handle=0000000009954E60
H91STBY RC=0 Dur=0.000119 COM Stmt=UPDATE PSPRCSRQST SET RUNSTATUS = :1,PRCSRTNCD = :2,CONTINUEJOB = :3,BEGINDTTM = CAST(SYSTIMES
H91STBY RC=0 Dur=0.000004 Bind-1 type=2 length=1 value=7
H91STBY RC=0 Dur=0.000004 Bind-2 type=6 length=4 value=0
H91STBY RC=0 Dur=0.000004 Bind-3 type=6 length=4 value=0
H91STBY RC=0 Dur=0.000004 Bind-4 type=8 length=4 value=852
H91STBY RC=0 Dur=0.000030 COM Stmt=UPDATE PSPRCSQUE SET RUNSTATUS = :1,PRCSRTNCD = :2,CONTINUEJOB = :3 WHERE PRCSINSTANCE = :4
H91STBY RC=0 Dur=0.000004 Bind-1 type=2 length=1 value=7
H91STBY RC=0 Dur=0.000005 Bind-2 type=6 length=4 value=0
H91STBY RC=0 Dur=0.000005 Bind-3 type=6 length=4 value=0
H91STBY RC=0 Dur=0.000005 Bind-4 type=8 length=4 value=852
H91STBY RC=0 Dur=0.004184 Commit
H91STBY RC=0 Dur=0.000019 Disconnect
H91STBY RC=0 Dur=0.000518 COM Stmt=SELECT PROCESS_INSTANCE, AE_RTNCD, AE_CRITICAL_PHASE, AE_STEP_DONE, MARKET, TO_CHAR(ASOF_DT,'Y
H91STBY RC=0 Dur=0.000005 Bind-1 type=2 length=2 value=PS
H91STBY RC=0 Dur=0.000005 Bind-2 type=2 length=8 value=psovmhcm
H91STBY RC=0 Dur=0.000004 Bind-3 type=2 length=10 value=AEMINITEST
H91STBY RC=0 Dur=0.000090 COM Stmt=SELECT OPRID, RUN_CNTL_ID, AE_APPLID FROM PS_AERUNCONTROL WHERE PROCESS_INSTANCE = :1
H91STBY RC=0 Dur=0.000005 Bind-1 type=8 length=4 value=852
H91STBY RC=0 Dur=0.000077 COM Stmt=SELECT OPRID, RUN_CNTL_ID, AE_APPLID, MIN(AE_DISABLE_RESTART) FROM PS_AETEMPTBLMGR WHERE PROCE
H91STBY RC=0 Dur=0.000005 Bind-1 type=8 length=4 value=852
H91STBY RC=0 Dur=0.000095 COM Stmt=INSERT INTO PS_AERUNCONTROL (PROCESS_INSTANCE, OPRID, RUN_CNTL_ID, AE_APPLID, RUN_DTTM, AE_RTN
H91STBY RC=0 Dur=0.000004 Bind-1 type=8 length=4 value=852
H91STBY RC=0 Dur=0.000004 Bind-2 type=2 length=2 value=PS
H91STBY RC=0 Dur=0.000004 Bind-3 type=2 length=8 value=psovmhcm
H91STBY RC=0 Dur=0.000004 Bind-4 type=2 length=10 value=AEMINITEST
notSamTran RC=0 Dur=0.000052 Open Cursor Handle=0000000009954F98

=> in the end, the process scheduler reconnect one more time onto the primary database :
H91STBY RC=0 Dur=0.000217 COM Stmt=UPDATE PS_AETEMPTBLMGR SET AE_DEDICATED = 1 WHERE 0 = 1
H91STBY RC=0 Dur=0.002722 Commit
notSamTran RC=0 Dur=0.000026 Open Cursor Handle=0000000009954E60
H91STBY RC=0 Dur=0.000065 COM Stmt=UPDATE PSPRCSRQST SET RUNSTATUS = :1,PRCSRTNCD = :2,CONTINUEJOB = :3,ENDDTTM = CAST(SYSTIME
H91STBY RC=0 Dur=0.000004 Bind-1 type=2 length=1 value=9
H91STBY RC=0 Dur=0.000005 Bind-2 type=6 length=4 value=0
H91STBY RC=0 Dur=0.000005 Bind-3 type=6 length=4 value=1
H91STBY RC=0 Dur=0.000005 Bind-4 type=8 length=4 value=852
H91STBY RC=0 Dur=0.000042 COM Stmt=UPDATE PSPRCSQUE SET RUNSTATUS = :1,PRCSRTNCD = :2,CONTINUEJOB = :3 WHERE PRCSINSTANCE = :4
H91STBY RC=0 Dur=0.000013 Bind-1 type=2 length=1 value=9
H91STBY RC=0 Dur=0.000004 Bind-2 type=6 length=4 value=0
H91STBY RC=0 Dur=0.000004 Bind-3 type=6 length=4 value=1
H91STBY RC=0 Dur=0.000004 Bind-4 type=8 length=4 value=852
H91STBY RC=0 Dur=0.003032 Commit
H91STBY RC=0 Dur=0.000023 Disconnect
H91TMPLT RC=0 Dur=0.000143 Disconnect
H91TMPLT RC=0 Dur=0.000109 Disconnect
H91TMPLT RC=0 Dur=0.000114 Disconnect
H91TMPLT RC=0 Dur=0.000100 Disconnect
H91TMPLT RC=0 Dur=0.000140 Disconnect
H91TMPLT RC=0 Dur=0.000140 Disconnect
H91TMPLT RC=0 Dur=0.000004 Commit
H91TMPLT RC=0 Dur=0.000124 Disconnect
H91STBY RC=0 Dur=0.000005 Commit
H91STBY RC=0 Dur=0.000102 Disconnect
notSamTran RC=0 Dur=0.000018 Open Cursor Handle=0000000009954F98
H91TMPLT RC=0 Dur=0.000096 COM Stmt=SELECT UPPER(MACHINENAME),PROCESSID,TO_CHAR(CAST((PTATREGDTTM) AS TIMESTAMP),'YYYY-MM-DD-H
H91TMPLT RC=0 Dur=0.000005 Commit
H91TMPLT RC=0 Dur=0.000054 Disconnect
By curiosity, I revert the read-only property to the default unchecked (read-write) for the AEMINITEST, and re-run it. No surprise, the tracefile shows only primary database connections.

Right now, except failover, we got a very nice and complete PSOVM environment ! Enjoy it !

Read my next article :

Application Server on Data Guard

Nicolas.

Documentation, find out more :
http://download.oracle.com/docs/cd/E18083_01/pt851pbr0/eng/psbooks/tadm/book.htm?File=tadm/htm/tadm13.htm#H4064

PSOVM and Active Data Guard : enabling ADG

2011-03-13T15:32:00.003+01:00

To go further, it is assumed you have set a Physical Standby Database on Peoplesoft OVM as shown in my previous blog entry : PSOVM and Activate Data Guard : Physical Standby Database
As explained in previous post, we created a Physical Standby Database, it should be relatively straightforward to enable the Active Data Guard. That will allow end users to query (in read only mode) the standby database whilst the redo are applying onto that standby database, feature known to be real-time query.
At the end of this stage, the architecture will be as follow (in blue the change compared to the previous post) :

1. dg_broker_start init parameter
Set the dg_broker_start to true on primary database and on secondary database
SQL> alter system set dg_broker_start=true;

System altered.

2. Create the dataguard configuration
On the primary site, start the Data Guard Manager client command line for the configuration settings :
[oracle@psovmhcmdb dbs]$ dgmgrl
DGMGRL for Linux: Version 11.1.0.7.0 - 64bit Production

Copyright (c) 2000, 2005, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/oracle@H91TMPLT (connection to the primary database)
Connected.
DGMGRL> create configuration psovmdgmgrl
> as primary database is H91TMPLT
> connect identifier is H91TMPLT;
Configuration "psovmdgmgrl" created with primary database "h91tmplt"
DGMGRL> add database H91STBY
> as connect identifier is H91STBY
> maintained as physical;
Database "h91stby" added
DGMGRL>
DGMGRL> enable configuration
Enabled.
DGMGRL> show configuration
Configuration
Name:                psovmdgmgrl
Enabled:             YES
Protection Mode:     MaxPerformance
Databases:
    h91tmplt - Primary database
    h91stby - Physical standby database
Fast-Start Failover: DISABLED
Current status for "psovmdgmgrl":
SUCCESS
DGMGRL>

3. Turn off the redo apply (dgmgrl)
In order to have an active data guard, we should stop the replication first (run dgmgrl on primary site) :
DGMGRL> edit database h91stby set state=apply-off;
Succeeded.
DGMGRL>

4. Read-only mode
Now, we can open the secondary database in read-only mode (on the further startups, that mode will be the default one):
SQL> alter database open read only;

Database altered.

5. Turn on the redo apply (dgmgrl)
Now, we can turn the redo apply on again (run dgmgrl on primary site)
DGMGRL> edit database h91stby set state=apply-on;
Succeeded.
DGMGRL>

6. Test
We will see if the replication is working whilst the standby database is open in read-only mode and “query-able” as SYSADM user.
6.1 On the secondary database
SQL> select instance_name,host_name from v$instance
SQL> /

INSTANCE_NAME    HOST_NAME
---------------- ----------------------------------------------------------------
H91TMPLT         psovmhcmdb2
SQL> conn sysadm/SYSADM
Connected.
SQL> select count(*) from psoprdefn;
COUNT(*)
----------
       155
SQL> select oprid from psoprdefn where trunc(LASTPSWDCHANGE)=trunc(sysdate);
no rows selected

6.2 Within the front-end application, we’ll duplicate PS user as following

6.3 And now, on the secondary database, re-run the previous query, it should return one more row
SQL> select oprid from psoprdefn where trunc(LASTPSWDCHANGE)=trunc(sysdate);

OPRID
---------------------------------------------------
NICOLAS
SQL> select count(*) from psoprdefn;
COUNT(*)
----------
156
SQL>

=> the new created user is coming to the secondary database, and we can check it directly from PSOPRDEFN (that would not be possible without Active Data Guard).

7. For the record, show the dgmgrl status (configuration and databases)
[oracle@psovmhcmdb ~]$ dgmgrl
DGMGRL for Linux: Version 11.1.0.7.0 - 64bit Production

Copyright (c) 2000, 2005, Oracle. All rights reserved.
Welcome to DGMGRL, type "help" for information.
DGMGRL> connect sys/oracle@H91TMPLT
Connected.
DGMGRL> show configuration
Configuration
Name:                psovmdgmgrl
Enabled:             YES
Protection Mode:     MaxPerformance
Databases:
    h91tmplt - Primary database
    h91stby - Physical standby database
Fast-Start Failover: DISABLED
Current status for "psovmdgmgrl":
SUCCESS
DGMGRL> show database h91stby
Database
Name:            h91stby
Role:            PHYSICAL STANDBY
Enabled:         YES
Intended State: APPLY-ON
Instance(s):
    H91TMPLT
Current status for "h91stby":
SUCCESS
DGMGRL> show database h91tmplt
Database
Name:            h91tmplt
Role:            PRIMARY
Enabled:         YES
Intended State: TRANSPORT-ON
Instance(s):
    H91TMPLT
Current status for "h91tmplt":
SUCCESS
DGMGRL>

Now we can talk, query a database without loading the primary database while the redo continue to be applied. That's really helpful, especially for users who run a lot of reports through a tier query tool. Once more, PSOVM allow us to test it easily before implementing it in real live.
But it can be not enough. An other great feature coming with the latest PSOVM and Peopletools 8.51 is the StandbyDBName configuration possiblity on Batch and AppServer. That's obviously the next step. To be continued.

Read my next articles :

Batch Server on Data Guard

Application Server on Data Guard

Documentation, find out more :
http://download.oracle.com/docs/cd/B28359_01/server.111/b28282/configbp006.htm#HABPT04477