Oracle Analytics Cloud and Server

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Oracle Analytic Server 2024 Installation - Configuration Fails

Accepted answer
810
Views
34
Comments
24

Answers

  • JPS-01055: Could not create credential store instance. Reason oracle.security.jps.JpsException: JPS-00027: There was an internal error: java.sql.SQLRecoverableException: No more data to read from socket

    This indicates there is connectivity issues with the database… this could be username/password, firewall, SSL connection, database configuration, network timeout, bad network hardware, etc.

    There is a slight chance the jdbc.url syntax is not correct in the jps-config.xml, but that is unlikely.


    I suggest you start with some basics:
    netcat to check access to database port
    check database sqlnet.ora for configuration
    potentially, install sql*developer on the OAS server and make a connection with JDBC

    Please work with your DBA

  • Rank 6 - Analytics Lead

    @User_XVFC1

    1- Please check the DB User's password if it does have special Characters if yes please try to change the User and schema password to NOT have any special characters

    2- Make sure your DB User does have SYSDBA Privileges .

    3- Double check the Firewall to allow connection between OAS & DB Servers on DB Port

  • Rank 3 - Community Apprentice

    Hi @Mostafa Morsy-Oracle & @SteveF-Oracle

    Thank you.

    1. We were able to connect to the database using sqlplus.

    2. On the firewall, we are still checking we haven't seen anything on that yet

    3. Also changing the password of the RCU schema password, now getting the errors below

  • Rank 6 - Analytics Lead

    @Eugene_A_O

    The Problem now with the schema Already used
    Caused by: com.oracle.cie.domain.security.external.ConfigSecurityException: oracle.security.opss.tools.lifecycle.LifecycleException: Error during configuring DB security store. Exception oracle.security.opss.tools.lifecycle.LifecycleException: The schema NEWOASDEV_OPSS is already in use for security store(s). Please create a new schema

  • Expanding on Mostafa reply, you can also run the RCU manually to delete (clean up) the RCU schemas created, so that you can then create them again with the same name (but a different password if your original password didn't follow the requirements and limitations for a RCU schema password).

  • Rank 3 - Community Apprentice

    Hi,

    I tried with a new schema

  • Rank 6 - Analytics Lead

    @Eugene_A_O

    Can you ask your DBA to create the RCU Schema with SYS User during the configuration with password only have _ as special character

  • Rank 1 - Community Starter

    @Eugene_A_O

    Please share the solution if you resolved the OAS configuration issue.

  • Rank 3 - Community Apprentice

    @Shekar-Oracle challenge still persists

  • @Eugene_A_O , so the issue isn't solved? Because the thread is marked as answered (and that's why it doesn't get any attention anymore).

    Was the reply marked as "correct" (best answer) not the correct one? I can unmark it for you if you want, that will "reopen" the thread marking it as not answered.

Welcome!

It looks like you're new here. Sign in or register to get started.