Error creating an OAC instance

Lenin Valencia

Summary

I get the Error PSM-BOOT-01009 DNS lookup failed for expected service hostname.

Content

Hello,

 

I try to create an instance of OAC, all the validations are correct, but I get the error:

 

04-sep-2018 16H13' UTC Started operation to create service [SENASICAOAC1] in identity domain [idcs-a4b176b3d2b3437f93d1fbe403f3c344].

04-sep-2018 16H13' UTC Started pre-check for load balancer configuration for service [SENASICAOAC1].

04-sep-2018 16H13' UTC Completed pre-check for load balancer configuration for service [SENASICAOAC1].

04-sep-2018 16H14' UTC Creating resources [senasicaoac1-bi-1] for service [SENASICAOAC1].

04-sep-2018 16H24' UTC Completed creating service [SENASICAOAC1] resources in domain [idcs-a4b176b3d2b3437f93d1fbe403f3c344].

04-sep-2018 16H24' UTC Started operation to establish security on VMs for component [BI].

04-sep-2018 16H24' UTC Completed operation to establish security on VMs for component [BI]

04-sep-2018 16H24' UTC Started operation to check provisioning status on the VMs for [BI]

04-sep-2018 16H24' UTC Started load balancer configuration for service [SENASICAOAC1].

04-sep-2018 16H26' UTC Completed load balancer configuration for service [SENASICAOAC1].

04-sep-2018 16H34' UTC Service has returned the following error(s) for service component [BI]: [Error during BI setup].

04-sep-2018 16H34' UTC PSM-LCM-01101 Unable to provision service. One or more components could not be configured. See additional errors for more details.

04-sep-2018 16H34' UTC The service creation failed in attempt [1] out of [2]. The service creation will be retried after [5] minutes. The failed service and its resources will be cleaned up before retrying the service creation.

04-sep-2018 16H34' UTC PSM-BOOT-01009 DNS lookup failed for expected service hostname.

04-sep-2018 16H34' UTC Submitted job to remove failed service.

04-sep-2018 16H34' UTC Started operation to delete service [SENASICAOAC1] in domain [idcs-a4b176b3d2b3437f93d1fbe403f3c344].

04-sep-2018 16H34' UTC Started pre-check for load balancer configuration for service [SENASICAOAC1].

04-sep-2018 16H35' UTC Completed pre-check for load balancer configuration for service [SENASICAOAC1].

04-sep-2018 16H36' UTC Predelete complete

04-sep-2018 16H36' UTC Successfully removed service resources.

04-sep-2018 16H36' UTC Execution of script [paasResources/preDelete] completed for component [BI].

04-sep-2018 16H36' UTC Started deletion of load balancer configuration for service [SENASICAOAC1].

04-sep-2018 16H36' UTC Completed deletion of load balancer configuration for service [SENASICAOAC1].

 

Someone knows what this error is due to and how to correct it.

 

Now try the Data Lake and Enterprise versions.

 

Thanks for your help.

Version

OAC 18.2.1-1510

FPonte

Hi Lenin.

You can also find more details navigating to your cloud storage and downloading the provisioning logs.

Follow this link Troubleshooting

Let us know your findings.

Cheers.

Fernando

 

Lenin Valencia

Thanks  Fernando,

I delete all oac configuration and i try with new configuration.

Regards.

 

 

FPonte

Hi Lenin.

Quick look at setupBICS.log and you can see on line 2854 the following error.

"RCU-6131 An error occurred while connecting to the database" it was while executing Repository Creation Utility.

Make sure the user and password provided are correct.

Question. On which database version are you creating your OAC?

I remember something that on 12c Version 2 (or something like that) the process will fail.

Cheers.

Fernando

 

FPonte

Hi.

Another message on the RCU.log file.

 

Was the database up and running?

 

Tue Sep 4 13:43:33.590 UTC 2018 ERROR assistants.rcu.backend.action.JavaAction: oracle.sysman.assistants.rcu.backend.action.JavaAction::perform: 

ERROR - RCU-6131 Error while connecting to the database.

CAUSE - RCU-6131 An error occurred while connecting to the database.

ACTION - RCU-6131 Provide correct database details and try again, or contact the system administrator. - WLS

oracle.sysman.assistants.common.dbutil.SQLFatalErrorException: Unable to connect to the database using the provided details.

Enter a valid hostname and port or check if the listener is up and running.

at oracle.sysman.assistants.common.dbutil.jdbc.JDBCEngine.connect(JDBCEngine.java:721)

at oracle.sysman.assistants.rcu.backend.action.JavaAction.perform(JavaAction.java:324)

at oracle.sysman.assistants.rcu.backend.task.AbstractCompTask.execute(AbstractCompTask.java:255)

at oracle.sysman.assistants.rcu.backend.task.ActualTask.run(TaskRunner.java:346)

at java.lang.Thread.run(Thread.java:748)

 

Cheers.

 

Fernando

Mark_Daynes

Fernando makes a good point - I was with a customer last week who was setting up OAC and I believe the current version of OAC needs 12.1 (or 11g) as the DB.  That was with the non-autonomous OAC of course.  I have yet to set up an autonomous OAC instance but looking at the setup documentation it looked like a really straightforward process.

Mark

Lenin Valencia

Hello Fernando,

 

Thanks for your time and your comments, I already verified and apparently this problem arises when trying to use a database in RAC.

I already made the same configuration with a single instance of the database and the error no longer occurs.

I appreciate your time very much.

 

I only have the doubt because it does not work with the database in RAC.

 

I will investigate this in the documentation.

 

Regards...

Lenin Valencia

Thanks Mark, i checked the version of the database and this is correct.

I solved the problem using a single instance of database.

 

Regards...