About ruturaj72

DaveHorne · ‎10-22-2018

Hi @ruturaj72, I checked the 9.3 doc on LOGPARM and the options appear the same. The only time I've seen the situation you describe is when I forget the ROLLOVER option. If that looks ok then you may need to open a track with tech support.

JuanS_OCS · ‎07-23-2018

Hello @ruturaj72, I would investigate a bit further, about the metadata and db permissions of the user who actually registers the table, and the one who updates the table. Check the permissions on the data and metadata (including folders and library) Perhaps also worth to check the options set for the library. Sometimes just an option makes a difference, such as the case sensitivity or the symbols.

alexal · ‎07-18-2018

@iscgonzalez, These messages occur when a SAS Application Server (often referred to as SASApp) contains an unresolvable host name that is defined in metadata. To resolve this issue, verify that the host name for the application server is correctly defined in SAS® Management Console. http://support.sas.com/kb/17/602.html

ruturaj72 · ‎07-17-2018

@JuanS_OCS Hey Juan, Thanks a lot for your response. understood in a better way.

Online Status	Offline
Date Last Visited	‎10-19-2018 03:57 AM

Re: Setting up ALTLOG in SASV9.cfg FIle

Re: Machine name could not be resolved to an ip address

Unable to update Metadata of one Oracle Table

Re: On which port sas responds back to client machine

On which port sas responds back to client machine

Unable to update Metadata of one Oracle Table

Re: On which port sas responds back to client machine

On which port sas responds back to client machine

Re: Setting up ALTLOG in SASV9.cfg FIle

Re: Unable to update Metadata of one Oracle Table

Re: Machine name could not be resolved to an ip address

Re: On which port sas responds back to client machine