Error importing Peopletools appliance

melove51 · ‎05-01-2014

So I'm trying to import a Peoplesoft Tools appliance (.ova file that works in virtualbox).

We are running vCenter 5.5 and all the hosts are 5.5

I found a really good post that walks you through converting the file and I'm really close: http://gasparotto.blogspot.com/2013/04/virtualbox-appliances-for-peoplesoft-on.html?showComment=1398...

I'm trying to import the server to a host using ovftool and i'm getting this error:

- Wrong file size specified in OVF descriptor for 'FSCMDB-SES-853-11-disk1.vmdk

' (specified: -1, actual 1726696448).

- Wrong file size specified in OVF descriptor for 'FSCMDB-SES-853-11-disk2.vmdk

' (specified: -1, actual 3460785664).

- Wrong file size specified in OVF descriptor for 'FSCMDB-SES-853-11-disk3.vmdk

' (specified: -1, actual 7048273408).

- Wrong file size specified in OVF descriptor for 'FSCMDB-SES-853-11-disk4.vmdk

' (specified: -1, actual 7914648576).

- Wrong file size specified in OVF descriptor for 'FSCMDB-SES-853-11-disk5.vmdk

' (specified: -1, actual 11116916224).

Completed with errors

I attached the .ovf if anyone wants to see that. I know it's a setting in there somewhere, i just can't figure it out.

johnnyhonda274 · ‎05-08-2014

Edit the ovf file, what is in bold needs to be added to the "<References>" section...

</References>

...and you will not get these errors when you use the OVF TOOL afterwards:

Warning:

- No manifest file found.

- Wrong file size specified in OVF descriptor for 'FSCMDB-SES-853-11-disk1.vmdk

' (specified: -1, actual 1726696448).

- Wrong file size specified in OVF descriptor for 'FSCMDB-SES-853-11-disk2.vmdk

' (specified: -1, actual 3460785664).

- Wrong file size specified in OVF descriptor for 'FSCMDB-SES-853-11-disk3.vmdk

' (specified: -1, actual 7048273408).

- Wrong file size specified in OVF descriptor for 'FSCMDB-SES-853-11-disk4.vmdk

' (specified: -1, actual 7914648576).

- Wrong file size specified in OVF descriptor for 'FSCMDB-SES-853-11-disk5.vmdk

' (specified: -1, actual 11116916224).

= )

JohnMarkston · ‎06-26-2014

Hi Johnny-

Thanks for the info. That did indeed make the error message go away. But now when we try deploying the OVF in vSphere we get a pop-up that says, "Error uploading file FSCMDB-SES-853-11-disk1.vmdk to server. Capacity of uploaded disk is larger than requested"

Do you have any idea what is causing this? We can try adding some more properties to the OVF if you can suggest other things to try out.

Thanks

John

JohnMarkston · ‎06-30-2014

You can ignore my my question from last Thursday, I actually figured why I cannot deploy the appliance in vSphere. The problem is that vSphere sees the value of ovf:capacity field in the DiskSection of the OVF and thinks that it is too small. Oracle VM and VirtualBox are both ok with this field, maybe they don't even look at it. I am not sure what vSphere is comparing ovf:capacity against in order to come to that conclusion though. To work around this issue I was able to double the value of the ovf:capacity field and run OVF Tool against it. And in fact, if I pass the --lax parameter to OVF Tool without your workaround on May 8 I am still able to deploy the OVF appliance. I successfully tried this technique with both the PeopleSoft HCM and FSCM PUM OVAs. (I think they call this revision of their OVAs 'PI 6')

In summary, here's what I did:

Download the PI6 OVAs from MyOracleSupport.
On Fedora extract the OVAs using tar: tar xvf FSCMDB-SES-853-12.ova
In vi edit the extracted .ovf file to replace <OperatingSystemSection ovf:id="109"> with <OperatingSystemSection ovf:id="36">
Also in vi edit the.ovf file to replace all occurrences of Oracle_64 with Linux
Still in vi double the values of all the ovf:capacity fields in the DiskSection element. e.g: increase the value of ovf:capacity="10092418560" to 20092418560
Totally remove the System element from the VirtualHardwareSection element.
Run ovftool, for example: ovftool --lax --skipManifestGeneration FSCMDB-SES-853-12.ovf FSCMDB-SES-853-12-vmware.ovf
Deploy OVF Appliance in vSphere.
Go to the console of the VM and answer all the goofy questions that it prompts you with.

I have attached a copy of the OVF file that I edited as described above.

JoeArr · ‎09-23-2014

Hi John

I use your ovf file but when I power up the VM and answer all the goofy questions it only loads a database no other parts get installed or loaded like AppServer, Batch server, and PIA shows up ??

JohnMarkston · ‎10-02-2014

I assume that you did not directly use my OVF file directly and that you instead used the instructions to edit your own OVF file? Just taking my OVF wouldn't be reliable. I just attached the OVF as an example to see the result of my steps 1-9.

I don't know why the VM would be able to load the database but not the other components such as AppBatch. Can you check to see if the PS_HOME is even present? It should be in /opt/oracle/psft/pt/tools. If it is, can you log in as the psadm2 user and invoke psadmin -envsummary to see if the AppBatch domains were even created when the VM started? if they are present can you take a look at the AppServer or Process Scheduler domains to see why they failed to boot? Does the VM have enough virtual resources allocated - such as RAM and VCPUs?

I doubt if there was a VMware issue or VM integrity issues because if there was then something more fundamental would have gone wrong prior to the DB starting. For example, volumes wouldn't be loaded and then there would be some kind of system initialization time failure with respect to the disk devices being mounted. Anyhow, do some more triaging along the lines of what I suggest in the above paragraph.

JoeArr · ‎10-03-2014

Thanks for the email reply John No I did not use your ovf file just looked at it for an example Here is my install C:\Program Files\VMware\VMware OVF Tool>ovftool --lax -ds=DataStore4h "--net:Hos tOnly=VM Network" "C:\Downloads\OVA-Sept\FSCMDB-SES-854-01.ovf" "vi://root:password here@192.168.163.173" Opening OVF source: C:\Downloads\OVA-Sept\FSCMDB-SES-854-01.ovf Opening VI target: vi://root@192.168.163.173:443/ Deploying to VI: vi://root@192.168.163.173:443/ Transfer Completed Warning: - No manifest file found. - Wrong file size specified in OVF descriptor for 'FSCMDB-SES-854-01-disk1.vmdk ' (specified: -1, actual 1141860352). - Wrong file size specified in OVF descriptor for 'FSCMDB-SES-854-01-disk2.vmdk ' (specified: -1, actual 3557715968). - Wrong file size specified in OVF descriptor for 'FSCMDB-SES-854-01-disk3.vmdk ' (specified: -1, actual 8084620288). - Wrong file size specified in OVF descriptor for 'FSCMDB-SES-854-01-disk4.vmdk ' (specified: -1, actual 7227442688). - Wrong file size specified in OVF descriptor for 'FSCMDB-SES-854-01-disk5.vmdk ' (specified: -1, actual 138240). - Wrong file size specified in OVF descriptor for 'FSCMDB-SES-854-01-disk6.vmdk ' (specified: -1, actual 138240). - No manifest entry found for: 'FSCMDB-SES-854-01-disk1.vmdk'. - No manifest entry found for: 'FSCMDB-SES-854-01-disk2.vmdk'. - No manifest entry found for: 'FSCMDB-SES-854-01-disk3.vmdk'. - No manifest entry found for: 'FSCMDB-SES-854-01-disk4.vmdk'. - No manifest entry found for: 'FSCMDB-SES-854-01-disk5.vmdk'. - No manifest entry found for: 'FSCMDB-SES-854-01-disk6.vmdk'. Completed successfully C:\Program Files\VMware\VMware OVF Tool>

I do not see PS_HOME present The VM has 2 CPU's and 6 GB of memory I do see some errors fly by for disks I think during boot up

JohnMarkston · ‎10-03-2014

Actually the screenshot you provided proves that you do have a PS_HOME. The directory /opt/oracle/psft/pt/tools is in fact the PS_HOME directory.

If you get me the output of psadmin -envsummary when logged in (on the VM itself) as psadm2 then then I can help you further. If you're not familiar with how to do this then let me know and I'll see if I can give you some guidance.

JoeArr · ‎10-03-2014

thanks here is the output

[psadm2@FSVM854 tools]$ psadmin -envsummary

PeopleTools Version 8.54.01

sh: /home/psadm2/psft/pt/8.54/tuxversion.out: No such file or directory

TUXDIR /opt/oracle/psft/pt/bea/tuxedo

PS_CFG_HOME /home/psadm2/psft/pt/8.54

PS_HOME /opt/oracle/psft/pt/tools

------------------------------------------------------

PeopleSoft Application Servers

------------------------------------------------------

none.

------------------------------------------------------

PeopleSoft Process Scheduler Servers

------------------------------------------------------

none.

------------------------------------------------------

PeopleSoft Search Servers

------------------------------------------------------

none.

[psadm2@FSVM854 tools]$

JohnMarkston · ‎10-06-2014

Something is definitely very wrong in your environment. The fact that it is not picking up the App Home and including it in the psadmin -envsummary output, is concerning. i.e: I would expect to see a file system location for PS_APP_HOME also echoed. I thought that the PS_APP_HOME location was always set via the psadm2 user's profile.

I don't know what to suggest at this point. You could of course try resetting the VM and then doing a fresh boot of it. If you want to try this out here is what you would do:

(as root)

(1) Invoke the command /usr/sbin/oraclevm-template --cleanup

(2) Invoke the command /usr/sbin/oraclevm-template --enable

(3) Reboot the VM

(4) When the VM console comes up go through the initialization prompts and make sure that what you're prompted matches what is described in the PUM manual that accompanied the PUM download on MyOracleSupport.

If you're still seeing the issue then I'd probably want to ask you for some more info. It's kinda hard when I can't see the machine, y'know.

mangoBlasterPac · ‎04-01-2015

http://www.itsecurenet.com/virtualbox-ova-to-vsphere-ovf/ I used this < URL, in addition as per suggestion above I doubled the ovf capacity as per item 5.

So in summary.

1. Use URL above to convert OVA file to OVF files (ovf txt file and all the VMDK disk files) using VMware ovftool

2. Use the FCIV tool in the article

3. Edit the OVF txt file to DOUBLE the ovf:capacity - otherwise u get error msgs about disk capacity

4. Replacing Oracle_64 with Linux in the ovf txt file tidies things up a little too.

All

Error importing Peopletools appliance