We have recently upgraded Sonar to 5.3 version. Sonar has collation requirement (Latin1_General_CS_AS). Collation on our existing DB is - Latin1_General_CI_AS
Followed below steps:
1. Got a new DB with new collation.
2. Setup the Sonar instance on the new DB. This created the required tables.
3. Truncated data on the new DB(basically drop and recreated tables)
4. Did a SELECT INSERT to copy data from existing DB to new DB.
I am aware of Sonar DB copy tool but I believe this is only for Enterprise version. (http://docs.sonarqube.org/display/SONAR/Sonar+DB+Copy+Tool)
Sonar is up and running but we see the project links are broken. Is there a proper method to migrate data from old DB to new DB in Sonar?
I see below error in sonar log:
2016.07.07 14:59:29 ERROR web[o.s.s.ui.JRubyFacade] Fail to render: http://:42224/dashboard/index/20464
undefined method project' for nil:NilClass
<INSTALL PATH>/web/WEB-INF/app/controllers/dashboard_controller.rb:53:inindex'
DB collation is automatically fixed in version 5.6, so I recommend to upgrade to this version instead of 5.3. It will avoid potential corrupted data introduced with your copy operation (for instance are the IDs correctly copied) ?
I had OBIEE 11.1.1.6.4 installed on a windows 7 server. The app installation was corrupted and I had to re-install. Well, I re-installed OBIEE 11.1.1.6.12 (only install files I have). I want to use the same MDS and BIPLATFORM repositories as before, however; I do not have the schema passwords for the MDS and BIPLATFORM schemas. To get around this, I copied the database and gave new passwords.
When I attempt to hook the OBIEE 11.1.1.6.12 installation up to the copied database, OBIEE config says the BIPLATFORM and MDS schemas cannot be found. Does anyone know if this can be a version issue? The copied database was from a 11.1.1.6.4 install and the app is now 11.1.1.6.12. Is this the problem?
Any thoughts?
I found the answer and wanted to post it for others. There is a table in the repository called dbo.schema_version_registry$. If you change the schema prefix in the copied database (required if using the same DB), then you will need to manually edit this table to reflect the new prefix!
Took me days to track down but it's just a simple update against the table. Hope this helps someone.
I was trying to migrate from PostgreSQL data from PostgreSQL 9.0.0 to 9.3. I am having an issue related to the collation.
ERROR: could not determine which collation to use for string comparison
Hint: Use the COLLATE clause to set the collation explicitly.
I have done quite a research and found that it has an issue in pre-9.1 we have "citext" and in post-9.1 we have to add the extension. [if I understood correctly].
Here what I have done so far :
Taken the dump from 9.0.0 database.
Installed the instance 9.3.1 in another instance.
Created a database there and run the following query to add the extension CREATE EXTENSION citext. Till here I do not have problem.
While importing the dump from 9.0 after executing the query, I am getting a error, as extension "citext" already exists.
I am not sure if i have done the correct steps in resolving the problem. As per mu understanding, in post 9.1 postgres, we do not have "citext" extension so we manually adding the extension by running the query. So now why it is trying to add the "citext" extension "create citext;" to add citext.
Please correct me if i am leading in a wrong direction.
Thanks
Sovan
I have a server that is capable of creating and running an Excel Import task using the Import Wizard. I am trying to automate that process by using a visual Studio 2010 Integration Services package, that I am developing on that server.
The problem happens when trying to design the package. I have added an excel connection and pointed it at the Excel file on a local disk (the same file I have already successfully imported using the import wizard). When I add an Excel Source to the DataFlow and specify the excel connection, when I go to the Name Of the Excel Sheet Drop down I just see "No tables or views can be loaded" and get the following error.
"Could not retrieve the table information for the connection manager.
Failed to connect to the source using the connection manager ..."
I can't find this error logged anywhere and i don't know why it is failing. The directory is shared to Authenticated users and the file is not in use.
Any ideas how to debug this error? I understand there can be issues running this in 64 bit mode, but does that apply to development?
I should add that it is an excel 2007 file .XLSX and the connection is set to Excel 2007.
2019-11-08 The answer by GavB841 below looks promising, if anyone tries it and it works please let me know. (I am no longer working in this area.)
It seems like the 32-bit version of Excel was not installed. Remember
that SSDT is a 32-bit IDE. Therefore, when data is access from SSDT
the 32-bit data providers are used. When running the package outside
of SSDT it runs in 64-bit mode (not always, but mostly) and uses the
64-bit data providers.
Always keep in mind that if you want to run your package in 64-bit
(which you should aim for) you will need both the 32-bit data
providers (for development in SSDT) as well as the 64-bit data
providers (for executing the package in production).
I downloaded the 32-bit access drivers from:
Microsoft Access Database Engine 2010 Redistributable.
After installation, I could see the worksheets
Source:
Extracting Data From Excel with SSIS
The workaround is, I save the excel file as excel 97-2003 then it works fine
I also ran into this problem today, but found a different solution from using Excel 97-2003. According to Maderia, the problem is SSDT (SQL Server Data Tools) is a 32bit application and can only use 32bit providers; but you likely have the 64bit ACE OLE DB provider installed. You could play around with trying to install the 32bit provider, but you can't have both the 64 & 32 version installed at the same time. The solution Maderia suggested (and I found worked for me) was to set the DelayValidation = TRUE on the tasks where I'm importing/exporting the Excel 2007 file.
The recommendations from this article Extracting Data From Excel with SSIS resolved the issue for me.
I downloaded MS Access Database Engine 2010 32 bit driver
from the link in that article.
Also set Project Configuration Properties for Debugging Run64BitRuntime = False
In SQL Server 2014 SSMS (Integration Service Catalog -> SSISDB -> Environments -> Projects for all Packages in Validate checked box 32 bit Runtime.
My SSIS packages are working now in both VS 2013 and SQL Server 2014 environments.
Simple workaround is to open the file and simply press save button in Excel (no need to change the format). once saved in excel it will start to work and you should be able to see its sheets in the DFT.
You need to use an older version of the data connectivity driver (2007 Office System Driver: Data Connectivity Components) and select Excel version 2007-2010 in the connection manager configuration window.
I assume the newest data connectivity driver for Office 2016 is corrupt
Here's the solution that works fine for me.
I just Saved the Excel file as an Excel 97-2003 Version.
As discussed in the below:
Solution:
Go to https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftAnalysisServicesModelingProjects and install the latest version, it has a fix in there to resolve this issue.
Reference: https://developercommunity.visualstudio.com/content/problem/745991/could-not-load-file-or-assembly-microsoftdatawareh.html
A fix for this issue has been internally implemented and is being prepared for release. We’ll update you once it becomes available for download. For now, please install latest SSAS from https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftAnalysisServicesModelingProjects to work around the issue. Sorry for any inconvenience.
I faced the same issue. I think #Rishit answer helped me.
This issue is related to 32 bit/ 64 bit version of driver. I was trying to read .xlsx files to SQL Server tables using SSIS
My machine was pre-installed with Office 2016 64 bit on Win 10 machine along
with MS Access
I was able to read excel 97-2003 (.xls) files using ssis, but unable
to connect .xlsx files
My requirement was to read .xlsx files
Installed AccessDatabaseEngine_X64 to read xlsx, that given me
the following error:
I uninstalled the AccessDatabaseEngine_X64 and installed
AccessDatabaseEngine 32 bit, that resolved the issue
My answer is very similar to the one from #biscoop, but I am going to elaborate a bit as it may apply to the question or to other people.
I had a .xls that was an extraction from one of our webapps. The Excel connection would not work (error message: "no tables or views could be loaded"). As a side note, when opening the file, there would be a warning stating that the file was from an online source and that the content needed activation.
I tried to save the same file as an .xlsx and it worked.
I tried to save the same file with another name as an .xls and it worked too.
So as a last test I only opened the source .xls file, clicking save and the connection worked.
Short answer: just try and see if opening the file and saving does the trick.
Solution
Actually, if you are using SSIS in VS2019 then a problem could occur so do the below things:
Go to the excel sheet and save it again in .xls format.
Once you will use it in .xls format, automatically type will be coming as Microsoft Excel 97-2003 worksheet.
Like in the attached picture.
You will be able to load your sheet data.
I found that my excel file that was created in Excel 365 was incompatible with any of the versions available. I re-saved the excel file in 97-2003 version and of course chose that version in the dropdown list and it read the file OK.
you can try this:
Uninstall office365
then install only Access Database Engine 2016 Redistributable 64 bit
Also set Project Configuration Properties for Debugging Run64BitRuntime = False
It should work.
After researching everywhere finally i have found out temporary solution. Because i have try all the solution installing access drivers but still i am facing same issues.
For excel source,
Before this step you need to change the setting. Save excel file as 2010 format.xlsx
Also set Project Configuration Properties for Debugging Run64BitRuntime = False
Drag and drop the excel source
Double click on the excel source and connect excel. Any way you will get an same error no table or view cannot load....
Click ok
Right click on excel source, click on show advanced edit.
In that click on component properties.
You can see openrowset. In that right side you need to enter you excel sheet name example: if in excel sheet1 then you need to enter sheet1$. I.e end with dollar symbol. And click ok.
Now you can do other works connecting to destination.
I am using visual studio 2017, sql server 2017, office 2016, and Microsoft access database 2010 engine 32bit. Os windows 10 64 bit.
This is temporary solution. Because many peoples are searching for this type of question. Finally I figured out and this solution is not available in any of the website.
I'm planning on distributing postgresql with my windows application but the size of postgresql is too big, what are some of the file that can be removed from the package to reduce the size of the postgresql server?
I think you can safely remove the following directories:
include
doc
installer
pgAdmin III
scripts
StackBuilder
symbols (not 100% sure about this, but I think they are only needed for debugging)
(Based on the layout after a typical install)
You can also delete
bin\stackbuilder.exe
bin\pgAdmin3.exe