OAS on Marketplace: Create Domain Error On Create Schema

davidkhala-Oracle

Summary:

My OAS stack cannot pass one of validation, due to

[VALIDATION] [ERROR]:PreReq Check for create new schema failed.

Content:

The following suggestion lets me check if DB is compatible.

[VALIDATION] [SUGGESTION]:Ensure the Database being used is compatible.
configuration Failed. Exiting configuration due to data validation failure.

I can confirm I am using DBVM of 19c. Specifically, it is 19.12.

I double check that the using DB user in stack configs has enough right granted to create schema.

I double check that I am connecting to the pluggable db fo the DBVM

Version (include the version you are using, if applicable):

Using OAS 2022 (6.4) 0301 (9/23/2022)

Gianni Ceresa

If the compute instance has not been killed, connect via SSH and run the RCU by hand to find out what is the issue with the info you are providing.

You say that you confirmed everything is correct but still the tool doesn't like it, therefore something isn't as correct as somebody/something think it is...

Are you using an account with SYSDBA privileges? Because it can be quite tricky to make sure your account has enough grants and that the tool will accept it.

Running the RCU manually, even just with the -validate attribute to not do anything else than just testing things will let you debug the situation.

SteveF-Oracle

To add:

Schema creation in RCU is performed in multiple phases; each phase requires a different level of access to your database.

Review this:

Preparing for Schema Creation

Regards.

Gianni Ceresa

True, in a full install with a separate execution of the RCU. That's the process to follow if you don't have a SYSDBA account.

The issue is that the marketplace image does use the implicit call for the RCU creation when calling config.sh, that's also why it doesn't show much details of what the RCU is doing and really generally require to match the most common case: to be called by providing the credentials of sys and not some kind of custom/hand-made account with a bunch of grants.

The OAS on Marketplace image is something that I will not suggest to use. Installing OAS yourself takes 10 minutes and can be done with a single script (or an Ansible playbook). The OAS on Marketplace image is not a great example of OAS. The first release was a collection of all the mistakes you should not do when installing OAS, luckily they started fixing some over time, but still ...

SteveF-Oracle

Yep, the post wasn't all that clear as to the steps performed, but I did pick up they were using an alternate DB user for the connection.

I never had any issue deploying OASMP via UI or terraform even with the first releases, but to each their own, there are several options available now (manual, vm, any IaaS, docker/podman, etc.)

The logs show you exactly what steps it is performing.

Addendum: I take that back, once, I forgot to enable the DBaaS port in the firewall.

Cheers

davidkhala-Oracle

Thanks, I would like to provide more details and clarify on points I have double check.

• VM access: Indeed, I am able to ssh into the VM. Actually, my previous provided error message is extracted from the VM, by

cat /var/log/oas_create_domain.log

• DB user: I am using the built-in DB user sys. It has built-in SYSDBA privilege, right? . In other attempts, I also have tried to create a new DB user and `grant SYSDBA to <the new user>` , but still failed.

My questions to @Gianni Ceresa

Running the RCU manually, even just with the -validate attribute to not do anything else than just testing things will let you debug the situation.

Would you mind point me out which binary should we use to run the RCU mannually? And what is the next step after Running the RCU manually? I mean, some steps to re-trigger the create-domain process.

Gianni Ceresa

The RCU is located in ORACLE_HOME/oracle_common/bin/rcu , you can find details on how it does work by command line in the OBIEE 12.2.1.4 doc (as the RCU didn't change much, it's only the content of the schemas that evolved): https://docs.oracle.com/en/middleware/fusion-middleware/12.2.1.4/rcuug/running-repository-creation-utility-command-line.html

It's true that you could re-run the script creating the domain once you managed to debug the issue with the RCU and database, but is it worth it? Knowing it come from a stack, just drop it and run it fully again to have a "clean" environment. It will only takes a few extra minutes.

Gianni Ceresa

Just a last comment: if your database has compressed tablespaces and the RCU try to create the schemas on those, it will fail. There isn't an error saying it's because of compressed tablespaces but it just fail to create some objects in the BIPLATFORM schema and therefore rollback everything else.

I did report the bug months ago but because it is in the installer, not really sure how/if/when it will be fixed (probably never waiting for the 2023 release of OAS and hopefully there it works?).

There are little chances this is actually your issue, but it's definitely one that kept me busy some time trying to figure out what the error was... Other than this the RCU generally works well.

Michal Zima

@Gianni Ceresa Gianni, could you, pls, share, Bug No for this (if it is a published Bug) ?

Thanks

Gianni Ceresa

Sadly I don't have one because I don't have a CSI allowing me to open SRs for on-premises products, I only have a few for cloud products (but I can't really report a RCU bug for OAC as it will not be accepted).

I did send all the details directly to a PM (@Alan Lee - Oracle-Oracle ) in March 2022 who passed it to the team in charge of it. It was treated as a bug (it is a regression as it fails with 6.4 while it works with 5.9). That's all I have.

Maybe Alan can find a bug number for this?

davidkhala-Oracle

Dear community members,

Here is my debugging result. In my previous setup which introduce the schema creation error, I use a password like

David-KL04#

This is a valid Oracle DB user password, but not valid for RCU schema.

According the `$ORACLE_HOME/oracle_common/bin/rcu` dry-run result,

A valid password must be specified. Password should be alpha numeric only and can contain the following special characters: $, # , _ .Password should not start with a number or a special character.

Hyphen (-) in my specified password is not an allowed char.

Hope it help later people how come across the same issue.

I feel a little bit uncomfortable since the Terraform didn't do this precheck. Neither anywhere in document mentioning about this different password restriction than a usual Oracle DB user. Most terrable is the initial error statement in /var/log/oas_create_domain.log has less implication on schema password issue, but bias towards a DB version issue.

I prefer to consider this as a user-friendly bug