Error during Enabling Monetization for an Organization

Hi,

I am running Apigee Private Cloud OPDK version 4.19.01 and while enabling monetization service for an organisation, i encounter the below error

Details are below:

[root@ip-xx.xx.xx.xx ~]# curl -H "Content-Type:application/json" -X POST -d \

> '{

> "orgName" : "<Org-Name>",

> "mxGroup" : "mxgroup001",

> "pgHostName" : "<PG-IP>",

> "pgPort" : "5432",

> "pgUserName" : "apigee",

> "pgPassword" : "postgres",

> "adminEmail" : "<username>",

> "notifyTo" : "<username>",

> "taxEngineExternalId" : ""

> }' \

> "http://xx.xx.xx.xx:<port>/v1/mint/asyncjobs/enablemonetization" -u <username>:<password> -vv

* About to connect() to xx.xx.xx.xx port <port> (#0)

* Trying xx.xx.xx.xx...

* Connected to xx.xx.xx.xx (xx.xx.xx.xx) port <port> (#0)

* Server auth using Basic with user '<username>'

> POST /v1/mint/asyncjobs/enablemonetization HTTP/1.1

> Authorization: Basic <Token>

> User-Agent: curl/7.29.0

> Host: xx.xx.xx.xx:<port>

> Accept: */*

> Content-Type:application/json

> Content-Length: 303

>

* upload completely sent off: 303 out of 303 bytes

< HTTP/1.1 200 OK

< Date: Mon, 22 Apr 2019 16:39:14 GMT

< Content-Type: application/json

< X-Apigee.user: <username>

< X-Apigee.organization: null

< Date: Mon, 22 Apr 2019 16:39:14 GMT

< Content-Length: 142

<

{

"id" : "ce5b364e-0369-48a6-a599-62d1a4eca6f0",

"log" : "",

"orgId" : "<Org-Name>",

"status" : "RUNNING",

"type" : "ENABLE_MINT"

* Connection #0 to host xx.xx.xx.xx left intact

and

[root@ip-xx.xx.xx.xx ~]# curl -X GET "http://xx.xx.xx.xx:<port>/v1/mint/asyncjobs/ce5b364e-0369-48a6-a599-62d1a4eca6f0" -u <username>:<password>

{

"id" : "ce5b364e-0369-48a6-a599-62d1a4eca6f0",

"log" : "ERROR: relation \"organization\" does not exist\n Position: 622 {prepstmnt 1463982336 \nSELECT t0.CREATED, t0.CREATED_BY, t0.UPDATED, t0.UPDATED_BY, \n t0.APPROVE_TRUSTED, t0.APPROVE_UNTRUSTED, \n t0.BILLING_CYCLE_TYPE, t0.COUNTRY, t0.CURRENCY, t0.DESCRIPTION, \n t0.HAS_BILLING_ADJUSTMENT, t0.HAS_BROKER, t0.HAS_SELF_BILLING, \n t0.HAS_SEPARATE_INV_FOR_PROD, t0.ISSUE_NETTING_STMT, \n t0.LOGO_URL, t0.NAME, t0.NET_PAYMENT_ADVICE_NOTE, \n t0.NETTING_STMT_PER_CURRENCY, t0.ORG_TYPE, t0.REG_NO, \n t0.HAS_SELF_BILLING_AS_EXCH_ORG, t0.SELF_BILLING_FOR_ALL_DEV, \n t0.IS_SEPARATE_INV_FOR_FEES, t0.STATUS, \n t0.SUPPORTED_BILLING_TYPE, t0.TAX_ENGINE_EXTERNAL_ID, \n t0.TAX_MODEL, t0.TAX_NEXUS, t0.TAX_REG_NO, t0.TIMEZONE, \n t0.TXN_RELAY_URL \n FROM ORGANIZATION t0 \n WHERE t0.ID = ? \n} [code=0, state=42P01]",

"orgId" : "<Org-Name>",

"status" : "FAILED",

"type" : "ENABLE_MINT"

But when i executed below command

[root@ip-xx-xx-xx-xx ~]# curl -v 'http://xx.xx.xx.xx:<port>/v1/organizations/<Org-name>' -u <username>:<password>

* About to connect() to xx.xx.xx.xx port <port> (#0)

* Trying xx.xx.xx.xx...

* Connected to xx.xx.xx.xx (xx.xx.xx.xx) port <port> (#0)

* Server auth using Basic with user '<email-id>'

> GET /v1/organizations/<Org-Name> HTTP/1.1

> Authorization: Basic aW5mcmEtZW5naW5lZXJpbmdAc2lkZ3MuY29tOkNsb3ZlcjEyMyE=

> User-Agent: curl/7.29.0

> Host: xx.xx.xx.xx:<port>

> Accept: */*

>

< HTTP/1.1 200 OK

< Date: Thu, 18 Apr 2019 22:18:58 GMT

< Content-Type: application/json

< X-Apigee.user: <email-id>

< X-Apigee.organization: <Org-Name>

< Date: Thu, 18 Apr 2019 22:18:58 GMT

< Vary: Accept-Encoding, User-Agent

< Content-Length: 523

<

{

"createdAt" : 1555532328633,

"createdBy" : "<email-id>",

"displayName" : "<Org-Name>",

"environments" : [ "dev-monit" ],

"lastModifiedAt" : 1555623043831,

"lastModifiedBy" : "<email-id>",

"mdc" : {

"first" : "org",

"left" : "org",

"right" : "<Org-Name>",

"second" : "<Org-Name>"

},

"name" : "<Org-Name>",

"properties" : {

"property" : [ {

"name" : "features.isMonetizationEnabled",

"value" : "true"

} ]

},

"type" : "paid"

* Connection #0 to host xx.xx.xx.xx left intact

and the management server log? Search for "26d33800-0b79-40c9-b32c-b8e1daa0b2b3"

in the system logs

0 2 248
2 REPLIES 2

I have the same problem, How do you fix?

@hariprasadar  Have you resolved the issue? Could you share how? I have a similar issue with OPDK 4.50.0