Hi,
I executed a DIS job under SAS DATA INTEGRATION and it works well. But when i deployed the same job, i had the bellow error when i executed the sas program in shell script
"ERROR 22-7: Invalid option name DBM" in libname statement of etlstmp in SCD step.
I used SCD type 2 in this job.
thank you
Hi,
Check this SAS notes.Hope it helps...
http://support.sas.com/kb/42/242.html
http://support.sas.com/kb/36/253.html
Thanks,
Shiva
Hi,
I executed this libname in SAS server:
LIBNAME etlstmp ORACLE DBINDEX=YES DBSLICEPARM=(THREADED_APPS,6) READBUFF=1000 INSERTBUFF=1000 UPDATEBUFF=1000 PATH=CAMPAIN_PROD CONNECTION=GLOBAL SCHEMA=SASMARTMA USER=SASMARTMA PASSWORD="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" DBMSTEMP=YES;
I had the bellow error:
3589? LIBNAME etlstmp ORACLE DBINDEX=YES DBSLICEPARM=(THREADED_APPS,6) READBUFF=1000 INSERTBUFF=1000 UPDATEBUFF=1000 PATH=CAMPAIN_PROD CONNECTION=GLOBAL SCHEMA=SASMARTMA USER=SASMARTMA PASSWORD="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" DBMSTEMP=YES;
3590?
3589 LIBNAME etlstmp ORACLE DBINDEX=YES DBSLICEPARM=(THREADED_APPS,6)
3589! READBUFF=1000 INSERTBUFF=1000 UPDATEBUFF=1000 PATH=CAMPAIN_PROD
3589! CONNECTION=GLOBAL SCHEMA=SASMARTMA USER=SASMARTMA
3589! PASSWORD="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" DBMSTE
------
22
ERROR 22-7: Invalid option name DBMSTE.
3590 MP=YES;
--
22
ERROR 22-7: Invalid option name MP.
But when i deleted some options in this libname "READBUFF=1000 INSERTBUFF=1000 UPDATEBUFF=1000" i didn't have any error.
there is a restriction in the length of SAS libname?
Thank you
Strange, seems like you could open a track to tech support.
Is this code generated from a libname definition, or have you entered it by yourself?
Is this an encoded passwort you're using?
I'm just guessing but may be the passwort contains a character which messes up things. You could try to %quote() it.
Is this just a deployd job which throws the error (and works when running directly in DIS) - or did you somehow copy the code; eventually even to another machine with a different code page?
If it's just a deployed job causing the issue then it's definitely a case for our friends from SAS Tech Support.
Hi,
Thank you.
This code is generated from a libname definition. This problem was resolve after that we changed the database password to reduce the length of libname statement.
Join us for SAS Innovate 2025, our biggest and most exciting global event of the year, in Orlando, FL, from May 6-9.
Early bird rate extended! Save $200 when you sign up by March 31.
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.