Category: Database

This section related to Oracle database different version

TT6003: Lock request denied because of time-out

Posted on by Osama Mustafa in Database
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 …

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

Posted on by Osama Mustafa in Database
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 ….

Timesten 15022: OraclePwd connection attribute

Posted on by Osama Mustafa in Database

con1: Command> call ttgridcreate (‘samplegrid’);
15022: OraclePwd connection attribute needs to be specified and has to be non-empty for using IMDB Cache features
 5109: Cache Connect general error: BDB connections not open.

As you see from the error,The OraclePWD connection attribute is not specified. which mean caching will not be enabled till you are set OraclePWD parameter , to do this reconnect with the following connection :-

connect “dsn=tt_orcldwh;uid=cacheadm;OraclePWD=cacheadm”;

Run your command again

Thank you
Osama Mustafa 

ORA-01031: insufficient privileges On ASM – Grid Infrastructure 11gR2

Posted on by Osama Mustafa in Database
Today like any other day started with customer call , Telling me There is problem on Grid infrastructure after restarting both node, They change heartbeat from cables to connected on switch after i told them to do this.

The Error in the logs like the  below :-
CRS-5011:Check of resource “+ASM” failed: details at “(:CLSN00006:)”

Node #2 was running without any problem , the issue was with node #1 and nothing changed recently.

The Error in Node #1 :-

crsctl start cluster

PRCR-1079 : Failed to start resource ora.asm
ORA-01031: insufficient privileges
CRS-5017: The resource action “ora.asm start” encountered the following error:
ORA-01031: insufficient privileges
. For details refer to “(:CLSN00107:)” in “/u01/app/grid/11.2.0.4/log/lux335/agent/ohasd/oraagent_oracle/oraagent_oracle.log”.

as you see from the above error “ORA-01031: insufficient privileges” i was running this command as root.
After check node #1 the solution so simple :-

Under $GRID_HOME/network/admin
vi sqlnet.ora

SQLNET.AUTHENTICATION_SERVICES = (NONE)

which is wrong and to be changed to the following value :-

SQLNET.AUTHENTICATION_SERVICES = (NTS)

Reboot Node #1 and everything running successfully.

Thank you
Osama mustafa

ORA-12505 SCAN Listener And JDBC

Posted on by Osama Mustafa in Database

The Above Error Appears when trying to connect RAC database Using SCAN Listener through JDBC, I checked everything and it was working without any problem, I could not find any reason why this issue happened, nothing in the Listener.log.

So I Used the below connection String instead of above one.

jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=SCAN-LISTENER-NAME)(PORT=1530))(CONNECT_DATA=(SERVICE_NAME=Service-name)))

Thank you
Osama Mustafa