You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a result for issue #17 A current workaround for large text entries in p_text is to move it to the EXTRA column. In 12c this may not be required since it supports varchar2 columns of 32767 characters.
Look at modifying the text column to 32767 for 12c or greater instances. Also need to check that the large text fields don't depend on a parameter configuration in the database. If so, need to verify that parameter.
If this issue goes in, then the check in log_internal doesn't need to happen (but will still need to be supported for older versions.
select*from v$parameter
where name ='max_string_size'
As part of Issue #17 already have a new compilation parameter LARGE_TEXT_COLUMN which will remove the need for #17 (and thus a slight performance boost since not checking text size anymore).
From @martindsouza on July 27, 2013 1:59
As a result for issue #17 A current workaround for large text entries in p_text is to move it to the EXTRA column. In 12c this may not be required since it supports varchar2 columns of 32767 characters.
Look at modifying the text column to 32767 for 12c or greater instances. Also need to check that the large text fields don't depend on a parameter configuration in the database. If so, need to verify that parameter.
If this issue goes in, then the check in log_internal doesn't need to happen (but will still need to be supported for older versions.
Need to check for parameter and version number: http://dbasolved.com/2013/06/26/change-varchar2-to-32k-12c-edition/
As part of Issue #17 already have a new compilation parameter LARGE_TEXT_COLUMN which will remove the need for #17 (and thus a slight performance boost since not checking text size anymore).
Copied from original issue: tmuth#30
The text was updated successfully, but these errors were encountered: