Getting " table verify failed for table WL_LLR_ADMINSERVER " error while starting server

While creating a new domain, sometimes things get messed up in the SOAINFRA schema and you might get below exception :

javax.transaction.SystemException:
weblogic.transaction.loggingresource.LoggingResourceException:
java.sql.SQLException: JDBC LLR, table verify failed for table 'WL_LLR_ADMINSERVER', row
'JDBC LLR Domain//Server' record had unexpected value 'soa11g_domain//AdminServer' expected
'soa_new_domain//AdminServer'*** ONLY the original domain and server that creates an LLR table
may access it ***

This exception is a result of a reference of old domain name in WL_LLR_ADMINSERVER table .
Lets say you were having a domain named "soa11g_domain" and you created a new domain
named 'soa_new_domain. While starting the AdminServer of new domain, the WL_LLR_ADMINSERVER table is expected to have the soa_new_domain in its RECORDSTR column but it still has reference to your old domain.
To get around this, just login to DEV_SOAINFRA DB schema with your username/password and execute below query ( change the value for RECORDSTR according to your domain and server name ) and you will be good to go :

update WL_LLR_ADMINSERVER
set    RECORDSTR = 'soa_domain//AdminServer'
where  XIDSTR    = 'JDBC LLR Domain//Server';

commit;

While opening em console for soa -- Error 404--Not Found

hi guys

usual error while settingup  weblogic domain :

while opeing the fm control using http://<hostname>.<domainname>:7001/em.

the below error message is displaying .

but i am able to open with http://<hostname>.<domainname>:7001/console.

*****************************************************************************************************************
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
**********************************************************************************************************************


Solution :  1) You may also like to check the status of application "em" in deployments section of your weblogic admin console. It must be in active state and targetted to admin server.
2) If not u find the EM option in deployements ,

I think you have not created your domain with Enterprise Manager template selected and hence no EM application is present. To extend your existing domain with EM, follow below steps-

1. Stop all servers of your existing domain.
2. Invoke the domain configuration wizard ($MW_Home\wlserver_10.3\common\bin\config.exe)
3. Choose "Extend an existing Weblogic domain" option. Click on next and select your existing domain. Then click on next.
4. Select "Oracle Enterprise Manager - 11.1.1.0[oracle_common]" template. Keep clicking on next and complete the wizard.
5. Start your servers.

Now you should be able to open the EM console.

before:

after :

                                                                                                            

[BEA-310003] OutofmemoryError when starting Weblogic

To solve out of memory error on Windows 7 64 bit platform, ensure the following

Open  <WL_HOME>\common\bin\commEnv.cmd

set  JAVA_HOME=<64 bit JDK Home>

set  JAVA_VENDOR=Oracle

set JAVA_USE_64BIT=true

Save the commEnv.cmd

Open domain\bin\setSOADomainEnv.cmd

Set the memory options as follows

set JAVA_OPTIONS=%JAVA_OPTIONS%
set DEFAULT_MEM_ARGS=-Xms1024m -Xmx2048m -XX:MaxPermSize=1024m -XX:CompileThreshold=8000
set PORT_MEM_ARGS=-Xms1024m -Xmx2048m -XX:MaxPermSize=1024m -XX:CompileThreshold=8000

if "%JAVA_VENDOR%" == "Oracle" goto OracleJVM
set DEFAULT_MEM_ARGS=%DEFAULT_MEM_ARGS% -XX:PermSize=512m -XX:MaxPermSize=1024m
set PORT_MEM_ARGS=%PORT_MEM_ARGS% -XX:PermSize=512m -XX:MaxPermSize=1024m


Save setSOADomainEnv.cmd

Restart the server

Error Starting Weblogic Admin Server: Could not reserve enough spacefor object heap

The first time that I run my weblogic admin server after installing and configuring oracle soa in weblogic 10.3.6, I encountered the following error:

Could not reserve enough space for object heap.
Could not create the Java virtual machine.

I resolved this by creating a new environment variable called EXTRA_JAVA_PROPERTIES with the following value "-Xms512m -Xmx512m". From the JDeveloper 11g Release Notes:

Running applications with limited free memory (7343786)

Under certain circumstances, if you do not have enough free memory available, you may receive an error when running an application:

Error occurred during initialization of VM
Could not reserve enough space for object heap

Normally you would resolve this by adding -Xms and -Xmx arguments to the project's Run/Debug profile. However, there are existing entries for these settings in the WebLogic startup that will override the project's settings. The proper way to resolve this error is to add EXTRA_JAVA_PROPERTIES to your environment, as follows:

On Linux
setenv EXTRA_JAVA_PROPERTIES "-Xms512m -Xmx512m"

On Windows
set EXTRA_JAVA_PROPERTIES="-Xms512m -Xmx512m"

Important update to this post!

"-Xmx512" is not sufficient to run and test an application in a SOA server, because it would be incredibly slow. If you encounter the above issue using the default config of "-Xmx1024m", then try to decrease the number until it will work. There is no hard rule, you could try "-Xmx1000m" for instance. If it still doesn't work, then try decreasing the number again.

Alternate Method :

Error

"Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine. "

Reason for this error is when we make changes memory variable and assign more memory and we don't have enough memory available... server startup is failed with this error.

Solution

You can remove this error while decreasing heap size in setSOADomainEnvt.cmd

%ORACLE_HOME%\user_projects\domains\DOMAIN\BIN\setSOADomainEnvt.cmd

set DEFAULT_MEM_ARGS=-Xms512m -Xmx1024m
set PORT_MEM_ARGS=-Xms768m -Xmx1536m

set DEFAULT_MEM_ARGS=%DEFAULT_MEM_ARGS% -XX:PermSize=128m -XX:MaxPermSize=512m
set PORT_MEM_ARGS=%PORT_MEM_ARGS% -XX:PermSize=256m -XX:MaxPermSize=512m

 

 

I have lowered my heap to below values


set DEFAULT_MEM_ARGS=-Xms768m -Xmx768m
set PORT_MEM_ARGS=-Xms768m -Xmx768m


instead of


set DEFAULT_MEM_ARGS=-Xms512m -Xmx1024m
set PORT_MEM_ARGS=-Xms768m -Xmx1536m

                                                                                                             By DeepthiReddy