Error behaviour in multi-threaded mode

I'm running TestStand 3.0 in sequential mode. In the middle of my sequence I have a multi-threaded (6 threads) section with the appropriate Waits. My problem is that if an Error occurs while inside the multi-threaded section, then execution bypasses the Waits and I lose all the result data from the other threads.
Is there anything that I can do to get the error thread to force each of the other threads to go through their Wait so that I can get their report data.
Hurst

Hi,
Try using the New Execution option instead of New Thread.
Or In the Properties set the step to ignore runtime errors. Then put your own error trapping in
Regards
Ray Farmer
Regards
Ray Farmer

Similar Messages

Oracle 8 on Linux in Multi-Thread mode

I installed Oracle 8.0.5.0.0 on Linux RedHat 5.1
But I cann't startup database in multi-threaed mode.
When I try to startup DB the errors follow
SVRMGR> startup;
ORA-00101: invalid specification for system parameter
MTS_DISPATCHERS
ORA-00102: network protocol
(ADDRESS=(PARTIAL=YES)(PROTOCOL=tcp)) cannot be used by
dispatchers
My configuration files are:
listener.ora
LISTENER =
(ADDRESS_LIST =
(ADDRESS= (PROTOCOL= IPC)(KEY= orcl))
(ADDRESS= (PROTOCOL= IPC)(KEY= PNPKEY))
(ADDRESS= (PROTOCOL= TCP)(Host=
pcstar.kharkov.ua)(Port= 1521))
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME= pcstar.kharkov.ua)
(ORACLE_HOME= /usr/oracle)
(SID_NAME = orcl)
(SID_DESC =
(SID_NAME = extproc)
(ORACLE_HOME = /usr/oracle)
(PROGRAM = extproc)
STARTUP_WAIT_TIME_LISTENER = 0
CONNECT_TIMEOUT_LISTENER = 10
TRACE_LEVEL_LISTENER = OFF
tnslistener working normally
tnsnames.ora
extproc_connection_data =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = orcl))
(CONNECT_DATA = (SID = extproc))
orcl =
(DESCRIPTION =
(ADDRESS = (PROTOCOL= TCP)(Host=
pcstar.pcstar.kharkov.ua)(Port= 1521))
(CONNECT_DATA = (SID = orcl))
orcl_BEQ =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = BEQ)(PROGRAM = /usr/oracle)
(argv0 = oracleorcl)
(args = '(DESCRIPTION =
(LOCAL=YES)(ADDRESS=(PROTOCOL=BEQ)))')
(envs =
'ORACLE_HOME=/usr/oracle,ORACLE_SID=orcl')
initorcl.ora
mts_dispatchers="tcp,1"
mts_max_dispatchers=3
mts_servers=1
mts_max_servers=5
mts_service=orcl
mts_listener_address="(ADDRESS=(PROTOCOL=tcp)(Host=pcstar)(Por
t=1521))"
If anybody started server in Multi-Thread mode, mail me
[email protected]
Best Regards!
Gennady Saldiga
null

Yes, the MTS for TCP protocol does not work. A patch will be
released soon for the production release with the fix for
the MTS problem.
Maturi
Satoshi Hirai (guest) wrote:
: Gennady Saldiga (guest) wrote:
: : I installed Oracle 8.0.5.0.0 on Linux RedHat 5.1
: : But I cann't startup database in multi-threaed mode.
: : When I try to startup DB the errors follow
: : SVRMGR> startup;
: : ORA-00101: invalid specification for system parameter
: : MTS_DISPATCHERS
: : ORA-00102: network protocol
: : (ADDRESS=(PARTIAL=YES)(PROTOCOL=tcp)) cannot be used by
: : dispatchers
: : My configuration files are:
: : listener.ora
: : LISTENER =
: : (ADDRESS_LIST =
: : (ADDRESS= (PROTOCOL= IPC)(KEY= orcl))
: : (ADDRESS= (PROTOCOL= IPC)(KEY= PNPKEY))
: : (ADDRESS= (PROTOCOL= TCP)(Host=
: : pcstar.kharkov.ua)(Port= 1521))
: : SID_LIST_LISTENER =
: : (SID_LIST =
: : (SID_DESC =
: : (GLOBAL_DBNAME= pcstar.kharkov.ua)
: : (ORACLE_HOME= /usr/oracle)
: : (SID_NAME = orcl)
: : (SID_DESC =
: : (SID_NAME = extproc)
: : (ORACLE_HOME = /usr/oracle)
: : (PROGRAM = extproc)
: : STARTUP_WAIT_TIME_LISTENER = 0
: : CONNECT_TIMEOUT_LISTENER = 10
: : TRACE_LEVEL_LISTENER = OFF
: : tnslistener working normally
: : tnsnames.ora
: : extproc_connection_data =
: : (DESCRIPTION =
: : (ADDRESS = (PROTOCOL = IPC)(KEY = orcl))
: : (CONNECT_DATA = (SID = extproc))
: : orcl =
: : (DESCRIPTION =
: : (ADDRESS = (PROTOCOL= TCP)(Host=
: : pcstar.pcstar.kharkov.ua)(Port= 1521))
: : (CONNECT_DATA = (SID = orcl))
: : orcl_BEQ =
: : (DESCRIPTION =
: : (ADDRESS = (PROTOCOL = BEQ)(PROGRAM = /usr/oracle)
: : (argv0 = oracleorcl)
: : (args = '(DESCRIPTION =
: : (LOCAL=YES)(ADDRESS=(PROTOCOL=BEQ)))')
: : (envs =
: : 'ORACLE_HOME=/usr/oracle,ORACLE_SID=orcl')
: : initorcl.ora
: : mts_dispatchers="tcp,1"
: : mts_max_dispatchers=3
: : mts_servers=1
: : mts_max_servers=5
: : mts_service=orcl
mts_listener_address="(ADDRESS=(PROTOCOL=tcp)(Host=pcstar)(Por
: : t=1521))"
: : If anybody started server in Multi-Thread mode, mail me
: : [email protected]
: : Best Regards!
: : Gennady Saldiga
: Hi!
: Same problem occured on my environment (Debian GNU/Linux 2.0).
: But I succeeded to start Multi-thread server on ipc protocol.
: My current configuration file (mts_* in init.ora) as follows:
: mts_dispatchers="ipc,1"
: mts_max_dispatchers=10
: mts_servers=1
: mts_max_servers=10
: mts_service=orcl
: # I confirmed mts_listener_address syntax by manual and
: # v$parameter.
: # Net8 Admn man says: If you have multiple MTS_LISTENER_ADDRESS
: # parameters, they must be adjacent to each other in your
: # initialization file.
mts_listener_address="(ADDRESS=(PROTOCOL=TCP)(host=j-00872)(port=
: 1521))"
: mts_listener_address="(ADDRESS=(PROTOCOL=IPC)(KEY=orcl))"
: So I tested MTS_DISPATCHERS parameter's other syntax.
: The test results are:
: # mts_dispatchers="ipc,1"
: # OK
: # mts_dispatchers="tcp,1"
: # ORA-00101,ORA-00102 occured
: # mts_dispatchers="TCP,1"
: # ORA-00101,ORA-00102 occured
: # mts_dispatchers="ipc,1","tcp,1"
: # ORA-00101,ORA-00102 occured
: # mts_dispatchers="(ADDRESS=(PARTIAL=YES)(PROTOCOL=tcp))"
: # ORA-00101,ORA-00102 occured
: # mts_dispatchers="(ADDRESS=(PARTIAL=NO)(PROTOCOL=tcp))"
: # ORA-00101,ORA-00102 occured
: # mts_dispatchers="(ADDRESS=(PARTIAL=YES)(PROTOCOL=ipc))"
: # OK
: # mts_dispatchers="(PROTOCOL=IPC) (DISPATCHERS=3)"
: # OK
: # mts_dispatchers="(PROTOCOL=TCP) (DISPATCHERS=3)"
: # ORA-00101,ORA-00102 occured
: # mts_dispatchers="(ADDRESS=(PROTOCOL=IPC)(KEY=orcl))
: (dispatchers=3)"
: # OK
mts_dispatchers="(ADDRESS=(PROTOCOL=TCP)(host=j-00872)(port=1521)
: ) (dispatcher
: s=3)"
: # ORA-00101,ORA-00102 occured
mts_dispatchers="(description=(ADDRESS=(PROTOCOL=IPC)(KEY=orcl))(
: connect_data=
: (sid=orcl))) (dispatchers=3)"
: # OK
mts_dispatchers="(description=(ADDRESS=(PROTOCOL=TCP)(host=j-0087
: 2)(port=1521)
: )(connect_data=(sid=orcl))) (dispatchers=3)"
: # ORA-00101,ORA-00102 occured
: ### While the test, sometimes ORA-00472 (ORA-00472: PMON
process
: ### terminated with error) occured when instance shutdown.
: ### I think the error reported in another message
: ### on the same thread.
: It seems dispatcher is not binded to tcp protocol adapter.
: Does anybody have more information about Multi-thread server
: using TCP protocol.
: ### Please forgive my bad english.
: Thank you.
: Satoshi Hirai
null

Does Firefox 13 run in a multi-threaded mode and can it utilize quad-core processors?

When purchasing a new PC, one chooses between dual-core vs. quad-core processors and some people claim that Firefox run in a mulch-threaded mode and treats each tab as a separate process and that it can fully utilize the advantage of a quad-core processor. Is that true?

Firefox doesn't treat each tab as a separate process. While this may be a feature sometime in the future, I don't know of any plans to introduce it anytime soon. Obviously, buying a quad core processor is going to be significantly faster than a dual-core, and your browser is usually less resource intensive than many other programs. I wouldn't use it as your purchasing decision. Firefox will run equally well on a dual-core or a quad-core, but windows and other programs will run better with 4 cores.

OCIServerAttach does not return in multi-threaded mode

RedHat 6.2, Oracle 8.1.5
With OCIInitialize mode is OCI_THREADED and OCIEnvInit mode is OCI_DEFAULT, and when another application thread is started prior to calling OCIServerAttach, OCIServerAttach never returns, and seems to lock up the app, as the previously started application thread also stops.
Changing the OCIEnvInit mode to OCI_NO_MUTEX allows OCIServerAttach to complete OK.
Anyone any idea where to start looking?
The following is the sample program I used to reproduce the problem:
#include <iostream.h>
#include <fstream.h>
#define GNUSOURCE
#include <unistd.h>
#include <pthread.h>
#include <oci.h>
void * busyBody(void * )
for( int i =0; i < 30; ++i )
cout << " busyBody..." << endl;
sleep(1);
return NULL;
int main()
pthread_t mId;
if( 0 != pthread_create( &mId, NULL/*attr*/, busyBody, NULL/*arg*/ ) )
cerr << "thread failed to start" << endl;
exit(1);
sleep(3);
OCIEnv *envhp;
OCIError *errhp;
OCIServer *srvhp;
OCISvcCtx *svchp;
int i = 0;
i = OCIInitialize((ub4) OCI_THREADED,
(dvoid *)0, //user defined context for the memory call back routines
(dvoid * (*)(dvoid *, size_t)) 0, //user-defined memory allocation function
(dvoid * (*)(dvoid *, dvoid *, size_t))0, //user-defined memory re-allocation function
(void (*)(dvoid *, dvoid *)) 0 ); //user-defined memory free function
i = OCIEnvInit( (OCIEnv **) &envhp, //a pointer to a handle to the environment
OCI_DEFAULT, //specifies initialization of an environment mode
(size_t) 0, //specifies the amount of user memory to be allocated
(dvoid **) 0 ); //returns a pointer to the user memory of size xtramemsz
i = OCIHandleAlloc( (dvoid *) envhp, //an environment or a statement handle
(dvoid **) &errhp, //returns a handle to a handle type
OCI_HTYPE_ERROR, //specifies the type of handle to be allocated
(size_t) 0, //specifies an amount of user memory to be allocated
(dvoid **) 0); //returns a pointer to the user memory of size xtramemsz
/* server/service contexts */
i = OCIHandleAlloc( (dvoid *) envhp,
(dvoid **) &srvhp,
OCI_HTYPE_SERVER,
(size_t) 0,
(dvoid **) 0);
i = OCIHandleAlloc( (dvoid *) envhp,
(dvoid **) &svchp,
OCI_HTYPE_SVCCTX,
(size_t) 0,
(dvoid **) 0);
// Creates an access path to a data source for OCI operations
cout << "before OCIServerAttach" << endl;
i = OCIServerAttach( srvhp, //an uninitialized server context handle
errhp, //an error handle which can be passed to OCIErrorGet()
// assume local server
0, //specifies the database (server) to use(specifies a connect string or a service point)
0, //length of previous parm
OCI_DEFAULT); //specifies the various modes of operation. For release 8.0, pass as OCI_DEFAULT
cout << "after OCIServerAttach" << endl;
sleep(3);
return 0;
}

Firefox doesn't treat each tab as a separate process. While this may be a feature sometime in the future, I don't know of any plans to introduce it anytime soon. Obviously, buying a quad core processor is going to be significantly faster than a dual-core, and your browser is usually less resource intensive than many other programs. I wouldn't use it as your purchasing decision. Firefox will run equally well on a dual-core or a quad-core, but windows and other programs will run better with 4 cores.

Found dead multi-threaded server

hi all
My database is not running in multithread mode.
mts_dispatchers = "(protocol=TCP)"
I am getting such error
found dead multi-threaded server 'S000', pid = (8, 4)
Pl guide me
suresh

go on metalink http://metalink.oracle.com
Good Luck,
Fred

Multi thread and deadlocks

I am running dataload from a text file to MS SQL SRVR database. The jobs are running in multi thread mode. I am getting deadlock errors with threads.
each thread is supposed to delete records.
with single thread mode log file order is as below
1. get product to be deleted A
2. delete A
3. get product to be deleted B
4. delete B
5. get product to be deleted C
6 delete C
with multi thread mode
1. get product to be deleted A
2. get product to be deleted B
3. get product to be deleted C
4. get product to be deleted D
5. delete A
6. get product to be deleted E
7. get product to be deleted F
8. deadlock while deleteing the product B
Any clues what is going wrong here?
Here is the code for the delete method:
================================
PreparedStatement prepStatement = null;
System.out.println("get product to be deleted " + product);
prepStatement = conn.prepareStatement("delete from MYTABLE where product = ? ");
prepStatement.setString(1, product);
prepStatement.executeUpdate();
================================
Please note that only unique data is sent to each thread.
Any help is greatly appreciated.
Thanks

Thanks for the responses. I need to do update/insert new records after delete operation is completed. Later at the end of the db changes, i close the connection.
From my understanding deadlocks happen when both threads try to touch the same record same time. But, i am sending unique records for each thread. Unless these is somethign wrong with the query, it should always return unique values.
This is the query that sends unique records for each thread in sql srvr.
select distinct top ? columnA, columnB from MyTable where processed = 'FALSE' and columnB = ? "
This should be equivalent of oracle query
select distinct columnA, columnB from MyTable where columnB=? rownum > ? and rownum <= ?
if the top in sql srvr is equivalent to rownum in oracle then i always get distinct records and there should be no deadlocks.
Any help?
Thanks

VI calling from a multi-thread Teststand

Hello,
My test system tests four UUTs at the same time(with batch mode in TS), the code is based on LabVIEW and call from TS, so every step the same VI will be accessed by four thread. however, it runs quite slow even i set the reentrant execution in VI propertise.
My Quesition:
Can I do it like this in multi-thread mode of TS?
How can I make it fast? (convert VI to dll?????)
Any help will be appreciated.
Thanks,Steven

Hello Allen,
Thanks for your help.
Problem: I have a LabVIEW VI with parallel code blocks. These blocks run in parallel as expected when I run my VI directly or from a top level VI. However, the code blocks seem to run sequentially when I call my VI from TestStand. Why is this happening and how can I fix it?
Solution: In order to fix this behavior, simply set the VI Properties of "Execution" of your LabVIEW VI to "Other 1" or "Other 2". This change will make the parallel code blocks in your LabVIEW VI run in parallel as expected. To change this setting, from your LabVIEW VI, go to File»VI Properties. Select the Execution category. Change the Preferred Execution System to be either other 1 or other 2.
You need to make this change to any LabVIEW VI with parallel code blocks that is called from TestStand. The reason for this is that TestStand is using the LabVIEW ActiveX interface to run LabVIEW VIs. The LabVIEW ActiveX interface sets the caller's execution system to "User Interface" by default. This execution system is not recommended for a VI with parallel code blocks. If your LabVIEW VI's execution system is set to "Same as caller" (which is the default setting when creating a new LabVIEW VI), then it is executed in the User Interface thread when run through the LabVIEW ActiveX interface. This prevents the blocks to be executed in parallel.
In fact, only one block in my LabVIEW code, but it accessed by four thread from TS. I am sure that my VI can be accessed by four thread simultaneously if I enable the reentrant excution in VI property. I also have tried what mentioned in above document but no use.
However, if i only add a 1000ms delay to my LabView code instead of the 'calculation', it is fast enough! what is happening or something i set wrong?
I don't want to convert all my LabView code to DLL cos too many VIs here, and difficult for mantenance either.
Any other good solution???
Thank you Allen...
Steven

Multi-threaded?

When a MessageListener is attached to a queue, are the messages received in multi-threaded mode? I have some global-variables to be taken care.
thanks for any help.

Message listeners have their own thread which is created for them by the client runtime.

Multi-thread failure - Error in assignment

Hello
I have a c++ program processor running under Windows XP with Oracle 9i. My program access to oracle by an ODBC driver version 9.2.0.4.0. It could be launched in multi-thread to increase performance. When I launch it with one thread everything is fine. When I use several threads I have problems. ODBC driver returns to me a "error in assignment ... General error" message and my updates queries failed. Under SQl server it works without problems. It seems to be a kind of deadlock. When I disable check box in my odbc driver of "enable query timeout" my program encounter a problem and freezes...
Could someone help me ?

user13335017 wrote:
I have thought of the above solutions as workable, however, it is not. Some exhibited errors are:
A. "Attempt to use database while environment is closed." This error applies to 2, 3 and 4 all the way;
B. "Attempt to read / write database while database is closed." This error applies to 3 in particular;
C. "Attempt to close environment while some database is still open." This error applies to 5.
Please help me with designing a better strategy to solve the concurrent issue. Many thanks in advance.All these are expected errors. You should design the application so that you do not close an environment handle while database handles are still open, keep database handles open for as long as operations need to be performed on the underlying databases, open the database handles after opening the database handles, and close database handles before closing the environment handle.
In short, in pseudo-code, you should have something like this:
- open environment handle,
- open database handles,
- perform whatever operations are needed on the databases,
- close database handles,
- close environment handle.
You can refer to the Getting Started with Data Storage and the Getting Started with Transaction Processing guides appropriate for the API you are using, from the Berkeley DB documentation page.
Regards,
Andrei

"Inconsistent cursor cache. Out of range cursor" error on dual processor multi thread

I have a C++ with Pro*C++ COM object running on a Win2000 OS on
a dual processor Middleware. The program is being called by a
service in a multi threaded way. An oracle error like ORA-2103
and SQL-02103 will be generated after running the program. We've
tried putting mutex on every SQL statement in Pro*C and it works
but the systems became very very slow. We concluded that the
error might be cause by a collision of threads accessing the
same Table or different tables having foreign constraints. This
is so because the error keeps coming from a statement accessing
Table A and following errors comes from a Table B having a
foreign key on Table A.
Our only solution now is to put Mutex on Statements accessing
same tables or tables with foreign constraints but this will
make our system run very very slow. I dont know if the problem
is in our Oracle Database because we already upgraded our system
from 8.1.6 to 8.1.7. The wierd thing on this is that the system
is running smoothly without oracle errors on a SINGLE PROCESSOR
Middleware. Hope you can give me any insights on this problem.

I have a C++ with Pro*C++ COM object running on a Win2000 OS on
a dual processor Middleware. The program is being called by a
service in a multi threaded way. An oracle error like ORA-2103
and SQL-02103 will be generated after running the program. We've
tried putting mutex on every SQL statement in Pro*C and it works
but the systems became very very slow. We concluded that the
error might be cause by a collision of threads accessing the
same Table or different tables having foreign constraints. This
is so because the error keeps coming from a statement accessing
Table A and following errors comes from a Table B having a
foreign key on Table A.
Our only solution now is to put Mutex on Statements accessing
same tables or tables with foreign constraints but this will
make our system run very very slow. I dont know if the problem
is in our Oracle Database because we already upgraded our system
from 8.1.6 to 8.1.7. The wierd thing on this is that the system
is running smoothly without oracle errors on a SINGLE PROCESSOR
Middleware. Hope you can give me any insights on this problem.

"SQL-02103: Inconsistent cursor cache." error on a dual processor multi threaded apps

I have a C++ with Pro*C++ COM object running on a Win2000 OS on
a dual processor Middleware. The program is being called by a
service in a multi threaded way. An oracle error like ORA-2103
and SQL-02103 will be generated after running the program. We've
tried putting mutex on every SQL statement in Pro*C and it works
but the systems became very very slow. We concluded that the
error might be cause by a collision of threads accessing the
same Table or different tables having foreign constraints. This
is so because the error keeps coming from a statement accessing
Table A and following errors comes from a Table B having a
foreign key on Table A.
Our only solution now is to put Mutex on Statements accessing
same tables or tables with foreign constraints but this will
make our system run very very slow. I dont know if the problem
is in our Oracle Database because we already upgraded our system
from 8.1.6 to 8.1.7. The wierd thing on this is that the system
is running smoothly without oracle errors on a SINGLE PROCESSOR
Middleware. Hope you can give me any insights on this problem.

I have a C++ with Pro*C++ COM object running on a Win2000 OS on
a dual processor Middleware. The program is being called by a
service in a multi threaded way. An oracle error like ORA-2103
and SQL-02103 will be generated after running the program. We've
tried putting mutex on every SQL statement in Pro*C and it works
but the systems became very very slow. We concluded that the
error might be cause by a collision of threads accessing the
same Table or different tables having foreign constraints. This
is so because the error keeps coming from a statement accessing
Table A and following errors comes from a Table B having a
foreign key on Table A.
Our only solution now is to put Mutex on Statements accessing
same tables or tables with foreign constraints but this will
make our system run very very slow. I dont know if the problem
is in our Oracle Database because we already upgraded our system
from 8.1.6 to 8.1.7. The wierd thing on this is that the system
is running smoothly without oracle errors on a SINGLE PROCESSOR
Middleware. Hope you can give me any insights on this problem.

"SQL-02103 Inconsistent cursor cache." error on dual processor multi threaded system

I have a C++ with Pro*C++ COM object running on a Win2000 OS on
a dual processor Middleware. The program is being called by a
service in a multi threaded way. An oracle error like ORA-2103
and SQL-02103 will be generated after running the program. We've
tried putting mutex on every SQL statement in Pro*C and it works
but the systems became very very slow. We concluded that the
error might be cause by a collision of threads accessing the
same Table or different tables having foreign constraints. This
is so because the error keeps coming from a statement accessing
Table A and following errors comes from a Table B having a
foreign key on Table A.
Our only solution now is to put Mutex on Statements accessing
same tables or tables with foreign constraints but this will
make our system run very very slow. I dont know if the problem
is in our Oracle Database because we already upgraded our system
from 8.1.6 to 8.1.7. The wierd thing on this is that the system
is running smoothly without oracle errors on a SINGLE PROCESSOR
Middleware. Hope you can give me any insights on this problem.

I have a C++ with Pro*C++ COM object running on a Win2000 OS on
a dual processor Middleware. The program is being called by a
service in a multi threaded way. An oracle error like ORA-2103
and SQL-02103 will be generated after running the program. We've
tried putting mutex on every SQL statement in Pro*C and it works
but the systems became very very slow. We concluded that the
error might be cause by a collision of threads accessing the
same Table or different tables having foreign constraints. This
is so because the error keeps coming from a statement accessing
Table A and following errors comes from a Table B having a
foreign key on Table A.
Our only solution now is to put Mutex on Statements accessing
same tables or tables with foreign constraints but this will
make our system run very very slow. I dont know if the problem
is in our Oracle Database because we already upgraded our system
from 8.1.6 to 8.1.7. The wierd thing on this is that the system
is running smoothly without oracle errors on a SINGLE PROCESSOR
Middleware. Hope you can give me any insights on this problem.

"SQL-02103: Inconsistent cursor cache." error on dual processor multi thread apps

I have a C++ with Pro*C++ COM object running on a Win2000 OS on
a dual processor Middleware. The program is being called by a
service in a multi threaded way. An oracle error like ORA-2103
and SQL-02103 will be generated after running the program. We've
tried putting mutex on every SQL statement in Pro*C and it works
but the systems became very very slow. We concluded that the
error might be cause by a collision of threads accessing the
same Table or different tables having foreign constraints. This
is so because the error keeps coming from a statement accessing
Table A and following errors comes from a Table B having a
foreign key on Table A.
Our only solution now is to put Mutex on Statements accessing
same tables or tables with foreign constraints but this will
make our system run very very slow. I dont know if the problem
is in our Oracle Database because we already upgraded our system
from 8.1.6 to 8.1.7. The wierd thing on this is that the system
is running smoothly without oracle errors on a SINGLE PROCESSOR
Middleware. Hope you can give me any insights on this problem.

I have a C++ with Pro*C++ COM object running on a Win2000 OS on
a dual processor Middleware. The program is being called by a
service in a multi threaded way. An oracle error like ORA-2103
and SQL-02103 will be generated after running the program. We've
tried putting mutex on every SQL statement in Pro*C and it works
but the systems became very very slow. We concluded that the
error might be cause by a collision of threads accessing the
same Table or different tables having foreign constraints. This
is so because the error keeps coming from a statement accessing
Table A and following errors comes from a Table B having a
foreign key on Table A.
Our only solution now is to put Mutex on Statements accessing
same tables or tables with foreign constraints but this will
make our system run very very slow. I dont know if the problem
is in our Oracle Database because we already upgraded our system
from 8.1.6 to 8.1.7. The wierd thing on this is that the system
is running smoothly without oracle errors on a SINGLE PROCESSOR
Middleware. Hope you can give me any insights on this problem.

Oraclient9i.dll error in multi threaded delphi server application

I created a multi threaded server application in delphi using oracle9i and indy server components. When I run my application, I am getting an error "oraclient9i.dll" error when executing my SQL statements. I have check communication between my server application and the client application without using oracle and its working fine, its only when I started executing SQL statements when I got this error.
Can anybody help me with this problem or point me to the right direction on how to resolve this issue.
thanks

> I have tried what you suggested. I have created a
seperate TOracleSession on each thread that I create
on the OnConnect event however I am having Problems
using the oraclesession created on the OnExecute
event. Somehow it is still executing the SQL that I
have created on the main form where I first opened an
oraclesession component created on the main form.
It sounds then like the TOracleSession object in the thread is a copy of the one in the main thread/form.
> Do you think that It would work if I create an
instance of the TOracleDatasets and TOracleQuery on
the OnExecute event and also at the same time create
my TOracleSession on this event and continue
processing the data receive from the client server.
I've never used the Indy components for threading. The default TThread class worked just fine for me.
What I used to do is define the session and database objects as privates in my new thread class (let's call it TThreadSQL) - which was subclassed from TThread.
The constructor of this new TThreadSQL class did the following (writing here purely from memory - have not done Delphi for some time now): constructor TThreadSQL.Create( TNSalias, username, password : string );
// constructor is called with the Oracle session connection details
begin
inherited Create; // call the parent class constructor
CreateOracleSession; // call own private method to create an Oracle connection
end;
The CreateOracleSession method would then:
- create a BDE Session (TSession) object
- create a BDE Database (TDatabase) object, using the BDE Oracle native driver and an Oracle TNS alias plus username and password for connection
The destructor would close the connection. The Execute method which is used to fire up the thread, would use a TQuery object (or whatever) to execute a SQL using it owns connection.

Found Dead Multi-Threaded Server Error!!!

I am in the process of testing an application based on EJBs deployed on an Oracle 8.1.5 database.
Some times the whole instance chashes without any obvious reason.
The error reported in the Alert file is
"found dead multi-threaded server 'SOOO',pid(8,1). Terminating Instance".
I check my code and i think that there is no problem with cleaning up resources. I increased also the JAVA_POOL_SIZE and LARGE_POOL_SIZE size without any result.
Can anybody give me a hint for the error cause?
Thanks in advance.
null

go on metalink http://metalink.oracle.com
Good Luck,
Fred

Error behaviour in multi-threaded mode

Similar Messages

Maybe you are looking for