Layer7 Access Management

Expand all | Collapse all

Error while importing policy store

Jump to Best Answer
  • 1.  Error while importing policy store

    Posted 08-01-2016 04:11 AM

    We are trying to import the the existing policy store in a new policy store. We are using smobjimport. Our existing policy store is R12SP3 and the new policy store is R12.52SP1

    We are able to successfully import all of the objects expect one object - RootConfig object.

    We get the below error in import logs.

    ERROR: Failed updating RootConfig object <OID> Status: 'Unknown Failure'

     

    We have tried the below steps:

    1) Dropped the tables and started afresh.

    2) Reduced the length of DynamicPrefs by deleting unused administrators as the length was more than 1024 which is the max limit.

     

    The error still persists and we are unable to find a solution for this. Please advise.



  • 2.  Re: Error while importing policy store

    Posted 08-01-2016 09:36 PM

    Hi Harshit,

     

    Just to clarify, you setup R12.52 SP1 policy store with its schema and data definition. Then you import the policy export from R12 SP3 server and getting error importing the RootConfig object.

     

    How did you remove the un-used admin -- from WAM UI or database/LDAP? -- try remove the entries from database/LDAP directly

    Are you able to export the existing R12.52 SP1 policy data (after the smobjimport)?

    Are you able to revert the import and try with XPSExport, XPSImport instead?



  • 3.  Re: Error while importing policy store

    Posted 08-02-2016 04:01 AM

    Hi Wonsa,

     

    Yes, we setup R12.52 SP1 with schema and Data Definition and then we import the policy export from R12 SP3 server and getting the error.

     

    We had cleared the unused administrators from the DynamicPrefs parameter in the smdif file. We tried deleting the entire value as well but it didn't work. This solution worked for another environment of ours though.

     

    We didn't try exporting the policy data from R12.52 SP1 after smobjimport as smobjexport is no longer available in 12.52.

     

    We have migrated two of our environments successfully using smobjimport, so we are keen on doing the same for this environment as well.

     

    Also, XPSExplorer fails to load after the import on 12.52 SP1. We get the below error:

    [16838/1][Mon Aug 01 2016 09:53:40][HSTMT.cpp:148][ShowError][ERROR][sm-xpsxps-00870] An error occurred when calling "SQLExecDirect" for "Create Object" query

    [16838/1][Mon Aug 01 2016 09:53:40][HSTMT.cpp:241][Error][ERROR][sm-xpsxps-00810] Native Diagnostic: HY000:1012 [DataDirect][ODBC Oracle Wire Protocol driver][Oracle]ORA-01012: not logged on

     

    Regards,

    Harshit Verma



  • 4.  Re: Error while importing policy store

    Posted 08-02-2016 10:38 AM

    Have you verified that the Policy Server can connect to the Policy Store?  That ORacle ODBC error would indicate otherwise.



  • 5.  Re: Error while importing policy store

    Posted 08-03-2016 03:31 AM

    Yes, the Policy server is able to connect to the policy store. I verified it through smconsole.



  • 6.  Re: Error while importing policy store

    Posted 08-03-2016 07:59 AM

    Hi Harshit,

     

    ORA-01012 is suggestive that there're some issues connecting to the Oracle Database instance. I suspect you will get the same error running XPSExport.

     

    Please enable ODBC trace, restart the database instance and check the ODBC trace and database log corresponding to execute XPSExplorer utility.



  • 7.  Re: Error while importing policy store
    Best Answer

    Posted 08-30-2016 02:42 AM

    Hi All,

     

    The issue has been resolved.

    We did the below steps to resolve the issue:

    1) Dropped the tables and created them again with the DynamicPrefs datatype/length set to varchar2[3120] instead of the default varchar2(1024). Our existing policy store had the same setting.

    2) Ran a fresh smobjimport after importing the schema and default objects. We didn't remove the DynamicPrefs value this time as its length was only 2400 which is lesser than what we have set in database.

     

    The import was successful.



  • 8.  Re: Error while importing policy store

    Posted 08-30-2016 06:43 PM

    Hi Harshit,

     

    Just want to thank you for sharing the solution back to the community. This will be helpful in the future for anyone getting across similar issue.

     

    Regards,

    Ujwol