NP_SOAINFRA.WL_LLR_ADMINSERVER Access Failed

 java.sql.SQLException: JDBC LLR, table verify failed for table ‘NP_SOAINFRA.WL_LLR_ADMINSERVER’, row ‘JDBC LLR Domain//Server’ record had unexpected value

The above error appeared when trying to start Adminserver nothing changed on the Domain

Solution :-

  • Goto  domain location –> config folder.
  •  remove this line from the config.xml file, Take backup before you do this.


    wlsbjmsrpDataSource
    AdminServer,osb_server1
    jdbc/wlsbjmsrpDataSource-jdbc.xml
 

Thank you
Osama Mustafa 

Resource temporarily unavailable in tsStartJavaThread

Resource temporarily unavailable in tsStartJavaThread (lifecycle.c:1096).
Java heap 3G reserved, 3G committed
Paged memory=3145728/36425712K.
Your Java heap size might be set too high.
Try to reduce the Java heap size using -Xmx: (e.g. “-
java.lang.OutOfMemoryError: Resource temporarily unavailable in tsStartJavaThread (lifecycle.c:1096).
Java heap 6G reserved, 6G committed
Paged memory=3145728/36425712K.
Your Java heap size might be set too high.
Try to reduce the Java heap size using -Xmx: 

The Above error appeared on OEDQ when trying to run the process this error related to Java Heap Size the OS control the Heap Size to solve this issue add the below parameters depend on your enviroment  :-

  • Add the following to /etc/sysctl.conf:

kernel.shmmni = 4096
kernel.sem = 256 32000 100 142
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default = 4194304
net.core.rmem_max = 4194304
net.core.wmem_default = 4194304
net.core.wmem_max = 4194304
fs.file-max = 134283264
fs.aio-max-nr = 1048576
vm.min_free_kbytes = 512000 

  • Add the following to /etc/security/limits.conf:

oracle soft nproc 16384
oracle hard nproc 63536
oracle soft nofile 16384
oracle hard nofile 63536

  •  Add the following to /etc/pam.d/login:

session required /lib/security/pam_limits.so

Thank you
Osama Mustafa

Dublin TECH SIG Day Impression

Third time in Dublin, and i still love this country i arrived to Dublin on 23-Sept to present about Oracle Security Features and how to protect Oracle Database it was exciting trip regarding to my reservation i supposed to be in Dublin at 2:00 PM But What i didn’t notice that my flight delayed Therefore i missed my flight and arrived to Dublin at 8:00 PM.

However TECH SIG was really amazing day meeting the people chatting with them, and presenting about Oracle Security with Full Room of people.

After the event me and Pete start chatting about Oracle Security and Talking about other stuff, my next Stop to SF Oracle Open World 2014.

Looking forward to meet everyone there.

Good time with Good People.

Thank you
Osama Mustafa

the version of the data that you are trying to import is not compatible with current dac version

This Error Appear On DAC Server when trying to Import Data  from the following :

Tools –> DAC Repository Management –> import

This error appears :-

the version of the data that you are trying to import is not compatible with current dac version

After trying to many Solution with no luck , i discover new Solution for this error and it’s simple :-

export from tools ( Empty files ) will generate 3 folder in DAC Folder Leave this folder without any copy or replace.

Now in my case i installed BIAPPS Copy the folder without Replace the old one.

after start copying the windows will ask dont replace these three folders DON’T REPLACE IT.


Start Import successfully.
Now The Import is done,
Thank you 
Osama Mustafa

java.lang.securityexception access denied. required roles admin

Weblogic Adminserver logs indicated to the below error :-

java.lang.securityexception access denied. required roles admin

To solve the above error, Follow the below steps :-

From the Navigation Tree –> Security Realms :-

New Page Will be Opened click on my Realms :-

From the configuration –> General 

Thank you 
Osama Mustafa

weblogic.socket.MaxMessageSizeExceededException

I recently encountered below error,Adminserver.log Indicate to :-

weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: ‘10000080’ bytes exceeds the configured maximum of: ‘10000000’ bytes for protocol: ‘t3’.
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: ‘10000080’ bytes exceeds the configured maximum of: ‘10000000’ bytes for protocol: ‘t3’
        at weblogic.socket.BaseAbstractMuxableSocket.incrementBufferOffset(BaseAbstractMuxableSocket.java:230)
        at weblogic.rjvm.t3.MuxableSocketT3.incrementBufferOffset(MuxableSocketT3.java:351)
        at weblogic.socket.SocketMuxer.readFromSocket(SocketMuxer.java:989)
        at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:920)
        at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:897)
        at weblogic.socket.EPollSocketMuxer.dataReceived(EPollSocketMuxer.java:215)
        at weblogic.socket.EPollSocketMuxer.processSockets(EPollSocketMuxer.java:177)
        at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
        at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:43)
        at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
        at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)

to fix this error follow the following steps :-

From Environment, Press on Adminserver  :-

Chose the tab like the below picture :-

Add the following parameter in arguments box, Save usually there is no need to restart :- 
Or if you would like change MaxMessageSize Directly from the console follow the below screen :-

Option #2 :- 
From the navigation tree :- 

Click on Module-FMWDFW

After choose the above tab, 3 options will be appear, press on each of them and Uncheck on Enable Watch  :-

Increase Transaction timeout in SOA Server

I received the below error in soa_server1 :-

Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 603 seconds BEA1-3FB6FB464035C13E3227 at 

From the above error, transaction timeout should be increased regarding to heavy transaction on soa server.

to do this follow the following steps :-

access weblogic console –> Deployment –> and search for Soa_infra. ( expand it)

Check the below EJBS services and click on it configuration tab :-
BPELActivityManagerBean
BPELEngineBean
BPELInstanceManagerBean
BPELProcessManagerBean
BPELServerManagerBean

If this not working on you have to increase transaction timeout for JTA, Access Weblogic Console select Services > JTA
Thank you 
Osama Mustafa