This error appears during UPD when a build fails. The _ant_generatedb will fail within a few minutes with the following error - Ant property "targetVersion" not set. This issue is because code generator has failed due to code generator files for the UPD you’re applying, hasn’t been updated properly in the build home. You will have to compare these two files:\build_home\source\fndbas\zip\ifs-codegenerator.zip (copy and extract in your user folder location)\build_home\build\IfsBuildTasks\developer.studio.libsSee if the version.txt has the version from latest UPD (from Archive) or does it have a different version applied from a hotfix. Then manually merge the correct file from Archive because the automatic merge in ISD tool will not merge the correct file.
Hi Team,While installing a fix related to reports the following error was encountered.C_RMA_PROFORMA_INVOICE_REP (CRmaProformaInvoiceRep.rdl) layout failed to importException on importing Layouts : ORA-20111: ReportLayoutDefinition.FND_RECORD_NOT_EXIST: The Report Layout Definition does not exist.But the respective RDL file was available in the delivery folder. Any idea why the above error is thrown?Thanks in advance.Regards,Nimaz
This post is just my experience with handling database and some good practices that have helped me so far. When applying a UPD we take a backup of the database and a VM Snapshot. The VM snapshot will be held for 3 days. The database backup taken by the DB Backup Management system is mostly kept for 1 week or in a very few instances for 1 month. As there are chances where the installation of the UPD might fail due to several reasons, it is a good practice to take a backup of this database into your work folder.The location of the backup can be found in this area in the DB Backup Management System Copy the RMAN folder in this location to your work folder (please note the size of the database and see if you have enough space to copy it).Now, in case the DB backups are deleted from the DB Backup Management System and the VM is expired. You can restore the database by copying the RMAN folder and pasting it into the same database folder created in corpnet Backups location. Example: \\corpnet
This is regarding Oracle Security Patches that need to be avoided when handling the apply of UPD. For App10, we follow the below document:https://ifs-my.sharepoint.com/:x:/r/personal/sampath_sitinamaluwa_ifsworld_com/_layouts/15/guestaccess.aspx?e=Z7Pv5f&CID=786C6397-3045-40ED-B5A4-9D2C8E1EBA6F&wdLOR=c7032613B-85D9-42D6-A642-2855467CD1B0&share=EWV2DnTwKJ1CtGVT6OjYEdUB8OtriBRfIiVHMEZ2QFpNrwHowever this document is not updated with bugs from APP10 UPD12 and UPD13. These bugs:Bug 159707 Bug 159363Both these bugs contain mws.zip file, so even though it’s fetched from the quick reports of mandatory and deployment bugs. Make sure these bugs are removed before merging mandatory patches and starting the build. Hopefully these bugs will be included in Oracle CPU excel sheet so it would be easier to avoid it.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
