!! Hello Team !!
We are using SAS DI STUDIO 9.4
I have one SAS DI ETL. I have worked on this etl from last 15 days . We had done multiple steps in this etl and use many transformations,Today after save this etl and try to reoprn , its not opening.Its load for sometime and then close automatically.
Now i dont have any backup (.spk) file for this etl.Can anyone help me how can i get back my etl. It is very important etl in my project.
Is there anyway to get back my job from the dms server (If server have any automatic backfile)
OR
Is possible to get my etl backup sas code(which is also help me to create new job)
Below i mentioned some trial which i already done but it not succesfully working
1) export the job spk file after crash the job and try to import that but still its not opening.
2) try to open etl from the diffrent user
please provide me guidlines to solve this truble.
If your job gets too big, you may need more memory to open it. A guide to fixing that is available here: https://rawsas.com/improve-performance-of-di-studio-client/
You have corrupt metadata. This happens under special circumstances like when a job is checked out, and the job reads or writes a table that is not checked out to the same user. If tableI is modified, it can result in columns that exist in metadata without a name, and this causes the job to close right after opening.
It can be fixed by deleting the nameless columns in metadata, which can be done in the metadata browser found under "solutions" in SAS Display Manager. I can't show how to fix it today, because our SAS installation is down over the weekend for upgrade, but I will follow up in the coming week.
Thank you so much @ErikLund_Jensen , For your guidence,Next time i make sure all these things which you notify.
I hope in comming week you give us solution to how to do this activity in SAS Display manager.
We are waiting for your response with solution.
Thanks,
I have discussed your problem with my coworkers. We have seen the problem with a job opening and closing again immediately without displaying the job flow several times. It has occurred in different situations, so we cannot pinpoint one specific event that causes the problem, but we have discovered that each time there was one or more table columns in metadata with an empty name attribute.
We have solved the problem by giving the columns temporary names using the metadata browser as editor. Any name will do as long as it is a legal SAS column name and unique in the given table (we have used aaaa, bbbb etc.). Then the job will open, but some table columns now have the temporary names and must be renamed to the proper column names.
Of course I cannot know if your problem is caused by the same error, so I cannot guarantee my solution will work, but I think it is worth a try.
1. Open the metadata browser in SAS Display Manager (found under Solutions) and log into the relevant metadata server.
2. Make sure editing is enabled:
3. In the metadata Browser, click on Foundation to display list of Metadata Object Types, then Double Click on Columns to open list of all columns in the right pane. The column names are supposed to be in sorted order, but to be sure Click on the Name column to sort in ascending order, so empty names are listed from top.
4. Repeat for all columns with empty names:
5. Now the job is supposed to open, so you can proceed with changing column names in the tables used in the job.
I hope it works and I look forward to hear from you. Dont hesitate to write again if something is unclear or you think I can be of any further help. Best wishes from Erik.
Join us for SAS Innovate 2025, our biggest and most exciting global event of the year, in Orlando, FL, from May 6-9. Sign up by March 14 for just $795.
Need to connect to databases in SAS Viya? SAS’ David Ghan shows you two methods – via SAS/ACCESS LIBNAME and SAS Data Connector SASLIBS – in this video.
Find more tutorials on the SAS Users YouTube channel.