Clarity

Expand all | Collapse all

checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

  • 1.  checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Posted Apr 09, 2015 11:42 AM

    anyone would have encountered the same error?

     

    running checkinstall from checkinstall folder works fine and gives no error.

     

    running install.jar (v14.2) to upgrade from 14.1 checkinstall gives errors when trying to connect to DB !!! logon denied username/passwork not ok...

     

     

    thanks,

     

    Olivier



  • 2.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Broadcom Employee
    Posted Apr 09, 2015 11:45 AM

    Hi Olivier,

     

    Can you please post the exact error message, also the <encryption line from properties.xml.

     

    Kind Regards

     

    Nika Hadzhikidi

    CA Technologies

    Principal Support Engineer



  • 3.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Posted Apr 09, 2015 11:53 AM

    the exact error message shown in install.log is:

    D:\temp\checkinstall\scripts\check-db-version.xml:99: java.sql.SQLInvalidAuthorizationSpecException: [CA Clarity][Oracle JDBC Driver][Oracle]ORA-01017: invalid username/password; logon denied

     

    there is no <encryption line in the properties.xml

     

    merci!



  • 4.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Broadcom Employee
    Posted Apr 09, 2015 11:53 AM

    Hi Olivier,


    Also check the NLS_LANG parameter is correctly set and all the mentioned Init.ora parameter is correct.

     

    Regards

    Suman Pramanik



  • 5.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Posted Apr 09, 2015 11:59 AM

    Hi Suman,

     

    those are the parameters that we are using and that are working with our actual 14.1.  There is a trigger for the NLS_DATE_FORMAT at the Session level.  Could ENGLISH (instead of AMERICAN) language be the problem?

     

    thanks

     

    parameter

    actual values

    *** mandatory values ***

    NLS_LANGUAGE

    AMERICAN

    AMERICAN

    NLS_TERRITORY

    AMERICA

    AMERICA

    NLS_CHARACTERSET

    AL32UTF8

    AL32UTF8

    NLS_DATE_FORMAT

    DD-MON-RR

    YYYY-MM-DD HH24:MI:SS

    NLS_SORT

    BINARY

    BINARY

    NLS_COMP

    BINARY

    BINARY

    NLS_RDBMS_VERSION

    1. 11.2.0.4.0
    2. 11.2.0.4.0

    NLS_LANGUAGE

    ENGLISH

    AMERICAN

    NLS_TERRITORY

    UNITED KINGDOM

    AMERICA

    NLS_SORT

     

    BINARY

    NLS_DATE_FORMAT

     

    YYYY-MM-DD HH24:MI:SS

    NLS_COMP

    BINARY

    BINARY

    NLS_LANGUAGE

    ENGLISH

    ENGLISH

    NLS_TERRITORY

    UNITED KINGDOM

    AMERICA

    NLS_DATE_FORMAT

    YYYY-MM-DD HH24:MI:SS

    YYYY-MM-DD HH24:MI:SS

    NLS_SORT

    XWEST_EUROPEAN

    BINARY

    NLS_COMP

    BINARY

    BINARY



  • 6.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Broadcom Employee
    Posted Apr 09, 2015 12:04 PM

    Hi Olivier,

     

    Yes, i could managed to get it resolved after changing the values. Can you change to mandatory values and give a try.

     

    Regards

    Suman Pramanik



  • 7.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Broadcom Employee
    Posted Apr 09, 2015 01:17 PM

    Olivier:

     

    The NLS values are requirement per Installation Guide, so they are mandatory. If they are set to something else, this can lead to all kind of different issues. Please ensure you set the Oracle database as follows:

    NLS_LANG - AMERICAN_AMERICA.AL32UTF8

    Character Set

    AL32UTF8

    National Character Set

    UTF8/AL16UTF16

    nls_date_format

    YYYY-MM-DD HH24:MI:SS

    nls_sort

    BINARY

    nls_comp

    BINARY

    query_rewrite_enabled

    true

    Cursor_sharing

    FORCE

     

     

     

    Then please restart the install and let us know how the checkinstall did go.

     

     

    Kind Regards

     

    Nika Hadzhikidi

    CA Technologies

    Principal Support Engineer



  • 8.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Posted Apr 09, 2015 06:07 PM

    Hi,

     

    We have the same issue. It is related to to the fact that there are two different oracle drivers in the package. CA already raised a bug for this. We managed to do the installation by copying the right driver. Also look to the setting for case sensitive in the database. We also had success by setting this to true, which is the default.

     

    Here an extract from our case:

    Next to that we also found 2 different versions of the jar file that

    contains the java class that is responsible for the connection to the

    database. The one in the checkinstall utility differs from the one in the

    installation itself.

     

    File with Oracle driver is c-oracle.jar on the following locations:

    %install-dir%/tools/lib

    2152668 Sep 19 10:06 c-oracle.jar

     

    %install-dir%/checkinstall/tools/lib

    2071808 Aug 28 15:30 c-oracle.jar

     

    The internal dates of the two files are 21-01-2014 and 25-10-2012

     

    %install-dir% is the directory where you unpacked the install.jar file from

    the installation DVD and where the install.sh file is located to start the

    actual upgrade process.

     

    Just as a test we copied the c-oracle.jar file from %install-dir%/tools/lib

    to %install-dir%/checkinstall/tools/lib and ran the checkinstall utility

    again. The checkinstall utility now also fails at the first check on the

    database connection. This demonstrates the issue that I face since the

    beginning but it seems that we found the cullprit that is responsible for

    the different behaviour.



  • 9.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Posted Apr 09, 2015 06:21 PM

    May I ask which version of Oracle exactly this was with please (for some internal testing/comparison purposes)?  The full version and patch level.

     

    Also which case sensitive setting do you refer to please?

     

    Thanks.



  • 10.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2
    Best Answer

    Posted Apr 10, 2015 02:11 AM

    See bug id :CLRT-77222

    It is all described in case 21954895-1, whiCh is handeld by Suman.

    We took the workarround of copying the wotking driver into the install package. I ivestigated this issue in depth and the failure is caused by the comminication between client and database server where the handshake is failiing. But Suman knows allbthe details of this case. We have experimented with the Case sensitive setting, but it may be a combination of some settings.



  • 11.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Posted Apr 10, 2015 05:29 AM

    indeed this is the same problem (bad c-oracle.jar file in package.jar) again I had this issue installing 14.1 and now again upgrading to 14.2...

     

    workaround from Suman that worked is the following:

    Extract the install.jar in my temp directory

    - Take the library "c-oracle.jar" inside ...temp\checkinstall\tools\lib and

    copy it inside the folder ..temp\tools\lib replacing the existing one.

    - Take the file "package.jar" contained in ..temp\install-packages\14.1.0

    and unbuild (renamed it in package.zip and extracted) it in my temp2

    directory.

    - Take the library "c-oracle.jar" inside ...temp\checkinstall\tools\lib and

    copy it inside the folder ..temp2\lib replacing the existing one.

    - rebuild the package.jar modified and run the install

    (Connection settings ignored by CSA... always localhost:1521... (14.1 on Oracle))

     

    thanks ddeneer and suman for pointing me to the right direction!



  • 12.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Broadcom Employee
    Posted Apr 10, 2015 05:34 AM

    Olivier,

     

    I am glad to hear, however can you please correct the mandatory setting and give it a try. I am working with our development team to see how we can get this fixed and I had this issue and after correcting the mandatory parameter I was able to get this fixed. So if you can give a try and let me know.

     

    Regards

    Suman Pramanik



  • 13.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Posted Apr 10, 2015 05:40 AM

    unfortunately I cannot change the shared database level NLS parameters as it resides on a shared DB server the customer does not plan to provide a dedicated DB server for CA PPM



  • 14.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Broadcom Employee
    Posted Apr 10, 2015 06:01 AM

    Hi Olivier,

     

    I understand, and I am working to find out what is the real cause and how we can overcome.

     

    Regards

    Suman Pramanik



  • 15.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Posted Apr 10, 2015 07:16 AM

    Hi Olivier,

     

    for the installation process, you can change the environment variables on your command prompt so the session on the database will use the required configuration.

     

    Regards

    Georg Schmid



  • 16.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Posted Apr 10, 2015 09:00 AM

    good to know for the next time thanks the installation went fine after replacing the failing "buggy" c-oracle.jar file!

     

    by the way I have experienced the same DB logon problem when installing Jaspersoft 5.6.1 !!! I have had to replace %jaspersoft-folder%/libs/c-oracle.jar file (with the checkinstall/tools/lib one) as well to start the installation... would be interesting to know why one jar files connects and the other not...



  • 17.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Broadcom Employee
    Posted Apr 10, 2015 09:28 AM

    I know the workaround works but it certainly looks due to the pre requisite not met its failing.

     

    Regards

    Suman Pramanik



  • 18.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Broadcom Employee
    Posted Apr 13, 2015 11:03 AM

    Olivier,

     

     

    Please note that instance schema NLS parameters can be set separately from the database ones, so I would strongly recommend you to change them as soon as possible.

     

    Unrelated to the fact you can or not workaround the upgrade issue:

     

    Using different from the required parameters such as NLS_LANG, NLS_DATE_FORMAT, NLS_TERRITORY, NLS_SORT and NLS_LANGUAGE makes your Clarity environment unsupported and can lead to all kinds of data issues, which will also be unsupported.

     

    Please ensure you have those corrected, it's very important.

    Kind Regards

     

    Nika Hadzhikidi

    CA Technologies

    Principal Support Engineer



  • 19.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Posted May 20, 2016 03:25 AM

    Hi Nika

     

    We are also facing same issue where PROD db is on shared server. Hence DB team refuse to apply setting (NLS_LANG) at database level. Are you confirming that if it is set at instance level, would also be fine. Please find below screen shot:

    Is this setting ok for us to start upgrade? Appreciate your quick response.



  • 20.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Broadcom Employee
    Posted May 20, 2016 11:53 AM

    Hi Sapan,

     

    Are you facing the same issue with the checkinstall "ORA-01017: invalid username/password; logon denied"?
    You can run the checkinstall now and see if it goes well.
    To do this, on your test server
    1. Ensure the Java_home is set to new variable if needed
    2. Extract the install.jar for the version you want to upgrade to
    3. Stop services
    4. Navigate to the install folder you extracted in step 2
    5. Run the command install

    After entering all the details, the checkinstall part will run. You are not obliged to run the full upgrade, just when asked if you want to perform the actual upgrade, after the checkinstall runs, say :

    n

    This will mean it will only run the checkinstall part.

    NLS_LANG setting is not related to the root cause of CLRT-77222, but is a required parameter. I see some of your parameters are not set, which probably means they will be inherited from the database. I'd speak to your DBA to ensure all the PPM required database parameters are set at instance level whenever possible. Territory should not be left as UNITED KINGDOM as well. Having the wrong parameters may cause issues with the upgrade or after upgrade with the product functionality.

     

    Please let me know how it goes.

    Kind Regards -Nika



  • 21.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Posted May 25, 2016 06:22 AM

    Thanks Nikka, will revert if any further questions.



  • 22.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Posted May 27, 2015 05:51 AM

    Are there any plans from CA Software Engineering to fix the existing installation packages and furthermore fix this in the future?

    One of our customers currently experiences this issue and a lot of manual trial/error is necessary to workaround, since the different states of c-oracle.jar occur several times throughout the whole installation routine, including the install-packages.

     

    Anyway, thanks Suman for the workaround.



  • 23.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Broadcom Employee
    Posted May 27, 2015 10:45 AM

    Hi Dennis,

     

    We are in discussion with Software Engineering and will update as soon as possible.

     

    Regards

    Suman Pramanik



  • 24.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Posted Aug 28, 2015 04:24 AM

    Hi all,

     

    We were facing exact same issue. But our expierience is that an Oracle password reset just before the upgrade will solve this issue.

    That saves us from modifying packages.:-)

     

    Kind regards,

    Coen Verweij



  • 25.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Broadcom Employee
    Posted Aug 28, 2015 04:52 AM

    Hi Coen,

     

    Thanks for the update, but what we figured out the problem is due to the defect(PSC00294082) in DataDirect Drivers. http://knowledgebase.progress.com/articles/Article/000048244

     

    Regards

    Suman Pramanik



  • 26.  Re: checkinstall v14.2 running as standalone works but NOT when launching install.bat to upgrade from 14.1 to 14.2

    Posted Aug 28, 2015 09:32 AM

    The defect is around the authentication (specifically the driver's encryption of the password before issuing it to the Oracle server) so altering the password can be a viable workaround - the only problem with that, is you may or may not find an acceptable password that works (and this may also depend from one environment to the next).  It isn't guaranteed, but if it does work it is easier than having to repackage.