- ABP Framework version: v5.1.2
- UI type: Angular
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): yes
OracleRelationalCommand.ExecuteReaderAsync() : Oracle.ManagedDataAccess.Client.OracleException (0x80004005): ORA-12899: value too large for column "ABDEV"."ABPAUDITLOGS"."EXCEPTIONS" (actual: 15651, maximum: 4000)
Hi. I faced with the situation that some exception cannot be stored because the value is too large for column "ABPAUDITLOGS"."EXCEPTIONS". At this moment I use "Volo.Abp.AuditLogging" module version 5.1.2. Unfortunatly, I didn't manage to find any logic in this module which can truncate too large text of exception. Could you please advice how this issue can be fixed? Not by incrementing the column length.
5 Answer(s)
-
0
Hi.
I've read the thread which you advice. But this solution looks like a trick. Would be great if the logic was contained inside "Volo.Abp.AuditLogging" and there was no need to make external solution modifications. We use ABP framework for developing a lot of services. What will happen, when ABP team changes the logic and structure of AuditLog tables in some new release?
We would prefer to truncate an error message for AuditLog instead of changing the corresponding DB field size. What is a proper way of doing this?
-
0
another solution https://github.com/abpframework/abp/issues/6341#issuecomment-733669760
-
0
First of all, the "MaxExceptionsLengthValue" property is missed in "Volo.Abp.AuditLogging.Domain.Shared" package version "5.1.2". Besides, you suggest me to make changes inside ABP module. Also, I've asked, "How exception can be truncated"? I don't want to change the length of DB field.
-
0
How exception can be truncated
Override the
AuditLogInfoToAuditLogConverterservice.https://github.com/abpframework/abp/blob/46de78b1b8bd1d7dff06e808179d08c0c3c958ca/modules/audit-logging/src/Volo.Abp.AuditLogging.Domain/Volo/Abp/AuditLogging/AuditLogInfoToAuditLogConverter.cs#L56
