Hello Karl, I was check then errlog.log and see this : BLACKY ::[32808 , 4e692b60]: Thu Apr 21 13:44:51 2005 E_DM011F_TRAN_ABORTED The transaction has been aborted to release transaction log space.
I repeat the upgrade and look the headers in the ingres monitor , in some moment the transaction log file it's too big taking 90% of space available and force abort. How can I increase the max size of the log file variable ? Thanks , Jose >>Hi , >>We are doing a migration from ingres 2.6 to ingres R3. It's a >>clean-install upgrade. I use the migration guide step 2 , and do a >>migrate test with the development database. >>When we are trying to upgrade front-end catalogs receive this error : >> >>upgradefe produccion INGRES >> (module CORE version 2 is already installed) >> Upgrading to front-end module APPLICATION_DEVELOPMENT_1 version 5 . . . >>E_US1264 The query has been aborted. >> (Wed Apr 20 12:17:21 2005) >>E_DD0026 Cannot upgrade to module APPLICATION_DEVELOPMENT_1 version 5. >> Error 1 occurred trying to upgrade to this front-end catalog module. >> Check if this error number is an operating system error. If not, then it >> is an internal Ingres error. Contact your site technical contact for >> assistance. >> > Which release of r3, and which platform? > Can you try running it with II_EMBED_SET=printqry set (setenv with a > c-shell)? That should show the queries including the failing query > in iiprtqry.log. "query has been aborted" with no explanation is > a bit odd. Is there anything in the error log from that time period? > Karl > _______________________________________________ > Users mailing list > [email protected] > http://ingres.ca.com/mailman/listinfo/users -- Best regards, Jose mailto:[EMAIL PROTECTED] _______________________________________________ Users mailing list [email protected] http://ingres.ca.com/mailman/listinfo/users
