I am trying to execute a workflow mapping from within Informatica Workflow. The source being MSSQL Server and target Oracle DB. The mapping alike every other mapping seems to be referring to the system's /etc/odbc.ini file rather than the one sitting in $INFA_HOME/ODBC7.1/odbc.ini.
I've tried checking everything but can't seem to understand how this linking is getting established. I did many hit & trials to confirm which odbc.ini was getting referred and it was always the one sitting under /etc/. The bash_profile's variable ODBCINI is also pointing towards the INFA_HOME location.
Can someone shed some light on how or why the system's odbc.ini is getting referred. Any idea on how is it linked?
We need to set two odbc related parameters in unix/linux users bash profile.
INFA_HOME=/opt/infa
ODBCINI= $INFA_HOME/ODBC7.1/odbc.ini
ODBCINST=$INFA_HOME/ODBC7.1/odbcinst.ini
Now, i feel like, your unix/linux user is not able to reach this location or they arent getting exported properly.
Login using the unix/linux user thats running informatica.
Then use more $ODBCINI to see if it has read permission.
Do same for ODBCINST.
Use ssgodbc tool to check connectivity to your mssql server DB.
I tried almost all the articles there is on this error. But in my case the services aren't installed. So i can't change them. I had 10g installed before but i needed to use Oracle for python too so I removed that. And also i did reset my pc(keep my files) after that. But now i have tried multiple times to install Oracle 18c but not working.
I.e modifying listener and sqlplus sys/mypassword as sysdba or many more.
These are the screenshots.
This is very frustrating. Any suggestions? Also What is the alternative for homepage of 10g in 18c.
I also tried running setup.exe from zip folder directly. But no luck.
Your screen shots clearly show that the services are indeed installed, your assertion otherwise notwithstanding. You even have sqlplus waiting to do your bidding. But you invoke it incorrectly.
The protocol error (ora-12560) occurs when 1) you do not specify a connect string when you invoke sqlplus thus causing it to try to connect to a local database specified by the environment variable ORACLE_SID, and 2) the environment ORACLE_SID does not specify an actual local database.
Unfortunately, your screen shot does not show how you invoked sqlplus, thus losing important diagnostic info. Far better to start cmd.exe, invoke sqlplus, then copy the entire text and paste that into your question, with formatting. I leave it as an exercise for the student to research how to do those elementary tasks.
I have installed oracle 11g, but got this error: "ORA-12705: Cannot access NLS data files or invalid environment specified" while I was trying to connect to it from eclipse. I googled alot and finally changed my nls language and territory settings + my windows language and territory settings (from Russian to English(American)). But that didnt solve the problem, so I decided to reinstall the oracle 11g. And got myself a step back in solving the problem by generating another error even before the first error. I tried to manualy set the environmental variable ORACLE_HOME, didnt help. Also I tried to login to the sqlplus as "sysdba" and then to launch the "startup" command. This brought me an error that my "spfilexe.ora" is missing, so maybe that could be the problem. And I have started the oracle database before. I would appreciate any suggestions on how to solve this problem.
After installing SP2 to an existing SQL Server 2008 R2 I lost access to all my databases and started facing the error in the screenshot.
Any ideas?
Check the environment value for Temp and TMP.
C:\Users\buck>set t
TEMP=C:\Users\buck\AppData\Local\Temp\2
TMP=C:\Users\buck\AppData\Local\Temp\2
Make sure the directory listed exist and your id has appropriate permission to write to that directory. Alternatively, through the control panel (Control Panel-> System and Security-> System -> Advanced system settings), you can change the default directories that are assigned to TEMP and TMP.
When I've seen this issue, it is usually because the Drive that SSMS is installed on has run out of free space. Deleting some old Log files clears the issue up.
Doing that quick check might be worthwhile before going forward with a re-install.
I got this error on our remote shared server. Turned out that our C drive did not have any space left.
I got it working by asking my colleague to close his SQL Server Management Studio session and it cleared up 7 GB right away! I could login then! Woot woot!
Right click on the SSMS icon and click 'run as administrator'. At the SSMS console verify that the error is gone by clicking on the 'Databases' tree node. The error should now be permanently fixed and you do not need to run SSMS as admin anymore. Next time just start SSMS normally and it should work fine.
Changing the temp variables did not resolve. Drive with SMMS installed has 34% free space.
However, using Run > %temp% > it would error out as "C:\%username%\appdata\local\temp\4 was missing" (this is not listed in my TEMP/TMP variables).
Quick solution was to add sub folder for "4" in c:\%username%\appdata\local\temp\ and now able to open SMMS without issue.
When running into this I found it was related to the environment temp folder (TMP Temp).
I had tried adding the "2" folder to this location with no success.
C:\Users\USER\AppData\Local\Temp\2
Try typing %temp% in file explorer and see if it takes you to a valid location. I found that I received an error because it was trying to go to a "4" location.
C:\Users\USER\AppData\Local\Temp\4
I created a folder named "4" in the Temp folder, reran SSMS, and it started working again.
A quick google suggest that apparently it is a bit common issue. It looks like that it is not an issue of SQL Server itself but actually .NET issue And most common (and quick) solution I found is to reinstall SSMS.
I've found that if you are upgrading an iseries odbc driver on a sql cluster. Lots of times you will run into this issue exactly. Renaming the machine.config in both the 32 bit and 64 bit folders does the trick. we currently upgraded from version 12 or 6.1 to 7.1 or 13 as the version 12 was causing a bug check on one of our SQL instances. Upgraded, and the issues all went away.
Cheers,
According to the following link:
https://connect.microsoft.com/SQLServer/feedback/details/573771/value-cannot-be-null
I just checked that my user is local admin, then i logged off and logged back in.
After that step i haven't received this error again.
I was receiving this exact error and thought I'd have a go at running the repair.
Well the repair didn't resolve the issue however it did tell me that it was unable to access machine.config in C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG - found it didn't exist! There was another file machine.config.default
So had a stab at copying, renaming to .config and viola resolved it and everything working like a champion.
I got the same error in SSMS and I found this link and followed the steps as it mentioned.
The problem appeared to be when accessing the contents of a settings file. The file had invalid entries. This file is CurrentSettings-. The fix for this is as shown below:
On the server Go to start menu–>Your profile–>Documents–>SQL Server Management Studio–>Settings (this is the location of the file specified above)
Delete all files from this folder
Restart sqlserver services
Launch the SSMS and this error is gone. You will be able to expand all the folders and perform regular SSMS activities without this error.
Once I performed these steps and restarted my PC this error was gone and SSMS worked fine.
I just faced this issue and resolved it immediately in 5 mins. Just go to Control Panel and Run Troubleshooting tool on Programs.
**PATH** Control Panel\All Control Panel Items\Troubleshooting\Programs
It will give you the list of installed programs which may have any issue. Scroll down that list and find 'SQL Server Management Studio' and run troubleshooting process on that. It will hopefully fix you issue.
I gets this messages many times and every time it is resolved by different solutions below few of it.
Solution: Clear cache from temp folder, Press windows + R => type "%temp%" => Delete all the files from temp folder... And try weather it works and opens ssms successfully
Solution: create folder named "2" in this above mentioned temp folder location... And try weather it works and opens ssms successfully.
Solution:create folder named "4" in this above mentioned temp folder location... And try weather it works and opens ssms successfully.
Solution: It may cause because of low disk space in drive ssms is installed... so free some space...And try weather it works and opens ssms successfully.
Solution: Format is the last solution...
I've been trying to figure how postgresql works for the last couple of days. There's something I don't get. Is there a way to see the data inside the tables graphically? Something similar to MySQL's phpMyadmin? Or can I only see the data by querying it?
Try pgadmin3. http://www.pgadmin.org/
If you are using a package manager on your machine like MacPorts, you can also download it using sudo port install pgadmin3.
Here are some example screenshots which will guide you to find where you can select "View Data".
Make sure your are connected to your postgresql server and the specific database you are interested in.
Then click into its hierarchy to open up public, which will contain another group named Tables, like this:-
There is a free program called pgAdmin that you can download from pgadmin.org.