4 Replies Latest reply on Sep 3, 2019 6:46 PM by Amol Gavali

    data is not saving in one column in docmeta

    3758633

      We have  column(XC_CAPIND VARCHAR2(30 CHAR)) in docmeta table, using java code  and url http://xxxx:16200/cs/idcplg to connect content server, uploading document and setting multiple columns in docmeta table, one column mentioned above is not storing with value, shows as null on running sql query. whereas using same code processing same data, save all data including value in the column. help what might be causing we have wcc 11g.

        • 1. Re: data is not saving in one column in docmeta
          Srinath Menon-Oracle

          one column mentioned above is not storing with value, shows as null on running sql query. whereas using same code processing same data, save all data including value in the column. help what might be causing we have wcc 11g.

           

          The issue that you are facing is not quite clear, what exactly is not storing and in what scenario ?

           

          Provide some illustration and details for the issue to be clear .

          • 2. Re: data is not saving in one column in docmeta
            3758633

            we have below code to upload document and set custom meta data. binder.putLocal("IdcService", "CHECKIN_UNIVERSAL"); binder.putLocal("XC_CAPIND", "100"); binder.putLocal("XC_TEST", "200"); .. .. .. response = client.sendRequest(userContext, binder); upload is successful and do see value XC_TEST=200, whereas XC_CAPIND=null. if we run same code point to another environment(http://host2:16200/cs/idcplg), upload is successful and do see value XC_TEST=200, whereas XC_CAPIND=100. this confirms something wrong in the (http://host1:16200/cs/idcplg) for the field XC_CAPIND. We have verified docmeta table has the column XC_CAPIND VARCHAR2(30 CHAR), don't see anytime value stored on the column. looks some configuration causing the issue.

            • 3. Re: data is not saving in one column in docmeta
              Srinath Menon-Oracle
              for the field XC_CAPIND. We have verified docmeta table has the column XC_CAPIND VARCHAR2(30 CHAR),

              Please check from configuration manager and verify if this metadata is created correctly or not .

               

              Secondly, enable requestaudit,systemdatabase + Full verbose option .

               

              Clear server output.

               

              Run the same test again and check from server output for the the insert sql statements and see what all values are being passed .

              • 4. Re: data is not saving in one column in docmeta
                Amol Gavali

                check using config man in both working vs not working instance if XC_CAPIND is created as option list validated vs no option list vs not validated. if its validated then it will not accept value if it doesnt exists in options list.