I'm not sure if I've understood your starting point.
Do you mean you already have a split schema in your pre-upgrade 6.2 environment?
Or are you previously running the migrate.sh script to move the rules tables to a new schema?
Also, what output do you see when you run generateddl.sh --action upgrade
Does this show any errors or any output at all?
Incidentally, I believe the script may try to clear up the previous run's files in /schema/generated/oracledate so if you have, say, another command line session currently in this directory then this may cause the cleanup to fail.
We are doing an in place upgrade in dev environment from 6.2 to 7.2.2. We are using the Run book for Non Admin User.
We have created a new blank schema and completed the rule Migration process successfully. This Rule Migration Process comprised of Editing MigrateSystems.Properties file. I am attaching the parameter format I used in this process. Next Executed Migrate.sh. Next Executing the SQL scripts got generated in OracleDate Folder by a databaseAdmin User. Next again we edited the MigrateSystems.property file with following parmeter[attached]Next we again executed the migrate.sh script
Upto this process was success ful and we entered in RuleShema Upgrade stage
In this step we were supposed to execute generateddl script. check the oracledate folder for generated sql and execute them using DAdmin User. But no sql script generated in oracledate folder although generatyeSQL got executed sucessfully
Thanks Laurence. It has worked now. I have one more question to you. While executing the Upgrade Shellscript after this process we hve to maintain the following setup in SetUpDataBase Property file to skip DDL Generation again