syslogins changed in ASE15 upgradation using dump and load

[sybanva]

Hi Folks!!

syslogins system table is changed in ASE 15 from ASE 12.5, It has more coloum related for lock reason, lock date, suid which locked this login etc.

If you doing upgrade from 12.5 to 15.0 using dump and load, and your dataserver has around 20+ logins you may need to be very cautious, in that case bcp in of syslogins(of ASE 12.5) wont possible in ASE15 and you can not create 50-100 logins manually using sp_addlogin with same as ASE 12.5 config(same password, settings) .

In my case , we manually edited our bcp out file of ASE 12.5 and added same no seprator to excatly matched the coloumns of ASE 15 and did the bcp in. It worked.

Before editing of bcp in file, make sure you have a copy of that file, and edit it very carefully with seprator, wth no new line char.

If you have done it in some other way, share with all!


Thanks

[sybanva]

I came accross one more method as below:

Before doing bcp out, We can create new syslogins_temp table same as ASE15.0 syslogins with new coloums and perform select into from ASE12.5 syslogins in this new syslogins_temp table after that take the bcp out from syslogins_temp and, after final upgrade bcp in...no problem at all ...

Its very safe..!!

[akilme]

Yes I agree sybanva, this is the safest and most preferred method for doing this. But how is this taken care in case of inplace upgrade. Does the ugrade process itself takes care of the syslogins table when we run the upgrade script?