BookmarkSubscribeRSS Feed
☑ This topic is solved. Need further help from the community? Please sign in and ask a new question.
grudos20
Obsidian | Level 7

 

Hi all.

We deployed a test environment and applied the settings as a production environment, completely the same. Os Linux(utf -8) server encoding was chosen, local language is Portuguese.
But for some reason, the data pulled into SAS CIS is displayed in incomprehensible characters, as if the encoding has gone astray.
To check, we decided to connect the test environment to the database of the production environment, but we still get strange characters in SAS CIS, which means that the problem is not in the Oracle database.
The info-map is imported from the production circuit, but I don't think it could be the problem.
Please share your ideas what could be the reason?

 

 

grudos20_0-1656435115935.png

 

1 ACCEPTED SOLUTION

Accepted Solutions
grudos20
Obsidian | Level 7

Hi
The problem was solved, we added a few settings
On the operating system, the NLS we need was prescribed
export NLS_LANG=
After we added the encoding we needed in the file
...../SASHome/SASFoundation/9.4/sasv9_local.cfg
-encoding *substitute language*

Hope this helps someone

View solution in original post

7 REPLIES 7
grudos20
Obsidian | Level 7
A few more points that may be useful to understand:
1. Installation was carried out in the following order:
meta date 01, 02, 03 (configuration and installation of the cluster);
wipd (configuration and installation); SASAppMA (installer) ;
SASAppEM (installation); Middle tear (installer);
SASAppMA (configuration);
SASAppEM (configuration);
Middle tear (configuration);
Middle tear kit (configuration);
Middle tear cis (configuration);

On the production environment, the encoding is displayed correctly, but on the test environment, strange characters are displayed.
SASKiwi
PROC Star

Run PROC CONTENTS on one of the problem tables and post what the encoding is like this:

SASKiwi_0-1656557075573.png

 

 

grudos20
Obsidian | Level 7
Hey,
done:
Data Set NameWORK._PRODSAVAILObservations8
Member TypeDATAVariables6
EngineV9Indexes0
Created30.06.2022 10:26:34Observation Length78
Last Modified30.06.2022 10:26:34Deleted Observations0
Protection CompressedBINARY
Data Set Type Reuse SpaceNO
Label Point to ObservationsYES
Data RepresentationSOLARIS_X86_64, LINUX_X86_64, ALPHA_TRU64, LINUX_IA64SortedNO
Encodingutf-8 Unicode (UTF-8)  

 

This is a table from which data is opened incorrect CIS

The CONTENTS Procedure

Data Set NameCICOMMON.AGENT_INFOObservations.
Member TypeDATAVariables7
EngineORACLEIndexes0
Created.Observation Length0
Last Modified.Deleted Observations0
Protection CompressedNO
Data Set Type SortedNO
Label   
Data RepresentationDefault  
EncodingDefault  
Schema/Userci_commonEngine/Host Dependent Information
Client version:19.3.0.0.0
Server version:19.0.0.0.0
7AGENT_CLASSIFIERChar1020$1020.$1020.AGENT_CLASSIFIERAlphabetic List of Variables and Attributes# Variable Type Len Format Informat Label
1AGENT_IDNum8  AGENT_ID
2AGENT_NAMEChar1020$1020.$1020.AGENT_NAME
3CHANNEL_IDNum8  CHANNEL_ID
4CHANNEL_NAMEChar1020$1020.$1020.CHANNEL_NAME
5LEVEL_1Char84$84.$84.LEVEL_1
6LEVEL_2Char64$64.$64.LEVEL_2

 

 

SASKiwi
PROC Star

Might be worth just confirming your CIS session encoding by running this:

proc options option = encoding;
run;

I'd also recommend opening a SAS Tech Support track as CIS is a specialist product that not many on the Communities use.

grudos20
Obsidian | Level 7

Hi, thanks for the reply.
Unfortunately, CIS does not have a line or field for executing a command for a specific session. Accordingly, such a parameter must be written in the configuration file, but in which configuration file and in what form to enter the command - I do not know.
We cannot contact SAS support, because There are some complications, not that I don't want to.

SASKiwi
PROC Star

I've never used CIS, but behind the application would be a SAS Compute (App) server which you could start a "vanilla" SAS session on using Enterpriser Guide or SAS Studio. These would allow you to run any SAS code.

 

grudos20
Obsidian | Level 7

Hi
The problem was solved, we added a few settings
On the operating system, the NLS we need was prescribed
export NLS_LANG=
After we added the encoding we needed in the file
...../SASHome/SASFoundation/9.4/sasv9_local.cfg
-encoding *substitute language*

Hope this helps someone

suga badge.PNGThe SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment. 

Join SUGA 

Get Started with SAS Information Catalog in SAS Viya

SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 7 replies
  • 1087 views
  • 0 likes
  • 2 in conversation