Friday, February 6, 2015

BEA-000000 - A call to flushChanges on the current MDSSession does not specify the correct transaction key

Applies to:
WebLogic Enterprise Manager for Fusion Middleware - version 11.1.1.7.0

Symptoms:
There are repeating warnings in AdminServer logs after 11.1.1.7 patchset when accessing Enterprise Manager Fusion Middleware Control.

As per Oracle Doc ID 1568075.1 - The cause is currently unknown and a bug has been created for the issue.

No negative impacts have been seen as a result of this issue.


Thursday, February 5, 2015

SOA 12c Database EM is not accessible in the browser

Assumption: Database 12c is installed successfully on your local VM.

After successful install of Oracle Database 12c and starting the Listener and the Database, you might notice that the EM is not accessible in the Firefox by typing https://localhost:5500/em/login,

You will see this issue only if you are running the database on Linux VM and trying to access the EM in the Linux Firefox. The initial login EM page requires Flash plugin. Usually, on the Linux based VM's the flash is not installed and you cannot bring up the login page.

You can try to access the EM from the host machine by typing https://<VM Machine Name>:5500/em/login and the page should come up if the Flash plugin is installed and the Database and Listener are running.

I hope this will help to resolve the issue if you happen to encounter one.





VM Workstation 11 - The virtual machine appears to be in use

The VMWare workstation sometimes cannot handle unexpected shutdown or restart of the host computer. When the host machine is restarted and you try to start the VM you might get the following error.



This error is due to some of the VM temporary working files which normally are deleted when you gracefully exit the VM. 

The work around is quite simple. Go to the VM image folder location and delete all the folders with .lck extension.




Once you delete the .lck folders, you can now successfully open the VM.

I hope this will help to resolve the issue if you happen to see the similar one with your VM.