Description:
This hotfix doesn't need any TRA hotfix. The patch can be downloaded from the TIBCO Support ftp server, support-ftp.tibco.com. Please use your eSupport username and password to access the server. After connecting, go to

ActiveEnterprise/SmartMapper-Enterprise-Server/5.3.0/hotfix-03/TIB_smartmapper_5.3.0_hotfix03.tar.gz
ActiveEnterprise/SmartMapper-Enterprise-Server/5.3.0/hotfix-03/TIB_smartmapper_5.3.0_hotfix03.zip
ActiveEnterprise/SmartMapper-Enterprise-Server/5.3.0/hotfix-03/readme-BWSM_5.3.0_hotfix03.txt
To download the appropriate hotfix for your OS/platform.

===============================================================
Closed Issues in 5.3.0-hotfix04 (This Release)

===============================================================
Affected Files for 5.3.0-hotfix04

All Platforms:

  - readme-BWSM_5.3.0_hotfix04.txt
  - xrefplugin.jar
  - xref.jar
  - xrefadminui.war

Note: Make backup copies of the existing xrefplugin.jar, xref.jar and
xrefadminui.war files before overwriting them with their
corresponding file in this hotfix.

======================================================================
Closed Issues in 5.3.0-hotfix04 (This Release)

1-8FEXBF
The Dynamic lookup activity failed with an error "ORA-01000: maximum
open cursors exceeded" while entity lookup was performed several times.  
This has been fixed.

1-8GP2Y3
The activity "Dynamic delete" was throwing an exception "maximum open
cursors exceeded" while trying to delete entities. This was happening
with both JDBC and Adapter repositories.
This has been fixed.

Note: BulkExtract activity, when configured for Subset based
extraction, will give "Object has been Closed" error in cases when
the extraction process takes longer than 5 minutes and the connection
times out.

This problem can be worked around by setting the following java
property in designer.tra (or adsmartmapper.tra for the Enterprise
version):

java.property.com.tibco.solution.sm.agedTimeout 3600000


1-8FH9IC
The activity "Delete Relationship Instance" was throwing an exception "java.lang.RuntimeException: no entryid" when the following conditions
were met:
- Cache was enabled
- An update was done to one of the entities in the relationship instance
  just before the deletion was attempted.
This has been fixed.