Category Archives: Windows - Page 7

Some VirtualBox Commands

VBoxManage Commands

By default, the VBoxManage command (VBoxManage.exe) on Windows is located in the C:Program FilesOracleVirtualBox directory. You need to change to this directory or place this directory in the PATH environment variable.

1. To list all existing virtual hard drives:

VBoxManage list hdds

For example:

UUID:        1817c1f6-6888-4105-b46d-e3135a99cfcb
Parent UUID: base
Format:      VDI
Location:    C:VasudevVirtualBoxWindows XPWindows XP.vdi
State:       inaccessible
Type:        normal

UUID:        260bd00a-d35e-47b5-8c4d-1821ec008818
Parent UUID: 1817c1f6-6888-4105-b46d-e3135a99cfcb
Format:      VDI
Location:    E:VirtualBoxWindows XPSnapshots/{260bd00a-d35e-47b5-8c4d-1821ec0
08818}.vdi
State:       created
Type:        normal

UUID:        712e180b-bbf0-4d0d-ac64-81d545a5669e
Parent UUID: 1817c1f6-6888-4105-b46d-e3135a99cfcb
Format:      VDI
Location:    E:VirtualBoxWindows XPSnapshots/{712e180b-bbf0-4d0d-ac64-81d545a
5669e}.vdi
State:       created
Type:        normal

2. To remove an existing or inaccessible virtual hard drive:

VBoxManage closemedium      disk|dvd|floppy <uuid>|<filename>
                            [--delete]

For example:

C:Program FilesOracleVirtualBox>VBoxManage.exe closemedium disk 1817c1f6-6888
-4105-b46d-e3135a99cfcb
VBoxManage.exe: error: Cannot close medium 'C:VasudevVirtualBoxWindows XPWin
dows XP.vdi' because it has 2 child media
VBoxManage.exe: error: Details: code VBOX_E_OBJECT_IN_USE (0x80bb000c), componen
t Medium, interface IMedium, callee IUnknown
Context: "Close()" at line 1186 of file VBoxManageDisk.cpp

C:Program FilesOracleVirtualBox>VBoxManage.exe closemedium disk 260bd00a-d35e
-47b5-8c4d-1821ec008818

C:Program FilesOracleVirtualBox>VBoxManage.exe closemedium disk 712e180b-bbf0
-4d0d-ac64-81d545a5669e

C:Program FilesOracleVirtualBox>VBoxManage.exe closemedium disk 1817c1f6-6888
-4105-b46d-e3135a99cfcb

C:Program FilesOracleVirtualBox>

3. To start a virtual machine without a console (i.e. ‘headless’):

VBoxManage startvm          <uuid>|<name>...
                            [--type gui|sdl|headless]

dsfdfs

4. After manually copying a VirtualBox hard drive in Windows Explorer and adding it to a newly created VM in the VirtualBox GUI, the following error appears:

Failed to open the hard disk J:VirtualBoxPatch11iPatch11i1.vdi.
Cannot register the hard disk 'J:VirtualBoxPatch11iPatch11i1.vdi' 
{d2696d49-07c6-46bd-9e31-84b4c5fa649b} because a hard disk 
'I:VirtualBoxOEL5VIS4BIOEL5VIS4I1.vdi' with UUID 
{d2696d49-07c6-46bd-9e31-84b4c5fa649b} already exists.
Result Code: E_INVALIDARG (0x80070057)
Component: VirtualBox
Interface: IVirtualBox {c28be65f-1a8f-43b4-81f1-eb60cb516e66}

Use the internalcommands parameter with VBoxManage.exe to set a change the hard drive’s UUID:

C:Program FilesOracleVirtualBox>VBoxManage.exe internalcommands
Oracle VM VirtualBox Command Line Management Interface Version 4.1.16
(C) 2005-2012 Oracle Corporation
All rights reserved.

Usage: VBoxManage internalcommands <command> [command arguments]

Commands:

  loadsyms <vmname>|<uuid> <symfile> [delta] [module] [module address]
      This will instruct DBGF to load the given symbolfile
      during initialization.

  unloadsyms <vmname>|<uuid> <symfile>
      Removes <symfile> from the list of symbol files that
      should be loaded during DBF initialization.

  sethduuid <filepath> [<uuid>]
       Assigns a new UUID to the given image file. This way, multiple copies
       of a container can be registered.

  sethdparentuuid <filepath> <uuid>
       Assigns a new parent UUID to the given image file.

  dumphdinfo <filepath>
       Prints information about the image at the given location.

  listpartitions -rawdisk <diskname>
       Lists all partitions on <diskname>.

  createrawvmdk -filename <filename> -rawdisk <diskname>
                [-partitions <list of partition numbers> [-mbr <filename>] ]
                [-relative]
       Creates a new VMDK image which gives access to an entite host disk (if
       the parameter -partitions is not specified) or some partitions of a
       host disk. If access to individual partitions is granted, then the
       parameter -mbr can be used to specify an alternative MBR to be used
       (the partitioning information in the MBR file is ignored).
       The diskname is on Linux e.g. /dev/sda, and on Windows e.g.
       \.PhysicalDrive0).
       On Linux or FreeBSD host the parameter -relative causes a VMDK file to
       be created which refers to individual partitions instead to the entire
       disk.
       The necessary partition numbers can be queried with
         VBoxManage internalcommands listpartitions

  renamevmdk -from <filename> -to <filename>
       Renames an existing VMDK image, including the base file and all its exten
ts.

  converttoraw [-format <fileformat>] <filename> <outputfile>
       Convert image to raw, writing to file.

  converthd [-srcformat VDI|VMDK|VHD|RAW]
            [-dstformat VDI|VMDK|VHD|RAW]
            <inputfile> <outputfile>
       converts hard disk images between formats

  modinstall
       Installs the necessary driver for the host OS

  moduninstall
       Deinstalls the driver

  debuglog <vmname>|<uuid> [--enable|--disable] [--flags todo]
           [--groups todo] [--destinations todo]
       Controls debug logging.

  passwordhash <passsword>
       Generates a password hash.

  gueststats <vmname>|<uuid> [--interval <seconds>]
       Obtains and prints internal guest statistics.
       Sets the update interval if specified.

WARNING: This is a development tool and shall only be used to analyse
         problems. It is completely unsupported and will change in
         incompatible ways without warning.

Syntax error: Command missing

C:Program FilesOracleVirtualBox>

C:Program FilesOracleVirtualBox>VBoxManage.exe internalcommands sethduuid J:
VirtualBoxPatch11iPatch11i1.vdi
UUID changed to: d716cc7b-749a-4e0d-83b5-c0abc379f18a

C:Program FilesOracleVirtualBox>VBoxManage.exe internalcommands sethduuid J:
VirtualBoxPatch11iPatch11i2.vdi
UUID changed to: 280d9129-f190-4422-82e1-083f6f750814

C:Program FilesOracleVirtualBox>VBoxManage.exe internalcommands sethduuid J:
VirtualBoxPatch11iPatch11i3.vdi
UUID changed to: e577df83-d2e5-49e9-9a2c-18a29dd8fc84

C:Program FilesOracleVirtualBox>VBoxManage.exe internalcommands sethduuid J:
VirtualBoxPatch11iPatch11i4.vdi
UUID changed to: bf722d45-9fdd-4a9f-a9ec-f646f6156c3d


 

 

 

 

 

load: class oracle/apps/fnd/formsClient/FormsLauncher.class not found

Problem:

After installing fresh Release 12 instance (12.1.3), attempted to log on to application from client PC (Windows XPSP3). Was able to log on to R12, but forms could not be launched. The following message was displayed on the Java console:

load: class oracle/apps/fnd/formsClient/FormsLauncher.class not found.
java.lang.ClassNotFoundException: oracle.apps.fnd.formsClient.FormsLauncher.class
	at sun.plugin2.applet.Applet2ClassLoader.findClass(Unknown Source)
	at sun.plugin2.applet.Plugin2ClassLoader.loadClass0(Unknown Source)
	at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source)
	at sun.plugin2.applet.Plugin2ClassLoader.loadClass(Unknown Source)
	at java.lang.ClassLoader.loadClass(Unknown Source)
	at sun.plugin2.applet.Plugin2ClassLoader.loadCode(Unknown Source)
	at sun.plugin2.applet.Plugin2Manager.createApplet(Unknown Source)
	at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Exception: java.lang.ClassNotFoundException: oracle.apps.fnd.formsClient.FormsLauncher.class

However, other client machines (Windows 7) were able to log on and launch the forms.

Solution:

After enabling logging (Control Panel > Java > Advanced tab > Debugging, check all options), the ‘java.net.SocketException: Connection reset’ error was seen in the Java console. This indicated a network issue rather than a Java or browser issue. The EBS server (192.168.63.49) was on a different network from the client PCs (200.65.1.x). Therefore, a network route was added to keep the connection alive:

route add 192.168.63.0 mask 255.255.255.0 200.65.1.1 -p

ORA-12518: TNS:listener could not hand off client connection

Problem:

Unable to connect to SQL:

F:oracleVIS12dbtech_st11.1.0>sqlplus / as sysdba

SQL*Plus: Release 11.1.0.7.0 - Production on Tue Mar 27 11:31:04 2012

Copyright (c) 1982, 2008, Oracle.  All rights reserved.

ERROR:
ORA-12518: TNS:listener could not hand off client connection

Solution:

Increase PROCESSES initialization parameter.

Use the following command to check the value of the PROCESSES initialization parameter in SQL*Plus:

show parameter processes

If the database was started using an spfile, then the following command can be used to change the PROCESSES initialization parameter to 500:

alter system set processes=500 scope=spfile;

If the database was started using a pfile, then the value of the processes parameter must be changed in the pfile and the database bounced.

[amazon asin=0071780262&template=iframe image&chan=default]     [amazon asin=1565922379&template=iframe image&chan=default]     [amazon asin=1430236620&template=iframe image&chan=default]

Oracle Installer Not Detecting Packages

Problem:

While installing 11gR2 64-bit version on Oracle Linux 5.7 64-bit, the installer states that certain RPMs (libaio-devel-0.3.106 and unixODBC-devel-2.2.11)  are missing. After installing the missing RPMs using the ‘rpm -Uvh’ command, the installer still does not detect the newly applied RPMs.

Solution:

Exit the 11gR2 installer, apply the RPMs and then rerun the installer.

Requests Remain In ‘Posting’ Distribution Status

Problem:

When a new request is submitted in PeopleSoft (Main Menu > PeopleTools > Process Scheduler > System Process Requests), the request’s ‘Run Status’ completes with status ‘Success’, but the ‘Distribution Status’ remains at ‘Posting’.

Solution:

Ensure that the Process Scheduler Report Node and Distribution Details for the Server are correctly set up.

Read more »

java.lang.ClassNotFoundException: oracle.apps.per.DataInstall

Problem:

After applying patch 9239090 (ORACLE E-BUSINESS SUITE 12.1.3 RELEASE UPDATE PACK), DataInstall must be run. However, after sourcing the environment and running the DataInstall command, the following error appears:

java.lang.ClassNotFoundException: oracle.apps.per.DataInstall

Solution:

Source the application tier environment (not the database tier environment) and then run DataInstall.

Read more »

FAILED: file OKLTXRBKUG.sql on worker while running patch 9239090

Problem:

While running patch 9239090, the following error appears:

ATTENTION: All workers either have failed or are waiting:

           FAILED: file OKLTXRBKUG.sql on worker  1.
           FAILED: file OKLTXRBKUG.sql on worker  2.
           FAILED: file OKLTXRBKUG.sql on worker  3.
           FAILED: file OKLTXRBKUG.sql on worker  4.
           FAILED: file OKLTXRBKUG.sql on worker  5.
           FAILED: file OKLTXRBKUG.sql on worker  6.
           FAILED: file OKLTXRBKUG.sql on worker  7.
           FAILED: file OKLTXRBKUG.sql on worker  8.
           FAILED: file OKLTXRBKUG.sql on worker  9.
           FAILED: file OKLTXRBKUG.sql on worker 10.
           FAILED: file OKLTXRBKUG.sql on worker 11.
           FAILED: file OKLTXRBKUG.sql on worker 12.

ATTENTION: Please fix the above failed worker(s) so the manager can continue.

Solution:

The OKL_TRANSACTION_PVT package was invalid. When this was compiled, the OKL_SECURITIZATION_PVT was invalid. In this way, a number of OKL packages were invalid and the error was cascading. In order to resolve the issue, I logged on to SQL*Plus as sysdba and ran the following commands:

alter package APPS.OKL_TXL_ASSETS_PVT compile;
alter package APPS.OKL_TXL_ASSETS_PVT compile body;
alter package APPS.OKL_TXL_ASSETS_PUB compile;
alter package APPS.OKL_TXL_ASSETS_PUB compile body;
alter package APPS.OKL_SPLIT_ASSET_PVT compile;
alter package APPS.OKL_SPLIT_ASSET_PVT compile body;
alter package APPS.OKL_SECURITIZATION_PVT compile;
alter package APPS.OKL_SECURITIZATION_PVT compile body;
alter package APPS.OKL_TRANSACTION_PVT compile;
alter package APPS.OKL_TRANSACTION_PVT compile body;

OKL_TRANSACTION_PVT now compiles without issue.

To resolve this in future, use adadmin to compile APPS schema. Afterwards, issue the following SQL statement in SQL*Plus to get the number of invalid objects:

select count(*) from dba_objects where status = ‘INVALID’;

Continue compiling APPS schema with adadmin and checking the number of invalid objects until that number no longer decreases.

FAILED: file OKLTXRBKUG.sql on worker 1

Problem:

While running patch 9239090, the following error appears:

ATTENTION: All workers either have failed or are waiting:

           FAILED: file OKLTXRBKUG.sql on worker  1.
           FAILED: file OKLTXRBKUG.sql on worker  2.
           FAILED: file OKLTXRBKUG.sql on worker  3.
           FAILED: file OKLTXRBKUG.sql on worker  4.
           FAILED: file OKLTXRBKUG.sql on worker  5.
           FAILED: file OKLTXRBKUG.sql on worker  6.
           FAILED: file OKLTXRBKUG.sql on worker  7.
           FAILED: file OKLTXRBKUG.sql on worker  8.
           FAILED: file OKLTXRBKUG.sql on worker  9.
           FAILED: file OKLTXRBKUG.sql on worker 10.
           FAILED: file OKLTXRBKUG.sql on worker 11.
           FAILED: file OKLTXRBKUG.sql on worker 12.

ATTENTION: Please fix the above failed worker(s) so the manager can continue.

Solution:

The OKL_TRANSACTION_PVT package was invalid. When this was compiled, the OKL_SECURITIZATION_PVT was invalid. In this way, a number of OKL packages were invalid and the error was cascading. In order to resolve the issue, I logged on to SQL*Plus and ran the following commands:

alter package APPS.OKL_TXL_ASSETS_PVT compile;
alter package APPS.OKL_TXL_ASSETS_PVT compile body;
alter package APPS.OKL_TXL_ASSETS_PUB compile;
alter package APPS.OKL_TXL_ASSETS_PUB compile body;
alter package APPS.OKL_SPLIT_ASSET_PVT compile;
alter package APPS.OKL_SPLIT_ASSET_PVT compile body;
alter package APPS.OKL_SECURITIZATION_PVT compile;
alter package APPS.OKL_SECURITIZATION_PVT compile body;
alter package APPS.OKL_TRANSACTION_PVT compile;
alter package APPS.OKL_TRANSACTION_PVT compile body;

OKL_TRANSACTION_PVT now compiles without issue.

To resolve this in future, use adadmin to compile APPS schema. Afterwards, issue the following SQL statement in SQL*Plus to get the number of invalid objects:

select count(*) from dba_objects where status = ‘INVALID’;

Continue compiling APPS schema with adadmin and checking the number of invalid objects until that number no longer decreases.

mth_pre_upgrade.sql Failed While Rerunning Patch 9239090

Problem:

When rerunning patch 9239090, the following error appears:

ATTENTION: All workers either have failed or are waiting:

           FAILED: file mth_pre_upgrade.sql on worker  1.

ATTENTION: Please fix the above failed worker(s) so the manager can continue.

Checked worker log file:
C:oracleTEST1appsapps_stappladminTEST1logadwork001.log

The following errors appeared:

Time when worker started job: Mon Jan 30 2012 09:42:06

Start time for file is: Mon Jan 30 2012 09:42:06

sqlplus -s MTH/***** @C:oracleTEST1appsapps_stapplmth12.0.0patch115sqlmth_pre_upgrade.sql 

Error:
Program exited with status 1

Cause: The program terminated, returning status code 1.

Action: Check your installation manual for the meaning of this code on this operating system.DECLARE
*
ERROR at line 1:
ORA-00955: name is already used by an existing object
ORA-06512: at line 59

Time when worker failed: Mon Jan 30 2012 09:42:06

Time when worker started job: Mon Jan 30 2012 09:42:06

Start time for file is: Mon Jan 30 2012 09:42:06

sqlplus -s MTH/***** @C:oracleTEST1appsapps_stapplmth12.0.0patch115sqlmth_pre_upgrade.sql 

Error:
Program exited with status 1

Cause: The program terminated, returning status code 1.

Action: Check your installation manual for the meaning of this code on this operating system.DECLARE
*
ERROR at line 1:
ORA-00955: name is already used by an existing object
ORA-06512: at line 59

Time when worker failed: Mon Jan 30 2012 09:42:06

Solution:

1. Edit C:oracleTEST1appsapps_stapplmth12.0.0patch115sqlmth_pre_upgrade.sql  and uncomment SQL code for Exception. Then restart worker (did not try this solution).

2. Use adctrl (option 8) to skip and restart this step (tried this solution).

Reference:

https://forums.oracle.com/forums/thread.jspa?messageID=9224027

[amazon asin=0070077290&template=iframe image&chan=default]     [amazon asin=1453742735&template=iframe image&chan=default]     [amazon asin=0615238440&template=iframe image&chan=default]

RW-50004: Error code received when running external process, Running Database Install Driver

Problem:

When running Rapid Install, the following error appears:

RW-50004: Error code received when running external process. Check log file for details.
Running Database Install Driver for TEST1 instance

In the ‘Rapid Install base window – do not close’ window, the following appears:

Configuration file written to: C:oracleTEST1instappsTEST1_ittl-hrmstestconf_TEST1.txt
Configuration file written to: C:oracleTEST1dbtech_st11.1.0appsutilconf_TEST1.txt
Database logfile - C:oracleTEST1dbtech_st11.1.0appsutillogTEST1_ittl-hrmstest1260950.log
uploadConfig() : Exception : TDU

Rapid Wizard completes with the following error:

RW-10001: Rapidinstall wizard has detected that your configuration has errors. You must resolve these issues before continuing.

The log file C:oracleTEST1dbtech_st11.1.0appsutillogTEST1_ittl-hrmstest1260950.log showed the following:

    RW-50010: Error: - script has returned an error:   1
RW-50004: Error code received when running external process

Solution:

Change the NUMBER_OF_PROCESSORS environment variable from 16 to 12 and restart installation.

Read more »