| remote process dies when selecting "large" table over dblink [message #367814] |
Tue, 05 September 2000 08:32  |
A.Haunschmidt
Messages: 2
Registered: September 2000
|
Junior Member |
|
|
Please help!
I've got a serious problem:
A job (PL/SQL Packages) on instance A tries to select
rows from a remote table on instance B using a database link.
The fetched rows from B are then inserted into the
table on A. This works for thousands of rows,
until the remote session on B dies and the loading
process on A waits forever for a response, without recognizing ,
that its remote conterpart session B is dead.
Both instances are version 8.1.6, running on NT,
each table contains about 50.000.000 rows.
It seems, that the problem arises, when the size of
the tables reach a imaginary limit: same trouble with
transferring 2 other tables of similar size.
How to fix this?
Are there any parameters, which influence
this behaviour (timeout,etc.)?
Many thanks in advance,
Andreas.
|
|
|
|
| Re: remote process dies when selecting "large" table over dblink [message #367815 is a reply to message #367814] |
Tue, 05 September 2000 21:34  |
freedba
Messages: 9
Registered: September 2000
|
Junior Member |
|
|
these are the my understanding and some of these i haven't tried . so i hope these will help you ..
1.Dblink is not suitable for the huge sort or query especially the report query .
2.try to check the temporary tablespace and sort size .
3.this might cause by the network because the waiting time is too long .
4.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
