Categories
- All Categories
- 76 Oracle Analytics News
- 7 Oracle Analytics Videos
- 14K Oracle Analytics Forums
- 5.2K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 40 Oracle Analytics Trainings
- 59 Oracle Analytics Data Visualizations
- 2 Oracle Analytics Data Visualizations Challenge
- 3 Oracle Analytics Career
- 4 Oracle Analytics Industry
- Find Partners
- For Partners
Oracle Analytic Server 2024 Installation - Configuration Fails
Answers
-
@SteveF-Oracle please can you direct me to the location of the "jps-config.xml" file
0 -
@Eugene_A_O > [DOMAIN_HOME]/config/fmwconfig
Check with your DBA if the database is in shared server mode
If this is not a requirement, then disable itALTER SYSTEM SET SHARED_SERVERS=0;
ALTER SYSTEM SET MAX_SHARED_SERVERS = 0;ALTER SYSTEM SET DISPATCHERS = '';
There is no requirement to restart any part of the database for this change to take effect.
If there is a requirement, then the JDBC URL connect string may need be updated with the optional switch: SERVER=DEDICATED
jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS_LIST =(ADDRESS =(PROTOCOL=TCP)(HOST=<HOSTNAME>)(PORT=1521)))(CONNECT_DATA=(SID=<SID>)(SERVER=DEDICATED)))
0 -
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.
@Gianni Ceresa - It looks like was marked inadvertently (not sure by whom). I have un-marked it.
1 -
I think mostafa already said above, but are you using any special characters in the schema passwords?
If you have any special characters restart from scratch choosing only A-Z 0-9 passwords. In the old days it created problems, its possible it still does. Same goes for any bi admin passwords through the install/config/upgrades.
0 -
@SteveF-Oracle > I confirmed with my DBA the database is in shared server mode and its a requirement.
Also I noticed I don't have this [DOMAIN_HOME]/config/fmwconfig when the installation fails.
@BrandonH > there are no special characters in any of my password
We currently working on with a workaround where we will install a database on the same server as the application server.
0 -
-Installing OAS 2024 on RHEL8 in AWS
-DB is Oracle 19c on RAC with SCAN
-RCU is successful - used jdbc url
jdbc:oracle:thin:@(DESCRIPTION=(ENABLE=BROKEN)(ADDRESS=(PROTOCOL=tcp)(PORT=1521)(HOST=<Node1-vip>))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=<srv-name>)))
-No special characters in password - only alpha-numeric.
-Confirmed the DB is DEDICATED - shared_servers=0, max_shared_servers=0, dispatchers=''
-Running enterprise deployment Configuration
cd /u01/oracle/products/fmw/oracle_common/common/bin
./config.sh -log=config26Aug24.log -log_priority=trace
Connection Timeout error at 95%
Generates a huge log file. Checking the logs to see if I can find the issue.
0 -
@CShekar-Oracle - You may need a new separate thread, since your environment may be different, or use internal channels.
@Eugene_A_O , test by creating the schemas first with RCU, when you get to the Database Details (step 3), then use the 'Connection String' option.
Test with:
(description=(address=(host=<hostname)(protocol=tcp)(port=1521))(connect_data=(service_name=<service_name>)(server=shared)))and with:
(description=(address=(host=<hostname)(protocol=tcp)(port=1521))(connect_data=(service_name=<service_name>)(server=dedicated)))
After, run the Configuration Assistant and connect to the pre-created schemas
If you still have an issue after that, please open a service request , because additional customer specific confidential information may need be collected about your database server.0 -
If you share the logs with the current error that may help here Also what is the FMW Version and from where did you download the Software to install and configure OAS ?
0 -
@Eugene_A_O , it’s more than 2 weeks and the thread hasn’t provided a solution because it’s a very unique problem on your environments and situation (the product installs fine in a standard environment).
To find out more, all the details would be required: exact steps done for the install, all the details of the environments etc.
In my opinion, it’s maybe time you open a SR, and work on it via the private, and secure, environment provided by the SR. Allowing you to share all details, including private informations that shouldn’t be posted in a public forum.
If then, the cause is found to be something that wasn’t documented correctly, I’m sure support will publish a MOS note describing it and providing a solution.
0