Bug #11925

SQL is generated improperly when tied to an Oracle DB

Added by Jeff Chapin 4 months ago. Updated 4 months ago.

Status:Investigating Start date:01/12/2012
Priority:Normal Due date:
Assignee:Avi Miller % Done:

0%
Category:stored configuration
Target version:-
Affected Puppet version:2.6.12 Branch:
Keywords:SQL Oracle Stored_Configuration
Votes: 0

Description

I have tied a puppetmaster to an Oracle database, and I am attempting to use stored configs.

When running puppet —test for the first time after configuring this, I get the following error:

err: Could not retrieve catalog from remote server: Error 400 on SERVER: OCIError: ORA-00907: missing right parenthesis: CREATE TABLE “RESOURCES” (“ID” NUMBER(38) NOT NULL PRIMARY KEY, “TITLE” CLOB NOT NULL, “RESTYPE” VARCHAR2(255) NOT NULL, “HOST_ID” NUMBER(38), “SOURCE_FILE_ID” NUMBER(38)(38), “EXPORTED” NUMBER(1), “LINE” NUMBER(38)(38)(38), “UPDATED_AT” DATE, “CREATED_AT” DATE)

note the extra (38) following the type declarations

If I run puppet —test a second time, I get:

err: Could not retrieve catalog from remote server: Error 400 on SERVER: OCIError: ORA-00907: missing right parenthesis: CREATE TABLE “RESOURCES” (“ID” NUMBER(38) NOT NULL PRIMARY KEY, “TITLE” CLOB NOT NULL, “RESTYPE” VARCHAR2(255)(255)(255) NOT NULL, “HOST_ID” NUMBER(38)(38)(38)(38)(38)(38)(38), “SOURCE_FILE_ID” NUMBER(38)(38)(38)(38)(38)(38)(38)(38), “EXPORTED” NUMBER(1)(1)(1), “LINE” NUMBER(38)(38)(38)(38)(38)(38)(38)(38)(38), “UPDATED_AT” DATE, “CREATED_AT” DATE) warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run

note the parenthesis are breeding

History

#1
Updated by James Turnbull 4 months ago

  • Category set to stored configuration
  • Status changed from Unreviewed to Investigating
  • Assignee set to Avi Miller

Avi – any views on this?

#2
Updated by Avi Miller 4 months ago

None. I’ll take a look to see if I can reproduce this either at or after linux.conf.au next week.

Also available in: Atom PDF