...
The entire installation and upgrade process is described in the Solution overview, Glossary, Quick Reference here and must be followed.
Incompatible objects
...
| Note |
|---|
It is strongly recommended to perform a product upgrade at a marginal time or in a locked upgrade window. |
Details about imports into running systems are documented in the following SAP Notes:
1454536 - Deadlock on table REPOSRC when importing into running system
2793192 - Avoid deadlocks on table REPOSRC during parallel import
3204136 - Transport import error - sql error: 133 transaction rolled back by detected deadlock
Errors in the transport system
Occasionally, errors occur during import caused by technical problems in the transport system. ProNovia has no influence on such errors. Such errors can have a wide variety of causes. They can be errors of SAP programs but also of the components R3trans or tp, which are necessary for the import. In a first step it is recommended to restart the import again. If the same error occurs again, check the SAP knowledge base to see if there is a solution.
Previous version not matching when importing ProNovia products
When importing ProNovia product transports, they may appear in the import queue with the status Does not match component version. This status indicates that the installed SAP components (and versions) on the ProNovia origin system do not match their system. However, this check can be ignored for the import of ProNovia products, since ProNovia products are delivered in their own namespace and ProNovia ensures compatibility with SAP components.
To import the transports, the option Ignore non-matching component version must be activated during the import.