on 03-31-2014 11:08 AM
Hi,
I am looking for limitations/issues associated with the existing plugin in Netweaver Developer Studio using which we normally generate the data dictionary for a particular JPA model persistence unit encapsulated in a ejb development component.
Currently I am facing issues when One of the JPA entity containing @OneToMany annotated column with orphanremoval option. Additionally I also observed that if even if I remove the orphanremoval option and build data dictionary DC errors the build errors out saying the below errors:
[ddgen] [Error]DtDbTable 'TMP_SVC_TMP_DEST': Table TMP_SVC_TMP_DEST is not generated
[ddgen] [Error]DtDbTable 'TMP_SVC_TMP_DEST': MySQL MaxDB:checkWidth TMP_SVC_TMP_DEST: total width(1026) greater than allowed maximum (1024)
[ddgen] [Error]DtDbTable 'TMP_SVC_TMP_DEST': Microsoft SQL Server:checkWidth (PK to TMP_SVC_TMP_DEST): total width of primary key (1020) greater than allowed maximum (900)
[ddgen] [Error]DtDbTable 'TMP_SVC_TMP_DEST': Sybase:checkWidth (PK to TMP_SVC_TMP_DEST): total width of primary key (1020) greater than allowed maximum (900)
[ddgen] [Error]DtDbTable 'TMP_SVC_TMP_DEST': SAP HANA Database:checkWidth TMP_SVC_TMP_DEST: total width(1026) greater than allowed maximum (1024)
[ddgen] [Info] Table //DtDictionary/DtDbTable:.TMP_SVC_TMP_DEST could not be generated
[ddgen] [Error] Generation failed due to errors (3 seconds)
Ant runtime 3.386 seconds
Ant build finished with ERRORS
[Error] Generation failed!
Build stopped due to an error: [Error] Generation failed!
I could find any recent blogs on any such issue. ANy help would be greatly appreciated to help me come up with a suitable design.
Thanks & Regards,
Akshay
Hi,
As it is stated in the error, the PK of the table between SVC and DEST is greater than allowed. I guess the reason is that PKs of SVC and DEST are String with width 255 characters.
I think, the easiest solution is to make the sum of the widths of both PKs(In SVC and DEST) to 255.
If you are going to use only Oracle, when generating the DB Tables you can generate them only for Oracle DB, not for MySQL and so on. There won't be an error also.
Greetings,
Ivan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ivan,
I just disabled one of the keys for the mapping table dtd and the error was gone. This confirms that the key length was greater than the limit. However is there any way to control this as the mapping table gets generated and I dont provide any entity class for the same.The primary keys for the mapping table are getting generated looking at the Svc and Dest entities.
Thanks & Regards,
Akshay
User | Count |
---|---|
82 | |
10 | |
10 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.