Hi Joachim,
I created a very simple headless GLORP/DB2 application for testing purposes and tried packaging using the following scenarios. All tests run using 9.2.2 x64:
1) On Windows x64 using UNIX XD image with Database - Glorp, DB2 CLI and Database - DB2 CLI installed features.
2) On Windows x64 using UNIX XD image with only Database - Glorp, DB2 CLI installed feature.
3) On Linux x64 using UNIX XD image with Database - Glorp, DB2 CLI and Database - DB2 CLI installed features.
4) On Linux x64 using UNIX XD image with only Database - Glorp, DB2 CLI installed feature.
I did not see any of the errors you documented in the Transcript, or elsewhere, for any of the scenarios.
My test app has a single class method which creates a connection to the database and then creates and deletes a table from the Samples database:
runTest
"comment"
| login table accessor keyField |
login := Login new
database: DB2Platform new;
username: '<username>';
password: '<password>';
connectString: 'sample'.
accessor := DatabaseAccessor forLogin: login. accessor login.
table := DatabaseTable named: 'GlorpTest'.
keyField := table createFieldNamed: 'cust_no' type: accessor platform int4.
table addAsPrimaryKeyField: keyField.
table createFieldNamed: 'cust_name' type: (accessor platform varChar: 255).
accessor createTable: table ifError: [:err |].
accessor dropTable: table ifError: [:err |].
accessor logout.
The prereqs for the app are GlorpVAPortCLISupport and GlorpVAPortPostLoad. Might be interesting to see what results you get with this. Maybe use this as a starting point to develop a better example.
An additional suggestion ... if you do have some defective LibraryObjects, I don't think cloning will eliminate them. Maybe you should try starting with a brand new manager and export your code into it to see if the problem still exists.
Regards,
Bob