Thursday, November 27, 2014

TT6003: Lock request denied because of time-out

Trying to create cache group lead to the below error :-

java.sql.SQLException: [TimesTen][TimesTen 11.2.1.4.0 ODBC Driver][TimesTen]TT6003: Lock request denied because of time-out
Details: Tran 143.23106 (pid 19946) wants Sn lock on rowid BMUFVUAAAAxogAALDp, table SUBSCRIBER. But tran 144.67398 (pid 19946) has it in Xn (request was Xn). Holder SQL (select ID,identifierType,identifiervalue,subscriberId,groupName,siid from subscriptionidentifie...) -- file "tindex.c", lineno 4277, procedure "sbTixNext()"

After check the Timesten parameter found the issue was with LockWait


Lockwait :- Allows an application to configure the lock wait interval for the connection.

LockWait may be set to any value between 0 and 1,000,000 inclusive to a precision of
tenths of a second. The default is 10 seconds.

Actual lock wait response time is imprecise and may be exceeded by up to one tenth of
a second, due to the scheduling of the agent that detects timeouts. This imprecision
does not apply to zero second timeouts, which are always reported immediately.

Cheers

Osama ...


Wednesday, November 26, 2014

Attempt to connect to a data store that has been manually unloaded from R AM

Timesten in-memory Database :-

ttisql DSN_NAME

ttIsql (c) 1996-2005, TimesTen, Inc. All rights reserved.
Type ? or "help" for help, type "exit" to quit ttIsql.
All commands must end with a semicolon character.
connect "DSN=DSN_NAME";
707: Attempt to connect to a data store that has been manually unloaded from R
AM

The command failed.

This should be easy to resolve. A TimesTen datastore (physical database), which is what a DSN points at, has a property called its 'ramPolicy' The default value for this is inUse which means that TimesTen will load the datastore into memory whenever it is being used.

Solution :

ttAdmin -ramload DSN_NAME


Reference :-
1- Oracle OTN Forum here

Cheers

Osama ....

Sunday, November 9, 2014

Cannot Integrated JDeveloper with SOA Server

When trying to integrated JDeveloper with SOA server the below error Appeared :-

Testing JSR-160 Runtime ... failed.
Cannot establish connection.
Testing JSR-160 DomainRuntime ... skipped.
Testing JSR-88 ... skipped.
Testing JSR-88-LOCAL ... skipped.
Testing JNDI ... skipped.
Testing JSR-160 Edit ... skipped.
Testing HTTP ... success.
Testing Server MBeans Model ... skipped.

all my searching on internet not working most of the blogs indicate it's proxy setting which is already disables in my case.

After invesgtation and check logs on the both side adminserver and Jdeveloper i found it's DNS server issue therefore i edited hosts in windows like the below

Adminserver-IP   Hostname

After do this and put hostname instead of IP it's worked Successfully.


Cheers
Osama Mustafa


Monday, November 3, 2014

OWB GUI Is Slow

Sometimes the default setting is not enough , therefore you need to apply some changes depend on your requirement and the work load. Today while working on OWB I faced huge slowness while open , mapping or even press any button.

to solve this issue all you have to do increasing JVM, to do this follow the below steps :-


  • Depend on OS, Open the following File :- 
    • Windows :- C:\oracle\product\owb11_1\owb\bin\win32\owbclient.bat
Or


    • Linux : $ORACLE_HOME/owb11_1\owb\bin\win32\owbclient.bat.
This file will indicate to setownenv.sh or setowbenv.bat usually in the same path. Open it with any editor.

be careful while adding this file  If you notice or read this file there is more than one line looking the same, these lines only depend on OS for example in my case i am working on LINUX then i have to add Line that indicate for Linux only.

Next to the line -d64 add new parameter -Xmx=1024M or depend on your work.

Restart OWB now.

Cheers.

Osama Mustafa