What concerns me the most about Enterprise Guide
in [SAS]
|
From: xlr82sas on 11 Jan 2010 11:59 Hi SAS-Lrs, I am a novice EG programmer so this may not be true, but I think it is possible. Heavily used binary objects that are constantly updated(in place?) can become corrupted. I make very heavy use of my sasuser.profile and about every three months it appears to get damaged. I back it up and usually can repair it. It seems to me that EG project files would be heavily used binary objects susceptible to corruption. Here is what happens to my SASUSER.POFILE about every three months. ERROR: Write to SASUSER.PROFILE.CATALOG failed. File is full and may be damaged. ERROR: Catalog SASUSER.PROFILE.CATALOG is in a damaged state. Use the REPAIR command of PROC DATASETS to restore it ERROR: An internal error has occurred while reading a compressed file. Please call your SAS Site Representative and report the following: compress offset = 2146 , de-compress offset = 3579 , compress buf = " 732077696C6C206265206173736F63696174656420776974682043757272656E" . ERROR: Entry XX.SOURCE could not be repaired. Here is what the first few bytes of a EG project file looks like K ¤Æ;ã@æ©. Jö project.xmlì]{sÃFâÿ{Uû X®ÃM|µâ |m mòüHd +±ä8[Ã¥*Hâ¬Å½6²ÂâdÃÃwÿ  When I look at the binary, egp project file it looks like changes are somehow appeneded to the end of the binary file, but I am not sure. At any rate there does not seem to be any usable information in the binary egp catalog? I hope corruption is never an issue with heavily used egp project catalogs. Another issue is the fact that project files may not upward compatible. Can you repair egp binary files?
From: Joe Whitehurst on 11 Jan 2010 13:14 When I had the problem, I just sent the files to SAS Tech support who recovered everything and returned them to me promptly. On Mon, Jan 11, 2010 at 11:59 AM, xlr82sas <xlr82sas(a)aol.com> wrote: > Hi SAS-Lrs, > > I am a novice EG programmer so this may not be true, but I think it is > possible. > > Heavily used binary objects that are constantly updated(in place?) can > become corrupted. I make very heavy use of my sasuser.profile and > about every three months it appears to get damaged. I back it up and > usually can repair it. It seems to me that EG project files would be > heavily used binary objects susceptible to corruption. > > Here is what happens to my SASUSER.POFILE about every three months. > > ERROR: Write to SASUSER.PROFILE.CATALOG failed. File is full and may > be damaged. > ERROR: Catalog SASUSER.PROFILE.CATALOG is in a damaged state. Use the > REPAIR command of PROC DATASETS to restore it > > ERROR: An internal error has occurred while reading a compressed file. > Please call your SAS > Site Representative and report the following: compress offset =3D > 2146 , de-compress > offset =3D 3579 , compress buf =3D " > > 732077696C6C206265206173736F63696174656420776974682043757272656E" . > > > ERROR: Entry XX.SOURCE could not be repaired. > > Here is what the first few bytes of a EG project file looks like > > K =C2=A4 =C6=92; =C3=A3@=C3=A6=C2=A9. J=C3=B6 project.xml=C3= =AC]{s=C3=9BF=E2=80=99=C3=87=C2=BF{U=C3=BB X=C2=AE=C3=9DM|=C2=B5=E2=80=9D = |m m=C3=99=C2=B2=C3=BCHd > +=C2=B1=C3=A48[=C3=A5* H=E2=82=AC=C5=BD6=C2=B2=C2=AD=E2=80=9Cd=C3=87=C3= =9E w=C3=9D=C2=BF > > When I look at the binary, egp project file it looks like changes are > somehow appeneded to the end of the binary file, but I am not sure. At > any rate there does not seem to be any usable information in the > binary egp catalog? > > I hope corruption is never an issue with heavily used egp project > catalogs. Another issue is the fact that project files may not upward > compatible. Can you repair egp binary files? >
From: Phil Holland on 12 Jan 2010 05:30 EGP project files are just Zip files containing compressed text files, mostly XML, so they are not really binary files. As Zip files they can be opened using WinZip, 7-Zip, etc., you could fix them manually by editing the text files, if you know where the problem lies. Note that EG only writes to a Project File when you save, otherwise everything is done using temporary files and in memory, so they are low-activity files, unlike PROFILE.CATALOG. That said I would recommend saving fairly regularly. ...........Phil In message <96f18b62-c1c2-49df-a687-f413b1029c9d(a)k19g2000yqc.googlegroups.com>, xlr82sas <xlr82sas(a)aol.com> writes >Hi SAS-Lrs, > >I am a novice EG programmer so this may not be true, but I think it is >possible. > >Heavily used binary objects that are constantly updated(in place?) can >become corrupted. I make very heavy use of my sasuser.profile and >about every three months it appears to get damaged. I back it up and >usually can repair it. It seems to me that EG project files would be >heavily used binary objects susceptible to corruption. > >Here is what happens to my SASUSER.POFILE about every three months. > >ERROR: Write to SASUSER.PROFILE.CATALOG failed. File is full and may >be damaged. >ERROR: Catalog SASUSER.PROFILE.CATALOG is in a damaged state. Use the >REPAIR command of PROC DATASETS to restore it > >ERROR: An internal error has occurred while reading a compressed file. >Please call your SAS > Site Representative and report the following: compress offset = >2146 , de-compress > offset = 3579 , compress buf = " > >732077696C6C206265206173736F63696174656420776974682043757272656E" . > > >ERROR: Entry XX.SOURCE could not be repaired. > >Here is what the first few bytes of a EG project file looks like > >K??? ? ¤?ƒ;?ã@æ©. Jö? ? project.xmlì]{sÛF'Ç¿{Uû?X®ÝM|?” ?|m?mÙ²üHd >+±ä8[å*?H€Ž6²“dÇÞ??wÝ¿?? ?? > >When I look at the binary, egp project file it looks like changes are >somehow appeneded to the end of the binary file, but I am not sure. At >any rate there does not seem to be any usable information in the >binary egp catalog? > >I hope corruption is never an issue with heavily used egp project >catalogs. Another issue is the fact that project files may not upward >compatible. Can you repair egp binary files? > > -- -------------------------------------------------------- Philip R Holland Holland Numerics Ltd 94 Green Drift, Royston, Herts SG8 5BT, UK mobile : +44-(0)7714-279085 tel/fax: +44-(0)1763-244497 email : <phil(a)hollandnumerics.com> URL : http://www.hollandnumerics.com/ --------------------------------------------------------
From: xlr82sas on 12 Jan 2010 11:52 On Jan 12, 2:30 am, Phil Holland <p...(a)hollandnumerics.com> wrote: > EGP project files are just Zip files containing compressed text files, > mostly XML, so they are not really binary files.  As Zip files they can > be opened using WinZip, 7-Zip, etc., you could fix them manually by > editing the text files, if you know where the problem lies.  Note that > EG only writes to a Project File when you save, otherwise everything is > done using temporary files and in memory, so they are low-activity > files, unlike PROFILE.CATALOG.  That said I would recommend saving > fairly regularly. > > ..........Phil > > In message > <96f18b62-c1c2-49df-a687-f413b1029...(a)k19g2000yqc.googlegroups.com>, > xlr82sas <xlr82...(a)aol.com> writes > > > > > > >Hi SAS-Lrs, > > >I am a novice EG programmer so this may not be true, but I think it is > >possible. > > >Heavily used binary objects that are constantly updated(in place?) can > >become corrupted. I make very heavy use of my sasuser.profile and > >about every three months it appears to get damaged. I back it up and > >usually can repair it. It seems to me that EG project files would be > >heavily used binary objects susceptible to corruption. > > >Here is what happens to my SASUSER.POFILE about every three months. > > >ERROR: Write to SASUSER.PROFILE.CATALOG failed. File is full and may > >be damaged. > >ERROR: Catalog SASUSER.PROFILE.CATALOG is in a damaged state. Use the > >REPAIR command of PROC DATASETS to restore it > > >ERROR: An internal error has occurred while reading a compressed file. > >Please call your SAS > >    Site Representative and report the following: compress offset = > >2146 , de-compress > >    offset = 3579 , compress buf = " > > >732077696C6C206265206173736F63696174656420776974682043757272656E" . > > >ERROR: Entry XX.SOURCE could not be repaired. > > >Here is what the first few bytes of a EG project file looks like > > >K???  ? ¤?Æ;?ã@æ©.  Jö? ?  project.xmlì]{sÃFâÿ{Uû?X®ÃM|?â ?|m?mòüHd > >+±ä8[Ã¥*?Hâ¬Å½6²ÂâdÃÃ??wÿ?? ?? > > >When I look at the binary, egp project file it looks like changes are > >somehow appeneded to the end of the binary file, but I am not sure. At > >any rate there does not seem to be any usable information in the > >binary egp catalog? > > >I hope corruption is never an issue with heavily used egp project > >catalogs. Another issue is the fact that project files may not upward > >compatible. Can you repair egp binary files? > > -- > -------------------------------------------------------- > Philip R Holland > Holland Numerics Ltd >      94 Green Drift, Royston, Herts SG8 5BT, UK >      mobile : +44-(0)7714-279085 >      tel/fax: +44-(0)1763-244497 >      email  : <p...(a)hollandnumerics.com> >      URL   :http://www.hollandnumerics.com/ > --------------------------------------------------------- Hide quoted text - > > - Show quoted text - Thanks Phil, Showing my ignorance again. I changed the extension from egp to zip and winzip unziped the '.egp' project file. Very interesting all programs, settings .. seem to be in the project.xml and probably could be extracted into SAS programs. All the logs were in separate files. Would be nice to have the xml map for 'project.xml'. Regards
|
Pages: 1 Prev: proc fcmp crashes Next: Comparing a value to a range to create a cut point |