OAS on Marketplace: Create Domain Error On Create Schema

Gianni Ceresa

Can you report it as a bug?

Technically the database accept '-' in a password, but it must be quoted. This makes me say that it's a limitation in the application and a design choice to use unquoted passwords, excluding '-' and a number of other special characters.

Because of that, I do expect the application to check if the password matches with the defined rules and if not, raise an error at the application level just like any other pre-requirement check. And the error message should be explicit, saying the password doesn't respect the rules.

A precise error message in the logs is even more important in the case when the RCU is called implicitly by the configuration script itself, because at the user level you aren't even aware of what the RCU is doing exactly and with what exact parameters (but you can of course guess it's with the most default settings).

It isn't a critical bug, but still a bug the fact that there isn't a check and an explicit error message.

Alan Lee - Oracle

Bug number to request status for compressed table space issue is 34017199.

SteveF-Oracle

We do document the password issue in the Appendix for Troubleshooting 

https://docs.oracle.com/en/middleware/bi/analytics-server/deploy-oas-cloud/troubleshooting.html 

How can I confirm a problem with the connection to the database? 

>> If the username or password contains illegal characters, you see an error 

message similar to this: .....

However, perhaps somewhere we can make an improvement to document restrictions, so tha one does not have to encounter the error in the first place. 

Possibly: in the 'Complete Predeployment Checklist" 

https://docs.oracle.com/en/middleware/bi/analytics-server/deploy-oas-cloud/deploy-oracle-analytics-server-oracle-cloud.html#GUID-F34E9A58-B40B-4FC1-9279-BB1 

Documentation Enhancement (BUG 34944590 - OASMP: LIST RESTRICTIONS FOR OASMP RCU PASSWORDS) has been filed.

davidkhala-Oracle

@SteveF-Oracle Hi Steve，

I think you take a mistake like some other helpers. Actually use hyphen char (-) is allowed to as Oracle DB user password.

It is not a connection to database issue. I had no issue to use another client to connect to the Oracle DB targeted as RCU with password including hyphen.

So please double check, my original post error message is not included in the troubleshoot page cases.

Here is where I get confused, the help center page

Database Schema Password - Password to access the database schemas used by Oracle Analytics Server. This is a new password so you can enter any suitable value that satisfies the password policy of database you want to use.

But actually it is not as free as `any suitable value of database you want to use` but another hiden layer of restriction overhead. It is the entry point for new OAS marketplace adopter. New adopter will not have any idea on searching keyword "RCU“. Even as an internal user I struggled for months to understand what is RCU and hesitating if fusion middleware pages can still work on our current release.

Gianni Ceresa

@davidkhala-Oracle when you did check the logs, didn't you find messages like the following?

[VALIDATION] [ERROR]:Password contains invalid characters 
[VALIDATION] [SUGGESTION]:Ensure password contains only alphanumeric, underscore (_), dollar ($) or pound (#) characters configuration Failed. 
Exiting configuration due to data validation failure.

Just asking to see if the messages aren't there (while the doc says they should) and all you got was the posted

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

(Asking because I'm not going to create a stack with a failing password to make sure the doc is in sync with reality: it wouldn't be the first time that they aren't...)

If the messages were there, then there isn't a bug as the detailed log messages say what the issue really is.

Still it would require somebody knowing what that compute instance is like, how the product is installed, which take me back to still not seeing the benefits of the marketplace thing because if you know how to debug an OAS install you know how to install it directly in the first place (but yeah, this is a point of "we agree to disagree" with Oracle, I get it).

davidkhala-Oracle

@Gianni Ceresa all I got was the posted

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

password format validation check is a previous step. And I got it passed already.

I don't want to post the full log file as attachment. But I am very sure it is the case.