Uploaded image for project: 'Network Controller'
  1. Network Controller
  2. SDNC-1811

Service Instantiation process error

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • Kohn Release
    • None
    • None

      Hello.
      I am trying to use ONAP Kohn for orchestrate physical network devices.
      I am using https://wiki.onap.org/display/DW/5G+-+PNF+PnP+-+Integration+Test+Cases like base guide for goal this.
      But at Service Instantiation step i am getting an error from SDNC:
      2023-05-29T11:56:25.343Z|680bfb6c-d110-4fc1-bab2-ea0ac4ea9935|org.onap.so.client.sdnc.SDNCClient - {"output":{"svc-request-id":"436a3661-72e4-422e-b7d4-fcd08b1523ad","response-message":"Error reading the table","ack-final-indicator":"Y"
      2023-05-29T11:56:25.343Z|680bfb6c-d110-4fc1-bab2-ea0ac4ea9935|org.onap.so.client.sdnc.SDNCClient - ResponseCode: 500 ResponseMessage: Error reading the table
      2023-05-29T11:56:25.344Z|680bfb6c-d110-4fc1-bab2-ea0ac4ea9935|org.onap.so.client.sdnc.SDNCClient - RA_RESPONSE_FROM_SDNC Error from SDNC: Error reading the table BPMN 300 Error from SDNC: Error reading the table
      2023-05-29T11:56:25.344Z|680bfb6c-d110-4fc1-bab2-ea0ac4ea9935|o.o.s.b.infrastructure.sdnc.tasks.SDNCRequestTasks - Did not receive a successful response from SDNC.
      org.onap.so.client.exception.BadResponseException: Error from SDNC: Error reading the table

      SDNC Logs:
      <sdnctldb01> Failed to execute: SELECT * from GENERIC_RESOURCE_NAME WHERE type = 'SERVICE_INSTANCE' AND name = 'Dummy_SVC_Dummy_PNF_Instance' with no arguments.
      java.sql.SQLSyntaxErrorException: (conn=937396) Table 'sdnctl.generic_resource_name' doesn't exist

      Could anybody help me understand and resolve this issue please?
      In which phase table generic_resource_name should be created?

            djtimoney Dan Timoney
            rbedretdinov rbedretdinov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: