Forum Stats

  • 3,855,530 Users
  • 2,264,518 Discussions
  • 7,906,048 Comments

Discussions

Cannot connect to Discoverer following database upgrade to 12c

ora_nut
ora_nut Member Posts: 71 Blue Ribbon
edited Jan 4, 2017 4:31AM in Discoverer

Hello,

We are on EBS 12.1.3, and have recently upgraded our database from 11.1.0.7 to 12.1.0.1.

Discoverer version: 11.1.1.3.0.

When trying to connect to Discoverer we now get the following error:

- Failed to connect to database - Unable to connect to Oracle Applications database (afscpgcs)

We'd had to reset the Apps password during the database upgrade, so then followed the steps in the following document:

After Cloning Oracle Applications And Resetting APPS Password, Discoverer 10g/11g Fails With Error: Unable To Connect To Oracle Applications Database (afscpgcs) (Doc ID 788706.1)

However this has not solved the problem and we still get the same error.

Does anyone have any ideas of something else we could try/check please?

Thanks

Hazel

Tagged:

Best Answer

  • sbeck-Oracle
    sbeck-Oracle Member Posts: 116 Employee
    edited Dec 28, 2016 10:06AM Answer ✓

    This can be caused by the APPS database password being in mixed case.  Discoverer passes the APPS password in all upper case.

    By default, passwords in Oracle Database 12c are case sensitive and the IGNORECASE argument of ORAPWD and the SEC_CASE_SENSITIVE_LOGON parameter are deprecated in Oracle Database 12c.
    So, you will need to run FNDCPASS utility to change the APPS password to a new one in ALL Caps and then try to connect using Discoverer.

    If that does not resolve, another possibility is that the Guest user password is corrupted or encrypted incorrectly.  This can be seen by following Note 370803.1 (How To Create An E-Business Suite Connection Trace For Discoverer 10g / 11g Administrator Or Desktop).  You will see messages like:

    ...
    STATEMENT fnd.src.security.afscp.afscpcon: Opening apps connection
    STATEMENT fnd.src.security.afscp.afscpcon: Get responsibility info
    STATEMENT fnd.src.security.afscp.afscpcon: user_id = 0, resp_type = I, resp_key = #20420 resp_id = 20420
    STATEMENT fnd.src.security.afscp.afscpcon: appl_type = I, appsname = #1, appl_id = 1, secgrp =

    STATEMENT fnd.src.security.afscp.afscpcon: Decrypting new oracle pwd for resp
    PROCEDURE fnd.src.security.afscp.afscpcon: End: Failure
    PROCEDURE fnd.src.security.afscp.afscpfree: Begin
    PROCEDURE fnd.src.security.afscp.afscpfree: End

    1. Set the EBS profile "Signon Password Case" is set to "Insensitive" and then use FNDCPASS to set the APPLSYS password to what it currently is, it forces the reencryption without changing the APPS password.

    2. Run autoconfig on Applications tiers so that new password is propagated correctly.

    Note:  Check FNDCPASS log for any kind of error. If there is any error in the FNDCPASS log, then DO NOT run autoconfig or try to change configuration file manually. Until and unless FNDCPASS log has no error.

    3. Restart Applications tier and concurrent servers.

    4. Reset "Signon Password Case" back to "Sensitive" again.

    5. Please copy the dbc file e.g. CMPRD1.DBC from Apps server after running auto config and paste it to the Discoverer Home secure folder with the name cmprd1_balance.dbc and another copy with the name cmprd1.dbc (all in lower case)

    Please always make a backup of the FND_USER and FND_ORACLE_USERID tables prior to such changes.

Answers

  • ora_nut
    ora_nut Member Posts: 71 Blue Ribbon
    edited Dec 19, 2016 6:07AM

    A couple of other things to add:

    I was able to connect using Discoverer Administrator, although I got this error message:

    "Some of your existing summaries have become invalid. These summaries need to be refreshed using the Refresh Summaries command under the Tools menu."

    After clicking on "OK" to this message I seem to be able to view the data folders OK.

    When connecting via Viewer/Plus we choose to connect to "Oracle Applications". This is when we get the error message mentioned above.

    Thanks

    Hazel

  • sbeck-Oracle
    sbeck-Oracle Member Posts: 116 Employee
    edited Dec 28, 2016 10:06AM Answer ✓

    This can be caused by the APPS database password being in mixed case.  Discoverer passes the APPS password in all upper case.

    By default, passwords in Oracle Database 12c are case sensitive and the IGNORECASE argument of ORAPWD and the SEC_CASE_SENSITIVE_LOGON parameter are deprecated in Oracle Database 12c.
    So, you will need to run FNDCPASS utility to change the APPS password to a new one in ALL Caps and then try to connect using Discoverer.

    If that does not resolve, another possibility is that the Guest user password is corrupted or encrypted incorrectly.  This can be seen by following Note 370803.1 (How To Create An E-Business Suite Connection Trace For Discoverer 10g / 11g Administrator Or Desktop).  You will see messages like:

    ...
    STATEMENT fnd.src.security.afscp.afscpcon: Opening apps connection
    STATEMENT fnd.src.security.afscp.afscpcon: Get responsibility info
    STATEMENT fnd.src.security.afscp.afscpcon: user_id = 0, resp_type = I, resp_key = #20420 resp_id = 20420
    STATEMENT fnd.src.security.afscp.afscpcon: appl_type = I, appsname = #1, appl_id = 1, secgrp =

    STATEMENT fnd.src.security.afscp.afscpcon: Decrypting new oracle pwd for resp
    PROCEDURE fnd.src.security.afscp.afscpcon: End: Failure
    PROCEDURE fnd.src.security.afscp.afscpfree: Begin
    PROCEDURE fnd.src.security.afscp.afscpfree: End

    1. Set the EBS profile "Signon Password Case" is set to "Insensitive" and then use FNDCPASS to set the APPLSYS password to what it currently is, it forces the reencryption without changing the APPS password.

    2. Run autoconfig on Applications tiers so that new password is propagated correctly.

    Note:  Check FNDCPASS log for any kind of error. If there is any error in the FNDCPASS log, then DO NOT run autoconfig or try to change configuration file manually. Until and unless FNDCPASS log has no error.

    3. Restart Applications tier and concurrent servers.

    4. Reset "Signon Password Case" back to "Sensitive" again.

    5. Please copy the dbc file e.g. CMPRD1.DBC from Apps server after running auto config and paste it to the Discoverer Home secure folder with the name cmprd1_balance.dbc and another copy with the name cmprd1.dbc (all in lower case)

    Please always make a backup of the FND_USER and FND_ORACLE_USERID tables prior to such changes.

  • ora_nut
    ora_nut Member Posts: 71 Blue Ribbon
    edited Jan 4, 2017 4:31AM

    Thanks very much sbeck!

    Unfortunately due to time contraints we had to change the plan and upgrade to 11.2.0.4 instead, but the information you have given will be extremely useful when we do come to upgrade to 12c in the future.

    Thanks again, it's much appreciated.

    Hazel

This discussion has been closed.