Hi guys,
I'm really in trouble now with a little application I've developped for a customer in Canada.
There is a big application which is in charge among other things to import a text file.
The datas are imported in an Oracle v8 DB .If the import succeeds it is possible to run an external program using a command line, that's where my program launchs. The problem is that the program doesn't reach the end and generates an error message.
I've seen using a trace that the import isn't far enough to have done all the commit and allow my program to make the updates it has to do, because some tables I need to update are also used in the import and of course I have to deal with the same record imported reading it from an Oracle table.
I hope you understand what I'm writing.
-If I run the program before the import, it's also possible but there is already a program which is run before the import, I haven't any problems.
-If I a run it outside the application neither.
I'm working with Oracle 9 in Western Europe.
When they try to run it outside the application they have a problem in reading the following sql statement. Maybe is a lock still sleeping in the darkness. ;-)
SELECT MAGRPNR_F FROM superuser.MONATSPLAN WHERE MANR_F = '42739200 ' and TAG_F = '5126'
The program stops at this point and at the end after a long time gives this error message:![[sad]](/data/assets/smilies/sad.gif "[sad] [sad]")
Error: 1013 from ODBC.Database : S1T00: [Oracle][ODBC][Ora]ORA-01013: user requested cancel of current operation
------------------------------------------------------------
Error: 3146 from DAO.Connection : ODBC--call failed.
Now here are my questions:
- is it possible in my program to check if the table I want to update is already locked by the other application ?
- is it possible that for some reasons a select like this one couldn't work in America because It seems to be, after the test I've made on their own test Pc, using a cable connection via PC Anywhere ? Isn't it there a problem of lock ?
Are the spaces after the value the reason of this error ?
Here if I run the SQL ,in SQL*plus, with or whitout spaces I always get a result
Any suggestions will really be appreciated![[bigears]](/data/assets/smilies/bigears.gif "[bigears] [bigears]")
Thanks in advance
Akinia
I'm really in trouble now with a little application I've developped for a customer in Canada.
There is a big application which is in charge among other things to import a text file.
The datas are imported in an Oracle v8 DB .If the import succeeds it is possible to run an external program using a command line, that's where my program launchs. The problem is that the program doesn't reach the end and generates an error message.
I've seen using a trace that the import isn't far enough to have done all the commit and allow my program to make the updates it has to do, because some tables I need to update are also used in the import and of course I have to deal with the same record imported reading it from an Oracle table.
I hope you understand what I'm writing.
-If I run the program before the import, it's also possible but there is already a program which is run before the import, I haven't any problems.
-If I a run it outside the application neither.
I'm working with Oracle 9 in Western Europe.
When they try to run it outside the application they have a problem in reading the following sql statement. Maybe is a lock still sleeping in the darkness. ;-)
SELECT MAGRPNR_F FROM superuser.MONATSPLAN WHERE MANR_F = '42739200 ' and TAG_F = '5126'
The program stops at this point and at the end after a long time gives this error message:
Error: 1013 from ODBC.Database : S1T00: [Oracle][ODBC][Ora]ORA-01013: user requested cancel of current operation
------------------------------------------------------------
Error: 3146 from DAO.Connection : ODBC--call failed.
Now here are my questions:
- is it possible in my program to check if the table I want to update is already locked by the other application ?
- is it possible that for some reasons a select like this one couldn't work in America because It seems to be, after the test I've made on their own test Pc, using a cable connection via PC Anywhere ? Isn't it there a problem of lock ?
Are the spaces after the value the reason of this error ?
Here if I run the SQL ,in SQL*plus, with or whitout spaces I always get a result
Any suggestions will really be appreciated
Thanks in advance
Akinia
