Schema Password can not be null

[53d117460ec63d70]

I'm getting the following error when creating an OID 12.2.1.3 domain:

Schema Password can not be null. Schema Password for component ROB_WLS is null.

ERROR - RCU-6091 Component validation failed.
CAUSE - RCU-6091 One or more component specific validation failed.
ACTION - RCU-6091 Check log for more details and fix the validation error.

Model:

domainInfo:
    AdminUserName: weblogic
    AdminPassword: welcome1
    ServerStartMode: prod
    RCUDbInfo:
        rcu_prefix : ROB
        rcu_db_conn_string: 'dbhost:1521/MYDB'
        rcu_variables: 'WORK_REPOSITORY_TYPE=D,WORK_REPO_NAME=WORKREP,ENCRYPTION_ALGORITHM=AES-128'
        rcu_schema_password: 'welcome1'
        rcu_admin_password: 'welcome1'

Typedef:

{
    "copyright": "Copyright (c) 2017, 2018, Oracle and/or its affiliates. All rights reserved.",
    "license": "The Universal Permissive License (UPL), Version 1.0",
    "name": "WLS",
    "description": "WLS type domain definitions",
    "versions": {
        "10.3.6": "WLS_11G",
        "12.1.1": "WLS_11G",
        "12.1.2": "WLS_12CR1",
        "12.1.3": "WLS_12CR1",
        "12.2.1": "WLS_12CR2",
        "19.1":   "WLS_19CR1"
    },
    "definitions": {
        "WLS_11G": {
            "baseTemplate": "@@WL_HOME@@/common/templates/domains/wls.jar",
            "extensionTemplates": [ ],
            "customExtensionTemplates": [ ],
            "serverGroupsToTarget": [ ],
            "rcuSchemas": [ ]
        },
        "WLS_12CR1": {
            "baseTemplate": "@@WL_HOME@@/common/templates/wls/wls.jar",
            "extensionTemplates": [ ],
            "customExtensionTemplates": [ ],
            "serverGroupsToTarget": [ ],
            "rcuSchemas": [ ]
        },
        "WLS_12CR2": {
            "baseTemplate": "Basic WebLogic Server Domain",
            "extensionTemplates": [
                "Oracle Data Integrator - Agent"
            ],
            "customExtensionTemplates": [ ],
            "serverGroupsToTarget": [ ],
            "rcuSchemas": [ "STB","OPSS","ODI","IAU","IAU_APPEND","IAU_VIEWER","WLS" ]
        },
        "WLS_19CR1": {
            "baseTemplate": "Basic WebLogic Server Domain",
            "extensionTemplates": [ ],
            "customExtensionTemplates": [ ],
            "serverGroupsToTarget": [ ],
            "rcuSchemas": [ ]
        }
    }
}

I am able to work around this issue by adding a conditional to @@ORACLE_HOME@@/oracle_common/bin/rcu which injects the -useSamePasswordForAllSchemaUsers true argument when -createRepository is passed:

[[ $ARGUMENTS == *create* ]] && ARGUMENTS="$ARGUMENTS -useSamePasswordForAllSchemaUsers true"

[jshum2479]

Currently we don't support ODI yet, but I am curious the domain you created - does it function normally ? The rcu command line utility actual prompt for multiple questions such as supervisor password, workspace password , schema password. When I run the rcu command line create even if I specified -useSamePasswordForAllSchemaUsers. e.g: -

rcu -silent -createRepository -databaseType ORACLE -connectString localhost:1521/pdborcl -dbUser SYS -dbRole SYSDBA -schemaPrefix ODIME -useSamePasswordForAllSchemaUsers true -component ODI -variables "WORK_REPOSITORY_TYPE=D,WORK_REPO_NAME=WORKREP,ENCRYPTION_ALGORITHM=AES-128"

I got prompted for 3 times.

Enter the schema password. This password will be used for all schema users of following components:ODI,STB,WLS.

Enter the value of Custom Variable [Supervisor Password] for Component ODI [Min Length:6, Max Length:12]

Enter the value of Custom Variable [Work Repository Password] for Component ODI [Min Length:0, Max Length:10]

I am afraid the domain created may not be fully functional even if it is completed correctly. Have you tried to use the domain that involves with supervisor password and work repository password ?

[kaifricke]

ODI RCU creation requires up to 7 custom variables to be set, from which 3 are passwords. I think it is not a problem to use the current WDT RCURunner to provide those , except that you want to encrypt the passwords or put them into a property file (I have not tried if the second works or not). As I mentioned in a different post, the other issue to create a functioning ODI domain is to create a credential mapping , which requires a FMW WLST function to be executed (currently) after WDT was running.

-Kai

[53d117460ec63d70]

Ah yes, I should clarify. I have not been able to successfully create an ODI domain from WDT. I am raising these issues in pursuit of that when I hit a stumbling block. The initial failure is during RCU creation. Using the above model and typedef file I am not prompted for any input but RCU creation fails with Schema Password can not be null. If I hack @@ORACLE_HOME@@/oracle_common/bin/rcu to pass the argument -useSamePasswordForAllSchemaUsers true during the -createRepository phase WDT creates all schemas successfully but the build fails at a later point (during writeDomain), mentioned in kaifricke's comment and described in another issue that I have raised.

Regarding this issue, could RCUDbInfo support a useSamePasswordForAllSchemaUsers attribute? I'm aware this wouldn't accommodate a scenario where we do want different passwords for each of the schema users but could be a quick win where we don't.

[jshum2479]

I doubted that is the only thing for rcu to complete. I have tried to use rcu in silent mode (not through wdt) with -useSamePasswordForAllSchemaUsers and it still prompt for other non-schema passwords. This means it needs to be provided as input for rcu to truly succeed.

The current WDT implementation actually has flaws, it just repeat to use the same schema password based on number of schema components + (1) and enter as many times as needed - regardless of what's being prompted.

We do intend to intend to change it to use -useSamePasswordForAllSchemaUsers but there still works to be done for rcu to work with odi - whether there is way to provide encrypted input as variable like @kaifricke mentioned or we invent some fields in domainInfo and use it as input.

We have floated some ideas on adding custom wlst script but nothing concrete yet.

There is a testoim branch which I have setup to accept other keys in the domainInfo section for creating OIM domain, conceivably we can do something similar to support ODI.

We need to do some research internally to see what's the best way to accomplish these different issues first.

[kaifricke]

If you anyway look into RCU, please consider also to support
[-compInfoXMLLocation omponentInfo.xml_file_location] and
[-storageXMLLocation Storage.xml_file_location] flags.
I am most probably the only one in the world extending RCU and requiring that options, but.....

[CarolynRountree]

-useSamePasswordForAllSchemaUsers is already used on createRepository and dropRepository.

Added support for compInfoXMLLocation and storageXMLLocation. Will be in the next release.

[vdrHorst]

variables SUPERVISOR_PASSWORD and WORK_REPO_PASSWORD can be used