Digital Developer Conference: a FREE half-day online conference focused on AI & Cloud – North America: Nov 2 – India: Nov 9 – Europe: Nov 14 – Asia Nov 23 Register now

Refine your search by using the following advanced search options.

Criteria	Usage
Questions with keyword1 or keyword2	keyword1 keyword2
Questions with a mandatory word, e.g. keyword2	keyword1 +keyword2
Questions excluding a word, e.g. keyword2	keyword1 -keyword2
Questions with keyword(s) and a specific tag	keyword1 [tag1]
Questions with keyword(s) and either of two or more specific tags	keyword1 [tag1] [tag2]
To search for all posts by a user or all posts with a specific tag, start typing and choose from the suggestion list. Do not use a plus or minus sign with a tag, e.g., +[tag1].

Ask a question

Environment variables set in .bashrc no longer getting picked up after upgrade to 4.1.1.1 or 4.1.1.2?

Question by kathey (618) | Dec 23, 2016 at 07:19 PM streamsdev environment

Have you recently upgraded to 4.1.1.1 or 4.1.1.2 and found environment variables are no longer being picked up by your application? For example with the database toolkit, you get an error like

 An SQL operation failed. The SQL state is 08003, the SQL code
 is 0 and the SQL message is [unixODBC][Driver
 Manager]Connnection does not exist.

Environment variables set in .bashrc no longer getting picked up after upgrade to 4.1.1.1 or 4.1.1.2?

0 answers

Follow this question

Environment variables set in .bashrc no longer getting picked up after upgrade to 4.1.1.1 or 4.1.1.2?

0 answers

Follow this question

Related questions