Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] SQL problem

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] SQL problem


Chronological Thread 
  • From: "Gettes, Michael" <>
  • To: Shilen Patel <>
  • Cc: grouper-users <>
  • Subject: Re: [grouper-users] SQL problem
  • Date: Fri, 13 Jul 2018 21:53:09 +0000
  • Accept-language: en-US
  • Ironport-phdr: 9a23:tJe7eRL+qB8QT8zZYdmcpTZWNBhigK39O0sv0rFitYgeI/jxwZ3uMQTl6Ol3ixeRBMOHs6wC07KempujcFRI2YyGvnEGfc4EfD4+ouJSoTYdBtWYA1bwNv/gYn9yNs1DUFh44yPzahANS47xaFLIv3K98yMZFAnhOgppPOT1HZPZg9iq2+yo9JDffwRFiCChbb9uMR67sRjfus4KjIV4N60/0AHJonxGe+RXwWNnO1eelAvi68mz4ZBu7T1et+ou+MBcX6r6eb84TaFDAzQ9L281/szrugLdQgaJ+3ART38ZkhtMAwjC8RH6QpL8uTb0u+ZhxCWXO9D9QKsqUjq+8ahkVB7oiD8GNzEn9mHXltdwh79frB64uhBz35LYbISTOfFjfK3SYMkaSHJBUMhPSiJBHo2yYYgBD+UDOuhYrpXyqVQBohalGQmjH+bvxiNIhnPq36A31fkqHwHc3AwnGtIDqHrYotTrO6cOTeC60rLIwS3eZP1R2Dfy9IjIfQo/rvGIU757bM3cyUYxGAPZklWft5flMiiI1uQDt2iX9fRvWv+yi2M+rQx6vzahxsApiobTh4IVzEjJ9SpjwIYyON24UFB0YcS+HJRKryGaL5N6QsElQ25zoiY617sGuYW7fCcUzJQnwwTTa+aac4iO5B/oSeWfIS9giX54Zr6yhAy+/Va+xuD+TMW50llHojBYntXStn0BzwHf5tSdRvZz/0qtwyuD2g7c5+1ePEw4iLLXK5A/zbMzipYetEHOEyzylUnqkKCbc1kr9fOy5OnnZ7jquJ2ROJRqhgz7L6shgdKzDOY+PwMTRWaU4/6826fm/UDhQLVFkPk2kq7BvZDBIMQbura5DxVI0oYt7xazFSmp38kFnXUfLVJFfgyIj5TxNl3TPvz1Du2zj0qynDpp3fzLPLLsDo/QInTdkLrtZbN95FRdyAo3w9Bf/ZVUCrQZLfL8REDxqMDYAQEiMwGv3ubnBtF92pkAVm2SH6+VKLnSvkOQ5uIzP+mMY5cYuDnnK/gi+v7ulWE2mUUEcam0xpsYdmq4Hu99LkWdYHrsmcsBEXwUsgYkTezqjkGCXiBJZ3a0Qa08+i83BJi4AojeW4D+yICGiRy7H5lbYCh+A0yBFT+8bIWFX/oKQC6PIcInnzAZA+uPUYgkgFuBuRPmxqEjZs/V8S0RuJapnIx66vHPmAoa6DJwScmRzjfeHClPgmoUSmpuj+hEqktnxwLGiPAgjg==

It’s not just testing and proof of concept work. Trigger based in the same
DB is tightly coupled data relationships and I intend to do what I can
message based allowing for loosely coupled data relationships. Messaging
should be fast so the delays should only be a few milliseconds to seconds.
And thank YOU for the consideration and your continued great work!

Have a wonderful weekend!

/mrg

> On Jul 13, 2018, at 5:27 PM, Shilen Patel
> <>
> wrote:
>
> OK I see. I think it’s that way because the assumption is that you would
> put triggers on your loader tables to populate the incremental table, so
> the same database would generally be used. But I could see that this makes
> it harder to do testing and proof of concept work. We’re planning on
> making a series of updates to the real time loader after 2.4 is released so
> I appreciate the feedback.
>
> Thanks!
>
> - Shilen
>
> On 7/13/18, 4:48 PM,
> "
> on behalf of Gettes, Michael"
> <
> on behalf of
> >
> wrote:
>
> Never mind - I think I get it now. I am using the incremental table in
> a mySQL (MariaDB) database but the loader job ultimately being executed
> goes against Oracle. So, I guess I can’t use the incremental loader until
> I can get appropriate Oracle access. Bummer. Would have been nice if the
> instantiation of the loaderjob was separate from the incremental job but I
> think I get there must be some reason one has to use the existing context.
>
> Sniffle, sniffle.
>
> /mrg
>
>> On Jul 13, 2018, at 4:37 PM, Gettes, Michael
>> <>
>> wrote:
>>
>> I am trying to continue down the path of making use of the realtime loader
>> and I am having a SQL error. I have turned up logging to DEBUG on
>> edu.internet2.middleware.grouper.app.loader but I am not getting any
>> useful output other than what is below. How can I better see the actual
>> statement creating the error? I get the impression my loaderJob SQL is
>> being wrapped by something else and that’s failing but I can’t see what is
>> actually failing.
>>
>> Pointers appreciated.
>>
>> /mrg
>>
>> daemon_1 | 2018-07-13T20:34:30.176376217Z
>> grouper-api;grouper_error.log;dev;build-2;2018-07-13 16:34:30,175:
>> [DefaultQuartzScheduler_Worker-7] ERROR
>> GrouperLoaderIncrementalJob.runJob(336) - - Error running job
>> daemon_1 | 2018-07-13T20:34:30.176434695Z java.lang.RuntimeException:
>> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an
>> error in your SQL syntax; check the manual that corresponds to your
>> MariaDB server version for the right syntax to use near '@SHIBPRD_pub p,
>> Role_List RL where p.ARP_PAR_UFID = r.ROLEUSER and r.rolename=RL' at line
>> 1,
>> daemon_1 | 2018-07-13T20:34:30.176444634Z 1 callables out of problem
>> count 1 had problems running outside of threads!
>> daemon_1 | 2018-07-13T20:34:30.176450505Z at
>> edu.internet2.middleware.grouper.app.loader.GrouperLoaderIncrementalJob.processOneRow(GrouperLoaderIncrementalJob.java:720)
>> daemon_1 | 2018-07-13T20:34:30.176455791Z at
>> edu.internet2.middleware.grouper.app.loader.GrouperLoaderIncrementalJob.access$000(GrouperLoaderIncrementalJob.java:73)
>> daemon_1 | 2018-07-13T20:34:30.176460452Z at
>> edu.internet2.middleware.grouper.app.loader.GrouperLoaderIncrementalJob$1.callLogic(GrouperLoaderIncrementalJob.java:286)
>> daemon_1 | 2018-07-13T20:34:30.176464931Z at
>> edu.internet2.middleware.grouper.app.loader.GrouperLoaderIncrementalJob$1.callLogic(GrouperLoaderIncrementalJob.java:281)
>> daemon_1 | 2018-07-13T20:34:30.176469333Z at
>> edu.internet2.middleware.grouper.util.GrouperCallable.tryCallablesWithProblems(GrouperCallable.java:51)
>> daemon_1 | 2018-07-13T20:34:30.176473956Z at
>> edu.internet2.middleware.grouper.app.loader.GrouperLoaderIncrementalJob.runJob(GrouperLoaderIncrementalJob.java:308)
>> daemon_1 | 2018-07-13T20:34:30.176478163Z at
>> edu.internet2.middleware.grouper.app.loader.GrouperLoaderIncrementalJob.execute(GrouperLoaderIncrementalJob.java:94)
>> daemon_1 | 2018-07-13T20:34:30.176483959Z at
>> org.quartz.core.JobRunShell.run(JobRunShell.java:202)
>> daemon_1 | 2018-07-13T20:34:30.176488543Z at
>> org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)
>> daemon_1 | 2018-07-13T20:34:30.176493674Z Caused by:
>> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: You have an
>> error in your SQL syntax; check the manual that corresponds to your
>> MariaDB server version for the right syntax to use near '@SHIBPRD_pub p,
>> Role_List RL where p.ARP_PAR_UFID = r.ROLEUSER and r.rolename=RL' at line 1
>> daemon_1 | 2018-07-13T20:34:30.176499131Z at
>> sun.reflect.GeneratedConstructorAccessor99.newInstance(Unknown Source)
>> daemon_1 | 2018-07-13T20:34:30.176503352Z at
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>> daemon_1 | 2018-07-13T20:34:30.176509368Z at
>> java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>> daemon_1 | 2018-07-13T20:34:30.176514977Z at
>> com.mysql.jdbc.Util.handleNewInstance(Util.java:404)
>> daemon_1 | 2018-07-13T20:34:30.176519375Z at
>> com.mysql.jdbc.Util.getInstance(Util.java:387)
>> daemon_1 | 2018-07-13T20:34:30.176540322Z at
>> com.mysql.jdbc.SQLError.createSQLException(SQLError.java:939)
>> daemon_1 | 2018-07-13T20:34:30.176545670Z at
>> com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3878)
>> daemon_1 | 2018-07-13T20:34:30.176550501Z at
>> com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3814)
>> daemon_1 | 2018-07-13T20:34:30.176555287Z at
>> com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2478)
>> daemon_1 | 2018-07-13T20:34:30.176560002Z at
>> com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2625)
>> daemon_1 | 2018-07-13T20:34:30.176565012Z at
>> com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2551)
>> daemon_1 | 2018-07-13T20:34:30.176570002Z at
>> com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1861)
>> daemon_1 | 2018-07-13T20:34:30.176575144Z at
>> com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1962)
>> daemon_1 | 2018-07-13T20:34:30.176579983Z at
>> com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeQuery(NewProxyPreparedStatement.java:353)
>> daemon_1 | 2018-07-13T20:34:30.176585062Z at
>> edu.internet2.middleware.grouper.app.loader.GrouperLoaderIncrementalJob.processOneRow(GrouperLoaderIncrementalJob.java:601)
>> daemon_1 | 2018-07-13T20:34:30.176590460Z ... 8 more
>>
>
>
>




Archive powered by MHonArc 2.6.19.

Top of Page