Hi Andrey, actually I didn't read any record. I described how it behaves just during first interactions with updated Orientdb server and old database files(first command I believe). Let me try to prepare a test database to reproduce it without a need to send whole production database.
Pawel On Monday, August 4, 2014 6:45:28 AM UTC+2, Andrey Lomakin wrote: > > Hi Pawel, > Do not think that those issues are related, because otherwise you will not > be able to read any record of any data. > > But we need to fix it. > How am I able to reproduce it ? Could you send me your database and I will > do some steps to reproduce this issue ? > > > On Sun, Aug 3, 2014 at 12:56 AM, Pawel K. <[email protected] <javascript:>> > wrote: > >> Seems that problem appeared after fix #2640. >> >> After this commit I am starting to receive >> >> 2014-08-02 23:49:58:915 SEVE Database's schema is empty! Recreating the >> system classes and allow the opening of the database but double check the >> integrity of the database [OSchemaShared] >> 2014-08-02 23:49:58:979 WARN Repairing security structures... >> [OSecurityShared] >> 2014-08-02 23:49:59:062 WARN Repair completed [OSecurityShared] >> >> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "OrientDB" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Best regards, > Andrey Lomakin. > > Orient Technologies > the Company behind OrientDB > > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
