Note, that upgrade from 2.1.2a (b 209) to the 3.2.1 (b 495) succeeds.

dobe is testing this upgrade from 2.1.a to 3.1.2.a3. and reported following error,

While applying the patch, we are facing this

[4/22/10 11:41:22:563 IST] 0000001a SchemaBootstr E org.alfresco.util.LogUtil error Statement execution failed:
SQL: alter table "ALF_ATTRIBUTES" disable constraint "FK_ATTRIBUTES_N_ACL"
Error: ORA-02431: cannot disable constraint (FK_ATTRIBUTES_N_ACL) - no such constraint

File: C:\Users\ADMINI~1\AppData\Local\Temp\1\Alfresco\AlfrescoSchema-AlfrescoOracle9Dialect-Update-2773935969724598448.sql
Line: 38
[4/22/10 11:41:22:563 IST] 0000001a SchemaBootstr E org.alfresco.util.LogUtil error Schema auto-update failed
java.sql.SQLException: ORA-02431: cannot disable constraint (FK_ATTRIBUTES_N_ACL) - no such constraint

======= Adobe made above contraints optional and tetsed further, following error was reported after that,

FK_ATTR_N_ACL is the constraint. Your script mentions that as FK_ATTRIBUTES_N_ACL. In addition we got one more error

[4/22/10 16:40:14:580 IST] 0000001b SchemaBootstr E org.alfresco.util.LogUtil error Statement execution failed:
SQL: INSERT INTO alf_access_control_entry SELECT * FROM NSI_ACE_TEMP
Error: ORA-01438: value larger than specified precision allowed for this column

File: C:\Users\ADMINI~1\AppData\Local\Temp\1\Alfresco\AlfrescoSchema-AlfrescoOracle9Dialect-Update-6103548449230263441.sql
Line: 208
[4/22/10 16:40:14:580 IST] 0000001b SchemaBootstr E org.alfresco.util.LogUtil error Schema auto-update failed
java.sql.SQLDataException: ORA-01438: value larger than specified precision allowed for this column

at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:79)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112)

r19983 | derekh | 2010-04-26 11:52:42 +0100 (Mon, 26 Apr 2010) | 7 lines

Changes for ALF-2545: Cannot upgrade from 2.1.2a (b 209) to the 3.1.2 (.a3 458) on Oracle

• Examined client-supplied scripts, which made some fixes but also reversed the upgrade-from-2.1.sql
• Took changes for the ACL scripts
• Alternate constraint enable/disable with appropriate optionals
• CAST function for temp table
• Column ordering for 'alf_access_control_entry'

This should be the QA-raised "value larger than specified precision allowed for this column" and constraint naming issues.

Issue appears during upgrade from 2.1a (builds 209/220/222) to 3.2.1.499 although doesn't appear during upgrade to 3.2.1.495.

We need to validate whether the upgrade was successful. The null pointer on restart is most likely to be due to a problem in overridden code (e.g. overridden bean missing some injection). To check that a schema and data upgrade was successful, starting a standard Alfresco WAR against the data will indicate whether the null pointer issue is schema+data upgrade related.

Still reproducible with 3.2 SP1 HF2 during upgrade from 2.1.4a (b 222) to the 3.2.1 (.2 3) both on Oracle 10g and 11g.
(upgrade logs attached)

Issue was actually submitted during testing upgrade to 3.1.2.a3.458 - the last 3.1.2.ax build available currently on FTP: ftp://ftp.alfresco.com/qa/Enterprise%203.1/.
As well issue is still actual for this branch.

Will be tested against 3.1.2.6 (build 16) in scope of ALF-2806 testing.

Successfully validated for 3.1 SP2 HF6 (build 16) upgraded from 2.1.4a (b 222) both on Oracle 10g and 11g, with clean db and with generated template data.
(upgrade logs attached)

But still reproducible with 3.2 SP1 HF2 during upgrade from 2.1.4a (b 222) to the 3.2.1 (.2 3) both on Oracle 10g and 11g.

Not reproducible during upgrade 2.1.4a (b 222) -> 3.3.0 (b 64) on Oracle 10g (both clean installation and upgrade data template).

Successfully validated for 3.1.2.a4 (build 462) upgraded from 2.1.4a (b 222) both on Oracle 10g and 11g, both with clean db and generated template data.
(upgrade logs attached)