Skip to main content

Use the interactive ODBC Configuration Tool (dfdbconf) to add new data sources to the ODBC configuration

1. From the root directory of the dfexec.cfg installation, run: ./bin/dfdbconf.
2. Select A. to add a data source. You can also use dfdbconf to delete a data source if it
is no longer needed.
3. Select a template for the new data source by choosing a number from the list of
available drivers.
4. You are prompted to set the appropriate parameters for that driver. The new data
source is then added to your odbc.ini file.

Once you have added all of your data sources, the interactive ODBC Viewer (dfdbview)
application can be used to test your connection. For example, if you added a data source
called my_oracle, run: ./bin/dfdbview my_oracle (from the installation root) to test the
connection. You may be prompted for a user name and password. If the connection
succeeds, you will see a prompt from which you can enter SQL commands and query the
database. If the connection fails, DIS displays error messages describing one or more
reasons for the failure.

Note: When configuring the new data source, it is critical that the
parameters (such as DSN, host, port, and sid) match exactly those used to
create the job on the client machine.


AccountString []:
AuthenticationDomain []:
AuthenticationPassword []:
AuthenticationUserid []:
CharacterSet [ASCII]:
ColumnSizeAsCharacter [1]:

Installaation :

./bin/dfdbconf
/apps/sas/dataflux/dfpower/etc

root@localhost # cd /apps/sas/dataflux/dfpower
root@localhost # ./bin/dfdbview DW_production
DataFlux ODBC Viewer

Please provide a user ID and password for 'DW_production'.
(Leave the fields blank to connect without a user ID or password.)

User ID:

DW_production is the DSN name

Comments

Post a Comment

Popular posts from this blog

SAS 9.4 server startup order

In Linux / Unix OS we normally use sas.servers to start the services. The script in the background follows an order to start the services. It is important to follow the order to run the services correctly. In this post we can see what is the order to start / stop and to generate the sas.servers script. It is not really required to memorize the order because SAS provide an utility to create the sas.servers script automatically which will start / stop the service in order. Starting order SAS Metadata server Olap server SAS object spawner SAS / SHARE server SAS / connect spawner SAP table server SAP remote services SAS deployment tester server Stopping will be the same in reverse. How to create sas.server script? We can create sas.server script by using generate_boot_script.sh. if you have made any changes to your environment like adding a new server or spawner we can use the script to generate new sas.server. You can use the script even if you have removed the spanner o...
Post a Comment
Read more

Insufficient authorization to access PIPE error in SAS EG

Issue: When I tried to run SAS code in SAS Enterprise Guide it throws following errors: ERROR: Insufficient authorization to access PIPE. ERROR: Error in the FILENAME statement. Screenshot of error: Solution: This error occurs when you try to run OS commands in SAS code. To run the OS commands in SAS code you need to enable XCMD option. You check it in SAS Management Console by following below steps.   Open SMC -> Expand Servers -> Expand   In SASApp , expand Logical Workspace Server -> right click on Workspace Server. Click properties -> option tab -> advanced options -> launch properties. Check whether Allow XCMD is checked. The issue arises if the Allow XCMD is not checked. In above image, Allow XCMD option is not checked. It should be checked to run OS commands from SAS code. In Unix /Linux machines, this XCMD option can be enabled by using system option XCMD in sasv9 config file or workspaceserver.sh script f...
2 comments
Read more

SAS - CLI error trying to establish connection

Issue: User asked me to make a database connectivity to SQL Server. They provided following details SQL server hostname and ip address Database/DSN name Username Password I made entry in ODBC.ini file. You know, SQL Server entries were made in ODBC.ini and Oracle entries were made in TNS.ora file. Everything went fine, took back up of odbc.ini, made entry and saved the file. So to test this connection I ran the libname statement in SAS Enterprise Guide 6.1. It throwed following error. Error Message: My DB team showed that they are able to login   14 GOPTIONS ACCESSIBLE; 15 LIBNAME test ODBC DATASRC=SGE_DS SCHEMA=VST USER=sales PASSWORD=XXXXXXXXX; ERROR: CLI error trying to establish connection: [SAS/ACCESS to SQL Server][ODBC SQL Server Legacy Driver][SQL Server]Login failed for user 'sales'. Solution: First I suspected that Login failed for user 'sales' meant the password provided by DB team was wrong. They responded that they were able to login wi...
2 comments
Read more