Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 8.7
    • Fix Version/s: 9.1, 9.0.5
    • Component/s: VDB
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      1) Create VDB 1 , name it in Upper case
      2) Create VDB 2 , name it in Upper case
      3) Create VDB 3 and import VDB 1 and VDB 2 as views, create connection profiles to VDB 1 and VDB 2 using vdbnames in connect string in a case that doesn't match VDB names case.
      4) Try deploying VDB 3 to see the error.

      Show
      1) Create VDB 1 , name it in Upper case 2) Create VDB 2 , name it in Upper case 3) Create VDB 3 and import VDB 1 and VDB 2 as views, create connection profiles to VDB 1 and VDB 2 using vdbnames in connect string in a case that doesn't match VDB names case. 4) Try deploying VDB 3 to see the error.

      Description

      I have built couple of VDBs using designer, their names are all CAPS and wanted to import these 2 VDBs as views in my 3rd VDB. As the VDB name is cases insensitive in connect string i used lower case to connect to the VDB to do JDBC import. After i completed my 3rd VDB when i tried to deploy the VDB onto the server it is going into INACTIVE state, after changing my connection string to upper case and reimporting the VDB i was able to deploy the 3rd VDB and it state turned to ACTIVE.

      The VDB import definition seem's to be case sensitive and this may be the cause of the errors.
      I haven't tested this in Dynamic VDB.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                shawkins Steven Hawkins
                Reporter:
                chanduakkin Chandra Akkinepalli
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: