Monday, July 30, 2018

Failed to import appliance Error reading OVA VERR_TAR_UNEXPECTED_EOS

Issue:
While importing OVA file in Oracle virtual box, below issue can come.
Failed to import appliance OST01.ova.  Error reading OVA 'OST01.ova' (VERR_TAR_UNEXPECTED_EOS).
 Result Code: VBOX_E_IPRT_ERROR (0x80BB0005) Component: ApplianceWrap Interface: IAppliance {8398f026-4add-4474-5bc3-2f9f2140b23e}

Failed to import appliance Error reading OVA  VERR_TAR_UNEXPECTED_EOS



Workaround:

Download the 7zip and extract your OVA file by using it. Now import your .ovf file which you got after extraction, this should work.

Process Verification Failure: The process has more than one thread.VirtualBox


Issue:

VirtualBox - Error In supR3HardenedWinReSpawn

rc= -55640)
Please try reinstalling VirtualBox

where: supR3HardenedWinReSpawn what: 1
VER_SUR_VP_THREAD_NOT_ALONE (-5640) - Process Verification Failure:
The process has more than one thread.


Workaround:
Download and install the VirtualBox 5.1.16 (released March 08 2017) and you will not get this issue.

Wednesday, July 11, 2018

C:\Program' is not recognized as an internal or external command

Issue:

D:\Software\Jdev\fmw_12.2.1.3.0_soaqs_Disk1_1of2>C:\Program Files\Java\jdk1.8.0_171\bin\java.exe -jar fmw_12.2.1.3.0_soa_quickstart.jar
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.

Reason:

Space in directory Program Files.

Workaround: Use " " like below: 

D:\Software\Jdev\fmw_12.2.1.3.0_soaqs_Disk1_1of2>"C:\Program Files\Java\jdk1.8.0_171\bin\java.exe" -jar fmw_12.2.1.3.0_soa_quickstart.jar
Launcher log file is D:\Users\muhammad.nasir\AppData\Local\Temp\OraInstall2018-07-05_12-00-01PM\launcher2018-07-05_12-00-01PM.log.
Extracting the installer . . . . . . . . . . .

xhost unable to open display,Please set the DISPLAY

Workaround:

1) log into console as root and open a terminal. 
2) DISPLAY=:0.0
3) export DISPLAY
4) xhost +
5) su - oracle
6) DISPLAY=:0.0
7) export DISPLAY


Detail Error:

SPLAY is not set.  Please set the DISPLAY environment variable and try again.
Depending on the Unix Shell, you can use one of the following commands as examples to set the DISPLAY environment variable:
- For csh:  %% setenv DISPLAY 192.168.1.128:0.0
- For sh, ksh and bash: $ DISPLAY=192.168.1.128:0.0; export DISPLAY
Use the following command to see what shell is being used:
echo $SHELL
Use the following command to view the current DISPLAY environment variable setting:
echo $DISPLAY
- Make sure that client users are authorized to connect to the X Server.
To enable client users to access the X Server, open an xterm, dtterm or xconsole as the user that started the session and type the following command:
%% xhost +
To test that the DISPLAY environment variable is set correctly, run a X11 based program that comes with the native operating system such as 'xclock':
%% <full path to xclock; see below>
If you are not able to run xclock successfully, please refer to your PC-X Server or OS vendor for further assistance.
Typical path for xclock: /usr/X11R6/bin/xclock
java.awt.HeadlessException:
No X11 DISPLAY variable was set, but this program performed an operation which requires it.
at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:204)
at java.awt.Window.<init>(Window.java:536)
at java.awt.Frame.<init>(Frame.java:420)
at java.awt.Frame.<init>(Frame.java:385)
at javax.swing.SwingUtilities$SharedOwnerFrame.<init>(SwingUtilities.java:1758)
at javax.swing.SwingUtilities.getSharedOwnerFrame(SwingUtilities.java:1833)
at javax.swing.JDialog.<init>(JDialog.java:272)
at javax.swing.JDialog.<init>(JDialog.java:206)
at javax.swing.JDialog.<init>(JDialog.java:154)
at oracle.as.install.engine.modules.presentation.ui.common.dialogs.SpecifyInventoryDirectoryDialog.<init>(SpecifyInventoryDirectoryDialog.java:248)
at oracle.as.install.engine.modules.presentation.ui.common.dialogs.SpecifyInventoryDirectoryDialog.showDialog(SpecifyInventoryDirectoryDialog.java:781)
at oracle.sysman.oio.oioc.OiocOneClickInstaller.main(OiocOneClickInstaller.java:643)

The log(s) can be found here: /tmp/OraInstall2018-07-12_12-27-39AM.

Thursday, May 11, 2017

ERROR: 1045 (28000): Access denied for user 'abc'@'localhost' (using password: YES)


This issue comes when you are not entering your MYSQL connection string properly. Below screenshot shows how to connect to MYSQL and avoid this issue.

Jdeveloper windows not showing


 Problems:
Jdeveloper windows are not showing properly 

Solution:
Rename or delete this file from Jdeveloper direcotry 
windowinglayout.xml
just search it and delete it

second option 

Reset windows to factory settings 

[SQLServer]Could not find stored procedure 'master..xp_jdbc_open2'.


Problem:

<Console encountered the following error java.sql.SQLException: [FMWGEN][SQLServer JDBC Driver][SQLServer]Could not find stored procedure 'master..xp_jdbc_open2'.


Workaround:

Go to your Data Source configuration on Weblogic Console and change the Driver Class Name to following:

weblogic.jdbc.sqlserver.SQLServerDriver

These are the drivers for NonXA data source. 

However if you want to create an XA connection with MS SQL server then some configuration are required at MS SQL side. 

Go to /fmwinfra/oracle_common/modules/datadirect of your weblogic installation directory. Copy these two files instjdbc.sql and x64sqljdbc.dll if you are using 64 bit SQL server otherwise select as per version from the same directory to MS  SQL Installation bin directory. 

Execute instjdbc.sql  in MS SQL server. Now create XA data source in your weblogic server. It should work. If there are multiple SQL servers then you will have to do the same configuration on all SQL servers. Hope this will help.