weirds problems after upgrade from 7.5.00.18 to 7.5.00.19

    bonjour,


I upgraded from 7.5.00.18 to 7.5.00.19.
I downloaded the python patch SDBPY.TGZ, because I got an error when I
tried to install 'Script interfaces'
Everything went fine.
Then I loaded system tables. No error.

I use 2 databases instance, say TEST and PROD
I connect to these instances with the same python scripts
(sapdb-python-linux-7.5.00.16) and the same dbprocs.

Now the weird things...

One script connects, performs an insert and do not commit.
The second, following, launches a dbproc: this dbproc tries to get a key
value inserted by the first one, then inserts other values in other tables,
depending on input parameters. The transaction is commited if no exception
is caught.

Everything worked perfectly with 7.5.00.18 version.

But now:

* it's ok on TEST instance
* on PROD instance, the first insert is performed and the session commited
  after the second one.
  There is no error but the second phase seems to have been skipped
  (no inserts). Remember, I work with the same scripts and dbproc.
# on both instances, ireport cannot find any row by pk on the first table
  wrote by script one, but can find rows with another column in the query.

  [22:38]jm@espinasse > ireport -d TEST
  SAP DB Terminal Report 0.3.3
  Type 'help' for help.
  An empty line repeats the last command
  ==> select * FROM FLUXFINANCIER where NOPIECE=696
  
|NOPIECE|NOFACTURE|DATEFACTURE|IDETABLISSEMENT|DATEREGLEMENT|IDMODEREGLEMENT|NOCOMPTE|
  
+-------+---------+-----------+---------------+-------------+---------------+--------+
  <<<End of Cursor>>>
  ==> select * FROM FLUXFINANCIER where NOFACTURE='retro-20041122'
  
|NOPIECE|NOFACTURE|DATEFACTURE|IDETABLISSEMENT|DATEREGLEMENT|IDMODEREGLEMENT|NOCOMPTE|
  
+-------+---------+-----------+---------------+-------------+---------------+--------+
  |696|retro-20041122|20041122|3409-001|?|?|?|
  ==> Q

Humm ?! Any idea ? (no error in knldiag.err)


-- 
jm


-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=gcdm-maxdb@xxxxxxxxxxx