Latest posts for the topic "java.sql.SQLException"

java.sql.SQLException

JimHobgood — GMT

Hi,
I've downloaded the trial and when I try and connect to my local SQL server database I get this is error message.

Couldn't Determine the repository schema version!
please check the repository settings of create the ...

any help would be appreciated.

Thanks,
Jim

Re:java.sql.SQLException

Jeff — GMT

Hello,

We'll need some more information.

1) What version of Power*MatchMaker are you using?

2) Is this the first time you're using Power*MatchMaker?

The Power*MatchMaker stores match results and other data in a database designated as the 'Repository'. By default, as of version 0.9.1, this is done in an embedded HSQLDB instance included with the application. However, you can optionally create a 'Repository' in a separate database, so if you're connecting to another database, then it will be expecting to 'Repository Schema' to be created in there.

Fortunately, you can create this from the Power*MatchMaker. You can check Ch. 4 pg. 21 of the User's Guide to get an idea of how to create a Repository. However, the documentation is awfully wordy and requires some work, so I'll try to summarize the steps you need here.

1) You need to log into the 'MatchMaker Default Repository' first. (If it is missing from your list of repositories, then let me know, as this will have to involve another process to get it back in there)

2) Once you've logged in, go to the Database menu and click 'Create Repository...'. From there, you can select the database and the catalog and/or schema (depending on your platform) you wish to create the repository in.

3) Click 'Create'. A dialog should pop up with the necessary DDL SQL statements to create the schema. Click 'Execute' to run the SQL script, and your repository should be created.

4) Once that's done, go to the Database menu again and click 'Connect to Remote Repository'. You'll get the login screen. Select the database where you created the repository to log in.

That should be it. Let me know if you run into any problems.

Re:java.sql.SQLException

JimHobgood — GMT

Jeff,

Thanks for the quick reply. The version is 0.9.2

yes it is the first time using Power Match Maker

1) It does seem that I can login to the 'MatchMaker Default Repository'. there are no errors when I choose from the database menu.
Title bar says sa@MatchMaker Default Repository

2) Create New Repository - I then choose the connection to my local SQL server, then my a new DB created through SQL Management Studio and last the schema. Click create...

Window appears and I choose execute.

errors -
Invalid object name 'mm_schema_info'.
Invalid object name 'pl_group'.
Invalid object name 'pl_user'.
Invalid object name 'user_group'.

successful 48 of 52.

Is there anything else I can provide so you better know what my problem is?

Thanks,
Jim

Re:java.sql.SQLException

JimHobgood — GMT

Jeff,

I was able to copy the script and execute it in SSMS. Now when I try and connect to remote repository i get a login failed.

com.microsoft.sqlserver.jdbc.SQLSwerverException

Invalid object name 'pl_user'

com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'pl_user'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement$StatementExecutionRequest.executeStatement(Unknown Source)
at com.microsoft.sqlserver.jdbc.CancelableRequest.execute(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeRequest(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeQuery(Unknown Source)
at ca.sqlpower.sql.jdbcwrapper.StatementDecorator.executeQuery(StatementDecorator.java:105)
at org.apache.commons.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:164)
at ca.sqlpower.security.PLUser.find(PLUser.java:46
at ca.sqlpower.security.PLUser.findByPrimaryKeyDoNotUse(PLUser.java:32
at ca.sqlpower.security.PLSecurityManager.(PLSecurityManager.java:97)
at ca.sqlpower.matchmaker.dao.hibernate.MatchMakerHibernateSessionImpl.(Unknown Source)
at ca.sqlpower.matchmaker.dao.hibernate.MatchMakerHibernateSessionContext.createSession(Unknown Source)
at ca.sqlpower.matchmaker.swingui.SwingSessionContextImpl.createSession(Unknown Source)
at ca.sqlpower.matchmaker.swingui.LoginDialog$LoginAction.doStuff(Unknown Source)
at ca.sqlpower.swingui.SPSwingWorker.run(SPSwingWorker.java:73)
at java.lang.Thread.run(Unknown Source)

Thanks,
Jim

Re:java.sql.SQLException

Jonathan — GMT

Hi Jim,

If you could send us a screenshot of your SQL Server repository database connection, we'll let you know if it looks right. Go to Database->Manage Database Connections, then edit the connection you're attempting to use for the repository. Post the screenshot of that "connection properties" dialog.

Also, are you sure you want to use a remote repository at all? For most projects, it's fine to use the default repository. You can still do cleansing and de-duping on your SQL Server database while using the default repository; the biggest difference with the remote repository is that it's easier to share your MatchMaker work with other people. See chapter 4 of the user guide for details.

-Jonathan

Re:java.sql.SQLException

Everett — GMT

Hi Guys,

I am running into the same problem as Jim. I attempt to open Power MatchMaker and almost immediately I receive the following exception:

ca.sqlpower.matchmaker.dao.hibernate.RepositoryException: Requested repository owner "public" not found. Please create it and try again.

When I initially downloaded and installed Power MatchMaker, I was able to open and configure the tool just fine. After tinkering with the tool for a while, I decided I was going to set up my repository on my default SQL server. I changed the configuration from a local repository to a remote repository. After making these changes and exiting, the app starting throwing these exceptions.

I have un-installed Power MatchMaker and re-installed it several times, even cleaning the registry in the process. But... for some reason, even if I re-install the app, it throws the exception.

If anyone could offer advice or guidance with this issue I would greatly appreciate it.

Thanks,

Everett

Re:java.sql.SQLException

Jeff — GMT

Hi Everett,

Based on the error message, it looks like you configured the wrong schema owner for your database connection.

Go to the Database menu and then select 'Manage Database Connections...'.

The 'Database Connection Manager' dialog should show up. Select the connection that you're using to connect to your remote repository and click the 'Edit...' button.

In there you should see your connection settings. At the very bottom, there is a 'Repository Schema Owner' field. You seem to have this set to 'public'. I believe you'll need to set this to the owner of the database you're connecting to.

Try that and let us know what happens.

Re:java.sql.SQLException

Everett — GMT

Hi Jeff,

Thanks again for the quick reply. I agree that I likely configured the wrong schema owner. Unfortunately, once I am presented with the error message describe in my last past, the app does not continue to load. When I clear the error, the screen disappears and the app exits.

Is there any way to modify this setting outside of the Power MatchMaker application? Is there a config file or a registry setting that I can update to point to a different schema owner? If not, do you have any recommendations regarding completely uninstalling the application so that I may re-install the app with its production defaults.

Thanks again for your time,

Everett

Re:java.sql.SQLException

Jeff — GMT

Hi Everett,

Yes, there is a configuration file that you can edit to set the Repository Schema Owner. This is the pl.ini file. It should be located in your home directory, which I believe should be in your C:\Documents and Settings\ directory if you're working on Windows.

Open it up with any text editor. The first few sections of the pl.ini are your database type configurations, which you don't need to worry about here.

The next few sections, each marked with '[Database_#]' (where # is a number), are your database connection configurations. Find the connection for the SQL Server database you're connecting to. You can tell by the property 'Logical', which is just the name that you gave your connection in the MatchMaker. When you find your connection, look for a property called
'PL Schema Owner'. If it's not there, then just add it. Set that to the owner of the database you want to connect to.

So for example, your database connection entry would look something like:
[code][Databases_4]
Logical=My Database
Connection Type=SQL Server
JDBC URL=jdbc:sqlserver://hostname:1433
UID=foo
PWD=abc
ca.sqlpower.architect.etl.kettle.database=
ca.sqlpower.architect.etl.kettle.port=
ca.sqlpower.architect.etl.kettle.hostname=
ca.sqlpower.architect.etl.kettle.repoin=
ca.sqlpower.architect.etl.kettle.repos.password=
PL Schema Owner=dbo[/code]
Also, if you happen to be not on Windows, then make sure that when you save the pl.ini that you save it with [b]Windows-style line-endings[/b] (CRLF). This is very important because the MatchMaker will not work if the pl.ini is using UNIX or Mac style line endings. This is because the password obfuscation that we're using in the pl.ini sometimes converts characters into CR or LF characters used by UNIX and Mac for line endings. We hope to fix this when we convert the Power*MatchMaker and Power*Architect to use an XML-based configuration file format.

Hope this helps!

Re:java.sql.SQLException

Everett — GMT

Hi Jeff,

Thanks for your help! That did the trick. I am just starting to evaluate the application, but so far it is exceeding my expectations!

Everett