On Wed, Dec 21, 2011 at 02:38:54PM -0500, Eric Lake wrote:
> On Wed, Dec 21, 2011 at 2:26 PM, Jan Pazdziora wrote:
> > Is it possible that taskomatic was (still) running while you were
> > doing the dump? We process the sequences first, so it's possible
> > that we saw the value 1329890 in the seq
On Wed, Dec 21, 2011 at 2:26 PM, Jan Pazdziora wrote:
> Is it possible that taskomatic was (still) running while you were
> doing the dump? We process the sequences first, so it's possible
> that we saw the value 1329890 in the sequence, but before the
> script got to dump the actual table data, t
On Wed, Dec 21, 2011 at 02:20:16PM -0500, Eric Lake wrote:
> On Wed, Dec 21, 2011 at 1:46 PM, Jan Pazdziora wrote:
> > If you still have the schema dump that you used to migrate from Oracle,
> > could you check whether it contains a line which would look like
> >
> > select pg_catalog.setva
On Wed, Dec 21, 2011 at 1:46 PM, Jan Pazdziora wrote:
> If you still have the schema dump that you used to migrate from Oracle,
> could you check whether it contains a line which would look like
>
> select pg_catalog.setval('rhn_tasko_template_id_seq', 1330170, false);
>
> ? Because the seq
On Wed, Dec 21, 2011 at 10:58:40AM -0500, Eric Lake wrote:
> On Wed, Dec 21, 2011 at 9:00 AM, Eric Lake wrote:
> > SQL> select * from user_sequences where sequence_name =
> > upper('rhn_tasko_template_id_seq') ;
> >
> > SEQUENCE_NAME MIN_VALUE MAX_VALUE INCREMENT_BY C O
> > CAC
On Wed, Dec 21, 2011 at 9:00 AM, Eric Lake wrote:
> SQL> select * from user_sequences where sequence_name =
> upper('rhn_tasko_template_id_seq') ;
>
> SEQUENCE_NAME MIN_VALUE MAX_VALUE INCREMENT_BY C O
> CACHE_SIZE
> -- -- --
On Wed, Dec 21, 2011 at 8:43 AM, Jan Pazdziora wrote:
> select * from user_sequences where sequence_name =
> upper('rhn_tasko_run_id_seq') ;
> select * from user_sequences where sequence_name =
> upper('rhn_tasko_template_id_seq') ;
Thanks Jan.
SQL> select * from user_sequences where sequence_
On Wed, Dec 21, 2011 at 08:09:03AM -0500, Eric Lake wrote:
> On Wed, Dec 21, 2011 at 5:57 AM, Tomas Lestach wrote:
> > Looking at the code we've used RHN_TASKO_TEMPLATE_ID_SEQ sequence (not the
> > RHN_TASKO_RUN_ID_SEQ) for the rhnTaskoRun table.
> >
> > Would you please check, what's the sequence
On Wed, Dec 21, 2011 at 5:57 AM, Tomas Lestach wrote:
> Looking at the code we've used RHN_TASKO_TEMPLATE_ID_SEQ sequence (not the
> RHN_TASKO_RUN_ID_SEQ) for the rhnTaskoRun table.
>
> Would you please check, what's the sequence number of the
> RHN_TASKO_TEMPLATE_ID_SEQ in your DB dump generated
Hi Eric,
Am 20.12.2011 20:20, schrieb Eric Lake:
Around 2 months ago we moved from an oracle-xe backend to postgresql
because we were hitting the 4GB limit that oracle-xe has. The
migration seemed to go fine but just recently we noticed that
taskomatic was not running.
I don't know how to fix
On Tuesday 20 of December 2011 14:20:25 Eric Lake wrote:
> Around 2 months ago we moved from an oracle-xe backend to postgresql
> because we were hitting the 4GB limit that oracle-xe has. The
> migration seemed to go fine but just recently we noticed that
> taskomatic was not running. It seems to b
Around 2 months ago we moved from an oracle-xe backend to postgresql
because we were hitting the 4GB limit that oracle-xe has. The
migration seemed to go fine but just recently we noticed that
taskomatic was not running. It seems to be an issue in the database
where taskomatic is trying to update t
12 matches
Mail list logo
