BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
jubikunjumon
Fluorite | Level 6

Hi,

Can anyone guide in resolving the below issue.

While running the query in EG getting following error "Incorrect length in SAS Metadata Repository for columns ABC".  After looking at the structure of oracle database i could see that ABC column is having character length of 40 while in EG its showing up with  140,  Any way that we can update in SAS Mangement console and will this  http://support.sas.com/kb/38/707.html help us in resolving the issue, since we need are having multiple environments

 

Regards

Jubi

1 ACCEPTED SOLUTION

Accepted Solutions
Patrick
Opal | Level 21

The KB you reference is only for the specific case where you're using DBSASTYPE= in your libname definition. Is this the case for you?

 

If not then I believe you could just change the column metadata definition in the table so it's in sync with what you have in Oracle (not sure but I would just try in a DEV environment, may be first by playing around on a copy of the existing table metadata object to not impact on anything existing).

 

In case you're using the table metadata not only in EG but also with tools like DIS then you will have to do some impact analysis first in order to determine where else you have to amend things.

 

I personally don't like to use the meta engine for EG. Is there any reason you have to?

View solution in original post

2 REPLIES 2
Patrick
Opal | Level 21

The KB you reference is only for the specific case where you're using DBSASTYPE= in your libname definition. Is this the case for you?

 

If not then I believe you could just change the column metadata definition in the table so it's in sync with what you have in Oracle (not sure but I would just try in a DEV environment, may be first by playing around on a copy of the existing table metadata object to not impact on anything existing).

 

In case you're using the table metadata not only in EG but also with tools like DIS then you will have to do some impact analysis first in order to determine where else you have to amend things.

 

I personally don't like to use the meta engine for EG. Is there any reason you have to?

jubikunjumon
Fluorite | Level 6

Hi Patrick,

 

Thanks for sharing an update for the query

 

 

The KB you reference is only for the specific case where you're using DBSASTYPE= in your libname definition. Is this the case for you? NO ,

 

I think the below option which you have specified sounds good, will try to take the backup of the metadata in SMC before replicating the changes. Will try to go through dev env. 

 

If not then I believe you could just change the column metadata definition in the table so it's in sync with what you have in Oracle (not sure but I would just try in a DEV environment, may be first by playing around on a copy of the existing table metadata object to not impact on anything existing).

 

 

there is no specfic reason for doing this in EG will try to have in DIS

sas-innovate-2024.png

Don't miss out on SAS Innovate - Register now for the FREE Livestream!

Can't make it to Vegas? No problem! Watch our general sessions LIVE or on-demand starting April 17th. Hear from SAS execs, best-selling author Adam Grant, Hot Ones host Sean Evans, top tech journalist Kara Swisher, AI expert Cassie Kozyrkov, and the mind-blowing dance crew iLuminate! Plus, get access to over 20 breakout sessions.

 

Register now!

SAS Enterprise Guide vs. SAS Studio

What’s the difference between SAS Enterprise Guide and SAS Studio? How are they similar? Just ask SAS’ Danny Modlin.

Find more tutorials on the SAS Users YouTube channel.

Click image to register for webinarClick image to register for webinar

Classroom Training Available!

Select SAS Training centers are offering in-person courses. View upcoming courses for:

View all other training opportunities.

Discussion stats
  • 2 replies
  • 1741 views
  • 0 likes
  • 2 in conversation