Upgrading an on-premises Touch App Server (TAS) installation across Update levels, the installer errors out right after entering database details, even though all the prepare-TAS and pre-deploy database scripts (permission grants, tablespace creation) already ran without any errors. What resolves this?

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Try completely dropping the TAS-specific database user and letting the installer recreate it fresh, rather than trying to reuse or repair the existing one — this has resolved exactly this kind of installer error partway through entering database details during a TAS version upgrade. Also worth knowing: this TAS installer track doesn't require a separate Oracle client to be installed on the machine running it.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions