On 10/30/06, Guy Spillman <[EMAIL PROTECTED]> wrote:
Have created a new user/schema to test with. The same problem exists. Oracle did not log anything to it's alert log. It has no problems with initializing and using it's tables the first time. The problem exists when you restart the server and it tries to access an existing empty file (/.locks).
very weird indeed. i debugged the code and verified that the empty /.locks file is successfully read using rs.getBinaryStream()... i hate to admit it but i am currently out of ideas/possible explanations. if you can distill a simple isolated test case that demonstrates your issue i'd give it another try, cheers stefan
Guy M. Spillman, Jr. On Sun, 29 Oct 2006 18:43:12 +0100, "Stefan Guggisberg" wrote: > > annie and guy, > > thanks for your feedback. did you test with an initially > empty schema? data from previous versions could > cause problems. > > strange, i know we had installs running on oracle 9i > without problems . at least there shouldn't be any > issues with OraclePersistenceManager, at least that's > what i thought. > > i quickly verified that it works with oracle 10. > i'll try to find an oracle 9i install for testing, > but that's not gonna be easy... > > if you could test again the current OracleFileSystem & > OraclePersistenceManager versions with a virgin > schema and report back any issues incl. full stack > traces > and log files that would be a great help. please attach > any log files to the jira iisue JCR-603 and add your > feedback > as comments. > > thanks for your help, > stefan
