Hi Ricardo,
Thanks for the info. Yes, the issue was on the database schema. I
noticed that some tables has extra fields in the new version.
I added it manually and it works now. Luckily most of the users have
the same CA DN : )
Regards
On Fri, Oct 12, 2012 at 10:44 PM, Ricardo Rocha <[log in to unmask]> wrote:
> Hi.
>
> Some additional info on this one.
>
> The difference is between the LFC versions, not really the
> distribution. We missed a couple of schema upgrade scripts in the
> packaging, which are documented in the known issues of the 1.8.3
> release:
> https://svnweb.cern.ch/trac/lcgdm/blog/official-release-lcgdm-183
>
> The information in that page is also valid for the LFC.
>
> """
> missing upgrade sql scripts with the new packaging
> """
>
> YAIM will fail to automatically upgrade the database due to this. Let
> us know if you need help applying the workaround, the schema change is
> minimal.
>
> Regards,
> Ricardo
>
>
> On Sat, Oct 6, 2012 at 8:34 PM, Maarten Litmaath
> <[log in to unmask]> wrote:
>> Hi Muhammad,
>>
>>
>>> Currently we are migrating our core services from gLite 3.2 to UMD-2.
>>> However we have some problem migrating our glite-LFC mysql database to
>>> UMD2-LFC mysql.
>>>
>>> I found that the UMD2-LFC and glite-LFC mysql's schema has some
>>> differences. Somehow the UMD2-LFC software unable to fetch the data
>>> because of different database schema.
>>>
>>> Is there any guide/tutorial on how to migrate gLite 3.2 LFC to UMD-2 LFC?
>>
>>
>> All admin docs should be available here:
>>
>> https://svnweb.cern.ch/trac/lcgdm/wiki/Lfc
>>
>> I suggest you open a GGUS ticket for the LFC developers to improve
>> the documentation if needed. Please include the YAIM command that
>> was used to configure the server and any errors and warnings that
>> appear in the YAIM log.
|