I´m having a lot of problems upgrading eB. While doing upgrade from 15.4 to 15.6 everything was OK, but during the execution of the scripts from 15.6 to 16.7.25 I´m getting a lot of errors. I managed to solve some of the errors but some not, and I´m stuck. Next I left to you some of the errors:
Using Oracle Console I was able to get the SQL script that was producing this error:
ALTER TABLE documents MODIFY( template NCHAR(1) DEFAULT(N'N') );
The problem was that Oracle automatically created and Index for performance on that column (Template), and when the script tried to change it the error appeard.
I solved this problem droppping the Index, but I had to restore the backup of the original 15.6 database make the fix discovered and run the upgrade again.
It seems that the scripts are trying to enable a constraint, but the column of that constraint has null values. This time I cannot get ths script runnig with Oracle Console, so I don´t know which table/column has null values. Then I clicked on “YES”.
After restoring the 15.6 database and applying all the fixes to solve many problems discovered durign the upgrade, I ran the upgrade again. The upgrade run for many hours, and I left it running on some scripts that verifies the files on the repository (I know this beacause I capture ths script running using Oracle Console), then I went to sleep. The next morning I found an error stating that wanted to create an Index and that Index already existed. So if the Index already exist there is no problem, so I clicked on "Yes" to continue the upgrade process, immediately I got this error:
This error happend to me many times during various upgrade attempts.
It seems that this error occurs after a long period of time after an error window appears, and after some hours later a user click on “Yes” on that window to continue with the process. Opposite the other errors, this error is really complicated beacuse our database has more tan 1.8 million documents and many of the upgrade scripts take a lot of time to execute, so it is imposible to watch the progress of the upgrade all time and be pending of every error that shows to quickly press some button.
I need help with this last error most, because I cant´t upgrade in this conditions.
Thanks in advance.
I have more info to add....In problem 2 the complete error in the log is this:
Upgrade/1645_numerics.sql line 113, Execution time: 00:01:17.5754697Upgrade/1651_consolidate_db_schema.sql line 64, Error: ORA-02296: cannot enable (EB16CHACOUSR.) - null values foundORA-06512: at line 14Error while processing line 64 in the file 'Core.16.5.1.Oracle.zip/Upgrade/1651_consolidate_db_schema.sql'.ORA-02296: cannot enable (EB16CHACOUSR.) - null values foundORA-06512: at line 14
I need to know which is the table/column involved so I can solve the null values.
There is a known issue with Oracle Upgrade scripts described in this Wiki: https://communities.bentley.com/products/assetwise/assetwise_platform/w/eb_internal_wiki/37108/database-upgrade-extremely-slow-on-oracle-for-upgrade-step-15-6-1-to-16-1-1
I have uploaded the file mentioned in the wiki to this link: https://bentley.sharefile.com/d-s8669d4213f943dba . Just download and replace the existing file in DB upgrade scripts folder.
I am not sure this is the root cause of the upgrade issues you are getting, but from my experience with other Oracle upgrades using the modified script zip file addresses a lot of the upgrade process errors. Can you please use the attached, rerun your upgrade and let us know? After doing the above, if you still are getting errors please share the upgrade logs with us.
Also, after replacing the zip , one test I always try is to disable the options that stops the upgrade on each step or on errors and let upgrade run all the way from 15.6.1 to version you are upgrading to. That will get you a full upgrade with all errors. In some cases errors can be ignored because later scripts might have addressed the issue reported in earlier versions.
Address: Bentley | 10052 Mesa Ridge Court Suite100 | San Diego | CA | 92121 | USA
I will try and I´ll let you know....