DRAC5 on Poweredge 2900III

It may sound old hardware, but still works like a charm and pretty good. I had a chance to get a Dell Remote Access Card (DRAC5). Easy to install, a little bit less to access.
Once you configured the IP from the boot, you can access the card from a browser (this is a small webserver).
From the browser you are supposed to be able to open the console and see what happens and configure on the server just like you were sitting in front with a screen/keyboard plugged in (including on server boot, OS boot), to me that’s one of the reason to have that card. The other reason is the virtual media for remote installation onto the server from a local CD/DVD or ISO file.

However, opening the console turns Java on and you may be face to the error below (from the java console) :

6/01/2015 02:17:42:500: packet type( 0x100)
Sending packet: com.avocent.kvm.e.a.bf@19c6246 (8, 208).
javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)
    at sun.security.ssl.Handshaker.activate(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.kickstartHandshake(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source)
    at sun.security.ssl.SSLSocketImpl.writeRecord(Unknown Source)
    at sun.security.ssl.AppOutputStream.write(Unknown Source)
    at java.io.BufferedOutputStream.flushBuffer(Unknown Source)
    at java.io.BufferedOutputStream.flush(Unknown Source)
    at java.io.DataOutputStream.flush(Unknown Source)
    at com.avocent.kvm.d.b.g.b(Unknown Source)
    at com.avocent.kvm.d.b.i.run(Unknown Source)
JNLPClassLoader: Finding library jawt.dll
06/01/2015 02:17:42:500: IOException on AVSP socket.

JNLPClassLoader: Finding library avctKVMIO.dll

Solution:, comment out the following line in java.security file (C:\Program Files\Java\jre1.8.0_45\lib\security\java.security):
#jdk.tls.disabledAlgorithms=SSLv3

It worked with IE8 and Chrome. Thanks to that thread, I would be harmless.
For some reason, Firefox 38.0.5 on Windows XP 32bit refuses to make it works at all (something with an unknown error about XSLT transformation).

Note: from the documentation of the DRAC5, only web browser 32bit is supposed to work, and Java must be 1.6 or above.

Nicolas.

VMWare snapshot management

Before testing several configurations on my new brand FreeNAS server hosted on VMWare ESXi 6.0, I took a snapshot. Then run tests. The FreeNAS is composed by two virtual disks : one for the software is 20Gb, one for the data is 900Gb.
After a while, bouncing the FreeNAS guest ended in error, VMWare is complaining about disk space not enough…
No way to start it up again.

Quite surprising. Except if we know that snapshots keep increasing while the VM is running. In fact, the snapshot keep all the logs to redo the difference made. Since the data virtual disk is big, after quite some time the snapshots can fill up all your physical disk hosting the VM.
The straightaway solution is to drop the snapshots.

Subsequent solution : hosting snapshot in a much larger disk array (datastore) – by default it is hosted where the virtual disk is sitting.
For the sake, here we go :
Creating snapshots in a different location than default virtual machine directory for VMware ESXi and VMware ESX
To make it short, stop the VM, add the following lines in .vmx file of the VM, and restart :
workingDir = "new_path_location"
snapshot.redoNotWithParent = "true"

Lesson learned.

Nicolas.

VMWare ESXi 6.0 upgrade (from 5.5u2)

First off, I put the all server in maintenance mode.

Then from the burned image .iso file downloaded from the VMWare site (VMware-VMvisor-Installer-6.0.0-2494585.x86_64.iso), boot from the CD on the server, choose upgrade and… everything goes smoothly ! Unfortunately, I still do not have a remote access card to make screenshot from BIOS boot. Anyway, this is really straightforward.

Second, I immediately applied the patch ESXi600-201504001.zip as followed, connected on the ESXi server (ssh) :
[root@hercules:/vmfs/volumes/5549e911-6babde10-89ba-001ec9deb63b/ESXi600-201504001] esxcli software vib update --depot=/vmfs/volumes/5549e911-6babde10-89ba-001ec9deb63b/ESXi600-201504001/ESXi600-201504001.zip
Installation Result
   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
   Reboot Required: true
   VIBs Installed: VMware_bootbank_esx-base_6.0.0-0.5.2615704
   VIBs Removed: VMware_bootbank_esx-base_6.0.0-0.0.2494585
<…snipped…>
After rebooting the server, verify the patch bundle was installed, by issuing the following command:
[root@hercules:~] esxcli software vib list | more
Name                           Version                               Vendor  Acceptance Level  Install Date
-----------------------------  ------------------------------------  ------  ----------------  ------------
OpenManage                     7.4.0.2.ESXi550-0000                  Dell    PartnerSupported  2015-05-11
mtip32xx-native                3.8.5-1vmw.600.0.0.2494585            VMWARE  VMwareCertified   2015-05-11
ata-pata-amd                   0.3.10-3vmw.600.0.0.2494585           VMware  VMwareCertified   2015-05-11
ata-pata-atiixp                0.4.6-4vmw.600.0.0.2494585            VMware  VMwareCertified   2015-05-11
ata-pata-cmd64x                0.2.5-3vmw.600.0.0.2494585            VMware  VMwareCertified   2015-05-11
ata-pata-hpt3x2n               0.3.4-3vmw.600.0.0.2494585            VMware  VMwareCertified   2015-05-11
ata-pata-pdc2027x              1.0-3vmw.600.0.0.2494585              VMware  VMwareCertified   2015-05-11
ata-pata-serverworks           0.4.3-3vmw.600.0.0.2494585            VMware  VMwareCertified   2015-05-11
ata-pata-sil680                0.4.8-3vmw.600.0.0.2494585            VMware  VMwareCertified   2015-05-11
ata-pata-via                   0.3.3-2vmw.600.0.0.2494585            VMware  VMwareCertified   2015-05-11
block-cciss                    3.6.14-10vmw.600.0.0.2494585          VMware  VMwareCertified   2015-05-11
cpu-microcode                  6.0.0-0.0.2494585                     VMware  VMwareCertified   2015-05-11
ehci-ehci-hcd                  1.0-3vmw.600.0.0.2494585              VMware  VMwareCertified   2015-05-11
elxnet                         10.2.309.6v-1vmw.600.0.0.2494585      VMware  VMwareCertified   2015-05-11
emulex-esx-elxnetcli           10.2.309.6v-0.0.2494585               VMware  VMwareCertified   2015-05-11
esx-base                       6.0.0-0.5.2615704                     VMware  VMwareCertified   2015-05-11
esx-dvfilter-generic-fastpath  6.0.0-0.0.2494585                     VMware  VMwareCertified   2015-05-11
esx-tboot                      6.0.0-0.0.2494585                     VMware  VMwareCertified   2015-05-11
esx-xserver                    6.0.0-0.0.2494585                     VMware  VMwareCertified   2015-05-11
ima-qla4xxx                    2.02.18-1vmw.600.0.0.2494585          VMware  VMwareCertified   2015-05-11
ipmi-ipmi-devintf              39.1-4vmw.600.0.0.2494585             VMware  VMwareCertified   2015-05-11
ipmi-ipmi-msghandler           39.1-4vmw.600.0.0.2494585             VMware  VMwareCertified   2015-05-11
ipmi-ipmi-si-drv               39.1-4vmw.600.0.0.2494585             VMware  VMwareCertified   2015-05-11
<…snipped…>
[root@hercules:~]

The esx-base has been updated with the proper package number 2615704.

Third, on client side, install the last version of ViClient.

It is not more than few minutes matter.
The login screen did not change from a bit compared to the previous one, still the warning with VMWare 5.5. I was even wondering if it upgraded at all.
 
On the license warning, do not forget to apply the new one which has been assigned when you downloaded the product:
 
“Assign a license to the ESXi” open a web browser to go on VMWare website and get a license number under your registration.
If you downloaded the free product ESXi within your VMWare account, click on OK.
Glad to see ESXi 6.0.
Then go to configuration tab and “Licensed Features” :
 
Click on Edit, on the top right of the page :
 
Then assign a key:


Then, confirm it’s ok :

Ok, now it is not limited in time anymore.

Finally put back the server out of maintenance mode, and reboot for the last time. All the VMs configured to restart automatically should restart. 

 

Your last step will be to upgrade the VMWare tools onto all the VMs hosted on the ESXi server… I installed recently FreeNAS9.3, no need to manage the VMWare tools, it is guest managed.



Amazingly, we can create VM from Windows 3.1 up to 10 which is not even GA…

Just a little trick I use, since my OS is in French, ViClient is using French UI. I wanted English, so I run the exe as following :
"C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe" -locale en_US

Nicolas.

FreeNAS 9.3

Just installed FreeNAS 9.3 on VMWare ESXi 5.5.
Software and data must have separate disks. So first create the VM with a disk defined for the FreeNAS software, second add a disk as you wish for the data (both disks can be on different datastore).
I choose to put boths in one datastore separated from all other VMs hosted on my server (two different RAID array), and on separated network card.

Anyway, this one just for me to remember few settings next time I’m setting up a FreeNAS from within VMWare ESXi.

1)
I encountered a bug which prevent the FreeNAS server to restart at all, as described here :
Timecounter "HPET" frequency

Here we go to solve it, extract from that discussion linked above :
"A virtual HPET was introduced with Virtual Hardware version 8 (which first appeared in ESX 5.0, Workstation 8.0 and Fusion 4.0). It runs in apparent time. Currently supported guest operating systems do not require a HPET, but some will use a HPET if one is present (including Windows Vista and later, and many versions of Linux). It can be disabled by setting hpet0.present=FALSE in the VM's configuration."

Step by Step
1) Turn off your FreeNAS virtual machine
2) Edit settings on the FreeNAS virtual machine
3) Click on Options Tab
4) Click on General under Advanced
5) Click the Configuration Parameters Button on the bottom right
6) Change hpet0.present from true to false.
6.5) Click OK, and then OK to save the settings.
7) Start the virtual machine, and it will pick the next fastest timer to hpet (and won't lockup on restart).

And it works.

2)
An other one, constantly having lines on the FreeNAS’ console a message as following : “matchname: host name/name mismatch”. It’s really becoming hundreds lines after a while.
It happens after configured CIFS and accessing the NAS from a Windows client machine.
Seems to be solve by unchecking the Hostnames lookups option from CIFS service (stop/start CIFS service after changing).


All what I can say so far, it seems a little bit complicated to configure and to use, at least more than a ready-to-go NAS like my (old) Qnap TS-409 PRO. In the meantime, perhaps more complete, and more professional (less multimedia oriented).

The list above may change in time.

Nicolas.

VMWare ESXi copy VM and datastore

Lately, one of my drive of my RAID5 array was gone to death. Time for an infrastructure change.

I was glad to buy 4 new drives of 2TB to add new datastore to my vMWare ESXi 5.5 server. My plan is to move all the VMs from the old datastore where the disk is broken (RAID5, previously 4*500GB) to the new datastore (defined as RAID5, 4*2TB).
Then redefined the old LUN as RAID5 on 3*500GB as a NAS server disk (I decided to run FreeNAS 9.3).

Just a note to remember (VMWare ESXi 5.5).
Whilst I was doing a cold copy of all VMs from entire local datastore to an other local datastore, I did a script for that.
But fist of all, remember the steps :
* shutdown the VM
* delete all (consolidate) the snapshot before hands
* I decided to unregister the previous VM via 
vim-cmd vmsvc/unregister <vmid>
you may first want to get vmid from the command : vim-cmd vmsvc/getallvms
* do not use an OS copy command for vmdk file, those files would take the all provisioning space on disk instead of the actual value if it’s “thin”, could be quite surprising in the end.
My actual command I used :
vmkfstools -i "/vmfs/volumes/src/myVM/myVM.vmdk" -d thin "/vmfs/volumes/trg/myVM/myVM.vmdk"
* register the new VM
vim-cmd solo/registervm /vmfs/volumes/trg/myVM/myVM.vmx

As a side note, I was creating new datastores from a newly created LUN, I learnt that we actually cannot make more than one datastore per LUN… Need more datastore ? Create more LUNs. Yes, it requires to think about what you want to do when building the infrastructure from the beginning… 

Nicolas.

Windows 10 Tech Preview

I had some spare time last week-end and still enough Gb free on my VMWare server, so I decided to have a look into that new Windows…

So far, all what I can say is that Microsoft was concerned about customers complaints regarding previous version 8. It’s kind of mix-up but looks much better. We can wonder why some applications are there (see XBox) that we cannot uninstall…

Probably a matter of time and maturity.

Nicolas.

No words

For once, nothing to do with tech, but I cannot do otherwise. 3 painting describe the thoughts which may came up.

After three bloody days last week in France…


… today, time for mourning…


… and hope the better for tomorrow…

Thanks to the painter Malevitch (1879-1935).

For all the innocent victims of terrorist attacks.

Nicolas.

Peoplesoft HCM92 image #9

It has been released earlier this week, time to move to VMWare ESXi.
My workaround I described here is still working. To make it short, updating the ovf file as below:
1. ovf:capacity=(ovf:capacity*2)-64512 (I used diskMode=thin in the VM disks’ definition for the import)
2. <OperatingSystemSection ovf:id="101">
3. <Description>oracleLinux64Guest</Description>
       <vbox:OSType ovf:required="false">oracleLinux64Guest</vbox:OSType>
4. <vssd:VirtualSystemType>vmx-08</vssd:VirtualSystemType>

And the VM starts properly.

Enjoy,

Nicolas.

PS JOB

PS_JOB is probably the most popular and well known table in Peoplesoft HCM… The name explains by itself the content, job data component is in there.
If I would have a table on my own, I’d like to add line(s) with my name in it…
It just means that I’m always looking for a new contract. This is the intent of that blog entry. Sorry to the people who are seeking a technical subject, it’s definitely not.

Who am I ?
I hope this blog name is clear enough about my job. I’m an Oracle and Peoplesoft administrator.

I have 19 years of experience. For the last the 14 years I worked on a various of projects which gave me strong skills on my areas. Implementation of Peoplesoft from scratch, upgrade, maintenance. Oracle administration, tuning, always in Peoplesoft context. On Unix (HP, AIX), Linux or Windows, that’s the daily task.
I worked for small as well as large organizations, I used Oracle from version 7 up to 12, OEM 8 up to 12. You can find several posts across my blog for technical articles on all these different aspects regarding my job.

My job is however more than a job, it’s really a passion. I hope this 8-years old blog is showing the high level of my motivation. Everything here has been tested on my own, within my own lab I invested in. Because I think reading documentation and testing are the secret of learning and being up to date of the latest version and new introduced features…
Building my own lab also showed here by a lot of articles, made me going through other technologies like virtualization software, such as Oracle VM and VMWare ESXi.

I also spent a lot of time trying to help people on the Oracle Database General and Peoplesoft forums. It’s a very good way to learn a lot.

Find out more on my LinkedIn page.

What am I looking for ?
Always looking for new opportunity, I’d like to continue in this exciting Oracle/Peoplesoft world !
Having new contract, on site or remotely, everything can be discussed. Do not hesitate to contact me for the details, I’ll give an answer. You have my words.

The show must go on on the Peoplesoft road.

Nicolas.

psadmin 8.54

Peoplesotools 8.54 made few changes in the main menu of psadmin. I thought to find easily docs in Peoplebooks PSADMIN utility description, but it’s not really straight away. So, I decided to write it down to keep ref.

Application domain :
Whether there’s still 28 options in the menu, one has been added, one has been removed.

Let’s see first the menu. Left side psadmin menu from Peopletools 8.53, right side Peopletools 8.54.
 
The option 13 (right side) has been added. The “Push Notifications” is an entire new concept. It seems promising even though quite complex to build. Once set in the configuration file, you have to do a lot of configurations from the front-end.
Find out more here in the Peoplebooks : Understanding the Push Notification Framework.
Pay attention to the system requirements, it’s not yet supported on WebSphere, only available for Weblogic.

The option 24 (left side) has been dropped. I suppose this is following the Peopletools end support for Sybase and Informix announced a month ago, since this was only required for those plateform. Amusingly, the Peoplebooks 8.54 have not been updated, this is still referenced (see Sartup Option).

Process Scheduler :
One option dropped, 2 added.

As above, here below screenshot for Process scheduler psadmin menu. Left side psadmin menu from Peopletools 8.53, right side Peopletools 8.54.
 
The option 13 “ServerName” (left side) has been removed. Same remark as above, only required for Sybase and Informix, since there are out of support, that’s fine.

From the right side – Peopletools 8.54 - two more options. Option 3) “Domains Gateway” and 4) “Push Notifications”. Nothing in the Peoplebooks regarding those two parameters for Process Scheduler. We have to assume it’s functioning the same way as for the Application server.

Other :
Do you want one more ?
Check the configuration file of application server (actually process scheduler as well), you‘ll see the added feature “InMemory” options:
 
The result search on Peoplebooks 8.54 returns nothing but “Your search term inmemorydbname did not match any topics.” I’d expect a reference to this configuration file description. Too bad. How are we supposed to use it ?

Sorry Oracle, but that documentation is weak.

Nicolas.

Script PIA and psadmin

Depending of how you are coding your script to start/stop your webserver, it might not work.

Small example:
[root@vv-cephei-b ~]# cat start_hcm92dmo_web.sh
su - hcm92 <<EOF
psadmin -w start -d peoplesoft
exit
EOF
[root@vv-cephei-b ~]# sh ./start_hcm92dmo_web.sh
Last login: Fri Sep 26 10:33:57 CEST 2014

Starting the domain [peoplesoft].
General Exception: null

java.lang.NullPointerException
        at com.peoplesoft.pt.psadmin.ui.Progress.<init>(Progress.java:135)
        at com.peoplesoft.pt.psadmin.ui.Progress.getInstance(Progress.java:123)
        at com.peoplesoft.pt.psadmin.pia.DomainBootHandler.BootWlsServer(DomainBootHandler.java:84)
        at com.peoplesoft.pt.psadmin.pia.DomainBootHandler.run(DomainBootHandler.java:62)
        at com.peoplesoft.pt.psadmin.pia.PIAAdminCmdLine.startDomain(PIAAdminCmdLine.java:270)
        at com.peoplesoft.pt.psadmin.pia.PIAAdminCmdLine.run(PIAAdminCmdLine.java:481)
        at com.peoplesoft.pt.psadmin.PSAdmin.runSwitched(PSAdmin.java:170)
        at com.peoplesoft.pt.psadmin.PSAdmin.main(PSAdmin.java:232)
[root@vv-cephei-b ~]#

It seems to be a known bug prior Peopletools 8.54:
Trying to Start or Stop WebLogic using psadmin while using Cron Results in Error - General Exception: null - java.lang.NullPointerException (Doc ID 1908227.1)
According to the note, it should be solved in Peopletools 8.54, and obviously it is not for me... even though I'm on the newest one, 8.54.03.

Now, rewording the script:
[root@vv-cephei-b ~]# cat start_hcm92dmo_web.sh
su - hcm92 -c "psadmin -w start -d peoplesoft"
[root@vv-cephei-b ~]# sh ./start_hcm92dmo_web.sh

Starting the domain [peoplesoft].......
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.

[root@vv-cephei-b ~]#

Much better ! Bug solved.

Nicolas.

Oracle Linux 7 : ps command as root produces a WARNING

When running a “ps” command as root user on Oracle Linux 7 (and CentOS 7), you may see the following :

root       694     1  0 09:01 ?        00:00:00 /usr/bin/abrt-watch-log -F Backtrace /var/log/Xorg.0.log -- /usr/bin/abrt-dump-xorg -xD
root       692     1  0 09:01 ?        00:00:00 /usr/bin/abrt-watch-log -F BUG: WARNING: at WARNING: CPU: INFO: possible recursive locking detected ernel BUG at list_del corruption list_add corruption do_IRQ: stack overflow: ear stack overflow (cur: eneral protection fault nable to handle kernel ouble fault: RTNL: assertion failed eek! page_mapcount(page) went negative! adness at NETDEV WATCHDOG ysctl table check failed : nobody cared IRQ handler type mismatch Machine Check Exception: Machine check events logged divide error: bounds: coprocessor segment overrun: invalid TSS: segment not present: invalid opcode: alignment check: stack segment: fpu exception: simd exception: iret exception: /var/log/messages -- /usr/bin/abrt-dump-oops –xtD

Note that, at the least, we can read “ernel” where we could expect “kernel”, “eneral” instead of “general”, “nable” instead of “unable”, “ysctl” instead of “sysctl”. Not very nice.

Whether it looks like a bug, it seems not to be. Please read that interesting description Red Hat Bugzilla – Bug 976581. It’s explained the first letter is explicitly not there to be able to catch both capital/lower letter.
It’s an old bug report, a new one has also been reported more recently for CentOS 7 on CentOS bug Tracker. Minor, but it’s worth to keep an eye.

Nicolas.

Restart CREATE_TEMP_TABLE won’t work

Whilst I was running the database setup of a brand new FSCM 92 Peopletools 8.54 database, the server has all of sudden crashed down.
Once restarted, checking the logs files produced by the DMS script, I was able to determine the step it was doing when it stopped. It was the very last step, CREATE_TEMP_TABLE.
Here’s the beginning of that log :

Since the server crashed without notice, it ends in the middle of nowhere and without error. There is nothing much about restarted this step in the Peopletools installation guide, I thought restart would simply work straight away…

And here start the troubles :
  
As you may see, the command restarts from the beginning. But it dramatically failed on a table it was successful at the first place.
The guilty here is the table PSPTMATVWDEP which does not exists. What ?
 
Indeed, it does not.
And now what ? Looking at all the logs files of load (epengs.log, epengl.log…), that table is “missing”.

I found a very old note on MOS – actually from 2010 !, “How can you restart Data Mover for the CREATE_TEMP_TABLE command (Doc ID 660214.1)”. It is clearly mentioned that CREATE_TEMP_TABLE cannot be restarted. If it fails for some reason, two ways :
1. if you don’t have to upgrade your database to the latest Peopletools release, open AppDesigner, create a new project, insert all the temp tables (or from the first it failed on till the end, cf log file) and build.
You should see something like this :


2. if you have to update your database to the latest Peopletools release, then continue (Task 7-2: Updating Database to Latest PeopleTools Release) and run what described above afterwards.
Just for info, that table PSPTMATVWDEP is created in rel854xx :

It was new to me. Never late for learning…

Should I say that whether table is mandatory, it is empty ? Also empty on image FSCM92008… Hmmm.

Enjoy,

Nicolas.

Windows Power Shell does not know psae

I’ve never notice it before, probably already known by most of you guys. But whilst I was building a Peoplesoft database from within Windows 2012R2, I ran psae (PSADMIN AppEngine) from a Windows Power Shell command prompt.
And here what I got:

PS E:\pt854\bin\client\winx86> psae
psae : The term 'psae' is not recognized as the name of a cmdlet, function, script file, or operable program. Check
the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ psae
+ ~~~~
    + CategoryInfo          : ObjectNotFound: (psae:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Suggestion [3,General]: The command psae was not found, but does exist in the current location. Windows PowerShell does
    not load commands from the current location by default. If you trust this command, instead type ".\psae". See "get-help
    about_Command_Precedence" for more details.
PS E:\pt854\bin\client\winx86>

Well, probably not a big deal, but good to know and worth a try what is recommanded, since I trust this psae command:

PS E:\pt854\bin\client\winx86> .\psae
Invalid command line argument list.
  process command line:
  GUID command line   : <unavailable>
Usage:
    psae -CT <dbtype>
         -CS <server>
         -CD <database name>
         -CI <connect id>
         -CW <connect password>
         -CO <oprid>
         -CP <oprpswd>
         -R  <run control id>
         -AI <program id>
         -I  <process instance>
         -DEBUG <Y|N>
         -DR <Y|N>
         -NOCOMMIT <Y|N>
         -TRACE <value>
         -DBFLAGS <value>
         -TOOLSTRACESQL <value>
         -TOOLSTRACEPC <value>
         -OT <output type>
         -OF <output format>
         -FP <file path>
  or
    psae <parmfile>
PS E:\pt854\bin\client\winx86>

Of course, we can also still use the good old Windows DOS cmd :
PS E:\pt854\bin\client\winx86> cmd
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

E:\pt854\bin\client\winx86>psae
Invalid command line argument list.
  process command line:
  GUID command line   : <unavailable>
Usage:
    psae -CT <dbtype>
         -CS <server>
         -CD <database name>
         -CI <connect id>
         -CW <connect password>
         -CO <oprid>
         -CP <oprpswd>
         -R  <run control id>
         -AI <program id>
         -I  <process instance>
         -DEBUG <Y|N>
         -DR <Y|N>
         -NOCOMMIT <Y|N>
         -TRACE <value>
         -DBFLAGS <value>
         -TOOLSTRACESQL <value>
         -TOOLSTRACEPC <value>
         -OT <output type>
         -OF <output format>
         -FP <file path>
  or
    psae <parmfile>

E:\pt854\bin\client\winx86>

Nicolas.

We’ve detected that your operating system is not supported by this website

For many, many years, the Peoplesoft users know this (infamous) message on the login page when using, well, a non-supported OS by Peoplesoft.
I remember Duncan found a workaround to hide this message, find out more here. Already 4 years ago…

Maybe I’m out of date by using my old – but very well running – laptop on Windows XP Pro SP3, here it is within the image HCM92004 (Peopletools 8.53.xx) :
 

What a surprise with the last image HCM92008 (Peopletools 8.54.02), using the same browser and of course the same old laptop and OS, the message is just gone :

Nice, but probably time for an OS upgrade anyway !

Nicolas.

Addendum (19-Sept-2014): if my test was done on Firefox 30.0, it’s worth to read PeopleTools Simplifies Internet Explorer Certifications

VMWare ESXi vSphere 5.5 update 2 and guest OS

As of the 1st of August 2014, VMWare ESXi 5.5 supports Oracle Linux 7. 1.5 months after RHEL 7 and 2-3 weeks after CentOS 7.
And good news, from the 5.5 update 2 released last week, we can set it for new guests from the Client:
 
Note that’s only for the 64-bit version of OS. Surprisingly, whether RHEL 7 64-bit is officially also supported, it’s not listed here…
Or, from within an existing guest:
  

Find out more about VMWare Compatibility Guide.

Nicolas.

VirtualBox Appliances for PeopleSoft on VMWare ESXi (bis)

Written in April last year, my procedure to move the Peoplesoft appliance to VMWare ESXi – see here – seems to be broken since image #6… My test was on image #3…
One of the reader found its own way and kindly shared experience, you can find here how to work around.

Right now we are on image #8, the first one ever on Peopletools 8.54. Time to have a shot.

1. I decided first to follow my own procedure and see.
1.1 OVF changes
First, the ovf file setting changes, very few are needed compared to last year :
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# diff HCMDB-SES-854-01.ovf HCMDB-SES-854-01.ovf.tmp
34c34
<     <OperatingSystemSection ovf:id="109">
---
>     <OperatingSystemSection ovf:id="101">
36,37c36,37
<       <Description>Oracle_64</Description>
<       <vbox:OSType ovf:required="false">Oracle_64</vbox:OSType>
---
>       <Description>oracleLinux64Guest</Description>
>       <vbox:OSType ovf:required="false">oracleLinux64Guest</vbox:OSType>
45c45
<         <vssd:VirtualSystemType>virtualbox-2.2</vssd:VirtualSystemType>
---
>         <vssd:VirtualSystemType>vmx-07</vssd:VirtualSystemType>
Nothing else.

1.2 ovftool control file
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# echo "lax" > .ovftool
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# echo "datastore=vm" >> .ovftool
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# echo "skipManifestCheck" >> .ovftool
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# echo "overwrite" >> .ovftool
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# echo "powerOffTarget" >> .ovftool
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# echo "net:HostOnly=VM Network 2" >> .ovftool
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# echo "annotation=Peopletools 8.54">> .ovftool
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# echo "name=HCM92008" >> .ovftool

1.3 Push to ESXi
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# ovftool --version
VMware ovftool 3.5.0 (build-1274719)
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# ovftool HCMDB-SES-854-01.ovf vi://root:pwd@192.168.1.10:443
Opening OVF source: HCMDB-SES-854-01.ovf
Opening VI target: vi://root@192.168.1.10:443/
Deploying to VI: vi://root@192.168.1.10:443/
Transfer Completed
Warning:
- Wrong file size specified in OVF descriptor for 'HCMDB-SES-854-01-disk1.vmdk' (specified: -1, actual 2258674176).
- Wrong file size specified in OVF descriptor for 'HCMDB-SES-854-01-disk2.vmdk' (specified: -1, actual 3552615424).
- Wrong file size specified in OVF descriptor for 'HCMDB-SES-854-01-disk3.vmdk' (specified: -1, actual 8894975488).
- Wrong file size specified in OVF descriptor for 'HCMDB-SES-854-01-disk4.vmdk' (specified: -1, actual 7227696640).
- Wrong file size specified in OVF descriptor for 'HCMDB-SES-854-01-disk5.vmdk' (specified: -1, actual 144896).
- Wrong file size specified in OVF descriptor for 'HCMDB-SES-854-01-disk6.vmdk' (specified: -1, actual 15863050240).
Completed successfully
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]#

Those warnings – which were not here last year on previous images- are really scary. If, like me you want to get rid off these, modify the ovf file.
First check the vmdk files size on disk:
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# ls -l *vmdk
-rw------- 1 root root  2258674176 Aug 12 08:30 HCMDB-SES-854-01-disk1.vmdk
-rw------- 1 root root  3552615424 Aug 12 08:35 HCMDB-SES-854-01-disk2.vmdk
-rw------- 1 root root  8894975488 Aug 12 08:53 HCMDB-SES-854-01-disk3.vmdk
-rw------- 1 root root  7227696640 Aug 12 09:04 HCMDB-SES-854-01-disk4.vmdk
-rw------- 1 root root      144896 Aug 12 09:04 HCMDB-SES-854-01-disk5.vmdk
-rw------- 1 root root 15863050240 Aug 12 09:24 HCMDB-SES-854-01-disk6.vmdk
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]#

Take all the size and add them into ovf file (ovf:size=…):
<File ovf:href="HCMDB-SES-854-01-disk1.vmdk" ovf:id="file1" ovf:size="2258674176"/>
<File ovf:href="HCMDB-SES-854-01-disk2.vmdk" ovf:id="file2" ovf:size="3552615424"/>
<File ovf:href="HCMDB-SES-854-01-disk3.vmdk" ovf:id="file3" ovf:size="8894975488"/>
<File ovf:href="HCMDB-SES-854-01-disk4.vmdk" ovf:id="file4" ovf:size="7227696640"/>
<File ovf:href="HCMDB-SES-854-01-disk5.vmdk" ovf:id="file5" ovf:size="144896"/>
<File ovf:href="HCMDB-SES-854-01-disk6.vmdk" ovf:id="file6" ovf:size="15863050240"/>

That’s it for the warning.

1.4 Start the VM
Unfortunately, despite ovftool specified a successful work, it’s not possible to boot the new VM. It systematically tries to boot from within the network card, ignoring all the hard drives. And of course, it fails.
 

2. The systems’ disks are broken.
In the link of the other blog I mentioned above, someone found a way by setting the disk capacity to a dummy size, say 98Gb (see the comment). Using the option “diskMode=thin” of the ovftool properties, it should not be a problem in space. And it works.
2.1 The new ovf
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# diff HCMDB-SES-854-01.ovf HCMDB-SES-854-01.ovf.orig
4,9c4,9
<     <File ovf:href="HCMDB-SES-854-01-disk1.vmdk" ovf:id="file1" ovf:size="2258674176"/>
<     <File ovf:href="HCMDB-SES-854-01-disk2.vmdk" ovf:id="file2" ovf:size="3552615424"/>
<     <File ovf:href="HCMDB-SES-854-01-disk3.vmdk" ovf:id="file3" ovf:size="8894975488"/>
<     <File ovf:href="HCMDB-SES-854-01-disk4.vmdk" ovf:id="file4" ovf:size="7227696640"/>
<     <File ovf:href="HCMDB-SES-854-01-disk5.vmdk" ovf:id="file5" ovf:size="144896"/>
<     <File ovf:href="HCMDB-SES-854-01-disk6.vmdk" ovf:id="file6" ovf:size="15863050240"/>
---
>     <File ovf:href="HCMDB-SES-854-01-disk1.vmdk" ovf:id="file1"/>
>     <File ovf:href="HCMDB-SES-854-01-disk2.vmdk" ovf:id="file2"/>
>     <File ovf:href="HCMDB-SES-854-01-disk3.vmdk" ovf:id="file3"/>
>     <File ovf:href="HCMDB-SES-854-01-disk4.vmdk" ovf:id="file4"/>
>     <File ovf:href="HCMDB-SES-854-01-disk5.vmdk" ovf:id="file5"/>
>     <File ovf:href="HCMDB-SES-854-01-disk6.vmdk" ovf:id="file6"/>
13,18c13,18
<     <Disk ovf:capacity="107374182400" ovf:diskId="vmdisk1" ovf:fileRef="file1" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="34649586-c43a-4df3-af9c-2445fd543fdf"/>
<     <Disk ovf:capacity="107374182400" ovf:diskId="vmdisk2" ovf:fileRef="file2" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="f108476c-e701-49f8-b8f0-f6a2b4d6c4d5"/>
<     <Disk ovf:capacity="107374182400" ovf:diskId="vmdisk3" ovf:fileRef="file3" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="6ca0b490-9258-4643-888c-1b0722199fe5"/>
<     <Disk ovf:capacity="107374182400" ovf:diskId="vmdisk4" ovf:fileRef="file4" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="1a394121-3721-4d20-8c09-cd4f9b7f2053"/>
<     <Disk ovf:capacity="107374182400" ovf:diskId="vmdisk5" ovf:fileRef="file5" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="3bbbc232-080d-4536-916c-262fe5b2d379"/>
<     <Disk ovf:capacity="107374182400" ovf:diskId="vmdisk6" ovf:fileRef="file6" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="696b9eac-bbe8-4e49-84c2-c0c5d8b84480"/>
---
>     <Disk ovf:capacity="10092418560" ovf:diskId="vmdisk1" ovf:fileRef="file1" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="34649586-c43a-4df3-af9c-2445fd543fdf"/>
>     <Disk ovf:capacity="5782371840" ovf:diskId="vmdisk2" ovf:fileRef="file2" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="f108476c-e701-49f8-b8f0-f6a2b4d6c4d5"/>
>     <Disk ovf:capacity="41957153280" ovf:diskId="vmdisk3" ovf:fileRef="file3" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="6ca0b490-9258-4643-888c-1b0722199fe5"/>
>     <Disk ovf:capacity="15743185920" ovf:diskId="vmdisk4" ovf:fileRef="file4" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="1a394121-3721-4d20-8c09-cd4f9b7f2053"/>
>     <Disk ovf:capacity="24675840" ovf:diskId="vmdisk5" ovf:fileRef="file5" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="3bbbc232-080d-4536-916c-262fe5b2d379"/>
>     <Disk ovf:capacity="27793221120" ovf:diskId="vmdisk6" ovf:fileRef="file6" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="696b9eac-bbe8-4e49-84c2-c0c5d8b84480"/>
34c34
<     <OperatingSystemSection ovf:id="101">
---
>     <OperatingSystemSection ovf:id="109">
36,37c36,37
<       <Description>oracleLinux64Guest</Description>
<       <vbox:OSType ovf:required="false">oracleLinux64Guest</vbox:OSType>
---
>       <Description>Oracle_64</Description>
>       <vbox:OSType ovf:required="false">Oracle_64</vbox:OSType>
45c45
<         <vssd:VirtualSystemType>vmx-09</vssd:VirtualSystemType>
---
>         <vssd:VirtualSystemType>virtualbox-2.2</vssd:VirtualSystemType>
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]#

2.2 The ovftool file content (thin option is used)
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# cat .ovftool
lax
datastore=vm
skipManifestCheck
overwrite
powerOffTarget
net:HostOnly=VM Network 2
diskMode=thin
annotation=HCM9.2 - Peopletools 8.54.01
name=HCM92008

2.3 Push to ESXi
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# ovftool HCMDB-SES-854-01.ovf vi://root:pwd@192.168.1.10:443
Opening OVF source: HCMDB-SES-854-01.ovf
Opening VI target: vi://root@192.168.1.10:443/
Deleting VM: HCM92008
Deploying to VI: vi://root@192.168.1.10:443/
Transfer Completed
Completed successfully
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]#

2.4 Boot of the new VM



Then you are back to the business and prompted to setup your brand new VM.

3. Capacity from vmdk file
Setting a larger value than needed is fine but a bit hazardous.
Looking in the vmdk file, we also can see the real disk capacity of the target. For instance, here for the disk1:
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# cat HCMDB-SES-854-01-disk1.vmdk|more
KDMV

version=1
CID=aa3d0432
parentCID=ffffffff
createType="streamOptimized"

# Extent description
RDONLY 19711755 SPARSE "HCMDB-SES-854-01-disk1.vmdk"
The size is in Kb, so it should be 19711755*1024=20184837120.
”Surprisingly”, it’s exactly the double of the specified capacity in the original ovf file for the disk1. And the same is true for all the other disks.
Using that size’s capacity is also a failure… Same as above, it’s booting from within the network.

4. Size from vmdk disk
WMWare is coming with a small tool, vmware-mount (version 5.1). Very useful in our case.
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# for i in `ls |grep vmdk`
> do
> echo $i
> vmware-mount -p $i
> done
HCMDB-SES-854-01-disk1.vmdk
Nr      Start       Size Type Id Sytem
-- ---------- ---------- ---- -- ------------------------
1         63     530082 BIOS 83 Linux
2     530145   10779615 BIOS 83 Linux
3   11309760    8401995 BIOS 82 Linux swap
HCMDB-SES-854-01-disk2.vmdk
Nr      Start       Size Type Id Sytem
-- ---------- ---------- ---- -- ------------------------
1         63   11293632 BIOS 83 Linux
HCMDB-SES-854-01-disk3.vmdk
Nr      Start       Size Type Id Sytem
-- ---------- ---------- ---- -- ------------------------
1         63   81947502 BIOS 83 Linux
HCMDB-SES-854-01-disk4.vmdk
Nr      Start       Size Type Id Sytem
-- ---------- ---------- ---- -- ------------------------
1         63   30748347 BIOS 83 Linux
HCMDB-SES-854-01-disk5.vmdk
Nr      Start       Size Type Id Sytem
-- ---------- ---------- ---- -- ------------------------
1         63      48132 BIOS 83 Linux
HCMDB-SES-854-01-disk6.vmdk
Nr      Start       Size Type Id Sytem
-- ---------- ---------- ---- -- ------------------------
1         63   54283572 BIOS 83 Linux

The size is given in Kb.
Let’s take the first, (530082+10779615+8401995)*1024=20184772608
Ok, we are not that far from the double of the original size (from vmdk, see above), are we ? See.
20184837120 (original capacity) – 20184772608 = 64512. And 64512 is nothing but 63 (start) *1024…

Verifying on the second drive:
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# cat HCMDB-SES-854-01-disk2.vmdk|more
KDMV

version=1
CID=8bdea51b
parentCID=ffffffff
createType="streamOptimized"

# Extent description
RDONLY 11293695 SPARSE "HCMDB-SES-854-01-disk2.vmdk"

11293695 * 1024 = 11564743680 (in other word original capacity*2, 5782371840*2).
Then, from the last output of vmware-mount, we have 11293632*1024=11564679168.
11564743680 - 11564679168 = 64512. Again.

So, I think we are safe to say the required capacity should be the double of the initial capacity minus 64512.

5. Let’s have a new try with this hypothesis.
5.1 New ovf
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# diff HCMDB-SES-854-01.ovf HCMDB-SES-854-01.ovf.orig
4,9c4,9
<     <File ovf:href="HCMDB-SES-854-01-disk1.vmdk" ovf:id="file1" ovf:size="2258674176"/>
<     <File ovf:href="HCMDB-SES-854-01-disk2.vmdk" ovf:id="file2" ovf:size="3552615424"/>
<     <File ovf:href="HCMDB-SES-854-01-disk3.vmdk" ovf:id="file3" ovf:size="8894975488"/>
<     <File ovf:href="HCMDB-SES-854-01-disk4.vmdk" ovf:id="file4" ovf:size="7227696640"/>
<     <File ovf:href="HCMDB-SES-854-01-disk5.vmdk" ovf:id="file5" ovf:size="144896"/>
<     <File ovf:href="HCMDB-SES-854-01-disk6.vmdk" ovf:id="file6" ovf:size="15863050240"/>
---
>     <File ovf:href="HCMDB-SES-854-01-disk1.vmdk" ovf:id="file1"/>
>     <File ovf:href="HCMDB-SES-854-01-disk2.vmdk" ovf:id="file2"/>
>     <File ovf:href="HCMDB-SES-854-01-disk3.vmdk" ovf:id="file3"/>
>     <File ovf:href="HCMDB-SES-854-01-disk4.vmdk" ovf:id="file4"/>
>     <File ovf:href="HCMDB-SES-854-01-disk5.vmdk" ovf:id="file5"/>
>     <File ovf:href="HCMDB-SES-854-01-disk6.vmdk" ovf:id="file6"/>
13,18c13,18
<     <Disk ovf:capacity="20184772608" ovf:diskId="vmdisk1" ovf:fileRef="file1" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="34649586-c43a-4df3-af9c-2445fd543fdf"/>
<     <Disk ovf:capacity="11564679168" ovf:diskId="vmdisk2" ovf:fileRef="file2" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="f108476c-e701-49f8-b8f0-f6a2b4d6c4d5"/>
<     <Disk ovf:capacity="83914242048" ovf:diskId="vmdisk3" ovf:fileRef="file3" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="6ca0b490-9258-4643-888c-1b0722199fe5"/>
<     <Disk ovf:capacity="31486307328" ovf:diskId="vmdisk4" ovf:fileRef="file4" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="1a394121-3721-4d20-8c09-cd4f9b7f2053"/>
<     <Disk ovf:capacity="49287168" ovf:diskId="vmdisk5" ovf:fileRef="file5" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="3bbbc232-080d-4536-916c-262fe5b2d379"/>
<     <Disk ovf:capacity="55586377728" ovf:diskId="vmdisk6" ovf:fileRef="file6" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="696b9eac-bbe8-4e49-84c2-c0c5d8b84480"/>
---
>     <Disk ovf:capacity="10092418560" ovf:diskId="vmdisk1" ovf:fileRef="file1" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="34649586-c43a-4df3-af9c-2445fd543fdf"/>
>     <Disk ovf:capacity="5782371840" ovf:diskId="vmdisk2" ovf:fileRef="file2" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="f108476c-e701-49f8-b8f0-f6a2b4d6c4d5"/>
>     <Disk ovf:capacity="41957153280" ovf:diskId="vmdisk3" ovf:fileRef="file3" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="6ca0b490-9258-4643-888c-1b0722199fe5"/>
>     <Disk ovf:capacity="15743185920" ovf:diskId="vmdisk4" ovf:fileRef="file4" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="1a394121-3721-4d20-8c09-cd4f9b7f2053"/>
>     <Disk ovf:capacity="24675840" ovf:diskId="vmdisk5" ovf:fileRef="file5" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="3bbbc232-080d-4536-916c-262fe5b2d379"/>
>     <Disk ovf:capacity="27793221120" ovf:diskId="vmdisk6" ovf:fileRef="file6" ovf:format="http://www.vmware.com/interfaces/specifications/vmdk.html#streamOptimized" vbox:uuid="696b9eac-bbe8-4e49-84c2-c0c5d8b84480"/>
34c34
<     <OperatingSystemSection ovf:id="101">
---
>     <OperatingSystemSection ovf:id="109">
36,37c36,37
<       <Description>oracleLinux64Guest</Description>
<       <vbox:OSType ovf:required="false">oracleLinux64Guest</vbox:OSType>
---
>       <Description>Oracle_64</Description>
>       <vbox:OSType ovf:required="false">Oracle_64</vbox:OSType>
45c45
<         <vssd:VirtualSystemType>vmx-09</vssd:VirtualSystemType>
---
>         <vssd:VirtualSystemType>virtualbox-2.2</vssd:VirtualSystemType>
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]#

5.2 ovftool control file
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# cat .ovftool
lax
datastore=vm
skipManifestCheck
overwrite
powerOffTarget
net:HostOnly=VM Network 2
diskMode=thin
annotation=HCM9.2 - Peopletools 8.54.01
name=HCM92008

5.3 Push to ESXi
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]# ovftool HCMDB-SES-854-01.ovf vi://root:pwd@192.168.1.10:443
Opening OVF source: HCMDB-SES-854-01.ovf
Opening VI target: vi://root@192.168.1.10:443/
Deploying to VI: vi://root@192.168.1.10:443/
Transfer Completed
Completed successfully
[root@omsa:/nfs/software/PeopleSoftCD/OVA/HCM-920-UPD-008_OVA]#

5.4 Booting VM
The new VM starts as expected. Back to normal.


Ok, I hope it is clear, briefly speaking, in the ovf file change the capacity as (capacity*2)-64512 for each file.

Successfully tested on HCM92008 and FSCM92008 images.

Nicolas.

Peopletools 8.54 client silent installation

Digging around the last Oracle VM appliance HCM92008 (based on Peopletools 8.54.01), I just discovered a file with a nice name.
Check at /opt/oracle/psft/pt/tools/setup/Client/Disk1/resp_file_client.txt
Does this mean we can install Peopletools client in silent mode ? Well, probably not so easily in fact. According to the documentation, it’s still not supported : “Note. Only the command line options listed in this documentation are supported for PeopleSoft installation. Note that the use of a response file for silent installation is not supported for the installer for PeopleSoft PeopleTools 8.54. For some of the installations described elsewhere in this documentation, such as PeopleSoft Pure Internet Architecture, the same options apply.”

Fair enough, looking across Internet, it seems I missed a very interesting blog entry, worth to go through :
http://otherdutiesasrequired.com/?p=17

Nice catch up !

Nicolas.

Peoplesoft stops certification on Sybase and Informix

Due to a low number of customers using Sybase and Informix, Peoplesoft team recently decided to stop supporting their products on these databases, please see MOS note Oracle Modifies Supported Platforms for PeopleSoft (Doc ID 1915316.1)
According to the note, the Peoplesoft application 9.1 will be the terminal release for these databases. However, you’ll still be able to go for Peopletools 8.54, it will be the last supported.
Anyway, most likely better to go for a database support change as soon as possible.

It reminds me a poll that I did 5 years ago (!), that was not a scientific nor official statistics but none of the readers here was already using these two db… http://gasparotto.blogspot.nl/2009/11/polls-results.html

Will DB2 next one ?

Nicolas.

JDK for Peopletools 8.54 on Linux 7

On Linux, once you installed JDK provided on edelivery for Peopletools 8.54 (jdk-7u55-linux-x64.rpm), you make a go for Weblogic.
Here you go:
java -jar wls_121200.jar

On Oracle Linux 7, it ends quickly by the following error :
OpenJDK JVM not supported on this platform.

Also tried with 7u65, no luck. To solve it, install the JDK 7u67 – the latest available. You can download it here :
http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html

Weblogic install should run now - do not forget to set JAVA_HOME before hands.
There’s a warning though about unsupported platform (Oracle Linux 7 is not yet), but it does not hurt.

Nicolas.